Malmstrom AFB Nuclear Incident Files

Malmstrom AFB Nuclear Incident Files are the declassified and near-primary record trail around March 1967 claims that UFOs coincided with Minuteman missile shutdowns near Malmstrom Air Force Base, Montana.¹²³⁴

The strongest public record documents the Echo Flight shutdown on March 16, 1967, while the UFO-report chain and Robert Salas/Oscar Flight shutdown account depend on separate Project Blue Book files, witness testimony, and later source reconstruction.¹²⁵⁶⁷

  Record Provenance

The central Air Force packet is an 88-page scan of declassified Malmstrom materials containing 341st Strategic Missile Wing histories for 1967 and early 1968, including the Echo Flight incident narrative, engineering-investigation references, and later testing summaries.¹

CUFON's archival presentation ties the release to FOIA work and reproduces a USAF declassification release letter dated August 8, 1995, along with representative pages from the 341st Strategic Missile Wing history and a Strategic Air Command message.²

The official Air Force fact sheet places the 341st Missile Wing at Malmstrom, identifies the wing's Minuteman mission, and states that the wing had three operational Minuteman squadrons by July 1963 before later expansion created a 200-missile complex.³

National Archives guidance identifies Project Blue Book as the declassified Air Force UFO-investigation record set, with case files arranged chronologically and accessible through microfilm publication T1206 after the program closed in 1969.⁴

  Echo Flight Shutdown

The 341st Strategic Missile Wing history states that at 0845 local time on March 16, 1967, all sites in Echo Flight shut down with No-Go indications on channels 9 and 12 of the Voice Reporting Signal Assembly, and that all Echo launch facilities lost strategic alert nearly simultaneously.¹

The same history says no other Wing I configuration lost strategic alert at that time, channel 50 data was collected from E-7 and E-8, and all ten sites were returned to strategic alert without launch-facility equipment replacement.¹

The engineering inquiry cited in the history questioned the launch-control crew, estimated the fault sequence at roughly 10 to 40 seconds, and recorded that SAC Headquarters called in OOAMA support for a complete engineering analysis.¹

The task group described in the file included personnel from OOAMA, Boeing, Autonetics, and 15th Air Force, showing that the shutdown moved immediately from local maintenance handling into contractor and higher-headquarters technical review.¹

The investigation ruled out weather as a contributing factor, recorded no unusual communications-maintenance or PAS activity, and reported a negative 801st Radar Squadron finding for radar or atmospheric interference tied to Echo Flight.¹

The same section also says rumors of UFOs around Echo Flight at the time of the fault were disproven, but the stated basis was questioning a Mobile Strike Team that had checked November Flight launch facilities that morning, making that denial an important record detail rather than a full independent audit of all later witness claims.¹

  Engineering Follow-Up

The April-June 1967 history says Boeing testing reproduced a channel 9 and 12 No-Go effect by placing a 30-microsecond, negative 10-to-0-volt square-wave pulse on the Self Test Command line at the C-53P Coupler Logic Drawer interface.¹

The same testing narrative says simulated transformer-failure and power tests at Malmstrom showed no significant noise propagation on the Sensitive Information Network or commercial primary-power lines, and that the cause then appeared to be of EMP or electrostatic nature.¹

The July-September 1967 history again treated adverse power effects as a recurring theory, but said tests conducted to determine that cause had repeatedly led to negative results.¹

The later engineering inspection found no set pattern of loose connections on SIN or ground lines, no arcing, burned areas, or tampering in the interconnecting box, and no major problems with missile-away drawers involved in the incident.¹

  UFO Report Chain

The separate Project Blue Book Belt case packet records a March 24, 1967 ground-visual report near Belt, Montana, classified on the Project 10073 record card as unidentified, with no photographs or physical evidence.⁵⁶

The transcribed Project Blue Book packet says a truck driver reported a dome-shaped object emitting intense light in a ravine, but that ground and air searches were negative and no evidence was found showing that any craft landed.⁵⁶

An unclassified preliminary UFO report in the same packet says Malmstrom agencies received numerous UFO sighting reports between 2100 and 0400 MST in the Great Falls area, including reports of a landing near Belt from several sources that included Cascade County Sheriff's Office deputies.⁵⁶

The packet also identifies Lt. Col. Lewis D. Chase as the base UFO investigating officer, documents a sheriff's ground-search plan and Malmstrom helicopter air-search plan, and later says the operations office had no knowledge of equipment malfunctions during the period of reported UFO sightings.⁶

  Salas and Oscar Flight Caveats

Robert Salas's first-person account originated as a witness statement about a Malmstrom launch-control-facility shift in which security personnel allegedly reported lights and a red, silent, saucer-shaped object before missiles went from alert to No-Go status.⁷

That account is not the same evidentiary category as the March 16 Echo Flight history: Salas described recollection, subsequent phone calls, FOIA results, and conversations with other crew members, while the declassified Air Force history itself documents Echo Flight but not a matching official Oscar Flight shutdown file.¹⁷

The chronology also changed over time; CUFON notes that earlier versions placed Salas at November Flight, while later research and testimony moved the account to Oscar Flight.²

NICAP's Oscar Flight directory dates the reported Oscar event to March 24-25, 1967 near Roy, Montana, and explicitly cautions that there is no documentation for the alleged Oscar missile shutdown comparable to the extensive official record for the March 16 Echo shutdown.⁸

  Why These Files Matter

The files matter because they separate three often-merged strands: a documented strategic-alert loss at Echo Flight, an official Project Blue Book UFO-report packet around Belt and Great Falls, and later witness testimony asserting a second Oscar Flight shutdown.¹⁵⁶⁷⁸

They also preserve the Air Force's own unresolved technical trail: the Echo outage was investigated through SAC, OOAMA, Boeing, Autonetics, and follow-on EMP/power testing, but the public histories did not produce a clean conventional cause.¹²

AARO's 2024 historical report shows why the Malmstrom file remains policy-relevant: AARO interviewed former USAF personnel who served around ICBM silos at Malmstrom, Ellsworth, Vandenberg, and Minot between 1966 and 1977, summarized nuclear-site UAP-disruption claims, and said unresolved allegations would be addressed in Volume II.⁹

The value of the Malmstrom record is therefore evidentiary discipline, not a simple conclusion: Echo Flight is documented, Belt-area UFO reports are documented separately, and Oscar Flight remains a testimonial claim requiring caveats unless additional official records surface.¹⁵⁶⁷⁸

  References

  References

1. documents.theblackvault.com ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹ ↩¹² ↩¹³ ↩¹⁴ ↩¹⁵ ↩¹⁶ ↩¹⁷

2. cufon.org ↩ ↩² ↩³ ↩⁴ ↩⁵

3. af.mil ↩ ↩²

4. archives.gov ↩ ↩²

5. nicap.org ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

6. nicap.org ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷

7. nicap.org ↩ ↩² ↩³ ↩⁴ ↩⁵

8. nicap.org ↩ ↩² ↩³

9. media.defense.gov ↩