Showing posts with label USAF. Show all posts
Showing posts with label USAF. Show all posts

Monday, September 11, 2017

Former USAF Missile Security Policeman Tells of Apparent UFO Abduction at ICBM Site

UFO Over November LF (Silo)
Bookmark and Share

     Over the past 44 years I have interviewed more than 160 U.S. military veterans regarding their involvement in nuclear weapons-related UFO incidents. For an overview of their testimony please view CNN’s live-streamed coverage of my September 27, 2010 press conference, or watch my documentary film or read my book. Declassified documents relating to some of these incidents are also available.

Many of the cases occurred at Minuteman Intercontinental

By Robert Hastings
The UFO Chronicles
8-8-17
Ballistic Missile (ICBM) sites during the Cold War era. Typically, a two-man team of missile launch officers at an underground Launch Control Center (LCC) would receive an alarm on their missile-status console, indicating a possible security breach at one of the ten, widely-scattered Launch Facilities (LFs) they controlled. A two-man Security Alert Team (SAT) would then be dispatched to that location to investigate.

Usually, upon arriving at the LF—commonly known as a “silo”—the SAT team would observe a UFO silently hovering directly over the site at low altitude. Depending on the case, the aerial object was described as a disc-shaped, or spherical, or triangular, or cylindrical-shaped craft. After a few seconds, the craft would leave the vicinity, typically at high speed. On occasion, as revealed by former missile maintenance personnel, the functionality of the ICBM would be disrupted during the incident, whether deliberately or inadvertently, requiring lengthy repairs.

In every case reported to me over the years, the SAT team members were debriefed upon returning to base and sternly warned never to discuss the incident. Sometimes they were required to sign national security non-disclosure forms which stipulated severe legal penalties for violating secrecy. Often, each team member was quickly transferred to another base, without his partner, probably to prevent them from discussing their experience between themselves and spreading stories about it within their squadron.

Recently, one such case was brought to my attention which appears to be far more dramatic in nature, in terms of its immediate and long-term impact on the security personnel involved. Indeed, based on the available information, it seems probable that the SAT team members were actually abducted by those aboard the UFO and transported—along with their vehicle—to a location some five miles away, where they were eventually discovered by other Air Force security teams.

What follows here is the written summary of that incident provided to me by USAF veteran Mario A. Woods Jr. who was stationed at Ellsworth AFB, South Dakota, from 1975 to 1979, as a member of the 44th Security Police Squadron. The narrative has been edited for the purpose of brevity and clarity:
In November 1977, while assigned to the November Flight Launch Control Facility (LCF), I was a Security Alert Team member on the night shift—6:00 p.m. to 6:00 a.m.—paired with Sgt. Michael -------, who outranked me thus making him the team leader. I'm not certain of the exact date but Thanksgiving was approximately two weeks later and, as a newlywed, I was looking forward to being home with my wife. On that particular night it was clear and very cold and the ground was spotted in snow.

While at the LCF, I walked outside several times to stretch my legs, have a cigarette, and look at the stars. The clarity of the sky in South Dakota is like you've never seen. We were positioned just a few miles north of the small town of Newell.

On one occasion—I really didn't look at the time but I'm guessing it was around midnight—I noticed a very bright star that I had not seen before. I first thought it was a large helicopter or a B-52 bomber flying one of the low-altitude sorties they sometimes did out on the prairies, but it was not. It was hovering at about a 30-degrees above the horizon. The way it shimmered and pulsated led me to continue to watch it for some time, say 20 minutes.

I eventually walked back inside the LCF and made a comment about it to Sgt. -------. He laughed and said, ‘Sure’, whatever that meant. Then I told the Flight Security Controller (FSC), who acts as a go-between the response team and the Missile Capsule Crew Officers below ground. The FSC also keeps Wing Security Control (WSC) back at Ellsworth apprised of all activities on-site.

After perhaps 30 minutes, I walked back outside and saw no star so I thought, ‘Okay, it was a plane or helicopter.’ But as soon as I said that to myself, it lit up again, not quite in the same place but at the same elevation and more north. So, instead of being due east of my location, it was more northeast.

I thought for a minute and, all of a sudden, got the idea to flash the facility lights off and on as a signal. Why? I don't know. I guess because that's what is done at sea, from ship-to-ship. My father was a merchant seaman and I had sailed with him in my youth.

So, anyway, the LCF had approximately 15 sets of super bright spotlights, located on all four corners of the security perimeter fence and along the roofline of the main building—all controlled by one switch in the FSC's office. I walked inside and told the FSC what I was doing and he laughed at me. I think it was SSgt. ---- --------- from North Carolina. He said go ahead so I proceeded to flash the facility lights at this object, not knowing if it was anything unusual or just a plane or chopper doing night flying.

I was not following any particular sequence, like an SOS or anything like that. My SAT team partner, Sgt. -------, got curious and after I had flashed the lights six to eight times we walked outside together to look at the object. There it was, no change in its appearance or position but, a moment or two after ------- made some comment about the light, it went out! The night sky was clear as a bell, so I know it hadn’t gone behind a cloud. But ------- went inside, laughing at me. I somehow knew I needed to keep watching the sky and, just like that, it re-appeared to the north and seemed closer, as it was brighter.

I turned and walked in and flashed the facility lights six to eight times again and told them both about the object’s new position. Neither took me seriously. I then went outside one last time but the object was gone. So I went back inside, thinking how strange all that had been and feeling stupid about flashing the facility lights at it. I went into the day room and sat down to read or watch some TV.

At approximately 0130hrs we received a [Situation]-4 alert from LF November-5, which was the closest to our LCF and also closest to the town of Newell. Sgt. ------- and I donned our heavy winter parkas and cold weather gear and I placed my ditty bag in the F-150 pick-up police vehicle. I then went back inside to receive our USKAPP 55 code tables, weapons and ammo from the FSC and our safety briefing from the LCC crew underground. WSC back at Ellsworth was also contacted and our estimated travel time to and from the site was discussed.

