James Carlson Posted October 23, 2006 #276 Share Posted October 23, 2006 Maybe it's just me, but I've got to be honest with you, I get this impression a lot when it comes to things like UFO reports. It's just a vague uneasiness, frankly, but with UFO reports, it does seem like there are people out there keeping an eye open for incidents that go back a few years that they can spin into a UFO contact story. Take for example this incident at Malmstrom AFB. When Robert Salas first wrote up his little story for publication, he said that he worked at November Flight LLC -- you'll note that isn't anywhere near Echo Flight where my Dad worked, and where the missile systems were shut down due to that 10 volt pulse we've already mentioned. There were rumors of UFO activity for that period at November Flight, and that's probably why Salas wanted people to think he had worked there, not realizing that someone might actually remember that he never worked at November Flight. Salas worked at Oscar Flight -- and you'll note that nothing ever happened at Oscar-Flight whatsoever. To me, it sounds like he wanted to push a UFO agenda in concert with America's nuclear missile capabilities of the time. He wrote up his report saying he was there -- "I saw it all" type of thing -- until somebody checked and figured out he was never at November Flight, he was at Oscar Flight. I can't possibly believe that he doesn't remember what missile launch system he worked at, so I conclude that he purposefully lied about in order to make his story sound more like eyewitness testimony, which it isn't. He was at Oscar Flight, and there is testimony to support that fact. Now at Echo Flight, where the missiles went offline and where my father had the watch that night as Crew Commander, there were no UFO reports. Salas wants us to believe that the Deputy Crew Commander spoke with security, and security told him there was a UFO. We know that's a lie, because the Deputy Crew Commander never mentioned anything like that to my Dad, the Crew Commander, which he would have since he was required to, and also because everybody on the surface was interviewed the next day due to the missiles going offline, and all of them said the same thing: that nothing strange had happened. There were "rumors," mentioned in the command history, of UFO sightings at November Flight, but these were discounted because the mobile security teams, upon being interviewed, were positive nothing odd had happened there either. Now Salas comes around 25 years later, thinking nobody will remember him from the original crews, and writes up some story saying "hey, guys, those UFO's at November Flight were real -- I saw them when I worked there that night the missiles went offline ay Echo Flight!" Someone who reads this comes back and says, "you weren't there -- you never worked November Flight -- you were at Oscar Flight. And nothing ever happened at Oscar Flight." Well Salas looks like a liar now, so he needs to get some verification. Around this time, some guys came nosing around to interview my Dad regarding that night, and he tells them that nothing had happened, no UFOs, and the missiles going offline were fully investigated -- no big deal, right? Then Salas contacts Don Crawford, the Captain who relieved my father the next day -- well AFTER anything that may have happened. Well, he spices the account up a bit by saying my Dad and the Deputy Crew Commander were "still visibly shaken," and that the missiles were inoperable for the entire following day (not surprising, given that an investigation was still in progress, but he makes it sound like the UFOs knocked our missiles out for the full day; they didn't -- we kept them off for an investigation; there's little doubt that they could have been brought back up without incident after a system reboot). Now Salas has nothing, because he was caught in a lie. He was actually at Oscar Flight -- 20 miles away from Echo Flight, so the missiles going offline can't be attested to, and nowhere near November Flight, so he can't even attest to the UFO rumors there. And keep in mind that those rumors were immediately discounted by eyewitnesses who said nothing happened there either. So what does Salas do to try and maintain his UFO agenda and rescue the shredded remnants of his credibility? He gets inventive: [This following is directly quoted - it should come up in color blue] 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 isn’t called “Big Sky Country” for 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. The only problem is there are no log entries, investigation reports, medical records, secuirty logs, watch command logs, eyewitness reports, or even newspaper articles to support ANYTHING in the above statement. There aren't any witness names that can be checked, or investigation records. There are lots of records available to reference the Echo Flight missiles going down, and there are even records to attest to UFO rumors at November Flight, where Salas first claimed to work, but absolutely NOTHING supporting events of any type at Oscar Flight, where he actually worked. Nothing... What Salas had was a bunch of lies, and Don Crawford, since he couldn't get my Dad to sign on with this ridiculous load of crap. You'd think Don Crawford wouldn't add much, since he wasn't even on duty when everything supposedly happened. He got background; Don Crawford says that [and this should be in blue, too]: It was during this same period, according to Col. Don Crawford (USAF ret.), that a two person SAT, assigned to Echo Flight, was performing a routine check of the missile launch facilities a few miles north of Lewistown, Montana. As they approached one of the launch facilities, an astonishing sight caused the driver to slam on his brakes. Stunned in amazement, they watched as, about 300 feet ahead, a very large glowing object hovered silently directly over the launch facility. One of them picked up his VHF hand microphone and called then Captain Don Crawford who was the DMCCC on duty that evening “Sir, you wouldn’t believe what I’m looking at,” he said. He described what they were seeing. Crawford didn’t believe him at first but the young airman insisted he was telling the truth, his voice revealing his emotional state. Eventually Crawford took him seriously enough to call the Command Post to report it. The officer on duty at the Command Post refused to accept the report and simply stated, “We no longer record those kinds of reports,” indicating he didn’t want to hear about the UFO. Crawford unsure of what to tell his shaken security guard, decided to give the guard his permission to fire his weapon at the object if it seemed hostile. “Thanks, sir, but I really don’t think it would do any good,” A few seconds later the object silently flew away. There were sightings in the area before and after the missile shutdown incidents by military personnel and civilians. No dates, no names, no verification -- NOTHING. But it's this ridiculous bit of testimony that puts UFOs at Echo Flight -- nothing else. And that's why I say that "It’s almost as if someone in an area of classified authority and legal trust was looking about for an incident of some sort that was reported with which to link an outlandish tale of UFO interference with national defense interests." That's what Robert Salas and Don Crawford did. They took a past incident that was at one time highly classified, and linked it to an asinine UFO story in order to create a new paradigm with an agenda they could profit off of. And they have profited -- TV appearances, radio interviews, Salas has co-authored a book on the topic, and there are those video tape sales to bring in a paycheck as well. It's obvious that Salas was at one time in a position of "classified authority and legal trust," otherwise he wouldn't have know how best to capitalize on these incidents for his own personal gain (and yet, he still managed to screw it up, and come off sounding like a loon or a liar). He picked up a copy of UFO magazine, and probably figured, "y'know, these clowns are idiots -- I bet I can exploit that, using my highly classified, military background. Heck, maybe I'll get laid in the process..." The day I found out that Salas had originally claimed to be at November Flight is the day I absolutely KNEW he had lied about the whole thing -- because there actually were rumors of UFOs being sighted around November Flight during that period of time. It was only after this example of "poor memory" was made public that his fully fictionalized account of the events at Oscar Flight came out. He couldn't fall back on his November Flight lie, and he wasn't at Echo Flight -- which was the only fully investigated missile outage. If it wasn't for the fact that this fully documented investigation had made very plain who was on duty when and where, I'm certain he would have first claimed to work at Echo Flight. But he couldn't, and that's why he claimed to work at November Flight first -- he didn't think he'd get called on it, and he needed something to back up his story. Well, he was called on it, and that's why he was forced to bring out Don Crawford and the whole Oscar Flight fiction. And now, the whole thing is part of the Disclosure Project, and people actually believe our government is hiding the true events of what went on March 16, 1967. Well, our government may be hiding something, but not that -- for the most part, our government has declassified the whole incident, an incident that was VERY highly classified at one time. One more short comment before I close up -- CUFON and Salas have made much of the fact that the original SAC command message states that the loss of the 10 Echo Flight missiles "is cause for grave concern to this headquarters." That really shouldn't be interpreted so wildly. Whenever "grave concern" is used in a message, all that means is that the message is classified Secret, and since it's stamped Secret at the top of this now-declassified message, it really shouldn't be considered as an exceptional sign of a concern that goes beyond the classification. ciao -- James Carlson Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now