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.

60 The Dorian Files Revealed: a Compendium of the <strong>NRO</strong>’s Manned Orbiting Laboratory Documents<br />

Worries Over <strong>MOL</strong> Security<br />

When <strong>NRO</strong> officials in Washington and Special<br />

Projects personnel on the West Coast read Dr.<br />

Brown’s 4 January memorandum, they were startled<br />

by its reference to acquiring a <strong>MOL</strong> reconnaissance<br />

capability. Twelve months before, in January 1964,<br />

the Director of the <strong>NRO</strong> Staff had expressed concern<br />

over the breakdown of security discipline resulting from<br />

widespread <strong>MOL</strong> discussions at that time. Subsequently,<br />

the <strong>NRO</strong> devised and established Project DORIAN as a<br />

means of controlling all information relating to satellite<br />

reconnaissance activities.<br />

Now, in January 1965, General Martin * bluntly informed<br />

Dr. McMillan that Brown’s memorandum constituted a<br />

violation of <strong>NRO</strong> security. He said its implication, although<br />

it did not explicitly use the word “reconnaissance,” was<br />

obvious. “The overall impression created in the minds of<br />

unwitting people involved,” he said, “has been that <strong>MOL</strong><br />

has finally been assigned a reconnaissance mission.”<br />

He emphasized the need for prompt security decisions<br />

before any further <strong>MOL</strong> correspondence was issued,<br />

pointing to the following dangers if no action was taken:<br />

The security of <strong>MOL</strong> reconnaissance<br />

aspects is inescapably tied to the<br />

security of the unmanned satellite<br />

reconnaissance program. Exposure<br />

of <strong>MOL</strong> reconnaissance capability<br />

to anyone outside the BYEMAN<br />

system automatically will provoke<br />

pressure for disclosure of unmanned<br />

reconnaissance data. Such personnel<br />

will want to know how the <strong>MOL</strong><br />

capability compares with the<br />

unmanned satellite reconnaissance<br />

capability. 5<br />

As a consequence of this situation, a working group<br />

which included General Greer’s special assistant, Col<br />

Ralph J. Ford, and Col Paul E. Worthman of the <strong>NRO</strong><br />

Staff, was formed to prepare recommendations on<br />

the security aspects of the <strong>MOL</strong> program. The group<br />

proposed a basic approach which would provide for<br />

“an absolutely clear and separate division between<br />

reconnaissance oriented tasks (DORIAN/BYEMAN)<br />

and non-reconnaissance related tasks in <strong>MOL</strong>.” General<br />

Greer endorsed this approach and on 30 January 1965<br />

recommended to Dr. McMillan that all payload studies<br />

and. development of passive-in-nature Sigint and<br />

terrestrial (of the earth) image forming sensors, “having<br />

* At this time General Martin, former Director of the <strong>NRO</strong> Staff, was<br />

understudying General Greer, who was scheduled to retire on 1 July 1965.<br />

practical intelligence collection application,” be controlled<br />

by the Director of <strong>NRO</strong> under Project DORIAN and within<br />

the BYEMAN security system. Studies and work not<br />

involving reconnaissance payloads, i.e., such as those<br />

concerned with general experiments to determine man’s<br />

usefulness in space, would be subject to normal security<br />

restrictions, such as those contained in DoD Directive<br />

520012 and AFR 205-3. 6<br />

Dr. McMillan approved these recommendations and, on<br />

5 February, he issued a paper titled “Special Security<br />

Procedures for the Department of Defense Manned<br />

Orbiting Laboratory,” a copy of which he sent to Dr. Brown.<br />

He advised the Defense Research Director that it had<br />

become clear from detailed analysis of work statements,<br />

procedures and methodology, “that the only practical<br />

recourse is to keep any reconnaissance, including active<br />

sensor work, black.” He said he thought this could be<br />

handled in a manner “which does not detract from the<br />

efficiency of the current activities nor will it hamper the<br />

DoD-NASA exchange of information...” 7<br />

Seven weeks later McMillan also issued additional<br />

guidance and security policies to govern <strong>MOL</strong> study and<br />

developmental activity. He emphasized that all payload<br />

study and other work would have to be cleared by him to<br />

insure appropriate security controls. 8<br />

A Revised <strong>MOL</strong> Management<br />

Structure<br />

Dr. Brown’s redirection of the program on 4 January was<br />

followed by important changes in the <strong>MOL</strong> management<br />

structure. As noted earlier, General Schriever during 1964<br />

had urged that a strong central management office be set<br />

up in the Washington area. McMillan, however, decided<br />

that an Air Staff coordination office, which in mid-1964<br />

was organized as the Office of the Assistant for <strong>MOL</strong> † ,<br />

would be sufficient for the time being. General Schriever<br />

objected to this arrangement as inadequate. He said<br />

the new office simply could not provide the leadership,<br />

channels, and direction needed for the program. On 18<br />

August 1964, he once more strongly urged the Air Force<br />

Under Secretary to establish “a single integrated office.” 9<br />

In response to General Schriever’s criticism, Dr.<br />

McMillan on 3 September met with Colonel Schultz, the<br />

Assistant for <strong>MOL</strong>, and Mr. Frank Ross, of the Office of the<br />

Assistant Secretary for Research and Development, to<br />

discuss the management question. Afterwards, he asked<br />

them to prepare working papers on <strong>MOL</strong> management<br />

† Redesignated on 9 November 1964 as the Assistant for Manned Flight,<br />

to take into account its other responsibilities including the NASA Gemini<br />

experiments project and certain coordination activities involving the space<br />

agency.

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

Saved successfully!

Ooh no, something went wrong!