Tuesday, February 8, 2011

Robert Hastings' Swiss Cheese Factor...Henry Barlow

It was brought to my attention a few days ago from a fellow Reality Uncovered forum member that Robert Hastings had attached what appeared to be an addendum to his post, "James Carlson Just Can't Get It."  A link was provided first to UFO Digest and the following day to UFO Magazine Blog.  This secondary post was the obligatory damning of James Carlson which was to be expected in a typical Robert Hastings piece.  Its the verbiage, half way into the post, that caught my eye.

As for Tim Herbert’s, ahem, “authoritative” summary of the missile shutdown incidents, Carlson is dreaming if he thinks that Hebert—who was not present when the events occurred—can explain them away. I will provide Hebert with former missile maintenance tech Hank Barlow’s email address—if he will write to me and ask for it—so that he can learn the facts from someone who was actually involved in the Echo shutdown aftermath. Again, Barlow says he was explicitly told that UFOs had caused the malfunctions. (Just as former targeting team officer Bob Jamison was told that the Oscar missiles had met the same fate. I will forward Jamison’s email address to Hebert as well.)
As Hebert told me in an email last year, he first became aware of the events at Malmstrom while writing a post-graduate psychology paper on “delusional thinking.” (Rather ironic that he should now be supporting James Carlson’s rants, eh?) Hebert’s remarks made quite clear his own anti-UFO biases. Is it any wonder he and James Carlson are such pals?

For starters, I agree with Hastings that I was not present when the event occurred, but neither was he.  Hastings was emptying trash cans some where in a building on Malmstrom AFB proper, but he was not at Echo.  I'm really not sure if he even knew where Echo-01 was situated or how to get there being that the LCF was some 120 miles east of Malmstrom. I'm sure that Robert will provide clarification about his where abouts at the given time.

As for Hastings providing Hank Barlow's contact information, it's not needed since Mr. Barlow's statements (attached at end of article) have been provided to me by Tim Printy based on what Hastings had posted on the Bad Astronomy Forum site some time back.  I did a web search and came across the same statements that Hastings had posted on other numerous sites and verified that what Printy had provided was exactly the same with no variations.

Assuming that Barlow was indeed assigned to Malmstrom in 1967, and Hastings had properly vetted Barlow, his statements are noteworthy in two ways:  what is said and what is not said.  Per Barlow, he was a member of an EMT unit situated at Mike 01 on 16 March 1967 that responded to the Echo Flight shutdowns.  Barlow states that there were no active VRSA channels reporting at any of the ten LFs.  This contradicts Walter Figel's statements to Hastings and Robert Salas that all ten of the LFs had active reporting VRSA channel 9 LF-No Go.  Per checklist procedures, Figel would have, via the LCC VRSA panel, checked any and all sorties that had fault indications and Figel made no mention that there were no active reporting channels.  Did Barlow initiate the LF VRSA interrogations himself, or did another team member accomplished this?  Barlow states that his team only restarted 3 or 4 missiles, so how would he have known of the VRSA status of the remaining 6 or 7 sites?  What of the other EMT teams that restarted those remaining sites?  So now Hastings has a problem, who is right?...Barlow or Figel?  The 341st Unit History states that all ten sites had active VRSA 9s.  Subsequent data dumps would also discover active VRSA 12s implicating the Logic Coupler. 

Let's also remember that Barlow's team was not the first to actually respond to the shut downs.  Prior to the shutdowns, there were maintenance teams at two of Echo's LFs.  After the No-Go indications were received at the LCC, one team immediately verified the VRSA channel  9, the other team eventually did the same after penetrating the site.  Again, this totally contradicts Barlow's assertions, unless...Figel's statements to Hastings and Salas were false.  Walter Figel's statements have always been the "definitive" answer concerning Echo's shutdowns, at least that is what we are constantly lead to believe.

Barlow states that he heard from an unknown secondary source that a UFO was spotted over E-02 by a security camper team.  One of the security team members supposedly photographed the object, but the film and/or camera was confiscated by Air Force officials.  Again, Barlow states that he was told this by someone, who couldn't be named, back at the Echo LCF.  A recognizable pattern?  What about the maintenance team that had to remain on site awaiting the arrival of the camper team.  It would have taken approximately two hours if not more to generate the camper team back at Malmstrom then dispatching them to E-02.  Again this conflicts with Figel's statements and the time lines don't match up, plus depending on what version of Figel is used (Hastings vs. Salas), a maintenance team reported the UFO or one of Echo's SATs saw the UFO over an anonymous LF from a distance...a camper team was never mentioned.

Further, Barlow states that upon returning back to Echo-01, "...there was brass all over the place.  They were from Offutt AFB - SAC Headquarters..."  Walter Figel never made this claim, though by that time he and Eric Carlson would have already departed back to base, but the relief crew, Don Crawford, never made this claim either.  Walter Figel told Salas that he made a TDY to Offutt to brief SAC officials, though admittedly I have seen no proof that verifies that particular claim.  Eric Carlson states that, while still at Echo, he received a call from the SAC Command Post, a general officer, inquiring on the launch status of Echo's sorties.  Perhaps Barlow misinterpreted a large contingency of wing personnel that had showed up on site due to the nature of the event, thus believing them to be SAC HQ officials.  The Unit History makes no reference either way other than to state that Boeing and OOMA (Hill AFB, Ogden) had dispatched personnel to investigate the shutdowns and by the time that this team had arrived, all of Echo's sorties had been brought back up to alert status.  Barlow appears to have more of an accurate recollection by eventually stating:

I was so tired when we got back to Echo 1—we had worked long hours, we had been out almost a week by that time and we were just pooped. All I remember is that there were lots of people there and there was no place to lie down.
What can we really learn from Barlow's statement?  He was out in the field and responded to the shutdowns.  Though it appears that he was involved with restarting all ten missiles, he did not.  He was only involved with three or four start ups.  He was told by various unnamed individuals that UFOs had cause the shutdowns.  Barlow, himself, did not state that he personally saw UFO activity while responding to the shutdowns.  In the end Barlow joins a growing list of Hastings witnesses who saw nothing, but heard second/third hand that UFOs had been in the flight area.

I noticed that when Hastings and Salas held their press conference, 27 Sept 2010, Barlow was not in attendance.  Perhaps Hastings could provide information as to whether Barlow was invited or not.  All of the participants had signed affidavits.  Based upon Barlow's story, would he have willingly signed an affidavit?  I also noted that Barlow was on station for approximately one year.  There may be good reasons, but one year is unusually short.  Perhaps Hastings/Barlow would be willing to shed some light on that subject.  One wonders why Barlow has never been prominently featured as a strong supporting witness, but I suspect that I now know why.

In conclusion, though interesting and entertaining, Barlow's accounting is filled with numerous holes and contradictions...a marginally weak supporting witness is the best that can be said.  Hastings appears to have adopted the "Swiss Cheese" factor, "sure there are a lot of holes, but its still edible."  If Barlow is right, then Walter Figel is wrong leading to another corner that Hastings has painted himself into.

