26.12.2015 Views

NRO-MOL_2015

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter XIII - AIR FORCE/NASA COORDINATION<br />

127<br />

AIR FORCE/NASA COORDINATION<br />

By 1965-1966 Air Force and NASA manned space<br />

programs had evolved to the point where the competition<br />

between the two agencies had manifestly declined.<br />

Deeply involved in its Gemini program, NASA at this time<br />

was also laying the ground work for its multi-billion dollar<br />

Apollo moon-landing project.* The Air Force, meanwhile,<br />

was working energetically to get going with the <strong>MOL</strong>,<br />

which it believed would provide the vehicle that would<br />

conclusively demonstrate the value of putting a man into<br />

space to perform various military missions, beginning<br />

with reconnaissance. This period saw increasing<br />

coordination of the efforts of both agencies. Thus, in 1965<br />

the Evans/Garbarini group had worked closely together<br />

on the Apollo/<strong>MOL</strong> studies, which provided comparative<br />

cost figures and other data to the Air Force. Also, the<br />

following year, as we have seen, NASA backed up the<br />

Air Force during the noisy ETR-WTR controversy.<br />

In addition to the above examples of cooperation, the<br />

two agencies coordinated their activities in several other<br />

areas. One involved the release and modification of<br />

certain NASA flight equipment for use in an Air Force<br />

pre-<strong>MOL</strong> flight test program. Another—which generated<br />

differing views before a compromise was reached—<br />

centered on the question of Air Force procurement of the<br />

Gemini B spacecraft.<br />

NASA’s Gemini and the Gemini B<br />

Contract<br />

Several months before John Glenn became the first<br />

Mercury astronaut to orbit the earth in early 1962,<br />

NASA formally announced the initiation of the Gemini<br />

program. On 15 December 1961 it awarded a $25 million<br />

contract to McDonnell to begin design, development,<br />

and manufacture of 13 Gemini spacecraft. (The cost<br />

of these vehicles eventually ballooned to more than<br />

$790 million. † ) NASA also assigned to SSD the job of<br />

procuring man-rated Titan II boosters to launch them.<br />

During 1962-1963, the development work proceeded<br />

satisfactorily and an important milestone was reached<br />

with the successful test firing on 21 January 1964 of the<br />

GT-1 (Gemini-Titan No. 1) launch vehicle.<br />

* NASA was allocated $5.2 billion in new obligational authority in fiscal year<br />

1965, $5.1 billion in fiscal year 1966.<br />

† In February 1963 NASA estimated the cost of the 13 Geminis, two mission<br />

simulators, five boilerplates, and other equipment at $456,650,062. By the end<br />

of the program, however, the cost of the spacecraft and ancillary equipment had<br />

risen to $790.4 million. [NASA Draft Chronology, Project Gemini: Technology<br />

and Operations, pp 108, 409]<br />

Meanwhile, McNamara’s announcement of 10 December<br />

1963 that DoD would undertake the development of<br />

<strong>MOL</strong> made it apparent that certain under standings<br />

would have to be reached by NASA and DoD, since<br />

the system required a modified Gemini. On 23 January<br />

1964, Drs. Seamans and Brown (then DDR&E) agreed<br />

the Air Force should negotiate a preliminary design<br />

study contract with McDonnell, with the arrangement to<br />

be subject to NASA review to assure McDonnell could<br />

do the work without interfering with the space agency<br />

program. The two officials also agreed the contract would<br />

not establish a pattern for any follow-on engineering or<br />

procurement contract relationship with McDonnell. 1 The<br />

Air Force contract subsequently was approved and, in<br />

June, McDonnell began a $1 million pre-Phase I Gemini<br />

B study which it completed by year’s end.<br />

In connection with this contract, the St. Louis firm was<br />

naturally eager to obtain additional Gemini business and<br />

retain the space engineering competency it had acquired<br />

during its work on Mercury and now Gemini. To support<br />

the latter, it had built up a Gemini team which included<br />

441 personnel, 240 of them doing advanced engineering<br />

work. McDonnell advised the Air Force that it would<br />

need an early USAF commitment in order to keep the<br />

team intact. The firm’s situation was discussed during<br />

the summer of 1964 by NASA and OSD officials, and<br />

they agreed that it was in the nation’s interest to retain<br />

the newly-acquired industrial base. However, OSD<br />

was unable to make a commitment until it had decided<br />

whether or not to proceed with <strong>MOL</strong> development. 2<br />

Toward the close of 1964 several factors, including<br />

congressional pressures, conspired to push OSD<br />

toward such a decision. ‡ Thus, when Senator Anderson<br />

expressed concern to the President about duplication<br />

between NASA and DoD space programs and<br />

recommended cancellation of <strong>MOL</strong>, he was assured<br />

the two agencies were working closely together and<br />

would take advantage of each other’s technologies and<br />

hardware. In January 1965 McNamara and Webb issued<br />

a joint statement touching on this point. “Duplicative<br />

programs,” they declared, “will be avoided and manned<br />

space flight undertaken in the years immediately ahead<br />

by either DoD or NASA will utilize spacecraft, launch<br />

vehicles, and facilities already available or now under<br />

active development to the maximum degree possible.” 3<br />

‡ In March 1965 Congressman Teague of Texas expressed concern to the<br />

President that the valuable Gemini industrial team would be disbanded if a<br />

<strong>MOL</strong> decision was not made.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!