The Malmstrom AFB Missile Shutdown

UFO

A UFO hovered over a nuclear missile base, and multiple nuclear missiles simultaneously went offline in one of the most disturbing UFO incidents ever reported.

March 24, 1967
Malmstrom Air Force Base, Montana, USA
20+ witnesses
Artistic depiction of Malmstrom AFB Missile Shutdown — wide hammerhead-style saucer with engine ports
Artistic depiction of Malmstrom AFB Missile Shutdown — wide hammerhead-style saucer with engine ports · Artistic depiction; AI-generated imagery, not a photograph of the event

In the cold darkness of a Montana morning in March 1967, deep beneath the prairie in a hardened underground capsule, Captain Robert Salas watched as the impossible happened. One by one, the ten Minuteman intercontinental ballistic missiles under his command began going offline, their status indicators switching from “Alert” to “No-Go” in a cascading sequence of failures that no training scenario had prepared him for. Each of those missiles carried a nuclear warhead. Each had been designed with multiple redundant safety and operational systems specifically to prevent exactly this kind of simultaneous failure. The probability of all ten missiles going down at once had been calculated by engineers at Boeing to be, for all practical purposes, zero. Yet there they were, ten missiles, ten “No-Go” indicators, and above ground, his security guards were reporting a glowing red object hovering silently at the front gate.

The Malmstrom Air Force Base incident of March 24, 1967, is one of the most disturbing events in UFO history, not because of what was seen in the sky, but because of what happened on the ground. Something interfered with America’s nuclear deterrent, the most powerful and heavily protected weapons system ever built, and did so with an ease that implied a technology so far beyond human capability that the implications were, and remain, profoundly unsettling.

The Nuclear Deterrent

To understand the gravity of what occurred at Malmstrom, one must first understand the nature of the Minuteman missile system and its role in American defense strategy. The Minuteman was the backbone of the United States’ nuclear triad, the ground-based component of a strategic defense architecture that also included submarine-launched ballistic missiles and nuclear-armed bombers. Each Minuteman missile stood approximately sixty feet tall in its underground silo, armed with a thermonuclear warhead capable of destroying a city, and was maintained in a constant state of readiness, able to launch within minutes of receiving a valid launch order.

The missiles were organized into flights of ten, each controlled by a launch control center, known as a capsule, buried deep underground and staffed by a two-person crew of missile combat officers. These officers monitored the status of their missiles twenty-four hours a day, seven days a week, ensuring that each weapon remained operational and ready. The entire system was designed with extraordinary redundancy. Multiple independent circuits, backup power supplies, and fail-safe mechanisms ensured that the missiles would remain available for launch under any conceivable circumstances, including nuclear attack on the base itself.

Malmstrom Air Force Base, located near Great Falls, Montana, was home to the 341st Missile Wing, which operated one hundred and fifty Minuteman missiles spread across a vast swath of central Montana prairie. The missile silos, called launch facilities, were dispersed over thousands of square miles, connected to their launch control centers by hardened underground communication cables. Each launch facility was surrounded by a chain-link fence and monitored by electronic security systems, with security police teams available to respond to any breach.

The system was designed to be invulnerable. No single point of failure could take multiple missiles offline simultaneously. The missiles were independent of each other, with separate power supplies, separate guidance systems, and separate communication links to their controlling capsule. The only scenario in which multiple missiles would go down at the same time was if something affected all of them simultaneously, an external force acting on the entire flight at once. The designers had considered this possibility and dismissed it. No known technology could produce such an effect.

Oscar Flight: Captain Salas

In the early morning hours of March 24, 1967, Captain Robert Salas was on duty as deputy missile combat crew commander at Oscar Flight’s launch control center, one of the missile capsules assigned to the 490th Missile Squadron. His commanding officer, Lieutenant Fred Meiwald, was also present in the underground capsule. Above them, on the surface, security guards maintained their watch over the launch control facility.

At approximately 8:00 AM, Salas received a call from the topside security guard, reporting that strange lights were being observed in the sky above the facility. The guard described the lights as unusual but did not seem alarmed. Salas, focused on his duties below ground, acknowledged the report but did not assign it particular significance. UFO reports from military personnel were not unheard of, and most proved to have conventional explanations.

A short time later, the guard called again, this time clearly frightened. A large, glowing red object was hovering silently outside the front gate of the launch control facility. It was clearly visible, clearly structured, and clearly not any aircraft or natural phenomenon the guard had ever seen. The object was close, perhaps just above the fence line, and it appeared to be watching the facility. The guard was requesting instructions and sounding close to panic.

