This programmer saved the Apollo 14 mission with 61 keystrokes
In the early hours of 5 February 1971, Don Eyles had a big problem. Apollo 14 astronauts Alan Shepard and Edgar Mitchell orbiting the Moon, preparing to land. But it looked like they were going to have to come home without putting so much as footprint on the surface. The only way to save the mission was for Eyles to hack his own software.
Don Eyle’s recent memoir details how the mission software for the lunar module was developed.
Shepard and Mitchell were onboard their lunar module, the Antares. The Antares flight computer was registering occasional presses of an Abort button in the cabin, even though the astronauts hadn’t touched it: a loose ball of solder was floating around in zero gravity inside the switch and shorting it out. The button was intended for extreme emergencies: once the descent to the lunar surface begun, pressing it would order the Antares computer to try to rocket the lunar module back into orbit. Eyles had written the mission software running in the Antares computer, and now his challenge was this: find a way to lock out the emergency switch behavior that he had carefully programmed into the computer.
Eventually, Eyles was able to come up a few lines of instructions that were radioed to the astronauts to punch into their computer, bypassing the code that paid attention to the switch. Apollo 14 landed on the moon later that day. His fix was elegant and creative, and it’s not hard to see why Eyles sees no discontinuity between engineering and art: in later life, he himself went on to become a photographer and sculptor.
IEEE Spectrum was able to speak to Eyles about how he saved the Apollo 14 mission at the Vintage Computer Festival East in May. He was there to give a talk and promote his recently released book, Sunburst and Luminary: An Apollo Memoir, which provides a wealth of inside detail about how the Apollo software was developed at the Charles Stark Draper Laboratory, then a part of MIT.