Picture a Thursday morning in March 1967, somewhere under the rolling prairie of central Montana. Two Air Force officers sit in a concrete capsule a few storeys below the grass, minding ten nuclear missiles. At about 8:45 a.m. an alarm sounds. Then, within what the records put at roughly 10 to 40 seconds, every one of those ten Minuteman missiles drops out of the system with a "No-Go" light. Ten of ten. Not one, not three. The whole flight.
That is the Malmstrom UFO incident, one of the most argued-over stories in American UFO lore, and it happened in Montana, on land you can drive past today. The Air Force has the shutdown on paper. A retired lieutenant says there was a glowing red object at the gate. A skeptic says there was a power failure and a tired memory. Right then, let's see who has the better case.
Malmstrom Air Force Base and its missile field
Malmstrom sits beside Great Falls, Montana, and in the 1960s it became home to the 341st Strategic Missile Wing. Its job was to keep a field of Minuteman missiles buried across the Montana plains, ready to launch. Crews worked in underground launch control centres and, by remote link, watched over the unmanned silos scattered around them. Each group of ten silos was called a "flight", and the flights had alphabet names. Echo Flight lies out east, in the empty country between the little towns of Hilger and Winifred.

16 March 1967: the Echo Flight shutdown
Here is the part the Air Force itself wrote down. The wing's unit history for early 1967, declassified decades later, records that at 8:45 on 16 March every site in Echo Flight shut down with "No-Go" indications. No other flight in the wing lost alert at that moment. Crews got the missiles back on alert within about a day, which is a lot quicker than most people expect from a nuclear arsenal that has just fallen over.
Headquarters took it seriously. A message from Strategic Air Command, as quoted by later researchers, called the loss of an entire ten-missile flight "cause for grave concern". Losing one missile to a gremlin is a Tuesday. Losing ten at once is a very different kind of memo.
What the engineers found
Boeing, which built the missile's guidance system, got involved, with testing at its plant in Seattle as well as at Malmstrom. According to the declassified pages as summarised by Skeptoid, the shutdown behaviour was linked to electrical noise on a communications line that could reach all ten missiles at once. About 200 panels were inspected for signs of electromagnetic damage and showed none, and simulated lightning tests came back negative. The Air Force's conclusion was only that Echo Flight had suffered "some type of adverse power effect". Another reading of the same records says the investigators could reproduce the shutdown only by injecting an artificial voltage pulse into a guidance data line, and that no real-world source for such a pulse was ever identified.
Put plainly: something electrical took out the flight, the engineers had a good idea of how it could have happened, and nobody ever proved what actually did it.
The UFO claim
The unit history also carries a line that explains why this story will not die. It says rumors of unidentified flying objects around Echo Flight at the time of the fault were "disproven". You do not disprove a rumor nobody was spreading, so somebody, somewhere, had been talking.
The loudest voice is Robert Salas, then a 26-year-old lieutenant in the missile wing, who went public in 1996 when the Great Falls Tribune printed his account on 13 August. His story, as he tells it: a security guard topside radioed down that strange lights were manoeuvring in the sky and that a glowing red object was hovering over the front gate of the launch control facility. Minutes later the missiles started dropping offline, and the object was gone. Salas later co-wrote the book Faded Giant (2005), and researcher Robert Hastings gave the case a starring role in UFOs and Nukes (2008). The Black Vault's write-up of the case adds a claim that crews and maintenance teams reported UFOs that morning, one directly over an Echo Flight silo. That is the story as told by later writers, not something the declassified records show.
The trouble with the dates
Here the plot thickens. Salas has said his own incident happened at a different flight, Oscar Flight, "on or about" 24 March 1967, not at Echo on the 16th. The Air Force records found so far describe only the Echo shutdown. No record of a separate Oscar shutdown has surfaced, and two of Salas's former colleagues, Capt. Eric Carlson and Lt. Walter Figel, told researchers in 2010 that they rejected the Oscar story, with Figel saying Oscar Flight "NEVER had any problems", according to Skeptoid. Meanwhile, newspapers of the day reported a UFO sighting at Belt, Montana, about 50 km from Malmstrom, on 24 March. Skeptic Brian Dunning sees no good reason to connect that sighting with any missile trouble. Salas's supporters see a pattern.


