Malmstrom AFB Echo Flight missile shutdown (16 March 1967) under-corroborated
On 16 March 1967, all ten Minuteman I ICBMs of Echo Flight at Malmstrom
AFB dropped off strategic alert within seconds of each other. The
simultaneous shutdown is in the unit record; the Air Force's engineering
investigation attributed it to a noise pulse in the guidance-and-control
system, while former missile officers and security personnel have
testified that UAP were seen over the flight at the time — a connection
the corpus treats as documented at the hardware layer and contested at
the causal layer.
Echo Flight is the corpus's reference case for the nuclear-weapons /
UAP-correlation claim — the thesis (advanced by researcher Robert
Hastings and by former missileers including Robert Salas) that UAP have
repeatedly been reported in proximity to U.S. strategic nuclear assets,
sometimes coincident with system malfunctions. It is also the corpus's
cleanest study of how a real, documented technical event becomes a
contested UAP case: the shutdown is not in dispute; the official noise-
pulse explanation is credible; and the UAP connection rests on testimony
that has itself been challenged on the record by the family of the Echo
Flight commander. Holding all three of those true at once is the
analytical exercise.
Timeline
1967-03-16_early_morning
All ten Minuteman I missiles of Echo Flight go off strategic alert in
rapid succession, registering 'No-Go' / channel faults at the Launch
Control Center. The deputy crew commander on duty is 1st Lt. Walter
Figel; the crew commander is Capt. Eric Carlson. The simultaneous loss
of an entire flight is highly unusual and triggers an immediate
maintenance and security response.
witnesses: Capt. Eric Carlson (Echo Flight crew commander) · 1st Lt. Walter Figel (Echo Flight deputy crew commander)
primary source: Echo Flight unit history (declassified); Figel and Carlson interviews
1967-03-16
Maintenance and security teams are dispatched to the dispersed Launch
Facilities. In the accounts gathered by later researchers, some
topside security and maintenance personnel report observing unidentified
lights or objects over or near the missile sites around the time of the
shutdown. These reports are testimonial and were not, in the surviving
official documentation, recorded as the cause of the shutdown.
witnesses: maintenance and security personnel (named in later interviews) · Robert Jamison (Targeting Team officer, recalled UFO reports during the recycle of the missiles)
primary source: Robert Hastings, 'UFOs and Nukes' (2008); witness interviews
1967-03_following_weeks
A Boeing and Air Force engineering investigation is conducted. The
finding attributes the shutdown to a transient electrical noise pulse
coupling into the missiles' logic circuits — a phenomenon the engineers
were able to partially reproduce. This becomes the official cause of the
Echo Flight event and is the explanation the Air Force has maintained.
primary source: Boeing/USAF engineering analysis as cited in the unit history and by skeptical researchers
1967-03-24_to_25_approx
In the account of former 1st Lt. Robert Salas, a SEPARATE shutdown
occurs at Oscar Flight roughly a week later, during which security
guards report a glowing red object over the front gate of the Launch
Control Facility and the missiles begin failing as he is on the phone
with the topside guard. Salas originally placed this on 16 March but
later corrected the date to 24–25 March and the flight to Oscar. The
Oscar Flight event is not corroborated in the same documentary way as
Echo Flight, and is the single most contested element of the case.
witnesses: 1st Lt. Robert Salas (Oscar Flight deputy crew commander, by his own account)
primary source: Robert Salas and James Klotz, 'Faded Giant' (2005)
2005
Salas and James Klotz publish 'Faded Giant,' bringing the Echo/Oscar
Flight accounts to a wide audience and establishing the missile-shutdown
case as the centerpiece of the UFO-and-nukes literature.
primary source: Salas & Klotz, 'Faded Giant' (2005)
2010-09-27
Researcher Robert Hastings convenes a National Press Club event in
Washington, D.C., at which seven former U.S. Air Force officers,
including Salas, publicly describe UAP incidents at nuclear-missile and
weapons-storage sites. The event is the high-water mark of the
UFOs-and-nukes thesis in the public record.
primary source: National Press Club event, 27 September 2010; Hastings, 'UFOs and Nukes'
2010s
James Carlson, son of Echo Flight commander Capt. Eric Carlson,
publishes detailed rebuttals arguing that the documented cause was the
noise-pulse engineering fault, that his father and Figel reported no
UFO, and that the UAP connection is a later overlay. Figel himself has
given accounts that complicate the simple 'UFO caused it' narrative
(including an early report of a UFO over a site that he has at times
characterized as a maintenance man's joke). The case settles into a
documented-event / contested-cause stalemate.
witnesses: James Carlson (rebuttal author; son of Capt. Eric Carlson)
primary source: James Carlson published rebuttals; Figel interviews
Named personnel
- Capt. Eric Carlson — Echo Flight crew commander on duty, 16 March 1967 rank at time: Captain primary witness to: the simultaneous Echo Flight shutdown from inside the Launch Control Center
- 1st Lt. Walter Figel — Echo Flight deputy crew commander on duty, 16 March 1967 rank at time: First Lieutenant primary witness to: the shutdown; his recollections of contemporaneous UFO reports are partial and have been characterized inconsistently
- 1st Lt. Robert Salas — Oscar Flight deputy crew commander (by his own account); later the principal public witness rank at time: First Lieutenant · later: Co-author of 'Faded Giant' (2005); National Press Club witness (2010) primary witness to: the separate Oscar Flight shutdown (~24–25 March 1967) and the red object over the gate — the contested testimony
- Robert Jamison — Missile-maintenance / targeting officer at Malmstrom rank at time: primary witness to: UFO reports during the effort to bring the missiles back on alert
- Robert Hastings — Civilian researcher; author of 'UFOs and Nukes' (2008) rank at time: role: Assembled the broader nuclear-correlation thesis and organized the 2010 National Press Club event
- James Carlson — Rebuttal author; son of Capt. Eric Carlson rank at time: role: Leading on-record skeptic of the UAP connection, arguing for the noise-pulse engineering cause
Sensor record
- Minuteman I guidance-and-control / Launch Control fault telemetry on Echo Flight (10 Launch Facilities + 1 Launch Control Center) near-simultaneous 'No-Go' / channel faults registered at the LCC; the primary hard datum of the case documentation: Echo Flight unit history (declassified); the engineering investigation
- Topside human observation (security and maintenance) on Launch Facility and Launch Control Facility perimeters reports of lights / objects over the sites (testimonial; not in the contemporaneous fault record) documentation: Witness interviews collected decades later
Object — reported
shape
varies by account; Salas's Oscar Flight account describes a glowing red object; Echo Flight topside reports describe lights
size
not reliably estimated
surface features
none described in detail
observed behaviors
- in the contested Oscar Flight account, a red object hovering over the Launch Control Facility gate coincident with missiles dropping off alert
- no maneuvering or performance data of the kind recorded in the Navy sensor cases
- the central hard datum is the hardware event (simultaneous shutdown), not an object's flight behavior
Theories that invoke this case (5)
The mundane-but-significant reading: the shutdown was a real
electromagnetic-compatibility vulnerability in the Minuteman I G&C
system (the noise-pulse finding), of genuine national-security
interest independent of any UAP — and the UAP overlay is a later
misattribution.
The literal nuclear-interest reading: an external intelligence
demonstrating the ability to disable strategic nuclear weapons,
consistent with the broader UFOs-and-nukes correlation thesis. Depends
on accepting the contested topside testimony as causal.
The institutional-handling reading: the interest is in how the event
was investigated, documented, classified, and later reconstructed — the
production of the record across the 1967 engineering analysis and the
2005–2010 testimonial revival.
The skeptical-institutional reading: the UAP-and-nukes narrative is a
durable cultural construct that may be amplified for reasons unrelated
to any 1967 event; the case's evidentiary thinness at the causal layer
makes it a candidate for narrative overlay.
The reading that the documented hardware event acquired its UAP
meaning retroactively, through decades of retelling, witness
recruitment, and date-conflation (the Echo/Oscar merger), rather than
from contemporaneous observation.
Theories that do NOT invoke this case — and why
no associated perceptual phenomenology; the case turns on hardware telemetry and contested object reports, not anomalous experience
no entity sighting
no time-displacement element
Conventional explanations advanced — and their status
Electrical noise pulse coupling into the Minuteman I logic circuits (the official Boeing/USAF finding)
proponents: U.S. Air Force · Boeing engineering investigation · James Carlson
The corpus's accepted explanation for the Echo Flight shutdown itself. The engineers were able to partially reproduce the fault; the Minuteman G&C system had a documented EMC vulnerability. This accounts for the hard datum without invoking a UAP. It does not address the topside sighting reports, which it treats as unconnected or as later overlay.
Date and flight conflation (Echo vs. Oscar; 16 March vs. 24–25 March)
proponents: James Carlson · skeptical analysts
Salas's own correction of his original account (from Echo/16 March to Oscar/24–25 March) is the documentary basis for treating the dramatic 'red object' narrative as a separate, less-corroborated event from the well-documented Echo Flight shutdown. This is the corpus's reason for keeping the two layers apart.
Retrospective narrative construction (testimony gathered decades later)
proponents: psychosocial reading · skeptical researchers
Credible for the causal connection but not for the underlying shutdown. The Echo Flight event is contemporaneously documented; the UAP-causation claim depends on memory and interview material assembled 35+ years later.
Where further investigation has leverage
- Full declassification and independent review of the complete Echo Flight unit history and the Boeing/USAF engineering investigation, including whether the noise-pulse finding fully reproduced a ten-missile simultaneous fault.
- Any contemporaneous (March 1967) security-police blotter or maintenance logs recording topside object reports, which would move the UAP connection from decades-later testimony to same-day documentation.
- Independent corroboration of the Oscar Flight event from a witness other than Salas, with a documentary anchor (duty logs, fault records) fixing the date.
- An EMC engineering assessment of whether any external electromagnetic source (rather than an internal noise pulse) could plausibly have produced the observed simultaneous fault signature.
Corpus status
under-corroborated
Documented at the hardware layer, contested at the causal layer. The
simultaneous Echo Flight shutdown of 16 March 1967 is in the 341st SMW
unit history and has a credible, *reproduced* engineering explanation: the
Boeing/USAF investigation showed a noise pulse coupling into the Minuteman I
logic coupler (a known EMC vulnerability, later fixed fleet-wide with
filters), and the lab reproduced the shutdown signature in roughly 60% of
trials. Two facts weigh hard against UAP causation. First, the SAME unit
history that records the shutdown states that UFO rumors at Echo Flight
"were disproven" and that a Mobile Strike Team across the field saw no
unusual activity. Second, the UAP connection is entirely later testimony:
deputy commander Walter Figel confirms a security guard reported a round
object over a silo but says he took it as a leg-pull; commander Eric Carlson
flatly denies any UFO reports; and Robert Salas's dramatic "red object"
account belongs to a SEPARATE, date-corrected (24–25 March) Oscar Flight
event with no documentary paper trail (per skeptic Robert Sheaffer) that is
disputed on the record by James Carlson, the commander's son. The corpus
holds the event as real, the engineering cause as credible, and the UAP
causation as under-corroborated — declining to collapse the three, while
noting the contemporaneous record actively cuts against the UAP reading
rather than merely failing to support it.
status history (2)
2026-06-09 · unannotated → phenomenologically-open
— initial annotation sweep (Epic J.F4)
2026-06-14 · phenomenologically-open → under-corroborated
— Adversarial audit. Reconciled to the deep-dive status (the dive was already under-corroborated; historical_cases lagged at phenomenologically-open). The Echo Flight shutdown has a reproduced engineering cause (Boeing logic-coupler noise pulse, ~60% lab reproduction, EMC fix deployed); the unit history itself records UFO rumors "disproven" and a Mobile Strike Team seeing nothing; the UAP link is all decades-later testimony (Figel guard report he dismissed, Eric Carlson's denial, Salas's uncorroborated/date-shifted Oscar Flight). Documented event, under-corroborated causation.
Threads of evidence
This case is one node in the connections that run across the record. It appears in 1 thread: