AI illustration cover for Malmstrom AFB Incident
AI ILLUSTRATION FOR REFERENCE ONLY

Malmstrom AFB Incident

Echo Flight incident · Oscar Flight UFO shutdown · Malmstrom missile shutdown
UNRESOLVED

Mainstream consensus: The Air Force's own engineering investigation documents a real, unexplained shutdown of all ten Echo Flight missiles and explicitly states it ruled out UFO involvement for that specific flight. Separate veteran testimony ties a UFO sighting to a different flight's shutdown around the same period. A 2024 All-domain Anomaly Resolution Office (AARO) historical report confirms it interviewed five former USAF personnel about these nuclear-site claims but has not confirmed a UAP cause for any ICBM malfunction, with later official statements attributing the Echo Flight fault to a transformer failure or an EMP test.

Share this page
Short answer

On 16 March 1967, all ten nuclear missiles in Echo Flight at Malmstrom AFB, Montana, dropped offline within seconds; Boeing's own investigation found no technical cause. Separately, veterans including Robert Salas say a glowing orange disc hovered near Oscar Flight's launch gate during a related shutdown; a 2024 AARO report logged the testimony without confirming a UFO link.

Overview

The Malmstrom AFB incident usually means two intertwined 1967 stories from Montana Minuteman missile fields. On 16 March 1967, all ten nuclear missiles in Echo Flight dropped offline within seconds; a Boeing-led engineering investigation traced an unexplained fault in the hardened intersite cable system and stated that contemporaneous UFO rumors for that flight were checked and disproven. Separately, veteran Robert Salas says a glowing orange disc hovered near Oscar Flight's launch gate around 24-25 March during a related No-Go cascade. A 2024 AARO historical report logged interviews with five former USAF personnel without confirming a UAP cause for any ICBM malfunction.

What happened

At 08:45 on 16 March 1967, every missile in Echo Flight lost strategic alert almost simultaneously, showing No-Go faults on voice reporting systems. Strategic Air Command sent Boeing engineers, who pointed to the shared cable system but never isolated an exact component failure. The team interviewed a mobile strike team and the base radar squadron and concluded no unusual aerial activity was reported for Echo that morning.

Salas, then a deputy missile combat crew commander, later said Oscar Flight security police reported an orange disc over the main gate just before alarms and sequential No-Go faults. Chronology work by researcher Jim Klotz places Salas's account roughly a week after Echo, at a different launch facility - meaning the famous "UFO shut down the missiles" story may conflate two real but separate episodes. Salas stayed quiet until 1996, then co-wrote a public account, spoke at a 2010 Washington press conference carried by CNN, and in 2023 testified directly to a Pentagon AARO investigator.

Why Echo and Oscar stay tangled

Official engineering language ("no technical cause found") is not the same as confirming a craft. Later AARO-linked statements have variously cited a transformer failure or an EMP test for Echo - explanations critics say clash with some unit records. No photograph, radar track, or recovered object has been independently verified for either flight. Nearby military cases with security-police witnesses include Rendlesham Forest Incident and Cash-Landrum Incident. For the glowing-orb craft label often paired with Salas's account, see Orb UAP.

Related phenomena

What witnesses reported

Former deputy missile combat crew commander Robert Salas says security police told him an orange, disc-shaped object was hovering over the Oscar Flight Launch Control Facility's front gate just before alarms sounded and missiles began dropping to "No-Go" status. 1st Lt. Robert Jamison, who helped restart a shutdown flight, separately recalled a UFO-related briefing. The Air Force's own Echo Flight engineering team, by contrast, interviewed a mobile strike team and the base radar squadron and reported no unusual sightings tied to that specific flight's fault.

Proposed explanations

  • Mainstream

    The Air Force's own 1967 engineering investigation found all ten Echo Flight missiles lost strategic alert almost simultaneously because of an unexplained electrical fault traced to the hardened intersite cable system, and it explicitly states that rumors of UFOs around Echo Flight at the time were investigated and disproven.

    Declassified SAC/Boeing Echo Flight engineering report (1967)

  • Alternative

    Former missile officer Robert Salas and fellow veterans say security police separately reported a glowing orange disc hovering near the Oscar Flight launch gate immediately before or during a missile shutdown there, a claim the Boeing engineer who led the technical investigation said he could not explain.

    Robert Salas public testimony; CUFON Malmstrom case file

  • Disputed

    Researcher Jim Klotz's review of unit records suggests the Oscar Flight sighting Salas describes most likely occurred on 24-25 March 1967, over a week after the well-documented Echo Flight shutdown, meaning the UFO claim and the officially investigated fault may concern two distinct incidents rather than one.

    Robert Hastings / Jim Klotz case chronology analysis

