Malmstrom 1967 - public domain

Malmstrom AFB ICBM Shutdown

UAP Oracle Intelligence Terminal β€” Case File CF-015

Malmstrom AFB ICBM Shutdown

πŸ“… March 16, 1967
πŸ“ Malmstrom Air Force Base, Great Falls, Montana
NUCLEAR FACILITY INCURSION
VERDICT: Multiple Launch Control Officers

Witness Testimony Under Oath
Witnesses

10 ICBMs Simultaneously Offline
Documentation

10/10
Evidence Quality

Highest β€” nuclear ICBM shutdown documented
Historical Significance

In the early morning of March 16, 1967, Minuteman ICBM missiles at Echo Flight, Malmstrom AFB, were taken offline one by one within seconds of each other while a glowing red oval object was reported hovering over the front gate by security personnel. Launch Control Officer Robert Salas was on duty in the underground capsule when his commander reported the UFO sighting above ground moments before all ten missiles in his flight went to ‘no-go.’ A separate incident at Oscar Flight occurred around the same time. This is the best-documented case of UAP interference with nuclear weapons systems.

Consensus Narrative

The Air Force’s official position was that the shutdowns were caused by a ‘glitch’ in the guidance system. This explanation was given to maintain classification. A subsequent Air Force report has never been released in full. The Air Force later claimed in 2010 that Salas ‘misidentified’ the incident β€” a claim Salas has publicly rebutted with documentation and fellow officer testimony.

Documentary Record

Robert Salas testified under oath before a 2010 press conference at the National Press Club, alongside six other military officers who witnessed UAP incidents at nuclear facilities. Captain Eric Carlson, the officer above Salas, has corroborated the incident. The 10-missile shutdown at Echo Flight is in official Air Force records β€” the debate is only about the cause. Robert Hastings documented 150+ cases of UAP near nuclear facilities for his book ‘UFOs and Nukes’ β€” Malmstrom represents the clearest example.

⚑ Clues Often Missed

β–ΆTen ICBMs going offline simultaneously is physically impossible under the ‘glitch’ explanation β€” each missile has independent systems. A simultaneous shutdown of 10 separate, hardened independent systems requires an external cause.
β–ΆSecurity personnel reporting a glowing red oval above the front gate were debriefed immediately and ordered not to discuss the incident β€” standard protocol for an event the Air Force did not want investigated.
β–ΆRobert Hastings documented 150+ similar incidents at nuclear sites globally β€” Malmstrom is not isolated. The pattern of UAP activity specifically clustering around nuclear weapons storage and delivery systems is established across decades.
β–ΆThe timing with Rendlesham 1980 (where beams were directed at the weapons storage area) and Tehran 1976 (weapons failure at lock-on) suggests a systematic and consistent pattern of UAP engagement with nuclear assets.

πŸ” Open Threads

β—‰The Oscar Flight incident involved a different set of missiles β€” how many total Minuteman missiles were affected on March 16, 1967, and are those records available?
β—‰What happened to the security personnel who reported the object at the gate? Were they transferred, debriefed under classification, or otherwise removed from the evidence chain?
β—‰The Air Force’s 1969 ‘Bolender Memo’ stated that UAP reports affecting national security were not part of Blue Book β€” meaning Malmstrom was never in the Blue Book record. Where are those reports?

/// END OF FILE ///

You've read the full file. There are 130+ more.

UAP Oracle tracks every disclosure thread β€” congressional hearings, FOIA releases, named whistleblowers, the people trying to stop them. Three ways to stay on the grid:

Scroll to Top