Wing 04 · UFOs & Disclosure · Caught on Camera: Legendary Cases

Malmstrom AFB 1967: Ten Missiles Went No-Go, and the UFO Account Belongs to the Other Flight

At 0845 on March 16, 1967, all ten Minuteman I missiles at Echo Flight, Malmstrom Air Force Base, Montana, dropped off alert with No-Go indications. That is not folklore. The time, the flight and the No-Go indications are the Air Force's own wording, the cause was traced to electronic noise pulses reaching the logic coupler units in each launch facility, and a then-SECRET contractor investigation replicated the failure and concluded that no satisfactory explanation for the missile disabling was found. The whole flight was back on alert in about a day. Here is what the 1967 record does not contain: an object. The famous glowing red thing over the gate belongs to a different flight about a week later, and it reaches us as testimony, from one man, a former deputy missile combat crew commander named Robert Salas, who went public with it in 1996. Echo Flight has a paper record with no UFO in it. Oscar Flight has a UFO account with almost no paper record. Nearly every telling of this case welds the two together with the word similar. This one takes them apart and shows you the seam, including the 1967 record's own answer and the very different explanation attributed to the Pentagon in 2025, 58 years apart.

CASE I_3_12 Reliability: The Echo Flight shutdown is documented (Tier 1); the UFO account is testimony, and it belongs to a different flight. 15 sources

Tier 1 · Verified Tier 2 · Credible Tier 3 · Speculative Tier 4 · Dubious

Start with the seam, because everything in this case runs along it. On one side there is a documented failure of ten nuclear missiles, recorded by the United States Air Force in its own operational history and investigated by the contractor that built them. On the other side there is a glowing red object over the gate of a launch control facility, described decades later by a former missile officer. Both of those are real things. They are not the same kind of thing, and at Malmstrom they are not even the same flight.

Here is what this dossier will not do. It will not use the word similar to walk you quietly from one to the other. Our own research file does exactly that in its opening summary, and that one word performs the work of an argument nobody has actually made. So this page keeps four kinds of claim visibly apart: what a document establishes, what a named person states, what the Air Force has itself said the cause was, and what anyone has inferred on top of those. Read the tier tags below, and read the kind too, because in this case the kind is where the entire fight lives.

01The Morning Of March 16, 1967

That is our research file's wording. The record's own wording, as reproduced in the public archives, is narrower and better, and it is worth having in front of you: 'On 16 March 1967 at 0845, all sites in Echo (E) Flight, Malmstrom AFB, shut-down with No-Go indications,' and the launch facilities in E Flight 'lost strategic alert nearly simultaneously.' Two differences matter. The record supplies a clock time, 0845, that our file does not carry at all. And it says nearly simultaneously rather than within approximately 10 seconds; the 10-second figure is our file's own characterisation and was not found in the primary wording located for this page.

Ten missiles is one flight, not a wing. The 341st Strategic Missile Wing was reassigned to Malmstrom on July 15, 1961, the first Minuteman I arrived by rail on July 23, 1962, and the wing became fully operational with 150 Minuteman I missiles on July 3, 1963, which makes Echo Flight one of fifteen such flights. What went off alert that morning was a fifteenth of a wing, dispersed across the Montana prairie, and during the Cold War that was already a serious national security event before anyone said the word object.

Read that claim twice, because of what it does not say. It identifies the mechanism, a noise pulse reaching the coupler, and it says nothing whatever about what generated the pulse. Every argument anyone has ever had about Malmstrom lives inside that gap. Follow-on Air Force testing found the Minuteman I most vulnerable at exactly that point, the Logic Coupler in the Missile Guidance Set, and the recommended fix was a system-wide installation of pulse-suppression filters through Engineering Change Proposals. That is a historical engineering fact about a weapon system retired long ago, and this page says nothing at all about the missiles on alert today.

Again our file summarises where the document is sharper. The contractor investigation was issued as a then-SECRET Boeing document titled 'Report of Engineering Investigation of Echo Flight Incident, Malmstrom, Mont - 16 Mar 1967,' and the conclusion quoted from it in the public archives is a single flat sentence: 'No satisfactory explanation for the missile disabling was found.' That is the strongest documented statement in this entire case, and notice how modest it is. It is not a statement that something extraordinary happened. It is a statement that the people best placed to find an ordinary cause looked, and did not find one, and wrote that down.