Case accounts

Attributed incident and cultural accounts from named sources. Links open the originals; AnomalyWiki does not verify these claims.

Claims vs mainstream

The claim

A UFO caused all ten Echo Flight missiles to shut down.

Mainstream view

The Air Force's own 1967 report says rumors of UFOs around Echo Flight were investigated and disproven; it attributes the fault to an unexplained electrical signal, not a craft.

The claim

The Air Force has never seriously looked into UFO claims at missile sites.

Mainstream view

AARO's 2024 Historical Record Report confirms it interviewed five former USAF personnel who served at Malmstrom and other ICBM bases between 1966 and 1977 about exactly these claims.

The claim

Boeing's own engineers confirmed a UFO disabled the missiles.

Mainstream view

The Boeing engineering lead on the investigation said no technical cause was ever found for the Echo Flight fault, which is different from confirming a UFO caused it.

The claim

Robert Salas's sighting and the official Echo Flight shutdown describe the same single event.

Mainstream view

Later chronology research suggests Salas's Oscar Flight sighting likely occurred around 24-25 March 1967, over a week after the well-documented 16 March Echo Flight incident.

Timeline

  1. 1967-03-16All ten Minuteman missiles in Echo Flight at Malmstrom AFB lose strategic alert within seconds of each other; a Boeing-led engineering team is dispatched to investigate.Source: SAC/Boeing Echo Flight engineering investigation (declassified)
  2. 1967-03-23The engineering investigation report is completed, tracing the fault to the hardened intersite cable system and stating that contemporaneous UFO rumors around Echo Flight were checked and disproven.Source: Declassified Echo Flight engineering report
  3. 1967-03-24Robert Salas, on duty as deputy missile combat crew commander, is told by security police that a glowing orange disc is hovering over the Oscar Flight Launch Control Facility's main gate; missiles there begin dropping to No-Go status soon after.Source: Robert Salas testimony (CUFON case file; Robert Hastings' "UFOs and Nukes")
  4. 1996Salas goes public with his account for the first time, co-written with researcher Jim Klotz.Source: Robert Hastings / Jim Klotz published account
  5. 2010-09-27Salas and six other Air Force veterans describe nuclear-site UFO incidents at a Washington, D.C. press conference live-streamed by CNN.Source: UFOs and Nukes press conference coverage
  6. 2023-02-15Salas testifies about his 1967 Malmstrom experience directly to an AARO staff investigator.Source: Robert Hastings, "AARO Interviews 'UFOs and Nukes' Witnesses"
  7. 2024-02AARO's Historical Record Report Volume I confirms it interviewed five former USAF personnel about UAP claims at Malmstrom and other missile bases, without confirming extraterrestrial causation.Source: AARO Historical Record Report, Volume I (2024)

FAQ

What happened at Malmstrom AFB in 1967?

On 16 March 1967, all ten Minuteman missiles in Echo Flight lost strategic alert within seconds of each other. The Air Force's own investigation found an unexplained electrical fault and stated it ruled out UFO involvement for that specific flight.

Who is Robert Salas and what does he claim?

Salas was a deputy missile combat crew commander on duty, by most chronology, around 24-25 March 1967 at Oscar Flight. He says security police reported an orange, disc-shaped object hovering over the launch facility gate just before missiles there dropped offline.

Are the Echo Flight shutdown and Salas's UFO sighting the same event?

Probably not. Researcher Jim Klotz's chronology work suggests Salas's Oscar Flight sighting happened over a week after the well-documented 16 March Echo Flight shutdown, making them likely separate incidents at different launch facilities.

Did the government ever investigate these UFO claims?

Yes. The Pentagon's All-domain Anomaly Resolution Office interviewed five former USAF personnel connected to Malmstrom and other missile bases and published its findings in a 2024 historical report, without confirming extraterrestrial causation.

What is the official explanation for the Echo Flight shutdown?

The 1967 engineering report blamed an unexplained fault in the hardened intersite cable system; later AARO-linked statements have variously cited a transformer failure or an unannounced EMP test, both of which critics say are contradicted by some unit records.

Is there physical evidence of a UFO at Malmstrom?

No. No photograph, radar track, or recovered object has been independently verified. The claim rests on veteran testimony years after the fact, compared against official but incomplete written records.