A Sit-4 meant that the outer zone antenna on the missile site and the underground soft support building had been penetrated or had alarmed for some unknown reason. That was no problem as I had done this type of clearing and reset procedure many times at other locations.

We left the LCF and headed toward Highway 79. I was in the passenger seat and, as we were nearing the highway, I looked off in the distance and could see that the bright object was apparently near the missile site, which was seven or eight miles away. I immediately turned to Sgt. ------- and said, ‘Look man, that light is over November-5!’ He replied, ‘No way!’ but I could see his face and he was hoping not!

We didn't inform anyone about that on the radio, to the best of my knowledge, but I continued to view the object. As we approached Newell we made a right turn onto the road that led to November-5. As we did, we immediately saw the object hovering directly over the site. It made no noise and was a huge glowing, reddish-orange sphere. It was only 15-20 feet above the ground and it was roughly the width of a Wal-Mart building! I’ve thought a lot about its size and I think that estimate is fairly accurate. It was enormous!

Its surface was shimmering with the red and orange colors constantly swirling and churning. When I recently watched your documentary film [UFOs and Nukes: The Secret Link Revealed] there’s one scene where a [computer-generated image of a] UFO is hovering over the front gate of an LCF at Malmstrom AFB and its colors are swirling around. What we saw looked just like that.

We stopped the vehicle and sat some distance from the security gate. There was no radio communication as neither of us really knew what to do. As we stared at this thing—it seemed like forever—all of a sudden I could not breathe, I mean I really could not breathe! It was like pressure on my chest. I could not figure out what was happening and turned to look at ------- and saw that both his hands were on the steering wheel and he was looking straight ahead with a blank stare on his face. Some kind of glow was all around him and I noticed that suddenly he too was gasping for air.

I carried a three D-cell Mag Light, a huge flashlight by today’s standards but the best back then. All I wanted was relief for me and him so, for some reason, I rolled the window down and pulled myself out and sat on the window frame and flashed the light at this object until the suffocating pressure seemed to go away. Then, after 15 to 30 seconds, I slid back into the seat. I remember my M-16 weapon was positioned between my legs so I guess I grabbed it as I sat back down.

At that point I didn't look at Sgt. ------- as I was in some kind of daze. But I saw something like shadows on the right side of the vehicle and I have a memory of voices in my head, more than one, saying , ‘Do not fear’, over and over. I think I remember small figures, maybe five or six, walking toward the vehicle. Standing behind them was a taller figure who I think was in charge. Then I believe I passed out.

The next thing I remember—and it seemed as if only a minute had passed—was the crackle of our radio and someone saying, ‘November-1, what’s your status?’ I turned to Sgt. ------- and said, ‘You get that and I’ll strike the site,’ but he said nothing. He simply stared off into the distance so I picked up the mike and informed our FSC that we would begin the strike and were positioning the vehicle. There was a long pause and then he came back and said, ‘Where are you located?’

This response seemed very odd and I said something to Sgt. ------- but again he said nothing. I asked the FSC to hold on as I didn't see the facility lights that were normally on at night. I put the mike down and stepped out of the vehicle only to find that we were somewhere other than at November-5. My first step was into wet mud; even though it had been really cold that night and the ground should have been frozen solid, the entire area was soft mud and our vehicle was almost in the middle of it.

But to my right, just feet away, was a tall concrete wall of some kind. The sun was just coming up and I could see that it was a dam that held water in a reservoir. It turned out to be located north of Newell, and is called Newell Lake, quite a few miles from the LF. We were parked next to a road that went past it. That made no sense to me!

The radio came back on and we were told to stay where we were. Our radio signal had been triangulated—something I knew very little about—and then the WSC came on and told me that our sister flights’ SAT teams had been dispatched to find us. A back-up sister team reached us first and I was told to follow them to the edge of their patrol boundary where we would be met by our November-1 back-up team.

When their vehicle arrived, I started asking them questions about what was going on but they told me that they had been ordered not to discuss the situation with us. I again tried speaking to Sgt. -------. I kept asking him if he was okay but he still would not respond.

Then it hit me like a chunk of lead: We or I never went onto the November-5 site! I didn’t understand why at that moment but I was certain that we never got past the LF’s security gate.

Because he was still just staring into space, I moved ------- over to the passenger seat; he was not a large man and I was in good shape. We maintained [radio] security checks for the entire ride back, met up with the sister team and proceeded to November Control.

The Flight Chief, MSgt ----- ------, and Assistant Flight Chief, TSgt. ---- ------, met us at the facility for a debrief. Sgt. ------- was in a pitiful condition and I later heard that he couldn't tell them anything; that he made no sense at all. He was removed from November Control and assigned to base duty for some time. Me, however, I remembered everything up to hearing voices and blacking out and everything after coming to and standing in the mud. Everything: the craft, the suffocating atmosphere, flashing lights at the object, not going onto the site and, yes, thinking only minutes had passed from first seeing this thing to being somewhere else.

During debriefing, I was told that nearly four hours had passed and that six security police back-up Alert teams had been searching for us. I did fill out an AF Form 1000 UFO sighting report and wrote all I knew about that night and early morning, before I was allowed to sleep.

The next day, I returned to Ellsworth and was interviewed by the 44th Missile Wing commander. There was a guy in civilian clothing with him who I think was from the [Office of Special Investigations]. Then I was also ordered to take a urinalysis at the base hospital, and two skin samples were taken—one from the back of my right hand and another above my right eyebrow—as I was sunburned for some strange reason.

Back home, as I slowly came to grips with all of this, I began to have strange dreams of that night. Every time, as something was about to happen or show itself, a great dread came over me. I would awake in a pool of sweat and afraid.

Two weeks went by and Sgt. ------- came by my apartment, out of the blue, and we sat down and talked about the incident in front of my wife. She just laughed at us. But he said one thing I’ll never forget: He had been terrified during the incident but didn't know why, as he had heard voices, many voices, saying not to be afraid. But he wasn't in the vehicle when he heard them, he was lying down somewhere.

