- Jack Garman
John R. "Jack" Garman is a computer engineer, former senior
NASA executive and a noted key figure of theApollo 11 lunar landing. As a young specialist on duty during the final descent stage on 20 July 1969 he dealt with a series of computer alarms which could have caused the mission to be aborted.Early life
Garman was born in
Oak Park, Illinois and attended theUniversity of Michigan . He graduated in 1966 with a bachelor of science degree in engineering physics and a specialty in computing.NASA career
In 1966 at the age of twenty-one Garman was hired by
NASA . He chose to specialise in onboard computing and was assigned to the Apollo Guidance Program Section where he worked withMIT , supervising the design and testing of theApollo Guidance Computer .During the Apollo missions Garman worked in a support role, advising
flight controller s inMission Control on the operation of spacecraft computer systems. A few months before theApollo 11 mission he suggested that simulation supervisors at Mission Control test how flight controllers might react to a computer error code. Guidance officerSteve Bales responded to the simulated error by calling an abort, which was found to be a needless reaction for that particular code. As Garman later recounted, "Gene Kranz , who was the real hero of that whole episode, said, 'No, no, no. I want you all to write down every single possible computer alarm that can possibly go wrong.'" Garman made a handwritten list of every computer alarm code that could occur along with the correct reaction to each of them and put it under the plexiglass on his desk.1202
An error in procedural protocol went undetected during simulations and during the final descent of
Apollo 11 this led to a switch in the lunar landing module (LM) being set to the wrong position. As a result (and unknown to anyone at the time) the onboard guidance computer was needlessly processing data from the rendezvousradar . Then, as the LM descended its separate landing radar acquired the lunar surface. Now processing data from two radars instead of only one as intended, the computer's duty cycle grew heavier than expected and a series of "1202" and "1201" alarms began signalling an executive overflow. Several seconds after the first alarmNeil Armstrong , with some concern apparent in his voice said, "Give us a reading on the 1202 program alarm." Meanwhile, given his knowledge of the computer systems Garman had already advised Steve Bales the computer could be relied upon to function adequately so long as the alarms did not become continuous. [ [http://klabs.org/history/apollo_11_alarms/console/index.htm "Console audio recording of Apollo 11 Lunar Landing"] ] Bales, who as guidance officer had to quickly decide whether to abort the mission over these alarms, trusted Garman's judgement and informed flight director Kranz. Within seconds this decision was relayed through CAPCOM to the astronauts, Apollo 11 landed successfully and Garman received an award from NASA for his role in the mission.Bales later recalled, "Quite frankly, Jack, who had these things memorized said, 'that's okay', before I could even remember which group it was in". [cite web| url = http://www.honeysucklecreek.net/msfn_missions/Apollo_11_mission/hl_apollo11.html | title = Apollo 11 | author= Lindsay, Hamish | accessdate = 2006-07-11]
IT and senior management
After the Apollo program Garman played a key role in the development of high level
programming language for theSpace Shuttle . From 1986 through 1988 he worked at NASA Headquarters inWashington, D.C. as director of information systems services in the Space Station Program Office. Returning toJohnson Space Center in 1988 he held various senior positions in information systems, finally serving as Chief Information Officer of Johnson Space Center from 1994 through 2000.Lockheed Martin
In 2000, Garman left NASA and became a part of the OAO Corporation. Two years later OAO was bought by
Lockheed Martin and Garman became Lockheed Martin's technical director of NASA services, in charge of technical support for the company's contractual activities with NASA.References
External links
* [http://klabs.org/mapld05/invited/garman_bio.htm John R. Garman: Biography]
* [http://www.jsc.nasa.gov/history/oral_histories/GarmanJR/GarmanJR_Bio.pdf John R. Garman Biographical Data Sheet]
* [http://klabs.org/history/apollo_11_alarms/console/index.htm Console Audio of Apollo 11 landing]
* [http://www.jsc.nasa.gov/history/oral_histories/GarmanJR/garmanjr.pdf Oral Histories]
Wikimedia Foundation. 2010.