Saturday, 23 April 2016

NORAD And The UFO Smokescreen

Part 7

 

In Part 6 of “NORAD and the UFO Smokescreen”, I introduced the possibility that the North American Aerospace Defence Command (NORAD), as well as other commands and their space components, had ever detected and tracked what we would ultimately called UFO’s outside Earth’s atmosphere. By UFO’s, I, of course, mean unknown and unidentifiable bodies above-and-beyond manmade payloads or debris, and natural, meteoritic material. I established that NORAD is not in direct command and control of space surveillance systems, but relies on incoming data from the United States Strategic Command (STRATCOM) and the component commands who run the vast Space Surveillance Network (SSN) – over thirty electro-optical and radar sensors distributed the world over. I also established that, if UFO’s do in fact exist, that NORAD and the SSN could, even in the 1950’s and 1960’s, have spotted serious UFO’s events – within technical limitations – and that such events would have been classified. Beyond those facts, much of what we know, at least up until the mid-1970’s, is inconclusive, and sometimes just rumor. However, this very large and complicated jigsaw puzzle was becoming clearer.


“Uncorrelated Target”,  or, “UCT”            

During this time, a seemingly new set of terminology came into usage. The most tantalizing of those new terms, which is still in use today, is “Uncorrelated Target”, often shortened to “UCT”.

Curiously, the earliest reference to UCTs I have discovered is actually in a 3rd April, 1968, letter from astronomer J. Allen Hynek’s close associate William T. Powers to astronomer Thornton Page. Powers states:

“So many statements have been offered publicly to the affect that astronomers don’t see UFOs or photograph unknown objects that everyone believes them, despite their falsity. The result is that when anomalous images show up on films, the tendency is to eliminate the UFO hypothesis simply by not calling them UFO’s, as NORAD eliminated UFO’s by calling them UCTs (Uncorrelated Targets).”

This is important as Page had been a member of the CIA’s Robertson Panel on UFO’s in 1953. He was one of the more hostile members towards UFO’s, though he later was involved with the American Association for the Advancement of Science’s (AAAS) UFO Symposium in 1969 which much of the established scientific community had resisted. Below is the page in question.  


So, what are Uncorrelated Targets? And do they really have anything to do with the UFO phenomenon?  

When an SSN detection and tracking site discovers what could be new and/or uncatalogued object in space, it is first given the label “Unknown Observation” (UO). If routine attempts to identify the UO fail, it is quickly “tagged” as an “Uncorrelated Target” (UCT) and further attempts are made to associate it with a previously known object which has moved in space, wrongly tagged by the SSN system, or otherwise lost. Publically available information concerning these capabilities is remarkably myriad. For example, NASA’s 2008 “Handbook For Limiting Orbital Debris” states:

“Individual SSN sensors are normally tasked each day to track a tailored set of satellites, taking advantage of each sensor’s location and capabilities. If the sensor can correlate the observations with a catalogued satellite, the observations are tagged accordingly and are sent to Cheyenne Mountain Operations Center (CMOC). If the observations cannot be associated with a known object, the observations are sent as Uncorrelated Targets (UCTs). Sometimes these UCTs can be correlated automatically with catalogued objects in Cheyenne Mountain, since the SCC database might have more accurate or more recent orbital data than the sensor. If no correlation is possible, the observations are retained as UCTs and can be compared with other UCTs at a later date by Space Control Center (SCC) analysts.”

The Massachusetts Institute of Technology’s (MIT) 1994 Project Report STK-221, titled “Proceedings of the 1994 Space Surveillance Workshop, Volume 1” reads:

“….the observations on the object come into Space Defense Operations Center (SPADOC) as Uncorrelated Targets (UCTs)… …UCTs may also enter the system from objects which are new to the network. New satellites can arise in a number of ways, the most obvious being a newly launched satellite or from debris related to a launch. Other processing in SPADOC has specific responsibility for identifying these objects and cataloguing them as quickly as possible. But, on occasion, pieces of debris may be missed and this will eventually result in UCTs entering the system. Other sources of UCTs include manoeuvres or orbital separations.”

Openly available information regarding UCTs, like the examples offered above, is extensive. Classified records, however, are regrettably very challenging to obtain. We are doing everything we can, using the Freedom of Information Act (FOIA) and Mandatory Declassification Review (MDR) to pry open hitherto unseen records.