As for Robert Jamison, I'll soon be looking again at his statements, both pre-affidavit and what is now listed on his affidavit as provided by Robert Salas.  I briefly touched on his original statements in my first blog article, "Did UFOs Disable Minuteman Missiles at Malmstrom..."  In light of Jamison's affidavit, he certainly deserves thorough consideration.


Below is Robert Hastings' interview with Henry "Hank" Barlow:

I (RH) have interviewed one of the missile maintenance technicians who responded to the Echo shutdowns on March 16, 1967. N. Henry “Hank” Barlow, then a buck sergeant, told me,

“I arrived at Malmstrom in October 1966 and left in November 1967. I was on Electro-Mechanical Team 24 at the time [the Echo Flight shutdown] happened. We had to go out to Mike-1 for about four or five days. We had to stay out there and cover the sites. The day we were supposed to return [to base, one of us] called Job Control to see if we could come in because it was really starting to snow. It was really miserable out, windy and all. Job Control said, ‘Yeah, come on in, there’s nothing going on, everything seems okay.’ So we packed up and started back to the base.

Then Job Control called us on the radio and said, ‘Hey, we’ve got a problem here, part of Echo Flight has shut down, so we want you to go to the nearest site.’ I think that was Echo-6, but I’m not sure. Anyway, somewhere around that area. We checked VRSA and there was nothing on it. [That] was a unit in each launch facility, with something like 19 or 20 channels on it. [Actually, VRSA or Voice Reporting Signal Assembly had 23 channels, one for each problem area.] If the missile went down for any reason, or if there was some other problem, Job Control back at Malmstrom would know about it, know what is was, from the kind of signal it sent. But when we got to the site, there was nothing on [VRSA] to indicate the reason for the missile shutting down. That in itself was unusual. I had never seen that before.”

The declassified 341 Strategic Missile Wing history states that the missiles went down due to VRSA signals 9 and 12. When I asked Jim Klotz about this apparent discrepancy, he commented, “------‘s team ran a ‘special (diagnostic) tape’ (mentioned in the wing history) and DID get VRSA data.” For the moment, Klotz is protecting the name of this targeting team member, whom he interviewed a few months ago. That individual also responded to the Echo shutdowns and also reports hearing of UFO involvement in them from one of his superiors. Klotz says that the information provided by the source, as well as his identity, will be published in revised edition of his and Bob Salas’ coauthored book, Faded Giant.

Barlow continued, “So Job Control said, do a start-up, which takes about four hours. After you initiate the startup, you can back out of there and leave because its automatic after a certain point. Usually, if there was nothing else going on, we would stay at the site to make sure everything was working fine. But that night, Job Control said go to the next site, whatever that was. So we did that, and [restarted] three or four missiles before going back to [Echo-1]. Of all ten missiles that went down, only one wouldn’t come back up, but that was due to something that was going to [fail] anyway, like a Logic Coupler Drawer, or something like that. But none of the missiles had anything on VRSA.

[When we got back to Echo-1] we heard what happened. At Echo-2, there was a team in there earlier that afternoon that could not get the security [telemetry] to set-up, through the parabolic antenna or the soft support building or something like that. So, they put an Air Police team out there, in a camper, two guys. Anyway, one of the guys went out to take a leak, and he noticed that it wasn’t snowing over top of his head. The perimeter lights were on and he could see the snow coming down all around him so he looked up and saw a ring of lights right over top of him. He was scared stiff, so he went back to the camper and woke up his team partner.

When this other guy came out, he had a camera with him, which they weren’t suppose to have, but guys would do stuff like that. By then this thing had moved off the perimeter fence and he took pictures of it. [When the security team was debriefed back at the base,] the Air Force confiscated the camera and film. I was told all of this back at Echo-1. We had passed our ‘timelines’ because we had worked 16 hours, or something like that, and could not go back to the base so we had to go back to Echo. When we got back there, there was brass all over the place. They were from Offutt AFB—SAC Headquarters—they had brought them in. There were just a lot of high-ranking officers there.”

I asked Barlow who had told him about the incident involving the Camper Alert Team. He responded, “I don’t remember. I don’t know if it was one of the security guys or someone else. I was so tired when we got back to Echo 1—we had worked long hours, we had been out almost a week by that time and we were just pooped. All I remember is that there were lots of people there and there was no place to lie down. But we were told that it was a UFO shutdown—that UFOs had been responsible—and that’s why all those guys were there.”

I asked Barlow if he had been surprised or shocked or skeptical when he was informed that UFOs had shutdown the missiles. He replied,

“Oh no! On many other occasions, we were out at the sites when Job Control called and told us that, you know, there are reports of UFOs in the area, so keep your eyes open. That happened many, many times. And I saw them! I would see a light in the sky and it would make a right-angle turn. Or it would make two different right-angle turns, one after the other. I saw that more than once. They were much faster than a helicopter and we certainly knew that aircraft [couldn’t] do that.

I once saw a light come straight down, hover at maybe 1000-feet, and then shoot straight off [horizontally] and out of sight. It was crazy! Job Control always called us first, before we saw anything. They would call and say, you know, heads-up. Then, most of the time, we would see something a little while later. So, they were getting reports from somewhere, and maybe they had [the UFOs] on radar, but I don’t know for sure. Sometimes, when the call came in, we were down in the missile [silo] and we would talk to the guard topside about what he was seeing. I remember one time, the guard was just a nervous wreck. Job Control had called and said UFOs were sighted in the area. Then, I’m not sure, but I think he saw some lights himself. But anyway, he was just scared out of his wits. He wanted to come down in the silo with us. But the guards weren’t allowed to do that.

One time, [probably during the summer of 1967,] we were at one of the Bravo sites when we got a call from Job Control saying that there were UFO sightings in our area. Then, a short time later, we saw a green light come straight down out of the sky and land on this hill. Then two lights separated from it, straight out to each side. We were sitting in the pick up truck, eating our box lunches, when we saw this, along with another team we were training, plus the guard. We reported it to Job Control. They told us to close up the site and go check that out. We told them that we didn’t think we were qualified to do that! This was around 4 a.m. When it got light, we were amazed how far away the hill was, where this thing had landed. It was far, far away. We thought it was much closer, so the light was really bright.

I asked Barlow if he had later been debriefed about the incident at Echo Flight. He said, “No, never! It was almost kind of a joke, we would all laugh about it. Now, it wasn’t a joke [with all the missiles down] but it was a joke because nobody would believe it if you told them about it.”

I asked Barlow if he had heard about the Oscar Flight missiles shutting down around the same time as the Echo Flight shutdowns. He said “No, I never knew about that...I wasn’t qualified to work there.”

Tuesday, February 1, 2011

Robert Hastings: "James Carlson Just Can't Get It"...Again?

So it goes once again that minus any legitimate attempts at debating the merits of the Malmstrom case, Robert Hastings resorts to his old habits of deflecting away from the issues, namely by using James Carlson as a shield against "the slings and arrows" hurled against his traveling ufology road show.

