TRUE SCIENCE STORIES · B2 · 50 min

The Successful Failure

Three men, 330,000 kilometres from home, in a dying spacecraft — and four days of the finest problem-solving human beings have ever done.

Today: you'll relive the greatest rescue in the history of engineering — and you'll master the grammar of crisis: they had to improvise, they couldn't turn back, they managed to bring them home.
Before we start. Talk these through out loud.
Discuss:
  • Describe the best problem-solving under pressure you have ever witnessed. What made it work?
  • In a crisis, what matters more: the plan you prepared, or the people you prepared?
  • Can a failure be more valuable than a success? Give one example.

The vocabulary of this story

Ten items. Work through the four activities — say your answer out loud before you reveal it.

A · What do they mean here? Work it out from the context

1. Fifty-five hours into the flight, a routine switch-flip ended in a bang, a shudder, and warning lights everywhere: an oxygen tank had suffered an explosion.
an explosion (n) — verb to explode. Damaged wiring ignited inside oxygen tank two; the blast tore open the spacecraft's side and its supplies of air, water and power began to die together.
2. The command ship was dying, but docked to its nose hung the lunar lander — undamaged, with its own engine, oxygen and power. It became the crew's lifeboat.
a lifeboat (n) — the small boat that saves you when the ship sinks. Metaphor and fact at once here: a two-man, two-day vehicle asked to keep three men alive for four days.
3. With every breath, the astronauts exhaled carbon dioxide — and the lifeboat's filters, built for two men, began to drown in it.
carbon dioxide / CO2 (n) — the gas we breathe out, toxic as it accumulates. The famous square-peg-round-hole problem of this story is a CO2 problem.

B · Which word means…?

Three words: trajectory · mission control · to improvise. Say the right one, then reveal.

1. Which term means the ground team that monitors and directs a spaceflight?
mission control — the room in Houston, and the institution: flight controllers, engineers, and the flight director whose word was law. The story's other hero, alongside the crew.
2. Which word means to create a solution on the spot, from whatever is available?
to improvise (v) — noun improvisation. This story's version: build a CO2 filter adapter from a flight-plan cover, plastic bags, a sock and grey tape — using only what was aboard.
3. Which word means the curved path a moving object follows through space?
a trajectory (n) — to correct / calculate a trajectory. Theirs was bent around the Moon: the "free return" path that used lunar gravity as the engine they no longer trusted.

C · Choose the meaning — a / b / c

1. Every non-essential system was switched off to save power; the cabin fell towards freezing. The crew had to ration everything. To ration means…
  (a) to share out strictly because there is not enough   (b) to throw away   (c) to repair
(a) — to ration (v/n). Water fell to about a fifth of a litre per man per day; the temperature to a few degrees above zero; sleep to almost nothing.
2. Commander Jim Lovell reported the emergency in one of the calmest sentences ever spoken: "Houston, we've had a problem." The tone was pure understatement. This means…
  (a) panic   (b) describing something as smaller than it is   (c) exaggeration
(b) — understatement (n) — the professional voice of test pilots and surgeons: the worse it gets, the calmer the words. (The film changed the line to "we have a problem" — the record says "we've had".)

D · Word building & collocation

1. You know to simulate. Build the set: a flight ___ (the machine) · a full-dress ___ of re-entry (the noun) · procedures were tested in ___ before being read to the crew.
A simulator · a simulation · tested in simulation. The unsung machinery of the rescue: nothing reached the spacecraft that had not first been flown, exhausted, on the ground.
2. One phrase completes all three: to bring them ___ · the long journey ___ · splashdown meant they were finally ___ . The simplest word in the story, and its whole objective.
home — bring them home, the journey home, finally home. Four days, one word.

Now use them — out loud

Before we read:
  • Using explosion, lifeboat, improvise and trajectory, predict the shape of the rescue — what do you think was the hardest of the four days?
  • Sort the items into problems and resources. The story is the conversion of the second list against the first.

The story, in three parts

Read each part. After it, there's a quick check (answer from memory first), then one question to discuss.

Part 1 — "Houston, we've had a problem"

By April 1970, flying to the Moon had begun to look routine — so routine that the television networks declined to broadcast Apollo 13's cheerful evening show from space. Aboard were Jim Lovell, veteran commander; Fred Haise; and Jack Swigert, the backup pilot promoted to the crew three days before launch when his colleague Ken Mattingly was grounded — exposed to German measles, which he never actually caught. Fifty-five hours and fifty-five minutes into the flight, some 330,000 kilometres from Earth, mission control asked Swigert to flip a routine switch stirring the oxygen tanks. Damaged wiring inside tank two — the legacy of a years-old manufacturing and testing error nobody had connected — ignited. The tank exploded, tearing off a panel of the spacecraft's side.