Then he said something that shocked me: He said he saw my mittens on the floor, next to where he was lying down, as he was hearing the voices. I reeled when I heard this! It meant that I was probably there with him and that we were no longer in the vehicle. I had not even thought about the mittens after that night—those heavy Air Force-issue gloves with open fingers, so you could fire a weapon—but, when he said that, I ran to my ditty bag to check and they were not there. I got shivers when I saw that. I can’t explain why I didn’t miss them.

One more thing: I have two small puncture marks on my skin that I can’t explain. They’re identical; a perfectly round depression with a raised dimple in the center. One is under my left armpit and the other is on my left foot, above the ankle. I don’t remember any time or situation when I could have gotten them. (Woods subsequently sent me photos of these marks.)

After a few weeks, I was removed from November Control and reassigned to Kilo Control near Sturgis, South Dakota. I had the sense that I could pick that object out of the sky, find it among the stars, even at Kilo—it made no difference where I was—but I never saw it close up again. But it was out there visiting all of our bases. We heard stories about other flights seeing things near the LFs on many occasions. Also, National Enquirer had heard rumors about UFO activity in our region and was patrolling our areas looking for stories. We were told never to speak with anyone about any of this so I never did, as ordered.

Sgt. ------- was transferred somewhere else a month or so after the incident. I found out somehow. I remained at Kilo Command, working with a different guy, Sgt. --- -------, as a SAT team member, then leader, and then FSC. Stories about sightings were all over the missile complexes, even reports of cattle mutilations; I once saw two of the dead cows myself while traveling to Kilo-1.

Later in the year, when Close Encounters [of the Third Kind] came out, the mailbox scene freaked me out so badly that I had to get up and walk out of the theatre. (In the movie, Richard Dreyfuss’ character, Roy Neary, looks out his parked truck’s window and sees a rack of mailboxes violently shaking. A moment later, a UFO that had been hovering over him directs a beam of light onto his vehicle.)
Having spoken with Woods a number of times, I consider his recollections of his experience to be credible if incomplete. I of course have his DD-214 service record, which confirms his presence at Ellsworth AFB in 1977 and his service as a missile security policeman. I am attempting to locate others who were present that night, to see whether any of them remember the events he describes and, if so, are willing to talk about them.

Also, although the technique remains controversial, I have arranged for hypnotic regression sessions for Woods, to attempt to draw out still-suppressed or long forgotten memories about the incident. For example, I am curious to know whether he can remember his SAT team partner driving them to the reservoir, in a dazed state following their sighting at November-5, or whether the UFO had actually lifted and transported the security vehicle to that location. And, of course, it would be interesting to learn whether Mario Woods’ memories of voices and small figures approaching his security vehicle might be augmented via the regression technique.

A follow-up article is planned, to update interested readers on this matter.

Thursday, July 06, 2017

UFO Files Exclusive: Cold War Spyplane Incident

UFO Files Exclusive: Cold War Spyplane Incident

     The release by Britain’s Ministry of Defence of 15 of its last remaining UFO files at the UK’s National Archives has revealed details of a stunning Cold War close encounter witnessed by the entire crew of a US Air Force spy-plane.

Formerly secret RAF files opened at The National Archives include a detailed account of an incident on 19 October 1982 when a USAF RC-135 plane, monitoring Soviet military activity, was buzzed by ‘a big object’ over the Eastern Mediterranean.
David Clarke
By David Clarke
ddrdavidclarke.co.uk
6-30-17

According to the files, British personnel at RAF Troodos, a remote base on the island of Cyprus listened in amazement to the radio calls of the American crew as the encounter unfolded at 35,000 feet above the sea.

The UFO – – described as covered in ‘a multitude of flashing lights 20 at a time’ – was picked up on the spylane’s radar as it approached from the south.

It then circled around the plane, call-sign Beano 73 – and closed in as the navigator appealed for help from the ground.

Two US Navy F-14 fighters were scrambled from an aircraft carrier and a RAF Phantom was diverted from a night flying exercise to intercept the UFO, south of the island of Cyprus.

As the three interceptors approached the USAF crew saw the UFO depart towards the African coast. Nothing was seen by the fighter pilots.

The files reveal how RAF personnel at the Troodos radar station monitored the entire incident for a period of 90 minutes, beginning shortly after 4pm local time.

Radome at RAF Troödos Station
Radome at 280 Signals Unit base, RAF Troodos, Mt Olympus, Cyprus – one of the most important overseas British installations (credit: Wikipedia/Ed Weissman)
But nothing was seen by British air defence stations – ‘nor was it seen on any ground or seaborne radar, including at 280 SU [280 Signals Unit – RAF Troodos]’.

Following the encounter a secret investigation was launched by the British authorities. The results were sent to the US Department of Defense in November 1982.

Neither the British or US government have ever released information about this incident before the files were opened this week.

Officially the US Air Force’s UFO Project, Blue Book, was closed in 1969. The British Ministry of Defence closed its own UFO desk in 2009 and its secret space intelligence unit, DI55, said it was no longer interested in ‘unidentified aerial phenomena’ (UAP) in 2000.

But the newly-released RAF file reveals that officials ordered a transcript to be made of the tape recording that captured radio transmissions made between the spyplane crew and ground controllers.

Copies of the report were circulated to Assistant Chief Scientist (RAF), DD Ops (GE) RAF, DI55 and DSTI.

Film provided by the RAF Troodos radar station was carefully studied by photographic experts in London and large prints, taken from the radar picture, were prepared for scrutiny by intelligence officers.

The file does not reveal what happened to this evidence. The results of the joint UK/US investigation do not appear in the file.

RAF File - Cold War spyplane incident
An extract from the RAF file on the incident [David Clarke/The National Archives]

But a tentative explanation is offered by a senior RAF official, who wrote: ‘We have a strong suspicion that the “UFO” was a mirage effect from lights on the coast of Israel or Lebanon’.

