UFOs Initiated Nuclear Missile Launch Countdowns Say Former U.S. Air Force Officers

By Robert Hastings www.ufohastings.com 12-15-14

     Since 1973, I have interviewed more than 150 U.S. military personnel regarding their UFO experiences at nuclear weapons sites. CNN streamed my September 27, 2010 press conference, at which seven of those veterans appeared, and the video may be viewed below:

As noted in my last article, dramatic testimony recently provided to me by a former U.S. Air Force Minuteman missile launch officer, who wishes to remain anonymous, reveals that UFO activity at ICBM sites is not confined to the temporary shutting down of the missiles but also, in his case, the unauthorized activation of the launch-countdown sequence in them—an ominous and terrifying prospect.

But this was not the first time I had been told, by a former nuclear missile launch officer, that a UFO had initiated the launch sequence in one or more ICBMs. The following material is excerpted from my 2008 book UFOs and Nukes: Extraordinary Encounters at Nuclear Weapons Sites:

Of all the tape-recorded interviews I’ve conducted with former or retired ICBM launch officers over the past three decades, this was perhaps the most disturbing. According to the source, former U.S. Air Force Captain David H. Schuur, a UFO once activated the launch sequence in most of his Minuteman missiles.

In August 2007, Schuur told me, “I saw your request for information in the [June 2007] Association of Air Force Missileers Newsletter. I was involved in a UFO incident at Minot AFB in the mid-1960s. I had read your earlier article [in the September 2002 AAFM Newsletter] but was hesitant to respond.” I asked Schuur why he had been hesitant. He replied, “Well, we were basically told, way back when, that it was classified information and, you know, it didn’t happen and don’t discuss it. I guess I was still operating on that idea when I saw your first article.”

Schuur had obviously had a change of heart. He continued, “Anyway, I was a Minuteman missile crewmember in the 455th/91st Strategic Missile Wing at Minot from December 1963 through November 1967. I was a 1st Lieutenant during that period and the deputy commander that night. Since the incident occurred some 40 years ago, my memories are a bit foggy but, based on who my commander was at the time, I would say it occurred between July 1965 and July 1967.”

“As far as the incident, here’s my best recollection of it: Alpha capsule, which was east of us, reported on PAS—the Primary Alerting System—that their security personnel were observing a large, bright object hovering over some of their missile sites. It was moving from missile to missile. I think the Alpha missile crew also reported that they were receiving ‘spurious indicators’ on their missile control console, but I’m not certain about that. I do know that a few minutes later our own capsule had spurious indicators—anomalous readings—from some of our missiles.”

Schuur continued, “But it wasn’t just Alpha and Echo. Over the next hour or so—I don’t recall exactly how long it was—all of the flights reported that their [Security Alert Teams] were observing a UFO near their facilities. The path of the object could be followed as it passed over each flight area by the reports on the PAS. The object moved over the entire wing from the southeast to the northwest, following the layout of the wing.”

“As far as our flight, Echo, a few minutes after hearing the report from Alpha, I received a call from topside security that a large bright light—actually, a large, bright object would be more accurate—was in the sky, to the east of the launch control facility. When the guard called down, he may have used the term ‘UFO’ but I don’t recall. He didn’t describe its shape or altitude because it was too far away. It never got close enough to the LCF to see any detail. At its closest, it was two, three, maybe four miles away from us, near one of the missile sites.”

Schuur continued, “However, when the object passed over our flight, we started receiving many spurious indications on our console. The object was apparently sending some kind of signals into each missile. Not every missile got checked [out] by the object, but there were several that did. Maybe six, seven, or eight. Maybe all ten got checked, but I don’t think so. As this thing was passing over each missile site, we would start getting erratic indications on that particular missile. After a few seconds, everything reset back to normal.”

“But then the next missile showed spurious indicators so the object had apparently moved on to that one and did the same thing to it. Then on to the next one, and so on. It was as if the object was scanning each missile, one by one. The Inner Security and Outer Security [alarms were triggered] but we got those all the time, for one reason or another. However, on this particular night, we had to activate the ‘Inhibit’ switch because we got ‘Launch in Progress’ indicators! After a few minutes, the UFO passed to the northwest of us and all indicators reset to normal.”