What we do know, though, is very interesting.

Uncorrelated Target data is, with only one special exception, classified SECRET. UCTs are fall into four “categories”, which are: “Nonsignificant ”, “Significant”, “Critical” or “False”. Furthermore, UCTs fall into two “classifications”, which are either “Near Earth” or “Deep Space”. All UCT data is sent from the initial detecting and tracking site to STRATCOM J3 (Operations), the Joint Functional Component Center – Space (JFCC-S) and the Joint Space Operations Center (JSpOC). NORAD too receives UCT data to fulfil its “Integrated Tactical Warning and Attack Assessment” (ITW/AA) mission, which includes missile warning and target prediction. Some UCTs are undergo a process known as “Space Object Identification” (SOI) whereby UCT data is processed with the aim of actually identifying the object. SOI includes the measuring of a UCTs reflective brightness, determining its radar cross section (RCS), and even eavesdropping on any transmission, if manmade. UCT processing focuses on bodies that are in orbit, or reaching orbit, or have ballistic trajectories expected of missile launches. Thus, UFO’s – if one considers the erratic and unpredictable manner they are said to behave – may be difficult for the SSN to verify or assess. Or, the other possibility is that the SSN is far more adaptive and sensitive than what publicly available information says.

How do we know all this? We know, because it can be all found in half a linear foot of military doctrine dating back thirty years.


Regulations, Instructions, Manuals, Directives, And Handbooks        

There exist a number of NORAD, STRATCOM and old US Space Command (SPACECOM) publications which are of great interest. Unfortunately many are classified, and, thus, totally unrealisable, or, releasable only after heavy redaction. My colleague David Carmichael and I are endeavouring to have a significant number of them identified, declassified and released under the Freedom of Information (FOI) Act. Moreover, we are attempting to access current publications as well, which is even more difficult. Despite these barriers, there have been notable successes. Dozens of doctrinal publications – regulations, instructions, directives, guidelines, manuals, handbooks, etc – have been released, if redacted, as we shall see.

The earliest publication we have on record that mentions UCT’s is an obsolete SPACECOM regulation titled “US 55-12 Space Surveillance Network (SSN) Operations”, dated 1st June, 1992. The version I have obtained is heavily redacted, but nevertheless contains information essential to the study of possible UFO detection in space. At a hefty 191 pages and classified SECRET by “multiple sources”, UK researcher Dr. Armen Victorian, also known as Henry Azadehdal, briefly wrote about its contents in 1996 after securing a copy. He was almost certainly the first UFO researcher to see it. I obtained my copy from someone else in the defence intelligence community, but I believe that the copy I have on file is the same as what Victorian acquired. My colleague David Charmichael attempted to get the redacted sections released in early 2015, but he was told by the STRATCOM J006 (FOI) desk that they remain currently and properly classified. The unclassified sections of “US 55-12 Space Surveillance Network (SSN) Operations” are, however, still of interest. The first page of states:

“This regulation provides policy and guidance for operations of the worldwide Space Surveillance Network (SSN). It applies to Headquarters US Space Command (HQ USSPACECOM); the component commands: Headquarters Air Force Space Command (AFSPACECOM), the Naval Space Command (NAVSPACECOM), and Army Space Command (USARSPACE); the Space Surveillance Centre (SSC), the Alternative Space Surveillance Centre (ASSC); and the SSN sensors…”

See below.


Despite this regulation being nearly twenty-five years old, the most critical segments to our research are precisely the ones that are heavily redacted. Much can be taken away from what is left, however. There are chapters detailing the roles and responsibilities of the various SSN sensors, the breakup of satellites, tracking and impact prediction, tasking procedures, emergency actions, computer system outages, communications security and other technical matters. The rest, though, is a patchwork of redaction. A good example is the first page of Chapter 6, titled “MANEUVERABLE SATELLITES”, speaks for itself, and I have imaged it below.


A more legible, and surprisingly more current, publication regarding UCTs is a 13th Feburary, 2004 STRATCOM Command Directive titled “505-1 VOL 2 Space Surveillance Operations – Event Processing”. Chapter 12, titled “UNCORRELATED TARGETS”, begins with:

“12.1 (U) General. … The SSN often detects objects on orbit that do not correlate with orbital elements of any catologed objects in the sites databases. These UCTs are important because such objects could be previously undetected or recently maneuvered foreign satellites or missiles with hostile missions…”

Additionally, UCT “Categories” and “Classifications” are laid out:

“12.2. (U) Categories. UCTs are classified into the following categories:

12.2.1.  (U) Nonsignificant UCT. A UCT with an average RCS of less than 1 square meter.

12.2.1. (U) Significant UCT. A UCT with an average RCS 1 square meter or more. Note: Optical sensors consider all UCTs as Significant unless processing a NFL.

12.2.3. (U) Critical UCT. Any UCT which is suspected to be related to a new foreign launch. Specifically, a UCT is “CRITICAL” if it meets one or more of the following criteria:…”  

This is where the predictable redactions begin. Four “criteria” are listed, but have been entirely blanked out. Additionally, a fourth category of UCT is listed. A “False UCT” is a system error, interference, and other tracking peculiarities that do not represent a real object in space. The page then continues on with a new sub-section describing “UCT Classification”:

“12.3. (U) UCT Classification:

12.3.1. (U) Near Earth. Near earth UCT observations and element sets are UNCLASSIFIED.

12.3.2. (U) Deep Space.”

Below is an image of this page.


In a 7th April, 1994 reply letter to Dr. Armen Victorian, SPACECOM stated:

          “Copies of any serious UCT event are sent to the Missions Systems Integration Board (MSIB). MSIB is composed of all NORAD and SPACECOM directorates, and senior level representatives from Naval Space Command, Army Space Command and Air Force Space Command.

Furthermore, UCT data is almost always classified SECRET. The STRATCOM “Dedicated SSN Sensors Security Classification Guide”, dated September 30th, 2005, states:

“Data collected on satellites with SECRET Element Sets is classified SECRET… … Signature data (e.g. Visual Magnitude Imagery, SOI) taken on deep space Uncorrelated Targets (UCTs) is classified SECRET and becomes UNCLASSIFIED if UCT data is correlated to an unclassified known object.”

Going back to the 1980’s, an obsolete SPACECOM publication titled “Uncorrelated Target Processing Handbook” apparently contains additional information about UCT’s. In 1995, Dr. Armen Victorian and researcher Ray Fowler were told by the SPACECOM Public Affairs Office that the handbook was a 1st Command and Control Squadron (1CACS) publication used for space surveillance tasking and guidance. Fowler, in his 1991 book “The Watchers”, states:

“…the handbook states that the 1st Command and Control Squadron (1CACS) is responsible for processing all UO’s that are reported to Cheyenne Mountain Space Surveillance Center (SCC) from the worldwide Space Surveillance Network (SSN). This includes UCT’s.”

1CACS was activated on the 1st Dec 1989 and redesignated 1st Space Control Squadron (1SCS) on the 1st of Oct 2001. Organisationally, 1CACS was subordinate to the 1st Space Wing, Air Force Space Command (AFSPC), but functionally supported the Cheyenne Mountain Complex (CMC), and thus, NORAD. An old SPACECOM Regulation published on January the 31st, 1995, titled “USR 10-5 Space Surveillance Network User Support Data”, states:

“1CACS is a part of Air Force Space Command (AFSPC) and is collocated with the Space Control Center (SCC). 1CACS performs all routine processing for the SCC”

So there is no doubt that 1CACS was at the forefront of UCT detection and processing, thus obtaining their old records is of utmost importance. Using the FOI Act, we are attempting to access the files of the old 1st Space Wing, which will include 1CACS files, and maybe material from other space surveillance squadrons. 

Another 1980’s-era example of NORAD’s role in processing data on unknown objects in, or near, space comes from the dedicated USAF missile and space warning squadrons. One such squadron is the 6th Space Warning Squadron (6SWS), formerly the 6th Missile Warning Squadron (6MWS). The 6SWS is based at Cape Cod Air Force Station, in Massachusetts, uses one of the world’s most powerful Solid State Phased Array Radar (SSPAR) to ceaselessly scan the skies and space over the Atlantic Ocean for sea-launched ballistic missile launches, plus incoming warheads thrown from intercontinental ballistic missiles (ICBM). Complementing that dedicated role, the 6SWS also supports the SSN in near earth space object identification. An obsolete 30th June, 1986 AFSPC regulation titled “AFSPACECOM Regulation 23-36 Organisation and Mission – Field 6 MISSILE WARNING SQUADRON” states, on Page 1:

“1. Mission. To manage operate, and maintain the AN/FPS-115 radar to provide tactical warning and support attack assessment of a sea-launched ballistic missile (SLBM) attack against the continental United States and southern Canada. Provides warning and attack assessment of an ICBM attack against these areas. Warning data are sent to North American Aerospace Defence Command (NORAD), United States Space Command (USSPACECOM), Strategic Air Command (SAC), National Military Command Center (NMCC), and Alternate National Military Command Center (ANMCC). The unit also provides surveillance, tracking and limited space object identification (SOI) support for space surveillance operations.”

It is safe to assume that the 6SWS is capable of plotting almost any solid object in its field of view, as long as the size of the object is appreciable. Also clear is that NORAD is in the data loop. Also, note that the “unit also provides surveillance, tracking and limited space object identification (SOI) support for space surveillance operations.”. Whether any truly anomalous UFO events have actually occurred on the screens of the 6SWS is unknown to us. The 6SWS is just one of twenty such space and missile warning squadrons organised within Air Force Space Command (AFSPC). It will be a gigantic task to submit individual FOI requests for detailed information on UFO-type occurrences to all of them; and, as we know, they may not be compelled to release anything substantial. Below is an image of the above mentioned document.


Also from the 1980’s is a Cheyenne Mountain Support Group (CMSG) regulation which governed the Cheyenne Mountain Complex (CMC) “Operations Loop” telephone system. “CMC Regulation 700-3 Computer Systems OPERATIONS LOOP”, on Page 1, states:

“…The Operations Loop is a secure telephone system cleared for SECRET. All Operations Loop calls are directed to NORAD Command Director (CD) or the USSPACECOM Space Director (SD).”

On Page 4, it is stated:

“…Information passed over the Operations Loop must be of an operational nature. Be brief, concise, and pass all information to the CD and/or SD. Examples of information passed over the Operations loop include:

(1) Event reported via missile tactical warning and attack assessment (TW&AA) system.

(2) Unknown tracks.

(3) System degradation.

(4) Events requiring CD or SD decision or discussion.

(5) Events affecting more than one operations center.

(6) Space object maneuvers.”

Note that “unknown tracks” and “space object maneuvers” are listed as prime “Operations Loop” telephonic conversation topics for the NORAD and SPACECOM Command Directors. Readers familiar with my earlier work will know that an “unknown track” refers to an unknown, unidentified radar detection and subsequent plotting in the atmosphere. In other words: potential UFO activity. As for “space object maneuvers”, one can only wonder what oddities may have discussed over the years. Below is the aforementioned page.


In Part 8 of this series I will be discussing how dedicated UFO researchers in the 1970’s, 1980’s and 1990’s, attempted to obtain actual Uncorrelated Target data. 

Thursday, 21 April 2016

The "Bolender Memo" And A New Lease On Life


            On 2nd, December 1978, researcher Robert Todd submitted a Freedom of Information Act request to the United States Air Force (USAF) for any unreleased records created during the closure of Project Blue Book. A response came back from the USAF’s 1947th Administrative Support Group (1947ASG), dated 19th December, 1978, with a number of documents attached. One of them was a three-page “Department of the Air Force Air Staff Summary Sheet” dated 20th December, 1969, prepared by a Maj. Espey and signed by Brigadier General Carroll H. Bolender, who was Deputy Director of Development, for the Deputy Chief of Staff, Research and Development, USAF. That “Air Staff Summary Sheet” became widely known as the “Bolender Memo”. The cover letter – and this is the first time this has ever been published – from the USAF to Todd stated:

“Dear Mr. Todd,

Attached in response to your Freedom of Information Act (FOIA) request of 2 December, 1978, are copies of all records from Secretary of the Air Force files of or relating to the decision to terminate Project Blue Book, as well as all other UFO-related records located during the search.”

Below is an image of the cover letter.