A signal reporting the sighting sent from RAF Troodos to MoD UK on 20 October describes the UFO as ‘larger than [a] RC-135’.

Boeing RC-135 aircraft are used by the USAF and RAF to support intelligence gathering. They have been used in every armed conflict including Cold War operations around the borders of the former Soviet Union. The aircraft are 136ft (41m) in length with a wingspan of 130ft (nearly 40m).

The RAF signal reporting the encounter says the ‘object’ was first spotted:
“…initially about two miles from wing of RC-135…moved position around aircraft and closed…object tailed Beano 73 for 90 mins on its northeast/southwest race track….”
The signal says the UFO was seen by the ‘whole crew’.

Three RC-135s were purchased by the RAF in 2017 to serve with 51 Squadron based at RAF Waddington in Lincolnshire. The crew includes two pilots, a navigator and up to 25 mission staff.

Elsewhere in the file a RAF Group Captain collated information on UFO reports received by his air defence staff for a thirty year period ending in 1996, in response to a Parliamentary Question from the Labour MP for Don Valley, Martin Redmond.

He asked all radar stations including the Ballistic Missile Early Warning Station at RAF Fylingdales on the North York Moors to submit UFO data to HQ No 11 Group.

His report says he could find “no reports or mention [was] found of UFOs detected by ADGE [Air Defence Ground Environment] units or 11/18 Group aircraft using radar equipment“.

Monday, July 03, 2017

MoD X-File Reveals a Terrifying UFO Encounter; F-14 Fighters Were Scrambled

Bookmark and Share

MoD X-File Reveals a Terrifying UFO Encounter
A TERRIFYING Cold War near miss witnessed by an entire crew of a US Air Force spy plane has been laid bare in a UFO dossier.
     The once top secret file was released by the Ministry of Defence last week, along with several other declassified documents.
By The Sun
6-30-17

They include the gripping account of an unexplained incident on 19 October 1982 when a USAF RC-135 plane snooping on Soviet military activity was buzzed by “a big object” over the Med.

British troops stationed at RAF Troodos – a base on Cyprus – listened in as the American crew called for help as a UFO cloaked in “a multitude of flashing lights, 20 at a time” zoned in.

During the 90 minute incident, two US Navy F-14 fighters were scrambled and an RAF Phantom was diverted from a flying exercise to tail the intruder spotted on the south of the island.

As the three jets approached the American crew watched the UFO turn away and head toward the African coast, but nothing was seen by the fighter pilots.

Wednesday, September 14, 2016

USAF Records Confirm 'UFO Activity' -Pt 2-

Bookmark and Share

Air Force Records Re UFOs and HMAS Hobart (4)
-click and or right click on image(s) to enlarge-

     In Part 1 of this series, I discussed the accidental missile strike on the Royal Australian Navy’s (RAN) HMAS Hobart by a United States Air Force (USAF) F–4 Phantom Fighter–Bomber in the early hours of June 17th, 1968. Specifically, I aimed to highlight that there has never really been official confirmation and consensus on what the jet was supposed to be firing on, and, that there was a possibility that the aerial targets it had in its sights were unusual and unidentifiable. The most sensible hypothesis has generally been that North Vietnamese M–14 Hound helicopters were flying in the vicinity of the Hobart, and that the F–4 Phantom made a dreadful targeting error.
Paul Dean
By Paul Dean
ufos-documenting-the-evidence.blogspot.com
8-11-16
However, in light of a series of recent discoveries, by both myself and Boston based researcher Barry Greenwood, this may not be the case. I have already gone to considerable length highlighting some never–before–seen information in one particular USAF record, which is titled Project CHECO South East Asia Report: Air War In The DMZ September 1967 – June 1968. Again, Part 1 of this series is worth looking at for those who haven’t.

Of course, no serious research project falls back on a single document. Anyone who knows my work will be well aware that I ceaselessly bring forth more, and more, and more, unseen government UFO records to the table. In this Part 2, I aim to present new, or barely known, records which relate to the HMAS Hobart incident. Moreover, there may be, unsurprisingly, a great deal more still–classified records relating to the incident that we simply do not have access to.

An important question which must be asked is that of terminology. Is the use of the term “UFO”, when used in Vietnam–era military records, merely a “catchall” for anything which is airborne and simply unknown to the observer? It would be easy to assume such is the case. However, time and time again we see the term “UFO”, or “Unidentified Flying Object” as distinctly referenced alongside terms like “unidentified aircraft”, “unknown aircraft” and the like.

One of the many examples of this distinction can be found in the individual line items found in a United States Marine Corps (USMC), Command Chronology” publication, titled “Command Chronology, Headquarters, 3erd Marine Division, 1st Amphibious Tractor Battalion, 1 June, 1968 to 30 June, 1968. In the “Sequential Listing of Significant Events” section of the document, there are pages of raw, tabulated text which discusses the daily activities of the 3erd Marine Division’s 1st Amphibious Tractor Battalion, in June, 1968. An entry for the 18th of June states:
Co "A" at C–4 position reported unidentified aircraft due east of C–4 position.
The very next line item states:
Elms Co "A" at Oceanview reported 6 UFOs vic of the mouth of the Ben Hai River
Note the distinction between the terms “unidentified aircraft” and “UFO”? Presumably, military observers would desire to use anything but the term “UFO”, yet we see it used time and time and again throughout all manner of such records.