I wanted to be certain about what I had just been told. I asked Schuur, “So, if you get a ‘Launch in Progress’ indicator, does that mean the launch sequence has been triggered—that the missile is preparing to launch?” Schuur replied, “That means the missile has received a launch signal. When that happens, we get an indication in the capsule that a launch command has been received by that missile. If that happens, without proper authority, you flip what’s called an ‘Inhibit’ switch, to delay the launch for a given period of time. If an Inhibit command comes in from another launch capsule, that shuts down the launch totally. But if that second command doesn’t come in, the missile will wait for a specified period of time and then launch automatically at the end of that expired period—theoretically. Of course, that night, we had all kinds of other indicators coming on from each missile so, in that situation, the launch probably would have aborted itself. I honestly don’t know.”

I asked Schuur if the “Launch in Progress” indicator had ever been triggered on any other occasion, either before or after the UFO incident, while he was on alert duty. He replied, “No, never.”

I asked Schuur if he had heard about missile maintenance teams having to replace components or whole systems in the affected missiles—the ones that generated the spurious readings. He replied, “No, if that happened, I never heard about it.”

Schuur said, “Upon returning to the base the next day, my commander and I were met by the operations officer. He just said, ‘Nothing happened, nothing to discuss, goodbye.’ Our logs and tapes were turned in. Every capsule had a 24-hour tape that, as I recall, recorded the communications that went over the PAS system, so all the reports would have been on that tape. But we were essentially told that nothing had happened that night and to discuss it no further. It was a non-event. We were never debriefed by OSI or anyone else. We just went home. Most of the returning missile crews drove back to the base from their facilities, so they all arrived at different times. There was no group debriefing that I know of. I never heard another thing about the incident.”

I asked Schuur, “I know that you were given no feedback from your superiors, but what is your personal assessment of the event?” He replied, “Oh, I think something was up there, uh, scanning the missiles, seeing what was going on. Some kind of a scanning process.” I asked Schuur whether he thought the launch activation had been incidental or deliberate. He seemed surprised by my question and said, “I think that the scanning just set it off. It set all kinds of things off, we were getting all sorts of indicators. There were some kind of signals being sent [from the UFO] to the missile that inadvertently triggered the launch activation, but I don’t think it was deliberate. I hope not! That would have been—.” Schuur didn’t finish this sentence. His voice broke and he heaved a deep sigh. Apparently, the thought that those aboard the UFO might have deliberately attempted to launch his nuclear missiles that night had caused him to pause—and probably shudder—over 40 years later.

I obviously accept Schuur’s report as credible, but am of course attempting to locate other former members of his squadron who are willing to corroborate it. As Schuur candidly admitted, after reading my first article in the September 2002 AAFM newsletter, he waited some five years before approaching me. It was only after my second published request for information from former/retired USAF missileers that he decided to unburden himself. This hesitant response is not atypical. Many of my former missile launch officer sources have not readily or easily divulged their UFO experiences to me, for one reason or another.

More UFOs At Minot AFB in 1967-68

In 2005, I posted a series of messages on the Yahoo missile_talk group’s bulletin board, summarizing the testimony of former and retired USAF sources who had reported their UFO-related experiences at various nuclear missile sites over the years. My hope was that some of the group’s members, largely made up of U.S. Air Force missileers, would be encouraged to come forth and discuss their own experiences. A few of them, including Larry Manross, did just that. He wrote:

Robert, you are right on. As a launch crew commander at Minot AFB from 1966-1970, I will tell you that there were UFO incidents. In one [during which I was present] the security team upstairs went into a defensive posture with lights turned out. They had called in a UFO sighting to the base and radar was tracking it. All of a sudden it buzzed the launch control center and that was when they cut the lights and took a defensive position.

The details are fairly slim on the incident [but it occurred sometime during] 1967 or ’68. It was treated by the Air Force as a non-incident. In other words, no report was asked for from the missile crew. I am not certain if the security team made a report, but the whole thing made you feel somewhat uneasy. But base ops did confirm that they were tracking an unidentified object on radar.