"By attempting to discredit these courageous men, some of whom spoke out at my September 2010 press conference in Washington D.C., Carlson only comes across as ever more delusional, except to those so negatively-biased against the UFO reality that such rants seem reasonable."

This shtick grows old as his theory continues to take on water and those of us who point out the obvious disconnects with his story are constantly, in Hastings eyes, becoming "...ever more delusional..."  Least I remind everyone that two of the principle characters of Hastings' Malmstrom UFO saga were notably missing at the D.C. press conference...Eric Carlson and Walter Figel.  Why was that...?

"Unlike the guys with backbone--the ones who participated in the press conference--Figel has been back-tracking in recent months. Fortunately, his more candid moments were caught on audio tape years ago and the world can now eavesdrop on his confessions."

Figel backtracking in recent months?  How about shape shifting the story since 1996 and eventually throwing Hastings' a UFO bone in 2008.  Which ones were Figel's most candid moments caught on audio?  The candid statements to Salas in 1996 or to Hastings in 2008?  Both "candid" moments are significantly different and Robert Hastings hasn't quite figured that one out, yet never mind, we are the ones that are considered delusional and misguided.  For a refresher on those candid moments see "A Tale of Two Figels..."

For a man whom Hastings once told me had "serious mental" issues, James Carlson appears to be causing Hastings some sleepless nights thus forcing Hastings to once again play the "delusional Carlson" card in yet another feeble attempt to throw the dogs off the scent.

Lastly, lets take a quick peek at the poster, or more accurately, who paste Hastings recent rant on UFO Magazine Blog, Alfred Lehmberg:

"You know -- it's selfish, self-interested, self-involved, self-motivated, and self-concerned cack-wits, like yourself, that the genuine truth-seeker has always had to leap over in pursuit of any real enlightened efficacy or validated self-respect... Pack sand and "die," Mr. Carlson, for all of us, including yourself. ...And Skippy? Don't make me explain the quotes around "die." I promise that it will be embarrassing."

"Much too little much too late, Mr. Carlson. Couple your paucity of legitimate rebuttal with the humiliating necessity of having to qualify the seeming cowardice of your father (?), and what was unconvincingly contrary is now just embarrassingly shrill."

Mr. Lehmberg...dude...calling a man, whom you've never met, a coward tells a lot about yourself and your lack of objectivity, and most importantly, lack of character.  Unfortunately, I'm not surprised.  Robert Hastings relies on others such as Alfred Lehmberg to be his covert and/or overt "sock puppets" parroting out what ever marching orders that filters down the way.  One would think that rather than paste someone else work, some thought provoking originality could be had to entice intelligent debate on the issues rather than childish name calling.  Skippy, make him explain "die" and keep his promise...

Monday, January 24, 2011

Walter Figel: No UFOs at Echo and Doubtful of Shutdowns at Oscar

A few months ago James Carlson provided me a copy of an email that he had received from Walter Figel.  Col Figel pretty much spells out his view on the whole Echo Flight affair as well as Salas' claims of an Oscar shutdown.

Re: telephone conversation
Thursday, March 11, 2010 9:03 AM
From Walter Figel, Jr. Thu Mar 11 14:03:27 2010
Re: telephone conversation.eml
James
I guess you must have posted something somewhere that got Hastings attention
He did call and we did speak for a bit, so did Salas.
You should know that both calls were very cordial as was ours.
However, I think you guys have a pissing contest going that I would rather not get in the middle of. I have no vested or financial interests in UFOs and actually not even a passing interest in them. Guess I am different from most people. But, I could really care less about the subject.
I reasserted that I personally never did see a UFO at any time.
I do not personally “believe” that UFOs had anything to do with Echo flight shutting down that year.
I repeated that I never heard about an incident at November or Oscar flight and have no knowledge that they ever happened and that I doubted they did.
That is obviously a personal opinion as I can not prove the negative.
I repeated that Colonel Dick Evans was at the alternate command post at Kilo which is in the same squadron as November and Oscar and he never mentioned anything about a shutdown at either of these two flights.
If it did happen, I personally don’t know anything about it.
One of their books said I had a personal log – I did not.
The only log I ever filled out was the official log that all flights kept and that I do not and never did have a copy of that log. Obviously I can not remember what I wrote that morning.
One of the books says that the flight shut down in “seconds” – that is not an exactly accurate statement.
It obviously took some time for your dad and I to run the appropriate checklists and make all the calls that we had to make to the command post and maintenance. We were near the end of the checklist when the second missile shut down and shortly threafter the rest of them followed suit.
That sequence of events took several minutes not seconds, but that is all a very minor point in fact and doesn’t change the facts of the overall sequence of events that morning.
I told him that when someone mentioned UFOs, I just laughed it off as a joke and assumed someone was just kidding around. I never took it seriously.
I also told them that no one from any UFO office in the Air Force ever interviewed/deriefed your dad and/or me and that I do not remember ever signing any papers about anything.
In fact, I told them that until he mentioned it, I did not even know there was an office that monitored sightings of “UFOs” in the Air Force.
When your dad and I came topside the next day – no one ever said anything about UFOs and there was no “large gathering” of people on site that morning.
There may have been later that afternoon, but I would have no knowledge of that as we were long gone back to the base as usual.
I did not know the targeting office’s name or even know that he was there.
I did say there was a VRSA recording reporting a “Channel 9 – NO GO” reported.
They said that the maintenance crews had no such report at the LF.
I told him that I did not know how the system worked at the missile site so that I do not know if that is possible or not.
I have always maintained that I do not personally believe in UFOs.
I am not convinced that November or Oscar ever happened.
But these are obviously personal opinions and I can not state them as facts or prove them – they are my personal beliefs.
I also believe these statements are accurate.
I also believe that is what I said 2 years ago, but I don’t have recordings.
So my knowledge is very slim and I have no records about anything at all.
In addition, that was 43 years ago and memories fail – especially about things that were not especially important to me at the time.
Today, I can’t remember what time my wedding was and that I assure you is more important to me then and now. And that was in 1971.
So if this is a help, so be it.
But I would rather stay out of any long standing debate about UFOs and leave that to the experts and researchers and those who know or at least truely believe that they know. After all they may be right and proven so some day.
As for me, I’ll just go my way as a skeptic until proven wrong.
As you can see, I cc’d Hastings so that you both have the same piece of paper. I don’t think that there are any inconsistencies in what I said to either of you. If there are, I’m sorry, that is not my intention at all.
Good luck in your pursuits. Stay professional and all will benefit.
Regards to your dad, I wish him well. It’s been many years.
With that said, I hope that this tug of war is over and the three of you can resolve your differences about the whole affair.  Walt.
As can be seen above, Robert Hastings was supposedly provided a copy of the above email.  As of this time, I'm not aware if Hastings has publicly acknowledge that he had received a copy of the above correspondence.  But one can suspect that he very well may have received it based on his recent labeling of Walter Figel as "waffling" and "timid."

