FO 150 · Shipboard roles and bridge 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 teams coordinating helm, navigation, status and mission roles.

Fleet Studies separates the bridge lead’s movement decision from the information supplied by each station. The case makes that separation observable.

One helm, two requests

Practice case · FO 150 · 2956 teaching edition

Helm is following the accepted approach. Navigation reports a limit requiring a hold.
Mission staff request an immediate change to a new destination.
The bridge lead owns the movement decision; the status operator then leaves the station.

Before you begin: entry and equipment

Complete these courses

Bring or arrange

A crewed vessel or station tabletop, a shared role list and communications.

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

Bridge systems and multicrew station work

Read the ship before issuing instructions

Walk from bridge to engineering, turret access, cargo space and exits. At each supported station identify its actual controls and readouts. The pilot reports flight mode and velocity; the engineer reports power, component and environmental limitations; gunners report available arcs and readiness. A seat labelled co-pilot does not imply every pilot control is duplicated.

Change configuration as a coordinated action

Before changing travel mode or allocating power, say which capability may be reduced and what the next task needs. Watch the resulting shield, weapon or thruster indications rather than assuming a command completed instantly. If a turret cannot bear on a contact, report the blind sector to the pilot; do not demand an unexplained turn that could spoil an approach.

Transfer actual control

The relieving operator checks the display and confirms the pending action before the outgoing operator leaves. For pilot transfer, first establish a stable state in a clear area and verify how the particular ship transfers control. Do not conduct an untested seat swap during descent. If the expected interface is unavailable, retain control and revise the role assignment.

Practical drill

Brief a crewed ship’s real station capabilities, conduct a travel-to-working-mode transition, then relieve one non-pilot station with an unresolved fault. Practise pilot relief only after checking that ship’s supported method.

Observed-skill checks

Reports identify actual indications and station limitations.
Configuration changes are announced and their effects confirmed.
Relief preserves control and explicitly transfers the pending task.

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 — Engineering
Engineering terminals, components, fuses, heat and fires. This community overview is incomplete; verify each interaction and vessel’s support in the session.
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 — Master Modes
SCM and NAV distinction. Check the actual mode, transition and available systems on the session build.

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

Learn the method

1. Name the decision owner

Separate steering the vessel, preparing the route, monitoring status and deciding the mission’s next step. One person may hold more than one role, but the crew must know which responsibility they are exercising. Identify who resolves competing requests.

Distinguish an information report from an order. Navigation may report that the route is unavailable while mission staff request a new objective; neither should produce an uncoordinated helm input. Brief who has the movement decision and how the helm recognises an immediate safety call without waiting through a conference.

Practise: Make a station and decision-owner list.
Ready when: Every station and movement decision has a named owner.

2. Turn competing requests into one instruction

Ask the helm to hold the affected action while navigation and mission staff explain the conflict. The decision owner chooses, then states one instruction and what has been deferred. Have the affected stations repeat the relevant detail.

Resolve conflicts at the smallest useful level. Ask Navigation for the constraint and mission staff for the required result, then choose an instruction that the helm can execute. State which earlier instruction it replaces. Avoid passing the disagreement down to the operator who has the least time to interpret it.

Practise: Resolve a new mission destination during an approach warning.
Ready when: The crew acknowledge one movement instruction and know which request was deferred.

3. Relieve a station without losing its state

Report the current setting, pending action, known limitation and next report. Ask the incoming operator to confirm all four. Do not treat sitting at the station as acceptance of every task previously assigned there.

Relief includes pending commands and abnormal conditions, not just normal settings. If an action was requested but not executed, say so explicitly. The incoming operator checks the actual station against the report before accepting; a written handover must not conceal a display or control state that has changed in the meantime.

Practise: Relieve a station with a status report outstanding.
Ready when: The incoming operator can explain the station state, open task and escalation contact.

A worked decision

Mission staff request a new destination while navigation reports an approach limit. The bridge lead pauses movement, hears both and issues one revised instruction.

Hold the affected movement and ask each reporting role for the fact behind its request.
The bridge lead selects one instruction and states which request is deferred. Helm reads it back; Navigation confirms the route implications.
Assign the vacant status task or reduce the operation until it is covered. Give the incoming operator the last reading and pending report.

Try it yourself

Run the conflicting requests once, then repeat with roles swapped. End with one acknowledged movement instruction and an accepted station relief.

What changes during the exercise

The monitoring station becomes vacant during the disagreement.

Keep this record

Station / operator / decision owner
Competing requests / selected instruction / deferred task
Relief: state / pending action / limitation / next report

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

Two officers give different directions. Should the helm follow the most senior voice?

Compare your reasoning

Use the authority agreed in the brief and surface the conflict. Do not guess from volume or title. If the decision owner is missing, hold the affected action and resolve that gap first.

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 role list, observed instruction sequence and station 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

Make the decision owner unavailable rather than the status operator. Require a held action and explicit resolution of authority.

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

A crewed vessel or station tabletop, a shared role list and communications.

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 150

Do not count louder repetition as resolution. Check whether Helm can say whose decision it is carrying out and what remains deferred.

If another attempt is needed

Make the decision owner unavailable rather than the status operator. Require a held action and explicit resolution of authority.

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 150 · 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.