Another (USMC) “Command Chronology” publication makes reference to ongoing UFO activity in the precise vicinity of where HMAS Hobart was patrolling, and only two nights beforehand. Titled III Marine Amphibious Force, Air Ground Team, Command Chronology, June 1968, it was printed by Headquarters, III Marine Amphibious Force, Military Assistance Command on the 9th of August, 1968. Originally classified “SECRET”, and only downgraded to “UNCLASSIFIED” in 2014, it is held, among thousands of similar publications, at the National Archives and Records Administration (NARA) in Washington DC. In a chapter titled “Intelligence”, there is this curious statement on Page 17:
During the late evening hours of 15 June approximately 15 unidentified aircraft, believed to be enemy helicopters, were reportedly sighted in the DMZ area. Since that time there have been numerous sightings, both visual and by radar, of unidentified, slow–moving UFO’s in the DMZ area and seaward toward Tiger Island. No hard evidence of these aircraft has yet been received.
So, even this USMC historical record – which was authored by utilising raw and classified records – states that “unidentified aircraft” on the 15th of June were only “believed” to be enemy helicopters. Beyond that, “numerous sightings” – seen both visually and on radar – of “unidentified, slow–moving UFO’s” around Tiger Island obviously were of concern. The date–range of these sightings, of course, lead right up to the accidental missile strike on HMAS Hobart. I have imaged the page above top. ...

Saturday, September 10, 2016

USAF Records Confirm 'UFO Activity' During Aerial Assault on The HMAS Hobart

Pt 1
Air Force Records Re UFOs and HMAS Hobart (1)
Air Force Records Re UFOs and HMAS Hobart (2)
- click and or or right click on image(s) to enlarge -

     On October the 16th, 1973, the United States Air Force’s (USAF) Chief of Staff, General George S. Brown, who was later appointed as the Chairman of the Joint Chiefs of Staff, delivered a press conference in Illinois. When the UFO matter was raised, Gen. Brown curiously stated:

“I don’t know whether this story has ever been told or not. They weren’t called UFOs. They were called enemy helicopters. And they were only seen at night and they were only seen in certain places. They were seen up around the DMZ in the early summer of ’68. And this resulted in quite a little battle. And in the course of this,
Paul Dean
By Paul Dean
ufos-documenting-the-evidence.blogspot.com
8-11-16
an Australian destroyer took a hit and we never found any enemy, we only found ourselves when this had all been sorted out. And this caused some shooting there, and there was no enemy at all involved but we always reacted…”

Candid statements like this were somewhat of a rarity in the 1970’s. The USAF had announced the closure of Project Blue Book in January, 1970, officially closing the doors in the Spring of 1970. But over in Vietnam, UFO reports were consistently being collected and investigated, in various forms, with the primary purpose being to determine whether or not these events were related to enemy activity. Often they were not.

Of all the reported sightings of unusual aerial activity, none have proved more controversial than those of June the 17th, 1968. There has been much written about this event, so further narrative is not needed beyond this brief summary. During the early hours of the morning, a Royal Australian Navy’s (RAN) guided missile destroyer, the HMAS Hobart, was patrolling the Demilitarised Zone (DMZ) near Tiger Island. A USAF F–4 Phantom Fighter–Bomber fired three missiles on unknown aerial targets, suspected to be North Vietnamese M–14 Hound helicopters. The missiles, however, struck HMAS Hobart, killing Ordinary Seaman R.J. Butterworth and Chief Electrician R.H. Hunt and wounding several others. This was, it seemed, a classic case of “friendly fire”, but rumours started filtering out that the F–4 Phantom hadn’t merely mistaken HMAS Hobart for offensive enemy helicopters, and, that unusual, unidentifiable aerial activity was the intended target. Some of those who were there even use the term “UFOs”.

Finding official USAF or RAN records which discuss this event is not too difficult. Finding the term “UFO” in such records is nigh impossible. Luckily, like so many pieces of history, nothing stays hidden for ever.

Recently, while painstakingly scouring through the online archives of America’s huge Defence Technical Information Center (DTIC) holdings, I honed in on a series of USAF publications which specifically discuss the UFO topic in relation to aerial activities during the Vietnam War. It’s no surprise that few unusual records – whether administrative in nature, or, actual reports – would be hiding in Vietnam War–era military documents. In fact, it would be very odd if there wasn’t – especially when one considers the gigantic quantity of material already begrudgingly released by the US government over the last forty years. Just last year, researcher Barry Greenwood discovered that the National Archives and Records Administration (NARA) had made available myriad Vietnam War files, including US Army records and thousands of pages of USAF “Combat Air Activities” (CACTA) papers – many of which contained references to UFO’s. The records Greenwood and I are finding are a variety of “Daily Staff Journals”, “Histories”, “Chronologies”, “Mission Reports” and so–called “Lessons Learned” publications. These files have only been declassified recently. We know there is much more which is apparently too sensitive to be released, even after forty years or more.

In the 1960’s the USAF ran “Project CHECO” which produced hundreds of detailed reports examining the USAF’s aerial operations in South East Asia. “CHECO” stands for “Contemporary Historical Examination of Current Operations”. Most of these reports have a standard introduction, which states:
“Project CHECO was established in 1962 to document and analyze air operations in Southeast Asia… …Project CHECO and other US Air Force Historical study programs provided the Air Force with timely and lasting corporate insights into operational, conceptual and doctrinal lessons from the war in SEA.”
The report that mentions the HMAS Hobart is titled Project CHECO South East Asia Report: Air War In The DMZ September 1967 – June 1968. It was produced by the 7th Air Force’s (7AF) Directorate of Tactical Evaluation, Headquarters, Pacific Air Forces (HQ PACAF), and was published on the 1st of August, 1969. Signed off by Col. Warren H. Peterson, the report was originally classified SECRET/AIR FORCE EYES ONLY, the report was only declassified on the 17th of August, 2006. In relation to the HMAS Hobart and UFO’s, on pages forty–five and forty–six it states:
“The several direct hits or near misses on friendly vessels by the Air Force missiles obviously raised the question of what went wrong with target acquisition. The pilots, based on their radar and visual sightings, fired at what they thought were helicopters. The joint service conference on the UFO problem took note of one possibility…”
This passage ends with an endnote, namely, number “128”. The next passage of text is a quote taken directly from raw USAF records, and it states:
“It is important to note that only in the case of the Hobart were the recorded targets in close proximity to ships. It is possible that targets fired on were airborne and that missiles subsequently [were] guided on the stronger radar return from ships in the vicinity.”
(I have imaged, above, top, the two pages that contain this startling text).

