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-28
WARD: One of the things you began to sense in Gemini, and particularly in Apollo and
then even more so in shuttle, is the complexity and the integration of systems, interactions,
one event affecting another in a way that you really can’t intuitively follow or anticipate.
And a simulation, it seems, would draw that out for you in ways you might not otherwise
appreciate.
MCDIVITT: Yeah. And I remember one case stands out very well in my mind. It was on
Apollo 16, when I was the Apollo Spacecraft Program Manager. We were—the lunar
module and command module had separated, and the command module [pilot, Thomas K.
“Ken” Mattingly II] was supposed to fire his engine on the back side of the Moon and come
around in a different orbit. And a certain—and if he had done that, he would have appeared
from behind the Moon at a certain time. And that time came up; no spacecraft. So, there’s
always the thought that, well, maybe he was never going to come around the Moon!
But anyway then, the next time was—some seconds later would’ve been when
he would have come around, had he not fired the engine. And sure enough, it came around at
that time. He hadn’t fired the engines. And we checked what the problem was, and he said
that he had an oscillating actuator on the service module engine; and the Mission Rules were
that if you got down to your last system, you came home. It didn’t make any difference what
it was—as long as it was a critical system. Well, that was a critical system obviously. So,
we had to determine whether the oscillating actuator would work.
WARD: Now this is the actuator that moves the engine nozzle that steers the—
MCDIVITT: It moves—that moves the engine back and forth, and it was going like this
[gestures]. Fortunately, I had flown a test like that on Apollo 9—it was called a stroking

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.