The crew heard a bang and felt the ship shudder; alarms lit the panels. Lovell's report to Houston has entered the language: "Houston, we've had a problem." For minutes the data made no sense — so many readings failing at once that controllers suspected the instruments. Then Lovell looked out of the window and saw the truth venting into space: "We are venting something out into the... into space," he reported. It was their oxygen. The command module Odyssey was dying — losing the gas that fed both the crew's lungs and, through its fuel cells, all their electricity and water. The Moon landing evaporated in those minutes; nobody said so aloud, because a far larger question had replaced it.

The answer to that question was hanging on the ship's nose. The lunar module Aquarius — the spidery lander built to carry two men to the Moon's surface for two days — was intact, with its own oxygen, batteries and engine. Within hours the crew powered it up as a lifeboat, shut the dying Odyssey down to save its last battery power for re-entry, and crowded three men into a cabin designed for two. The mathematics were not encouraging: two days of supplies, four days from home — and no way back but forward, around the Moon.

Quick check — from memory, then reveal:

1. What caused the explosion, and why did the crisis compound so fast?

2. What was the lifeboat, and what was wrong with the arithmetic?

1. Damaged wiring in oxygen tank two ignited during a routine stir — a dormant manufacturing/testing fault. Oxygen fed the fuel cells, so air, electricity and water all began failing together.

2. The intact lunar module Aquarius — built for two men for two days, now holding three men four days from home, with the only route back leading forward, around the Moon.

Discuss:
  • The fault had been built in years earlier and passed every check. What does this say about where disasters actually begin — and when the real mistake was made?

Part 2 — Four days of arithmetic

What followed was not one problem but a queue of them, each fatal, each solved in hours by exhausted people who refused to panic. The trajectory came first: mission control chose the free-return path — burn the lander's engine to bend the ship around the Moon and let lunar gravity sling it home. The crew executed the burn manually, steering by the Earth's position in the window, in a vehicle never designed to push the dead weight of the ship it was rescuing. Rounding the far side of the Moon, they set a record no crew has broken: the farthest human beings have ever been from Earth. Haise and Swigert photographed the surface; Lovell, who had flown to the Moon once before and now lost it a second time forever, reminded them gently that getting home was the photograph that mattered.

Then the air itself turned hostile. Three men breathing in a two-man cabin overwhelmed the lander's round CO2 filters, and the dying command module's square spares did not fit — the literal square peg in a round hole. In Houston, engineers dumped onto a table only the objects known to be aboard and built an adapter out of them: a flight-plan cover, plastic bags, a sock, a hose, and grey tape. The procedure was read up to the crew step by step; Swigert and Haise built their copy; the CO2 levels fell. The "mailbox" is still, half a century on, the first slide in every engineering lecture on improvisation.

Behind the drama ran the quieter epic: power. The re-entry module had to be brought back from the dead with a fraction of its normal energy, and the start-up sequence — normally months in the writing — was invented in three days, largely by the grounded Mattingly and controller-legends in the simulators, tested, rejected, rewritten and tested again before a word of it was read to space. The crew copied it by hand in the freezing cabin — the temperature had fallen near zero, water rationed to a fifth of a litre a day, Haise feverish with an infection — onto whatever paper remained. It ran almost without error.

Quick check — from memory, then reveal:

1. How was the trajectory problem solved, and what record resulted?

2. Describe the CO2 fix and the power-up effort — who did each?

1. A free-return path around the Moon, using a manual burn of the lander's engine — steering by the Earth in the window. Rounding the far side, the crew became, and remains, the farthest humans from Earth.

2. Houston engineers built a filter adapter from only items aboard — flight-plan cover, bags, sock, tape — and read the build instructions up; the crew replicated it. The re-entry power-up was written in three days by Mattingly and controllers in simulators, then hand-copied by the freezing crew, and ran almost cleanly.

Discuss:
  • Houston's rule for the fix: only objects certainly aboard. What discipline does that constraint impose — and where would "solve it with what they already have" improve rescues in your own world?

Part 3 — Splashdown, and the meaning