It is important to reiterate that the information used by the author of this Project CHECO report was sourced directly from two raw USAF documents. These are listed under endnote 128 at the end of the report. They are titled “20 June Helicopter Conference” and “Memo, Brig Gen George W. McLaughlin, TACC, 7AF to Comdr, 7AF, ‘Air Attacks on Naval Surface Vessels’, 18 Jun 68”. Both are listed with an “(S)” next to them, meaning they were, and probably still are, classified SECRET.

As for the text itself, the first sentence highlights the issue of faulty target acquisition and the accidental hits on HMAS Hobart. The second sentence indicates the pilots of the USAF combat jets had a mix of “radar and visual sightings” and fired on “what they thought were helicopters”. But it is the third sentence where things get interesting. Note that it reads, “The joint service conference on the UFO problem took note of one possibility…”. Clearly stated here is that there was a “conference” on the “UFO problem”, and a “joint services” conference at that. This may mean that all branches of the US armed forces attended, not just components of the USAF. More importantly, the “UFO problem” strongly indicates that there was an ongoing issue with UFO’s in the region; which is what weary UFO researchers have been saying for years.

The next passage of text, quoted from raw administrative records, discusses HMAS Hobart directly. Key here are the sections that read “…only in the case of the Hobart were the recorded targets…” and “It is possible that targets fired on were airborne…”.

Questions need to be raised here. The USAF’s official UFO study, “Project Blue Book”, which closed in 1970, was not being informed of this “UFO problem”. We know this because Project Blue Book files have been publicly available since 1976, and there are comparatively few Vietnam War sourced cases or investigations. As for the “UFOs” themselves, it could be argued that the term “UFO” was a catchphrase for all aerial oddities and unknown aircraft, but ’researchers experience with other caches of military documents often tells us the opposite. “UFOs” are often dealt with as distinct from helicopters, planes, flak, etc. Barry Greenwood’s work last year shows that there the term “UFO” was being used very regularly, including instances where the phrases “UFO landing” and “UFO chase” are used within combat and intelligence assessments.

Other questions must also be asked. Did the “joint service conference” on the “UFO problem” include Royal Australian Navy (RAN) officers? After all, it was an Australian ship that was struck. If so, where are those records? Were any technical studies completed by the USAF’s 7AF science and technology directorates? What about the source documents used in compiling this Project CHECO report, which, I state again, are listed on Page as “20 June Helicopter Conference” and “Memo, Brig Gen George W. McLaughlin, TACC, 7AF to Comdr, 7AF, ‘Air Attacks on Naval Surface Vessels’, 18 Jun 68”? One can only imagine how many records like this must be languishing – still classified – in permanent archives across the continental United States.

There are other overt references to UFO’s amongst the pages of Project CHECO South East Asia Report: Air War In The DMZ September 1967 – June 1968. On Page 47, it is stated:
“Another facet of target identification involved confirming the many visual, radar, and infrared sightings. No ‘hard evidence’ such as photographs or wreckage was obtained. On three successive August nights, RF–4s flew a total of 12 sorties against 34 radar–plotted UFO targets. The photos showed no helicopters despite several runs which, according to the radar, passed directly over the targets. On 28 August, an RF–4C using photo flash cartridges ran controlled tests to photograph a friendly helicopter at night. Of 38 exposed frames made on four passes, only two frames showed the helicopter. The summary of results to the 7AF Command Section said…”
The author then quotes directly from classified USAF records, which reads:
“This test confirms previous opinion by DOCR that chances of photographing one of the UFOs in the DMZ is extremely remote… …Even the two successful exposures required last minute flight correction by a DOCR representative riding in the lead helicopter.”
The page continues with:
“Two special projects were established to observe the UFOs from Con Thien, the highest hill in the eastern DMZ area. The primary mission of project HAVE FEAR did not concern the helicopter reports, but this Air Force Weapons Laboratory project had laser range finders and night observation devices (NOD) that offered some chance of identifying the sightings. HAVE FEAR personnel saw red lights and got video blips. The UFOs usually traveled at speeds from 30 to 80 mph at altitudes from 1,200 to 1,600 feet. After several days of tracking, the red blinking lights would extinguish when under HAVE FEAR surveillance. The project ran from 4–12 August 1968 and resumed from 18–31 August.”
Within the above text there are three endnote listed. Endnote 132 is listed as a document titled Msg, 7AF to COMUSMACV, ‘Summary Report of UFOs in DMZ, 19 Sep 68.”. Endnote 133, is listed as “Memo, Col Michael J. Quirk, DOC, 7AF, ‘Test–Night Photo of Helicopters,’ undated (About 30 Aug 68).”. The final endnote, 134, references a document titled “Msg, Det 1, 620th TCS to 7AF, ‘HAVE FEAR,’ 25 Aug 68; (S/NF) Memo, ‘Intelligence Annex (Enemy Helicopters),’ undated (Late Aug 68).”. This leaves no doubt that the content of the page was gleaned directly from raw, established USAF authority. The page in question is imaged below.

Air Force Records Re UFOs and HMAS Hobart (3)
- click and or right click on image(s) to enlarge -

So what can we take from this? The fact that USAF attempted to make sense of these elusive “visual, radar, and infrared sightings”, by organising the photographing of them, is something that we scarcely see in the established official record. The statement “…On three successive August nights, RF–4s flew a total of 12 sorties against 34 radar–plotted UFO targets” demonstrates clearly the urgency of the situation. The statement about the “…chances of photographing one of the UFOs in the DMZ is extremely remote…” indicates that a fair degree of discussion must have taken place over the matter. If that is not enough, note the passage of text which states “…two special projects were established to observe the UFOs…”. There is no question that something odd was going on. To use the frowned–upon term “UFO” so readily implies that US forces had few clues as to what they were visually witnessing and plotting on radar systems. Also, as I mentioned at the beginning of this entry, the term “UFO” is utilised as distinct from terms like “hostile aircraft”, “flak”, “rocket barrage”, “formation of planes” and so forth.

