Documents / Document

James A. McDivitt oral history (Doug Ward)

NASA Johnson Space Center · 1999-06-29 · 110 pages · text from the file's own layer

This is a NASA Johnson Space Center Oral History Project transcript of astronaut James A. McDivitt, interviewed by Doug Ward at Elk Lake, Michigan, on 29 June 1999. McDivitt talks about flying F-86s in Korea, test pilot work at Edwards, and his first class at the Aerospace Research Pilot School. He also covers turning down Dyna-soar, joining NASA in 1962 and learning to be an Apollo Program Manager. He describes the Change Board and says decisions were not second-guessed.

  • p. 6 …t a definition of the roles and missions of all the different military services and NASA…
  • p. 29 …control, there was no doubt in my mind what my decision would have been. The Mission…
  • p. 37 …There wasn’t anybody in that Mission Control Center who knew anything about it, so there…
  • p. 40 …Your flight—your Gemini IV mission—was also the first flight where Mission Control was located…
  • p. 61 …But sometimes they just got out of control. WARD: Getting back to the effects of the…
  • p. 68 …We made very few changes to it for the original missions. We made a lot
  • p. 69 …McDivitt 29 June 1999 12-69 of changes to it later on for the longer mission…
  • p. 90 …And nobody was getting this live feed of us possibly losing an Apollo mission. And when…
  • p. 91 …One of which was to allow the reporters in Mission Control with access to the flight…
Johnson Space Center Oral History Project James A. McDivitt
29 June 1999 12-101
I think that was a good decision.
Then every one of the big flights we had, we had a major problem, you know. My
first effort as a Program Manager was Apollo 12, when we launched it and then it got struck
by lightning twice. Then I had to decide whether it was okay to send it to the Moon or not.
And I did. Then 13 was—it was probably the greatest spaceflight anybody has ever flown.
And that worked out fine. Then—I think it was 14, we had solder balls flying around and
sending “I’m going to shut off”—engine shut off signals to the engine. And in 15 we had a
major problem. I don’t remember what they were. 16 we had the gimbal thing. And we
were able to go forward with all of those except 13.
And the philosophy that I used I think is important. Because I always thought when
the guys are on the ground and we hadn’t launched anything, we had no investment of risk.
So that it would be easy to stop. A little thing could go wrong, we could stop it. The only
risk that we would have, we’d have another month on the pad if it was going to take another
month, which did increase the risk. So, I was always weighing the risk that we had invested
or the risks that we were going to get into, against the gain that we were going to have.
Now if we’d launch and something happened, then I’d have to—if something went
wrong, you already had the risk of the launch. So, I would be more aggressive on a
individual problem. It’d be the same problem if we were airborne or on the ground. If we
were airborne, I would go forward a lot more than I would have on the ground. And if we
were at the Moon, where we’d made the risk of getting—taken the risk of getting there, I
would be more aggressive in the decisions I made at the Moon than I would be back at the
Earth. And if we were separated and were about to do the lunar landing or something like
that, I would be more aggressive in the decisions I made there than if we were anyplace on
the way.

About this file

Document, cited by the archive. The PDF is mirrored here; the original link is above. 110 pages are in the text index: search them above, or from the library's search.