Final preparations are underway for NASA’s Artemis II mission, the first crewed flight around the moon in more than 50 years, with an early February launch in sight. The 10-day journey will loop four astronauts around the moon and back to Earth, led by commander Reid Wiseman, pilot Victor Glover, and mission specialists Christina Koch and Jeremy Hansen of the Canadian Space Agency.
The flight is designed to push Orion and its crew systems farther from Earth than any human mission since Apollo, while proving the playbook for sustained lunar operations later this decade.
The team has spent months inside high-fidelity simulators at the Johnson Space Center in Houston, drilling through emergencies, communications breakdowns and rapid decision points that could define the mission’s toughest moments.
Trainers call the philosophy “trial by fire.” Astronauts call some of the tests “sort of evil.” Both sides agree the aim is to make the real thing feel manageable, even when it delivers surprises.
Who is flying and what the mission will do
Artemis II will ride the Space Launch System to orbit, verify life-support and navigation on Orion, execute a translunar burn, swing around the far side of the moon, then return for a high-energy reentry and splashdown. Wiseman carries overall responsibility for crew coordination and flight rule execution.
Glover, a Navy test pilot, manages critical piloting tasks and flight deck procedures during ascent, burns and reentry. Koch and Hansen backstop navigation checks, systems monitoring and communications while taking on specialist tasks that rotate depending on the phase of flight.
Although roles are defined, the crew trains to be interchangeable at key points. If a display fails or a tablet reboots at the wrong time, any astronaut on the front deck should be able to pick up the right checklist, read the callouts and keep the sequence moving. That redundancy is the point of the months of integrated runs with mission control.
Inside the “evil” sims
Chief training officer Lisa Voiles and her team script failures that range from minor to mission-threatening. A sensor might lie about temperature. A valve might stick during a burn. A caution-warning system might flood the crew with tones just as a timeline hits a critical mark. Instructors watch for how the astronauts diagnose, divide responsibilities and communicate under pressure, then dial up the complexity by stacking a second or third fault before the first is fully cleared.
The crew practices triage for flashing-light moments. One person is heads down on procedures. One keeps the big picture and watches the clock. The others cross-check and read back. The mantra is clear talk, crisp checklists, no freelancing.
The same pattern repeats in integrated runs with mission control, where timing and tone on the voice loops matter as much as the content. A clean handoff between console and cockpit saves seconds that can matter during burns or reentry setup.
Controllers train beside the crew
Flight controllers run the same gauntlet. Veteran flight director Judd Frieling will oversee ascent and early orbit. His team works from a script that hides the next failure so controllers must spot the first odd data and respond in real time.
The exercise teaches both sides to think in branches. If you cannot nail down every outcome, you at least carry a straw-man plan for the next two minutes. That mindset keeps the loop moving when telemetry jitters or a checklist proves longer than the clock allows.
After each integrated sim, controllers and crew sit for a no-blame debrief. Instructors replay a minute of audio to adjust phrasing that was ambiguous. Console leads tweak call templates. Procedure writers adjust steps that forced unnecessary page flips.
The result is incremental tightening. Over dozens of runs, wording becomes shorter, checklists clearer and roles more intuitive.
