| **Evidence packet for Module 1, Lecture 2 | Team formation, roles, trust, communication, verification, and redundancy** |
Apollo 13 is useful because it makes normally invisible coordination structures easy to see. It is not a simple story of heroic individuals improvising under pressure, and Mission Control is not a direct model for a newly formed student team. The sections below distinguish:
Apollo 13 launched on April 11, 1970, with Commander James Lovell, Command Module Pilot Jack Swigert, and Lunar Module Pilot Fred Haise. At approximately 55 hours 55 minutes into the mission on April 13, an oxygen-tank failure damaged the Service Module. The Command Module lost its normal supply of oxygen, electrical power, and water while the spacecraft was roughly 200,000 miles from Earth. The lunar landing was abandoned, the crew used the Lunar Module Aquarius as a lifeboat, and the Command Module Odyssey was largely powered down until it was needed for reentry. The crew splashed down safely on April 17. These facts are documented in NASA’s Apollo 13 Mission Report, accident chronology, and mission overview.
This successful return should not obscure the failure that created the emergency. The Apollo 13 Review Board traced the accident to a chain involving design changes, hardware handling, testing, and an oxygen-tank fault. NASA’s summary of the Review Board report is a reminder that a strong emergency response does not prove that the larger system’s earlier decisions were sound.
Apollo Mission Control divided work among specialized console positions. NASA’s Apollo 13 press kit described the Flight Director as responsible for operational decisions and actions in the control room; the capsule communicator, or Capcom, normally carried Mission Control’s voice to the crew. Controllers responsible for spacecraft systems, trajectory, guidance, crew health, activities, and communications advised the Flight Director through defined communication loops.
Apollo 13 had four complete flight-control teams, led by Eugene Kranz, Glynn Lunney, Gerald Griffin, and Milton Windler. Lunney later recalled that, after the accident, Kranz’s team was moved off the live console rotation to concentrate on restarting the Command Module and preparing for reentry while the other teams continued real-time operations. This is supported by Lunney’s NASA oral-history transcript, a first-person retrospective source, and by NASA’s account of the return and reentry preparations.
Teaching inference: Defined roles, a clear decision integrator, and separation of live operations from longer-horizon planning likely reduced duplicated or conflicting work. The evidence does not establish that every decision was centralized, that disagreement disappeared, or that the teams followed fixed 12-hour shifts. “Four flight-control teams” is supported; “four flight directors rotating through 12-hour shifts” is not supported by the sources reviewed here.
The record shows information moving through several channels: telemetry supplied machine data; the crew reported a bang, warning indications, and visible venting; specialist controllers interpreted the changing system state; the Flight Director integrated recommendations; and Capcom relayed instructions. The actual first report was Swigert’s “Okay, Houston, we’ve had a problem here,” followed by Lovell’s repetition after Capcom asked him to say it again—not the film’s “Houston, we have a problem.” The timed exchange appears in NASA’s detailed accident chronology.
The Capcom structure gave the crew a coherent voice from Mission Control while preserving specialist discussion behind that voice. It also created a responsibility: information could not merely circulate; someone had to decide what was ready to transmit and state it clearly enough to be acted upon.
Teaching inference: “Open communication” does not mean everyone speaks to everyone at once. A student-team analogue might be a named meeting facilitator, a single system of record, or an identified person who communicates a final decision—not a permanent command hierarchy.
The Lunar Module’s carbon-dioxide-removal system used round lithium-hydroxide canisters, while usable Command Module canisters were square. A ground team led by Robert “Ed” Smylie, James Correale, and James LeBlanc developed an adapter using replicas of materials available aboard the spacecraft. NASA records that the team tested the setup in an altitude chamber before Capcom read the procedure to the crew. Swigert and Lovell then assembled it, and carbon-dioxide levels fell. See NASA’s reconstruction of the response and the “mail box” artifact description.
Ground personnel also wrote and tested new procedures in simulators before transmitting them, including work to reactivate the cold Command Module. Ken Mattingly, removed from the flight crew shortly before launch, spent hours in the simulator helping finalize the reentry sequence. An alternate navigation check used the Sun when debris made star sightings unreliable; the crew estimated approximately one-half degree of misalignment in an undetermined direction, below the mission rule’s one-degree tolerance. NASA summarizes the simulator and reentry work in its mission details and reentry account; the Sun check and its limitation are documented in the Apollo 13 Mission Report Supplement, section 4.4.1.
Teaching inference: The lesson is not “experts can improvise anything.” It is that novel work was constrained by an inventory, assigned to people with relevant expertise, tested in a realistic environment when possible, translated into an executable procedure, and checked after implementation.
Several forms of redundancy mattered:
Redundancy was incomplete. The emergency exposed incompatible canister interfaces, limited consumables, common dependencies, and the consequences of the oxygen-tank failure. Apollo 13 therefore supports a more precise question than “Did the team have a backup?”: Which critical function has an independent path, who knows how to use it, and has that path been tested?
Mission Control did not begin building trust on April 13. The crews and controllers had trained, simulated failures, worked earlier missions, developed specialist competence, and practiced formal handoffs. Their response therefore illustrates substantial competence-based and calculus-based trust: people relied on demonstrated expertise, known roles, procedures, communication channels, and checks. Swift trust helped newly assembled problem-solving groups act quickly, but it rested on a mature institutional system.
Teaching inference: Apollo 13 does not show that interpersonal chemistry or confidence alone is sufficient. Nor does the safe return prove that every judgment made during the mission was correct. Trust made distributed work possible; verification and explicit authority bounded that trust.
| Popular shorthand | What the record supports |
|---|---|
| “Houston, we have a problem.” | Swigert and then Lovell said variants of “we’ve had a problem”; the film changed the tense. |
| Gene Kranz said “Failure is not an option” during the crisis. | NASA notes that screenwriters Al Reinert and Bill Broyles coined the line from sentiments described in interviews. It is not in the mission transcript. See NASA’s Spaceport Magazine, May 2015, pp. 19–20. |
| One heroic leader or one “tiger team” solved the emergency. | Four flight-control teams, the flight crew, back-room specialists, simulators, contractors, and many support groups contributed. Kranz’s team did important offline reentry work while other teams staffed live operations. |
| The carbon-dioxide adapter was a flash of untested improvisation. | A specialist team built it from replicated onboard materials, tested it in an altitude chamber, taught it to Capcom, and then transmitted the procedure. |
| Mission Control never guessed. | Teams worked with incomplete information and revised hypotheses. The stronger supported claim is that critical novel procedures were tested and verified where time and facilities allowed. |
Mission Control was a mature, hierarchical, highly rehearsed operational system with specialist roles, round-the-clock staffing, simulators, hardware replicas, contractor support, established communication loops, and authority tied to human safety. A new three-person graduate team has little of that infrastructure. Directly copying its hierarchy could silence expertise rather than empower it.
Reasonable student-team transfers include:
Do not infer that student teams should normalize crisis work, long shifts, command-and-control leadership, or unquestioned deference. The goal is dependable coordination under ordinary conditions so fewer situations become emergencies.
Roles and authority: Which Apollo 13 decisions required a single integrator, and which benefited from distributed specialist authority? For your team, name one decision that can be delegated to a domain owner and one that requires consultation or escalation.
Trust: Which evidence in the case supports competence-based, calculus-based, or swift trust? What would a newly formed student team have to substitute for NASA’s years of shared training?
Communication: What did the Capcom structure solve, and what bottleneck could it create? What is the least hierarchical student-team equivalent that still produces one clear, documented decision?
Verification: The carbon-dioxide adapter was built and tested on the ground before use. Under a short deadline, what is your team’s minimum credible verification standard for a calculation, reference, AI-assisted draft, or experimental claim?
Redundancy: Distinguish duplicate people, backup tools, spare capacity, cross-training, and an independent technical path. Which one does your current team actually need, and how will you test it?
Charter stress test — Friday at 4:52: Your submission is due at 5:00. The member responsible for validation finds a possible unit mismatch that could invalidate the conclusion. The coordinator proposes a two-to-one vote to submit; the domain specialist asks to pause. Write one Charter clause that identifies the pause trigger, who verifies the concern, what evidence is recorded, who may authorize proceeding, and when the instructor or advisor is contacted.