I asked Manross to elaborate on these statements. He responded:

I was in the 742nd [Strategic Missile Squadron]. The capsules we manned were Kilo, Lima, Mike, November, and Oscar. I was primarily assigned to Kilo or Lima. I do not remember the name of the senior officer during that [alert] assignment; he was not the usual commander I was assigned with. He was several years older than I and was a career officer, I believe. I was never assigned with him again and don't remember much about him. He may have been in a different squadron. Sometimes they mixed and matched us when they were having scheduling problems.

The year was ’67 or ’68, before I moved up to the commander role. I was attempting to sleep while the commander was dealing with security upstairs and the base headquarters regarding some unidentified [flying] object. It was when his [missile status console] lit-up like a Christmas tree for a moment that he got scared and asked for back-up. The lit-up board had signaled that the missiles had launched. It was a false signal but correlated with the incident taking place upstairs. It all happened quite fast. Then things returned to normal.

[Anyway,] that was when I became engaged. The commander was rattled and so was the security team upstairs. They reported that something had buzzed the LCF and that they had gone into a defensive posture, turning out the lights and drawing their weapons. They indicated it was very bright and traveling at a high rate of speed. They did not describe any shape, etc., other than it was bright. [Then] base headquarters reported that the unidentified object was no longer on radar and that was the last we heard of it.

There was no debriefing—nada. Just another day pulling an alert at Minot. I do remember the senior officer saying something about how I should not talk about the incident without getting authorization. [In spite of that,] all the officers talked about UFOs and what was going on. As you can imagine, there was quite a range of opinions. The common assumption among many [launch officers] was that the objects were somehow drawing power from the missile warheads.

The number of UFO incidents at the time, during 1966-’70, were so frequent that in the summer the security team sometimes would put chairs in front of the building, or on the roof of the building, to watch for UFOs. Can you believe it?

Regarding this last statement, I told Manross that I had heard nearly identical stories from other former or retired USAF personnel who had been stationed at Ellsworth, F.E. Warren, and Malmstrom AFBs during that era. This particular side show is almost humorous: Nuclear missile security guards sitting outside Minuteman Launch Control Facilities at night looking for UFOs because the objects appeared above the missile field so frequently! If only the American media had been given that story at the time. But, of course, like everything else relating to these classified incidents, almost no information leaked out to the press or public.

Purchase Robert's Book (click on book image)

Visit Robert's Site . . .

See Also:

UFO Activated One of his ICBMs—Twice, Says Former U.S. Air Force Missile Launch Officer

UPDATE/REBUTTAL To D'Antonio: UFO Activated One of his ICBMs—Twice, Says Former U.S. Air Force Missile Launch Officer

Malmstrom Air Force Base Picks Up UFO on Radar; "Sabotage Alert Team Located Another UFO Directly Over The Base"

UFO Buzzes ICBM Launch Capsule at Minot AFB

My Evidence: The Account of Minute-Man Missiles Being Disabled, While UFOs Hovered Over The Launch Facilities

REPORT YOUR UFO EXPERIENCE

UPDATE/REBUTTAL To D'Antonio: UFO Activated One of his ICBMs—Twice, Says Former U.S. Air Force Missile Launch Officer

Tweet

By Robert Hastings www.ufohastings.com 12-12-14

     Since 1973, I have interviewed more than 150 U.S. military veterans regarding their involvement in, or knowledge of, UFO incursions at nuclear weapons facilities. Those who have read my book, UFOs and Nukes, know that 98% of my sources are identified by name in it.

However, I was recently approached by a former U.S. Air Force captain, who wishes to remain anonymous for now, who related his participation in a very dramatic incident at Malmstrom AFB in 1974, involving the unauthorized launch activation of one of his Minuteman-II missiles—twice—apparently by those aboard a UFO hovering over it.

I possess this individual’s DD214, or service record, which verifies his nuclear missile launch officer status, at that base, during that year.

He told me, “This incident occurred sometime Between 01 Jan 74 and 30 Jun 74, and my best guess is in the March time-frame. I know this because of who my crew commander was during the event, and this is the time I was crewed with him.”

He continued:

I was at Malmstrom AFB Montana, a member of the 564th Strategic Missile Squadron, and that night I was on alert at Romeo Flight. The missile that activated was at Launch Facility Romeo-29.
It happened during the first shift of a 40-hour alert—I'd say between 20:00 and 22:00 hours (8:00 p.m. and 10:00 p.m.). There was no [missile] maintenance activity going on at the time, and I don't recall anything else out of the ordinary.

The event lasted more than 30 minutes but probably less than 90 minutes. There was a situation with Outer and Inner alarms going off. Outer means the security fence has been penetrated somehow; Inner means the missile silo itself has been compromised in some manner.

A Security Alert Team was dispatched. Upon arrival, the team reported a large self-illuminated object hovering over the Launch Facility. The light was so bright that the shape of the craft could not be determined.

Suddenly, [down in the launch control capsule], a launch enable / inhibit / no-go shutdown event took place. In other words, the missile went into countdown mode and was preparing to launch! I quickly flipped the Inhibit switch, which disrupted the missile-enabled status. Then we got a no-go shut down, which is what is supposed to happen. The launch system was offline.

This was extremely unnerving. I mean, that missile had been preparing to launch. I later learned where it had been targeted—its destination—and it was a major target. I don’t plan to discuss the specifics with you because I don’t want that information made public. Meanwhile, as all of that was happening, the Security Alert Team at the site indicated that the UFO was still hovering over it.
Just as my missile commander and I were collecting our wits and wondering what all of this was about—the object, the launch enable—we got a spontaneous restart, which shouldn’t have been possible after the no-go shutdown. Then [on our consoles] there came another launch enable, followed by another inhibit procedure—which didn’t work!

Now we were panicking. We watched the read-outs which proceeded to launch-commanded, launch-in-process, and all the way through missile-away! In other words, as far as we knew, the missile had left the launch facility and was heading to its target. We couldn’t believe it!

My commander quickly called the SAT team and asked whether the missile was airborne. They said, ‘No sir.’ So, in reality, the missile-away code was false and the missile was still in the ground. Then we finally got another no-go shutdown code.

Shortly after that, the team said that the UFO had left, straight up, at high speed. There was no noise. They also reported observing an F-106 interceptor flying in the squadron area and then unsuccessfully trying to intercept the object.

After-the-fact, it was learned that the object was tracked by weapons controllers in the 24th NORAD Region SAGE Center at Malmstrom AFB. They recounted that they could see the object on radar as well as the F-106's unsuccessful attempts to intercept it.

We also later learned that all of the ground electronics in the launch facility were ‘fried’ as though the system had been destroyed by a massive electrical surge.

The former launch officer then said, “A couple of years later, when I was stationed at NORAD headquarters in Colorado Springs, as a public information officer—an assignment I didn’t ask for or want—I was in the ‘approval-loop’ for an FOIA request about this incident.”

He continued, “I was surprised that part of the information which was being provided in response to the request was my crew log, with all of my handwritten notes, although much of the relevant information had been redacted. This means that NORAD was the apparent destination, at least one of them, for paperwork related to the incident.”

Two other former USAF Minuteman missile launch officers, Captains David Schuur and Larry Manross, had previously discussed with me their own involvement in very similar incidents at Minot AFB, North Dakota, in the late 1960s.

Moreover, documents smuggled out of Russia after the collapse of the Soviet Union by television investigative reporter George Knapp confirm that one such incident—a UFO-initiated, temporary missile activation-for-launch—occurred at an ICBM base in Soviet Ukraine, on October 4, 1982.

Consequently, in addition to the now-widely publicized UFO-related missile shutdown incidents—such as the Echo and Oscar Flight incidents at Malmstrom AFB, Montana, in March 1967—we now have a number of ICBM activations being reported by former nuclear missile launch officers—on both sides of the ocean during the Cold War era. Predictably, Washington and Moscow continue to remain silent about these dramatic and perhaps ominous disclosures.

UPDATE:

Shortly after I revealed this case on the Coast to Coast AM radio show (11/30/14), bloggers began discussing and dissecting it. One of them, MUFON’s chief photo and video analyst, Marc D’Antonio, skeptically challenged the scenario provided by the former missile launch officer, writing, “Was it confirmed to be OVER the silo and not possibly a distant object brightly lit in the sky and seen past the silo? If so it could have been mistaken as being OVER the silo especially at night where precious few reference points are available for observations. Was it possibly the moon seen through clouds and in the excitement mistaken for a bright UFO over the silo? Were the proximity alerts a malfunction which led to a security team seeking an ‘intruder’ and thus self-primed to ‘find one’ unconsciously?”

D’Antonio continued, “Was it possible that the F106 and the ‘bolting’ UFO were actually the same object misinterpreted? Missile folks and security personnel are not people who are trained to discern situations outside of their expected purview and this situation whether actual or mistaken was clearly outside all of their training regimen. Intruders on foot or in a helicopter they can manage. But if they thought that the light WAS over the silo and the other members agreed with the lead person who made that potential observation, then all of them would report as observed by the lead in all likelihood.

Could it have been the F 106 flying through clouds that night that caused them to mistake the light as a more nearby object entirely? Jet exhaust in [military] planes really lights up clouds. I have seen this personally quite a bit.”

At my request, my ex-U.S. Air Force source responded to this attempt to debunk the case:

I think Marc D'Antonio is overlooking or disregarding one key element of this situation, that being that the object over R-29 was visible on the radar scopes in the 24th NORAD Region SAGE Center (blockhouse) at Malmstrom AFB. Further, the controllers in the SAGE Center were directing the F-106 in pursuit of the object. Also, the F-106 pilot observed the object ‘bolting’ straight up.

The SAGE Center controller involved in this situation lived in my neighborhood on base and after this was all over, he commented to a friend of mine (who had been on alert at the adjacent Quebec Launch Control Center and watched this all take place) that the object definitely did not behave like any aircraft that NORAD was familiar with.

So no, the security team members weren't mistaking the F-106 for the object because the F-106 was scrambled to intercept the object after it appeared on radar in the vicinity of R-29. And while Mr. D'Antonio can discount the ability of us missile types to accurately discern flying objects, I don't believe he can make the same statement about a combat-qualified F-106 interceptor pilot.

In his critique, D’Antonio had also written, “Isn't it quite possible that the fried electronics could have actually occurred FIRST and subsequently caused all of the observed electrical malfunctions? The mistaken proximity alarms, the launch go-no-go, and the strange on/off sequencing, could all have been generated by a cascading systems failure that occurred beforehand.”

He continued, “This actually may be much more likely given electrical systems propensity for failure. Lest anyone think that these systems are bulletproof, search for the records of electrical maintenance and failure and you will be surprised to find how fragile our missile launch systems really have been. Given a failure-as-cause as potential, albeit of course unprovable at this point, the UFO sighting could have been a mistaken identity and would then be the only strangeness associated with the case.”

To which my ex-Air Force source responded:

The electronics that were ‘fried’ were the ground electronics in the launch facility which could have accounted for the MISSILE AWAY indication. I would go further and conjecture that this is what likely did cause the MISSILE AWAY display.

All of the other status reports, however, are generated and reported by the missile guidance computer. (Point of technical information: The missile guidance computer ‘runs’ the launch facility. That it, it monitors and reports status, responds to all commands for ground and missile tests and alignment sequences, etc. Of course, after launch, the guidance computer actually flies the missile to its target and then deploys the weapons.)

The missile guidance computer at R-29 was not damaged like the ground electronics. Further, the ground electronics have nothing to do with generating the launch-sequence commands and status, and, therefore, would not have the capability to falsely report on launch events. More importantly, the sequences and timing of all the launch indications were ‘spot-on’ to what would be reported in an actual launch for that particular sortie and the target for which it was set.

I would argue that if these indications were all a result of cascading electronics failure, they would be random. The statistical odds of a random equipment failure causing a 100-percent-accurate sequence of status-changes is astronomical. (It would be like putting a monkey in a room with a typewriter and having it produce a perfect copy of the Encyclopedia Britannica, or the collected works of Shakespeare!)

One final point: What we (the launch crew) observed at R-29 was totally isolated from the ‘unknown’ that NORAD detected and launched an interceptor on. We did not call NORAD; the F-106 appeared in the area while we were dealing with our security situation and the subsequent (false) launch indications. Two completely separate sequences of event—with the object over R-29 as the common element.

D’Antonio also wrote, “Who saw [this alleged UFO event] and where are they now? It's now public so they can speak...where is the F106 pilot, tower and crew who would recall chasing a UFO if that is in fact what happened?”

My own response to D’Antonio’s last comment involved pointing out that one demanding the appearance of corroborating witnesses—in any given decades-old UFO case—is easier said than done. While I am hopeful that the guards who participated in the incident will be made aware of the former launch officer’s recent candid remarks and subsequently come forward to add their own statements to the public record, the likelihood of even one of them learning about this development, and doing so, is low. Only rarely do such cases have multiple, corroborating witnesses.

(For example, in the March 24, 1967 full-flight missile shutdown incident at Malmstrom’s Oscar Flight, former Minuteman targeting officer Captain Bob Jamison has corroborated former launch officer Captain Bob Salas’ account of a UFO-involvement in the event. Jamison discussed his participation in the retargeting of those missiles during his appearance at my UFOs and Nukes press conference in 2010. A video of CNN’s live streaming of the event may be viewed at my homepage.)

One declassified USAF document discusses yet another case at Malmstrom, in November 1975, involving as many as seven UFOs maneuvering near ICBM sites, as well as the radar tracking of those objects—which hovered at times—before being chased from the missile field by F-106 fighters. In short, the newly-reported, dramatic event at Romeo Flight, in 1974, was only one of many such incidents, although reports of missile activations are still rare.

Marc D’Antonio is not the first—and will not be the last—skeptic to try to evaluate these cases in terms that they are comfortable with. At least he was attempting to raise legitimate questions, unlike those deluded debunkers who call the veterans who report the incidents “liars and frauds”.

Nevertheless, there are now so many of these nuclear weapons-related UFO cases on record that for skeptics to attempt to explain them all away as due to misidentified manmade aircraft or natural phenomena, or the result of fallible human perceptions, only demonstrates the degree to which they are in deep, deep denial.

Visit Robert's Site . . .

See Also:

MUFON’s Marc D’Antonio Questions UFO Activity at Nuke Missile Site

UFO Activated One of his ICBMs—Twice, Says Former U.S. Air Force Missile Launch Officer

Malmstrom Air Force Base Picks Up UFO on Radar; "Sabotage Alert Team Located Another UFO Directly Over The Base"

UFO Buzzes ICBM Launch Capsule at Minot AFB

My Evidence: The Account of Minute-Man Missiles Being Disabled, While UFOs Hovered Over The Launch Facilities

REPORT YOUR UFO EXPERIENCE

MUFON’s Marc D’Antonio Questions UFO Activity at Nuke Missile Site

By Marc D'Antonio The UFO Chronicles 12-12-14

     In our movie called UFOTOG Hasting's book was used as source material but it left me with some questions. I don't disbelieve Bob but I ask the questions science insists on.

For every statement in the story you link to for example there would be a trail of evidence and definitive observation from multiple sources.

For instance:

–Stmt: A security alert team saw a UFO hovering directly over the silo.

– Questions:

• Who saw it and where are they now? It's now public so they can speak.

• Was it confirmed to be OVER the silo and not possibly a distant object brightly lit in the sky and seen past the silo?

• If so it could have been mistaken as being OVER the silo especially at night where precious few reference points are available for observations?

• Was it possibly the moon seen through clouds and in the excitement mistaken for a bright UFO over the silo?

• Were the proximity alerts a malfunction which led to a security team seeking an "intruder" and thus self-primed to "find one" unconsciously?

–Stmt: . . . the security team said "the UFO left straight up at high speed."

– Questions:

• Could the sudden absence of an object in a scene where it was seen moments before be construed as an object bolting straight up?

Well I know this answer from direct example. Yes, we illustrated this on a National geographic special with a live demo showing how people perceive disappearance and reappearance of an object. In every case people felt the object bolted upward.

–Stmt: After the object was seen to "bolt" straight up an F106 was seen giving "chase."

– Questions:

• Was it possible that the F106 and the "bolting" UFO were actually the same object misinterpreted?

Missile folks and security personnel are not people who are trained to discern situations outside of their expected purview and this situation whether actual or mistaken was clearly outside all of their training regimen. Intruders on foot or in a helicopter they can manage. But if they thought that the light WAS over the silo and the other members agreed with the lead person who made that potential observation, then all of them would report as observed by the lead in all likelihood.

• Could it have been the F 106 flying through clouds that night that caused them to mistake the light as a more nearby object entirely?

Jet exhaust in mil planes really lights up clouds. I have seen this personally quite a bit.

• Since this is a public event now where is the F106 pilot, tower and crew who would recall chasing a UFO if that is in fact what happened?

–Stmt: They learned later the ground electronics were fried as if by a massive electrical surge.

– Questions:

• Isn't it quite possible that the fried electronics could have actually occurred FIRST and subsequently caused all of the observed electrical malfunctions?

The mistaken proximity alarms, the launch go-no-go, and the strange on/off sequencing, could all have been generated by a cascading systems failure that occurred beforehand. This actually may be much more likely given electrical systems propensity for failure. Lest anyone think that these systems are bulletproof, search for the records of electrical maintenance and failure and you will be surprised to find how fragile our missile launch systems really have been. Given a failure-as-cause as potential, albeit of course unprovable at this point, the UFO sighting could have been a mistaken identity and would then be the only strangeness associated with the case.

The above questions reduce the compelling stature of this case for me because the cascading failure that was indeed later found could likely have occurred FIRST and subsequently caused all electronic warnings and problems seen in the systems.

As I said before I am in no way saying Bob isn't reporting accurate information, I am just asking the tough questions because answers to such tough questions will elevate cases from a status of "interesting but unprovable" to "fascinating and compelling".

See Also:

UPDATE/REBUTTAL To D'Antonio: UFO Activated One of his ICBMs—Twice, Says Former U.S. Air Force Missile Launch Officer

UFO Activated One of his ICBMs—Twice, Says Former U.S. Air Force Missile Launch Officer

Malmstrom Air Force Base Picks Up UFO on Radar; "Sabotage Alert Team Located Another UFO Directly Over The Base"

UFO Buzzes ICBM Launch Capsule at Minot AFB

My Evidence: The Account of Minute-Man Missiles Being Disabled, While UFOs Hovered Over The Launch Facilities

REPORT YOUR UFO EXPERIENCE

UFO Activated One of his ICBMs—Twice, Says Former U.S. Air Force Missile Launch Officer

Tweet

By Robert Hastings www.ufohastings.com 12-6-14

     Since 1973, I have interviewed more than 150 U.S. military veterans regarding their involvement in, or knowledge of, UFO incursions at nuclear weapons facilities. Those who have read my book, UFOs and Nukes, know that 98% of my sources are identified by name in it.

Recently, however, I spoke with a former U.S. Air Force Captain, who wishes to remain anonymous for now, who related his participation in a very dramatic incident at Malmstrom AFB in 1974, involving the activation of the countdown sequence in one of his Minuteman-II missiles—twice—apparently by a UFO hovering over it.

I possess this individual’s DD214, or service record, which verifies his nuclear missile launch officer status, at that base, during that year.

He told me, “This incident occurred sometime Between 01 Jan 74 and 30 Jun 74, and my best guess is in the March time-frame. I know this because of who my crew commander was during the event, and this is the time I was crewed with him.”

He continued:

I was at Malmstrom AFB Montana, a member of the 564th Strategic Missile Squadron, and that night I was on alert at Romeo Flight. The missile that activated was at Launch Facility Romeo-29.