Before Salas could fully process this report, alarms began sounding in the underground capsule. The status panels that showed the condition of each of the ten Minuteman missiles under Oscar Flight’s control began changing. One by one, the missiles registered a “No-Go” condition, indicating that they had gone offline and were no longer launch-ready. The failures did not occur all at once but in rapid sequence, each missile dropping off the board within seconds of the last.

Salas and Meiwald ran through their checklists, attempting to diagnose the cause of the failures. They checked their own systems, verified their communication links, and ran diagnostic procedures on the missile circuits. Everything within the capsule was functioning normally. The problem was at the missile silos themselves, ten separate locations spread across miles of Montana prairie, each of which had independently suffered a failure that took its weapon offline.

The failures were not caused by a loss of power to the silos. They were not caused by a communication breakdown between the capsule and the missiles. They were caused, according to subsequent investigation, by faults in the missiles’ guidance and control systems, faults that occurred simultaneously across all ten weapons despite the complete independence of those systems. Whatever had caused the failures had reached into each silo individually and disrupted the missile’s ability to function.

Echo Flight

Salas and Meiwald were not alone in their experience. At Echo Flight, another launch control center in the same missile wing, a similar sequence of events was occurring. Echo Flight’s ten Minuteman missiles also went offline, their status indicators showing “No-Go” conditions in the same rapid cascade that Salas had witnessed at Oscar Flight.

The Echo Flight incident has been described by multiple witnesses, though the details have been slower to emerge than those of the Oscar Flight event. What is known is that UFO reports were also being made in the vicinity of Echo Flight’s launch facilities at the time of the missile failures. Security guards at one or more of the remote launch sites reported seeing unusual aerial phenomena, lights and objects that did not correspond to any known aircraft, in the same time frame as the shutdowns.

The simultaneous failure of missiles at two separate flights, each miles from the other, deepened the mystery considerably. A local equipment malfunction might explain the failure of one missile, or even several missiles in a single flight, if a common vulnerability were identified. But the failure of twenty missiles across two geographically separated flights, occurring at the same time and in the same manner, eliminated virtually all conventional explanations and pointed to an external cause affecting a wide area.

The Investigation

The Air Force launched an immediate investigation into the missile failures. Boeing, the prime contractor for the Minuteman system, was brought in to analyze the shutdowns and determine their cause. Both military investigators and Boeing engineers examined the affected missiles, tested their systems, and reviewed every possible technical explanation for the failures.

The investigation’s findings were as remarkable as the events themselves. No equipment malfunction was identified. No software error was found. No common vulnerability that could have caused all the missiles to fail simultaneously was discovered. The missiles were tested after the incident and found to be functioning normally, their systems showing no evidence of permanent damage or degradation. Whatever had caused them to go offline had done so temporarily and without leaving a detectable trace in the hardware.

Boeing’s analysis was particularly significant. The company’s engineers concluded that the probability of all ten missiles in a single flight failing simultaneously due to random chance was essentially zero, so small as to be statistically meaningless. For twenty missiles across two flights to fail simultaneously, the probability was astronomically smaller still. The engineers stated flatly that an external cause was the only plausible explanation, something outside the missiles themselves had affected all of them at once.

The nature of this external cause was never identified. Electromagnetic interference was considered but could not account for the specific type of failure observed in the guidance and control systems. No conventional source of electromagnetic energy in the area was identified that could have produced the effect. The possibility of sabotage was investigated and ruled out. The missile silos had not been breached, and there was no evidence that anyone had tampered with the weapons.

The Classification and the Silence

The events at Malmstrom were classified. The participants were debriefed by superior officers and told not to discuss what had happened. This was standard procedure for incidents involving nuclear weapons, which were surrounded by layers of secrecy and security classification. But the effect of the classification was to suppress knowledge of the event for decades, preventing public discussion and independent investigation.

Captain Salas and other witnesses honored their orders for many years, but the weight of what they had experienced eventually led them to speak publicly. Salas, in particular, became a vocal advocate for disclosure, describing the Malmstrom events at press conferences, in documentaries, and in his book “Faded Giant.” He testified before the National Press Club in Washington, D.C., alongside other military witnesses of UFO events, and has been a consistent and credible voice calling for official transparency.