As for James Carlson’s completely discredited claim about there being no UFO involvement in a full-flight missile shutdown at Malmstrom, on March 16, 1967, one may hear what actually happened from the lips of Carlson’s father’s deputy missile commander, retired Col. Walter Figel, by listening to the tape recorded conversations Salas and I had with Figel years ago, before he began nervously changing his story after the public spotlight fell on him. Unfortunately for the timid, now-waffling Figel, his earlier admissions are a matter of record...
If the above correspondence from Walter Figel is accurate then James Carlson may well be owed a "public" apology from Robert Hastings.  As stated in my past postings, Walter Figel, as well as Eric Carlson, have consistently denied that UFOs were involved in the Echo incident.  If Figel's statements are the lynch pin to Hastings' and Salas' UFO theory, which it has been, then the "theory" collapses like a house of cards.

Special thanks to James Carlson for allowing me to post the above information.

Project Loggy Ebb: EMP or UFO Supression?


I was skimming through Bernard C. Nalty's USAF Ballistic Missile Programs, March 1967, and came across this interesting information concerning the Titan II system.  The entire volume of work can be viewed here and also via the NSA Archives site. (Bold faced emphasis by post writer.)



In light of the forthcoming retirement of Titan II, the Air Force was reluctant to spend large amounts to protect the system's Mk-6 reentry vehicle against nuclear detonation effects. Although a $50 to $60 million hardening program of this type was disapproved, the Air Force did proceed with two projects to protect the Titan launch complexes. They were Yard Fence and Loggy Ebb, originally called Low Ebb. Begun in 1965, Yard Fence was aimed at improving the reliability of equipment installed at Titan II sites. Work done under this program included adding. neutron shielding and acoustical lining and fitting new seals around blast doors. The project was to have been completed in the spring of 1966, but a silo fire near Searcy, Ark., in 1965 killed 53 civilian workers and compelled the Air Force to suspend work.
and...
Loggy Ebb, the other major project, was designed to provide protection against electromagnetic pulse, an effect of nuclear explosions that could damage vital electrical equipment. During the summer of 1967 workers at Little Rock began installing surge arrestors to protect Titan II circuits, generators, and buried cables. USAF plans called for completion of Loggy Ebb in October 1968 at Davis-Monthan AFB.
Of interest is the fact that work on the Titan II sites, for Loggy Ebb, started during the summer of 1967 possibly in conjunction with SAC's directives to install EMP filters/suppressors in the Minuteman I and II weapon systems.  Loggy Ebb was more than likely already in the engineering and planning phase the year prior to Echo Flight's shutdown, but could the project have been expedited due to Echo's ten missile shutdown?  At a minimum, programs such as Loggy Ebb, demonstrates that the Air Force, SAC and DOD were cognizant of the growing vulnerabilities of the entire ICBM force to the effects of EMP.

I have provided the link to the Engineering Change Proposal (ECP) , HIC EM Pulse Suppressor, for fixing the EMP issues effecting the Minuteman system.  Note that the ECP is marked "routine" at the top, line 2, for Boeing's recommended priority.  Boeing appeared not to be in "panic" mode to rush out a quick fix.

Wednesday, January 5, 2011

A Tale of Two Figels: Robert Hastings' and Robert Salas' "Hard Problem"

David Chalmers, philosopher of the mind, states that the issue of deciphering the mystery of qualia is the "hard problem" concerning the understanding of consciousness.  So it is with Salas and Hastings, both conjoined together, having their own version of "the hard problem", that being phenomena-wise, either as co-existing together, or as separate entities.  Can the one exist without the other, or does Salas' claims survive solely on an "incident" involving Echo Flight?

Robert Hastings recently posted an article on The UFO Chronicles web site, "UK UFO Debunker Strikes Again:  Will Dr. David Clarke Ever Get Anything Right?"  In the midst of the article, Hastings makes the following statement:


As for James Carlson’s completely discredited claim about there being no UFO involvement in a full-flight missile shutdown at Malmstrom, on March 16, 1967, one may hear what actually happened from the lips of Carlson’s father’s deputy missile commander, retired Col. Walter Figel, by listening to the tape recorded conversations Salas and I had with Figel years ago, before he began nervously changing his story after the public spotlight fell on him. Unfortunately for the timid, now-waffling Figel, his earlier admissions are a matter of record...
Hastings now believes that Figel is "timid and now-waffling", yet his "earlier admissions are a matter of record," ergo the truth.  So was he telling the truth back in 1996 and 2008, but now he is lying in 2010?  Perhaps James Carlson is not so "discredited " after all when the main witness is now being treated as a hostile witness.  Hastings and Salas have been using Figel's statements for years in an attempt to shore up their UFO claims, yet when you read both interviews they are filled with contradictions.  Both versions of the Echo incident can't be reconciled with one or the other.  One version may be fabricated based upon the confabulations of the interviewee and the wishful thinking of authors leaving the other as the "correct" version.  But, which one is which?  Figel's statements are fundamentally different when each interview is viewed separately.  With this revelation, one begs to ask the question...Who is the real Figel in any of the versions of the story?  Contradictions abound and one has to wonder if both Hastings and Salas were totally oblivious to the differences in Figel's statements or were both willing to "throw caution to the wind " with the hopes that no one would notice the discrepancies.   If both authors knew of the contradictions in Figel's interviews then one is led to believe that this was an attempt at deception, but who is deceiving who?  The answer lies in Figel's statements made separately to Hastings and Salas, twelve years spaced between the two interviews.

Walter Figel's Version According to Salas

In 1996, Salas interviewed Walter Figel, presumably, for the purpose of providing information on Echo Flight that would soon go into the book, Faded Giant.  In this setting, Salas needs the Echo incident, UFOs and all, to form the foundation of an initial erroneous November flight shutdown and eventually the final settlement of an Oscar flight shutdown.  Figel tells Salas that on 16 March 1967, all ten of Echo's sorties dropped off of alert. Figel tells Salas that two of his ten LFs had maintenance teams on site performing maintenance on the "cans" (slang for missile guidance system).  One of the LFs, site not specified, dropped off alert and Figel contacts the security team via VHF radio.  Figel has the security guard authenticate and asks for one of the maintenance team members.  The security guard tells Figel that there is a UFO hovering over the site.  Figel dispatches the SAT strike teams to both manned LFs.  By then, the remaining LFs would have already dropped off of alert status.  The strike teams report back to Figel that they were able to observe that each manned LF had a maintenance team and security guards on site. (Figel does not mention any observations of a UFO at this point in the interview.)  Figel states that after the incident he made a special trip to Offutt AFB for the purpose of briefing CINCSAC:

WF: I remember I got a trip to Omaha to discuss [the Echo Flight shutdown] with CINCSAC (the office of the Commander-in-Chief, Strategic Air Command, Offutt AFB, Omaha , Nebraska ).

RS: Oh, you did?!

WF: Oh yeah. Someplace, if I look deep enough, I could probably find the TDY (Temporary Duty) orders to do that.


Towards the end of the interview, Figel alludes to the strike teams actually observing a UFO over one of the sites, but is unable to provide a specific LF, manned or not, nor is he able to recall names of the individuals involved:

WF: ...having a dozen [sic] missiles go down in one flight is significant. [Laughs] Let’s face it, the [average] failure rate was nowheres near—was miniscule compared to that.

