Skip to content
— CH. 1 · INTRODUCTION —

Apollo 5

~6 min read · Ch. 1 of 6
6 sections
  • Apollo 5, launched on the 22nd of January 1968, sent a spacecraft to orbit with no crew aboard and no windows visible through its hull. Where windows once sat on LM-1, the first flight-ready Apollo lunar module, engineers had bolted aluminum plates. A window on a later module had cracked during testing in December 1967, and NASA decided the risk was too high to leave the originals in place. So the craft that rose from Launch Complex 37B at Cape Kennedy that afternoon looked like nothing that had ever flown before: a squat, legless vehicle sealed behind metal plates, riding a rocket that had originally been slated for a mission that ended in tragedy.

    What was riding inside that rocket mattered enormously. The lunar module was the machine that would actually land astronauts on the Moon. No one had ever flown one. The question hanging over everything that January was whether it would work at all. And the answer, when it came, arrived in a way nobody had planned.

  • On the 7th of November 1962, NASA announced that Grumman, based in Bethpage, New York, had won the contract to build the lunar module. The agency had invited eleven companies to compete, and Grumman's design would eventually become the only spacecraft ever to carry human beings to the surface of another world.

    Building it proved far harder than anyone anticipated. Apollo Program Manager Major General Samuel C. Phillips had originally hoped that LM-1 would launch in April 1967. To make that happen, NASA asked Grumman to deliver the module to Kennedy Space Center by September 1966. That deadline came and went. The delivery date remained uncertain well into 1967, forcing engineers at Launch Complex 37 to work around an absence rather than a presence. Grumman built a plywood mockup of the lunar module and installed it at the launch site simply so facilities verification could proceed.

    When LM-1 finally arrived at Cape Kennedy on the 23rd of June 1967, carried aboard Aero Spacelines' Super Guppy, the problems did not stop. Leaks discovered in the ascent stage forced engineers to separate the two stages in August. After repairs and remating, another leak appeared and the stages were pulled apart again in September. Equipment was removed for repair, stages were remated in October, and the timeline kept slipping. By the 6th of September 1967, the mission was running approximately 39 days behind the revised schedule set that July.

  • The Saturn IB that carried LM-1 to orbit had its own complicated past. Originally designated AS-204, it had been brought to Cape Kennedy in August 1966 and assigned to the Apollo 1 mission. When the fire on the 27th of January 1967 killed the three-person Apollo 1 crew, AS-204 survived unscathed at its separate launch complex. Engineers inspected it for corrosion or other fire-related damage and found none.

    NASA made a deliberate choice in repurposing this vehicle. AS-204 was the last Saturn IB equipped with full research and development instrumentation. With crewed flight suspended after the fire, the agency wanted that instrumentation flying on the first lunar module test. The booster was moved from Launch Complex 34 to Launch Complex 37 and renamed SA-204R. Its launch vehicle designation was changed; its hardware was not.

    The space vehicle that rolled to the pad stood 55 metres tall but looked stubby compared to what most people associated with the Apollo program. There was no command and service module on top, and no launch escape system either. Instead, LM-1 sat within the spacecraft-lunar module adapter, designated SLA-7, which had four panels designed to open once the nose cap was jettisoned in orbit. The total ignition weight of the vehicle, including spacecraft and propellant, was 1,299,434 pounds.

  • At 17:48:08 Eastern Standard Time on the 22nd of January 1968, Apollo 5 lifted off from Launch Complex 37B. The Saturn IB performed without fault, placing the second stage and LM into an orbit of 163 by 222 kilometres. The nose cone was jettisoned, and after a coast of 43 minutes and 52 seconds, the LM separated from its adapter.

    After two orbits, controllers initiated the first planned burn: a 39-second firing of the descent engine. Four seconds in, the Apollo Guidance Computer shut it down. The computer had detected that the spacecraft was not accelerating as quickly as its program expected, and it treated that as an emergency.

    The underlying cause was a design and communication failure. One of the engine's valves was suspected of being leaky, so engineers had chosen not to arm it until the moment of ignition in orbit. That decision meant propellant took longer to reach the engine than the software anticipated. Additionally, the propellant tanks were only half full, which further slowed the vehicle's response. Programmers could have adjusted the software to account for these conditions but were never told about the valve decision. On a crewed mission, astronauts would have recognised the situation and could have decided whether to restart the engine themselves. LM-1 carried no crew.

  • Gene Kranz was the flight director for Apollo 5, running Mission Control in Houston. Faced with a mission that had just aborted its primary burn, Kranz and his team had a narrow window to salvage it. Cancelling the remaining engine tests would have meant declaring the entire mission a failure.

    Kranz's team devised an alternate plan quickly, conducting the descent-engine and "fire-in-the-hole" tests under manual control rather than the automated sequence. The "fire in the hole" test was one of the mission's most critical objectives: it was designed to verify that the ascent stage could ignite while still physically attached to the descent stage. This replicates what would happen on the lunar surface if a landing had to be aborted. The procedure required shutting down the descent stage, transferring control and power to the ascent stage, and firing the ascent engine while the two modules were still mated. The name came from mining, where the same phrase signals that explosives are about to detonate.

    Despite communication problems with the spacecraft, Kranz's team completed every burn. Eight hours into the mission, after all engine tests were finished, the ascent stage spun out of control due to a problem with the guidance system. By that point, it no longer mattered. The work was done.

  • Mission planners had intentionally left both stages of LM-1 in a low enough orbit that atmospheric drag would bring them down within weeks. The ascent stage re-entered the atmosphere on the 24th of January 1968 and burned up. The descent stage lasted longer, re-entering on the 12th of February and falling into the Pacific Ocean several hundred miles southwest of Guam. Simulations indicated the S-IVB stage of the launch vehicle re-entered approximately 15.5 hours into the flight.

    Apollo Spacecraft Program Manager George M. Low credited two things for the mission's outcome: the quality of the hardware Grumman had built, and the leadership Gene Kranz provided over the flight control teams. NASA's formal verdict was success. A second uncrewed LM test, which would have used LM-2, was cancelled. The agency had learned enough from LM-1.

    That cancellation had a direct consequence for the Moon landing schedule. Eliminating the second uncrewed test pushed NASA's timeline forward, bringing the goal of landing an astronaut on the Moon before the end of the 1960s closer to reality. The first time a crew actually flew a lunar module came on Apollo 9, in March 1969.

