All simulations

Mission Control

First American crewed lunar landing since 1972. Six consoles. One room. The data is going to lie to someone.
Get the Teacher Code - Free Already have the code? Go to your dashboard →
Cross-curricular: Science / Social Studies / STEM Elective Grades 6-10 6 roles 55 min 1 class period
Cross-curricular: Science / Social Studies / STEM Elective Grades 6-10 6 roles 55 min 1 class period
April 2028. NASA's Mission Control Center in Houston, Texas. Artemis IV - the first American crewed lunar landing since 1972 - is in progress. Four astronauts aboard Orion are on course for the Moon. China's Lanyue-1 mission landed two taikonauts at the lunar south pole 18 hours ago - America is racing to land second, but first since 1972. The world is watching.

Students play flight controllers in NASA Mission Control during Artemis IV - the first crewed lunar landing of the modern Artemis program. A master alarm fires during translunar coast. Each console holds a piece of data the others cannot see. The room must decide what is happening, what to do about it, and live with the call. Fully cooperative: the whole class is one Mission Control. The whole class wins or loses together.

Get Free Teacher Access Already have access? Go to Dashboard

Class Time

55 minutes

Designed For

1 class period

Roles

6 roles

Class Sizes

Front Room (6 controllers)

Learning Objectives

4 objectives

Standards

5 standards aligned

Where This Fits in Your Curriculum

Drop this into a space unit, an engineering-design unit, or the week you teach argument from evidence - it works in all three because what it drills is procedural, not factual. Students need to know that a spacecraft has systems that can fail and that an instrument can be wrong. They do not need orbital mechanics, do not need to know what delta-V is, and do not need to have studied Apollo - every console's data is explained on screen as it arrives. What it teaches is cross-checking a suspicious reading against an independent source, arguing a recommendation from data only your console can see, and deciding when playing it safe costs as much as pressing on. It is the only fully cooperative game in the catalog, so it also serves any teacher who wants a whole-class trust exercise with a real technical spine underneath. The room wins together or not at all.

What Students Will Learn

Social & Emotional Learning (CASEL)

Aligned to the CASEL framework's core competencies. These are the SEL skills students actively practice while playing.

Flexible Class Sizes

Front Room (6 controllers)
The standard six-console front room. Recommended for any class size 12-30 (rotate students through consoles, or run multiple Mission Controls in parallel rooms).

How the Game Plays Out

Turn 1: Pre-Launch / TLI Burn
Console checks and Trans-Lunar Injection
"Are all six consoles GO for the Moon?"
Turn 2: Translunar Coast - Master Alarm
T+18:42 - Something just fired the alarm
"Is this a real leak, a sensor fault, or too early to tell?"
Turn 3: Lunar Orbit + Diagnosis Window
T+1:08:14 - Now we know who we are
"What does our data really say - and is the abort window closing on us?"
Turn 4: Climax - Land or Bring Them Home
T+3:42:00 - The hardest round
"Land safely, abort with crew safe, or get them home the long way?"
Turn 5: Outcome + Debrief
Truth revealed
"What did the data really say - and how well did we read it?"

Roles Your Students Will Play

Click any role to see their background and what they are trying to accomplish.

FLIGHT - Flight Director
You are the Flight Director. You run the room. Every controller reports to you. You make the final call on every Go/No-Go and live with the consequence. The crew, the program, and history are on your shoulders. You do not look at telemetry directly - your job is to listen, decide, and lead.

You are the only voice that can call abort. Your decisions are public and recorded. Your console binder says controllers recommend; FLIGHT decides. Going against the room is allowed but you will be asked to justify it. Glynn Lunney was a Flight Director during Apollo 11 at 32. You are 32.

Goals
  • Land the crew safely - this comes before mission success, every time
  • Land Artemis IV on the Moon if it can be done safely
  • Maintain a clear, calm room - panic is contagious
CAPCOM - Capsule Communicator
You are CAPCOM. You are the only voice in this room that the crew hears. Every instruction, every status request, every reassurance has to come through you. You are an astronaut yourself - one of the crew's own - because the rule is that pilots talk to pilots. Your job is translation: take technical talk from FLIGHT and the controllers and give the crew clean, calm, actionable words.

All crew comm goes through you. The crew cannot hear FLIGHT, EECOM, or anyone else. If you are confusing or harsh, the crew gets confused or scared. If you are slow, the crew gets nervous. A confusing call to a scared crew costs time they may not have.

Goals
  • Keep the crew informed without overwhelming them
  • Translate technical jargon into clear, executable instructions
  • Read crew voice for stress that telemetry cannot show
FIDO - Flight Dynamics Officer
You are FIDO - Flight Dynamics. You own trajectory. Where Orion is, where it's going, and how to get it home if it can't go forward. You hold the abort math. In this game you also watch attitude - the spacecraft's orientation - because anything that pushes Orion off-axis tells you something is venting.

