NRO-MOL_2015
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter XIV - NEW FINANCIAL AND SCHEDULE PROBLEMS 1967-1968<br />
143<br />
NEW FINANCIAL AND SCHEDULE PROBLEMS 1967-1968<br />
As noted, from the earliest days of the program Air Force<br />
officials had felt a sense of urgency about getting the<br />
<strong>MOL</strong> into orbit at an early date. They were motivated in<br />
part by their experiences with “the B-70 and Dyna-Soar<br />
programs, which had been dragged out interminably—<br />
mainly due to lack of administration support—until<br />
finally cancelled. In both cases, the Air Force rationale<br />
had been disputed and neither was supported by the<br />
White House. <strong>MOL</strong> on the other hand, had been publicly<br />
endorsed by President Johnson and was assigned an<br />
important mission—very high resolution photographic<br />
reconnaissance. Still, Air Force officials felt it essential to<br />
get a laboratory vehicle into orbit as soon possible. They<br />
were consequently pleased when <strong>MOL</strong> entered Phase II<br />
engineering development in September 1966 and they<br />
had additional cause for satisfaction two months later<br />
when the Gemini B heat shield underwent a successful<br />
test flight launch from Cape Kennedy. The first unmanned<br />
<strong>MOL</strong> launch was set for April 1969 and the first manned<br />
flight for December 1969. *<br />
Although engineering development work got under<br />
way officially in the late summer and fall of 1966, the<br />
<strong>MOL</strong> System Office at the time was still involved in hard<br />
contract bargaining with the Associate Contractors.<br />
The problem was a familiar one: the contractor’s cost<br />
estimate and those of the Air Force were millions of<br />
dollars apart. McDonnell, for example, estimated its<br />
Gemini costs at $205.5 million for a fixed price, incentive<br />
contract whereas the Air Force offered $147.9 million.<br />
Douglas requested $815.8 million to develop and build<br />
the laboratory vehicles (fixed price incentive/cost plus<br />
incentive fee), the Air Force proposed $611.3 million.<br />
General Electric sought $198 million (cost plus incentive<br />
fee), the Air Force offered $147.3 million. 1<br />
With the government and contractors unable to reach an<br />
agreement, Air Force officials—with the approval of the<br />
<strong>MOL</strong> Policy Committee—in late November 1966 adopted<br />
a new “negotiating strategy.” They directed the <strong>MOL</strong><br />
Systems Office to reopen competition for those systems<br />
not already under contract and to halt the issuance of any<br />
further DORIAN clearances to contractor personnel. This<br />
tough stance broke the deadlock; by early December,<br />
the contractors had substantially reduced their cost<br />
estimates to bring them closer to the Air Force offers.<br />
On 4 January 1967—when Dr. Flax summarized the<br />
* This schedule constituted a year’s slip from the launch dates announced by<br />
the President in August 1965. See Chapter XI.<br />
results of these negotiations to Dr. Foster—he was thus<br />
able to report that total <strong>MOL</strong> development costs would<br />
run approximately $1.92 billion, a sum which included<br />
$295.0 million in “deferrals. † ’’ 2<br />
The FY 1968 Budget Crisis<br />
The December 1966 agreements with the contractors—<br />
completed to the handshake stage—were based on an<br />
understanding that OSD would release all deferred fiscal<br />
year 1967 funds and that at least $80 million would be<br />
provided the program in fiscal year 1968. The latter<br />
premise soon proved faulty. OSD—finding it needed<br />
huge sums to support U.S. operations in Southeast<br />
Asia—notified the Air Force on 7 January that it planned<br />
to request only $430 million from Congress in new<br />
obligating authority (NOA) for fiscal year 1968. This sum<br />
was $157 million below the amount the <strong>MOL</strong> Systems<br />
Office estimated was its minimum requirement and $381<br />
million below the contractors’ estimates.<br />
McNamara’s decision meant that the Air Force would<br />
have to renegotiate the prime contracts to reduce fiscal<br />
year 1968 fund requirements to $430 million NOA. On 15<br />
February, in an effort to define a revised <strong>MOL</strong> baseline<br />
to fit the lower funding level, contractor and Air Force<br />
officials,including Dr. Flax, convened a meeting on the<br />
West Coast. It became evident during their discussions<br />
of ways to reduce the impact of the cut in funds that there<br />
would be additional slippage in the launch schedule.<br />
At the end of the conference, Dr. Flax directed the<br />
contractors and the <strong>MOL</strong> Systems Office to prepare new<br />
program schedules, using as their “Bogeys” the planning<br />
figures of $500 million and $600 million NOA’s for fiscal<br />
years 1969. ‡3<br />
It was against this background that General Evans—<br />
soon to be succeeded as Vice Director, <strong>MOL</strong>, by Maj.<br />
Gen. James T. Stewart § —summed up “the current mess’’<br />
and the “Pearl Harbor”-type crisis facing the program. In<br />
a memorandum to several aides, he reviewed various<br />
options they might examine in the future. One would<br />
accept a nine or 12-month program slip; another would<br />
† Items deferred included the data readout system, various spares, some<br />
test activities, and manpower requirements to support “out-of-plant” or field test<br />
operations for all of the contractors concerned.<br />
‡ It was Dr. Flax’s intention to reprogram other Air Force funds to meet the<br />
fiscal year 1968 deficit.<br />
§ Stewart took over on 27 March 1968. General Evans retired to join an<br />
industrial concern.