Most UFO cases ask you to weigh what someone saw. Malmstrom asks something harder: it pairs a witnessed object with a documented, high-consequence malfunction in the United States nuclear deterrent, and asks whether the two are connected. That combination — trained military officers, a glowing craft, and a flight of intercontinental ballistic missiles dropping off alert within seconds — is why the case has never gone quiet, and why the men who were underground that morning have spent their lives insisting it deserves a serious answer.
An ordinary shift, an extraordinary morning
In March 1967, at Malmstrom Air Force Base in Montana, the Minuteman missile fields were run the way they always were: two-officer crews sealed in hardened underground launch control capsules, each responsible for a flight of ten nuclear missiles sitting in silos spread across the surrounding countryside. On the morning in question, Deputy Missile Combat Crew Commander Robert Salas was on duty underground when he received a call from a security guard on the surface, agitated, reporting strange lights in the sky above the launch control facility.
Salas, by his account, told the guard to keep him posted and thought little of it — until a second, far more alarmed call came moments later: a glowing red object was hovering right over the front gate, and the guards were frightened.
The missiles drop offline
Then, Salas says, the missiles began to fail. Within a very short span — seconds — one after another of the flight’s ten Minuteman missiles dropped from “alert” status into “no-go,” effectively taken off the board and rendered unlaunchable, their guidance and control systems faulting out.
For a crew whose entire purpose was to keep those weapons ready, this was close to unthinkable. A single missile going down for maintenance was routine; most of a flight failing near-simultaneously, in seconds, was not something the system was supposed to be able to do. The commander, Frederick Meiwald, was on the same crew and, over the years, has corroborated the essentials of the account. Salas has stated that a similar shutdown affected another flight, Echo, around the same period, with security personnel there also reporting an object.
What the record says — and doesn’t
Here the case splits into two threads that sceptics and proponents pull in opposite directions. On one hand, the missile shutdowns were real and were investigated: the failures happened, engineers looked into them, and the incident entered the maintenance and unit record. On the other hand, the official explanation for the shutdowns focused on electronic or electrical causes — a noise pulse propagating through the system — and Air Force documentation does not tidily link the malfunction to a UFO.
Sceptics make the reasonable point that a documented electronic fault plus separately reported lights is not the same as an object disabling nuclear weapons, and that the tight causal link rests substantially on the testimony of the officers rather than on a paper trail that says so. Proponents — led by researcher Robert Hastings, who has gathered on-the-record accounts from many former missile officers across several bases — counter that the guards’ object and the near-simultaneous mass failure, in the same place at the same moment, is an extraordinary coincidence to wave away, and that the military had every institutional reason to keep the two threads officially separate.
The UAP Times take
Malmstrom earns a credibility of 2 — Credible. Its strength is the calibre and consistency of its witnesses: these are nuclear-launch officers, security-cleared and rigorously selected, describing a specific operational event with real documentary residue in the missile failures themselves. Its weakness is the join between the two halves — the object and the shutdown are each well attested, but the causal link between them lives largely in testimony, and the official record declines to draw it.
Our reading is that Malmstrom is one of the most consequential cases in the whole field precisely because of what it touches. Strip it to the defensible core and you still have something remarkable: credible military officers reporting an unexplained object over a nuclear missile facility, coincident with an unexplained mass malfunction of the missiles themselves. Whether the craft caused the shutdown or merely shared the sky with it is the open question — but that the two occurred together, at the sharp end of the Cold War, is testimony too solid and too senior to dismiss. It is exactly the kind of case that argues for disclosure rather than folklore.
Further reading: for another case where trained military witnesses met an unexplained object, see The Tehran Dogfight, where jets’ weapons systems failed near the craft. The objects-over-nuclear-sites pattern runs back further than Malmstrom — to the green fireballs over Los Alamos in 1949, whose conference transcript was declassified this month — and forward to the 2015 lockdown at the Pantex warhead plant, where security officers chased an object they could not identify. Malmstrom’s object was reported as a glowing sphere / orb; it’s on the sightings map.
Source: Testimony of Robert Salas and other missile officers; Air Force records; researcher Robert Hastings' interviews