Echo Flight: Ten Minuteman ICBMs Disabled at Malmstrom AFB

On 24 March 1967, all ten Minuteman I ICBMs at Echo Flight, Malmstrom AFB, Montana, dropped offline simultaneously. Security guards on duty reported a glowing airborne object near the missile sites in the minutes before the shutdown. A near-identical event reportedly occurred later that morning at Oscar Flight. No electromagnetic fault was ever reproduced. Former Air Force officer Robert Salas has testified about the incident before Congress. The Air Force attributed the shutdowns to a logic coupler failure; the cause of that failure has never been definitively established.

On 24 March 1967, all ten Minuteman I intercontinental ballistic missiles at Echo Flight — a launch control facility within Malmstrom Air Force Base, Montana — dropped from operational alert status within seconds of each other. No conventional malfunction accounted for the simultaneity. Security guards on duty had, minutes earlier, called the launch capsule to report an unidentified glowing object in the sky above the missile complex.

The incident remains one of the most extensively documented intersections between UAP activity and nuclear weapons infrastructure in the historical record.

What Was Reported

Echo Flight was one of five flights of the 341st Strategic Missile Wing, each controlling ten Minuteman I ICBMs dispersed across a wide area of the Montana high plains. Crew Commander Captain Eric Carlson and Deputy Crew Commander Lieutenant Walt Figel were on alert duty in the underground launch control capsule on the morning of 24 March 1967.

Beginning at approximately 0845 local time, the flight’s missiles began dropping off alert status in rapid succession. Within a matter of seconds to minutes — accounts differ on the precise interval — all ten ICBMs reported a “No-Go” condition on Figel’s display. The specific fault code indicated a problem in the Guidance and Control System’s logic coupler, which managed arming and launch enable circuits. Ten simultaneous identical failures were not a condition the system was designed to produce.

Before the shutdown sequence began, Figel later told investigators that at least one security guard at one of the remote missile sites had called the capsule to report seeing an unidentified disc-shaped or circular object in the sky near that site. Figel’s own recollection of what weight he gave the report at the time has varied across decades of interviews.

Later that morning, accounts suggest a comparable event occurred at Oscar Flight, another launch control facility in the same wing. Captain Robert Salas was the Deputy Crew Commander. By his account, a security guard telephoned him from the launch control facility perimeter to report a glowing red oval-shaped object hovering over the main gate, and that a second guard had been injured during the incident. Shortly afterward, Salas says, Oscar Flight’s missiles also began dropping off alert — again a No-Go condition across the flight. Salas has maintained this account consistently in published interviews and under sworn testimony.

Whether Echo Flight and Oscar Flight represent one incident or two that morning remains a point of contention between Salas’s account and the recollections of some former Air Force personnel.

Witnesses

Military personnel involved fall into two categories: capsule crew and topside security.

Capsule crew — Captain Eric Carlson (Flight Commander) and Lieutenant Walt Figel (Deputy Crew Commander) were in the Echo Flight capsule. Both are Air Force officers who held nuclear weapons release authority. Figel has spoken to multiple investigators over the years; his statements on the UAP element have been characterized as acknowledging that a guard reported something anomalous but have stopped short of personally endorsing a UAP explanation. Carlson, who later became a general officer, has given statements to his son James Carlson — who became a prominent skeptic of the Salas account — indicating that he recalls no UAP involvement and attributes the shutdowns to an equipment fault.

Security personnel — Site Security Controllers at Echo Flight’s dispersed LFs (launch facilities) reported aerial observations to the capsule. The names of most security guards involved have not been definitively established in public record, in part because raw security logs from that day have not been fully released under FOIA.

Oscar Flight personnel — Captain Robert Salas (Deputy Crew Commander) is the primary public witness. He went public in the early 1990s after seeing a documentary about UAPs at nuclear facilities. He has stated that his flight commander, Captain Frederick Meiwald, was present in the capsule and was awakened by Salas during the incident. Meiwald has reportedly confirmed to investigators that the shutdown occurred, though his characterization of the UAP element has been more measured.

Raymond Fowler — A civilian investigator for NICAP, Fowler investigated the Echo Flight incident and associated reports shortly after they occurred, collecting testimony from base personnel. His findings were filed with NICAP and constitute one of the earliest structured civilian investigations of the case.

Official Response

The Air Force launched a formal technical investigation immediately following the Echo Flight shutdown. Boeing, the prime contractor for the Minuteman system, sent engineers and technical representatives to Malmstrom. The investigation eventually attributed the fault to an inadvertent signal that propagated through the logic coupler in the Guidance and Control System — in effect, a spurious voltage that caused the missiles’ No-Go circuits to activate.

The critical point, which the Air Force investigation acknowledged and which subsequent analysts have returned to, is that the technical team was never able to reproduce the fault under controlled conditions. A spurious signal of the kind described would require a common-mode cause — something that triggered all ten missiles simultaneously and identically. No electromagnetic phenomenon consistent with known equipment failure was identified as the source.

The incident was documented in the 341st Strategic Missile Wing’s official history for 1967, an excerpt of which was later obtained through the Freedom of Information Act by researcher Robert Hastings. That excerpt acknowledges the Echo Flight shutdown but does not discuss any UAP element in the official record; the security guard reports appear in separate documentation that has been only partially released.

The Air Force did not formally link the shutdown to any unidentified aerial object in any declassified document.

In the 2023 House Oversight Subcommittee hearing on UAP — one of the most prominent Congressional UAP proceedings since the issue re-entered mainstream political discussion — Salas submitted testimony and spoken statements describing the Oscar Flight incident as context for the broader pattern of UAP activity near nuclear weapons infrastructure. His testimony was entered into the Congressional record.