Keep that one. It is going to come back twice before this page is finished, once on each side of the argument, and watching a single fact change sides is the most instructive thing in the whole file.

One honest limit on all of the above. This page has not read those originals. It has read secondary reproductions and direct quotations of them, two of which agree word for word, and our own file gives no document number, no release date and no archive call number for any of it. The documents demonstrably exist and are partly public. Nobody writing this page has held one.

Malmstrom is also not a ruin, and the tone of everything that follows should account for that. Today the 341st Missile Wing, under Air Force Global Strike Command, operates 150 Minuteman III intercontinental ballistic missiles across a missile field covering roughly 23,500 square miles of central Montana. The base runway was decommissioned in 1996 and helicopter operations continue in support of the missile mission. This is a story about a working installation, told about a morning fifty-nine years ago.

02What The 1967 Record Says About Objects

Almost everyone who writes this case up, including our own research file, presents the official record as silent on the UFO question. It is not silent. It is negative, and it says so out loud. The contemporaneous Air Force record states: 'Rumors of Unidentified Flying Objects (UFO) around the area of Echo Flight during the time of the fault were disproven.' It records that a Mobile Strike Team which had checked launch facilities on the morning of March 16, 1967 was questioned, and stated that no unusual activity or sightings were observed.

Our file does not contain that line anywhere, and its absence is the largest hole in it. A page that tells you the record is merely unexplained, while leaving out the sentence in which the record refuses the UFO connection by name, is misleading you by omission even if every word it prints is true.

Now weigh the sentence properly, because it cuts less deeply than it first looks. It is an official position rather than an established fact: the record asserts that the rumours were disproven, and it does not show the work. It rests on questioning one strike team. And it is about Echo Flight, which is precisely the flight where nobody has ever placed an object anyway. On the thing it actually addresses, it is the Air Force's own contemporaneous answer, and it is a no.

That sentence is the most valuable in the file, and it is buried in the middle of the file's own supportive section. Our library, arguing for the case, concedes that at Echo Flight there is no single human being who saw an object and saw the missiles fail. The documented event and the reported object are joined by nothing but the fact that they are in the same article.

03The Other Flight, And The One Man Who Carries It

Every clause of those two claims is Salas states. There is no document behind any of it that this page could find. The attribution is not politeness and it is not a hedge; it is the actual epistemic situation, and our own file's opening summary drops it, writing the object into plain narrative as though a record had reported it. The entire nukes-and-UAP thesis rests on the sequencing in the second claim, an object first and the No-Go indications after, and it rests on it as one man's memory of one night.

The dating comes from the same channel. Robert Hastings, the researcher who has done most to promote the case, places the Oscar Flight event on the evening of March 24, 1967, eight days after Echo, on the basis of information from Robert Jamison. Our file says only approximately one week. Both are compatible; only one of them can be checked against anything.

The first half of that needs one qualification, and it comes from the case's own advocates rather than from any critic, which is exactly why it is safe to state plainly. Salas's first public account appeared in the Great Falls Tribune in August 1996, about twenty-nine years after the events. By his own description and Hastings's, he initially believed he had experienced the Echo Flight incident, later wondered whether it had been November Flight, and settled the question in the summer of 1996 after locating his former commander Frederick Meiwald, who placed it at Oscar Flight. The content of what he describes has been consistent. The flight and the date he assigned it to were not, until he went and found the man who could tell him.

Meiwald is reported to corroborate the account while recalling six to eight missiles affected rather than ten. That difference is worth stating rather than smoothing over: two men remembering the same night in the same capsule do not agree on the number, which is ordinary for human memory at thirty years and is also exactly the sort of thing a written log settles in one line, if a written log exists.

Our file uses the word confirmed there, and the word does real damage. Jamison states this. A witness statement does not confirm anything; it is the thing that would need confirming. Hastings additionally reports that Jamison said he was briefed that UFOs had been involved before retargeting missiles, which is a researcher reporting a man reporting a briefing, and that is testimony at two removes.

