Dated: 22 Feb 2006
Subject: Oscar Flight account from CUFON web site
Original Source

ttp://www.cufon.org/cufon/malmstrom/malm1.htm


CUFON:
Because of this unique incident, as an ex-Missileer describes it: "All Hell broke loose!" Among the many calls to and from the E-Flight LCC one was to the MCCC of Oscar-Flight which links to the equally dramatic story of what happened in another LCC that same morning.

---------------------------------------------------------------------------------------------------------------
Note:
Robert Hastings:
When Salas and Klotz published their article, The Malmstrom AFB UFO/Missile Incident, some years ago, they believed that the two shutdown incidents had occurred within the same 24-period, on March 16, 1967. As my article points out, Klotz still believes that. However, Salas now agrees with me that they probably occurred on two separate days.

This alternate time-line is based on the testimony of my source, Bob Jamison. In light of that, I propose that the Oscar Flight shutdown probably took place on the night of March 24/25, 1967--the same night as the Belt, MT incident. (The Echo Flight shutdown is documented as having occurred on March 16, 1967, in the 341st Missile Wing unit history.

See Bob Jamison statement in my paper, located on the NICAP site at:
http://nicap.org/babylon/missile_incidents.htm

-------------------------------------------------------------------------------------------------------------------


OSCAR-FLIGHT

The Oscar Flight LCC was located a mile or two south of the town of Roy, about 20 miles southeast of the Echo-Flight LCC.

The following is as told by Robert Salas who was the DMCCC in O-Flight that morning:

My recollection is that I was on duty as a Deputy Missile Combat Crew Commander below ground in the LCC, during the morning hours of 16 March 1967.

Outside, above the subterranean LCC capsule, it was a typical clear, cold Montana night sky; there were a few inches of snow on the ground. Where we were, there were no city lights to detract from the spectacular array of stars, and it was not uncommon to see shooting stars. Montana isnt called Big Sky Countryfor no reason, and Airmen on duty topside probably spent some of their time outside looking up at the stars. It was one of those airmen who first saw what at first appeared to be a star begin to zig-zag across the sky.  Then he saw another light do the same thing, and this time it was larger and closer. He asked his Flight Security Controller, (FSC, the Non-Commissioned Officer (NCO) in charge of Launch Control Center site security), to come and take a look. They both stood there watching the lights streak directly above them, stop, change directions at high speed and return overhead. The NCO ran into the building and phoned me at my station in the underground capsule. He reported to me that they had been seeing lights making strange maneuvers over the facility, and that they weren't aircraft. I replied: "Great. You just keep watching them and let me know if they get any closer."

I did not take this report seriously and directed him to report back if anything more significant happened. At the time, I believed this first call to be a joke. Still, that sort of behavior was definitely out of character for air security policemen whose communications with us were usually very professional. 

A few minutes later, the security NCO called again. This time he was clearly frightened and was shouting his words:

"Sir, there's one hovering outside the front gate!"
"One what?"
"A UFO! It's just sitting there. We're all just looking at it. What do you want us to do?"
"What? What does it look like?"
"I can't really describe it. It's glowing red. What are we supposed to do?"
"Make sure the site is secure and I'll phone the Command Post."
"Sir, I have to go now, one of the guys just got injured."

Before I could ask about the injury, he was off the line.  I immediately went over to my commander, Lt. Fred Meiwald, who was on a scheduled sleep period .  I woke him and began to brief him about the phone calls and what was going on topside.  In the middle of this conversation, we both heard the first alarm klaxon resound through the confined space of the capsule, and both immediately looked over at the panel of annunciator lights at the Commander's station.  A 'No-Go' light and two red security lights were lit indicating problems at one of our missile sites.  Fred jumped up to query the system to determine the cause of the problem.  Before he could do so, another alarm went off at another site, then another and another simultaneously.  Within the next few seconds, we had lost six to eight missiles to a 'No-Go' (inoperable) condition.

After reporting this incident to the Command Post, I phoned my security guard. He said that the man who had approached the UFO had not been injured seriously but was being evacuated by helicopter to the base. Once topside, I spoke directly with the security guard about the UFOs. He added that the UFO had a red glow and appeared to be saucer shaped. He repeated that it had been immediately outside the front gate, hovering silently.

We sent a security patrol to check our LFs after the shutdown, and they reported sighting another UFO during that patrol. They also lost radio contact with our site immediately after reporting the UFO.

When we were relieved by our scheduled replacement crew later that morning. The missiles had still not been brought on line by on-site maintenance teams.

Again, UFOs had been sighted by security personnel at or about the time Minuteman Strategic missiles shutdown