Lieutenant Meiwald confirmed Salas’s account of the Oscar Flight shutdown. Other military personnel who had been stationed at Malmstrom at the time of the incident came forward to corroborate various aspects of the story. Former security guards described the UFO they had seen at the Oscar Flight gate. Missile maintenance crews confirmed the unusual nature of the failures. The picture that emerged from these multiple independent accounts was consistent with Salas’s description of the events.

The Air Force has never provided a satisfactory public explanation for the Malmstrom missile shutdowns. Official statements have acknowledged that missile failures occurred but have not addressed the UFO reports or the correlation between the sightings and the shutdowns. The gap between the documented events and the official explanation remains one of the most significant silences in the history of America’s nuclear program.

The UFO-Nuclear Connection

The Malmstrom incident was not an isolated example of UFO activity near nuclear weapons facilities. Throughout the Cold War, numerous UFO sightings were reported at or near nuclear weapons storage areas, missile silos, nuclear power plants, and other installations associated with nuclear technology. The pattern was too persistent and too widespread to be easily dismissed as coincidence.

In 1975, a series of UFO overflights at Malmstrom and other northern-tier missile bases prompted security alerts and investigation. Objects were tracked on radar and observed visually by military personnel as they penetrated restricted airspace around missile launch facilities. These events, documented in official Air Force records later obtained through Freedom of Information Act requests, demonstrated that the 1967 incident was not a one-time occurrence but part of an ongoing pattern of UFO interest in America’s nuclear arsenal.

Similar incidents were reported at other nuclear facilities. At Minot Air Force Base in North Dakota, at Ellsworth Air Force Base in South Dakota, and at missile sites in Wyoming, security personnel reported UFOs near missile silos during the same general period. In the United Kingdom, the Rendlesham Forest incident of 1980 occurred adjacent to RAF Bentwaters and RAF Woodbridge, bases that were widely believed to store American nuclear weapons.

This pattern has led some researchers to propose that whatever intelligence is behind the UFO phenomenon has a specific interest in humanity’s nuclear capabilities. The nature of this interest, whether it represents surveillance, concern, warning, or something else entirely, remains a matter of speculation. But the correlation between UFO activity and nuclear weapons facilities is too well-documented to be ignored.

The Implications

The Malmstrom incident raises questions that extend far beyond the UFO phenomenon itself. At its core, the case is about the vulnerability of the most powerful weapons system ever created. If an external force, whatever its nature, can simultaneously disable multiple nuclear missiles without physical contact, without leaving evidence, and without being identified or intercepted, then the fundamental assumptions underlying nuclear deterrence are called into question.

Nuclear deterrence depends on the certainty that weapons are available for use. If an adversary believes that a nation’s nuclear arsenal can be neutralized by an unknown external force, the deterrent effect is diminished. If the weapons themselves can be switched off at will by something that cannot be identified, tracked, or countered, then the entire strategic framework built around nuclear weapons is based on a premise that has been empirically falsified.

This may explain, at least in part, the military’s reluctance to discuss the Malmstrom incident publicly. Acknowledging that nuclear missiles were disabled by an unidentified force would be, from a strategic perspective, an admission of vulnerability that no military establishment would make voluntarily. The classification of the incident and the silencing of witnesses served not just the usual imperatives of nuclear secrecy but the broader strategic interest of maintaining the appearance of invulnerability.

Legacy

The Malmstrom Air Force Base missile shutdown remains one of the most consequential UFO cases ever documented. It is a case in which the phenomenon moved beyond mere observation and into direct physical interaction with military systems, an interaction that had potential strategic implications for national and global security.

Captain Salas, now long retired, continues to speak publicly about the events of March 24, 1967. His testimony has been consistent for decades, corroborated by other witnesses, and supported by the documented facts of the missile failures. He does not claim to know what the object at the gate was or where it came from. He simply states what happened: a UFO appeared at his launch control facility, and while it was there, his nuclear missiles went offline. When the object departed, the missiles came back.

The Montana prairie where the missile silos stood is quiet now. Many of the launch facilities have been decommissioned, their silos sealed and their capsules abandoned. But some remain active, their missiles still standing ready in their underground tubes, their crews still watching their status boards through the long watches of the night. Whether anything watches them in return, from the dark skies above the prairie, is a question that the events of March 1967 posed and that no one has yet been able to answer.

The missiles went down, all of them, at once, while a red light hovered at the gate. The engineers said the probability was zero. The Air Force said nothing at all. And the questions that morning raised, about what shares our skies, what takes an interest in our most terrible weapons, and what power it possesses over them, remain as urgent and as unanswered as the day they were first asked.

Sources