Search Add a publication

ID No : 803   Edit
Title: Rocketdyne - Lunar Ascent Engine
Summary / Review : "The ascent engine was the last one from the moon, and I want to focus on the idea of redundancy and teams in regard to the engine. By teams, I mean teamwork - not just within Rocketdyne. It was teamwork within Rocketdyne; it was teamwork within Grumman; it was teamwork within NASA. These were all important elements leading to the successful development of the lunar excursion module (LEM) engine. Communication, rapid response, and cooperation were all important. Another aspect that went into the development of the ascent engine was the integration of technology and of lessons learned. We pushed all the above, plus technology and lessons learned, into a program, and that led to a successful result. One of the things that I like to think about - again in retrospect - is how it is very "in" now to have integrated product and process teams. These are buzzwords for teamwork in all program phases. That s where you combine a lot of groups into a single organization to get a job done. The ascent engine program epitomized that kind of integration and focus, and because this was the mid- to late-1960s; this was new ground for Rocketdyne, Grumman, and NASA. Redundancy was really a major hallmark of the Apollo Program. Everything was redundant. Once you got the rocket going, you could even lose one of the big F-1 engines, and it would still make it to orbit. And once the first stage separated from the rest of the vehicle, the second stage could do without an engine and still make a mission. This redundancy was demonstrated when an early Apollo launch shut down a J-2 second-stage engine. Actually, they shut down two J-2 engines on that flight. Even the third stage, with its single J-2 engine, was backed up because the first two stages could toss it into a recoverable orbit. If the third stage didn't work, you were circling the earth, and you had time to recover the command module and crew. Remember how on the Apollo 13 flight, there was sufficient system redundancy even when we lost the service module. That was a magnificent effort. TRW Inc. really ought to be proud of their engine for that. (See Slide 2, Appendix I) We had planned for redundancy; we had landed on the moon. However, weight restrictions in the architecture said, "You can t have redundancy for ascent from the moon. You've got one engine. It s got to work. There is no second chance. If that ascent engine doesn't work, you re stuck there." It would not have looked good for NASA. It wouldn't have looked good for the country. There was a letter written that President Richard Nixon would read if the astronauts got stuck on the moon, expressing how sorry we were and so forth. It was a scary letter, really. The ascent engine was an engine that had to work. (See Slide 3, Appendix I)." (Author's abstract)
Author(s) : Harmon, Tim, [Stennis Space Center]
Publication Date: 2009
Category(s) : Transportation / Lunar launch and landers
Web URL : http://hdl.handle.net/2060/20100027321
If this link is broken, please Add Comment below.
We try to keep author contact details, and a backup copy in our offline library.
PERMANENT code(s) : L,U
(Explanation of the
last 3 rows above)
In the row above, there are up to 4 possibilities:
U = URL you can click on to get a copy instantly from another source on the internet, or request it from that source
D = Downloadable from PERMANENT (such as because no other URL known...)
L = LAN copy, PERMANENT has a digital copy but not downloadable from our website
P = Paper copy in the PERMANENT office
Typically, only 0 to 3 methods are available.
NTRS : 20100027321
Submitted by : MEP
Comments: Please add your thoughtful Comments to this paper after reading it.
All comments are reviewed and approved before being posted publicly below.
If you wish to submit a private comment to the curator, instead of a public comment, just write "Private" at the start of your comment.
Corrections and suggested additions to our records are appreciated.
  Add Comment 
Add Comment     Green is public,     Pink is private.
Screen Name: Either real name or anonymous alias are OK.
Real Name and
optional info:

Please provide at least your real name, and optionally additional information.
Email Address: We keep your email address private.
Date - Time Sorry, just click on the field, then on the popup calendar click "Now" then "Done".
Your Comment: (if private to curator, then just start with "Private:" or something like that.)