The moon landing that failed, and became the finest thing NASA ever did.
Today the definitions come first. Below is a word bank, and under it ten definitions in a different order. Read each definition aloud and say which word from the bank it belongs to — before you look. Then reveal to check. All ten appear in the story you are about to read.
Read each part. After it there's a quick comprehension check (try it from memory first), then one thing to discuss.
By the spring of 1970 the Moon had become, astonishingly, ordinary. Nine months earlier Apollo 11 had drawn what was probably the largest television audience in human history; Apollo 12 had gone back and landed again. So when Apollo 13 lifted off from Florida on 11 April 1970, public interest had fallen so sharply that the American networks did not carry the crew's television broadcast from space live. Somewhere beyond the atmosphere, three men gave a cheerful guided tour of their spacecraft to an audience that, unless you counted the families sitting in a room at Mission Control, scarcely existed. The crew was commanded by James Lovell, an experienced astronaut who had already flown round the Moon without landing on it. Fred Haise was the lunar module pilot. The third seat had changed hands only days before launch: Ken Mattingly had been exposed to German measles and had no immunity, and the doctors would not clear him unless he could show he would not fall ill in flight. He could not, so Jack Swigert was moved up from the backup crew, trained in parallel in case of exactly this — the kind of contingency NASA planned for meticulously and hated having to use.
The spacecraft came in two joined halves, and their names would soon become famous. The command module Odyssey was the cone the crew launched in, lived in and would come home in; behind it sat the service module, carrying the engine, the oxygen tanks and the fuel cells that made the ship's electricity and, as a by-product, its drinking water. Docked to the front was the lunar module Aquarius, a thin-walled, spidery craft built for one job: to carry two men down to the surface and back up. The launch was not perfect: one engine on the second stage shut down early and the others burned longer to compensate, which was unsettling but not dangerous. After that the flight settled into the methodical rhythm every Apollo crew knew — checklists read aloud, numbers called down to Houston, small corrections to keep the ship on its trajectory towards a Moon still three days away. Provided that nothing broke, the landing was on.
About fifty-six hours into the flight, Houston asked the crew to do a routine housekeeping job: a "cryo stir". The oxygen and hydrogen in the service module tanks were held as super-cold liquid and tended to settle into layers, so small fans inside each tank were switched on now and then to mix the contents and give accurate readings. Swigert flipped the switches. Number two oxygen tank exploded. The cause was traced back, painstakingly, through years of paperwork. That particular tank had been dropped during earlier handling on the ground. More seriously, its internal thermostatic switches had never been upgraded to match a higher-voltage ground power supply, so during a pre-flight test the switches had failed to protect the wiring and the insulation had been burned away. The result was bare wire sitting inside a tank of liquid oxygen — an accident waiting for a spark. When the fans turned, it found one.
1. Why was almost nobody watching Apollo 13 when the accident happened?
2. What was the underlying cause of the explosion, and where did it begin?
1. After Apollo 11 and 12 the Moon already felt routine; interest had dropped so far that the American networks did not carry the crew's live broadcast.
2. Damaged wiring inside number two oxygen tank: it had been dropped in earlier handling, and its thermostatic switches did not match an upgraded ground power supply, so insulation burned off during a pre-flight test, leaving bare wire in liquid oxygen.
The crew felt a bang and saw the ship shudder. Swigert's report to Houston is usually rendered as "Okay, Houston, we've had a problem here", with Lovell repeating it a moment later; the famous film line reverses the tense, and the exact wording is best treated as reported rather than quoted with confidence. Whatever was said, the numbers on the ground turned bad within minutes. The explosion had blown a panel clean off the side of the service module, destroyed one oxygen tank and damaged the other, which was now venting its contents into space. That mattered far more than the air itself: the fuel cells needed oxygen to make electricity and water, so as the oxygen drained away the command module was losing its power, its heat and its drinking supply all at once. Lovell, looking out of the window, could see the gas escaping in a great pale plume. The landing was abandoned within the hour, and nobody argued. The mission was aborted and became, from that moment, a rescue.
The answer was to evacuate into Aquarius and use the lunar module as a lifeboat. It had its own oxygen, its own batteries, its own engine, and none of them depended on the ruined service module. But Aquarius had been built to support two men for two days, and it now had to keep three alive for four. Everything aboard was rationed: water above all, and power down to the last amp. As long as the crew kept the command module cold and dark, the charge in its re-entry batteries would still be there at the end — but that created a problem nobody had solved, because no one knew how to bring a frozen spacecraft back to life on a nearly depleted supply. That puzzle fell to a controller called John Aaron, who worked out a start-up sequence that had never been written down, switching things on in the exact order that would not overload what little current remained. Meanwhile the flight dynamics teams put the ship on a free-return trajectory that would swing it round the far side of the Moon, and fired the lunar module's descent engine to speed the journey home.
In Mission Control, the flight director Gene Kranz and his teams worked the problems one at a time. The deadliest was invisible. Three men in a two-man cabin were breathing out more carbon dioxide than the lunar module's scrubbers could remove, and the level was climbing towards the point at which judgement fails and, eventually, so does life. There were plenty of spare canisters — in the command module. But Odyssey's were square and Aquarius's were round, and unless the two could somehow be joined, the crew would slowly be poisoned by their own breath. So engineers on the ground were shut in a room with an exact copy of everything the astronauts had aboard and told to improvise. What they produced was a jury-rigged adapter of plastic bags, cardboard from a flight manual, tape and a sock, and its design was read up to the crew step by step over the radio. It worked; the carbon dioxide fell. Everything else stayed grim. The powered-down ship grew freezing, water condensed on the walls, the men were dehydrated and barely slept, and Haise developed a urinary infection and a fever. That ingenuity had bought them time; nothing had yet brought them home.
1. Why did the loss of oxygen threaten far more than the crew's air supply?
2. What was the carbon dioxide problem, and how was it solved?
1. The fuel cells needed oxygen to produce the command module's electricity and its water, so losing the oxygen meant losing power, heat and drinking water as well.
2. Three men in a two-man lunar module produced more carbon dioxide than its round canisters could handle, and the command module's spares were square. Engineers improvised a jury-rigged adapter from plastic bags, card, tape and a sock, and read it up to the crew step by step.
The last day was the worst. The command module had to be woken from the cold, and John Aaron's start-up sequence was read up and followed switch by switch, in an order that could not be varied; get it wrong and the power would collapse, and there would be no second attempt. The service module was released first, and as it drifted away the crew saw for the first time the size of the wound — an entire panel torn off, the machinery inside ruined. Then Aquarius, the lifeboat that had kept them alive for four days, was let go too: a lunar module cannot survive re-entry and would otherwise have followed them down. Odyssey hit the atmosphere alone, on battery power, its heat shield of unknown condition. Radio contact always breaks during re-entry, as ionised gas around the capsule blocks the signal, and the blackout was expected to last about four minutes. It ran longer. In Mission Control nobody spoke. Then the tracking aircraft saw the parachutes, and on 17 April 1970 Odyssey splashed down in the Pacific with all three men alive. Kranz, who had held himself together for four days, did not manage it for much longer.
What followed was not celebration but investigation. A review board chaired by Edgar Cortright took the accident apart and found, as such boards usually do, that the fault had been made long before launch by a chain of small, forgivable decisions: the dropped tank, the switches that were never upgraded to match the new ground supply, the test in which the insulation burned away unnoticed. The oxygen tanks were redesigned, the wiring protected, and an extra tank added so that a single failure could no longer take everything at once. The programme flew again the following year and went on to land four more crews. But the deeper legacy was not hardware. Apollo 13 became the standard case study in how to handle a crisis: define the real problem before reaching for a solution, work the list methodically, test the fix on the ground before anyone trusts their life to it, and never let the room be run by whoever shouts loudest. Business schools, hospitals and emergency services still teach it, under headings like improvisation, teamwork and disciplined problem-solving.
Then in 1995 the film arrived, and it fixed the story in public memory more firmly than any report could. It is a careful film in many ways, and made heroes of the flight controllers as well as the crew — but it also invented. The line most people can quote, "Failure is not an option", was written for the screen version of Gene Kranz; he never said it in 1970, though he liked it well enough to use it as the title of his memoir. The film's clean version has replaced the messier real one in most minds, which is worth noticing, because the honest lesson is less cinematic and more useful. Apollo 13 did not survive because a few brilliant individuals improvised under pressure. It survived because a very large, well-drilled organisation had spent years rehearsing for trouble it hoped would never come, and had built the simulators, the procedures and the habits of mind that made improvisation possible at all. That is the long echo: not that heroes save you, but that preparation does.
1. What did the Cortright review board conclude, and what was changed afterwards?
2. Why is "Failure is not an option" a slightly misleading thing to quote?
1. That the accident came from a chain of earlier decisions — the dropped tank, the switches never matched to the upgraded ground supply, the test that burned the insulation away. Tanks and wiring were redesigned and an extra tank added.
2. It was written for the 1995 film, not said by Kranz at the time — though he later used it as his memoir's title. It also flatters lone heroism over the real explanation: years of rehearsal by a huge organisation.
Apollo 13 is a story told almost entirely in conditions. The crew could not fly unless the doctors cleared them. The landing was on provided that nothing broke. Spares were carried in case the first canisters failed. The lifeboat would hold as long as power was rationed. The lunar module had to be released; otherwise it would have burned up with them.
Rewrite each sentence with the word in brackets, keeping the meaning.
1. If the doctors did not clear him, Mattingly could not fly. (unless) → Mattingly could not fly him.
2. The landing would go ahead only if nothing broke. (provided that) → The landing would go ahead broke.
3. They had to release the lunar module. If they didn't, it would burn up. (otherwise) → They had to release the lunar module; up.
1. unless the doctors cleared (unless = if not; the verb stays positive)
2. provided that nothing ("as long as" would also work)
3. otherwise it would burn
Each sentence has one error of form or meaning. Write the corrected part only.
1. Unless the crew did not power down the ship, the batteries would die. →
2. They took extra canisters in case the scrubbers will fail. →
3. As long as the trajectory will stay correct, they would pass behind the Moon. →
1. Unless the crew powered down the ship (never "unless… not" — the negative is already inside "unless")
2. in case the scrubbers failed (after "in case", no "will"; here a past form to match the narrative)
3. As long as the trajectory stayed correct (no "will" after these linkers)
Fill each gap with unless, provided that, in case, as long as or otherwise — each once. Read the finished passage aloud.
Houston knew the lifeboat would hold the crew rationed water and power. Every switch was thrown in a fixed order, because the depleted batteries would collapse. The spare canisters had been carried something went wrong with the first ones — and something did. the ground could improvise an adapter, the carbon dioxide would go on rising. It worked, and the heat shield was undamaged, three men were going home.
as long as · otherwise · in case · Unless · provided that
Notice the different jobs: a condition that must continue, a warning of the consequence, a precaution taken in advance, a negative condition, and a requirement that had to be met.
Hold on to these conditionals — you'll need them in the Speak tab, where almost everything you say about this mission will be a sentence about what had to be true, and what would have happened otherwise.
You've read the story and you have the words — so now the real thing is within reach. There's a full podcast episode that tells this story in far greater depth, in natural, real-speed English. It's optional: the lesson stands on its own without it.
From the Noiser podcast network. Hosted by historians, roughly 50 minutes. Search "Short History Of Apollo 13" on Spotify to open the episode.
Open the show on Spotify →This is the heart of the lesson — do all of it out loud. The timer is there to keep you going: fill the time with detail rather than escape it.
Tell the story of Apollo 13 in your own words, as if to someone who has never heard of it. Move through the arc: a Moon flight nobody was watching, and a last-minute change of crew → the cryo stir and the explosion → the landing aborted, the move into the lunar module → the powerdown, the water, the carbon dioxide and the sock → the restart, the blackout, the splashdown → what the accident changed.
Use the conditionals of contingency throughout (unless, provided that, in case, as long as, otherwise), and work in at least five key words (trajectory, abort, contingency, improvise, canister, depleted, methodical, ration, jury-rigged, ingenuity).
Apollo 13 is usually told as a story of brilliant people improvising under pressure. It could equally be told as a story of a huge organisation that had rehearsed for years — and that created the fault itself on the ground. Which telling is closer to the truth, and which is more useful? Build an argument, using examples from work, medicine, aviation or your own country.
Describe a time a plan of yours failed and you had to improvise — or a time you prepared for something that never happened. Lean on the grammar: what would have gone wrong unless you acted, what you did in case, what held as long as you were careful, what would have happened otherwise.
Stuck for an idea? Pick one of these and run with it: