Skip to content
Student & faculty portalLex Astra · Founded 2891Governance
EXCELLENCE THROUGH DISCIPLINELex AstraACADEMY

Excellence
Through Discipline

CS 115 / Civil Services

Reception and passenger accountability

Prepare a CradleFleet passenger movement and confirm who boarded, arrived or still needs contact.

Publication and delivery

This course is published for study. Publication does not confirm an available class, appointed instructor or completed practical validation. Before booking, obtain a session brief naming the organiser, instructor and assessor, equipment access and any independent review arrangements.

Before live assessment, the organiser must record the current LIVE build, validation date, ship and equipment used, tasks checked and any known limitations. If a required mechanic is unavailable, defer the affected assessment rather than certify an unobserved outcome. A material game update calls for a check of affected tasks, not cancellation of earlier academic achievements.

Your brief

For cradleFleet boarding and reception coordinators.

The civil school applies the distinction between departure and receipt to passenger care. A passenger must not disappear from the record because the vessel completed its trip.

A passenger missing from reception

Practice case · CS 115 · 2956 teaching edition

  • P-01 through P-04 are volunteer identifiers on the boarding list.
  • All four are confirmed boarded. Reception confirms P-01 through P-03.
  • P-04 has disconnected; their latest in-game location is not currently confirmed.
Before you begin: entry and equipment

Bring or arrange

Volunteer passengers, suitable berths and a tested route.

The organizer must confirm equipment access before booking. No ship purchase, pledge tier or donation is required.

Technical knowledge and game skills

Practical instruction revision 1 · 9 October 2026

Passenger handling at ramps, lifts and landing sites

Make boarding physically workable

Choose an assembly point outside landing and loading movement. Explain the route to the ramp, lift and seat, then board in a sequence that avoids crowding narrow access. Test a lift before committing the full group. Verify that passengers have environmental protection for every exposed part of the journey, not merely for the destination interior.

Secure the cabin before flight

Check each person is aboard and in a usable seat where available; do not infer this from a party marker hovering near the hull. Confirm ramps and external doors are closed. Warn the pilot about anyone still moving or unable to use the intended seating. Boarding completion and readiness for manoeuvre are separate calls.

Deliver beyond the ramp

After landing, confirm the exit is usable and the ground is suitable before releasing passengers. Use one guide at the receiving point and one final cabin check. Record remaining aboard, disembarked and received separately. If the lift or ramp fails, keep passengers in a safe location while the crew tests an alternative instead of encouraging repeated jumps into an uncertain opening.

Practical drill

Board a small group, perform a short trip and guide them to a named reception point. Simulate a failed exit or missing passenger report and reconcile the cabin and reception counts.

Observed-skill checks

  • All passengers can reach their assigned places with the equipment worn.
  • The pilot receives a verified cabin-ready call.
  • A receiving count is based on actual arrivals, with unresolved people assigned a follow-up.

Use these checks to document the technical evidence supporting the course outcomes in your agreed role. Record what you personally performed, what assistance you needed and what remains unobserved. A discussion or simulated action does not certify live equipment handling; Crew Support evidence does not confer Pilot qualification.

Game references and build-sensitive details

The linked pages were read for this revision. Community references mix release eras; each source note identifies what is used and what is excluded. Technical explanations below are an Academy synthesis, and drills and performance checks are Academy-designed. Before practice, compare the named actions with the installed LIVE build and actual equipment. Bind actions by name rather than copying old default keys. Research is not an in-game validation.

  • Star Citizen Wiki — Controls

    Control categories, movement axes and targeting concepts. The page contains legacy bindings and flight-system descriptions; use the installed game’s bindings, not its key table.

  • Star Citizen Wiki — Medical

    Body-part injuries, Hemozal, symptom medication, BDL, bed tiers and regeneration. Ship tables, resource costs and ranges change; inspect the actual bed and tool.

Check the official LIVE release notes and record the session build, equipment and observed limitations before practical sign-off.

Learn the method

1. Collect only what the movement needs

Use passenger handles or exercise identifiers, boarding point and the agreed movement need. Do not collect private health or identity details. Make sure the departure and reception teams use the same identifiers so they can compare lists.

Reception begins before boarding. Tell passengers where to assemble, how their exercise identifier will be checked and what to do if they lose contact. Confirm the destination and any agreed assistance need in operational terms. A short, understandable instruction is more useful than a detailed manifest the passenger never sees.

Practise
Prepare the passenger list and boarding brief.
Ready when
The list supports matching passengers across the movement without unnecessary personal data.

2. Count boarding and arrival separately

Name who confirms boarding and who confirms receipt. Read back changes to either list. A seat assignment, boarding report and arrival report describe different events; do not advance a passenger to the next state without confirmation.

Use one receiving confirmation for each passenger, tied to an identifier and time. At destination, distinguish remaining aboard from reaching the agreed reception point. A transport report can establish that the vessel landed without establishing that every passenger left it or reached the receiving coordinator.

Practise
Run boarding and receiving checks with volunteers.
Ready when
The record contains separate, confirmed departure and arrival counts.

3. Keep the missing check-in visible

Record the last confirmed state, current uncertainty and person making contact. If the passenger reconnects, update the list with the new observation. Do not diagnose a missing check-in or remove it to make the totals match.

For P-04, keep four boarded, three received and one unconfirmed as separate facts. Assign a reconnect contact and a next update, then check the last supported location before proposing recovery. If the session closes, transfer the contact task explicitly; an unresolved arrival must not disappear when the original coordinator leaves.

