
Vandenberg Launch Summary: Documenting 42 Years of Nuclear and Space Operations as Context for Understanding Unidentified Aerial Phenomena
Vandenberg Launch Summary: Documenting 42 Years of Nuclear and Space Operations as Context for Understanding Unidentified Aerial Phenomena
Source file: dow-uap-d49-launch-summary-february-2000.pdf Originating agency: Department of Defense / DoD Modern UAP — 30th Space Wing, Office of History Date range: December 1958 – January 2000 Page count: 113 (all read) High-significance pages: 1–11 (introduction and early launch log), 87–91 (launches 1994–2000), 92–99 (launcher status and history), 100 (glossary)
Official Blurb (from war.gov)
This report summarizes the historical record of launches occurring at Vandenberg Air Force Base between 1958 and 2000.
Summary
This is a comprehensive launch summary compiled by the 30th Space Wing Office of History at Vandenberg Air Force Base, California, and published in February 2000. It catalogs 1,790 launches conducted between December 1958 and January 2000, covering ballistic missiles, satellites, commercial launch vehicles, and NASA missions. The document's relevance to UAP research is direct and essential: it constitutes an exhaustive list of all military and civilian launch activity along the U.S. West Coast, allowing researchers to separate known and documented activity from phenomena that remain unexplained.
Research Article
Introduction
In February 2000, the 30th Space Wing Office of History published a comprehensive launch summary recording all launch activity conducted from Vandenberg Air Force Base since its first launch on December 16, 1958, through January 2000. This document, identified under the code DoW-UAP-D49, is the historically oldest document in the Department of Defense's modern UAP release. Its distinctiveness lies in the fact that it describes no specific UAP incident. Instead, it provides the foundational dataset without which it is impossible to verify whether an object sighted over the Pacific Ocean was a known launch, a classified test, or something for which no explanation exists.
Document Structure and Comprehensiveness
The document contains two principal information systems. The first is a chronological list of all launches, spanning pages 1 through 91. Each entry includes a sequence number, date, operational nickname, operation number (OP#), launch facility, vehicle type, program name, and cumulative data by booster type and command. The second system, covering pages 92 through 99, is the Vandenberg Launcher Status and History table, prepared by the STRAD/HO office and last updated in March 1983.
Scale of Operations: 42 Years of Launches
The document's quantitative data reveals the intensity of military and civilian activity from Vandenberg. In total, 1,790 launches were recorded between December 1958 and January 2000. Launch number 1 was a Thor IRBM from facility SLC-2E on December 16, 1958; launch number 1,790 was a Minotaur from the SLF on January 26, 2000.
Among the principal vehicle types represented are: Minuteman (variants A, B, F, and G), Titan (variants I, II, IIIB, IIID, and 34D), Atlas (variants D, E, and F), Thor/Delta, Peacekeeper, Scout, Pegasus, and Pegasus XL. Operating commands include SAC (Strategic Air Command), AFSC (Air Force Systems Command), NASA, NAVY, ADC (Air Defense Command), AFSPC (Air Force Space Command, which replaced AFSC from 1992), ACC (Air Combat Command), AFMC (Air Force Materiel Command), OSC, MDA (McDonnell Douglas / Boeing), LM (Lockheed Martin), and others.
Historical Phases of Activity
Four principal phases can be identified in Vandenberg's launch history.
Phase one (1958–1964) is characterized by the development of intercontinental ballistic missile (ICBM) capabilities. The early Atlas, Titan I, and Minuteman A launches were primarily developmental tests, demonstrations, and operational validation flights. During this period one facility (OSTF) was also constructed and destroyed following a silo explosion on December 3, 1960.
Phase two (1964–1975) saw a flowering of space programs, including numerous satellite launches aboard Thor/Agena, Atlas/Agena, and Titan IIIB vehicles. The number of participating agencies grew, and NASA–Air Force cooperation began. The SAFEGUARD anti-ballistic-missile program (Minuteman B – SAFEGUARD) operated in parallel.
Phase three (1975–1990) was defined by the consolidation of the Peacekeeper (MX) missile, advanced Minuteman G capabilities, and the development of commercial satellites. From 1985 onward, collaboration with commercial firms such as OSC (Orbital Sciences) and McDonnell Douglas increased, with vehicles such as the Pegasus entering service.
Phase four (1990–2000) brought a fundamental shift: the dissolution of the Soviet Union reduced demand for nuclear test launches while the commercial satellite market expanded rapidly. By the late 1990s new players had entered — Boeing (which acquired McDonnell Douglas on August 4, 1997), Lockheed Martin, and Iridium LLC. The Iridium constellation launches (nine launches, 1997–1998, deploying a 66-satellite LEO system) constitute a chapter of their own.
Connection to UAP Phenomena: Why This Document Was Released
Understanding why a logistical-historical document of this kind was released within a Department of Defense UAP release package requires some reflection, but its logic is clear to researchers. Whenever an illuminated object, fireball, or unaccounted-for phenomenon is reported in the skies over California, Oregon, British Columbia, Hawaii, or the Pacific Ocean, the first step in any serious investigation is cross-referencing the sighting against Vandenberg's launch schedule. If the observation can be matched to a Minuteman G Glory Trip launch, a Peacekeeper FDE test, or an Iridium satellite in transit, the sighting is explained and closed. If not, it remains open.
Beyond that, this document disclosed information that had not previously been in the public domain at this level of granularity: the classified nicknames of test operations (Glory Trip, Olympic Trials, Gin Baby, Old Fox, Giant Moon, Giant Fist), the numerical operation codes (OP#), and the detailed breakdown of launch facilities. This information enables independent researchers and analysts to cross-reference UAP sighting reports from the archive.
Key Findings from the Launcher Status Table
The Vandenberg Launcher Status and History table (pages 92–99, STRAD/HO, March 1983) contains data significant to UAP research.
On December 16, 1958, the first launch in Vandenberg's history took place from facility SLC-2E — also the first U.S. military launch from the West Coast. Facility SLC-1W conducted "the first space launch at Vandenberg and the world's first polar-orbit satellite."
On December 3, 1960, the OSTF facility was destroyed when a silo explosion eliminated it entirely. No actual launch had occurred. The facility was subsequently removed from real-property records.
Nuclear Weapons Program Connections
One of the document's more striking features is the density of nuclear-program operation codes. The visible encyclopedia of operational nicknames includes:
- GLORY TRIP — Minuteman B and G launches for operational testing (FOT/OT Phase I/II/FDE)
- OLYMPIC TRIALS — Minuteman F launches for accuracy testing
- GIANT FIST, GIANT MOON, GIANT BLADE, GIANT PATRIOT — Minuteman F launches
- GIN BABY — Minuteman B research-and-development launches
- OLD FOX — Minuteman G launches for DASO (Demonstration and Shakedown Operations)
Each of these names was classified as recently as 1983. Their publication in 2000 constitutes a step toward transparency. What was not published are the test outcomes: did the missile hit its target? Did it deviate from its planned trajectory? Were unidentified objects observed near the missile during the test?
Key People
This document does not list individual names in the main body of the launch log. However, the appendix table (page 100, INDEX) includes a distribution list naming officers and industry representatives who received the document in 1983:
- Ralph Vernola — Boeing Co.
- Bill Leary — Martin Marietta
- Kenworthy — Martin Marietta / MX40X
- Ed Kranz — TRW
- Robt. Martin — Rockwell
These individuals represent the defense-industry companies that developed the weapon systems launched from Vandenberg. Their names appear in the context of the STRAD/HO document from 1983, which is included as an appendix to the comprehensive 2000 summary.
Locations
| Location | Role |
|---|---|
| Vandenberg Air Force Base, California | Site of all documented launches |
| Point Arguello | Original U.S. Navy site; transferred to the Air Force on July 1, 1964 |
| Pacific Ocean | Impact / reentry zone for all ballistic missiles |
| KMR — Kwajalein Missile Range | Target landing zone for many missiles (not explicit but implied) |
| SLC-2W, SLC-2E | Oldest facilities; active 1958–2000 |
| TP-01 | Peacekeeper test pad; active from 1982 |
| SLF (Space Launch Facility) | Commercial launch facility operated by ITT / California Commercial Spaceport |
Incidents
| Incident | Date | Location | Pages |
|---|---|---|---|
| First launch at Vandenberg | December 16, 1958 | SLC-2E | 92 |
| First space launch at Vandenberg | February 28, 1959 | SLC-1W | 92 |
| World's first polar-orbit satellite | February 28, 1959 | SLC-1W | 92 |
| OSTF silo explosion | December 3, 1960 | OSTF | 93 |
| First Minuteman launch at Vandenberg | September 28, 1962 | LF-00-04 | 95 |
| First Titan II launch at Vandenberg | February 16, 1963 | 395-C | 94 |
| Titan I launch from a silo that had been on strategic alert | May 20, 1969 | 395-B | 94 |
| First Pegasus launch from Vandenberg | April 3, 1995 | Air Lift | 87 |
| Iridium launches (9 launches, 1997–1998) | 1997–1998 | SLC-2W | 88–89 |
| First Minotaur launch | January 26, 2000 | SLF | 91 |
Notable Quotes
From the marginal notes of the launcher status table (page 94):
"Last launch on 20 May 69 involved an ICBM that had been on strategic alert in this silo for a year."
From the notes for launch 1748 (page 89):
"About this time, the Air Force began using the term FDE (Force Development Evaluation) to replace the term OT Phase II used for Peacekeeper and Minuteman G (III) missions."
From the note for launch 1777 (page 91):
"The Athena rocket was formerly called LMLV (Lockheed Martin Launch Vehicle). The name was changed in September 1997."
From the note for launch 1790 (page 91):
"Minotaur was the nickname for 'Orbital Suborbital Program Space Launch Vehicle,' a hybrid booster consisting of Minuteman II and Pegasus stages."
Research Notes
Understanding the document's limits: This document records known and officially acknowledged launches. It does not address classified activity that went unreported, test missiles that deviated from their planned trajectory without public notification, failure events, or UAP observations made in proximity to launches. Genuine UAP analysis would need to cross-reference this list with observation reports from West Coast areas.
Relevance in 2026: U.S. Congressional NDAA guidance from 2022 and 2023 directs AARO (All-domain Anomaly Resolution Office) to account for known-launch "false positives." This document is a working tool for characterizing the "background environment" of known aerial activity against which anomalies can be assessed.
Open questions: Were UAP sightings reported during Glory Trip launches? Did Peacekeeper and Minuteman G test protocols include documentation of anomalous phenomena? Does the missile that was on strategic alert in silo 395-B from 1968 until its launch on May 20, 1969 have any connection to UAP events reported at the same time?
Images
1 image - click any image to enlarge
Related Articles
- DoW/DoD · 1996
Modeling of Unlikely Space-Booster Failures in Risk Calculations
This report, authored by James A. Ward, Jr. and Robert M. Montgomery of the Research Triangle Institute (RTI), presents a mathematical methodology for analyzing improbable space-vehicle and missile failures. Prepared for the U.S. Air Force Space Command (AFSPC) and serving Patrick AFB in Florida (45th Wing) and Vandenberg AFB in California (30th Wing), its central aim is to refine the DAMP risk-analysis program by more accurately quantifying Mode-5 failures — the rare cases in which a vehicle deviates extremely from its planned flight line. This is an engineering-statistical report, not a UAP document.
- DoW/DoD · 2022
Unresolved UAP Report DOW-UAP-PR20: Digitally Annotated Still Image, Kuwait, May 2022
An Unresolved UAP Report (PR series) submitted by USCENTCOM to AARO, consisting of a single still image captured by a U.S. military sensor system in 2022. The original reporter added a freehand red digital annotation encircling an area of interest before forwarding the image to AARO. The image shows an elongated area of contrast in its upper-left quadrant whose intensity increases from northwest to southeast. An accompanying mission report, DOW-UAP-D12, described the UAP as moving north to northeast. The operator could not positively identify the object. AARO was unable to resolve the incident, classifying it as "Unresolved."
- DoW/DoD · 2016
Identification of an Unidentified Flying Object Northwest of Latakia, Syria — P-8A Mission Report, November 2016
On November 18, 2016, a U.S. Navy P-8A Poseidon maritime patrol aircraft assigned to Task Group 67.1 was monitoring Russian naval activity in the eastern Mediterranean when its crew identified a low-flying unidentified object of unknown origin. The object was observed traveling southeast at approximately 500 knots from the area of the Russian Carrier Task Group. The P-8A lost visual contact two minutes after first detection, 40 nautical miles northwest of Latakia. This declassified document represents the first recorded P-8 observation of possible missile activity in the eastern Mediterranean.
- DoW/DoD · 2020-07-16
Mission Report DOW-UAP-D65: Three UAP Observations in the Persian Gulf, July 16, 2020
USCENTCOM Mission Report Misrep 4472514 documents three separate observations of an unidentified aerial phenomenon during a single ISR sortie over the Persian Gulf, the Strait of Hormuz, and the Gulf of Oman on July 16, 2020. A U.S. Air Force operator from the 482 ATKS / 432 AEW reported sightings at 1830Z, 1920Z, and 2345Z at MGRS grid coordinates in the 39R zone. The 21-hour mission supported NAVCENT, and all three observations were captured via full-motion video.