Salas himself has not been quiet. Our file records appearances at the National Press Club in 2010 and 2013 and testimony submitted to congressional offices, and it lists his books: Faded Giant, written with James Klotz in 2005, and Unidentified in 2014, joined since by UAPs and the Nuclear Puzzle in 2023. One correction to the file's language. At a press club a person speaks; they do not testify. The September 27, 2010 event was verified independently for this page, the 2013 appearance was not, and the distinction between speaking at a press conference and testifying under oath is the whole subject of section 08.

04The Asymmetry, Which Is The Whole Case

Put the two flights side by side and the shape of the problem becomes impossible to miss. This is the comparison our file's opening summary collapses into the word similar, and it is the reason this page exists.

One more absence belongs in the comparison, and it belongs to both columns equally. There is no photograph of any of this. Not of Echo Flight, not of Oscar Flight, not of the object, not of the consoles on either night. The events happened underground and at unmanned silos in the dark, and they were classified. Any picture you have ever seen attached to this story is a picture of a missile, a museum, or a base, and a photograph of a Minuteman is not evidence that anything happened to a Minuteman.

05What Reaches Us Second Hand

The Echo Flight crew on duty that morning were Capt. Eric Carlson, the missile combat crew commander, and Lt. Walter Figel, his deputy. One capsule, one shift, two men. Their recollections do not match. Hastings reports that Figel described receiving a security guard's report of an object over one of the silos, and that Figel was later debriefed and told not to discuss the incident. Eric Carlson has stated that he does not recall any credible UFO reports during the shutdown or the debriefing.

This page does not adjudicate that, and nobody reading it is in a position to either. Notice instead the shape of it, because the shape is the lesson. Two officers sat side by side through the single most documented event in this case. Their accounts differ. And even the difference reaches us at second hand, through an interested party, from accounts that are themselves publicly disputed. That is what witness testimony is: not a weaker fact, but a different kind of object entirely, one whose reliability degrades through every hand it passes through.

The same channel explains something else. The dramatic version of Boeing's role, the one that circulates everywhere, is not in the engineering report. Hastings reports the account of Boeing missile engineer Robert Kaminski, who is said to have stated that UFOs were sighted near the launch silos, that his investigation found no conventional cause for the failures, and that the Air Force halted the investigation before a report could be filed. This page could not locate an independent primary source for that account. Set it beside the documented line, 'No satisfactory explanation for the missile disabling was found,' and you have two very different claims that our own file blends into one Tier 1 statement about what Boeing engineers concluded.

Our file goes one step further still and states that aerospace engineers who reviewed the Boeing logic coupler analysis found no conventional mechanism for simultaneous independent failures. It names no engineer, no review, no publication and no date, and the verification pass behind this page could not find one. It stays here as our file's unnamed assertion, and it is not being upgraded into a source.

06The Pentagon's Answer, 58 Years Later

In June 2025 the Pentagon's current position on Malmstrom became public through a Wall Street Journal article, 'The Pentagon Disinformation That Fueled America's UFO Mythology,' published June 6, 2025. It attributes the events to a Cold War electromagnetic-pulse test: a large electromagnetic generator, described as built near the front gate of the Oscar 1 launch control facility and mounted on a portable platform 60 feet above it, which when activated would gather power until it glowed, sometimes with a blinding orange light.

Look at what that explanation concedes before you look at what it explains. It accepts that something bright and orange was in the air near the Oscar facility. It identifies that thing as United States Government equipment, put there on purpose. This is an official position taken in 2025 about an incident the Air Force's own 1967 paperwork treated as an unexplained fault with the rumours disproven, and our research file, last updated in March 2026, does not mention it at all.

It has not been established, and this page will not present it as though it had. It is a position attributed to the Pentagon and reported by one newspaper, whose own text sits behind a paywall and was not read for this page. The newspaper gave no citation for a specific source document. Independent analysts working on the claim identified the relevant transportable EMP simulator programme documentation as the Defense Technical Information Center report on TEMPS, the Transportable EMP Simulator, whose final report volume is dated August 1973, six years after the incident. Be precise about what that does: it does not prove no earlier device existed, and it does establish that the specific documentation identified postdates the events it is being used to explain.

Robert Salas published a detailed point-by-point rebuttal. Among his arguments is one that should stop any reader who has been paying attention: a genuine electromagnetic pulse of the strength required would be expected to leave permanent damage, and the Malmstrom missiles were back on alert within about a day.

Watch what just happened to a single sentence from section 01. The missiles were restored within approximately one day. Our own file uses that fact to refuse a fringe claim, that the weapons were permanently disabled. The Pentagon's 2025 explanation runs into the same fact from the opposite direction, on Salas's argument, because an electromagnetic pulse powerful enough to knock Echo's ten hardened launch facilities off alert, if the 2025 explanation is meant to reach Echo at all, should not leave them repairable overnight. One documented outcome, cutting against the wildest version of the story and against the official version of it, in the same breath. That is what an actual piece of evidence looks like: it does not care whose side it is on.

And one observation offered as an observation, an inference and not a finding. Set the 2025 explanation beside the 1996 testimony and they put a bright object in roughly the same place, near the gate of the Oscar launch control facility. They disagree entirely about what it was. Nothing follows from that overlap on its own, but it is the reason this explanation is a genuine competitor to the anomalous one rather than a dismissal of it.

07The Pattern Argument

Our file grades that Tier 1 and this page does not, quite. Those five are reported sightings, which is testimony, and the file supplies no document for any of them. Treat the list as real, since these are the sites the literature names, and treat each individual case as entirely unexamined here. Naming a place is not the same as documenting an event at it.

The same file states that Soviet military records describe UAP encounters at nuclear missile sites in Ukraine and Kazakhstan, including a 1982 incident at Byelokoroviche where an object allegedly triggered a launch sequence initiation that was subsequently overridden. That framing did not survive checking. The Byelokoroviche account is dated October 4, 1982 and traces in every accessible source to a witness account, principally from a base radio operator named Vladimir Matveyev, circulated through post-Soviet television and UFO literature. No released Soviet military document was located. It is a witness account, which is a real thing, and it is not a record, which is what our file called it.

The largest collection of this material is Robert Hastings's. Our file credits him with testimony from over 150 former US military personnel; the figure his own organisers used publicly at the September 2010 press conference was more than 120 former or retired military personnel, and the number has grown across successive editions of his book. Either way, be clear what is being counted. That is a count of testimonies, not a count of incidents, and certainly not a count of documented events. A hundred and twenty people saying a thing is a hundred and twenty statements.

One genuine link outward, and only one, because it is already told properly elsewhere on this site. The Rendlesham Forest incident of 1980 occurred adjacent to RAF Bentwaters and RAF Woodbridge, bases widely reported to have housed US nuclear weapons; our Rendlesham Forest dossier carries that question in full. There is also a pattern of unexplained military hardware failures around these encounters, which our Tehran Intercept dossier owns, and which already names Malmstrom in passing. And one boundary worth drawing: March 1967 falls inside the operating years of Project Blue Book, but Echo Flight was handled through Strategic Air Command, Air Force Systems Command and the missile contractor. Do not go looking for a Blue Book file on it; nothing in our sourcing says one exists.

08A Press Conference Is Not A Hearing

The September 27, 2010 event that put this case in front of the public was a press conference at the National Press Club in Washington DC, titled UFOs and Nukes, organised by Robert Hastings with Robert Salas and streamed live by CNN. The participants named in the event's own release were Dwynne Arneson, a retired USAF lieutenant colonel and communications centre officer-in-charge; Bruce Fenstermacher, a former USAF nuclear missile launch officer; Charles Halt, a retired USAF colonel and former deputy base commander; Robert Jamison, a former USAF nuclear missile targeting officer; Patrick McDonough, a former USAF nuclear missile site geodetic surveyor; Jerome Nelson, a former USAF nuclear missile launch officer; and Salas himself.

That is a serious room, and Charles Halt's presence in it is a real thread rather than a coincidence, since he is the officer behind the memo at the centre of the Rendlesham case. It is also, precisely, a privately organised press conference at a private club. It was not a congressional hearing, no one in it was under oath, and describing it as testimony, as our file does, quietly upgrades what happened there.

That is the structurally strongest criticism of this case, and it is not an accusation against anybody's honesty. The 2010 statements, whatever the standing of the men making them, occurred without independent cross-examination and without access to original classified equipment logs. A press conference has no adversarial process. Nobody in the room could hand a witness a document and ask him to reconcile it with what he had just said, which is exactly the procedure that would settle the Oscar Flight question in an afternoon if the document existed.

09The Explanations On Offer

Our file's own counter-arguments section is unusually good, and it argues with itself rather than lining up one side. Critics, it notes, could explain the 1967 shutdown by electromagnetic pulse from atmospheric phenomena, or by design flaws in the early Minuteman I guidance systems. In the very next breath it supplies the counterweight: the simultaneous shutdown of ten independent missile silo control systems challenges any explanation requiring a single localized equipment failure. Both of those belong on the same page, adjacent, and neither is settled.

Where the file is weaker is in attribution. It says scholars remain skeptical that testimony provided decades later can be fully reconciled with the fragmentary FOIA record, and it names none. Real named people have made real named arguments, so here they are, with what each of them actually answers.

Now notice the column that is missing from that table. Not one of those four arguments explains what generated a noise pulse across ten dispersed launch facilities connected by hardened underground cables at 0845 on March 16, 1967. Sheaffer and Dunning are arguing about an object. West is arguing about the record. James Carlson is arguing about his father's crew. The Boeing report's open question sits exactly where it sat in 1967, untouched by any of them, and lacking contemporaneous written records that explicitly attribute the shutdown to anything, the official cause of the incident remains uncertain.

10What Would Have To Be True

Those last four words are our own file's, and they survive into this page unchanged, because this is the most emotionally attractive idea in the entire case and the one with the least behind it. It is also circular, and the circle is easy to see once you look. The reasoning takes the absence of permanent damage and reads intent into it. But the absence of permanent damage is equally, and far more commonly, the signature of an ordinary transient fault. A restraint that looks like a message is the same data as a fault that simply passed.

Unfalsifiable by construction, and our file names no personnel. State it as the claim it is: no source available to this page can test it, and no source available to this page can refuse it either. That is not a mystery, it is a dead end, and the difference matters.

There is one more consideration the file never raises, and it belongs here as reasoning rather than as evidence. Nuclear weapons sites in this era were among the most heavily instrumented, most continuously staffed and most rigorously log-keeping places in the United States. If anomalous things are reported more often near nuclear sites, that is exactly what a genuine attraction to nuclear weapons would produce, and it is also exactly what an observation bias would produce. Our file's own closing counter-argument puts it as a live question, and it stays live: whether nuclear sites are targeted as a deliberate technological demonstration, or whether the proximity is coincidental, is inconclusive.

Those two entries are not the same verdict and should never be read as one. The first is a flat no aimed at a fringe claim, and the documentary record settles it. The second is our file refusing an explanation for being inadequate rather than for being wrong, and it is aimed at the skeptical side, which is rarer and worth noticing. Read it carefully: it refuses the word routine, not the word technical. Something technical plainly happened at Echo Flight. Ten couplers do not stop on a rumour.

So what do you do with a case like this? You stop letting one column borrow the other's strength. At Echo Flight there is a record, a time, a mechanism, a contractor's report and an explicit official position, asserted on the record and never shown, that the UFO rumours were disproven. At Oscar Flight there is a detailed account from a named officer who went and found his old commander to be sure which flight he was on, and almost nothing on paper. Then in 2025 the Pentagon put its own bright object at the Oscar gate and called it a generator on a platform, and the newspaper that carried the claim named no document to support it, and the one fact that refuses the wildest version of this story, that everything was back on alert in a day, turns out on Salas's reading to cut against the official version too. Two questions are genuinely open, and both are the kind a reader could go and settle. Does the 341st Strategic Missile Wing unit history for March 1967 stop where the Boeing report stops, or does it name something the summaries have never quoted? And what document, exactly, does the 2025 explanation rest on, since the newspaper that carried it named none and the simulator documentation identified so far is dated 1973?