Practise
Handle one missing arrival acknowledgement.
Ready when
The record preserves the missing passenger and a clear contact or recovery action.

A worked decision

P-04 disconnects after boarding. Reception confirms three arrivals and keeps P-04 unconfirmed with a reconnect contact.

  1. Enter four boarded and three received as separate observations. Leave P-04 unconfirmed with the earlier boarding report preserved.
  2. Assign a reconnect contact and tell the transport and reception roles who owns it.
  3. Update P-04 only when new evidence arrives, and hand over the contact task if the session ends first.

Try it yourself

Brief boarding, compare the arrival list and handle the missing check-in. Finish with an accepted follow-up, not a falsely balanced total.

What changes during the exercise

One passenger does not check in at the destination.

Keep this record

  • Passenger identifier / boarding confirmation / time
  • Arrival confirmation / receiver / current state
  • Unconfirmed passenger / last observation / contact owner

Download CS 115 worksheet

Plain-text worksheet with this case, your working fields and the assessment criteria. Fill it in privately; downloading does not submit work or record completion.

Check your reasoning

Four boarded and the ship arrived. What arrival total can Reception enter?

Compare your reasoning

Only the passengers actually confirmed at reception. Keep the others unconfirmed and investigate the gap; a vessel’s arrival is not four separate passenger confirmations.

Answer first, then compare. In a later session, explain the decision using a changed case without referring to this answer.

How completion is judged

Matched departure and arrival lists and the missing-check-in handover.

The assessor checks your own work against all three “Ready when” criteria above. Use the observed-skill checks in the technical chapter to establish the applicable game-handling evidence in your agreed role. A successful team result does not replace an action they did not observe.

Findings, another attempt and review
Demonstrated
Your observed work meets the criterion in the agreed role.
Further practice required
The assessor identifies the observed gap and the specific practice needed.
Interrupted
Equipment, staffing or personal circumstances prevented a valid assessment. This is not a failure.
Not assessed
There is not yet enough evidence for this outcome.

A fresh attempt

Use a passenger confirmed waiting at origin rather than disconnected after boarding. Require the correct state and onward plan.

Reassess the missing outcome, plus any linked skill that needs new evidence. For prior learning, compare existing work with the same criteria and observe any missing practical action.

Ask for the reasons behind a finding. Reviews must be handled by someone independent of the original decision; defer the review if that person is not available.

Read the Academy Ordinance and review rules

For instructors

Session setup and coaching

Prepare the session

Volunteer passengers, suitable berths and a tested route.

Assign crew stations and tell each learner what they will practise. The instructor must be able to hear the calls and see the action being assessed. Brief the callsigns, channel, route and expected duration. Replace the example locations with the places you will actually use.

  1. Ask the learner to explain the relevant earlier procedure without notes; correct any gap before the practical.
  2. Teach and demonstrate the technical chapter using the actual game indications. Run its drill with feedback before connecting those skills to the three methods and worked decision. Use the observed-skill checks to identify missing handling evidence.
  3. Let the learner complete the normal procedure first, then introduce the change described in the exercise. Give them time to respond without coaching. Keep unrelated failures out of this attempt.
  4. Record the learner's action against each criterion. Give one specific next step for any gap and transfer unfinished operational work before closing.

What to watch for in CS 115

Check that the learner does not request private health details to explain a disconnect. The movement needs a contact and recovery action, not a diagnosis.

If another attempt is needed

Use a passenger confirmed waiting at origin rather than disconnected after boarding. Require the correct state and onward plan.

Running the exercise

Before the crew assembles, try the exercise in the ship you intend to use. Check station access, equipment and the route. Brief the crew on any faults that affect the task. If a bug prevents someone completing it, repeat that part once it works; do not record a failure for a broken mechanic.

Brief the command “Stop exercise” before starting. On that call, cease the drill and tell the instructor what needs attention. For weapons practice, identify the participating ships and crew; anyone else entering the area is a reason to hold fire.

Session administration: use player handles in your notes. Ask before recording voice or video, and agree when the recording will be deleted. Academy rules and review procedure.

Sources and edition

Lex Astra · School of Civil Practice
Course CS 115 · edition 2956.3 · 2956 teaching edition · revised course text.

Case CS–3: one berth remaining

Civil Practice case issued by CDR Yuki Tanaka-Reis in 2956. These variants use present-day service responsibilities and new training lists; they are not transcripts of the Pyro Station Alpha response.

Professional references and instructional revision

Instruction revised 9 October 2026. Lex Astra cases supply the teaching situations. Professional references inform communication, decision-making and instructional design; they do not confer external qualifications. LIVE capabilities remain subject to the recorded session check.

Editorial context and teaching basis

The lessons are current Academy teaching, not newly discovered historical records. Lex Astra opened in 2891. Historical sources keep their original issuer and date; all case callsigns, quantities, times and conditions are supplied for practice.

Your session brief names the instructor, the crew assignments and the equipment provided. Contact the teaching office above to arrange a place.

Course-text revision: 8 October 2026. Educational references were reviewed for the framework on 8 October 2026; they inform the teaching approach, not external accreditation or current game-capability claims.

Teaching research and its limits

Where this leads

Civil Services requirements

Courses that use this work

Course records retain the edition and role assessed. New teaching text does not erase earlier achievements.