The Malmstrom record contains a documented missile-system outage at Echo Flight on 16 March 1967 and Robert Salas's later account of a different event at Oscar Flight. A flight was a group of missiles monitored from a launch control centre. Official histories follow the Echo investigation through successive electrical tests; later witness statements describe reported sightings and operational responses. Their comparison depends on preserving which event each source addresses and whether a participant saw an object, received a report or investigated a malfunction.
Oscar Flight launch officer whose later account combines received guard reports and console observations
Robert Salas
What Salas personally experienced and what he was told
In his signed July 2010 affidavit, Salas places himself on duty at Oscar Flight on or about 24 March 1967 as deputy missile combat crew commander. He describes receiving telephone calls from the flight security controller above ground: first about manoeuvring lights, then about a red, glowing object near the front gate. His location below ground distinguishes his direct experience of the calls from the controller's reported visual observation.
Salas states that he briefed commander Frederick Meiwald and that console alarms and fault indications then showed all or nearly all ten missiles disabled. He also recalls security indications at launch facilities and a dispatched team's subsequent sighting report. These are his remembered operational sequence and received reports. The affidavit does not provide the original console log, guard statements or a recorded common time reference proving a physical link between the sighting and the faults.
His affidavit describes a later briefing by his squadron commander and an Air Force Office of Special Investigations officer, including instructions not to discuss the incident. That account is a retrospective claim about the response, rather than an inspected briefing record or independently authenticated secrecy document.
In his August 2010 essay, Salas explains that he initially associated his experience with the declassified Echo incident, then identified his own flight as Oscar. He also corrects his earlier belief that the two shutdowns occurred on the same day. The essay states that all ten Oscar missiles failed, while the affidavit uses the less definite all-or-nearly-all formulation. These distinctions preserve the wording and development of his recollection instead of treating the later narrative as an unchanged 1967 statement.
Evidence review
Salas supplies a direct account of received calls and perceived console conditions, recorded decades after the event. His stated corrections materially affect the relationship between his testimony and the official Echo record: documentation of Echo cannot simply be relabelled as documentation of his duty at Oscar.
The affidavit's signature and notarisation establish a formal personal statement, not independent verification of every remembered detail. His account supports examination of the claimed sequence; it does not by itself identify the reported object or establish that it caused a missile fault.
Statement and reporting history
March 1967: duty period described in Salas's later account.
On or about 24 March 1967: date assigned to Oscar in his 2010 affidavit.
July 2010: Salas signs the inspected two-page affidavit.
August 2010: Salas publishes his explanation of the Echo/Oscar and same-day corrections.
Both full-size affidavit images, salas_01.jpg and salas_02.jpg, visually read from the host's linked scans. Received reports and console experience distinguished. Signature and notarial form do not independently establish the narrated events; no private address or birth details reproduced.
Full substantive first-person essay read. Displayed posting date 21 August, copyright date 19 August. Flight and date corrections attributed to Salas; statements he says other witnesses made are not treated as their independently examined statements.
Original official history excerpt in an 88-page released packet; PDF pages 7, 13-14 and 21 visually read. PDF page 7 records event time and alert loss; page 21 retains the initial unresolved assessment and further-test plan. The Black Vault's interpretive introduction is not used as primary evidence.
Unnamed security personnel whose reports reach the record through officers and a targeting-team member
Malmstrom security guards
The guards' reported observations and their transmission
For Oscar, Salas's affidavit attributes the first calls to his flight security controller. It places other guards outside during the later reported observation but does not identify them or provide their separate statements. The controller's estimates and description therefore reach the public through Salas. A minor hand injury is also mentioned; Salas explicitly states that it was not caused by the object.
Robert Jamison's signed 2010 affidavit supplies another route by which security reports circulated. He recalls a non-commissioned officer confirming a UFO report before the missile malfunction, and later conversations with security-team guards. Those conversations document what he says he was told; the guards remain unnamed and their descriptions were not separately elicited in the inspected material.
For Echo, Robert Hastings's published interview page includes an excerpt attributed to Walter Figel, in which he recalls a guard reporting a large, round object over a launch facility while he initially suspected the guard was joking. The excerpt distinguishes receipt of a report from Figel's reaction to it. The interview page also contains the interviewer's summaries and interpretations; these do not provide direct access to the original guard's words.
The official Echo history records a different investigative position: it says UFO rumours were disproven and then describes questioning a Mobile Strike Team that had checked November Flight's launch facilities on the morning of 16 March. The team reported no unusual activity or sightings. That is a negative report recorded in the official investigation history, with a stated location and inquiry scope. It is not a published interview with every guard later mentioned in Echo or Oscar accounts.
Evidence review
The existence of a reported sighting and the observation described by that report require different checks. Several later officers repeating a security report can preserve its circulation without supplying several independent visual observations. The unnamed collective cannot be assigned a verified number, common position or agreed object description.
The history's negative report deserves comparison with the later testimony, but the scope matters. A November Flight team's account cannot settle every later claim about another post, and the later guard narratives cannot establish a continuous unidentified-object presence across separate flights.
Statement and reporting history
16 March 1967: date of the November Flight team check described in the Echo investigation history.
March 1967: security reports retrospectively associated with the separate Echo and Oscar accounts.
2010: Salas and Jamison record their accounts of received security reports.
4 June 2011: displayed publication date of Hastings's Figel interview page.
Both full-size affidavit images, salas_01.jpg and salas_02.jpg, visually read from the host's linked scans. Received reports and console experience distinguished. Signature and notarial form do not independently establish the narrated events; no private address or birth details reproduced.
Both full-size affidavit images, jamison_01.jpg and jamison_02.jpg, visually read. His restart activity, received briefings, date inference and explicit lack of a UFO sighting kept separate. Original work orders, dispatch log and newspaper item used for his dating were not examined.
Published page and selected directly quoted exchange read; displayed posting date 4 June 2011. The excerpt records a received guard report and Figel's sceptical reaction. Embedded 2008-2010 audio recordings were not auditioned; host commentary and interview summaries are not represented as a complete verified transcript.
PDF page 14, printed page 38, visually read. The history's conclusion is retained with its stated team inquiry and location. Original individual questioning records and a complete guard roster were not examined.
Launch and targeting personnel with operational access distinct from visual sighting claims
Malmstrom missile crews
Operational records and the targeting-team account
The unit history records all ten Echo launch facilities losing strategic alert nearly simultaneously at 08.45 on 16 March 1967, with channels 9 and 12 indicating No-Go conditions. In this context, No-Go meant the missiles were unavailable for their operational alert role. The history records their return to alert without launch-facility equipment replacement. It documents an operational failure; it does not record a missile launch or the destruction of the weapons.
Jamison's affidavit identifies his role as a Minuteman I targeting-team commander who restarted missiles after shutdowns. He recalls being called to work late at night, a delay before dispatch, a briefing about UFO reports and subsequent work at Oscar. He expressly states that he did not see any UFOs himself. His direct contribution concerns the response and restart activity, while the alleged aerial event reaches him through briefings and conversations.
Jamison links the night to a reported landing near Belt in the following day's newspaper and believes it was 24 March 1967. That retrospective date inference has a different basis from the official Echo event time. His affidavit also recalls a later, separate India Flight problem; it cannot be counted as another direct observation of the Oscar object.
Meiwald's presence and actions are described by Salas, and Figel's receipt of an Echo guard report appears in the published interview excerpt. Original operational logs and a complete set of separately recorded crew statements were not examined for this comparison. Statements that Salas says other people made are not silently substituted for those people's own complete testimony.
Evidence review
The official Echo history and Jamison's later targeting account address operational access through different records and dates. Combining them into one verified shutdown with a single cause would erase the distinction between a recorded outage and a retrospectively described response at another flight.
Restart work and fault indications can establish a problem in missile readiness without identifying its external cause. A targeting officer's report of a briefing is relevant to what personnel were told, while his explicit lack of a sighting limits its role as visual corroboration.
Statement and reporting history
16 March 1967, 08.45: official history records the Echo loss of strategic alert.
March 1967: period associated with Jamison's later Oscar restart account.
1967-1968: official history excerpts follow the Echo investigation through successive testing phases.
July 2010: inspected Jamison affidavit records his recollection of targeting work and briefings.
Original official history excerpt in an 88-page released packet; PDF pages 7, 13-14 and 21 visually read. PDF page 7 records event time and alert loss; page 21 retains the initial unresolved assessment and further-test plan. The Black Vault's interpretive introduction is not used as primary evidence.
PDF pages 35-39, 47-50, 53 and 76-77 visually read, including pulse testing, rejected signal path, later susceptibility work and continued testing. No new calculation or experimentally identified source of the original disturbance is asserted. Complete 88-page packet not read.
Both full-size affidavit images, jamison_01.jpg and jamison_02.jpg, visually read. His restart activity, received briefings, date inference and explicit lack of a UFO sighting kept separate. Original work orders, dispatch log and newspaper item used for his dating were not examined.
Both full-size affidavit images, salas_01.jpg and salas_02.jpg, visually read from the host's linked scans. Received reports and console experience distinguished. Signature and notarial form do not independently establish the narrated events; no private address or birth details reproduced.
Published page and selected directly quoted exchange read; displayed posting date 4 June 2011. The excerpt records a received guard report and Figel's sceptical reaction. Embedded 2008-2010 audio recordings were not auditioned; host commentary and interview summaries are not represented as a complete verified transcript.
What the engineering record establishes
The initial Echo investigation did not determine a satisfactory cause and proposed further contractor testing. Subsequent histories show that the investigation continued. They examine the logic coupler, an electronic component involved in the fault indications, and distinguish potential electrical inputs from the source and path by which such an input might have reached all the sites.
The later record reports that a deliberately applied short pulse at the coupler's self-test command line reproduced the relevant No-Go response. This was a test result, not a recording of a pulse striking the operational missiles on 16 March. A proposed route through the Sensitive Information Network was investigated and rejected. Simulated power disturbances also failed to reproduce the operational shutdown. The record therefore supports a demonstrated circuit susceptibility while leaving important parts of the original causal sequence unresolved.
Further passages discuss electromagnetic-pulse and electrostatic hypotheses, later tests and proposed protective modifications. The late-1967 material describes negative results from the adverse-power testing and further work expected into 1968. Those stages prevent treating an early statement of uncertainty as the investigation's final word. They also prevent describing the packet as proof that an unidentified craft emitted an electromagnetic pulse: the technical term names a proposed type of disturbance, not an identified object or intentional action.
Hastings's published summary of his January 2009 Figel interview also attributes to Figel continued scepticism that a second shutdown occurred at Oscar. This is the interviewer's presentation rather than an independently checked recording. It documents disagreement within the later participant record and prevents treating the officers' accounts as one agreed reconstruction.
The principal evidential separation remains between Echo's documented outage, the subsequent engineering work and Salas's Oscar narrative. The official history's treatment of rumours and later received-report testimony differ in their sources and scope. Neither institutional status nor later sworn form resolves that difference automatically. Establishing a UFO-related cause would require evidence connecting a particular observed source to the fault mechanism and event, beyond coincidence asserted in retrospective accounts.
Key dates
16 March 1967, 08.45
Echo loses strategic alert at ten launch facilities, according to the unit history.
On or about 24 March 1967
Date Salas assigns to the separate Oscar account in his 2010 affidavit; Jamison's later date inference is separately explained.
March 1967
Initial Echo investigation examines fault indications and proposes further contractor work.
April-June 1967
Later history describes power tests and pulse injection reproducing the coupler's No-Go response.
Later 1967
Continuing investigation reports a rejected signal-path hypothesis, additional susceptibility testing and no complete determination of the original disturbance.
Late 1967-early 1968
The packet records further electromagnetic-effects testing and continuing work rather than a demonstrated UFO mechanism.
June 2001
Air Force release letter identifies the quarterly history excerpts supplied in the inspected packet.
July-August 2010
Salas and Jamison's signed statements and Salas's corrective essay enter the public source history.
Original official history excerpt in an 88-page released packet; PDF pages 7, 13-14 and 21 visually read. PDF page 7 records event time and alert loss; page 21 retains the initial unresolved assessment and further-test plan. The Black Vault's interpretive introduction is not used as primary evidence.
PDF page 14, printed page 38, visually read. The history's conclusion is retained with its stated team inquiry and location. Original individual questioning records and a complete guard roster were not examined.
PDF pages 35-39, 47-50, 53 and 76-77 visually read, including pulse testing, rejected signal path, later susceptibility work and continued testing. No new calculation or experimentally identified source of the original disturbance is asserted. Complete 88-page packet not read.
Both full-size affidavit images, salas_01.jpg and salas_02.jpg, visually read from the host's linked scans. Received reports and console experience distinguished. Signature and notarial form do not independently establish the narrated events; no private address or birth details reproduced.
Full substantive first-person essay read. Displayed posting date 21 August, copyright date 19 August. Flight and date corrections attributed to Salas; statements he says other witnesses made are not treated as their independently examined statements.
Both full-size affidavit images, jamison_01.jpg and jamison_02.jpg, visually read. His restart activity, received briefings, date inference and explicit lack of a UFO sighting kept separate. Original work orders, dispatch log and newspaper item used for his dating were not examined.
Published page and selected directly quoted exchange read; displayed posting date 4 June 2011. The excerpt records a received guard report and Figel's sceptical reaction. Embedded 2008-2010 audio recordings were not auditioned; host commentary and interview summaries are not represented as a complete verified transcript.