On 17 April 1970 the crew cast off their faithful lifeboat — "Farewell, Aquarius, and we thank you," said Lovell — strapped into the revived Odyssey, and fell into the atmosphere. Re-entry blackout was expected to last about three minutes; it stretched well past four, the longest silence of the mission, before the parachutes broke out of the clouds on live television and the world, which had spent four days holding its breath from Times Square to the Vatican, exhaled. The crew, frostbitten, dehydrated and lighter by kilos, were safe aboard the recovery ship within the hour. The Moon rocks they never collected were the cheapest price ever paid for a legend.

The investigation that followed traced the explosion to its buried origins — a design change and a pre-flight test procedure that had cooked the tank's wiring insulation years before launch — and its findings rebuilt the spacecraft's innards for every later flight. NASA named the mission a successful failure, and meant it precisely: the failure was in the hardware and the processes behind it; the success was in everything built to survive such a failure — the margins, the simulators, the cross-trained teams, and a culture in which the flight director could tell his controllers, as legend has flight director Gene Kranz saying, that failure was not an option, and be believed because they had rehearsed its avoidance for years.

That is why this story ends a science series. The other stories here are about discovery — seeing what no one had seen. Apollo 13 is about the other half of engineering civilisation: what happens when the discovered, designed, tested machine breaks anyway, off the edge of every checklist. The answer, demonstrated across four April days, is that the real spacecraft was never the metal one. It was the years of drills, the habit of speaking calmly, the teams who trusted each other's arithmetic at 3 a.m., and the institutional decision — made long before launch — that people would be trained deeper than the machines could fail. Every organisation owns a version of that choice, and most discover which version they chose the way Apollo 13 did: fifty-five hours in, with a bang.

Quick check — from memory, then reveal:

1. What did the investigation find, and what does "successful failure" precisely mean?

2. According to the ending, what was "the real spacecraft"?

1. The tank's wiring had been damaged years earlier by a design change plus a pre-flight test that overheated it — a buried process fault. "Successful failure": the hardware and processes failed; the margins, training and culture built for exactly such a day succeeded.

2. Not the vehicle but the preparation: years of simulation, cross-trained teams, calm procedures and mutual trust — the decision, made long before launch, to train people deeper than the machines could fail.

Discuss:
  • "Trained deeper than the machines can fail." Has your organisation made that choice — and what would your fifty-fifth hour reveal?

Grammar — past ability & necessity

A crisis story runs on four questions: what did they have to do, what couldn't they do, what were they able to do — and what did they, against everything, manage to do? English marks each precisely.

Necessity in the past:
• had to — it was necessary (and done): "They had to shut down the command module."
• didn't have to / didn't need to — not necessary: "They didn't have to navigate alone — Houston computed everything twice."
• needn't have + participle — done, but unnecessary (B2+ refinement): "They needn't have worried about the parachutes — but nobody knew that until they opened."
Ability in the past — the crucial distinction:
• could / couldn't — general ability, or negative single events: "Lovell could fly anything." · "They couldn't turn back."
• BUT for one specific successful achievement, positive could is wrong — use managed to / was able to / succeeded in -ing:
✗ "They could build the filter that night." ✓ "They managed to build the filter that night." ✓ "They were able to restart the ship."
Managed to carries effort against odds — the exact flavour of this story. Negative is free: couldn't = wasn't able to = didn't manage to.

1. Necessity — had to or didn't have to?

Complete with had to, didn't have to or needn't have + verb.

1. To save power for re-entry, they (shut down) almost every system.

2. Thanks to Houston's double-checking, the crew (calculate) the burns themselves.

3. Swigert (worry) about his last-minute promotion — he flew the re-entry perfectly, though nobody could have told him so in advance.

1. had to shut down   2. didn't have to calculate   3. needn't have worried

2. Ability — the could/managed-to trap

Choose the correct form; where could is impossible, say why out loud.

1. Before the flight, Lovell (fly) by the stars — a general skill from years at sea and in space.

2. That night, despite the frost and the fever, Haise (copy) the whole procedure without a serious error. (one specific achievement)

3. The controllers (not / explain) the sensor chaos at first — the readings seemed impossible.

1. could fly (general ability — could is fine)

2. managed to copy / was able to copy (specific single success — positive could impossible)

3. couldn't explain (negative — could returns)

3. The mission report — complete the paragraph

Fill each gap with the right necessity or ability form, then read it aloud as a debriefing.

After the explosion, the crew (abandon) the command module within hours and (not / use) its engine, which nobody trusted. They (survive) on a fifth of a litre of water a day, in a cabin near freezing. Houston's engineers (build) a working filter from spare objects, and the crew (replicate) it in space. Mattingly's team (write) in three days a power-up sequence that normally (take) months. In the end, all three men (come) home alive — something the first night's numbers said (not / be done).