RS: That’s right, and then UFO sightings at the same time.

WF: Well, I [reportedly] had them hovering over the sites, you know, and I said, “Right, I’m not a believer in that crap!” And that was reported over the secure line, and I told those guys to make no transmissions and, when the Strike Team got out there—they were on VHF back to me—and they had no idea in the world what I even told them to look for, and they reported them [too].


Walter Figel's Version According to Hastings

Per Robert Hastings, "On October 20, 2008, I called Col. Figel and asked him to elaborate on his earlier statements to Bob Salas."

In Walter Figel's statements to Hastings, Echo had three to four sites with maintenance teams performing routine maintenance.  When pressed by Hastings, Figel narrows in on four LFs being manned.  At least two of the sites were running on diesel generators.  Figel was unable to recall what type of maintenance was actually being performed but reiterated that it was "routine."  Figel then tells of the incident:

WF: [When] the missiles dropped off alert, I started calling the maintenance people out there on the radio to talk to them. I had the security guard authenticate so I know I’m talking to a security guard and, you know, [I asked] “What’s going on? Is maintenance trying to get into the silo?” [The guard said,] “No, they’re still in the camper.” [So, I said,] “Get ‘em up, I want to talk to them.” Then I tried to tell them what I had was a Channel 9 No-Go.

WF: Uh, we did that with the sites that were there, that [had maintenance teams and their guards on site] and I sent Strike Teams to two other sites. There’s no sense sending them where I [already] have a guard and a gun and an authenticate.

RH: So far in this narrative, you haven’t mentioned UFOs.

WF: [Laughs] That’s correct. Um, somewhere along the way, um, one of the maintenance people—cause he didn’t know what was going on any place else either, they have no capability of talking to each other [at different launch sites], in other words, they can talk to the [launch] capsule but they can’t talk to each other—

RH: Right

WF: —unless they were on the radio and no one was using the radio except the security police. And the guy says, “We got a Channel 9 No-Go. It must be a UFO hovering over the site. I think I see one here.” [I said,] “Yeah, right, whatever. What were you drinking?” And he tried to convince me of something and I said, well, I basically, you know, didn’t believe him. [Laughs] I said, you know, we have to get somebody to look at this [No-Go]. [A short time later] one of the Strike Teams that went out, one of the two, claimed that they saw something over the site.


