The Malmstrom AFB Missile Shutdowns

Theoretical Alignment

The Malmstrom case earns a moderate ETH score primarily on the strength of its human testimony — credentialed former missile officers who, decades later, described security reports of a hovering luminous object close in time to an unexplained hardware failure — rather than on any instrumented data confirming the object's structure or performance. The Psycho-Social component is unusually significant for this file because the case's public history has been genuinely shaped by decades of retelling, conflation between the Echo and Oscar Flight incidents, and a bitter, ongoing dispute among the primary witnesses' own families about what was actually said and by whom. Neither framework, however, addresses this case's real center of gravity: a documented, still not conclusively explained failure of ten hardened Cold War nuclear-missile control systems at Echo Flight on 16 March 1967, which the Air Force's own history says was unaccompanied by any confirmed UFO report, and a second, Oscar Flight shutdown that is known only from later testimony.

Background

The 341st Missile Wing was reassigned to Malmstrom Air Force Base — renamed in 1955 from Great Falls Air Force Base in honor of Colonel Einar Axel Malmstrom, a former base commander killed in a 1954 T-33 training crash — on July 15, 1961, and became fully operational on July 3, 1963, ultimately controlling 150 LGM-30A/B Minuteman I intercontinental ballistic missiles spread across three squadrons and fifteen ten-missile "flights," each lettered with a phonetic-alphabet designation (Alpha through Oscar). Each flight's ten missiles sat in unmanned, hardened underground silos called Launch Facilities, scattered several miles apart across the Cascade County plains, all remotely monitored and, if ordered, launched from a single hardened Launch Control Facility where a two-officer missile combat crew stood 24-hour alert roughly 60 feet underground in a blast-hardened capsule. A small number of Air Force security personnel, organized into mobile Security Alert Teams, patrolled the dispersed Launch Facilities and responded to intrusion alarms.

Robert L. Salas, a 1964 graduate of the U.S. Air Force Academy, arrived at Malmstrom in 1966 as a newly qualified missile launch officer. On the night of March 24, 1967, he was serving as deputy missile combat crew commander at Oscar Flight under crew commander Capt. Fred Meiwald. Eight days earlier, on March 16, the missile combat crew on duty at Echo Flight — commander Capt. Eric Carlson and deputy 1st Lt. Walt Figel — had experienced the documented incident: the shutdown that generated an engineering investigation and a declassified wing unit-history entry. No Air Force document so far released records an Oscar Flight shutdown; it survives through Salas's testimony and Meiwald's later, partial recollection, and both Echo Flight officers deny that Oscar Flight had any problem. Both crews were flying under the standard, exhausting rhythm of Minuteman alert duty: 24-hour shifts underground, largely isolated from the outside world except for radio contact with their own Security Alert Teams and the wing command post.

The immediate geopolitical backdrop was the peak of the Cold War nuclear standoff: Malmstrom's Minuteman I force represented a substantial fraction of the United States' land-based strategic deterrent, and any anomaly affecting multiple missiles simultaneously was, by definition, a matter of the highest strategic concern — message traffic on the Echo Flight incident reportedly called the failure to find a cause "cause for grave concern." It is against that backdrop that the engineering inquiry was classified, and that later claims of UFO involvement were made.

Complete Timeline