had to abandon · couldn't use · had to survive · managed to build · were able to replicate · managed to write · would have taken / took · managed to come / were able to come · couldn't be done

Count the "managed to"s — every one marks effort against odds. That is why the verb exists.

Take the toolkit into the Speak tab — Task A is the four days, told with these verbs carrying the weight.

Going deeper

A note on the record: this is among the best-documented crises in history — transcripts, telemetry and memoirs align. Two legends need flags: the line was "we've had a problem", and "failure is not an option" was coined for the film, though Kranz liked it enough to take it for his memoir's title.

What the story actually teaches. First, that the rescue was purchased years earlier. Every asset that saved the crew — the lander's margins, the simulators, the cross-trained backup crew, the culture of calm — was an "inefficiency" someone had funded before it was needed. Resilience always looks like waste until the fifty-fifth hour; the organisations that survive their explosions are the ones that paid for slack when the budget review called it fat. (The Maersk case in the business series is this lesson's corporate twin — there the slack was a fluke; here it was policy.)

Second, the discipline of the constraint. "Only what's aboard" turned an impossible problem into a solvable one by shrinking the search space; the three-day power-up succeeded because simulators rejected drafts reality would have punished. Improvisation, done professionally, is not the absence of process — it is process running at emergency speed, with rehearsal as its fuel.

Third, the fault that passed every check. The tank was damaged by procedures that were each individually approved — the disaster was assembled from compliant steps, then waited years. That pattern (Boeing's case tells its tragic version) points the real safety question away from "who broke the rule?" toward "which of our approved steps combine badly?" — a question no checklist answers, and every post-incident review should ask.

Talk it through:
  • Name the "inefficiencies" in your organisation that are actually resilience — and the ones that were already cut. What would your fifty-fifth hour expose?
  • "Only what's aboard": apply the constraint to a current problem of yours. What does the shrunken search space reveal?
  • The film improved the line and invented the slogan. Does polishing a true story serve or betray it? Where is the line?
  • Series thread: Fleming's luck was caught by prepared minds; Apollo's disaster was caught by prepared institutions. Which is harder to build, and which does your field lack?

Speak

All of it out loud, against the clock — in the mission-control register: calm, precise, understated. The worse it gets, the quieter the voice.

Useful language: they had to… within hours · they couldn't risk… · they managed to…, despite… · Houston was able to… · it needn't have happened, and it must never again · we've had a problem
Time remaining: 4:00
Task A · Tell the four days (4 minutes)

Tell it hour by hour: the routine flight nobody televised → the stir, the bang, the venting oxygen → the lifeboat decision → the burn and the far side of the Moon → square peg, round hole, and the mailbox → the freezing cabin and the hand-copied power-up → the long blackout → the parachutes → "successful failure".

Use had to, couldn't, managed to and were able to at least once each, and five key words (explosion, lifeboat, carbon dioxide, mission control, improvise, trajectory, ration, understatement, simulation, home).

Task B · The budget hearing, 1969 (4 minutes)

One year before the flight, a cost committee proposes cutting: the backup crew, half the simulator hours, and the lander's "excessive" margins. Round one: as the programme director, defend each item — without being able to predict Apollo 13. Round two: as the committee, make the honest case for the cuts. Close with the principle that should decide such hearings.

Task C · Your fifty-fifth hour (4 minutes)

Run a crisis from your own world in the Apollo method: state the problem in one calm sentence, list only what is "aboard", assign the teams, and give the first three instructions. Then debrief: what preparation would have had to exist for this to work?

Prefer a ready-made scenario? Take one of these:

  • A hospital generator fails during a storm, with backup fuel for six hours.
  • A ship loses its main engine two days from port in worsening weather.
  • A live broadcast loses its studio twenty minutes before air.
  • A mountain expedition's stove fails at high camp with three days of descent ahead.

To finish — the harder questions

  1. The world only paid attention once the mission was dying. What does that say about attention — and does an organisation need its near-disaster to be believed about risk?
  2. Mattingly, grounded by a disease he never caught, may have saved the mission from the simulator. Construct the argument that the backup role — in any field — is the most underrated job there is.
  3. NASA called it a successful failure and rebuilt the tank; other organisations in this series hid, spun or litigated their explosions. What lets an institution metabolise failure instead of denying it?
  4. Before you go — from memory: one sentence with had to, one with couldn't, one with managed to, all about the four days — and explain why "they could build the filter that night" is wrong.