Based upon the above narrative, Figel tells Hastings that it was the maintenance team that reports the UFO and the strike teams are sent out only to two unmanned sites.  Most importantly, the maintenance team that makes the UFO claim is completely underground in the LF/silo reporting to Figel on the SIN line (Secure Intersite Network) and as discussed in a previous article, the top side security guards do not make any reports via radio that they have seen anything unusual.  One of the strike teams report that they see an object over one of the sites, but no site location is specified as to whether it is one of the two manned LFs or one of the remaining eight unmanned LFs. (Tim Hebert's "Off Alert, Echo...Parts 1 and 2.)

Contradictions, Deceptions, or Lies

As can be seen, we now have two versions of the same incident for consideration.  Both are filled with contradictions and cannot be reconciled with one another:

1.  The number of manned LFs and the actual maintenance that was being performed.  Was it two LFs or three to four LFs?  Were the maintenance teams working on the Missile Guidance Systems, the "cans", or were they doing normal routine work?

2.  Who made the first report of a UFO over one of the sites...the maintenance team or the topside security guard?

3.  The manner in which the SAT strike teams were dispatched...to two unmanned LFs or to the manned LFs.

4.  Figel states to Salas that he made a TDY trip to Offutt to brief CINSAC, but this information is omitted in Hastings' interview.   Eric Carlson, the Echo crew commander, states that he did receive a call from a general officer from SAC HQ, presumably from the SAC Command Post, asking about the launch capabilities of Echo ten missile sorties.  He makes no mentioning of having to personally go to Offutt AFB to brief anyone.

Only one of the two versions can be considered "correct" with the other being either a fabrication or the confabulations of the interviewee.  Both cannot exist together.  Hastings and Salas have spent a decade researching the Echo incident and both have relied heavily on Walter Figel's statements.  Both authors were in contact with each other and would have compared notes.  It seems illogical that both could not have seen the remarkable differences in content and context with both interviews.  Perhaps Figel only told them what they wanted to hear and both ran with the story regardless of the facts.  Figel always believed the UFO report to be a joke and maybe led both interviewers on a "wild goose chase" as a continuation of the original joke.  But one issue stands out, both versions contradict each other, either Hastings and Salas were blinded by their "quest", or they and/or Figel deceptively misled the public, or they foolishly and unknowingly propagated the continuation of a confabulation.  There lies Hastings' and Salas' "hard problem."

Reference:

http://www.theufochronicles.com/2010/01/uk-ufo-debunker-strikes-again.html

http://www.realityuncovered.net/blog/2010/09/an-interview-with-malmstrom-afb-witness-eric-carlson/

http://www.theufochronicles.com/2010/09/echooscar-witch-hunt.html

Friday, December 31, 2010

Off Alert, Echo Flight: The "UFO" Encounter...Part 2

In "Off Alert, Echo Flight:  Part I", I attempted to recreate the alert based upon the statements of Eric Carlson, Walter Figel and documentation from the 341st SMW's Unit History.  Eric Carlson would have been in the command position allowing him to witness and direct the actions of the crew and security forces for Echo Flight.  What then of the statements that would come from Figel some thirty and forty years later?  Did UFO activity cause the entire flight to drop off alert forcing SAC, the Air Force, and the DOD to cover up the event?  Let us see if the statements of the principle witnesses actually support such a conclusion.

The passage of time has a way of diluting one's memories, yet it seems right to ask the pertinent and hard questions concerning that  particular day some 43 years ago.  Did Figel recall, with absolute certainty, the contents of a phone call from a missile maintenance team?  Probably not with total accuracy.  Figel's own words in two different interviews underlies his difficulties with total recall:

Figel to Robert Hastings 10/20/08

RH: Do you know how many maintenance teams were out overnight?

WF: You know, I think it was four. It was the two sites that had diesels running and two others. And when maintenance stays overnight they...stay in a camper...When you have maintenance on the site and they’re going to stay overnight, you have a security team on the site.

Figel to Robert Salas 08/11/1996


WF: [On the date of the Echo shutdowns we already had teams out in the field] because they were doing maintenance on, I don’t know, the guidance cans or something, and the maintenance crews were staying [overnight] and there was security and maintenance on-site on both, uh, on two of the ten sites.

RS: Uh-huh
In my previous Part I post, I postulated that only two Launch Facilities had maintenance crews on site, E-2 and E-8.  Figel tells Salas that he had maintenance teams on only two LFs, yet some twelve years later, Figel tells Hastings that he had maintenance teams on four of Echo's LFs, thus demonstrating that Figel's statements to Hastings probably were clouded and somewhat suspect based on the passage of time.  If Hastings had access to Figels statements as given to Salas, then he should have recognized this discrepancy and thus treated the contents of his own interview with caution. 

The key to understanding the "UFO" component is to understand what LFs were occupied by maintenance teams and what type of maintenance was being performed on 16 March.  So it is with the the possibility of faded memory that one has to look, as closely as possible, at the most important statements that Figel makes to Hastings:
WF: Uh, we did that with the sites that were there, that [had maintenance teams and their guards on site] and I sent Strike Teams to two other sites. There’s no sense sending them where I [already] have a guard and a gun and an authenticate.

WF: [Laughs] That’s correct. Um, somewhere along the way, um, one of the maintenance people—cause he didn’t know what was going on any place else either, they have no capability of talking to each other [at different launch sites], in other words, they can talk to the [launch] capsule but they can’t talk to each other—

RH: Right

WF: —unless they were on the radio and no one was using the radio except the security police. And the guy says, “We got a Channel 9 No-Go. It must be a UFO hovering over the site. I think I see one here.” [I said,] “Yeah, right, whatever. What were you drinking?” And he tried to convince me of something and I said, well, I basically, you know, didn’t believe him. [Laughs] I said, you know, we have to get somebody to look at this [No-Go]. [A short time later] one of the Strike Teams that went out, one of the two, claimed that they saw something over the site.
          RH: How did they describe that?


The above is an interesting exchange between Figel and Hastings, because the portion of the statement in bold is taken as gospel by Hastings demonstrating that the maintenance team "saw" a UFO.  If Hastings had known the actual physical layout of a typical Minuteman launch facility, he would have realized the fallacy of his interpretation of Figel's statements.  The maintenance team was deep inside of the LF/missile silo with no way to physically see anything in the sky above the site, especially with the launcher closure door securely in place over the top of the silo.  It can be concluded that the maintenance team was in the missile silo due to their use of the SIN line for communication to/from the the missile crew back in the Launch Control Center.  Figel is clear that this is how he had contacted the team.  Plus, the maintenance team was able to physically verify that the missile had shut down with a VRSA channel 9 No-Go...this can only be done while inside of the LF/silo itself.  Both maintenance team members would have had to be in close proximity to one another due to the LF being a No Lone Zone and the implementation of the SAC Two Man Policy rule.  The two security guards located topside on the LF never report seeing any object directly over the site.  They were the only individuals that were in position and could have visually verified such a sighting, yet there is no record stating that they saw anything, nor does Figel state to Hastings that he had received a radio report of such a sighting from any of the security guards on the two LFs.


Cut away view of Minuteman ICBM Launch Facility (LF).  Note:  Maintenance team in Figel's narrative would have been on the support equipment level.  Silo cover/door would have been in the closed position.  This shows that there is no physical possibilities that anyone inside of the LF could have seen an object above the topside of the LF.




WF:  ...[A short time later] one of the Strike Teams that went out, one of the two, claimed that they saw something over the site.

What site was Figel referring to?  He gives the impression that the Strike Team was at one of the two manned LFs with security already in place..."...the site.." rather than "...a site..."  But Figel tells Hastings that the Strike Teams were not dispatched to the LFs that already had security details on site and who had properly authenticated with either himself or Echo's Flight Security Controller (FSC) via VHF radio.  As of now, the Echo Flight Security Controller, who remains unknown, did not provide any information confirming what site or what Strike Team (primary or secondary) made the report to Figel.  The FSC would have been monitoring all VHF radio traffic in the flight area.



WF: Uh, we did that with the sites that were there, that [had maintenance teams and their guards on site] and I sent Strike Teams to two other sites. There’s no sense sending them where I [already] have a guard and a gun and an authenticate.

This begs the question, what two sites did the two Strike Teams investigate?  What of the six remaining sites in the flight?  As stated in the "Part I" post, it would not have been unreasonable for Delta or Oscar's Strike Teams to have assisted Echo.  If this did occur, what of any reports of any strange sightings at the remaining of Echo's LFs.  After all these years, nothing has surfaced that even remotely hints of any unusual sightings above or near those remaining LFs.  A Mobile Fire Team was dispactched from the November Flight area to investigate and found nothing unusual.
WF: Oh, on radio, [they said,] “There’s this large object hovering over the site!” I’ve always been a non-believer [in UFOs] so I said, “Right, sure you do.” [They responded,] “Yeah! Yeah, we do!” So, [I said,] “There’s two of you there, saying so, so write it down in your report.” [The Strike Team leader] said, “What do you want us to do?” [I said,] “Follow your checklist. Go to the site, open it up, and call me.”


RH: What was the demeanor of the guard you were talking to?


WF: Um, you know, I wouldn’t say panicked, or anything [like that]. I was thinking he was yanking my chain more than anything else.


RH: But he seemed to be serious to you?


WF: He seemed to be serious and I wasn’t taking him seriously.


RH: Alright. If it was a large object, did he describe the shape of the object?


WF: He just said a large round object.


RH: Directly over the LF?


WF: Directly over the site

Figel tells Hastings that he believed that the Strike Team was joking and again no specific site or location is given. 

(BREAK. Figel describes hearing from the maintenance man about his opening up the silo, going down into it, and reporting that even though the missile was offline, nothing was visually damaged or otherwise amiss at the site.)


RH: Did he describe the object leaving the scene?


WF: No. He never said anything about it again.

Was Figel referring to the maintenance team or the Strike Team, and what site is specified?  The only site that was not penetrated was E-08 (maintenance team still asleep in the on-site camper) so this would mean that E-08 was eventually penetrated and inspected by the on site maintenance team.  But keep in mind, the maintenance team that reported the UFO was at E-02 which was already penetrated prior to the sortie dropping off alert and they were in no physical position to visually verify any objects over the LF.  This leads to the conclusion that no one was in a position to "describe the object leaving the scene" and why "nothing was said about it again."

So far, all that Hastings provides is Figel's accounting of the incident.  What about Figel's crew commander, Eric Carlson?  According to Hastings, he had interviewed Eric Carlson two weeks prior to the interview with Figel.


WF: What did Eric [Carlson] have to say [about the shutdown incident]? (RH had interviewed Carlson two weeks earlier, on 10/6/08)



RH: Uh, he said that he couldn’t recall any UFO-involvement in the incident. He couldn’t remember if you had mentioned UFOs, one way or another. His son [James] has now [posted] on a blog, a web log, a couple of lengthy statements in which he defamed Salas, said Salas was a liar, [and said] there was nothing involving UFOs at Echo...



WF: Did Eric say anything else that was a discontinuity [relative to what I’ve said]?



RH: ...Well, I [told Eric] that you had [heard from] a guard or a maintenance person that there was an object above the site, which you’ve confirmed today—



WF: Yes.



RH: —And I asked Eric if he remembered any of that, and he said that he did not. And, um, I asked him why his son would have written this scathing, very negative summary, which I will send [to] you, about the event—



WF: That will be interesting.

As can be seen above, Eric Carlson told Hastings that no UFOs were mentioned or alluded to.  Figel may have been "uncomfortable" as evident by his asking Hastings, "Did Eric say anything else that was a discontinuity...?"  Does this mean that Figel was not told of the UFO story by the maintenance team?  Since Figel was talking directly to the team via SIN line (telephone hand set in the LCC), Carlson may not have heard the conversation that was taken place, since he would have been busy assessing the situation from the commander's console and relying solely on Figel to gain what ever information that could be had from the maintenance team.  In short, both may be right in their own individual assertions.

Though I am not aware if Robert Hastings has ever provided the complete contents of his telephone interview with Eric Carlson,  Carlson does provide a detailed accounting here.  Walter Figel's current views of the incident here

In conclusion, it has been shown that though UFOs were reported to Figel on at least two occasions, he never took these reports seriously.  To this very day, Figel believes that the maintenance and Strike teams were joking with him.  Eric Carlson has consistently maintained for the past 43 years that no UFOs were involved in the Echo Flight shutdowns.  Most importantly it has been shown that no individual mentioned in Figel's statements to Hastings could have been in the position to physically see a UFO.  Based upon Figel's statements to Robert Hastings, UFO activity could not have played a role in the shutdown of ten ICBMs in Echo Flight.

Thursday, December 16, 2010

Off Alert, Echo Flight, 0845: A Reconstruction...Part 1


During the morning of 16 March 1967, an unprecedented event occurred at the 341st SMW's Echo Flight, all ten of the flight's Launch Facilities (LFs) abruptly dropped off alert.  This incident would set in motion a large scale effort by SAC, the 341st SMW, and various support agencies to bring the sorties back up to alert status.   An investigation into the cause of the incident, lasting almost a year, would yield no definitive conclusion other than a "noise" pulse causation with characteristics similar to that of an EMP.  Much has been written and discussed about the Echo Flight shutdowns with speculations swirling around the statements made by Col Walter Figel, the Deputy Missile Combat Crew Commander on duty at Echo-01, and the possibility of UFO involvement.  With that said, the story of Echo Flight remains cloudy and lacking of clarity.  Figel and other often mentioned maintenance and security guards consistently frame the storyline, yet what of the others?  These individuals are referenced to, yet always remain in the shadows.  Some are known, but the majority remain unknown to this day.  Based upon numerous articles, the reader gets the sense that only Figel was on alert that morning and the crew commander, Eric Carlson, is mysteriously absent, soundly sleeping while the drama unfolds.  And what of the actual events, can the morning of 16 March 1967 be recreated on paper?  I believe that by combining relevant portions of Figel's statements and correlating the 341st SMW's Unit History narrative then some degree of clarity can be achieved.  By reviewing and analyzing Figel's and Eric Carlson's recollections and comparing the unit history reports, one sees both supporting and contradicting evidence of what actually happened on that morning, yet some form of clarity unfolds as the alert itself is recreated and we find that Eric Carlson plays a major part, as he should have, because after all he was the crew commander in charge of Echo Flight.

The Road to Echo

A short background and the setting of the table is needed to mentally place the day of the incident.  Echo-01, the Launch Control Facility was, and still is, located roughly between the small farming communities of Winifred and Hilger.  The time of travel, from base to the site, would have been approximately two hours, barring weather and road conditions.  Back at Malmstrom, all of the squadron crews would have met for their pre-depature briefing starting at 0700 with actual departure to their respective sites between 0800 and 0830. The road to Echo would have taken the missile crews south easterly passing through Belt, Stanford and eventually to Lewistown, transversing the 10 SMS and a portion of the 490 SMS's Mike Flight.  From Lewistown, the crew would turn and head due north passing through Hilger and eventually taking a county road heading due west and finally arriving at Echo-01.

The 341st SMW had three operational squadrons in 1967, the 10th, 12th, and 490th Strategic Missile Squadrons.  The 564th was soon to be operational with its new Minuteman II LGM-30F) missile and Sylvania designed Launch Control Center, but as of March 1967 its sorties were yet to be placed on active alert status.  Numerous civilian contractors were spread throughout the wing's Launch Facilities installing and integrating new hardened HF antennas.  There is no documentation that shows such contractors on any of Echo's ten LFs on 16 March.  With the exception of the 564th SMS, the three active squadrons employed the Minuteman IA (LGM-30A) missile which would remain in service until the three squadron's upgraded to the Minuteman II in 1972.