Date	Event
July 15, 1961	The 341st Missile Wing is reassigned to Malmstrom Air Force Base, Montana.
July 3, 1963	The 341st Missile Wing becomes fully operational with 150 LGM-30A/B Minuteman I ICBMs across three squadrons.
1966	Robert Salas arrives at Malmstrom as a newly qualified missile launch officer.
December 19, 1966	Three launch facilities in Malmstrom's A Flight (A-6, A-7, A-10) shut down; the wing history later notes the similarities with Echo Flight: the same capsule crew, adverse weather, and commercial power failure after the shutdown.
March 16, 1967, ~0845 hrs	All ten Minuteman I missiles at Echo Flight, commanded by Capt. Eric Carlson and deputy 1st Lt. Walt Figel, drop into "No-Go" status within seconds of each other. The unit history says "rumors of Unidentified Flying Objects (UFO) around the area of Echo Flight during the time of fault were disproven"; decades later, Figel told Robert Hastings that a guard had radioed a report of "a large round object" over one of the flight's Launch Facilities.
March 16, 1967 (same day)	An investigation begins; a task group from the Ogden Air Materiel Area (OOAMA), Boeing, Autonetics and the 15th Air Force is due on site by 17–18 March. Boeing engineer Robert Kaminski later described himself as leading the Boeing engineering team.
March 16, 1967, ~1450 hrs	A 7.2 kV transformer on the line to site E-3 shorts one phase to ground, and the launch control center logs a power problem at E-1 at 1453 — roughly six hours after the shutdown. The wing history later concludes commercial power switching was "not the cause."
"On or about" March 24, 1967 (Salas)	By Salas's account (first published in this form in the late 1990s), at Oscar Flight deputy crew commander Robert Salas is woken by crew commander Fred Meiwald after a Security Alert Team, investigating a perimeter intrusion alarm, reports fast-moving lights performing erratic maneuvers, then a glowing, red-orange, oval or disc-shaped object hovering silently over the Launch Control Facility's front gate. One guard is reportedly too shaken to complete his shift. Missiles under Salas's command begin dropping to "No-Go" status; accounts of the final count vary between six and ten. No Air Force record of an Oscar Flight shutdown has been released, and Echo Flight's two officers say Oscar Flight had no such problem.
March 24–25, 1967, from ~2100 MST	About five miles southeast of Belt, Montana, truck driver Ken Williams reports a domed object pacing his vehicle before descending into a canyon; Highway Patrolman Bud Nader reports "an unusual light emanating from the area." A Malmstrom teletype records that "between hours of 2100 and 0400 MST numerous reports were received by Malmstrom AFB agencies."
March 1967	By Salas's and Meiwald's accounts, they are debriefed by an Air Force Office of Special Investigations (AFOSI) agent and required to sign non-disclosure statements; the Echo Flight officers' recollections of their own debriefing differ.
Spring 1967	Base UFO investigating officer Lt. Col. Lewis Chase investigates the Belt report and reports "negative results," writing that there were "no equipment malfunctions during this sighting"; he tells Condon Committee investigator Roy Craig of the Echo Flight incident, "I can't talk about that," while assuring him it had not involved a UFO (per Craig's notes, as quoted by Kevin Randle).
March–November 1967	The Engineering Investigation Team's "Report of Engineering Investigation of Echo Flight Incident, Malmstrom AFB, Mont. — 16 Mar 67" (23 March 1967) finds no definitive cause. Later tests reproduce the same No-Go indications by injecting noise pulses into the C-53P logic coupler; OOAMA thinks the cause "of the Electro Magnetic Pulse (EMP) noise or electrostatic nature"; by November the wing history says the cause "has been connected with some type of adverse power effect" but tests "have always lead to a negative result."
1996	After reading a Timothy Good book in 1994, Salas tells the Great Falls Tribune (13 August 1996) of a guard's report of a glowing red object before the missiles at his "Echo" complex went offline. With researcher James Klotz he begins locating surviving personnel; by the time of Faded Giant (2005) he places his own incident at Oscar Flight instead.
2005	Salas and Klotz publish Faded Giant, the first detailed firsthand account of the Oscar Flight shutdown.
2008	Robert Hastings publishes UFOs & Nukes: Extraordinary Encounters at Nuclear Weapons Sites, consolidating decades of interviews including Malmstrom personnel.
Sept. 27, 2010	Hastings organizes a press conference at the National Press Club, Washington, D.C.; Salas and six other retired U.S. military officers testify on the record, carried live by CNN.
2011	Fred Meiwald, in a taped interview with Hastings, confirms a Security Alert Team reported "a bright object" during the Oscar Flight incident but says he cannot personally corroborate the specific red oval object Salas describes at the gate.
2009–2013	James Carlson, son of Eric Carlson, circulates "Echo Flights of Fantasy: Anatomy of a UFO Hoax" and later the book Americans, Credulous, arguing no UFO was involved at Echo Flight, that no incident occurred at Oscar Flight, and disputing Hastings's and Salas's characterization of his father's and Figel's recollections.
Oct. 19, 2021	A second National Press Club-adjacent panel again features Salas and other former missile officers discussing UFO incidents at nuclear sites.
March 2024	The All-domain Anomaly Resolution Office (AARO) publishes its Historical Record Report, Volume I, noting interviews with five former USAF members who served at Malmstrom, Ellsworth, Vandenberg and Minot between 1966 and 1977.
2025	A June 6 Wall Street Journal report, citing unnamed sources, is widely read as attributing the 1967 shutdown to an electromagnetic-pulse test (some readers note the article implies rather than states this). In 2025 interviews, former AARO deputy director Timothy Phillips is quoted describing a report of a "cascading transformer failure" during an "electrical storm." Researchers including Hastings argue the transformer account is contradicted by the wing's declassified unit history. Neither explanation has been published as an official AARO finding.

Echo Flight: The First Shutdown

The documented core of the Malmstrom story begins at 0845 hours on March 16, 1967, when, in broad daylight, all ten Minuteman I missiles assigned to Echo Flight dropped into "No-Go" status within a span the wing's own unit history describes as occurring "nearly simultaneously" (between about ten and forty seconds, per the engineering data). Echo Flight's launch control facility lay between Hilger and Winifred. The missile combat crew on duty, commander Capt. Eric Carlson and deputy 1st Lt. Walt Figel, found themselves watching their entire flight's strategic-alert status collapse at once — an event serious enough that headquarters message traffic reportedly described the lack of an identified cause as "cause for grave concern," reflecting the reality that ten nuclear-armed ICBMs going simultaneously unlaunchable, for reasons no one on duty could immediately explain, was itself a national-security emergency independent of any UFO question.

"A Large Round Object"

The wing's own history says the opposite of the popular story: "Rumors of Unidentified Flying Objects (UFO) around the area of Echo Flight during the time of fault were disproven. A Mobile Strike Team, which had checked all November Flight's LFs on the morning of 16 March 67, were questioned and stated that no unusual activity or sightings were observed." The UFO element instead rests on accounts Figel gave decades later in audiotaped interviews with Hastings and Salas, in which a security guard radioed a report, shortly before the shutdown began, describing "a large round object" hovering directly over one of Echo Flight's Launch Facilities. Figel has described his own initial reaction as dismissive — joking with the guard, "Yeah, right. What have you guys been drinking out there?" — before deliberately withholding the object description when he dispatched Security Alert Teams to investigate the triggered site alarms, specifically so as not to bias what they reported. According to this account, the teams independently radioed back describing the same large hovering object, without having been told what to look for. It is this detail — independent corroboration from personnel who were not primed with the original guard's description — that Hastings and other proponents cite as the strongest point in the Echo Flight narrative. Figel has also said he took the guard's report as a joke, and later told James Carlson that UFOs were not associated with the incident (see below).

Oscar Flight: Salas, Meiwald, and the Object at the Gate

According to Salas, a broadly similar sequence unfolded at Oscar Flight "on or about" March 24, 1967 — a date he has tied to the Belt sighting reports of that night; in his earliest public account, in 1996, he placed the event at Echo Flight. 1st Lt. Robert Salas, serving as deputy missile combat crew commander, was resting in the underground capsule when crew commander Capt. Fred Meiwald woke him amid a run of unusual console indications and perimeter security violations. A Security Alert Team, dispatched to investigate an intrusion alarm at one of the flight's Launch Facilities, first reported fast-moving lights executing maneuvers the guards described as inconsistent with any known aircraft — sudden stops, sharp reversals, tight turns without engine noise — before radioing that a glowing, red-orange, oval or disc-shaped object was now hovering silently just outside the facility's perimeter fence. According to Salas's account, a guard's voice came over the radio: "Sir, there's one hovering outside the front gate! ...A UFO! It's just sitting there. We're all just looking at it." At least one member of the security team was reportedly so shaken by the encounter that he required early relief and, in some accounts, medical attention. Within minutes, missiles under Oscar Flight's command began registering "No-Go" indications one after another; Salas has maintained that all ten missiles were ultimately affected, though some secondary accounts describe the count as six to eight. No Air Force document so far released records an Oscar Flight shutdown, and skeptics including Robert Sheaffer have suggested that a light seen from Oscar Flight could have been the planet Mars.

The Corroboration Problem

Meiwald's own role in corroborating this account has become one of the case's most closely scrutinized details. In a 2011 taped interview with Hastings, Meiwald confirmed that a Security Alert Team he directed to investigate reported "a bright object; a bright, flying object at low-level," and that the guards involved "were upset and were directed to come back to the LCF." But when asked specifically about Salas waking him to describe a bright red, oval-shaped object over the security fence gate, Meiwald said: "I really don't remember that portion of it, relative to the bright object" — explaining that he had been resting when the first missile or two dropped offline and could speak with confidence only to what happened within Oscar Flight generally, not to the specific gate sighting Salas has always centered his account on. Both officers agree they were debriefed by an Air Force Office of Special Investigations agent afterward and required to sign national-security non-disclosure statements.

The Belt, Montana Landing Report

The evening of March 24 produced a separate, independently sourced sighting near Belt, Montana, about 20 miles southeast of Great Falls. At about 9:00 PM truck driver Ken Williams, driving on US 87/89 about five miles southeast of Belt, reported that a domed object paced his vehicle at 50 to 60 miles per hour before descending into a nearby canyon; Williams stopped and approached on foot, describing an intensely bright light that briefly blinded him before the object rose "like a bolt of lightning" and vanished. Montana Highway Patrolman Bud Nader, arriving as the object reappeared, "observed an unusual light emanating from the area" where Williams said it had landed a second time, and three Cascade County deputies searched for about two and a half hours and found freshly broken twigs and branches, with no cattle in the area. The base UFO investigating officer, Lt. Col. Lewis Chase, reported "negative results" after a search, and wrote that there were "no equipment malfunctions during this sighting." A Malmstrom teletype in the Blue Book file records that "between hours of 2100 and 0400 MST numerous reports were received by Malmstrom AFB agencies" — establishing that the region had an unusual concentration of reports on the night of March 24–25, the date Salas later attached to the Oscar Flight shutdown. Blue Book carried the Belt case as unidentified.

Radar, Interceptors, and the Overnight Flap

Several secondary accounts add further detail to the March 24–25 overnight period. Notes by researcher Warren Mahoney, cited by Kevin Randle, place a low object on FAA radar from 3:42 to 4:26 AM; other accounts describe an unidentified target climbing vertically near the missile field, prompting the scramble of two F-106 interceptors, with the object reportedly disappearing from radar as the jets approached and reappearing, climbing to an extreme altitude, once they departed. This file presents that detail with an explicit caveat: unlike the missile telemetry and the Boeing investigation, which rest on the wing's own declassified unit history and a still-extant engineering report, the interceptor-scramble narrative has not been traced by this file's research to a primary Air Defense Command or FAA document, and should be read as a widely repeated but less rigorously sourced part of the case's popular retelling rather than an established fact on the same footing as the missile shutdown itself.

The Boeing Investigation

Echo Flight is the incident that received a formal engineering review. A task group from the Air Force's Ogden Air Materiel Area (OOAMA), Boeing — the Minuteman system's prime contractor — guidance contractor Autonetics and the 15th Air Force investigated, and an Engineering Investigation Team produced the classified "Report of Engineering Investigation of Echo Flight Incident, Malmstrom AFB, Mont. — 16 Mar 67," dated 23 March 1967. According to the wing history, the team judged that "external generated signals" had caused the two No-Go channels, but called this "very remote" because all ten couplers would have had to fail within seconds; weather and the capsule crew were eliminated; and after testing, "commercial power switching operations were not the cause," because other flights on the same substation were unaffected and similar shutdowns in A Flight had different power feeds. A transformer short on the line to site E-3 in the afternoon, after the shutdown, was simulated in May 1967 without producing significant noise. Laboratory tests did reproduce the same Channel 9 and 12 No-Go indications by injecting noise pulses into the C-53P logic coupler, and OOAMA thought the cause "of the Electro Magnetic Pulse (EMP) noise or electrostatic nature"; but no source for such a pulse was found, and by November the wing history recorded that tests "have always lead to a negative result." Boeing engineer Robert Kaminski, who has said he led Boeing's team, later wrote, in a letter Salas and Klotz quote: "There were no significant failures, engineering data or findings that would explain how ten missiles were knocked off alert." According to Salas and Klotz, Kaminski also said he had heard of UFO reports at the time, though his mandate was limited to the hardware.

Debriefing and Silence

Salas and Meiwald describe a similar aftermath: formal debriefing by an Air Force Office of Special Investigations (AFOSI) agent, and a requirement to sign statements acknowledging the classified nature of what had occurred and agreeing not to discuss it. This is, by itself, unremarkable for any incident touching operational nuclear weapons security in the 1960s — but it is also the mechanism proponents point to when explaining why the case remained essentially unknown to the public for nearly three decades, surfacing only once Salas and researcher James Klotz began independently locating and re-interviewing surviving Malmstrom personnel in the 1990s.

Salas Goes Public

Salas's public advocacy began in earnest in the 1990s and culminated in 2005 with the publication of Faded Giant, co-authored with Klotz, the first detailed firsthand account of the Oscar Flight shutdown to reach a general audience. His account has changed in one important respect: in his first public account, to the Great Falls Tribune in August 1996, the missiles that went offline were at his "Echo" complex; by the time of Faded Giant (2005), after the Echo Flight unit history had been released in 2001 naming a different crew, he placed his own experience at Oscar Flight, "on or about" March 24, and has acknowledged that "some uncertainty exists" about whether the Echo and Oscar shutdowns happened on the same morning or on different days. Salas has said he came to see the incident as UFO-related after reading a Timothy Good book in 1994. He has told the story in interviews, briefings and media appearances, including Coast to Coast AM and ABC News. He resigned his Air Force commission in 1971, citing opposition to the Vietnam War, earned a master's degree in aerospace engineering from the Air Force Institute of Technology, worked for the Federal Aviation Administration from 1974 to about 1995, and taught mathematics; he unsuccessfully ran for the U.S. House of Representatives from California's 26th district in 2020.

The Carlson Rebuttal

The case's sharpest and most sustained public dispute did not come from a skeptic outside the story, but from inside Echo Flight's own crew. James Carlson, son of Echo Flight's commander Eric Carlson, has argued at length, in the self-published "Echo Flights of Fantasy: Anatomy of a UFO Hoax" and the book Americans, Credulous, that no UFO was reported at Echo Flight at all, and that Hastings, Salas, and Klotz have built a "poorly executed" and knowingly false narrative around his father's incident. Eric Carlson has denied knowledge of any UFO report to journalists and, replying to Salas in 2010, wrote that "there was no, repeat no, incident at Oscar flight as Salas maintains" (as quoted by Brian Dunning). Figel, replying to Salas in 2010, wrote that "Oscar flight NEVER had any problems" and that the books contain "many inaccurate statements" (as quoted by Dunning), and James Carlson has reported that Figel, in later communications with him, disputed the UFO framing as well, stating that "UFOs were not remotely associated with the Echo Flight Incident, or any other equipment failures" at Malmstrom, and that Salas himself "was never involved in any of them (the flights) at all" — a claim consistent with this file's own finding that Salas's documented, firsthand encounter belongs to Oscar Flight, not Echo Flight.

This creates a genuine, unresolved contradiction rather than a simple case of a skeptic versus a believer. In the same audiotaped interviews cited earlier in this file — interviews Hastings maintains were recorded before Carlson's book was published and are not, as Carlson has suggested, a later fabrication — Figel described the "large round object" report and the independent corroboration from the Security Alert Teams in considerable, unprompted detail, and stated that Carlson had been "sitting right there, two feet away" during the radio traffic describing the object, making it difficult, in Figel's account, for Carlson to have simply missed the conversation. Hastings has published detailed rebuttals, and researcher Kevin Randle has argued arguing that Carlson selectively quotes his father and Figel while omitting or reinterpreting their earlier, on-tape statements. This file does not resolve that dispute in either direction; it is presented here, with each side's own words, precisely because the case's popular retelling too often flattens a genuinely contested, multi-sided family and institutional disagreement into a simple "proven" or "debunked" headline.

2010: The National Press Club

On September 27, 2010, Hastings organized a press conference at the National Press Club in Washington, D.C., at which Salas and six other former or retired U.S. military officers — whose affidavits were later posted online — went on the record by name about UAP incidents at nuclear weapons sites, including Malmstrom, Minot, and F.E. Warren Air Force Bases. The event was carried live by CNN and was, at the time, the largest coordinated public appearance of named former military witnesses in the UAP-nuclear research field. A follow-up event on October 19, 2021, again featured Salas and several other former officers presenting similar testimony and affidavits to a new generation of press coverage.

2024–2025: AARO Revisits Malmstrom

The Pentagon's All-domain Anomaly Resolution Office (AARO), created in 2022 to investigate historical and ongoing UAP reports across the U.S. government, addressed nuclear-site claims directly in its March 2024 Historical Record Report, Volume I, noting interviews with five former USAF members who had served at Malmstrom, Ellsworth, Vandenberg, and Minot Air Force Bases between 1966 and 1977 regarding both sightings and claimed UAP-linked disruptions to launch control facilities. In 2025 interviews given after he had left government, former AARO deputy director Timothy Phillips was quoted as saying that what he knew of was a report attributing the 1967 Malmstrom shutdown to "a cascading transformer failure" during an "electrical storm," and that AARO had found no evidence of UAP activity in the relevant logs. A June 6, 2025 Wall Street Journal report, citing unnamed sources, was widely read as attributing the incident to an electromagnetic-pulse test — a materially different explanation. AARO has published neither explanation as an official finding.

The transformer explanation runs into the primary-source problem the 1967 investigation itself had already documented. The 341st Strategic Missile Wing's declassified unit history states that weather was ruled out as a contributing factor and that commercial power switching was not the cause; the one documented transformer short in the area happened in the afternoon, about six hours after the shutdown, and simulating it in May 1967 produced no significant noise. (The "numerous reports" logged between 2100 and 0400 MST, sometimes cited against Phillips, belong to the night of March 24–25, not to the Echo Flight shutdown, for which the unit history says UFO rumors were disproven.) Hastings and other researchers have publicized these specific, document-level contradictions since Phillips's remarks were made, arguing that his account should be evaluated against the primary documents rather than accepted at face value — a criticism this file finds is well-supported by the surviving unit history text itself, regardless of what one ultimately concludes caused the shutdown.

Circumstantial Evidence

• Ten Minuteman I missiles at Echo Flight dropped to "No-Go" status within seconds of one another on 16 March 1967 — a failure the Air Force's engineering investigation was unable to fully explain even after months of testing. (A second, Oscar Flight shutdown is claimed by Salas but undocumented.)
• The 341st Strategic Missile Wing's own declassified unit history rules out weather and commercial power switching as causes of the Echo Flight shutdown, and a simulated transformer failure produced no significant noise.
• Former crew members recalled, decades later, Security Alert Team reports of a hovering, glowing object close in time to the missile failures, including, per Figel's 2008 account, guards who were not told in advance what they were being sent to investigate.
• A Malmstrom teletype in the Blue Book file records "numerous reports" between 2100 and 0400 MST on the night of March 24–25, the date Salas attaches to the Oscar Flight shutdown, including the Belt sighting.
• Salas and Meiwald say they were debriefed by AFOSI and required to sign non-disclosure statements, consistent with an incident treated as serious and classified regardless of its ultimate cause.
• Explanations for the cause have shifted across nearly six decades (undetermined, "adverse power effect" or EMP/electrostatic noise in the Air Force's 1967 records; transformer failure per a former AARO official's 2025 interviews; EMP test per a reading of 2025 press reporting citing unnamed sources) without ever definitively resolving the case, and the two most recent accounts are difficult to reconcile with each other and with the primary unit-history document.
• Working directly against the case's anomalous reading: the flight where the incident is most thoroughly documented by surviving official paperwork, Echo Flight, is also the flight whose unit history says UFO rumors were "disproven" and whose crew commander denies any UFO was reported at all — a direct, named, on-the-record contradiction from inside the case's own primary source base.

Key Researchers

• Robert Hastings (b. 1950) — The field's leading researcher, whose father's own USAF career brought him to Malmstrom as a teenager. Interviewed more than 150 retired military personnel over four decades and organized the 2010 National Press Club press conference; author of UFOs & Nukes (2008).
• Robert Salas — The Oscar Flight deputy crew commander whose firsthand, on-the-record testimony has anchored the case's public profile since the 1990s; co-author of Faded Giant (2005).
• James Carlson — The case's most sustained internal skeptic, whose self-published research disputes the UFO framing of the Echo Flight incident his father commanded.
• Kevin Randle — Veteran UFO researcher and retired lieutenant colonel who has written source-by-source analyses of the Echo/Oscar dispute and the Belt, Montana sighting, arguing that UFO reports existed around Echo Flight while conceding that no documentation of an Oscar Flight failure exists.
• Brian Dunning — Host of the Skeptoid podcast, whose episode "The Day the UFO Deactivated the Nukes" presents the leading skeptical synthesis of the case, comparing Salas's account with the wing's records.
• Robert Sheaffer — Skeptic who has argued that the light reported at Oscar Flight was very likely Mars, and that the Echo Flight missiles went offline from an electronic fault unrelated to any UFO.

Key Witnesses

The Five Observables Assessment

The Five Observables framework, developed by former AATIP director Luis Elizondo, is used to classify UAP encounters by performance characteristics exceeding known technology of their era. Malmstrom poses a familiar challenge for the framework: witnesses describe a silent, hovering, non-luminous-to-brightly-glowing object with no confirmed flight-performance data, since no radar track of the object itself (as distinct from the missiles' own hardware failure) has been located in a citable primary document by this file's research.

Assessment: Anti-Gravity Lift is rated speculative: witnesses at both flights describe a silent, motionless hover with no rotor wash, exhaust plume, or engine noise, but no instrumented lift data exists to confirm the object was not simply a distant light source. Instant Acceleration is rated speculative largely on the strength of Ken Williams's account of the Belt object rising "like a bolt of lightning" and the erratic, high-speed maneuvering Salas attributes to Oscar Flight's security team, neither of which is independently instrument-confirmed. Hypersonic Velocity is rated absent: no witness or document in this file's research offers a specific, verifiable velocity figure for either object. Low Observability is rated speculative, resting on the less rigorously sourced secondary account of the object disappearing from radar as F-106 interceptors approached; because this file cannot trace that detail to a primary Air Defense Command document, it is flagged rather than treated as confirmed. Trans-Medium travel is rated absent; no air-to-water, air-to-space, or other medium transition was reported at either flight. Taken as a whole, the Five Observables data here is thinner and more secondary-sourced than the missile-hardware anomaly itself, which is this case's genuinely strongest and most independently documented element.

Evidence Assessment

Why "Disputed"

This file rates the Malmstrom AFB missile shutdowns DISPUTED because the case genuinely contains two of the strongest kinds of evidence this catalogue evaluates — multiply-corroborated, credentialed military witnesses, and an independently documented, still-unresolved technical anomaly — sitting directly alongside one of the most concrete, named, on-the-record contradictions found anywhere in this site's case files. What is not seriously disputed: ten missiles at Echo Flight genuinely failed nearly simultaneously on 16 March 1967; a dedicated engineering investigation, with direct physical access to the hardware, could not identify a definitive conventional cause; and explanations offered from or attributed to government sources have changed across nearly six decades, most recently producing two mutually inconsistent accounts in 2025, neither an official finding. The Oscar Flight shutdown, by contrast, is undocumented and denied by the Echo Flight officers. What remains genuinely and specifically unresolved, in a way that goes beyond ordinary evidentiary uncertainty, is the status of the UFO reports themselves: the wing's own 1967 history says UFO rumors around Echo Flight were disproven, and Echo Flight's crew commander, Eric Carlson, denies on the record that any UFO was ever reported during his watch, directly contradicting both the popular narrative and, on Figel's account, his own crewmate's recollection of events Carlson was reportedly present for. A case where the strongest documented anomaly (the missile hardware failure) is essentially uncontested, but the human testimony explaining it is contested from within its own witness pool rather than only from outside skeptics, is precisely the kind of case this site's "Disputed" rating exists to describe honestly rather than force toward a cleaner verdict than the record supports.

Sensor & Instrumentation Detection Profile

Malmstrom is fundamentally a testimony-and-telemetry case rather than a radar-visual one, and the two data streams never fully overlap. The "sensor" record that is genuinely solid is the missile wing's own automated status telemetry: Echo Flight's ten launch facilities registered "No-Go" indications on their strategic-alert status displays nearly simultaneously at 0845 hours on March 16, 1967, a hardware event recorded in the 341st Strategic Missile Wing's own unit history and and by the Engineering Investigation Team's report of 23 March 1967. The 801st Radar Squadron at Malmstrom reported no radar or atmospheric interference problems related to Echo Flight. Separately, and less rigorously documented, notes by researcher Warren Mahoney place a low object on FAA radar from 3:42 to 4:26 AM on March 25, and other secondary accounts describe an unidentified target in the Great Falls area that night, and two F-106 interceptors reportedly scrambled toward it, with the object said to disappear from view as the jets approached and reappear once they departed. This file treats that radar-and-interceptor detail as a secondary, less independently verified claim rather than an established fact on the same evidentiary footing as the missile telemetry, since the strongest primary sources for it are researcher compilations rather than a surviving, citable radar log. No gun-camera, photographic, or FLIR data of any kind exists for either flight's object.

Environmental & Geospatial Context

Both incidents occurred on the high, exposed wheat-and-cattle plains of Cascade County, Montana, where Malmstrom's Minuteman flights were dispersed across dozens of miles of rural farmland, each unmanned launch facility separated from its Launch Control Facility by several miles of unpaved access road. Echo Flight's shutdown at 0845 occurred in daylight; the 341st Strategic Missile Wing's own unit history states that "weather was ruled out as a contributing factor in the incident," directly foreclosing one obvious conventional explanation. Oscar Flight's reported overnight encounter and the Belt, Montana landing report both occurred in the dark, in the isolated, sparsely populated terrain that made Malmstrom's dispersed missile field notoriously difficult for security patrols to monitor continuously — a geospatial reality independent of anything anomalous.

Observer Credibility & Occupational Profile

The case's witness base is unusually credentialed for the UAP field: every primary witness at both flights was an active-duty U.S. Air Force officer or enlisted security specialist performing an assigned nuclear-alert function, not a chance civilian observer. Robert Salas, a 1964 Air Force Academy graduate, and his crew commander Fred Meiwald were qualified missile combat crew officers entrusted with the physical launch keys for ten armed intercontinental ballistic missiles; at Echo Flight, Eric Carlson and Walt Figel held the same qualifications. This credentialing cuts in two directions at once, which is precisely what makes the case genuinely disputed rather than simply corroborated: the testimony describing the object comes from trained, security-cleared professionals, though recorded decades after the event; but the flat, direct denials offered by some of those same officers — Carlson in particular, and Figel in his later statements — carry equal institutional weight, rather than being dismissible as an untrained or unreliable account. Civilian witness Ken Williams, by contrast, was an ordinary truck driver with no known connection to the base, and his report near Belt was investigated by base UFO officer Lewis Chase through the standard Project Blue Book field process.

Physical & Material Assays

No physical trace evidence connected to any object has ever been recovered from either flight. What was materially documented and physically inspected was the missile hardware itself: the investigating engineers, including Boeing's Robert Kaminski, tested cabling, logic couplers and power systems at Echo Flight; laboratory tests reproduced the same No-Go indications by injecting noise pulses into the logic coupler, but no source for such a pulse was found at Echo Flight. Kaminski later wrote that "there were no significant failures, engineering data or findings that would explain how ten missiles were knocked off alert." At the Belt, Montana site, three sheriff's deputies found freshly broken twigs and branches consistent with Ken Williams's account of a landed object, with no cattle in the area, though nothing positively attributed the damage to anything else; Lt. Col. Lewis Chase's report on the site nonetheless concluded with "negative results."

Historical Precedents & Archive Matches

Malmstrom sits at the founding center of an entire sub-genre of UAP research — the "UFOs and Nukes" pattern this site catalogs in depth on its dedicated theory page — alongside later incidents at Minot AFB (October 1968), F.E. Warren AFB (October 2010), and the United Kingdom's Rendlesham Forest (December 1980), where a UAP was reported near a NATO tactical nuclear weapons storage area. It also sits inside a smaller, specifically Montana pattern: Great Falls, adjacent to Malmstrom, was already the site of one of the earliest and most-analyzed motion-picture UFO records in history, Nick Mariana's August 1950 film, and the region logged a cluster of UFO reports on the night of March 24–25, 1967, including the landed-object report near Belt, the date Salas later attached to the Oscar Flight shutdown. Within the broader institutional archive, Malmstrom occupies an unusual position similar to the Kinross Incident: a real, officially documented hardware anomaly whose Air Force investigative paper trail is fragmentary, contested, and has never definitively closed the loop between the missile failures and the UFO reports filed on the very same shifts.

Material Analysis

Malmstrom's material record is split between two very different kinds of physical evidence, neither of which points conclusively toward or away from an exotic explanation. The missile hardware itself was the subject of a genuine, hands-on forensic engineering investigation: the OOAMA, Boeing, Autonetics and 15th Air Force task group inspected cabling, logic couplers and support equipment at Echo Flight, tested for commercial power and transformer faults, reproduced the No-Go indications in the laboratory by pulse injection, and arrived (in OOAMA's view) at an EMP or electrostatic noise mechanism without identifying its specific source — a rigorous negative result rather than an absence of investigation. By contrast, no physical trace evidence connected to any hovering object has ever been recovered at either flight. The one site with physical ground evidence at all is the Belt, Montana landing report, where sheriff's deputies and a highway patrol officer documented freshly broken tree branches and disturbed brush, explicitly ruling out livestock as the cause but never positively attributing the damage to anything else before Project Blue Book closed the case with "negative results."

The Conventional Explanation Candidate: Electromagnetic Pulse or Electrostatic Interference

The explanation closest to an official Air Force position, and the one with the strongest contemporaneous documentary support, holds that an unidentified electromagnetic pulse or electrostatic discharge — whether from a natural source, a hardware defect in the Minuteman I logic coupler system, or a nearby unannounced military test — induced a false shutdown signal across Echo Flight's logic control circuits. It deserves serious weight because it is the actual, physically tested conclusion of the 1967 engineering investigation (in OOAMA's words, a cause "of the Electro Magnetic Pulse (EMP) noise or electrostatic nature"), whose laboratory tests reproduced the same No-Go indications, rather than a later reinterpretation, and because early Minuteman I control and guidance systems are independently documented to have had real vulnerabilities to electrical noise and interference during this period of the program's development.