What the skeptics say
The skeptics' case is that the records show a real shutdown but no UFO, and that Salas's memory has blended two different times. Dunning, writing for Skeptoid, thinks Salas is honest and mistaken, a victim of memory drift and confirmation bias, and points to a power failure: the 2001 documents mention a short in a transformer at a substation at Winifred, which sent the launch facilities onto diesel generators. Michael Shermer said in a 2008 CNN appearance that he did not think Salas was lying, only that people are not always reliable witnesses. Robert Sheaffer has suggested the thing in the sky was the planet Mars. James Carlson, whose father commanded Echo Flight, has argued the shutdown was an equipment malfunction that was thoroughly investigated, and that Salas's account has changed over the years.
The weak spot in the power-failure theory is that Boeing's engineers, who knew these systems better than anyone, did not simply sign off on "the lights flickered". They kept testing and never pinned down the cause. A utility hiccup that stumps the manufacturer is a little less ordinary than it sounds.
2025: the EMP twist
In June 2025 the Wall Street Journal reported that the Pentagon's All-domain Anomaly Resolution Office (AARO) had traced the Oscar story to a Cold War electromagnetic-pulse test, with a generator mounted about 60 feet above the facility. That reporting is behind a paywall, so the details here come from second-hand summaries. AARO's first historical report, in March 2024, had interviewed five former Air Force members about UAP claims at Malmstrom and other bases, and left unresolved allegations for a second volume that has not been released.
The EMP idea promptly ran into trouble. Salas published a rebuttal in the Ojai Valley News on 10 June 2025. He said he had given AARO a two-hour briefing in 2023 and was never told of a terrestrial explanation, that crews were never briefed on EMP testing on live missiles, and that the Department of Energy says no nuclear testing took place on 16 or 24 March 1967. (That last point is slightly beside the mark, since an EMP generator is not a nuclear test, but it is his argument.) A former AARO deputy director, Timothy Phillips, said he knew of no EMP test and instead described a storm-related surge that beat the filters on the power lines and knocked some silos offline. So the official side has not even agreed with itself.
Weighing it up
- Well documented: On 16 March 1967 all ten Echo Flight missiles went to No-Go in under a minute, an engineering investigation followed, and the cause was never definitively found.
- Documented, but only as a rumor line: The unit history says UFO rumors were disproven.
- A witness's account, decades later: The red object over the gate and the Oscar Flight shutdown. No 1967 paper backs the Oscar event, and the dates do not line up with the Echo records.
- Unresolved: Whether the Echo and Oscar stories are one event told two ways, and whether a power fault, a noise pulse, a test or something else tripped the missiles.
The honest answer is that nobody has shown a UFO did anything, and nobody has shown it did not. What can be shown is that something took out ten nuclear missiles at once and a lot of clever people never agreed what.
Visiting Malmstrom country today
The missile field is not a tourist site. Malmstrom is an active Air Force base, and the launch facilities sit on fenced military property, so the plain fact is that you cannot wander up to one. The place you can go is the Malmstrom Air Force Base Heritage Center and Air Park, just inside the base's 2nd Avenue gate. Its displays have included a Minuteman III missile, Minuteman launch consoles and a launch facility cutaway. It has been listed as open weekdays from 10 a.m. to 4 p.m., but base access rules change, so check before you drive out. For the tin-foil hat, bring a sense of humour. For the prairie, bring a jacket.
...and if you find it, remember who encouraged your questionable life choices.
The short version of this story is on YouTube at @TenToeExpress.
Deep dive yourself
- Malmstrom UFO incident · Wikipedia
- The Day the UFO Deactivated the Nukes · Skeptoid
- UFO Case: Malmstrom AFB UFO/Missile Incident (March 16, 1967) · The Black Vault
- Case File US-1967-001: Malmstrom Echo Flight Shutdown · Anomaly Index
- A rebuttal from Robert Salas of Ojai to Wall Street Journal's June 6 article · Ojai Valley News
- Malmstrom & Eagle Flight: Was this an EMP Test? · Metabunk
- Malmstrom Air Force Base Heritage Center and Air Park · Frommer's