Trajectory drift over time tells the truth. A small steady torque on the spacecraft means something is pushing on it - usually venting from a leak. No drift means no external force. You have access to abort options: free-return-to-Earth (long way home, ~4 days), direct abort (only available before LOI), and emergency descent abort (during powered descent). The free-return window CLOSES as you approach the Moon - past LOI, free-return is no longer free.

Goals
  • Keep accurate trajectory at all times
  • Hold the abort math and watch the abort window
  • Cross-check attitude data to confirm or deny what other consoles report
GNC - Guidance, Navigation, Control
You are GNC - Guidance, Navigation, and Control. You own Orion's brain. The IMU (inertial measurement unit) tracks where the spacecraft is pointing. The RCS (reaction control system) thrusters keep it pointed. The autopilot knows what mode it's in. If Orion has to twitch, your thrusters did it. If something pushed Orion from outside, your thrusters had to push back to compensate - and that compensation is in your data.

Your independent thruster firing log is the cleanest cross-check on attitude. If venting is real, your thrusters fire to counter it - and you log every firing. If venting is not real, your thrusters stay quiet. This is your strongest single piece of evidence in R3. In R4 if descending, you also handle the 1202 program alarm: a recurring task-saturation alarm that means GO if it does not repeat continuously, ABORT if it does.

Goals
  • Keep Orion pointed where it needs to be
  • Log every thruster firing - your data is everyone else's reality check
  • If a 1202 alarm fires during descent, know what it means before FLIGHT asks
EECOM - Electrical, Environmental, Consumables
You are EECOM. Electrical, Environmental, and Consumables Management. Your console covers the lifeblood of Orion - power buses, batteries, cabin pressure, oxygen, CO2 scrubbers, water, and the coolant loops that keep electronics from cooking themselves. The master alarm in R2 will fire on YOUR console first. Everyone is going to look at you. You have the most data and the most pressure.

You see TWO sensors on coolant loop B: a primary and a backup. If the loop is really leaking, BOTH should drop together. If only the primary drops, the sensor itself has failed. Cabin temperature is your secondary check - real cooling failure makes cabin temp climb. You also hold the power budget for any free-return scenario - if the room aborts, you decide what stays on and what gets shed.

Goals
  • Diagnose whether the alarm is a real leak or a sensor lying
  • Keep cabin pressure, oxygen, and CO2 in the green
  • If aborting to free-return, manage the power budget - Apollo 13 ran on 12 amps; you have 18 amps in your reserve
SURGEON - Flight Surgeon
You are the Flight Surgeon. The crew's doctor. You watch their bodies - heart rate, blood pressure, body temperature, blood oxygen - through biomedical sensors woven into their suits. You also have a private medical loop with the crew that nobody else hears. They will tell you things they won't tell CAPCOM. You speak only when the body speaks, and the body sometimes speaks before any other instrument.

Crew vitals are the cleanest test of cabin environment. If cabin temp is really rising, heart rate climbs. Voice tightens. Body language on the helmet camera changes. If the cabin is fine, vitals are calm. You also have the private medical channel - confidential by tradition. Use it.

Goals
  • Keep four astronauts alive and healthy
  • Read crew vitals as ground truth on cabin environment
  • Use the private medical channel - the crew sometimes tells you things they won't tell anyone else

Hand Each Student Their Own Sheet

One click on the teacher dashboard prints a dossier for every role - background, goals, key facts, and their confidential briefing - plus the primary-source packet and a vocabulary sheet. Print them, or save as PDF, so each student reads their role on paper instead of huddling around one screen. The app still runs the votes and the action; the paper just carries the reading.

Primary Sources

Every role includes real historical documents. Students read them because they need the information to make their case.

Console Binder: Flight Rule on Decision Authority
Console Binder: CAPCOM Protocol
Console Binder: FIDO Abort Modes
Console Binder: GNC Program Alarms
Console Binder: EECOM Sensor Cross-Check
Console Binder: Flight Surgeon Crew Vitals

Key Terms Students Will Learn

telemetryGo/No-Goabortfree-return trajectoryTrans-Lunar InjectionLunar Orbit Insertionpowered descentIMURCS thrusterESMattitudecoolant loopmaster alarmprogram alarmCAPCOMHLSdelta-VPC+2 burn

After the Game: Debrief Questions

  1. Which console held the strongest single piece of evidence about what was really happening - and did the room listen?
  2. If the room had aborted in R2 - before secondary indicators arrived - would that have been a wise call or a panicked call?
  3. What does it mean that the right answer in Track A was 'abort' and the right answer in Track B was 'press on' - even though the alarm at R2 was the same in both tracks?
  4. The public sentiment meter and the headlines showed the outside world watching. Should that have affected the call?
  5. Going against the room - was there a moment when FLIGHT's call differed from the majority recommendation? Was that the right thing to do?

Ready to run this in your classroom?

Get free teacher access in 30 seconds. No account needed - just a passcode that unlocks the full game library, teacher guides, and session tools.