Where the EMP/Electrostatic Explanation Falls Short

Its central weakness, then and now, is that no one has ever identified a specific, verifiable source for the pulse. The 1967 investigation stopped at "EMP noise or electrostatic nature" and "some type of adverse power effect" without naming a source; no declassified document surfaced by this file's research specifies a nearby test, storm, or hardware defect responsible. The Wall Street Journal's June 2025 report of an unannounced electromagnetic-pulse device test, attributed to unnamed sources, would finally supply that missing source if accurate — but it conflicts with former AARO deputy director Timothy Phillips's separate 2025 interview remarks blaming a transformer failure and electrical storm, an inconsistency that undermines confidence in either version as a settled, verified answer rather than another still-provisional guess six decades after the fact.

The Transformer Failure/Electrical Storm Theory

A second, more recently offered candidate holds that a "cascading transformer failure" triggered by an electrical storm caused the Echo Flight shutdown. This candidate is attractive to AARO's broader mandate because it requires no unexplained military hardware and no UAP involvement at all. It is contradicted, however, by the primary documentary record this file has been able to review: the 341st Strategic Missile Wing's declassified unit history states that weather was ruled out as a contributing factor and that commercial power switching was not the cause, and the one documented transformer short in the area (on the line to site E-3) happened in the afternoon, about six hours after the 0845 shutdown; simulating it produced no significant noise.