Echo Launch Control Center:  15-16 March 1967

Carlson and Figel started their alert duty on the late morning of 15 March.  It's not readily known which crew that they changed over with and taking over the alert.  Leading up to 0845 on 16 March, the alert appears to have been uneventful with all 10 of Echo's LFs showing strategic alert.  On the commander's console the Launcher Status Missile Indicator Panel (LSMIP) would have displayed ten green lighted indicators annotating "Strategic Alert.'' Two of Echo's LFs had maintenance teams on site with the following status annotated on the LSMIP:

E-02: Strat Alert, OZ/IZ illuminated, Mnx on site due to failure of secondary door actuating motor.  Site penetrated by team, two security guards topside.

E-08:  Strat Alert, Fault indicator illuminated, active VRSA 26 (site on diesel generator), OZ illuminated hard or cycling, Mnx on site, two security guards topside with Mnx team in rest status in on-site camper.


Launcher Status Missile Indicator Panel at Commander's console


Note to readers: 


OZ, Outer zone security motion detection system covering the topside of the Launch Facility, particularly covering the launcher closure door, personnel access hatch, and the below ground Soft Support Equipment Building which housed the diesel generator, equipment cooling air system and other support equipment.

IZ, Inner zone security system that covered the inside of the Launch Facility/missile silo.


Eric Carlson was in bed asleep in the early morning hours.  Figel was awake monitoring the alert since he had taken the first sleep shift.  Figel had the LCC lighting set for "dark running" with only the emergency lights illuminated. No message traffic was being transmitted on the Primary Alerting System (PAS) nor was there active traffic on the 487L communication equipment.  All command and control components and equipment were operating without incident.

There is a question as to when Figel woke Carlson.  There are two possibilities, either Figel woke Carlson as was previously requested prior to Carlson starting his sleep shift, or Figel awoke Carlson after the first fault indication and alarm had sounded from the commander's console.  Based upon an interview with Carlson, an assumption could be made that Figel probably woke Carlson at a requested time and was briefing him on the current status of the flight which coincided with the initial sortie dropping off alert.

0845 16 March 1967

The first alarm sounded approximately at 0845 with E-08 dropping off alert.  On the LSMIP, on the commander's console, E-08 would have shown no "alert" indicator illuminated and only the previous fault indicator illuminated for the active VRSA 26.  Figel, per T.O. (Technical Order) checklist procedure was at the deputy commander's console interrogating VRSA for any new active reporting channels for E-08 and would have received the following voice report, "VRSA channel 9...VRSA channel 26...all channels monitored."  The T.O. would have listed the channel 9 report as an LF No-Go situation affecting the missiles guidance and control.  While Figel was busy with VRSA, Carlson was facing the commander's console and saw the rest of Echo's LFs drop from "strategic alert" to "fault" with audible alarms sounding for each consecutive sortie dropping off of alert status.  The crew would then have checked on the VRSA reporting for the rest of the nine LFs receiving active VRSA channel 9s.  The role of the deputy commander was to handle any VRSA requirements.  Eric Carlson, as crew commander, delegated which crew member was to be responsible for contacting the maintenance teams, the Flight Security Controller (FSC), Wing Job Control, and other command elements.  All of the crew actions were dictated by various checklists outlined in the weapon system Technical Manual/Technical Order (T.O.).  Both crew members each had a personal copy of the T.O.


