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.
10 The Dorian Files Revealed: a Compendium of the <strong>NRO</strong>’s Manned Orbiting Laboratory Documents<br />
document as being submitted for approval in connection<br />
with the fiscal year 1964 budget. He said that specific<br />
recommendations would be forwarded separately. 29<br />
On 9 November Zuckert submitted his recommendations.<br />
He said he recognized the fiscal implications of the Five-<br />
Year Space Program, but explained that it had been<br />
deliberately prepared without regard to cost limitations.<br />
In fiscal year 1964 alone, the proposed projects would<br />
require $1 billion more than the amount tentatively<br />
approved by OSD. The Air Force Secretary said that,<br />
since such costs were unacceptable, he was limiting<br />
his recommendations to four specific programs—Midas,<br />
Saint, MODS, and Blue Gemini—with additional funds<br />
required totaling $363 million in fiscal year 1964. Of this<br />
amount, $75 million would be for MODS and $102 million<br />
for Blue Gemini. Previously, no funds had been provided<br />
for those projects. 30<br />
Concerning MODS, Zuckert argued that it possessed<br />
“distinct advantages beyond Dyna-Soar and the NASA<br />
Gemini program” and would provide a useful vehicle<br />
to help resolve some of the uncertainties concerning<br />
military space applications. As for Blue Gemini, in which<br />
the Air Force hoped to get some “stick time” in space,<br />
he said it would be available at an early date and could<br />
provide “an important and required steppingstone to<br />
MODS.” While NASA’s Gemini operations would be<br />
important for the general acquisition of information,<br />
Zuckert said it could not substitute ‘’for actual Air Force<br />
experience with the vehicle.” 31<br />
Figure 16. Gemini Capsule Used by USAF<br />
Source: NMUSAF<br />
Tentative USAF planning at this time called for six Blue<br />
Gemini launches beginning in May 1965. During the first<br />
four flights, the Air Force would investigate and evaluate<br />
manned space flight techniques and subsystems of<br />
particular interest for MODS and other space operations.<br />
There would be attempts to rendezvous and dock with<br />
an Agena vehicle, inspection of an Agena in orbit, postdocking<br />
maneuvers, and precise recovery. The final two<br />
flights would concentrate on mission subsystem testing.<br />
Each Blue Gemini pilot would first ride as a co-pilot on a<br />
NASA Gemini flight.<br />
In summing up his fiscal year 1964 recommendation,<br />
Zuckert admitted that “certain items appear to be similar<br />
to activities included in the NASA program.” However,<br />
he argued that while this might be considered in some<br />
quarters as ‘’duplication,” he felt it was essential to explore<br />
alternate approaches and to exploit different techniques<br />
to achieve effective, rapid progress in acquiring military<br />
space capabilities. 32<br />
The NASA-DoD Gemini Agreement<br />
Figure 15. Zuckert and LeMay<br />
Source: CSNR Reference Collection<br />
Not unexpectedly, the Air Force’s proposals were<br />
rejected in OSD. Defense officials objected not only<br />
to the price tag, but also to the duplication between<br />
USAF plans and projects already underway in NASA.<br />
Secretary McNamara told a congressional committee<br />
that the Air Force’s recommendations posed “a real<br />
danger that two national programs will develop; one<br />
in the Defense Department and one in NASA.” OSD’s<br />
negative stand was discouraging to the Air Force, but an<br />
important change had in fact occurred. McNamara and<br />
his staff were now in general agreement that DoD—as