Most compelling is the fact that the author of this Project CHECO report was able to reference a classified document which, again I want to highlight, titled Msg, 7AF to COMUSMACV, "Summary Report of UFOs in DMZ," 19 Sep 68. Quite simply, this means that there was a 7th Air Force “Report Of UFOs in the DMZ”. There is most definitely no mention of this is the Project Blue Book files, which were supposed to be the last word on UFO’s by the USAF. It would be amazing if this was the only record of its type. Where are these raw records, and, more importantly, in what volume are they? As I have raised before, there was also a “joint service conference on the UFO problem” at nearly the same time.

These situations – where sensitive UFO–related records are found far outside Project Blue Book – keep coming up all the time. Anyone who clings to the notion that there is nothing more to be found, no more mysteries, no more classified files, is living in the early 1970’s. There always seems to be some recorded fact, some official opinion, or some unseen report that departs massively from the USAF’s public relations stance that UFO’s have never been an issue for national security or something worth seriously considering in future policy or plans.

In Part 2 of this series, I will present another bevy of US military documents, as well as some Australian records, that relate to the UFO matter in Vietnam, including, specifically, the strike on HMAS Hobart. Finally, I have imaged below the front page of Project CHECO South East Asia Report: Air War In The DMZ September 1967 – June 1968 to further establish the provenance of this hitherto classified paperwork.

Project Checo Report - Air War in The DMZ 1967-1968
- click and or right click on image(s) to enlarge -

Monday, August 08, 2016

USAF Considers Shooting Down a UFO with a Missile – 1952

USAF Considers Shooting Down a UFO with a Missile

Have we Visitors From Space – Life Magazine 1952

     Brigadier General William Garland in a 1952 Memorandum for Record (MFR) told a LIFE magazine researcher that the US Air Force had considered using a missile to shoot down a UFO.
By Jan L. Aldrich
Project 1947
8-7-16
Robert Powell, Scientific Director of the Mutual UFO Network (MUFON) found two MFR recording LIFE magazine researcher, Robert Ginna’s visit to the Pentagon in February 1952. Ginna met with a number of high ranking officers and intelligence officials gathering more research data for his article which was published in April. Among the general officers who helped him during his visit in addition to Brigadier General Garland were Brigadier Sory Smith, in charge of Public Information, and General Joseph F. Carroll, Deputy Inspector General and Director of Special Investigations. With their help, he was able to interview Lt. Col. Doyle Rees, for Commander of the 17th Air Force Office of Special Investigation, in New Mexico, and who had worked with Dr. Lincoln LaPaz, University of New Mexico expert on meteors. Both Dr. LaPaz and Lt. Col. Doyle Rees had investigated numerous UFO cases and green fire ball incidents in the southwest US. Also, involved in these meeting was Lt. Col. Dewitt Searles, public information UFO spokesman going back years, and a civilian Mrs. Helen Barber, managing editor of the classified internal publication, Air Intelligence Digest, who also figured in a number of Air Force Headquarters UFO investigations. General Garland arranged for a visit to the Air Technical Intelligence Center (ATIC) where Ginna could confer with Lieutenant Edward Ruppelt newly appointed chief of the USAF’s revitalized UFO investigative project which would shortly be renamed Project Blue Book. Read more at Project 1947….

Friday, January 23, 2015

Project Blue Book Declassified - Really?

Bookmark and Share

Project Blue Book Declassified - Really?

By Kevin Randle
A Different Perspective
1-20-15

"the only 'news' here is that John has provided us with another site where we can see these files"

      I’m watching the ABC Evening News, something I attempt to avoid because there is so little news in the broadcast (but that’s another story) and they tell me that the Project Blue Book files are now declassified and on line. I’m wondering what they mean because they have been on line for quite some time.

They’re referring to John Greenwald’s efforts to post all of these files at his Black Vault website, and his effort is commendable. But NICAP had many of the files on line for years and I have never found a gap in the Fold 3’s Blue Book files also on line. Or, in other words, the only “news” here is that John has provided us with another site where we can see these files.

ABC also seemed to suggest that this was something new. The Air Force had finally released all of the files of its investigation, except, of course, they did that in 1976. I made a trip down to Maxwell Air Force Base and spent time going through the files*. Anyone could have done it but the fact the files had been declassified hadn’t been announced publically. There had been some sort of announcement in an Air Force bulletin that I happened to see, so I made arrangements to take a look.

And once those files were transferred to the National Archives in Washington, D.C., they were more accessible to the public. You could buy the microfilm copies for something like eight or ten dollars a roll back then, but there were ninety some rolls of them. Over the years I actually managed to obtain a full set of the microfilms, so I’ve had all of the Blue Book files in my office for a couple of decades.

The statistics “announced” by ABC didn’t tell the whole story either, and they seemed to think Blue Book began as a result of the Roswell UFO crash (Roswell isn’t even mentioned in the Blue Book files except a short paragraph in a newspaper clipping that is part of another file), but actually the idea for an investigation can be traced back to December 1946 and probably had more to do with the Ghost Rockets of Sweden and some sightings in the US than it did with either Roswell or the Kenneth Arnold sightings. I laid this out in Government UFO Files, along with documentation to support the idea.

They said that 701 cases of the some 12,000 remained unidentified but the truth is that many of the cases are labeled, but not identified. These are labeled as “insufficient data for a scientific analysis.” In many of those cases all the information necessary for a complete investigation is included, but it is labeled that way. This was an attempt to reduce the number of unidentified cases by labeling them as something else and that is all that it was.

