Lesson 1 of 6 · Controller roles
Build a shared picture from specialist views
8 minute lesson · 3 checks along the way
Your goal for this lessonExplain why mission control needs specialist expertise and coordinated decision authority.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
No console sees the whole spacecraft
A spacecraft combines power, thermal control, navigation, communication, software and mission equipment. Mission control divides this complexity into responsibilities so specialists can recognize important changes in their area. The exact roles and console names vary by mission and organization; a crewed station and a distant robotic probe do not need identical teams.
NASA’s Johnson Mission Control Center describes a flight director coordinating controllers with different responsibilities. ESA’s mission-control account includes spacecraft operations, flight dynamics and ground-station support. Both examples show that control is a coordinated service, not a single person steering every spacecraft action.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
A local improvement can create a system problem
Imagine a fictional instrument team requesting a long observation. The thermal team predicts overheating in that pointing direction, while the communication team needs the antenna aimed elsewhere for a scheduled contact. Each team has a valid concern. A useful decision must consider their combined constraints and the mission’s priorities.
This is why recommendations should state the evidence, consequences and available alternatives. “We prefer the observation” says little about whether the full system can support it. “A shorter exposure stays inside the thermal limit and preserves the contact” gives the team a concrete option to evaluate.
Flight controllers and NASA officials confer in Mission Control on April 16, 1970, during Apollo 13’s return. The image shows people coordinating across consoles; the supporting telemetry and decision records explain what information they were evaluating.
Look closely
What can the image show about teamwork, and what needs written or recorded evidence?
See what to notice
The visible discussion and consoles document a working control room. Specific recommendations, uncertainties and decisions require logs, voice records or other contemporaneous evidence.
Check 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Coordinate without hiding disagreement
A decision process assigns responsibility for integrating advice and authorizing actions. That does not mean specialists should conceal uncertainty or dissent. If a critical assumption is disputed, the disagreement belongs in the decision record with its operational consequence. A unanimous-looking display is not a substitute for a correct shared understanding.
During a handover, the incoming team needs more than current numbers. It needs the active configuration, recent changes, unresolved issues and expected events. Practice explaining a spacecraft state in three sentences: what is known, what could change next and what requires attention. That structure turns separate observations into a usable shared picture.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.