In March 1967, UFOs shut down a flight of nuclear Minuteman missiles at Malmstrom Air Force Base
Where the evidence lands: UnresolvedThat in March 1967 one or more unidentified flying objects appeared over Minuteman missile sites at Malmstrom Air Force Base and caused entire flights of nuclear missiles, first Echo and then Oscar, to drop off alert, and that the U.S. Air Force has downplayed or concealed the connection between the sightings and the shutdowns.
Believed by: UFO researchers and disclosure advocates, a handful of former Minuteman launch officers, and audiences drawn to the UFOs-and-nukes theme; skeptics, most Air Force investigators, and the Pentagon's modern UAP office reject the extraterrestrial reading
The full story
What is documented
Start with the parts of this story that are not in dispute, because they are stronger than in most UFO cases. On the morning of 16 March 1967, all ten Minuteman I missiles controlled by Echo Flightat Malmstrom Air Force Base in Montana dropped off strategic alert within seconds of one another, each showing a no-go fault. This was not a rumor. It was recorded in the 341st Strategic Missile Wing's own history, later released under the Freedom of Information Act.
Strategic Air Command treated it as serious and ordered an immediate engineering analysis. Teams at Malmstrom, at the Ogden Air Materiel Area, and at the Boeing plant in Seattle worked the problem. Their finding was that an electronic noise pulseentering the launch control equipment could cascade through the tightly linked system and knock an entire flight off alert, with the guidance system's logic coupler as the vulnerable point. What they could not do was reproduce the event on demand or name with certainty what generated the pulse. The wing history says plainly that investigators were unable to determine a logical cause.
So the honest starting point is a documented, near-simultaneous shutdown of nuclear missiles that a capable engineering team could not fully explain. The question this file weighs is the next step: whether an unidentified flying object caused it, as the popular version holds, or whether the cause was mundane, if elusive.
The case people make
The believers' version is not built on a light in the sky alone. It rests on a coincidence of two anomalies: missiles failing, and objects reported overhead at roughly the same time. Its most prominent voice is Robert Salas, a former Air Force launch officer who says that days after Echo, while he was on duty far underground at Oscar Flight, security police called to report a glowing red object hovering silently over the site. Within minutes, he says, his own flight's missiles began dropping off alert.
Supporters add the testimony of a Boeing engineer who reportedly said he had been told UFOs were seen near the silos during the malfunctions, and they lean on the investigators' own admission that no cause was pinned down. For a hardened, shielded system to fail with no settled explanation, the argument runs, something extraordinary must have reached inside it.
An entire flight of nuclear missiles dropped off alert, the Air Force could not say why, and men on the surface said something was in the sky. That is a real anomaly, and it is why the story refuses to die.
At its strongest, the case is not that aliens have been proven. It is that a documented failure, a credentialed witness, and a government paper trail together make this the rare UFO claim with a spine, and that the official reluctance to connect the sightings to the shutdowns looks, to believers, like an unwillingness to follow the evidence where it leads.
Where the claim breaks down
The weak seam runs between the two anomalies. A shutdown happened and sightings were reported, but the claim requires that one caused the other, and that link is where the evidence thins.
For Echo Flight, the flight with the firmest documentation, the Air Force's checks found no confirmed UFO tied to the fault, and a mobile strike team sent to look reported nothing unusual. The surface-sighting drama attaches mainly to Oscar Flight, and that account has real problems as evidence. It was given from memory decades later, and its particulars moved over time. Salas at first believed his experience was Echo itself, on the same day; only after researcher Jim Klotz identified the actual Echo officers, and Salas's former commander placed their shutdown at Oscar on a different date, was the timeline corrected. Shifting core details are what one expects from distant recollection, not from a clean contemporaneous record.
The engineering side points away from the exotic as well. The investigators' inability to name a cause is often quoted as if it were a confession that no earthly thing could be responsible. It was not. They identified a plausible mechanism, the noise pulse, and the institutional response was telling: the Minuteman force received electromagnetic-pulse suppression fixes. That is what you do about stray electronics, not about spacecraft. An unsolved 1960s hardware fault is ordinary ground, and treating the gap in the explanation as proof of the paranormal fills a hole in the evidence with the very thing to be shown.
The electromagnetic-pulse question
The newest layer is the Pentagon's. In 2024 its All-domain Anomaly Resolution Office reviewed UAP reports around nuclear sites, and later reporting, including a 2025 Wall Street Journal investigation, tied the Malmstrom episode to a classified electromagnetic-pulse test rather than to any craft. The same reporting argued that the military at times seeded or tolerated UFO stories precisely to cover for secret programs.
Critics of this account, Salas among them, have a fair point worth stating clearly: the EMP-test explanation is largely asserted in official summaries and press accounts, without a fully public primary record showing what was tested, where, and whether it could reach a hardened, shielded launch facility. Some note that the missiles returned to service without the lasting damage an intense EMP might be expected to leave. Skepticism about the tidy new answer is reasonable.
But two things keep that skepticism from reviving the UFO as the default. First, the electronic noise-pulsehypothesis is not a modern invention; it dates to the original 1967 investigation, so the recent EMP account extends the old engineering finding rather than contradicting it. Second, doubting the government's specific explanation does not transfer proof to any competing one. If the EMP story is under-sourced, the correct verdict is that the cause is still not firmly established, which is different from concluding a spacecraft did it.
Why the story endures
Of all the missile-and-UFO tales, this one survives best, and its durability owes as much to its structure as to its facts.
It pairs a genuine anomaly with a maximal stake. The shutdown is real and unexplained, and the target is nuclear weapons, the most consequential machines the country owns. A story that combines a documented mystery with the possibility that something could switch off the deterrent has an emotional grip that an ordinary sighting never achieves.
It also carries credentials and paper. A former launch officer speaking on the record, and declassified unit histories that can be cited chapter and page, give believers materials that feel like proof even where the documents stop short of naming a UFO. And it fits a pattern: similar accounts cling to other bases of the era, and a repeated shape reads, to a sympathetic audience, as corroboration.
Layer on a real history of official secrecy around Cold War missile operations, and every classification stamp and every unanswered question becomes, in the retelling, another brick in a wall the government is presumed to be hiding behind.
Where the evidence lands
Hold the record and the claim apart. The recordis solid and genuinely strange: on 16 March 1967 an entire flight of Minuteman missiles dropped off alert at once, and the Air Force could not conclusively say why. Robert Salas's Oscar Flight account and the surface sightings are real testimony that deserve to be reported, not waved away. None of that is in question here.
The rated claim is narrower: that unidentified craft caused the shutdowns. That specific link is not established. The best documented flight showed no confirmed UFO tied to its fault; the dramatic sightings rest on later, revised recollection; the engineering trail points to an electronic pulse and was answered with hardware fixes; and the modern EMP-test explanation, however thinly sourced in public, extends that same electronics-first reasoning rather than an extraterrestrial one. On the other side, no evidence puts a craft over the silos at the instant the missiles failed.
That is why the verdict is Unproven, not debunked and not confirmed. The shutdowns are documented; the UFO cause is not. An honest reading keeps the anomaly on the table, credits the witnesses, and still declines the leap from an unexplained fault to a deliberate act by unknown craft. The mystery is real. The explanation people most want for it is the part that has never been shown.
What's still unexplained
- The Air Force never published a single, fully settled cause for the Echo Flight shutdown at the time, and the noise-pulse mechanism was inferred rather than reproduced on demand. What precisely triggered the pulse remains, in the strict sense, unresolved.
- How much of the Oscar Flight account can be independently confirmed is unclear, since it rests largely on decades-later recollection and a commander's corroboration, with the original date and flight designation revised along the way.
- The modern EMP-test explanation is asserted in official reviews and press accounts without a fully public primary record, so exactly what was tested, where, and whether it could reach a hardened launch facility is not yet independently documented.
Point by point
The claim: Ten nuclear missiles really did shut down at once, which cannot be a coincidence and points to an outside force.
What the record shows: The near-simultaneous Echo Flight shutdown is genuinely documented in the wing's own history, and the Air Force treated it as a serious anomaly. But an anomalous cause is not the same as a UFO cause. Engineers concluded that a single electronic noise pulse entering the launch control equipment could ripple through and knock the whole flight off alert, which is exactly the tightly coupled failure they observed. That the cause was hard to reproduce makes it a puzzle, not a spacecraft.
The claim: Security guards saw a glowing object over the site at the moment the missiles failed.
What the record shows: The surface UFO reports come mainly from Robert Salas's account of Oscar Flight, given from memory decades later, and the details shifted over time, including which flight and which date. For Echo Flight, the Air Force's own checks found no confirmed sightings tied to the fault, and a mobile strike team reported nothing unusual. Real testimony exists, but it is later, singular, and not independently corroborated at the instant of shutdown.
The claim: Boeing engineers admitted they could find no cause, which means the failure was beyond known technology.
What the record shows: Investigators did say they could not settle on a definitive cause, and that honesty is often cited as proof of the extraordinary. But an unsolved engineering fault in a 1960s guidance system is common ground, not evidence of the paranormal. The team identified a plausible mechanism, the noise pulse, and the practical response was to install electromagnetic-pulse suppression fixes across the Minuteman force, a fix aimed at electronics, not aliens.
The claim: The Pentagon's EMP-test explanation was invented recently to bury the UFO story.
What the record shows: The 2024 AARO review and 2025 reporting attributing the event to a classified EMP test are the newest layer, and critics fairly note the explanation is asserted more than it is fully sourced in public. Yet the electronic noise-pulse hypothesis dates to 1967, long before AARO existed, so the modern account extends the original engineering finding rather than contradicting it. Skepticism about the detail is warranted; it does not restore the UFO as the default cause.
The claim: The Air Force covered up the connection by keeping the records classified.
What the record shows: The documents that establish the shutdown were classified for decades, then released under FOIA, which is how the public learned the specifics at all. Classification of Cold War missile-wing operations is routine and expected, and the released histories describe the fault candidly, including the failure to find a cause. A record that admits an unexplained shutdown is weak evidence of a cover-up of its own contents.
Timeline
- 1967-03-16At about 0845, all ten Minuteman I missiles of Echo Flight, controlled from an underground launch control facility in central Montana, lose strategic alert almost simultaneously, each showing a no-go fault. Strategic Air Command orders an immediate engineering analysis.
- 1967-03Boeing and Air Force engineers run tests at Malmstrom, the Ogden Air Materiel Area, and the Boeing plant in Seattle. They conclude a noise pulse could shut down the flight and identify the guidance system's logic coupler as the vulnerable component, but cannot reproduce or definitively explain what generated the pulse.
- 1967-03-24By Robert Salas's later account, he is on duty deep underground at Oscar Flight when security police call to report a glowing red object hovering over the front gate, moving without sound. Minutes later, he says, the flight's missiles begin dropping off alert.
- 1967The 341st Strategic Missile Wing records the Echo episode in its quarterly unit history under the heading of an investigation into the incident, noting that investigators were unable to determine a logical cause. The record makes no confirmed link to any UFO.
- 1989Timothy Good's book Above Top Secret describes the Echo Flight shutdown, bringing the missile-failure story to a wider UFO readership and prompting Salas to connect it to his own memory of an on-base incident.
- 1995-1996Salas goes public, initially conflating his experience with Echo Flight. Researcher Jim Klotz identifies the actual Echo officers, and Salas's former commander Frederick Meiwald confirms their shutdown was at Oscar Flight, on a separate date, correcting the timeline.
- 2001Researcher John Greenewald obtains declassified 341st Strategic Missile Wing histories under the Freedom of Information Act, giving the public a documentary trail for the Echo Flight shutdown and its inconclusive investigation.
- 2024-03The Pentagon's All-domain Anomaly Resolution Office releases its Historical Record Report, which reviews UAP claims around 1966-1977 nuclear sites and later reporting ties the Malmstrom episode to a classified electromagnetic-pulse test rather than to any craft.
- 2025-06A Wall Street Journal investigation reports that the military at times seeded or tolerated UFO stories to mask secret programs, and repeats the EMP-test explanation for Malmstrom. Salas and several researchers publicly dispute it, reviving the debate.
From the case file
The actual records: declassified, released, or leaked. We link straight to each document in its official archive, so you never have to take our word for it. Read the originals yourself.
Unresolved. Two things are well documented and not in dispute: on 16 March 1967 all ten Minuteman I missiles of Echo Flight at Malmstrom AFB dropped off strategic alert nearly simultaneously, and the Air Force could not pin down a definite cause at the time. A second account, from former launch officer Robert Salas, describes a similar shutdown at Oscar Flight days later, coinciding with guards reporting a glowing object over the site. The rated claim is narrower: that unidentified flying objects caused these shutdowns. The Air Force attributed the Echo failure to an electronic noise pulse in the guidance system, and a 2024 Pentagon review tied the episode to a classified electromagnetic-pulse test, while witnesses insist a UFO was overhead. Because the surface UFO reports and the missile faults are separately real but the causal link is not established, the claim is rated unproven, not confirmed and not fully debunked.
Sources
- 1.Malmstrom UFO incident, Wikipedia (2025)
- 2.AARO Historical Record Report, Volume 1, U.S. Department of Defense, All-domain Anomaly Resolution Office (2024)
- 3.US Pentagon fueled UFO rumors for decades, Wall Street Journal reports, Semafor (2025)
- 4.Pentagon fueled UFO myths around Area 51 to hide secret weapons programs, Wall Street Journal reports, The Jerusalem Post (2025)
- 5.UFOs and nukes: Robert Salas of Ojai recounts shutdown of nuclear missiles, Ojai Valley News (2023)
- 6.Project BLUE BOOK, Unidentified Flying Objects, U.S. National Archives (2024)
- 7.Pentagon planted UFO myths to hide secret weapons programs, report finds, LiveNOW from FOX (2025)
Help us investigate
This is a living case file. If you spot an error or know evidence we missed, tell us, and weigh in on where you land.
Where do you land?
Cast your read on this one.
Comments
Add your take. Comments are read and approved by a human before they appear, so keep it on topic and civil. Please do not accuse named, living people of crimes.