Minuteman I Enable and VRSA Panel at Deputy Commander's console


It is estimated that all ten sorties dropped off alert within a 10 to 40 second time interval.  Carlson noticed that for each LF, none of them dropped into "standby" mode due to the lack of any white light "standby" indicators illuminating.  This would have indicated that the missiles would have started an internal calibration sequence.  Under some circumstances, a missile might drop automatically into "standby" and stay for an extended time in calibration mode and then eventually drop into an LF No-Go condition.  With specific fault and VRSA indications, the crew would command the sortie to drop into calibration mode possibly averting a No-Go situation, but in the case of Echo, there would have been no time to initiate such a command.  There were no flickering of any other indicator lights on the panel, nor did any of the LCC lighting dim.
 
From statements made later by Figel, he contacted the maintenance team on E-08 via VHF radio.  One of the security guards reported to Figel that the maintenance team was still asleep in the camper which was situated on the LF.  Figel stated that he had the guard authenticate though the authentication process with security personnel would normally have been accomplished by the on duty Flight Security Controller (FSC) top side in the LCF.  Once the maintenance team chief had awoken, Figel would have had him authenticate.  It can be assumed that both members on the LF authenticated properly since no security situation was declared for E-08 itself.  Since E-08 was not penetrated (B-plug was not lowered down and no hard IZ alarm illuminated on the LSMIP), there was no way that the maintenance team could have verified the E-08 was indeed off alert with a channel 9 No-Go.  It would have taken approximately 20 to 30 minutes to lower the B-plug and gain access internally to the LF.


Topside view of Minuteman Launch Facility.  Note the Launcher Closure Door and at the bottom of the photo the Soft Support Building housing diesel generator and equipment cooling air system


After dealing with E-08, Figel turned his attention to E-02.  Figel contacted the maintenance team chief via the Secure Intersite Network (SIN) line.  Both maintenance members were inside the LF proper, possibly repairing/replacing the secondary door actuating motor.  It can be assumed that Figel had the team chief authenticate and then explained the indications that he had received back from the LF.  The maintenance team was in position to verify that E-02 had an active VRSA channel 9 No-Go.  It is at this point where controversy begins as one of the maintenance team members verifies the active channel 9 and then, per Figel's statements, makes the following reply on the SIN line:

“We got a Channel 9 No-Go. It must be a UFO hovering over the site. I think I see one here.”

Figel took this as a joke and continued with his checklist procedures.  Why did Figel believe this to be a joke?  The maintenance team was calling from inside the LF/silo.  Figel makes it clear that the communication was conducted via SIN line, which is only located inside of the LF and the Soft Support Equipment Building (also located underground).  Due to SAC Two-Man Policy and the internal portion of the LF being a No Lone Zone, both team members would have been in eye contact of each other.  Since the team was able to physically confirm the VRSA channel 9 condition, this means that they were definitely inside the LF and not in the Soft Support Building.



Ariel view of a Launch Facility

With both crew members following their respective T.O. (Tech Order) checklist, it appears that Carlson would have been the one making the required notifications.  Carlson's first call would have been to Wing Job Control (WJC) reporting the indications and active VRSA channel 9s.   The WJC  controller would have declared that all sorties were "officially" listed as off of Strategic Alert.  The controller would have provided Carlson with his initials which Carlson would have written down on his crew log.  The controller, enlisted rank, would have immediately notified the OIC of Wing Job Control who in turn would have placed an urgent call to the Deputy Commander for Maintenance (DCM.)

Carlson's next call would have been to the Wing Command Post (WCP) relaying that all of Echo's sorties were off of Strategic Alert.  The command post controller would have annotated his status board with the fault indications and provided his initials for Carlson's crew log.  The WCP would have then notified the wing's Deputy Commander for Operations (DO) and then reported the situation to the Wing Commander.  The information would have immediately been channeled up to 15th Air Force's and SAC's command post listing Echo's sorties as off of alert.  Due to the unusual number of LFs involved, the information would have immediately been sent to CINCSAC.  All of this would have occurred within a matter of minutes.  Carlson would later recall that he received a call from a SAC general verifying that Echoes sorties were not launch capable.

Carson and/or Figel would have notified Alph-01, the 10th SMS's squadron command post' notifying the crew of Echo's situation.  The missile crew at Alpha would have then called the 490th SMS's Kilo-01, the Alternate Wing Command Post.  The Kilo crew would have annotated in their logs that all ten of Echo's sorties were off alert.  By then the 10th's squadron commander and operations officer would have been aware of the situation, as well as, the Echo Flight Commander.

If not done so earlier, the Echo crew would have declared a flight-wide security situation.  Echo's FSC would have dispatched both the primary and secondary SATs to investigate the 8 LFs that were not manned.  Though its unclear, a Mobile Fire Team (MFT) located in the November Flight area was requested to check for unusual activity.  The MFT may have been asked to leave their location and render assistance to Echo's two SATs.  It would not have been unreasonable for Delta or Oscar to send one of their SAT teams to provide further assistance.   Though there is no supporting documentation, it is reasonable to assume that one or two Flight Security Officers may have been nearby to render assistance.

By 12 noon, Carlson and Figel would have relinquished the alert to the new on-coming crew.  Once the change over briefing was accomplished and the classified documents were inventoried, the on-coming crew would  handled and monitored the rest of the flight activities.  Carlson and Figel would then have driven back to Malmstrom arriving approximately two hours later.  While they were en route back to base, plans would have been in the process of being devised to bring the sorties back up to operational alert status. SAC would started the planning stage to investigate the shutdowns.  Even though the Echo incident was classified, per Eric Carlson, by the following day, most people in the field, on the base and in the city of Great Falls knew what had happened at Echo.

I can't affirm that this is how the morning went exactly for Eric Carlson and Walter Figel, but based upon the available documentation and statements, I believe that it comes close.  Figel would later tell Robert Hastings that there were maintenance teams on three or four of his LFs, yet based upon current documentation, there were only two LFs with maintenance teams on site.  Where others concentrate strictly on Figel's actions and statements, I've been able to bring Eric Carlson appropriately into the picture...taking command of his flight...Echo Flight.

Note:  I briefly introduced the UFO controversy.  As most know, Figel made statements about his SAT strike teams making claims of UFO sightings.  Those claims will be analyzed, in detail, in a follow on Part II posting.

References:

Robert Hastings, "Did UFOs Cause the Shutdown of ICBMs at Malmstrom AFB, in March 1967?" 12/22/2008

Ryan Dube, Reality Uncovered, "An Interview with Malmstrom AFB Witness Eric Carlson", 09/12/2010