Thursday, February 16, 2012
The Oscar Flight Mystery: The Other Malmstrom UFO Story
As I mentioned in a previous post, I'll break the story down over a series of blog posts. Where to begin? I believe that the best starting point is to look at the case in it's present state and work backwards. This will allow us to look at the story's evolution since 24 March 1967.
It appears that the Echo Flight shutdown that occurred one week prior to the alleged Oscar incident, 16 March, may have been the catalyst for the story. Initially, Salas believed that he was at Echo, but eventually settled on being at Oscar. I'm aware that he also believed that he was out at November prior to changing his final location to Oscar. While some have been critical of Salas' changing location, I'll give him a pass on this one due to the lapse of 40 plus years. I must confess that for a while, I had a difficult time remembering for certain where I had pulled my last alert back in 1985, but certain alert peculiarities and events during that last alert settled my location to have been at Kilo.
Robert Salas' affidavit, along with the others can be viewed on spiralgalaxy.org. Below is a short synopsis of Salas' story according to his affidavit.
Salas' Current Claim
Approximately on 24 March 1967, Robert Salas, was on alert at Malmstrom's Oscar Flight (490th SMS) with his crew commander Frederick Meiwald. Meiwald was in rest status (sleep shift). Salas had received a call from the Flight Security Controller (FSC) and reported that he and other topside personnel had observed "lights" in the sky making unusual maneuvers. The FSC had ruled out aircraft due to the "objects" travelling at a high rate of speed and making unusual directional changes. The objects made no noticeable noise.
A few minutes later, the FSC called again screaming that a large red oval shaped object was hovering over the LCF's front gate. The FSC described the object as being 30-40 feet in diameter. The FSC abruptly cut off the conversation stating that one of his men had been injured. At this point, Salas had awaken Meiwald briefing the contents of the FSC's reports. Per Salas, alarms started sounding and "fault" light indicators on the commander's launch control console were illuminated. Meiwald queried VRSA and most, if not all, of the missiles showed "guidance and control system failure."
Meiwald contacted the Wing Command Post and Squadron Command Post (Kilo). Meiwald told Salas, "The same thing happened at another flight."
Due to security violation lights at one or more of Oscars LFs, Salas contacted the FSC to have one of the security teams respond to the LFs in question. The FSC reported to Salas that the object had flown off. When the security team approached one of the LFs with a security violation, they reported seeing an object similar to that sighted at Oscar's LCF.
Per Salas, Oscar's ICBM were disabled for the remainder of the alert tour. Prior to departing back to Malmstrom, Salas talked to the FSC who had nothing different to add concerning the incident. The individual who had been injured suffered a minor injury to his hand, but the injury had nothing to do with the sighted object. After being relieved by another crew and returning to base, Salas and Meiwald were debriefed by their squadron commander and another officer from the AFOSI (Air Force Office of Special Investigation). Both Salas and Meiwald were told that there were no explanations of why the event occurred, nor were there any Air Force exercises taking place. The OSI officer told Salas and Meiwald that the incident was classified SECRET and they were not to speak about it to anyone. According to Salas, he would hear nothing further about the incident for the remainder of his time on active duty.
Affidavits, Lack of Documentation and Investigation
Why the affidavits? Presumably, this gives the air of truth to the accounting/s as Salas has always thought that the evidence supporting his claim could be proven in a court of law. But is the "truth" supported by facts, and does Salas have enough evidence to mount even a circumstantial case? Who is supplying the evidence since the 341st SMW's Unit History and Bernard Nalty (History of the US ICBM Program) make no hint or reference to anything happening with Oscar Flight? There is a secondary effect of the affidavits. Since this is a 40 plus year old case, there is bound to be confusion and changing accounts as the years have passed. This allows all of the participants to settle on one "concise" story regardless of any conflicts with past statements.
Project Blue Book investigated both Minot UFO reports in 1966 and 1968, yet did not investigate any UFO incident involving Oscar Flight. This defies common logic by omitting Oscar from official scrutiny by the Air Force, SAC, and Blue Book. True, Echo Flight's ten missile shut down was not investigated by Blue Book, but I had theorized that such an investigation was not warranted since the Air Force and SAC had mounted an engineering analysis that pin pointed an EMP-like noise pulse emanating from the LCC. A subsequent Boeing Engineering Change Plan implementing EMP suppression kits solved the problem SAC-Wide.
Since the Sept. 2010 press conference participants provided affidavits, I decided to look into the use of an affidavit. I contacted a local notary public and asked about the process of notarizing an affidavit. This gentleman stated that just because an affidavit was notarized it had no legal bearing as to the "truthfulness" of the statement. Basically, the individual provides proof of who he/she is and the notary bears witness to that individual signing a statement or document regardless to its contents.
In the next following blog posts we'll look at the statements of Robert Jamison, Dwynne Arneson and Fred Meiwald. Do these individuals provide conclusive evidence that UFOs caused Oscar Flight's missiles to drop off alert? We'll further look at earlier versions of Salas' claims and see if they are consistent. Since I secured a copy of "Faded Giant" by Klotz and Salas, I'll compare it's content for story consistency. I'll try to update the blog on a weekly basis. This should be a fun case to look at.