In addition to that, many cases that are labeled with a solution are clearly in error. For example, the Portage County UFO chase of 1966. (It was on April 17 and involved several police officers, deputy sheriffs and their supervisors and a stylized version was seen at the beginning of Close Encounters of the Third Kind. See also my posting here on May 20, 2014 for more information.). It has been explained as a combination of Venus and a satellite. The police officers saw the satellite in the west and as it passed over them, as they chased it across Ohio and into Pennsylvania; their attention was then drawn to Venus. The trouble here, as outlined in the Project Blue Book files is that there were no satellites visible in that part of the United States at that time of the morning. Letters and other documents in the Blue Book file prove this, yet the satellite portion of the solution is allowed to stand.

To make it worse, drawings made by the police officers show what was visible in the sky. Those drawings mark the position of the UFO, that of the moon, and that of Venus. Or, to put a point on it, the police officers did see Venus and identified it as such. But the label on the case, which is clearly in error, is allowed to stand and the case is shown to have a solution.

There are many such cases in the Blue Book files. Cases in which the solutions are simply not borne out of the documentation available. Yet we continue to hear about only 701 unidentified cases when the number is probably closer to 5000 when the solutions are examined carefully and those labeled as insufficient data are included. Insufficient data is not a solution, but is a label other than unidentified.

It was good to see a news report that treated UFOs seriously. It was not so good to see facts and figures used that were clearly inaccurate. I’m sure John knew the difference but I’ll wager that the reporter looked at a few things on line, misunderstood them, and ran with his story. The best thing about all this is that you don’t have to believe me. You can look it all up in the Black Vault.

*Bob Cornett and I might have [been] the first outsiders to go through the Blue Book files. The first thing we did was list all the unidentified cases complete with the names and locations. When the files were released into the public mainstream the names had been redacted. We could, of course, put the names back in… but the job of redacting was poorly done and in most of the case files you can find the names. A complete listing of the unidentified cases is available in Project Blue Book – Exposed in both hardback and as a Kindle ebook.

I will note that Jack Webb, in preparation for his TV series about Project Blue Book paid to have all the files microfilmed. We all owe him thanks for doing that.

Thursday, January 15, 2015

USAF UFO Project Blue Book Files Go Online for Free

Bookmark and Share

Project Blue Collection (Black Vault)

By Alejandro Rojas
openminds.tv
1-12-15

     . . . Project Blue Book is regarded as the third UFO investigation project by the USAF. The first was Project Sign, which began in 1947, then Grudge, which ran from 1949 to 1951, and the final project, Blue Book, ran from 1951 to 1969. The files surrounding the investigation of the sightings are all included in the Project Blue Book files. That is, unless, as some suggest, there are secret investigations that the public still does not have access to. . .

. . . Now researchers and UFO enthusiasts, including myself, can save some money. The files have been placed online by John Greenewald who runs a website called The Black Vault. Greenewald has been submitting Freedom of Information Act (FOIA) requests since he was a teenager to get the government to share what it knows about UFOs and other clandestine matters.

He has posted these files online, and over the years has amassed the largest online repository of such materials. He has over one million pages hosted there. Now that he has finally finished the daunting task of making the Blue Book files available, he now has over 130,000 more. . . .

Monday, October 13, 2014

“…He, Too, Began To Realize the MSM Doesn't Cover UFOs”

Bookmark and Share

Larry Klayman
Five years ago, the obstreperous Larry Klayman vowed to get "the goverment" to admit in court that UFOs were a national security issue. Yet not a squeak out of him on that issue since./CREDIT: maxresdefault

Radar tracks on a gasbag


By Billy Cox
De Void
10-10-14

    Larry Klayman is still alive. We know this because, last week, he petitioned the Department of Homeland Security to deport President Obama back to Africa. “He has no legitimacy to be president, and he must be tried, convicted, and removed from our shores,” Klayman declared in a press release, “before he destroys everything the Founding Fathers bequeathed to us.”

How could anyone forget Klayman, the prodigiously litigious Gennifer Flowers attorney who lodged more than a dozen lawsuits against the Clinton administration during the 1990s? Since then, he’s sued everybody from Elena Kagan to Dick Cheney to Mark Zuckerberg to Mahmoud Ahmadinejad to even his own mother. When he left Judicial Watch in 2003 to seek the Republican nomination for Florida's U.S. Senate post, Judicial Watch wouldn’t take him back, so he sued them, too.

Anyway, the only reason Klayman rates a De Void blurb is because, for a few fleeting moments in 2009, the guy swiveled his omnivorous targeting-acquisition machinery at UFOs. Back then, Klayman promised to get “the government” to concede that UFO data was classified for reasons of national security. Such an admission, of course, would be seismic insofar as the USAF wriggled out of its UFO mission in 1969 by declaring there were no national security angles to the phenomenon. Klayman's new platform, Freedom Watch, hurled FOIA missiles at the CIA, the DIA, the DoD, the NSA and the USAF, knowing before hearing back that his barrage would be futile.

“We’re not waiting for them to go through their administrative aspects,” Klayman vowed of the anticipated military evasiveness. “We’re going straight into a court of law because they’re in violation.” He told De Void he was looking forward to gathering affidavits from government officials who “shouldn’t have a problem with this if it isn’t a national security issue, as they claim.” At the time, he hadn’t decided where to file but he was certain he could have his pick of venues. “The media loves a good story,” he said. “Most (judges) are egocentric, they don’t make a lot of money and they like to get their names in the news.”

De Void kept waiting for the court action. Surely the wires would pick up on the story when it broke. After all. Larry Klayman. The seasons changed. Nothing. The UFO gambit didn't even get him on TV. De Void left unreturned messages with Klayman’s gatekeepers. The clock kept ticking and the seasons changed again. After months of radio silence it became clear that Klayman had given up. No clarion press announcement this time.

Sometimes you wonder which exact species of anger or attention deficit disorder motivates and drives characters like Larry Klayman. Maybe he figured there wasn’t enough divisive partisan red meat in UFOs to sustain his appetite. Maybe he, too, began to realize the MSM doesn't cover UFOs. And maybe it all worked out for the best.