Mundane Explanations Considered

Logic coupler fault without external cause — The official Air Force/Boeing conclusion. A transient electrical fault propagated through the guidance system interfaces and triggered simultaneous No-Go conditions across the flight. The mechanism is technically plausible; logic couplers in early Minuteman systems were known to have sensitivities to spurious signals. The problem is causation: what produced the spurious signal, and why no subsequent fault has ever been reproducible. This explanation is incomplete rather than impossible.

Electromagnetic interference from a ground-based source — If a powerful radio-frequency emitter were operating near the flight at the time, it could theoretically have induced a fault signal. No such emitter was identified. The Cold War context makes a Soviet-origin EMP or electromagnetic jamming exercise a theoretical candidate, but no intelligence evidence has ever been cited for it.

Scheduling or maintenance variance — Skeptics, including James Carlson, have argued that the “simultaneous” nature of the shutdowns has been exaggerated and that staggered faults across ten missiles within a maintenance cycle could be misremembered or misrepresented as simultaneous. The 341st SMW history excerpt does not provide exact timing data for each individual missile’s No-Go event, leaving the strict simultaneity question partially unresolved.

Security guard misidentification — The most parsimonious explanation for the UAP reports from topside security is that guards seeing Venus, an aircraft navigation light, or another conventional aerial object in the predawn Montana sky misidentified it under the stress of an active alert situation. This remains plausible for the perimeter sighting reports. It does not resolve the missile shutdown mechanism.

The Salas account is contested — James Carlson — son of Flight Commander Eric Carlson and himself a researcher who has devoted substantial effort to debunking the Salas narrative — argues that Salas has conflated and embellished a conventional equipment failure into a UAP incident over three decades of public retelling. Eric Carlson told his son directly that he witnessed no UAP activity and that the shutdown was equipment-related. Walt Figel has given statements to investigators that James Carlson characterizes as contradicting Salas’s account in material ways. The Council notes this dispute is genuine and long-running; it does not affect the factual baseline that ten missiles went offline simultaneously, which is independently documented. It does affect any claim that UAP were the direct cause.

Open Questions

• What produced the initiating spurious signal? The Boeing investigation never established an electromagnetic source consistent with a simultaneous ten-missile No-Go.
• What did Echo Flight security personnel observe? The full security logs for 24 March 1967 have not been released in unredacted form.
• What is the relationship between Echo Flight and Oscar Flight on that morning? Were they independent events, or part of a continuous episode? Classified records may resolve this.
• Do the Department of Energy materials released through the PURSUE program — which include documentation of UAP incidents at nuclear facilities between 2018 and 2021 (Case #00489) — indicate any comparable pattern of UAP-adjacent system anomalies in the contemporary nuclear security enterprise?
• The All-domain Anomaly Resolution Office (AARO) has received historical UAP reports through its legacy case review. Whether Echo Flight appears in AARO’s historical review database, and how it is rated, has not been publicly disclosed. The AARO FY2025 report (Case #00471) does not address the case by name.

The Council’s Verdict

Inconclusive.

The factual core of Echo Flight is not in serious dispute: ten Minuteman ICBMs at Malmstrom AFB dropped offline simultaneously on 24 March 1967, and the Air Force investigation never identified a reproducible cause for the initiating fault signal. Those facts are established by official records obtained through FOIA.

What is in dispute is whether a UAP was causally involved. The eyewitness accounts of perimeter security guards — filtered through decades of partial declassification, inconsistent on-record statements, and genuine conflict between primary witnesses — do not individually carry sufficient weight to conclude that a UAP was present and active. Salas’s account of Oscar Flight is consistent and has been given under testimony, but is contested by the recollections of others who were present, and the Council cannot resolve that testimonial conflict without additional documentation.

The case is most accurately characterized as a genuine anomaly in the operation of a nuclear missile system, with a claimed UAP association that is plausible on the available evidence but not established beyond reasonable doubt. The simultaneous ten-missile shutdown remains unexplained by the official investigation’s own standard. That is an honest “inconclusive” — not a dismissal, and not a confirmation.

The pattern claim — that UAP have shown a recurring interest in nuclear weapons facilities since at least the late 1940s — is a broader argument that the Malmstrom incident cannot prove or disprove on its own. Assessed cumulatively with similar reported incidents at Minot AFB, Loring AFB, and other nuclear-capable installations documented by Hastings and others, the pattern is at minimum a legitimate research hypothesis. It warrants systematic investigation rather than reflexive dismissal.

For context on the continuing relevance of UAP at sensitive installations, see Case #00489 (PURSUE Release 1, which includes Department of Energy nuclear facility UAP records from 2018–2021) and Case #00041 (the Nimitz encounter, which established the modern credibility threshold for military UAP reports).

Sources

1. Robert Hastings, UFOs and Nukes: Extraordinary Encounters at Nuclear Weapons Sites (2008). Hastings conducted multi-decade interviews with missile crew personnel and obtained key FOIA documents, including the 341st SMW history excerpt.
2. Robert Salas & James Klotz, Faded Giant (2005). First-person account of Oscar Flight with contemporaneous documentation assembled by Salas and Klotz.
3. NICAP case file, Raymond Fowler investigation (1967). Filed at nicap.org/670324dir.htm.
4. 341st Strategic Missile Wing Organizational History, 1 January–30 June 1967 (FOIA release via Robert Hastings).
5. U.S. House of Representatives, “Unidentified Aerial Phenomena: Exposing the Truth,” House Oversight Subcommittee on National Security hearing, 26 July 2023. Congressional record includes Salas testimony.
6. Citizens Hearing on Disclosure, Robert Salas testimony, Washington D.C., 29 April–3 May 2013.