The 1967 Malmstrom Air Force Base Nuclear Incursion: Analysis of Strategic Air Command Missile Shutdown Records
— EXECUTIVE SUMMARY
On March 16, 1967, multiple Minuteman intercontinental ballistic missiles at Malmstrom AFB abruptly dropped offline simultaneously while security guards reported an illuminated aerial object hovering over the launch control facility. Declassified military records and subsequent congressional inquiries examined the incident as a benchmark case of electromagnetic disruption at critical defense installations.
Sequence of the E-Flight and Echo-Flight Shutdowns
In the early morning hours of March 16, 1967, personnel stationed at Malmstrom Air Force Base in central Montana experienced one of the most thoroughly analyzed multi-sensor incursions in U.S. military history. Lieutenant Robert Salas, serving as the Deputy Missile Combat Crew Commander at the Echo Flight Launch Control Facility (LCF), received a report from the topside security controller detailing an unexplained luminous object hovering directly above the perimeter fence of the site.
Within seconds of this visual encounter, the underground capsule's command console registered an alert cascade. Indicator lights signaled 'No-Go' status across the flight: all ten Minuteman I intercontinental ballistic missiles (ICBMs) sequentially fell into a non-operational mode. Each missile had suffered an uncommanded guidance and control failure, rendering the primary retaliatory assets completely disabled.
Simultaneously, reports indicated that another launch complex under the 341st Strategic Missile Wing—Oscar Flight—suffered an identical rapid shutdown of its missile complement under similar observational conditions. In total, nearly twenty strategic nuclear missiles dropped from high alert to inoperability within minutes.
Official Inquiries and Technical Evaluations
Strategic Air Command immediately ordered an exhaustive technical investigation to determine the cause of the sudden hardware and software failures. Extensive telemetry diagnostics conducted by Air Force technical staff and contractor Boeing examined potential causes, including power transients, atmospheric conditions, and commercial carrier failure.
Investigators systematically ruled out external utility fluctuations and internal circuit flaws, failing to replicate the simultaneous failure mode across redundant backup power channels. Subsequent declassified case files acquired under FOIA requests and indexed by civilian defense archives documented that no single mechanical or electrical origin could be definitively established. The incident returned to mainstream intelligence scrutiny in recent years, prompting witness depositions before congressional defense committees and technical reviews conducted by the All-domain Anomaly Resolution Office (AARO).
— CHAIN OF CUSTODY: SOURCES & FURTHER READING
— FIELD REPORTS (0)
Sign in to post a field report.
No field reports yet. Be the first to contribute.
DISCLAIMER: Every story on this site is based on documented real-world reports or official records. We do not publish fiction. All sources are cited above.
