The spacecraft I had labored over was now safely in orbit. Humans were heading to the moon for the first time. And that command module worked like a dream, with the fewest problems of almost any flight in the program. After orbiting the moon ten times, my colleagues returned safely to Earth without a hitch. We grew ever closer to a lunar landing. First, however, was the Apollo 9 mission.
As a member of its support crew, Apollo 9 was the first flight in which I truly had a stake. We only had two months after the Apollo 8 mission to finish planning and prepare to launch. NASA was hustling to get the lunar module ready for its first manned test flight, while I worked on the command module, finalizing the checkouts and the docking tests. We were acutely aware of time running out. It was the spring of 1969, the year NASA planned to land astronauts on the moon. We had a lot of test flying to do before that could happen.
When the Saturn V carrying the Apollo 9 crew thundered off the launchpad in early March, I was aware that three friends—Jim, Dave, and Rusty—were aboard this time, which was quite a different feeling. I had worked with these guys for a year and naturally felt very relieved when they safely reached orbit. Although they were not going to journey to the moon, in many ways their mission was even more important. They tested all of the elements required for a moon landing: the command and service modules, the lunar module, and the spacesuit designed for the lunar surface. When Jim and Rusty entered the lunar module and undocked from Dave in the command module, it was a real test of faith; Dave now had the only spacecraft with a heat shield. In order to return all three astronauts safely back to Earth once the test flying was done, it was vital that the two spacecraft find each other in orbit and redock.
Flying solo in the command module, Dave had an enormous responsibility shouldered by no astronaut before. He had to know how to hunt down and rescue his two crewmates if anything went wrong with their lunar module. Dave carried out his duties perfectly. After ten days, the crew returned safely from Earth orbit in the command module. The two spacecraft had successfully test-flown together, and we now knew that the lunar module was a great flying machine.
After Apollo 9, it was clear that Dave Scott was on a career fast track. Dave splashed down on March 13, and by April 10 NASA publicly named him as the backup commander for Apollo 12. For all NASA knew at that time, Apollo 12 might end up being the first lunar landing, so Dave had gained a plum assignment. He’d earned it.
As a backup commander, Dave needed two other astronauts on his crew. I was in my office in Houston one day when Dave put his head around the door and asked me to join him in a meeting with another astronaut, Jim Irwin. After the three of us sat down in his office, Dave came right to the point, telling us casually that he’d been assigned to the mission. Would we like to join him on the backup crew?
I answered right away: “Hell, yeah—absolutely!” I was enormously pleased that Dave wanted me on his crew. I had always been somewhat in awe of him, so his offer was a dream come true. Although the backup crew does not normally get to fly the mission, they generally became the prime crew three missions down the road. If we played our cards right, Dave explained that day, we would be the prime crew for Apollo 15. It looked like we were all going to fly to the moon, perhaps as early as the following year.
I have no idea why I was selected for that crew. I suspect that I would have been assigned to an earlier mission if it hadn’t been for the switches of missions with Apollo 8 and 9. As it was, I think my name, and Jim’s, were simply next on the list of eligible astronauts. I had a feeling that our peers rated Jim and me highly for the work we had done, and that Deke Slayton probably asked Dave if we’d be good additions for his crew. I believe that Dave was happy to have us. Certainly, if he’d had any objections, we would not have flown with him.
Whatever the reason for my assignment, I knew some of the hardest work of my life now lay ahead. A known perfectionist, Dave would be a tough boss. It wasn’t hard to see the signs of his disciplined West Point background. I knew that training with him would be a challenge, but if I could handle it, I would end up a better astronaut and a better person.
There were three different Apollo crew positions: commander, command module pilot, and lunar module pilot. There never seemed to be any doubt that I would be named as the command module pilot. Even for Apollo 9, I specialized in that spacecraft and its docking mechanism. I’d spent so much time working with command modules at Downey that I already had a lot of experience related to the position. It never felt like a conscious decision, simply the way my experience had directed me. Jim Irwin, on the other hand, had helped to develop and check out the lunar module. It made perfect sense that he would be the lunar module pilot.
Of those two positions, which was the better one? It was a tradeoff. The command module pilot was able to fly a spacecraft, but the lunar module pilot set foot on the moon. I guess if your goal was to walk on the moon, disregarding everything else, then being a lunar module pilot was the safest bet. But despite the title, you were essentially a systems engineer in the lunar module. You monitored the spacecraft while the commander, in this case Dave, flew it from lunar orbit to the lunar surface and back. In the meantime, the command module pilot flew the command and service module to and from the moon, as well as solo in lunar orbit, and was responsible for docking with the lunar module. I was keener on the idea of actually flying something. Less glory, but more flying—that was my tradeoff.
There was another consideration: the best route to become a mission commander was to first serve as a command module pilot. Dave Scott had just done that. The reason was simple: if you spend years training to be a command module pilot, then you only have to learn how to fly one other spacecraft when you become a commander. A lunar module pilot would have to learn how to fly two. It wasn’t impossible, just much harder, because it took at least a year and a half of full-time training to understand just one of those vehicles.
I was proud to be the first person in my selection group to be assigned a command module pilot crew position. In fact, I was the first person with no prior space experience to ever be assigned that slot for a lunar flight. It felt like a huge honor; the kind of thing Deke only did if he thought you were up to the task.
Jim Irwin and I had joined NASA at the same time, and this was the first backup crew assignment for both of us. An air force test pilot and University of Michigan graduate like me, Jim and I didn’t know each other before the space program. He had been at Edwards a few years before I got there. He worked on the precursor to the SR-71 Blackbird spy plane. He’d originally applied to NASA in 1963, but was rejected because of injuries he received in a horrific air crash two years earlier. There had been some doubt that he would ever pass the physical, but he got in on his second try, because he worked hard to get back into condition.
Jim and I, now sharing an office, quickly became good buddies. Slim and sleek, Jim was a runner and a weight lifter, muscular with dark, slicked-back hair like a beach boy. He was also very handsome, and probably could have used his good looks to get his way with a lot of people. But I never saw him play that card. During our training, Jim was mostly quiet and withdrawn. He could be very thorough and detail oriented, which was a great asset for a crew. But he was also extremely laid-back. There were times when I felt like shaking him and shouting “Jim, are you there?” He was so restrained and reticent; I really wished he would come out of his shell.