A caveat on the competing 2025 explanations: this case is a rare instance where the institutional caution this site applies broadly to government UAP explanations is demonstrated directly by the record rather than argued from general principle — the Wall Street Journal's EMP-test account, attributed to unnamed sources, and former AARO deputy director Phillips's transformer-failure remarks are mutually inconsistent, and the transformer version is contradicted by the unit's own declassified history. Neither has been published as an official AARO finding. That two different explanations from or attributed to government insiders surfaced within the same year, one of which conflicts with the primary documentary record, is treated here as concrete evidence that a government resolution is one input to weigh rather than a final word, not as proof the missile shutdowns were themselves anomalous.

Witness Misperception, Conflation, and Institutional Confusion

A third candidate, favored by skeptics including James Carlson and, in a more measured form, podcaster Brian Dunning, holds that the missile failures were a real but purely conventional hardware event, and that the UFO narrative attached to them is the product of decades of imprecise retelling, memory drift, and the genuine, demonstrable conflation between the Echo and Oscar Flight incidents that this file's own research had to carefully untangle. This candidate is strengthened by the fact that the case's documented flight, Echo, is also the one whose 1967 history calls the UFO rumors "disproven" and whose crew commander denies any UFO was reported, and by Salas's own move of his account from Echo to Oscar Flight; it is weakened by the fact that it does not, on its own, explain Figel's detailed 2008 taped account of Security Alert Team reports, nor the Project Blue Book files documenting a genuine regional cluster of UFO reports on the same night as the Oscar Flight shutdown.

