Apollo 11's 1202 Alarm, July 1969

Thirty-three thousand five hundred feet above a grey plain no human has ever touched. Twelve minutes into a controlled fall. And then a light comes on in the cabin. Neil Armstrong's voice, flat as a man reading a gas meter. It's a twelve oh two. Nobody in that spacecraft knows what that number means. Nobody in Houston has ever seen it in a run that counted. A computer smaller than a suitcase has just announced, mid-descent, that it cannot finish its work. Twenty-seven seconds of silence are coming. And at the end of them, one of two words. Land... or run. Twelve oh two meant executive overflow. No core sets. In plain words... the computer had more jobs queued than it had room to hold. Don Eyles, who wrote the lunar landing code at MIT, later explained what the machine did about it. When the executive program ran out of resources, it jumped to a chunk of code the programmers had literally named BAILOUT. Not a crash. Not a freeze. A deliberate, designed collapse... backwards into safety. And at one point in that descent, the astronauts' display just went blank. About ten seconds. Ten seconds, falling toward the Moon. Rewind a few years. Cambridge, Massachusetts. The MIT Instrumentation Laboratory, where a woman named Margaret Hamilton runs the Software Engineering Division, writing the code that will fly the lunar module... at a time when almost nobody trusts software with anything that can kill you. When the United States later hands her the Presidential Medal of Freedom, the citation lists the ideas she helped build. Asynchronous software. Priority scheduling. Human-in-the-loop decision capability. Grand phrases. Strip the jargon away and you get one stubborn assumption. Something WILL go wrong up there. Here's the design, in human language. Every task gets a priority number. Steering the engine... high. Updating a nice-to-have display... low. If the queue overflows, the machine doesn't panic and it doesn't stop. It throws away the unfinished junk, restarts, and rebuilds only the jobs marked essential. Restart protection. Picture a chef whose kitchen is suddenly flooded with orders. A bad chef freezes. This one sweeps the garnishes into the bin and keeps cooking the thing that matters. That is what kept Eagle flying. Over and over. But software can only save you if a human believes it. Weeks before launch, in a simulation, an alarm like this appeared and the guidance officer called an abort. Wrongly. Flight director Gene Kranz was not delighted. As Jack Garman remembered it, Kranz told them... I want you all to write down every single possible computer alarm that can possibly go wrong. So Garman, twenty-four years old, sat down and handwrote them. Every code. And beside each one, a verdict. Continue... or abort. He slid the page under the plexiglass on his console in the back room. Ballpoint pen. Against the Moon. So when twelve oh two lights up, Garman already knows. His note says it plainly. If it doesn't recur, Go. He tells guidance officer Steve Bales, twenty-six, that the computer can be trusted as long as the alarms don't go continuous. Kranz recalled Garman's words coming down the loop... it's a bailout alarm, the computer is busier than hell. Bales calls it to Kranz. Kranz calls it to CAPCOM Charlie Duke. And Duke says the line that lets history happen. We're Go on that alarm. Twenty-seven seconds after Armstrong asked. Four more alarms follow, including a twelve oh one. Roger. Same type. We're a go. Now it gets tight. Armstrong takes manual control, hunting past a boulder field, fuel draining. Duke's voice. Thirty seconds. Behind him, chief astronaut Deke Slayton mutters... shut up Charlie, and let 'em land. Contact light. Then Armstrong, unhurried, like a man parking a car. Houston, Tranquility Base here. The Eagle has landed. And Duke, breaking every rule of mission-control cool, tells him they've got a bunch of guys about to turn blue. Down there, grown engineers had forgotten to breathe. But nobody yet knows WHY the computer was drowning. That evening, a hardware specialist named George Silver remembers something. The rendezvous radar. The one used to find the command module. Useless for landing... but its electronic link to the computer could still be live. And if it was, it could steal as much as fifteen percent of the machine's time. Next day, confirmed. The cockpit switch had been sitting in auto-track. Eyles calculated the interface ate roughly thirteen percent of the computer's duty cycle. Five alarms. Five restarts. A switch position. That's the thing that nearly ended it. Land, or run. They landed, because somebody years earlier assumed the worst day would come. Every time your phone drops the video and keeps the audio. Every time a flight computer sheds a luxury to protect the essentials. You're living inside that same idea. Not software that never fails. Software that fails gracefully, and tells you which failure to ignore. When Margaret Hamilton got her medal, the President put it simply. Our astronauts didn't have much time, but thankfully they had Margaret Hamilton. Eagle was flown by two pilots, a pen-and-ink cheat sheet... and a few thousand lines of code that knew how to let go.