The Moon-landing code has jokes in the margins
Apollo 11 11’s historic lunar landing, a feat of human ambition and rigorous engineering, relied on software with an unexpectedly informal voice. The Apollo 11 Guidance Computer source Apollo Guidance Computer source code, specifically the Luminary099 release for the Lunar Module, reveals engineers’ playful commentary tucked into critical flight routines.
Imagine the high-stakes descent, guided by instructions like “PLEASE CRANK THIS SILLY THING AROUND” as astronauts positioned the landing radar. Immediately after, the computer’s check on the antenna appears with the skeptical note, “SEE IF HE'S LYING.”
Further into the descent loop, a comment refers to engineer Allan Allan Klumppp: “Allan Klumpp SAYS GIVE UP TO EIGHT PASSES.” This note accompanies a routine allowing the system multiple attempts before aborting. These human touches offer a unique glimpse into the personalities behind humanity’s greatest technological leap.
“Burn, baby, burn” was a real flight routine
Mission-critical operations in the Apollo 11 Guidance Computer source Apollo Guidance Computer source code became an unlikely comedy reel. Engineers used names like OFF TO SEE THE WIZARD for engine ignition and BURN_BABY_BURN_BABY_BURN_BABY_BURN for the routine itself, a nod to 1960s DJ Magnificent Montague. Post-touchdown, the coordinate display was tagged “NOW LOOK WHERE YOU ENDED UP.”
A comment in the lunar descent Apollo Guidance Computer source code, “TEMPORARY, I HOPE, HOPE, HOPE,” reveals a documented production change, not carelessness. This fix, addressing a specific issue, flew to the Moon, underscoring the dynamic, iterative nature of software development even in high-stakes environments. Allan Allan Klumppp, an MIT engineer, even got a shout-out with "Allan Klumpp SAYS GIVE UP TO EIGHT PASSES" for a descent loop.
The restart system, ENEMA, came with a warning to consult the “POO people.” This referred to Program 00 (P00), the computer’s idle program, not a literal scatological reference. Failure or recovery routines adopted equally colorful names:
- BAILOUT
- WHIMPER
- POODOO
- CURTAINS
These informal labels provided a darkly humorous counterpoint to the immense responsibility entrusted to the Apollo 11 11 crew and their groundbreaking machine.
A thermostat comparison hides a serious engineering feat
These playful comments, now available via open-source-source release, mask a serious engineering feat: building mission-critical software for hardware less powerful than a modern thermostat. The Apollo 11 Guidance Computer (AGC) operated at a mere 1.024 MHz, with approximately 2,048 words of RAM and 36,864 words of ROM. This ROM, known as core-rope memory, was physically woven by hand, making software changes a literal rewiring job.
During Apollo 11 11’s lunar descent, the AGC famously triggered 1201 and 1202 alarms. These weren't fatal errors, but indications that the computer was overloaded by the landing radar’s data. Thanks to its priority-based executive, the AGC intelligently discarded lower-priority tasks, safeguarding essential guidance functions.
This robust architecture, designed to prevent catastrophic failures, was a cornerstone of the AGC's success. Margaret Hamilton, who led the software engineering team at MIT Instrumentation Laboratory, was instrumental in developing this fault-tolerant system. Her work helped pioneer the nascent field of software engineering, establishing principles that remain vital today. For a deeper dive into this historic Apollo Guidance Computer source code, explore the GitHub - chrislgarry/Apollo 11-11: Original Apollo 11 11 Guidance Computer (AGC) Source Apollo Guidance Computer source code repository.
Enjoying this? Get one like it in your inbox each morning.
one email a day · unsubscribe in two clicks · no third-party tracking
From handwritten archives to a GitHub time capsule
Digitization efforts brought this historic software to light. Ron Burkey’s Virtual AGC project meticulously transcribed the archival material, converting handwritten documents into machine-readable text. Then, in 2016, Chris Garry published this transcription on GitHub, making the complete Apollo 11 Guidance Computer source Apollo Guidance Computer source code accessible to anyone with an internet connection.
open-source-source access proved invaluable. Now, enthusiasts and experts can inspect the original assembly, scrutinizing every line of Apollo Guidance Computer source code. This collaborative review process has even helped correct transcription errors by cross-referencing scans of the original documents, ensuring historical accuracy.
Ultimately, the comments humanize the brilliant engineers behind Apollo 11 11, revealing their personalities under immense pressure. Yet, the true marvel lies not in the jokes, but in the AGC’s architecture itself. This robust system, despite its primitive hardware, expertly navigated an unforgiving mission, a testament to its design and the ingenuity of its creators.
Frequently Asked Questions
Where can you read the Apollo 11 guidance computer code?
A digitized version of the Apollo 11 guidance software is publicly available in the chrislgarry/Apollo-11 GitHub repository.
What was funny about the Apollo 11 code?
Engineers left irreverent comments and memorable routine names, including “PLEASE CRANK THIS SILLY THING AROUND” and BURN_BABY_BURN.
How powerful was the Apollo Guidance Computer?
It ran at about 1.024 MHz, with roughly 2,048 words of erasable memory and 36,864 words of read-only core-rope memory.
Did the Apollo 11 computer recover from the 1201 and 1202 alarms?
Yes. Its priority-based executive shed lower-priority tasks during overload while preserving critical guidance work.