Common questions

When was Apollo 5 launched and what was its mission?

Apollo 5 was launched on the 22nd of January 1968 from Launch Complex 37B at Cape Kennedy. It was an uncrewed test flight of the Apollo Lunar Module, designated LM-1, designed to verify the module's systems before astronauts flew it.

Why did Apollo 5's descent engine burn shut down after only four seconds?

The Apollo Guidance Computer aborted the burn because the spacecraft was not accelerating as quickly as the software expected. A valve had not been armed until ignition to prevent a suspected leak, causing propellant to reach the engine more slowly than programmed. The propellant tanks were also only half full, compounding the delay.

Who was the flight director for Apollo 5?

Gene Kranz served as flight director for Apollo 5. When the planned automated burn failed, Kranz and his Mission Control team in Houston devised an alternate plan and completed all engine tests under manual control.

What was the 'fire in the hole' test conducted during Apollo 5?

The 'fire in the hole' test verified that the lunar module's ascent engine could fire while still physically attached to the descent stage. It simulated the procedure for an aborted lunar landing, requiring the descent stage to be shut down and control transferred to the ascent stage before ignition. The name came from a phrase used in mining when explosives are about to be detonated.

What company built the Apollo Lunar Module tested on Apollo 5?

Grumman, based in Bethpage, New York, built the Apollo Lunar Module. NASA awarded Grumman the contract on the 7th of November 1962 after inviting eleven companies to bid.

What happened to LM-1 after the Apollo 5 mission?

LM-1's ascent stage re-entered the atmosphere on the 24th of January 1968 and burned up. The descent stage remained in orbit longer, re-entering on the 12th of February and falling into the Pacific Ocean several hundred miles southwest of Guam.

Did Apollo 5's success affect NASA's Moon landing schedule?

Yes. Apollo 5 was successful enough that a planned second uncrewed lunar module test using LM-2 was cancelled. This advanced NASA's timeline toward landing astronauts on the Moon before the end of the 1960s. The first crewed lunar module flight took place on Apollo 9 in March 1969.

All sources

8 references cited across the entry

  1. 1webSATCATJonathan McDowell — Jonathan's Space Pages
  2. 3webApollo 11 Mission OverviewNASA — December 21, 2017
  3. 4webSA-206: The Odyssey of a Saturn IBAndrew LaPage — May 25, 2018
  4. 6web50 Years Ago: The Apollo Lunar ModuleNASA — January 24, 2018
  5. 7conferenceTales From The Lunar Module Guidance ComputerDon Eyles — American Astronautical Society — February 6, 2004
  6. 8bookEscaping the Bonds of Earth: The Fifties and the SixtiesBen Evans — Springer — 2010