Related Cases

Further Reading — Recommended Literature

DISCLOSURE: Some links above are affiliate links. If you purchase through them, OverClassified receives a small commission at no additional cost to you. This helps support independent research.

Essential Viewing

Sources

• "Malmstrom UFO incident," Wikipedia (comprehensive incident summary with citations, including the 341st Strategic Missile Wing unit history excerpts and 2024–2025 AARO statements). en.wikipedia.org
• "Malmstrom Air Force Base," Wikipedia (base and 341st Missile Wing institutional history). en.wikipedia.org
• "Robert Hastings (ufologist)," Wikipedia (biography, research history, and the 2010 National Press Club event). en.wikipedia.org
• "Robert Salas," Wikipedia (biography, military service, and post-Air Force career). en.wikipedia.org
• National Investigations Committee on Aerial Phenomena (NICAP). "Malmstrom Missile Incident, March 16, 1967." nicap.org
• NICAP. "Malmstrom AFB Missile/UFO Incident, Mar 16, 1967" (document archive). nicap.org
• CUFON (Computer UFO Network). "Malmstrom AFB Missile/UFO Incident, March 1967" (personnel names, Boeing investigation team, and witness quotes). cufon.org
• UFO Evidence. "The Malmstrom Air Force Base UFO/Missile Incident." ufoevidence.org
• Project Black Echo. "Malmstrom Close Encounter Reports: Echo Flight, Oscar Flight and the 1967 Missile-UFO Debate." projectblackecho.com
• The UFO Chronicles. "The Echo and Oscar Flight Incidents: UFOs Disabled American ICBMs" (2012). theufochronicles.com
• The UFO Chronicles. "The Echo/Oscar Witch Hunt" (2010, Figel/Carlson dispute). theufochronicles.com
• The UFO Chronicles. "Echo Flight UFO Incident Not Unique: Retired Col. Frederick Meiwald Says 'Bright Object' Also Sighted During Oscar Flight Missile Malfunctions" (2011). theufochronicles.com
• The UFO Chronicles. "The Echo Flight UFO Incident: James Carlson is Still Wrong After All These Years" (2013). theufochronicles.com
• The UFO Chronicles. "UFOs at Missile Base: AARO Deputy Director Misstates Facts" (August 2025; Marik von Rennenkampff letter via Robert Hastings, unit-history contradiction analysis, with Phillips's quoted interview remarks). theufochronicles.com
• The Hill, via Yahoo News. "Opinion: Did the Pentagon spread false UFO stories? We're skeptical" (July 3, 2025; critique of the Wall Street Journal's June 6, 2025 EMP-test report). yahoo.com
• Exonews. "Doubts Cast on 1967 Malmstrom AFB UFO Incident" (James Carlson's skeptical case summarized). exonews.org
• Randle, Kevin D. "A Different Perspective: The Belt, Montana UFO Sighting and the 'Attack' on Echo Flight" (2023). kevinrandle.blogspot.com
• Metabunk. "UFOs at Nuclear Weapons Sites (Salas, Malmstrom, Eagle Flight) — Skeptical Resources" (community-compiled skeptical source archive). metabunk.org
• All-domain Anomaly Resolution Office (AARO). "Report on the Historical Record of U.S. Government Involvement with UAP, Volume I" (2024), via Wikisource. en.wikisource.org
• PR Newswire. "Former USAF Officers to Present Evidence of UFOs Tampering with Nuclear Weapons" (October 2021 press conference announcement, Salas quoted on the Oscar Flight/March 24, 1967 date). prnewswire.com
• PR Newswire. "The UFO-Nukes Connection Press Conference: Military Witness Affidavits and Declassified Documents Are Now Available Online" (2010 press-kit materials). prnewswire.com
• Fox News. "Aliens Are Monitoring Our Nukes, Worry Ex-Air Force Officers." foxnews.com
• OverClassified. "UFOs & Nuclear Weapons" theory page (site cross-reference; Echo/Oscar Flight timeline and related nuclear-site cases). omniledger internal
• Wikimedia Commons. "Launch Control Facility after construction at Malmstrom AFB, Montana.jpg" (U.S. Air Force photograph, public domain, source for this file's hero image). commons.wikimedia.org
• Hastings, Robert L. UFOs & Nukes: Extraordinary Encounters at Nuclear Weapons Sites, AuthorHouse, 2008 (revised 2017).
• Salas, Robert, & Klotz, James. Faded Giant: The 1967 Missile Shutdowns at Malmstrom Air Force Base, BookSurge Publishing, 2005.
• Clark, Jerome. The UFO Encyclopedia, 4th Edition, Relevant Information LLC (Malmstrom AFB incident entry).
• 341st Strategic Missile Wing, unit histories, January–December 1967 (Echo Flight Incident), released to FOIA requester 14 June 2001, via The Black Vault. theblackvault.com
• Dunning, Brian. "The Day the UFO Deactivated the Nukes," Skeptoid (Figel and Carlson 2010 replies; Belt date). skeptoid.com
• Randle, Kevin D. "The Belt, Montana UFO Sighting and the ‘Attack’ on Echo Flight," A Different Perspective, 3 March 2023 (Chase letter, deputies, teletype, Craig notes).
• Good, Timothy. Need to Know: UFOs, the Military, and Intelligence, Pegasus Books, 2007 (nuclear-site intrusion cases).

Corrections (October 2026)

This page was checked in October 2026 against the 341st Strategic Missile Wing unit histories released under FOIA in 2001, the Belt case material quoted by Kevin Randle, Brian Dunning's Skeptoid episode, Robert Salas's published accounts and contemporary reporting. Corrected or added: the unit history's statement that UFO rumors around Echo Flight "were disproven," which the page had omitted while presenting the guard report as part of the event; the absence of any released record of an Oscar Flight shutdown, and Figel's and Carlson's 2010 statements that Oscar Flight had no problem; Salas's 1996 placement of his experience at Echo Flight (the page said his account "never deviated"); the investigating agency (Ogden, not Oklahoma City, Air Materiel Area); the source of the "EMP or electrostatic" wording (OOAMA, not the Boeing report) and the report's date (23 March 1967); the laboratory reproduction of the No-Go indications; Kaminski's quote (a later letter, not the report); the December 1966 A Flight shutdowns; the Belt sighting's time (about 9:00 PM on March 24, not the early hours), its distance from the base, and Lt. Col. Chase's "no equipment malfunctions" statement; the claim that the "numerous reports" teletype contradicts statements about Echo Flight (it concerns March 24–25); and the skeptical Mars proposal. Removed as unverified: the "precursor" February 1967 Chester reports, a June 17 Mick West interview date, the claim that the device in the Wall Street Journal report was "not proposed until 1971," a 357-page length for Carlson's work, an unsourced Eric Carlson quotation, the Oscar Flight location "near Roy," and a 20–40 minute duration.

Following this review, the rating was changed from Disputed 62 to Disputed 42 (October 26, 2026), because the higher rating had rested partly on claims corrected or removed above.