Deadhorse UFO Incident: NORAD Logs Reveal Insights into Potential Defense Systems
Liberation Times Opinion & Insight
Written by Geoff Cruickshank B.IT, M.IEEE - 7 October 2024
Declassified NORAD logs show mysterious power fluctuations during the event at the command centre controlling the intercept.
Evidence suggests that the facility involved was the CONR facility at Tyndall AFB in Florida, over 3000 nautical miles from where the shootdown took place – was this a long range Unidentified Anomalous Phenomena (UAP) countermeasure weapons effect?
Thanks to a FOIA release from the Canadian Government in September 2024, we may now have a glimpse of the extraordinary countermeasures deployed by UAPs against NORAD command and control facilities during the intercept and shootdown of an object assigned a NORAD designator of UAP#20 off the coast of Deadhorse, Alaska on February 10, 2023.
The documents include the logs of the operations centre in control of the shootdown, which appears to be the Continental U.S. NORAD Region (CONR) facility directing the intercept from Tyndall AFB in Florida where Operation NOBLE EAGLE is conducted from.
Co-located with Headquarters First Air Force (Air Forces Northern), this Combined Air Operations Centre coordinates CONR sector activities and executes the NORAD air sovereignty mission for the continental United States. First Air Force (AFNORTH) plans, conducts, controls, and coordinates all Air Force forces for the NORAD-NORTHCOM Commander.
This facility is one of the most sophisticated and high technology bases that the United States possesses; it was rebuilt after a direct hit from Hurricane Michael in 2018 as the first “Installation of the Future” concept prototype.
The additional microgrids and “self-reliance” power generation systems installed in 2022 appear to be no match for a dedicated UAP adversary.
Military jargon and acronyms
Before we examine the logs, we should get familiar with the military jargon used extensively throughout the documents. This will help to understand what exactly is happening as the logs give a blow-by-blow account of the event.
NORAD: The North American Aerospace Defense Command (NORAD) is a bi-national United States and Canadian organization charged with the missions of aerospace warning and aerospace control for North America. Aerospace warning includes the monitoring of man-made objects in space, and the detection, validation, and warning of attack against North America whether by aircraft, missiles, or space vehicles, through mutual support arrangements with other commands. Aerospace control includes ensuring air sovereignty and air defense of the airspace of Canada and the United States. The commander maintains his headquarters at Peterson Air Force Base, Colo. The NORAD-U.S. Northern Command (USNORTHCOM) Command Centre serves as a central collection and coordination facility for a worldwide system of sensors designed to provide the commander and the leadership of Canada and the U.S. with an accurate picture of any aerospace threat. Three subordinate regional headquarters, located at Elmendorf Air Force Base, Alaska, Canadian Forces Base, Winnipeg, Manitoba, and Tyndall Air Force Base, Florida, receive direction from the commander and control air operations within their respective areas of responsibility.
ANR: Alaskan NORAD Region HQ - Elmendorf Air Force Base, Alaska
CANR: Canadian NORAD Region HQ - Canadian Forces Base, Winnipeg, Manitoba
CONR: Continental U.S. NORAD Region HQ - Tyndall Air Force Base, Florida.
EADS: NORAD Eastern Air Defense Sector HQ – Rome, New York. Subordinate to CONR.
MCC: Mission Crew Commander – controls the floor of the Ops Centre
CADS: 22 Wing at North Bay, Ontario also known as the Canadian Air Defence Sector (CADS), is responsible for providing surveillance, identification, control and warning for the aerospace defence of Canada and North America at the Sector Air Operations Centre.
Op NOBLE EAGLE: Operation NOBLE EAGLE is the name given to all North American Aerospace Defense Command (NORAD) aerospace warning, control, and defense missions in North America. Through Operation NOBLE EAGLE, NORAD deters, detects, and defeats potential threats to U.S. and Canadian airspace 24/7/365. Since Sept. 11, 2001, CONR has been the lead agency for Operation Noble Eagle in the continental United States. Its continuing mission is to protect the United States from further airborne aggression from inside and outside of the contiguous U.S. Today, CONR stands watch 24/7/365 and aids NORAD in providing continuous 360-degree defense of North America.
CAOC: There are two instances of CAOCs in the logs for 10 February 2023.
1. Royal Canadian Air Force Combined Aerospace Operations Centre (CAOC) in 1 Canadian Air Division (1 CAD)/Canadian NORAD Region Headquarters at 17 Wing Winnipeg, Man.
2. Co-located with Headquarters First Air Force (Air Forces Northern) at Tyndall AFB, Fla., a CAOC coordinates CONR sector activities and executes the NORAD air sovereignty mission for the continental United States. First Air Force (AFNORTH) plans, conducts, controls, and coordinates all Air Force forces for the NORAD-NORTHCOM Commander.
SODO: The CAOC includes the Air Operations Centre (AOC), which is staffed at all times by a senior operations duty officer (SODO) on a 12-hour shift, a defensive duty officer, and two defensive duty technicians.
CCO: An on-duty Chief of Combat Operations, or CCO, is continuously in touch with the CAOC, and a general officer is always either in the building or on call.
Zulu: To co-ordinate with multiple teams across multiple time zones, Greenwich Mean Time (GMT) is referenced by a lower case “z”.
In order to understand the general “layout” of the Operations Centre and how data flows between key positions within it, the following image is from the MCC on duty at EADS at Rome, NY during the 9/11 attacks. The Mission Crew Commander is the key position here.
The image above is taken from a website that tells the story of 9-11 by documenting the activity of then Major Kevin Nasypany, Commander, Alpha Flight, and the Mission Crew Commander (MCC) on duty at the Northeast Air Defense Sector (NEADS) on September 11, 2001.
The Vanity Fair article 9/11 Live: The NORAD Tapes by Michael Bronner October 17, 2006 gives further insight into how these Op Centres work.
Although the NEADS (now called EADS) setup is from 2001, it can be assumed that the general layout is a common one throughout NORAD sites.
The Canadian Logs released via FOIA
Now let us step line-by-line through the log of the 10th of February 2023 UAP shootdown event, the first page of which is located on page 264 of the FOIA release.
This release was instigated by someone with the X handle AtreonZ and journalist Daniel Otis.
Line 1: Classification: SECRET// (Redacted) – other pages in the release indicate that the redacted portion originally had the Dissemination Limiting Marker (DLM) of CANADIAN EYES ONLY. How this was to be accomplished within NORAD is not known. It is also not known why there is no strikethrough of the SECRET classification as part of the declassification process.
Line 2: CADS MCC DAILY LOG 10 Feb 23 – going by our acronym list above, this heading appears to show that this is the Mission Crew Commander log for 22 Wing HQ at North Bay, Ontario. However, as we delve into the logs in depth it becomes clear that these logs are a consolidation of the NORAD infrastructure executing Operation NOBLE EAGLE, in response to a perceived potential threat to the Continental United States from an object later designated UAP20.
Line 3: A repeat of line 2 – perhaps one of these headings was added at a later date for clarity?
Lines 4&5: A summary of the flight crew and personnel on duty during the new day changeover from 9 February 2023 to 10 February 2023 at Greenwich. This would be 19:00 Local Time if the logs are from either CANR or CONR. If the facility is CADS, it would be 20:00 Local Time. The Duty Flight is the Voodoo Flight, the Mission Crew Commander is Major Carter, the Mission Crew Commander – Technical is Warrant Officer Brodie, Canadian Air Defence Sector Commander at 22 Wing is Colonel Jolette and the Duty Officer is Lt. Colonel Verran.
Line 6: A redacted entry, followed by three full stops and the initials of the person who entered this into the log. In this instance, “dwb” is probably WO Brodie.
Line 7: At 2044 Zulu time, the Duty Officer at CANR has changed from Lt. Colonel Verran to Lt. Colonel Bruns. “tlg” could possibly be the person at CANR who entered this into the log.
Line 8: Classification level is SECRET / (redacted) – again most likely a DLM of “Canadian Eyes Only”.
Line 9: Multiple sources of information providing the “fused” situational air picture (ANR, CANR, CONR etc.)
Line 10: A “Real-World” log as opposed to an “Exercise”. As we saw with Major Nasypany, who was expecting the highjacked airplane exercise to commence an hour after the actual 9/11 highjack events started, the first thing he asked the ATC was “is this Real World or Exercise?”.
Line 11: The CLOSED status possibly means there are no outstanding tasks for Voodoo flight from the day in question of the log.
Line 12: The log for Zulu day 10 February 2023 was completed at 00:00 GMT 11 February 2023 (the beginning of the next Zulu day – i.e. the last entry into the log).
Line 13: Updated by an automatic Stata command file execution? (i.e. generating a new logfile to analyse). Stata is a general-purpose statistical software package developed by Stata Corp for data manipulation, visualization, statistics, and automated reporting.
Line 14: This is where the fun starts. WO Brodie notes the day change at Greenwich.
Line 15: 10 minutes later (probably 19:10 Local Time) something happens that prompts WO Brodie to update the log. Something so important that it is redacted.
Line 16: 3 minutes after that log entry, something else happens that is also redacted.
Line 17: 9 minutes after that event, WO Brodie logs another event that is redacted. Probably the initial reports of the UAP coming in.
Line 18: At 03:15z the facility’s hard copy COMSEC data for the day is destroyed, as per “Clear Desk” Standard Operating Procedures.
Line 19: At 04:43z (23:43 Local Time, 20:43 on February 10 2023 at Deadhorse, Alaska) the ANR at Elmendorf AFB was contacted in regards to Tracking Number B3334 over the North Slope oilfields of Alaska. Advised (adz) by Alaskan Air Defense Sector Mission Crew Commander Major Pandy that the object has been classified as a UAP. The “vcs” could be a reference to a catalogue system for UAP, in this instance the designator UAP20 was given. This entry by Mission Crew Commander Major Carter also appears to indicate that the F-22 Raptors from Elmendorf AFB have merged on the object’s plot and identified it as a “metallic airborne floating object”. It is hard to determine by the time of this entry to what extent UAP20 has been engaged but the “Discussions are ongoing” probably refer to NORAD asking for Presidential approval for a hostile engagement plan to be formulated.
Line 20: 3 hours later, at 07:48z, something happens that is redacted. I posit here that the facility where Major Carter is the Mission Crew Commander experiences a sudden power loss at this exact time and is running on a large Uninterruptable Power Supply (UPS) system whilst the emergency diesel generators are starting up and reaching 1800 rpm (60 Hz) output. The reasoning here is simple – having worked in the power generation industry for over thirty years, I know for a fact it is common practice for the oncoming diesel generators to stabilize for around 300 seconds before the automatic synchronization system matches the diesel(s) generator’s frequency and voltage to the UPS system before closing the generator circuit breaker and allowing them to take the facility electrical load.
Line 21: 300 seconds after the redacted event at 07:48z, WO Brodie enters the log that the facility is running on diesel power.
Line 22: At 07:55z, (around 02:55 Local Time) WO Brodie notes in the log that technicians under the command of a Sgt Kitchen will attend the facility at 07:30 Local Time to troubleshoot faults with “the scopes”. This could be a reference to oscilloscopes or spectrum analysers in the facility that went into fault during the power transition from commercial power to UPS and diesel generation. These instruments are well known to be sensitive to these events.
Line 23: At 09:26z, the Chief of Combat Operations at either CANR or CONR (depending on which facility these logs are actually from) approves the plan to shootdown UAP20 that is travelling on NORAD designated track #B3334. WO Brodie notes this in the log. My bet is that this is the CCO from CONR at Tyndall AFB approving the plan.
Lines 24 – 26: A series of events from 09:30z to 10:18z that have been redacted are recorded by WO Brodie.
Line 27: At 10:27z, WO Brodie notes that commercial power to the facility has been restored.
Line 28: Another redacted log entry at 11:32z by WO Brodie.
Line 29: At 12:14z, the Duty shift changeover occurs. As indicated in other logs in this FOIA release, the shift hours at these NORAD facilities appear to be 07:00 to 19:00 Local Time. Given the fact that the change occurs at 12:14z, the facility therefore must be located in a time zone that is 5 hours behind GMT. Both CANR (Winnipeg) and CONR (Palm Beach, Florida) are in these time zones. To my mind, this rules out these facility logs as being for CADS at 22 Wing at North Bay, Ontario as it is 4 hours behind GMT, despite that appearing in the header. The incoming Mission Crew Commander is Major Boutilier, the Mission Crew Commander Technical is Master Warrant Officer Gillespie, and also in the Duty Watch is Warrant Officer Roberts, the CADS Commander is Col Jolette and the Duty Officer is Lt. Colonel Verran. These last two positions not having changed during shift handover also indicates that these people are located elsewhere. Additional people are present during shift handover but their names and ranks are redacted. Importantly, from their LinkedIn profile, one of the persons mentioned in the incoming shift has spent the entire period from 2021 to the present based at CONR, which leads me to believe that these logs are actually from Tyndall AFB, Florida.
Above - LinkedIn profile of one of the persons named in the logs.
Line 30: WO Roberts is now making the log entries, with an event occurring during or just after shift handover at 12:23z that is redacted.
Line 31: Another redacted entry at 12:30z by WO Roberts. Possibly related to power supply issues at the facility – a coincidence or a countermeasure effect produced by UAP20, whose eavesdropping of the comms between CONR and the F-22 make it aware of the shootdown order?
Line 32: At 12:42z, after a power “bump” that restarts the diesel generators, Mission Crew Commander Major Boutilier orders the facility remain on emergency diesel generation power until after the UAP20 intercept mission is completed. This is a very odd command to give and appears to be directly related to the ongoing UAP intercept – and perhaps Major Boutilier is acutely aware of this fact. The second reason it is curious is that Tyndall AFB was devastated by Hurricane Michael in 2018 and was rebuilt as the prototype “Installation of the Future” for the U.S. military, with resilient, self-sufficient power supplied by large solar arrays and battery banks as microgrids. In 2022 a USAF press conference at the base stated that the microgrid alone could supply critical infrastructure for more than 3 hours. Given that Local Time at Tyndall AFB at this point is 07:42, there would not be enough sunlight available for the solar panels to generate electricity and the batteries may have had insufficient time to recharge after the power issues the facility experienced 5 hours previously.
Line 33: At 12:46z, WO Roberts notes the facility is once again supplied by emergency diesel generators after the 300 seconds of synchronization time have elapsed from the power “bump”.
Line 34: After 3 hours without log entries, WO Roberts records an event at 15:59z that is redacted.
Line 35: An interesting entry here by WO Roberts at 16:00z, which gives the name of Eric Doucette as the “Viper NFE”. This may be a reference to Captain Eric J. Doucette, who, from his bio, “is a Certified Emergency Manager (CEM) by the International Association of Emergency Managers (IAEM) and is certified as a National Interagency Management System Type I Incident Commander. His response experience includes key leadership roles at the World Trade Centre Ground Zero following attacks of September 11, 2001, salvage of the NEW CARISSA, Coos Bay, Oregon 1999, Typhoon Paka in Guam 1997, and the 1996 TWA Flight 800 disaster offshore Long Island, New York. He has decades of crisis and incident management experience coordinating with federal state, industry and international partners to realize whole of government and community solutions to crises.” Perhaps this log entry is part of a UAP Protocol Checklist for NORAD? Page 297 of the FOIA release from another NORAD facility log a few days later states explicitly that there is indeed a large “checklist” for these events, including steps for “collecting the logs and locking down”.
Above - Page 297 of the FOIA release from NORAD facility log
Line 35: Another log entry by WO Roberts at 1615z that has been redacted.
Line 36: A very important log entry here at 16:40z – the Canadian NORAD Region’s Chief of Combat Operations advises that the Alaskan NORAD Region has designated a circular Temporary Flight Restriction Zone of dimensions 150 nautical miles diameter centred on Deadhorse, Alaska from the surface (land and frozen sea) up to Flight Level 600, or 60,000 feet. They have decided not to send out a Notice to Aviators (NOTAM) at this time and will “go on chat” when NOTAM is active. This directive is stated to have come directly from NORAD Commander General Glen VanHerck. The TFR lines up with the eyewitness vlogging of You Tuber Backcountry Alaska, as this screen shot from his live feed stream during the crash retrieval event displays. The red dot represents his filming location north of Deadhorse, with the C-130 military aircraft track around 30km away at the crash site.
Line 37: At 16:44z, the Weapons section of CONR at Tyndall AFB advise that the Temporary Flight Restriction zone will become active at 17:00z, which is 09:00 Local Time at Deadhorse.
Line 38: At 16:57, ANR at Elmendorf AFB advise UAP20 with NORAD track number B3334 was intercepted (merge plot) by F-22 Raptors at 16:57z. Going by the length of the next log entry, the Raptors did not immediately shoot it down.
Line 39: A rather lengthy log entry by WO Roberts, possibly describing the countermeasures the UAP deployed against the Raptors that were reported by the pilots involved. Redacted in full.
Line 40: At 18:07z, precisely an hour after the last entry WO Roberts makes an entry that again is redacted. Possibly related to the recovery efforts that Backcountry Alaska is documenting from around 30km away around 10:00 Local Time at Deadhorse.
Line 41: At 19:04z another redacted log entry by WO Roberts. Possibly an update for NORAD Commander Gen. VanHerck on recovery operations.
Line 42: Another very important log entry – at 19:10z, the Senior Operations Duty Officer from the CANR CAOC (a Major Zeaton is listed as SODO in the logs from CANR at this time) directs Mission Crew Commander Major Boutilier to “shut everything off”. Why would the Senior Operations Duty Officer in CANR Winnipeg direct the Mission Crew Commander in CONR Florida to do this? Was the entire NORAD system being actively jammed or otherwise interfered with by other UAPs that may have been traveling with UAP20, and were angered by this hostile action? For instance, just a day later UAP23 was also shot down by USAF F-22s over the Yukon using a version of the AIM-9 Sidewinder missile that the Canadian Air Force did not possess. Could this UAP have been the source of the countermeasures against NORAD, prompting a complete “power down” of Tyndall’s CONR facility and perhaps others?
Line 43: Redacted log entry at 19:12z by WO Roberts.
Line 44: At 20:44z, CANR informs the facility (CONR) that the CADS Duty Officer has changed from LCOL Verran to LCOL Bruns.
Line 45: Just under two hours after being directed to “shut everything off”, at 21:02z the CONR facility is back on normal commercial power. Whatever was causing the massive power fluctuations has stopped doing so.
Line 46: Another redacted log entry by WO Roberts at 21:22z, perhaps giving an update on power stability or UAP crash retrieval operations.
Line 47: The last log entry of an insanely busy shift for the CONR crew under Major Boutilier is entered by WO Roberts at 22:56z – but once again it is redacted.
Line 48: This entry at 23:42z is added by the oncoming shift and entered by WO Brodie. Redacted.
Line 49: The oncoming night shift of MCC Major Carter and MCC Technical WO Brodie is noted in the log, as well as the standing CADS Commander and Duty Officer at 23:50z (19:00 Local Time CONR).
Line 50: The end of the 10th February 2023 at Greenwich is noted in the log by WO Brodie at 23:59z. What a day!
Questions arising from the logs of the events at Deadhorse and Tyndall.
Was CONR at Tyndall AFB the only facility experiencing “power fluctuations”?
Were these power fluctuations a direct result of active countermeasures deployed by the UAP being targeted by NORAD at the time (UAP20), or were other UAPs discovered over the next few days (UAP22, UAP23) involved?
If so, how did the UAPs determine that Tyndall AFB was the one to target, and not Elmendorf AFB near Anchorage, AK which was much closer?
Is it possible that the radiative energy from the F-22s or other radars in the area was in fact manipulated and returned with some type of trace route mechanism to follow the data path from the F-22 sensors back to CONR?
We are all familiar with the concept of an “Integrated Battlespace”, where warfighting assets are used as network nodes to share information amongst themselves:
This concept works well in the lower latitudes of our planet, where communications from the constellation of geostationary satellites sitting on or near the celestial equator is relatively easy.
It is not so easy from the polar regions.
This photo was taken by me about 40km from Deadhorse, AK in 2019:
As you can see, these C-band COMSAT antennas are pointed directly at geostationary satellites orbiting 36,000 km above the Equator, which at these high latitudes is only a few degrees above the horizon.
For a UAP over Deadhorse to intercept these satellite feeds for a “man-in-the-middle” style attack to inject some type of trace route mechanism, it would have to be located south of Deadhorse – but as Backcountry Alaska documented, the UAP20 was located well north of Deadhorse and therefore ruling out this method of attack.
We can also rule out a space originated Electro Magnetic Pulse (EMP) mechanism being employed by UAP20 against Tyndall AFB.
With a straight-line distance of 3172 Nautical Miles (5874 KM) between the “battleground” off Deadhorse to Tyndall AFB, Florida, any metallic infrastructures in between those two endpoints that could carry an electric current (power transmission lines, oil and gas pipelines and wire fences) would have been destroyed. As far as we know, that did not happen.
Conclusion
This image from Google Earth gives us an idea of the scale of the distance from Deadhorse to Tyndall AFB that these potential UAP countermeasures had an effect over:
Could these so-called UAP “countermeasures”, deployed over thousands of miles with pin-point accuracy be the real reason for government non-disclosure?
A “we’ve got nothing” response to a potential adversary’s “other-worldly” capabilities?
Time will tell.
Geoff Cruickshank is a security consultant and researcher based in Darwin, in the Northern Territory of Australia. He is a former Mission Support Specialist / Installation & Integration Co-ordinator for Boeing Defence Australia and is a professional member of the Institute of Electrical and Electronics Engineers, the Australian Computer Society and a member of the Scientific Coalition for UAP Studies.
