137 Pages, No Return Address
SPADE stands for Space Development. The Air Force used it as the internal codename for a 137-page classified planning guide dated October 20, 1959, produced by the Air Force Ballistic Missile Division (AFBMD), the California-based unit then responsible for military satellite development, operating under the Air Research and Development Command (ARDC). The name of Major General Osmond J. Ritland, the AFBMD commander from April 1959, appears in the National Reconnaissance Office’s scan of the document.
The guide was digitized as a 5.5-megabyte PDF and is held in the NRO’s WS-117L Records declassified collection, document 54 in that series. John Greenewald of The Black Vault published it publicly on September 2, 2023. No declassification date appears in the available record, no releasing authority is identified, and the specific directorate within AFBMD that produced the document is not stated anywhere in the available material. Sixty-four years separate the document’s date from its public appearance. What happened to it in the intervening period is not addressed in the available record.
The Problem, in Their Own Words
The document states its own cause directly. The Air Force, as of late 1959, had no unified framework governing its space program, and the guide opens by acknowledging this in plain administrative language. The word “urgent” appears in the document’s own account of why the plan was needed.
The problem had already been named formally. In February 1959, the Air Force’s Deputy Chief of Staff for Plans completed an analysis concluding that the service’s weakness in space came from its failure to develop a coordinated program, and recommended the Air Force build its own integrated space effort rather than simply requesting mission authority from the Advanced Research Projects Agency (ARPA), which until September 1959 had held primary authority over military space development. When ARPA’s dominant role ended and mission responsibilities were divided among the services, the Air Force gained authority over reconnaissance and surveillance satellites and, exclusively, over military space launch vehicles. SPADE was written into that reorganization.
The guide drew on Air Force General Operational Requirements already issued by Headquarters USAF, supplemented by additional requirements the document describes as necessary to complete a comprehensive program. Its three stated objectives were: identify Air Force space requirements, catalogue the systems already under development or under consideration, and advance the technology needed to achieve those systems.
A Tool Designed to Stay Incomplete
The document describes itself, in its own language, as “very preliminary” and as an initial report designed to serve as the framework for continuing study, to be revised periodically as circumstances changed. That characterization is a design choice, not a placeholder.
Its intended readership divided into two groups. Air Force commands were to use it as a reference for articulating operational requirements; technical centers and laboratories were to use it for assessing what those requirements would demand in development terms. Section VII of the document, as identifiable in the NRO-released scan, covers systems analysis and sub-system correlation, including a consolidated schedule of space systems programs and a summary of specifications for programs that had reached the specification stage by October 1959. The longer analytical goal was to map interdependencies among technical requirements and identify areas where available technology still fell short of mission timelines. The document was built to locate gaps.
Bureaucratic Rush at the Dawn of the Space Age
The straightforward reading of SPADE is that it is precisely what it describes itself as being: a coordination instrument produced under genuine institutional pressure in October 1959. That reading is consistent with everything in the available record.
Sputnik launched in October 1957, two years before SPADE was dated. The military services spent the intervening period competing for mission authority while ARPA held the organizational center. When that arrangement ended in September 1959 and the Air Force found itself responsible for specific space programs without a unified planning framework, a coordination guide was a direct and logical response. The ARDC had undergone a reorganization announced on October 5 and 6, 1959, roughly two weeks before SPADE’s date. A planning guide that admits, in its own text, that the program it describes is not yet fully defined, produced in that specific organizational moment, requires nothing beyond that context to explain it.
No Verdict, No Successor, No Final Version
The record is silent on what followed. The document states explicitly that it was to be revised as circumstances required. Whether any revision was ever produced, and whether such a revision has been released, is not established in any source reviewed.
No declassification date or releasing authority appears in the record. Whether SPADE was formally part of the WS-117L program or was filed in that collection for administrative reasons is not addressed in any source reviewed. AFBMD’s successor organization, the Space Systems Division, was established under the Air Force Systems Command in 1961. Whether SPADE fed into that reorganization, was superseded by it, or was simply archived is not addressed in any source reviewed.
The Interior of the Document
A specific and bounded uncertainty deserves to be stated on its own terms. What the full 137 pages contain is not fully determinable from the summary material publicly accessible. Section VII is identified in the NRO scan as addressing a consolidated schedule and system specifications for programs at the specification stage in 1959. The names of specific space systems described as under development or under consideration do not appear in the accessible summary.
That is a statement about the limits of the available material, not a claim about what the full document holds or withholds. The SPADE guide’s stated purpose was to catalogue the systems then in development; whether the 137-page text does that in detail visible to a reader of the summary is simply not established by what is accessible. The assessment concluded, in the document’s terms, that the program was urgent, preliminary, and in need of a coordinating framework. Whether that framework ever reached a final version, the record does not say.