Despite the fact that his degree was in electrical engineering, Greene was assigned to the flight dynamics branch and trained to be a Flight Dynamics Officer (FIDO) for the upcoming Apollo program. His responsibilities in Mission Control would include monitoring the trajectory of the Apollo spacecraft, computing changes in orbit, and plotting course corrections and adjustments.
His first shift as a flight controller was during the launch of the unmanned Apollo 6. The launch turned out to be a memorable one, as two engines cut out on the second stage of the Saturn V booster less than five minutes after lift-off. Although the mission was not aborted, it was a challenging launch for the Flight Dynamics officer—the spacecraft diverged from its intended trajectory so severely that Greene was nearly forced to call an abort.[5]
In 1969, Greene was chosen to work the descent shift for Apollo 11, the first lunar landing. This was a coveted and prestigious assignment, showing the esteem in which he was held by his superiors.[6] Flight Director Gene Kranz, who also worked the descent shift, described Greene as "elite in the ranks of the FIDOs, cocky and crisp with his calls."[7]
During the Apollo 13 crisis, Greene played a lesser role. Unlike many other flight controllers, most notably Gene Kranz, he was not positive about the astronauts' chance of survival. "A lot of them in retrospect will tell you how macho and cool [it was]," he said in an interview some years later, "but it was pretty grim."[8] Greene later stated that "when they opened up that capsule, I was sure all they would find would be three dead bodies. I honestly didn't see how we could get them home."[9]
After the Apollo program concluded, Greene spent two years as a Range Safety Coordinator, planning the procedures that would be followed if something went wrong with the trajectory of the Space Shuttle during launch. He fought to keep the Shuttle from being fitted with a range safety destruct system, which would allow it to be destroyed remotely from the ground. However, he was not successful and believed that he was removed from the position as a result of his stand on the issue.[11]
Greene remained in the flight dynamics branch until 1982, spending 1976 through 1979 as section head and 1980 through 1982 as branch chief. He was a FIDO on STS-1 and worked his last mission as FIDO in 1981 on STS-2, the second Shuttle launch. By that point, his responsibilities in the flight dynamics branch were largely managerial.[1]
That year, at the request of Johnson Space Center flight operations director George Abbey, he began the process of training to become a flight director. He worked STS-3 and STS-4 as a backup flight director, learning the job by being paired with the experienced flight director Tommy Holloway and observing him at work. Greene's first mission as flight director in his own right was STS-6, which launched on April 6, 1983.[1] As a flight director, Greene specialized in the ascent shift, considered to be one of the most demanding and dangerous phases of a mission.[12] He worked on ten flights between 1983 and 1986, including STS-61-C, which was notable for having included Rep. Bill Nelson (D-FL) as a member of the crew. In his book about the mission, Nelson characterized Greene as a "no-nonsense type of man," "underpaid and overworked," yet dedicated to his job.[13] His tenth and final mission as lead Flight Director was on STS-51-L.[10]
Challenger disaster
Greene was not originally assigned to work the STS-51-L mission, which was scheduled to launch a mere ten days after the landing of STS-61-C. Due to staffing issues, he was pulled from STS-61-C and reassigned as ascent flight director for STS-51-L. As flight director, Greene was involved in discussion (although by his own recollection, "not a lot") about concerns with the cold weather and ice on the morning of the launch. These concerns had been worked primarily during the shift preceding his, and their conclusion had been that the freezing weather was not a reason to call off the launch as far as the orbiter was concerned.[14] While he did have the authority to halt the countdown, he chose to report 'GO' to the KSC Launch Director.
In the minutes following the loss of Challenger, Greene's responsibilities as flight director centered on ensuring that data from the accident was properly recorded and preserved, and that incident reports were written up.[15]
NASA adopted a policy of minimum engagement with the press in the immediate aftermath of the accident. On the following day, the New York Times noted that "neither Jay Greene, flight director for the ascent, nor any other person in the control room, was made available to the press by the space agency".[16] He did, however, appear at a press conference later that day, where he answered questions about the accident. All the data received at Mission Control up to the time of Challenger's disintegration appeared normal, he reported, and he was not able to shed light on the accident's cause.[17]
Managerial positions
After Challenger, Jay retired as a flight director. In October 1987, after a short period working with a study group on lunar exploration, he was appointed head of NASA's safety division. The division had been created after the Challenger accident at the recommendation of the Rogers Commission, which saw its establishment as key in creating a new, more vigorous "safety culture" at NASA.[18] However, Greene feared that too much introspection by NASA engineers could lead to a damaging loss of confidence. In an interview a year later, he said that NASA had been on "a fantastic guilt trip," adding that "I believe NASA has been overly eager to defend itself against all critics. Any time you have an independent panel, you ought to be able to name a defense attorney for the status quo."[19]
In the following years he worked as Deputy Associate Administrator for Exploration at NASA Headquarters in Washington, DC from 1991 through 1993, he also held other positions throughout. In 1995 he became Manager of the Space Shuttle Engineering Office, a technically challenging job that he enjoyed greatly. "That was an amazingly good feeling," he later said, "owning four Shuttles. Going down to the Cape and visiting them and actually feeling ownership and responsibility for them." However, his opposition to the creation of the United Space Alliance was controversial, and he spent less than two years in the position.[20]
From 1996 to 2000, Greene was Deputy Manager for Technical Development on the International Space Station. He received the NASA Distinguished Service Medal, the Rotary Stellar Award, and a Silver Snoopy award for his work on the station. Finally, between 2000 and 2004, he served as Chief Engineer at Johnson Space Center, where his role consisted primarily of advising the Center Director.[1]
Retirement
After retiring from NASA in 2004, Greene worked as a part-time consultant on the Exploration Systems Architecture Study, which aimed to provide a blueprint for America's return to the Moon and Mars. "We put together a greybeard review team," explained NASA Associate Administrator Rex Geveden, describing Greene as "a famous technical curmudgeon in the Agency."[2]
In films
Greene was interviewed extensively for two History Channel documentaries about Mission Control, Failure Is Not an Option and Beyond the Moon: Failure Is Not an Option 2.
Footnotes
^ abcdJ. Greene, oral history, December 8, 2004, JSC OHP.
^K. Sawyer (September 25, 1988). "The Struggle Back to the Launch Pad; After Shock and Disbelief, the Space Community's Sense of Purpose Reemerged". Washington Post. pp. A22.
Cohen, Don (2006). "Interview with Rex Geveden". Academy Sharing Knowledge (NASA). Archived from the original on September 29, 2006. Retrieved September 21, 2006.
Recer, Paul (January 28, 1987). "Jay Greene: Challenger Destroyed Confidence For A Time". Associated Press.
Reinhold, Robert (January 29, 1986). "At Mission Control, Silence and Grief Fill a Day Long Dreaded". New York Times. p. A8.
Sawyer, Kathy (September 25, 1988). "The Struggle Back to the Launch Pad; After Shock and Disbelief, the Space Community's Sense of Purpose Reemerged". Washington Post. p. A22.