At 102:38:26 mission elapsed time, the Apollo 11 lunar module was still over seven minutes away from landing when Neil Armstrong reported a program alarm. The code was 1202. Eagle was approximately 33,500 feet, or 10 kilometers, above the Moon, and neither Armstrong nor Buzz Aldrin was certain if the alarm necessitated an abort.<\/p>\n
The Apollo 11 Lunar Surface Journal indicates that Houston authorized the crew to proceed 27 seconds after Armstrong’s initial alarm announcement. The quick decision was made by 26-year-old guidance officer Steve Bales, collaborating with computer expert Jack Garman and the other members of the flight-control team.<\/p>\n
There were four additional overload alarms that followed. However, the computer did not lose its navigational state, cease control of Eagle, or trigger an abort. Its recovery software consistently eliminated unfinished tasks, restarted vital programs, and carried on with the descent.<\/p>\n
When the alarms actually occurred<\/p>\n
A technical memorandum crafted by the MIT Instrumentation Laboratory on August 4, 1969, outlines the clearest sequence. According to the contemporaneous alarm analysis, the first 1202 alarm occurred 316 seconds after powered descent began. Another one followed 40 seconds later, while the final three alarms were registered during the last three and a half minutes before touchdown.<\/p>\n
The entire sequence included four 1202 alarms and one 1201 alarm. This is the reason later narratives sometimes claim the crisis began three minutes prior to landing: the last cluster did, but the initial alarm was triggered more than seven minutes before touchdown.<\/p>\n
The meanings of 1201 and 1202<\/p>\n
The two codes signified slightly different deficiencies within the Executive, the job-control system of the Apollo Guidance Computer. A 1201 alarm indicated that no vector-accumulator memory areas, known as VAC areas, were available. A 1202 indicated that the computer had depleted its smaller core sets.<\/p>\n
In both instances, the response was a managed software restart. A NASA-hosted explanation by Apollo programmer Peter Adler details how the computer reinitialized itself and resumed selected programs close to the points where they had been interrupted. It restarted critical functions like engine steering and the cockpit display while discarding non-essential tasks.<\/p>\n
This was more precise than merely \u201cdropping low-priority tasks.\u201d The restart cleared the Executive and Waitlist queues and utilized phase tables prepared by the programmers to restore jobs that needed to continue. Navigation, guidance, and digital-autopilot functions persisted; crew-requested displays could be requested later.<\/p>\n
Reasons for Eagle\u2019s computer overload<\/p>\n
The rendezvous radar switch was set to AUTO TRACK, as specified by the crew checklist. Due to an electrical phase mismatch in the radar interface, the system generated a rapid stream of counter-increment requests. These requests consumed approximately 15 percent of the computer\u2019s available processing time.<\/p>\n
The landing programs were already utilizing most of the machine\u2019s capacity. Consequently, some recurring guidance tasks had not been completed when the Executive was prompted to schedule their next cycle. The resulting backlog consumed the available core sets and VAC areas, prompting the computer to initiate its recovery routine.<\/p>\n
Aldrin observed that one of the 1202 alarms occurred while Verb 16 Noun 68 was executing. That display provided data including velocity and range to the landing site. The request itself was not the main issue, but its extra workload could potentially overwhelm an already burdened computer, leading Houston to monitor some of that information instead.<\/p>\n
Roles of Hamilton and Laning<\/p>\n
Margaret Hamilton, aged 32, led the Software Engineering Division at MIT\u2019s Instrumentation Laboratory. She oversaw the team responsible for the onboard flight software utilized by the Apollo command and lunar modules. Her documented contributions involved asynchronous software, error detection and recovery, and priority displays that could interrupt the crew\u2019s standard readouts during emergencies.<\/p>\n
However, the Executive operating system itself merits more specific credit. MIT\u2019s history of the Apollo computer attributes the design of the Executive and its priority-based program management method to J. Halcombe \u201cHal\u201d Laning. That operating system was vital during Apollo 11 as it safeguarded the tasks required to maintain Eagle’s flight.<\/p>\n
Hamilton did encounter opposition at MIT and NASA, but the recorded incidents pertained to different concerns. In a 2019 Guardian interview, she recalled that managers initially dismissed a safeguard aimed at preventing an astronaut from selecting a prelaunch program during flight. Additionally, she mentioned that one supervisor feared that male employees might resist her authority when she assumed their management.<\/p>\n
These anecdotes illustrate the resistance Hamilton occasionally encountered but do not prove that she personally enforced Laning\u2019s priority scheduler against MIT objections. Apollo\u2019s recovery system was a joint engineering accomplishment, with Hamilton\u2019s leadership and Laning\u2019s operating-system design both crucial for an accurate account.<\/p>\n
The decision-making at Mission Control<\/p>\n
The software was capable of recovering from the overload, but individuals still needed to determine whether its operation was safe. Bales conferred with Garman and informed the flight director that Eagle could proceed as long as the alarms were sporadic and the computer\u2019s critical outputs remained stable.<\/p>\n
Bales was later chosen to accept a NASA Group Achievement Award on behalf of the mission-operations team.<\/p>\n","protected":false},"excerpt":{"rendered":"
At 102:38:26 mission elapsed time, the Apollo 11 lunar module was still over seven minutes away from landing when Neil Armstrong reported a program alarm. The code was 1202. Eagle was approximately 33,500 feet, or 10 kilometers, above the Moon, and neither Armstrong nor Buzz Aldrin was certain if the alarm necessitated an abort. The […]<\/p>\n","protected":false},"author":2,"featured_media":374811,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"Default","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[179],"class_list":["post-374810","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-source-scienceblog-com"],"_links":{"self":[{"href":"https:\/\/wolfscientific.com\/index.php?rest_route=\/wp\/v2\/posts\/374810","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wolfscientific.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wolfscientific.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wolfscientific.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wolfscientific.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=374810"}],"version-history":[{"count":0,"href":"https:\/\/wolfscientific.com\/index.php?rest_route=\/wp\/v2\/posts\/374810\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wolfscientific.com\/index.php?rest_route=\/wp\/v2\/media\/374811"}],"wp:attachment":[{"href":"https:\/\/wolfscientific.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=374810"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wolfscientific.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=374810"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wolfscientific.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=374810"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}