LEX ASTRA ACADEMY FO 150 / Shipboard roles and bridge coordination Lex Astra · School of Fleet Studies Teaching edition 2956.3 / Hybrid ———————————————————————————————————————————————— LEARNER WORKSHEET For bridge teams coordinating helm, navigation, status and mission roles. This is a private working copy. Downloading submits nothing and records no completion. Use exercise identifiers, not private player information. ———————————————————————————————————————————————— SESSION DETAILS Learner identifier: ____________________________________________________________ Instructor / assessor: ____________________________________________________________ Session date / agreed role or variant: ____________________________________________________________ Vessel, configuration and equipment: ____________________________________________________________ LIVE build / capability test date / tested by (if practical): ____________________________________________________________ Stop signal / recovery contact / communication arrangement: ____________________________________________________________ ———————————————————————————————————————————————— PURPOSE Give a bridge clear responsibilities and resolve competing requests before the helm acts. COURSE CONTEXT Fleet Studies separates the bridge lead’s movement decision from the information supplied by each station. The case makes that separation observable. ———————————————————————————————————————————————— ENTRY Complete: FD 100, FD 110, FD 120, FD 130, FD 140, FD 199 Equipment: A crewed vessel or station tabletop, a shared role list and communications. ———————————————————————————————————————————————— CASE: One helm, two requests 1. Helm is following the accepted approach. Navigation reports a limit requiring a hold. 2. Mission staff request an immediate change to a new destination. 3. The bridge lead owns the movement decision; the status operator then leaves the station. ———————————————————————————————————————————————— TECHNICAL KNOWLEDGE AND GAME SKILLS Bridge systems and multicrew station work Practical instruction revision 1 / 9 October 2026 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. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ Configuration changes are announced and their effects confirmed. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ Relief preserves control and explicitly transfers the pending task. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ Apply the technical checks in the agreed role. Discussion and simulation do not certify live handling; Crew Support evidence does not confer Pilot qualification. GAME REFERENCES 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 https://starcitizen.tools/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 https://starcitizen.tools/Guide: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 https://starcitizen.tools/Master_Modes SCM and NAV distinction. Check the actual mode, transition and available systems on the session build. Official LIVE release check: https://robertsspaceindustries.com/patch-notes ———————————————————————————————————————————————— 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. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— METHOD 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. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— METHOD 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. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— 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. 1. Hold the affected movement and ask each reporting role for the fact behind its request. 2. The bridge lead selects one instruction and states which request is deferred. Helm reads it back; Navigation confirms the route implications. 3. Assign the vacant status task or reduce the operation until it is covered. Give the incoming operator the last reading and pending report. ———————————————————————————————————————————————— YOUR EXERCISE Run the conflicting requests once, then repeat with roles swapped. End with one acknowledged movement instruction and an accepted station relief. WHAT CHANGES The monitoring station becomes vacant during the disagreement. My decision and reason: ____________________________________________________________ ———————————————————————————————————————————————— YOUR WORKING RECORD Station / operator / decision owner ____________________________________________________________ ____________________________________________________________ Competing requests / selected instruction / deferred task ____________________________________________________________ ____________________________________________________________ Relief: state / pending action / limitation / next report ____________________________________________________________ ____________________________________________________________ ———————————————————————————————————————————————— CHECK YOUR REASONING Two officers give different directions. Should the helm follow the most senior voice? My answer before consulting the explanation: ____________________________________________________________ ____________________________________________________________ ———————————————————————————————————————————————— EVIDENCE TO KEEP A role list, observed instruction sequence and station handover. Criterion 1: Every station and movement decision has a named owner. Individual evidence / finding / assessor's reason: ____________________________________________________________ Criterion 2: The crew acknowledge one movement instruction and know which request was deferred. Individual evidence / finding / assessor's reason: ____________________________________________________________ Criterion 3: The incoming operator can explain the station state, open task and escalation contact. Individual evidence / finding / assessor's reason: ____________________________________________________________ ———————————————————————————————————————————————— FINDINGS AND NEXT ATTEMPT Demonstrated: observed work meets the criterion. Further practice required: an observed gap needs a specific practice task. Interrupted: conditions prevented valid assessment; not a failure. Not assessed: enough evidence has not yet been collected. All three criteria need individual evidence. A team result or quiz cannot replace an unobserved practical. Practice variant for a fresh attempt: Make the decision owner unavailable rather than the status operator. Require a held action and explicit resolution of authority. My next practice task: ____________________________________________________________ Review contact: ____________________________________________________________ ———————————————————————————————————————————————— COMPARE AFTER ANSWERING 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. ———————————————————————————————————————————————— SOURCE AND EDITION Case FO–7: the vessel that misses assembly /academy/archives/convoy-case 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. 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. Course text revised 8 October 2026; fictional teaching edition 2956.3. ———————————————————————————————————————————————— PROFESSIONAL REFERENCES 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. FAA · crew resource management (2004 reference) https://www.faa.gov/documentLibrary/media/Advisory_Circular/AC_120-51E.pdf IMO · competence and watchkeeping structure https://www.imo.org/en/OurWork/HumanElement/Pages/STCW-Convention.aspx RSI · verify release notes before live delivery https://robertsspaceindustries.com/patch-notes ———————————————————————————————————————————————— INSTRUCTOR CHECK Try the exercise with the ship and equipment you will use. Brief station assignments, callsigns, channel and recovery point. Explain the command “Stop exercise” before starting. If a bug prevents completion, repeat the affected task when it works. Ask before recording the session; use player handles in your notes. Review rules: /academy/archives/academy-ordinance Teaching basis: /academy/framework#research