To this the “Air Staff Summary Sheet”, or “Bolender Memo”, was attached and immediately – rightly or wrongly – caused a stir in the UFO community. The contents of the document are not what this blog post is about; though I will mention them later. Many readers will be aware that the three-page “Bolender Memo” was very difficult to read, and multi-generation copies have been circulated, each more blurred or scratchy than the last. Finally, now, we have an enhanced and clean-up version of the famous document, which I have presented below.

This much more readable version has come to us from Barry Greenwood, co-author of the quite shocking 1984 book “Clear Intent”, later published as “The UFO Cover-Up”, and editor of two ground-breaking newsletters, “Just Cause” and “UFO History Review”. Barry was in constant contact with like-minded “heavy lifters” like Robert Todd and Lawrence Fawcett, who, you know, actually did research, as opposed spin and waffle. Barry said to me, regarding the newly presented “Bolender Memo”:

“Many of the documents we get from government are wretched multi-generation copies that are often the only copies available. When a document is photocopied, a certain degree of damage is done to the copy. It is predictable damage, like thin parts of letters disappearing, linear and vertical alignments are distorted, dirt is incorporated, etc. Such damage, with patience, can be fixed. It is like wrecking a car on the highway and bringing it to a repair shop. You get an outwardly new car. It is never the same as an original but looks pretty good regardless. Same with documents. Not all damage is fixable but it can be restored to a surprisingly good condition. So the attached Bolender document has been given a repair job, not perfect as some text is simply unreadable. But 99% is clarified and is ideal for display.”

The document is important for two reasons. Firstly, it is one of the preparatory documents for the draw-down of the U.S. Air Force’s Project Blue Book, which closed in 1970. Secondly, it illustrated an understanding by many researchers that some UFO reports of national security concern were handled differently than through Blue Book channels. As stated above, the “Bolender Memo” has a new lease on life, and is presented below. I have also, beneath the newly scanned three pages, presented an example of the rough, poor quality copies which have been circulated online for two decades. 




Below is an example of what researchers have been working with for years.






Saturday, 16 April 2016

Admission Of Malmstrom Missile Shutdown Incident In Kirtland Air Force Base Trip Notes?


          A rather extraordinary document, sourced from the in the Edward U. Condon Collection at The American Philosophical Society in Philadelphia, has come to my attention. It’s a page from the “trip notes” written by members of Condon’s UFO Study Team. The same Condon who was head of the most flawed major UFO study in history. Anyway, while visiting Kirtland Air Force Base in mid-Feburary, 1968, the some of those team members met with, I guess, aerospace and missile experts, and discussed the recent and alarming missile shutdowns at Malmstrom Air Force Base which occurred less than a year before. We all know the detailed stories, and there exist enough United States Air Force (USAF) and other ’agencies documents to be sure something was going on. Something really serious. None of this has been admitted by the USAF. But they may want to rethink that stance one day, when more documents leak out. Not unlike the document below. Under the heading “KIRTLAND AIR FORCE BASE” it is dryly stated:

“Checked classified aspects of electromagnetic effects possibly associated with UFO sightings near a Minuteman missile base. Notes results of the discussion were inconclusive, in that it cannot be ruled out that UFOs were the cause of the effects observed at the base. Nothing more can, within security limitations, be said.”

There are a number of very important aspects to this. Firstly, note the use of the word “sightings”, not “sighting”. That means that more than one missile shutdown event was discussed, or, that only one event was discussed, but was confirmed by multiple people or systems in situ. Secondly, there is the admission that it “…cannot be ruled out that UFOs were the cause of the effects…”. Thirdly, more was discussed, but nothing of it was to be put on paper, or, word verbatim “Nothing more can, within security limitations, be said.”.

That’s a lot of punch on half a page of notes. I have yet to study this further, and more will be coming soon. On another note, I discovered this while digging deeply for North American Aerospace Defence Command (NORAD) documents, and, on the same page as this Minuteman missile business, there are trip notes relating to space objects, obviously of the UFOs variety, being conceivably detected on air defence systems. The briefing was conducted at the West Coast Study Facility, which functioned under the old USAF Systems Command (AFSC). Again, like the Kirtland AFB visit, the details of the briefing were classified. A summary was presented, however, which is on the document below. I will be discussing this aspect of things in my continuing series “NORAD And The UFO Smokescreen”.

Below is the above mentioned document.