FO 220 · Ship systems and emergency coordination

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 bridge and systems coordinators; physical repair is assessed separately.

The watch leader must decide whether a vessel can continue even when the crew cannot establish that an intervention worked. Fleet Studies teaches the coordination decision here.

The intervention did not clear the indication

Practice case · FO 220 · 2956 teaching edition

The station reports indication F1. The facilitator separately supplies a reduced-capability condition.
One operator can perform the session-checked action; a second observes status.
After the action, no improvement is confirmed.

Before you begin: entry and equipment

Complete these courses

Bring or arrange

Available ship-status displays or a clearly labelled tabletop fault packet.

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

Abnormal flight and damage response

Stabilise before troubleshooting

When thrust or attitude response changes, reduce the task to maintaining a clear flight path. Compare commanded input with velocity and rotation; asymmetric thrust may make the usual correction excessive. Move away from terrain and traffic if control allows. Do not shut down the whole vessel in atmosphere as a generic reset: the loss of lift can turn a manageable fault into impact.

Separate power, component and interface faults

Ask engineering for the relevant component state and supply path while the pilot checks engine and mode indications. A dark display, an unpowered component and a damaged thruster are different observations. Make one authorised intervention, then compare the same indication. Repeated blind toggling removes the ability to determine which action affected the fault.

Fly the reduced capability

After an apparent recovery, test small inputs in clear space before returning to an approach. Reassess stopping, vertical support and turn response, allowing larger margins. If the ship cannot sustain the required landing profile, select a suitable alternate or arrange recovery rather than continuing because the route was already briefed. Inform passengers before movement or evacuation changes.

Practical drill

Use a reversible, instructor-tested configuration change to simulate reduced capability in clear space. Stabilise, report the symptom, restore or isolate the tested cause, and demonstrate the revised handling envelope before recovery.

Observed-skill checks

The pilot preserves clearance while diagnosing.
The crew distinguishes observation, hypothesis and intervention.
Continuation is based on a handling recheck, not merely a cleared warning.

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 — Engineering
Engineering terminals, components, fuses, heat and fires. This community overview is incomplete; verify each interaction and vessel’s support in the session.

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

Learn the method

1. Identify the source of the fault report

Write down the indication, where it appeared and who observed it. If the facilitator supplied the fault, label it as a scenario condition rather than a display reading. This distinction tells the crew what can actually be checked.

Describe the operational consequence before naming a presumed cause. “This station no longer provides the required indication” is actionable even when the crew cannot establish why. Compare independent observations where available, but do not mistake several people reading the same display for independent confirmation of the underlying fault.

Practise: Compare a station report with an exercise fault notice.
Ready when: Each fault entry identifies its source and what remains unverified.

2. Assign work that the crew can perform

Check the crew’s position and the mission’s stop conditions before assigning an intervention. Give each task to someone with the right station, tools and preparation. Keep a monitoring role separate from the repair attempt so someone can assess the result.

Prioritise maintaining control, accounting for the crew and preserving a recovery option before restoring the original schedule. Ask what an intervention may interrupt and notify those stations first. An operator sent to investigate cannot simultaneously be counted as continuously monitoring the station they have left.

Practise: Allocate a status check and response to two competing faults.
Ready when: Your assignments match the available capabilities and preserve crew accounting.

3. Check the result before continuing

Compare the same indication before and after the action. If it has not improved, say so and consider withdrawal or a reset. “Action attempted” and “fault cleared” are different statements and lead to different movement decisions.

Set a continuation condition before the attempt: which indication must change, who will verify it and which limitation would still prevent movement? This avoids redefining success after an inconclusive result. A reduced mission may be acceptable even when the original mission is not; state the new limit explicitly.

Practise: Brief the decision after an intervention produces no confirmed improvement.
Ready when: You report the observed result and justify continuation, withdrawal or reset.

A worked decision

A scenario fault reduces available capability. The coordinator shortens the movement and records the limitation without claiming that a physical repair took place.

Enter the display report and facilitator condition as different sources. Ask which limits each one places on the movement.
Assign the checked action and keep someone watching the relevant indication. Notify affected stations before the attempt.
Record the unchanged or missing feedback. Compare it with the mission’s stop limit and recommend withdrawal or reset where continuation is unsupported.

Try it yourself

Produce the fault log and direct the response. State what the crew knows after the attempt and what evidence would permit continuation.

What changes during the exercise

The proposed intervention produces no confirmed improvement.

Keep this record

Fault / source / indication / operational limit
Assigned action / operator / monitoring role
Before and after / uncertainty / continue or withdraw decision

Download FO 220 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

The operator completed the requested action. Is the ship ready to continue?

Compare your reasoning

Not yet established. Check the resulting indication and the mission’s limits. If the effect cannot be verified, report that uncertainty instead of treating effort as repair.

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

How completion is judged

A source-labelled fault log and observed crew assignments and decisions.

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

Provide confirmed improvement on one indication but leave a second limit unresolved. Require a decision that considers both.

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

Available ship-status displays or a clearly labelled tabletop fault packet.

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.

Ask the learner to explain the relevant earlier procedure without notes; correct any gap before the practical.
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.
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.
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 FO 220

Keep the coordination outcome separate from engineering manipulation. A learner may make a sound withdrawal decision without claiming a repair.

If another attempt is needed

Provide confirmed improvement on one indication but leave a second limit unresolved. Require a decision that considers both.

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 Fleet Studies
Course FO 220 · edition 2956.3 · 2956 teaching edition · revised course text.

Case FO–7: the vessel that misses assembly

Fleet Studies case issued by CAPT Renard Okonkwo in 2956. These new practice variants extend its receiving-window and watch-handover problem; their callsigns, quantities and times are teaching inputs, not additional historical facts.

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

Fleet Operations requirements

Courses that use this work

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