It happened during the first shift of a 40-hour alert—I'd say between 20:00 and 22:00 hours (8:00 pm and 10:00 pm). There was no [missile] maintenance activity going on at the time, and I don't recall anything else out of the ordinary.

The event lasted more than 30 minutes but probably less than 90 minutes. There was a situation with Outer and Inner alarms going off. Outer means the security fence has been penetrated somehow; Inner means the missile silo itself has been compromised in some manner.

A Security Alert Team was dispatched. Upon arrival, the team reported a large self-illuminated object hovering over the Launch Facility. The light was so bright that the shape of the craft could not be determined.

Suddenly, [down in the launch control capsule], a launch enable / inhibit / no-go shutdown event took place. In other words, the missile went into countdown mode and was preparing to launch! I quickly flipped the Inhibit switch, which disrupted the missile-enabled status. Then we got a no-go shut down, which is what is supposed to happen. The launch system was offline.

This was extremely unnerving. I mean, that missile had been preparing to launch. I later learned where it had been targeted—its destination—and it was a major target. I don’t plan to discuss the specifics with you because I don’t want that information made public. Meanwhile, as all of that was happening, the Security Alert Team at the site indicated that the UFO was still hovering over it.

Just as my missile commander and I were collecting our wits and wondering what all of this was about—the object, the launch enable—we got a spontaneous restart, which shouldn’t have been possible after the no-go shutdown. Then [on our consoles] there came another launch enable, followed by another inhibit procedure—which didn’t work!

Now we were panicking. We watched the read-outs which proceeded to launch-commanded, launch-in-process, and all the way through missile-away! In other words, as far as we knew, the missile had left the launch facility and was heading to its target. We couldn’t believe it!

My commander quickly called the SAT team and asked whether the missile was airborne. They said, ‘No sir.’ So, in reality, the missile-away code was false and the missile was still in the ground. Then we finally got another no-go shutdown code.

Shortly after that, the team said that the UFO had left, straight up, at high speed. There was no noise. They also reported observing an F-106 interceptor flying in the squadron area and then unsuccessfully trying to intercept the object.

After-the-fact, it was learned that the object was tracked by weapons controllers in the 24th NORAD Region SAGE Center at Malmstrom AFB. They recounted that they could see the object on radar as well as the F-106's unsuccessful attempts to intercept it.

We also later learned that all of the ground electronics in the launch facility were ‘fried’ as though the system had been destroyed by a massive electrical surge.

The former launch officer continued, “Finally, a couple of years later, when I was stationed at NORAD headquarters in Colorado Springs, as a public information officer—an assignment I didn’t ask for or want—I was in the ‘approval-loop’ for an FOIA request about this incident.”

He concluded, “I was surprised that part of the information which was being provided in response to the request was my crew log, with all of my handwritten notes, although much of the relevant information had been redacted. This means that NORAD was the apparent destination, at least one of them, for paperwork related to the incident.”

Two other former USAF Minuteman missile launch officers, Captains David Schuur and Larry Manross, had previously discussed with me their own involvement in very similar incidents at Minot AFB, North Dakota, in the late 1960s.

Moreover, documents smuggled out of Russia by television investigative reporter George Knapp confirm that one such incident—a UFO-initiated, temporary missile activation-for-launch—occurred at an ICBM base in Soviet Ukraine, on October 4, 1982.

Consequently, in addition to the now-widely publicized UFO-related missile shutdown incidents—such as the Echo and Oscar Flight incidents at Malmstrom AFB, Montana, in March 1967—we now have a steadily increasing number of ICBM activations being reported by former missile launch officers—on both sides of the ocean. Predictably, both Washington and Moscow remain silent about these dramatic and perhaps ominous disclosures.

Continue Reading . . .

See Also:

Malmstrom Air Force Base Picks Up UFO on Radar; "Sabotage Alert Team Located Another UFO Directly Over The Base"

UFO Buzzes ICBM Launch Capsule at Minot AFB

My Evidence: The Account of Minute-Man Missiles Being Disabled, While UFOs Hovered Over The Launch Facilities

SHARE YOUR UFO EXPERIENCE