Saturday 8 February 2020

American Airlines 'Flight 11' - “An Independent Analysis”

By Mark Conlon

Introduction

In this analysis I present some of the discrepancies in relation to American Airlines "Flight 11”. (AAL 11). The information in this analysis is in the public domain, and from official sources. My hypothesis has been carefully considered from the telemetry data, Bureau of Transportation Statistics data-base, Air Traffic Control communications, Airline employee witness statements and media reports.

The official narrative of American Airlines ‘Flight 11’

American Airlines ‘Flight 11’ (AAL 11) was a domestic passenger flight that was hijacked by five al-Qaeda members on September 11, 2001, as part of the September 11 attacks. Mohamed Atta deliberately crashed the plane into the North Tower of the World Trade Center in New York City, killing all 92 people aboard and an unknown number in the building's impact zone. The aircraft involved, a Boeing 767-223ER, registration N334AA was flying American Airlines' daily scheduled morning transcontinental service from Logan International Airport in Boston to Los Angeles International Airport in Los Angeles. Fifteen minutes into the flight, the hijackers injured at least three people (possibly killing one), forcibly breached the cockpit, and overpowered the captain and first officer. Atta, an al-Qaeda member and licensed commercial pilot, took over the controls. Air-traffic controllers noticed the flight was in distress when the crew was no longer responding. They realized the flight had been hijacked when Mohamed Atta's announcements for passengers were transmitted to air traffic control. On board, flight attendants Amy Sweeney and Betty Ong contacted American Airlines, and provided information about the hijackers and injuries to passengers and crew.

The Mystery of Gate 32

One of the earliest discrepancies surrounding AAL 11 is the Bureau of Transportation Statistics (BTS) has no record of AAL 11 departing on September 11th 2001, as the BTS should. This discovery was made by Gerard Holmgren. The data is automatically generated and recorded electronically when a flight takes off, so there is not human error involved in this process. To compound matters further, early mainstream media reports suggest that two different gates from which AAL 11 departed from, Gate 32 and Gate 26.


The Daily Telegraph:

The Washington Post:

Gate 32 was the scheduled gate, which the flight controller transcripts say, and that is what the 9/11 Commission accepted. http://www.nytimes.com/2001/10/16/national/16TEXT-FLIGHT11.html?ex=1071378000&en=4b6d66a63bf99b3a&ei=5070


Ground crew accounts in this video clip below, chief ground crew Donny Bennett recalls after a flight cancellation he was assigned to AAL 11. No gate number is mentioned in his account, although he talks of AAL 11 getting ready for push-off into the taxi way. Another crew member Howard Crabtree recalls attending to ALL 11, while another ramp crew member Richie Sorbello recalls waving-off Pilot John Ogonowski. No gate number is mentioned in their accounts in this video, it is only implied with a video of Gate 32. Source: https://www.bitchute.com/video/Gm8M40NjT2Vk/



Adding further confusion to the discrepancy is flight attendant Betty Ong’s phone call at 8:18 a.m. to the North Carolina Reservations Center, where Betty Ong told Vanessa Minter she was on Flight 12, and then repeated it to Winston Sadler. To compound matters further, Amy Sweeney in her first phone call at 8:30 a.m. said: “Flight 12 at Gate 32 had two flight attendants stabbed.” Phone Call Transcription FBI Document: https://www.scribd.com/document/14094215/T7-B17-FBI-302s-of-Interest-Flight-11-Fdr-Entire-Contents

Sweeney’s phone call message prompted Michael Woodward and his colleague Elizabeth Williams to proceed directly to Gate 32, and according to the FBI’s interview with Williams she said that they found “an empty plane”. See below:

WILLIAMS stated on September 11, 2001, at approximately 8 a.m., she was working in her office at LOGAN AIRPORT when MICHAEL WOODWARD, Manager of Flight Services for AMERICAN AIRLINES AA, advised her that they needed to go to Gate 32 because two flight attendants had been stabbed. Upon arrival at the gate, WILLIAMS and WOODWARD found an empty airplane. WOODWARD then got on the phone and contacted EVELYN NUNEZ, an employee of AA at LOGAN AIRPORT. While WOODWARD was on the phone, WILLIAMS searched the gate-side computer for information for the flight time of the airplane at Gate 32.
https://www.scribd.com/document/18775594/T7-B10-FBI-302s-Olsen-Fdr-302s-Re-Michael-Woodward-372


This important detail disclosed by Williams about the “empty plane” at the Gate 32, that both Williams and Woodward observed is omitted in the – 9/11 Commission Memorandum “For the Record” interview with Michael Woodward. https://catalog.archives.gov/OpaAPI/media/2609599/content/arcmedia/9-11/MFR/t-0148-911MFR-00013.pdf


So according to Elizabeth Williams they found “an empty plane” at Gate 32, yet according to the official narrative AAL 11 was in the air, and had been for 30 minutes, which begs the question why Amy Sweeney said it was at Gate 32 in her phone call? If Elizabeth Williams is telling the truth, and I have no cause to disbelieve her, and if she is not mistaken or misreported, then we may have the key to explain what might have happened to AAL 11.

According to the BTS database entry which lists no wheels-off time for AAL 11 for that day, there has been two explanations for this discrepancy. In the official record, the NTSB say that the data was not reported, in the confusion of the day. The “conspiracy theorists” say that it proves AAL 11 never existed. But the data does not say either of these things. If we just take the data at face-value, rather than assuming it is incorrect, misreported, or falsified, what does the data tell us? It tells us that AAL 11 existed but that it never took off. See below:


 
The wheels-off data is recorded automatically and electronically, the fact that the entry exists shows that AAL 11 was scheduled. The fact that the data shows the time as 00:00 indicates that the wheels never moved. This corresponds exactly to what Elizabeth Williams saw and described in her account. The plane was there and had not taken off. If Elizabeth Williams is correct in what she saw, then the entry in the BTS database for AAL 11 exactly matches what she described. So we have two witnesses now who testify that the plane labelled as AAL 11 never took off that morning: Elizabeth Williams, who says it twice, unambiguously, and the NTSB data, which shows that the plane never moved from Gate 32. Another fact is, the 9/11 Commission alleged that some passengers boarded AFTER pushback from gate, which is troubling. 

Aircraft Communications Addressing and Reporting System (ACARS) discrepancies 

The Aircraft Communications Addressing and Reporting System (ACARS) is a device used to send messages to and from an aircraft. Very similar to text messages and email we use today, Air Traffic Control, the airline itself, and other airplanes can communicate with each other via this "texting" system. ACARS was developed in 1978 and is still used today. Similar to cell phone networks, the ACARS network has remote ground stations installed around the world to route messages from ATC and the airline, to the aircraft depending on its location and vice versa. https://www.skybrary.aero/index.php/Aircraft_Communications,_Addressing_and_ReportingSystem 

According to the official ACARS data contained in the PDF document - 5 AWA 898 Printout between 11:47:30 a.m. (7:47:38 a.m. EST) and 12:00:15 p.m. (8:00:15 a.m. EST) American Airlines Flight 11's ACARS (Downlink) messages sent from the airplane indicates a discrepancy in the identity of the flight number. The flight number is identified as: AA0000. This should not be the case. Note, there is a noticeable 9 minute gap in the ACARS data communications when the discrepancy occurs just before AAL 11 is due for take-off at 8:01 a.m. EST. The anomalous flight number AA0000 does not exist, yet lists the correct tail number N334AA. In the other instances, it shows the correct flight number AA0011 and correct tail number N334AA. Why is there a 9 minute gap in the ACARS data?


The ACARS data is sent automatically to the airline, and then the airline forwards the data to the BTS on a regular basis. Ostensibly, no human intervention is involved, thus no human failure is possible, suggesting an airplane with the tail number N334AA took-off without an assigned flight number to it, which was not recorded in the BTS data base? Does this explain the BTS listing for AAL 11’s tail number as “unknown”, indicating that it a different airplane that was at Gate 32 which was not AAL 11, and did not take-off, which was recorded in the BTS data base? This explains the official discrepancies in relation to AAL 11 and answers the confusion why the BTS data-base reported AAL 11 as not taking off, and the account of Amy Sweeney in her first phone call at 8:30 a.m. (“Flight 12 at Gate 32 had two flight attendants stabbed.”) indicating that the airplane was still grounded at Gate 32?  Phone Call Transcription FBI Document: https://www.scribd.com/document/14094215/T7-B17-FBI-302s-of-Interest-Flight-11-Fdr-Entire-Contents

AAL 11 still airborne after it "allegedly" crashed at 8:46 a.m.

In the official narrative it has never been adequately explained why information of AAL 11 still being airborne after it "allegedly” crashed into the North Tower were officially reported. It appears from the Federal Aviation Administration (FAA) and North American Aerospace Defense Command (NORAD) communications recordings that AAL 11's last known coordinates were (40'38N 074'03W) which locates AAL 11 - 5.77 miles past the North Tower according to the ATC communications, and heading towards the Washington, DC. area.
 

In this short video I made from the FAA and NORAD communication recordings I include the relevant communication segments: https://www.bitchute.com/video/o70FbWu5QflU/

 

Official Explanations for this Evidence:


In the aftermath of 9/11 the scramble of Langley Fighters has been described by the Defence Department as a response to the hijacking of AAL 77, or United 93 (UAL 93), or a combination of the two. Yet the report of AAL 11 heading towards Washington, DC. as the reason for the Langley Fighter Jets to be scrambled does not reflect what is captured in the taped conversations at NEADS or in taped conversations at FAA centres, on chat logs compiled at NEADS and NORAD. In reality at 9:24 a.m. when the fighter jets were scrambled from Langley, NEADS wasn’t even aware that AAL 77 or UAL 93 were hijacked. Why did the Defence Department lie about this? Shortly after 9/11, a time-line provided by senior Defence Department officials to CNN will state, NORAD orders jets scrambled from Langley in order to “head to intercept” AAL 77.

Major General Larry Arnold, the CONR commander, will give a different explanation. He will tell the 9/11 Commission, “we launched the aircraft out of Langley to put them over top of Washington DC, not in response to AAL 77, but really to put them in a position in case UAL 93 were to head that way.” Major Nasypany will tell the 9/11 Commission that the real reason for the Langley jets are scrambled and directed toward Baltimore area is to position them between the reportedly southbound AAL 11 and Washington, DC, as a “barrier cap”. It seems NORAD deliberately misled Congress and the 9/11 Commission by hiding the fact that the Langley scramble takes place in response to the report that AAL 11 still airborne.
 


Emergency Transmitter Locator (ELT) went off over two minutes before AAL 11 allegedly crashed into the World Trade Center?

Another discrepancy in the official data supports the case that AAL 11 didn't crash into the North Tower is due to the timing of the Emergency Transmitter Locator (ELT) going-off over two minutes before AAL 11 crashed at 8:46 a.m.

The Emergency Locator Transmitters (ELT) are emergency transmitters that are carried aboard most general aviation aircraft in the U.S. In the event of an aircraft accident, these devices are designed to transmit a distress signal on 121.5 and 243.0 MHz frequencies. ELTs are mounted aft in the airplane, and designed to be triggered upon impact or may be manually activated using the remote switch and control panel indicator in the cockpit. Activation of the ELT triggers an audio alert, and 406-MHz ELTs transmit GPS position for search and rescue. [Emergency Locator Transmitters – AOPA]. https://www.aopa.org/advocacy/aircraft/aircraft-operations/emergency-locator-transmitters

According to the 9/11 Commission, AAL 11 crashed into the North Tower at 8:46 a.m. [The 9/11 Commission Report: Final Report of the National Commission on Terrorist Attacks Upon the United States. New York: W. W. Norton & Company, 2004, p. 7.] However, two and a half minutes earlier, David Bottiglia, an air traffic controller at the FAA's New York Center, received an important message from one of the planes in the airspace he was monitoring. At 8:44 a.m. the pilot of U.S. Airways Flight 583 told Bottiglia: "I just picked up an ELT on 121.5. It was brief, but it went off." (121.5 megahertz is an emergency frequency that ELTs are designed to transmit their distress signals on.) A minute later, about 90 second before AAL 11 crashed into the WTC another plane in the New York Center's airspace reported the same thing. The pilot of Delta Airlines Flight 2433 told Bottiglia: "We picked up that ELT, too. But it's very faint." [Transcript of United Airlines Flight 175] - https://www.nytimes.com/2001/10/16/national/transcript-of-united-airlines-flight-175.html 


According to author Lynn Spencer, "several" facilities picked up the ELT signal around this time. [Lynn Spencer, Touching History: The Untold Story of the Drama That Unfolded in the Skies Over America on 9/11. New York: Free Press, 2008, p. 50.]. 

Peter McCloskey, a traffic management coordinator at the New York Center, later recalled that the ELT had gone off "in the vicinity of Lower Manhattan." [Memorandum for the Record: Federal Aviation Administration (FAA) New York Air Route Center Interview with Peter McCloskey." 9/11 Commission, October 1, 2003].

And, around the time AAL 11 crashed into the WTC, a participant in an FAA teleconference stated, "We got a report of an ELT in the area that (the radar track for Flight 11) was in." (Before it disappeared from radar screens, the track for AAL 11 had indicated the plane was about 20 miles from New York's JFK International Airport). [9/11 Air Traffic Control Transcript] https://www.scribd.com/document/13484898/9-11-Air-Traffic-Control-Transcript 

Additionally, while an ELT went off two minutes before AAL 11 crashed into the WTC, it appears that no ELT went off at the time of the crash itself at 8:46 a.m. as it should have done. This is analogous to United Airlines “Flight 175” (UAL 175) which “allegedly” crashed into the South Tower at 9:03 a.m. where an ELT signal was activated and transmitted in the New York area four minutes before at 8:59 a.m. The pilot of 'Flight 583', who had reported the ELT signal before the North Tower was struck, told David Bottiglia at the New York Center that he had noticed another ELT going off. The pilot said, "I hate to keep burdening you with this stuff, but now we're picking up another ELT on 21.5." Again the same as the previous crash with AAL 11, with the ELT being activated minutes before UAL 175 crashed into the South Tower, and no ELT being activated at the time of the crash itself. Furthermore, there is no evidence cited of an ELT reported with United Airlines ‘Flight 93' and there is no evidence cited that an ELT was activated for American Airlines 'Flight 77', thus indicating none of the four airplanes listed as being involved on 9/11 crashed at any of the "alleged" targets named in the official 9/11 narrative.  

The ELT activated over Ann Arbor, Michigan at 9:53 a.m.

An ELT was broadcast/transmitted over Ann Arbor, MI. at 13:53 p.m. PST, 9:53 a.m. EST. This ELT has not been "officially" related to any of the four alleged airplanes listed as involved on 9/11. However according to this evidence it indicates that an airplane crashed in Ann Arbor at 9:53 a.m. but has never been accounted for as any airplane crash taking place. Note: in the communication between the two controllers it appears there is an audio drop-out, or editing done, just after when the controller say "wait that doesn't make sense", and the other controller replies "yes it does, it...(audio drops-out or is edited)". The controller seems to go on to explain something to the other contoller, however there's an audio drop-out or edit towards the end? Why was this information removed? What was being concealed about this ELT occurrence?



There is no evidence that an airplane crash took place in Ann Arbor, MI. at 9:53 a.m. This has never been reported officially as happening, however the incident of the ELT being activated was officially reported. 


Does this indicate that ELTs were being broadcast/transmitted which were part of the many military training exercises taking place on 9/11, where it has been alleged, simulated airplane hijackings were in progress during the morning on 9/11. The Ann Arbor, MI. ELT could explain why ELT's were being broadcast too early in the case of AAL 11 and UAL 175 ahead of their "alleged" crashes?
       

The official ELT evidence alone implies that none of the two airplanes crashed at their targets. The evidence of ELT signals being broadcast/transmitted in the New York area before the World Trade Center towers were hit raises serious questions about the official narrative of the 9/11 attacks. If ELTs had been activated, this should have been at the times the airplanes crashed into the towers, not several minutes beforehand. But while a number of Air Traffic Controllers (ATC) mentioned the ELT signals in their interviews with the 9/11 Commission, the 9/11 Commission Report offered no explanation for this anomalous evidence. For example, where the sources of the ELT signals originated from? Or were they from somewhere else? And were the transmitters themselves ever found? After all, according to the FAA, "In most installations the [ELT] is attached to the aircraft structure as far as practicable in the fuselage; or in the tail surface, in such a manner that damage to the beacon will be minimized in the event of a crash impact." http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgNPRM.nsf/0/ae86aa83c819fdbd86256819006c1c0f!OpenDocument

Summary & Conclusion


The mystery surrounding the gate discrepancy could suggest that AAL 11 did not take-off, as reflected in the BTS data-base, which recorded AAL 11 as not leaving the ground. Also ACARS data indicates a discrepancy with a non-existent flight number which happens leading up to AAL 11's "alleged" take-off, which was clearly recorded in the ACARS telemetry data "downlink" from the airplane. There is no reason to suggest why this should happen. Furthermore these two pieces of evidence cited could indicate that perhaps another airplane actually took-off instead, which could explain the discrepancy regarding the gate departures. To support this is the evidence of Amy Sweeney in her first phone call at 8:30 a.m. who said: “Flight 12 at Gate 32 had two flight attendants stabbed.” Phone Call Transcription FBI Document: https://www.scribd.com/document/14094215/T7-B17-FBI-302s-of-Interest-Flight-11-Fdr-Entire-Contents. This prompted Woodward and Williams to check Gate 32, where they observed an "empty airplane" at the gate, although strangely this was omitted in Woodward's account in the - 9/11 Commission Memorandum Report. WHY? Moreover, Sweeney's phone call confirms that she referred to 'Flight 12' and Gate 32. Does this further support the discrepancy with the flight number which is reflected in the ACARS data leading up to the take-off? Additionally, evidence suggests that an airplane identifying itself as AAL 11 with the (correct) tail number: N334AA was 5.77 miles past the North Tower after it was allegedly meant to have crashed into the North Tower at 8:46 a.m. according to Air Traffic Control's last known "official" latitude-longitude coordinates. The official ELT evidence alone does not support AAL 11 crashing into the North Tower, because it was activated/broadcast too early before the crash itself, thus indicating it was not AAL 11 involved in the event at the North Tower, which the NORAD communication recordings support, indicating that AAL 11 was heading towards Washington, DC. area. (My speculation to land at Reagan National Airport where UAL 93 landed at 10:28 a.m. Interestingly, Reagan National Airport was the only airport to close for 23 days after 9/11). This is also reinforced by reports of a airplane heading towards Washington, DC. which passed-by the White House, heading from the direction that AAL 11 would have been flying towards. An added note is, none of airplanes bound for Los Angeles (LAX) were listed on the arrivals board, and even more strangely none of the passenger's relatives were at the airport to meet any of the passengers, which could be expected, even taking into to account of what unfolded. 

On a final note...


I have suspected for a long time that the four airplanes allegedly involved on 9/11 where part of a "real world" simulated hijacking, which was most likely part of the war-games exercises happening on 9/11. I consider none of the airplanes which were named by the 9/11 Commission crashed into their alleged targets. Something else took place at each event that did not involve the four airplanes. The evidence does not support the official narrative and I feel the evidence cited here in this blog-post goes someway to support my suspicions.

I will always keep an open mind and allowance of new evidence which will warrant further enquiry, which may form a new updated hypothesis in the future.

Thank you for reading and caring!


Friday 24 January 2020

The Naudet Disappearing and Reappearing Wing Study

By Mark Conlon

In this short analysis I am studying an anomaly captured in 12 frames taken from the Naudet Brothers video footage of the "alleged" 2nd plane just before it impacted the South Tower. In the video footage it captures the plane's wing disappearing for 6 of the 12 video frames. See below:


Some researchers believe that video compression is responsible for the plane's wing disappearance, while others say it is because of the reflection of the sun light off the wing. I explore this more in my two previous blog articles here: The Disappearing and Reappearing Wing Study and The Disappearing Wing Study (2)


I demonstrate that from other different video camera locations which captured the same anomaly, however in some videos the plane's wing is only disappearing for one frame only, whereas in higher quality video cameras such as the one the Naudet Brothers used the plane's wing is captured disappearing for 6 frames. This does make me question whether this was the reason why we have never seen any professional news camera crew footage of the 2nd plane from the ground? Were the news media camera teams kept away in case they captured more anomalies like this of the plane in their higher quality video recording equipment, which would have shown more detail of the anomalies with the plane?

It is interesting to note, that a number of eyewitnesses that witnessed the 2nd airplane describe it as exactly what we see in the Naudet analysis image below: (a smaller looking airplane). 




"We saw a plane flying low overhead which caught all of our attention. We looked up. It was making a b-line for the World Trade Centre. It was very low, extremely low, not a big plane like an airliner …uh… but not a tiny propeller plane, a small, small jet plane."- Credited to: Mary Cozza

We’re walking the dogs and we saw a plane flying really low, a jet, a small jet, and it flew directly into the World Trade Center..”- Credited to: (news report) 

I saw it come up from the left, and I saw the plane coming through to the building, go inside, a small plane….no, no, it was plane, you know, like they teach the people to pilot a plane, a small plane, you know, it was that kind of plane…, and I never saw that plane before. It's like something, I don't know, it's like they worked with the motors, I never saw a plane like that before”- Credited to: Karim Arraki

"At that point we were still not sure that it was a plane that had hit the tower. There was some talk from the civilians coming down that a plane hit. The consensus was that it was a small plane."- Credited to: Roy Chelson  

The Complete Impossibility of Video Fakery, CGI Planes & Video Compositing...
 
Many researchers attempt to explain many of these anomalies suggesting that the planes were inserted CGI graphic planes or composited planes into the TV media footage or the amateur video footage later. A question I have regarding this theory is: Why would the perpetrator's insert CGI planes which were NOT convincing enough or full of glitches? This is illogical. Also another difficulty is, how did they control all of the eyewitnesses in NYC of those who witnessed a planes hitting the buildings, and please note, before even seeing anything on TV or media coverage? I believe this would be impossible. At the same time we are yet to see any videos put into the public domain showing no plane at all in the video footage. One would think at least one video slipped through the net over the last 18 years and surfaced on the internet on at a public gathering. No matter what anybody tells you their are reliable witnesses who seen what they took to be a plane in the sky. The "video fakery" promoters never confront this issue, only to make empty accusations calling all the eyewitnesses, videographers and photographers liars, crisis actors or part of the conspiracy. They provide no credible evidence to support their "bogus" claims.

Image Projection Technology

As many may know we have already established with research by Richard D. Hall and his 3D Radar Analysis, Andrew Johnson, Chris Hampton, Conspiracy Cuber and myself, that the planes on 9/11 were most likely the result of some type of advanced "image projection" technology which were videoed and photographed by various eyewitnesses in NYC and also used at the Pentagon and Shanksville. However this technology was not without faults as captured in the 2nd plane videos, such as the crash physics and anomalies with its wings and tail section. From my own research I have already demonstrated that various 9/11 researchers are "falsely" promoting "video fakery" as the answer to many of the anomalies captured in the 2nd plane impact videos. The promotion of "video fakery" was a clever "Psychological Operation" which was circulated to "cover-up" the existence of the "advanced" image projection technology. It has been the aim by those 9/11 researchers to promote this "false" explanation to conceal such technology.
 
For further study in this area, I suggest watching the above documentary film by Chris Hampton: 9/11 Alchemy "Facing Reality"

Wednesday 8 January 2020

Disinformation Comments "Setting The Record Straight"

By Mark Conlon

It is with great angst that I have to write this short blog post, however it is necessary in order to set the record straight regarding false information which is being attributed to me by AnneBeck58 (Anne Beckett) in relation to the 9/11 airplanes research I have conducted. 

I came across the comments on the 5th January 2020 by Anne Beckett on this website here: http://incamera.info



AnneBeck58 writes about me 

"He seems to believe in (De’ak) missiles. I don’t know how he can go with any of that and not only because silly Grandpa =Yankee yammers on about it, making no sense at all". 

My Response To This Claim 

This is inaccurate, I have never supported Steve De’ak’s “multiple missiles” theory. It is well documented by myself and Steve De’ak that we do not share the same interpretations of the airplane crash evidence. In fact we have had several disputes with each other in the past which is documented on Steve's website.

For Anne Beckett to align my research with Steve De’ak’s is a misrepresentation of my research. I have never suggested “multiple missiles” were involved at any of the airplane crash events. This is also reflected in all the research I did for Chris Hampton’s film - 9/11 Alchemy “Facing Reality”.

Anne Beckett also claimed in her comments that I was “extremely” rude to her. Anyone who knows me will know this to be untrue. I was not rude to Anne Beckett, challenging her assumptions yes, but not rude, even despite her condescending nature towards me during our conversation, whereby she showed no interest or respect for my knowledge in this area of 9/11 studies, publishing over 50 articles along with the various interviews I have done with Richard D. Hall, Unite Planet and my contributions in the 9/11 Alchemy “Facing Reality” film. Perhaps if she had bothered to read my blogs or watch the film she would know my position on the matter. Anne Beckett failed to provide me with any links to her own research after several times of me asking, whereby she cut-off the conversation abruptly unfortunately, or conveniently for her.

It is interesting in further comments she made how Anne Beckett claims she heard Andrew Johnson “talking about it in not the kindest manner”.


In her comment Anne Beckett is implying that Andrew Johnson is making reference to myself and Steve De’ak. This is untrue. She has falsely linked me to De’ak’s “multiple missile” theory as though Andrew was commenting about myself and Steve De'ak. Andrew Johnson knows very well my personal position regarding Steve De’ak’s “multiple missile” theory, that I do not, or ever have in the past or present supported the use of “multiple missiles” on 9/11. For Anne Beckett to suggest Andrew Johnson was talking about myself when possibly making reference to Steve De’ak's theory is grossly inaccurate, but more importantly misquoting Andrew Johnson himself. I suggest Anne Beckett should apologise to Andrew Johnson for using his name inaccurately in her comment above. I am sure Andrew wouldn’t appreciate the inaccurate implication she is making about his comment inferring about myself, when in reality Andrew was most likely talking about De'ak alone.  

My Official Position

I have never supported the idea or theory that “multiple missiles” were involved in the 9/11 airplane crashes. I have pondered the use of a missile that could be cloaked with an airplane image around it, however a missile would not make an airplane shaped hole in a building or ground. So I have believed something more would have been at play to create the airplane shaped holes. I tend to use the term "delivery system" in my later research, not missile as this is biasing what I am observing in the video and photographic evidence. I have learnt since that the military use the term "delivery vehicles". 

I cannot rule out the use of a single “delivery vehicle” projecting a cloaked image projection around itself of an airplane flying through the sky which was not always convincing depending on which angles and locations people were observing, photographing and videoing the airplane, or whether some type of magnetic field interference affected the image projection itself (as Chris Hampton suggests in his film), because of the anomalous issues (missing wings and tail section) of the projected image as the airplane gets closer to the WTC South Tower. Also to be considered, is whether the high quality video cameras captured the airplane image projection midway to being drawn due to the varying shutter speeds of the video cameras as seen in the Luc Courchesen video and also the second hit Naudet video, where 6 frames shows the missing wing, which was also captured in other videos and from different angles. 



I also cannot rule out the possibility that there was external locations were the airplane image was being broadcast/projected from, meaning that there was nothing actually in the sky apart from a projected image of the airplane heading towards the WTC Towers. I can to some degree show evidence of field interference at all 4 airplane crash events and 3 crash sites, indicating the use of directed energy to create the airplane holes in the WTC buildings, Pentagon Building and in the ground at Shanksville which is highlighted in the - 9/11 Alchemy “facing Reality” film, especially in relation to the flashes, magnetometer data, seismic disturbances and water features installed at the 3 crash sites.

I compared the airplane crash holes damage at the WTC towers to the “Hutchison Effect” (also ‘Conspiracy Cuber’ did) along with other “Blooming Effects” captured on the morning news regarding the formation of holes that appeared in the road in New York, before the event itself happened, something which Anne Beckett attempted to take ownership of during our conversation, although she didn’t realise (I don’t believe) at that point it was myself who actually made this discovery and connection to the Hutchison Effect, which I posted in Andrew Johnson’s 9/11 Facebook Group, and was included in Chris Hampton’s film in August 2018, whereby I produced image comparisons inset for use in his film. I did ask Anne Beckett to provide me with links to her own research, however she cut the conversation short at this point and I didn’t hear back from her again afterwards.
 
Conclusion

I can only conclude that this was an attempt by Anne Beckett to spread disinformation about my research position, and ostensibly blacken my character for some reason judging by her comments she has made. It also appears she was trying to caused division, or imply division between myself and Andrew Johnson. This is a common pattern of behaviour I have experienced in the past, due to the nature of the research I am conducting into the airplane crashes and image projection technology. It is an interesting note: Anne Beckett is a supporter of “video fakery” which was a major Psychological Operation (Psy-Op) which I exposed and is something that I have written about extensively on my blog, and those promoting it, which I demonstrated how it was used to conceal and misdirect people away from the image projection technology that was involved, which I am trying to expose which created the illusions of the airplanes in the sky at all 4 airplane crash events on 9/11. 

Wednesday 4 December 2019

Photos: From the Ferry in Battery Park

By Mark Conlon

It has been claimed by many 9/11 researchers in the past and present, that no other people's photos exist or have been produced from the same location of Michael Hezarkhani or Carmen Taylor. This is simply incorrect. It is an established fact that both Michael Hezarkhani and Carmen Taylor were situated on the top deck of a ferry in Battery Park during the second airplane impact into the South Tower.

 Photo: Carmen Taylor

Video Still Image: Michael Hezarkhani

I am going to share two other people's photos which were taken just after the second airplane impacted the South Tower. The photos were captured by John McCaskill and Sara Jones. 


Judging by Sara Jones' photo she captured the top of a person's head/hair. Also similar to Carmen Taylor who also captured the top of a person's head/hair. It appears both Sara Jones and Jack McCaskill were located on a lower level of the ferry boat compared to both Carmen Taylor and Michael Hezarkahni. I think this debunks Killtown's theory that no other people were on the ferry boat with cameras.

Update: 5th March 2020

911AnalysisVideo's YouTube Channel posted two new Battery Park ferry boat photos. See below:

 
The photos were taken by Ritsu(Risa Hirayama) and posted at her Instagram profile: She wrote: “Today is 9.11 Memorial Day. This picture took by me 9/11 2001 from Battery park. I'm so scary that bring back to memory that days happened.” https://www.instagram.com/p/s09lu6AHvt/  


Also watch my "Setting The Record Straight About The Michael Hezarkhani Video" analysis, where I discuss some of the false information that has been circulated about the Michael Hezarkahni video.

Monday 24 June 2019

Revealing Facts About Simon (Shack) Hytten's Background

By Mark Conlon

In September 2013 I posted a blog showing how Markus Allen (a 'video fakery' promoter) put-out a video claiming the Michael Hezarkhani video had a CGI glitch contained in it, when the airplane's wing passed behind a building in the foreground. This turned-out to be false, and I demonstrated why in this blog post. Following-on in January and July 2014, I also wrote two more blogs showing how Markus Allen's other two claims were false about the Michael Hezarkhani video, where he claimed buildings were missing, in the video and the location where Michael Hezarkhani took his video didn't exist. I demonstrated thoroughly how this was not true.



In this revealing exchange between Markus Allen and Simon (Shack) Hytten, the maker of the September Clues film 2007-8, in the interview he admits to having done work for the European Space Agency. This is revealing because of other interesting family members connections they have. For example, Shack's brother Mario, was a racing car driver and was sponsored by the brother of Osama Bin Laden, and Shack's father worked for the United Nations (UN). Is this just a coincidence? The interview can be found here: 
https://www.bitchute.com/video/qTCxMpWiL1ah/

Sunday 30 December 2018

No Emergency Locator Transmitters (ELTs) Activated When the Four Planes Crashed on 9/11

By Mark Conlon 


The Emergency Locator Transmitters (ELT) are emergency transmitters that are carried aboard most general aviation aircraft in the U.S. In the event of an aircraft accident, these devices are designed to transmit a distress signal on 121.5 and 243.0 MHz frequencies. ELTs are mounted in the airplane, and designed to be triggered upon impact. Activation of the ELT triggers an audio alert, and 406-MHz ELTs transmit GPS position for search and rescue. [Emergency Locator Transmitters – AOPA]. https://www.aopa.org/advocacy/aircraft/aircraft-operations/emergency-locator-transmitters


According to the 9/11 Commission, AAL 11 crashed into the North Tower at 8:46 a.m. [The 9/11 Commission Report: Final Report of the National Commission on Terrorist Attacks Upon the United States. New York: W. W. Norton & Company, 2004, p. 7.] However, two and a half minutes earlier, David Bottiglia, an air traffic controller at the FAA's New York Center, received an important message from one of the planes in the airspace he was monitoring. At 8:44 a.m. the pilot of U.S. Airways Flight 583 told Bottiglia: "I just picked up an ELT on 121.5. It was brief, but it went off." (121.5 megahertz is an emergency frequency that ELTs are designed to transmit their distress signals on.) A minute later, about 90 second before AAL 11 crashed into the WTC another plane in the New York Center's airspace reported the same thing. The pilot of Delta Airlines Flight 2433 told Bottiglia: "We picked up that ELT, too. But it's very faint." [Transcript of United Airlines Flight 175] - https://www.nytimes.com/2001/10/16/national/transcript-of-united-airlines-flight-175.html 

According to author Lynn Spencer, "several" facilities picked up the ELT signal around this time. [Lynn Spencer, Touching History: The Untold Story of the Drama That Unfolded in the Skies Over America on 9/11. New York: Free Press, 2008, p. 50.]. 

Peter McCloskey, a traffic management coordinator at the New York Center, later recalled that the ELT had gone off "in the vicinity of Lower Manhattan." [Memorandum for the Record: Federal Aviation Administration (FAA) New York Air Route Center Interview with Peter McCloskey." 9/11 Commission, October 1, 2003].

And, around the time AAL 11 crashed into the WTC North tower, a participant in an FAA teleconference stated, "We got a report of an ELT in the area that (the radar track for Flight 11) was in." (Before it disappeared from radar screens, the track for AAL 11 had indicated the plane was about 20 miles from New York's JFK International Airport). [9/11 Air Traffic Control Transcript] https://www.scribd.com/document/13484898/9-11-Air-Traffic-Control-Transcript 

Additionally, while an ELT went off two minutes before AAL 11 crashed into the WTC, it appears that no ELT went off at the time of the crash itself at 8:46 a.m., as it should have done. Likewise with United Airlines Flight 175 (UAL 175), which “allegedly” crashed into the South Tower at 9:03 a.m. An ELT signal was transmitted in the New York area four minutes before, at 8:59 a.m. The pilot of Flight 583, who had reported the previous ELT signal, told David Bottiglia at the New York Center that he had noticed another ELT going off. The pilot said, "I hate to keep burdening you with this stuff, but now we're picking up another ELT on 21.5." Again, the same as the previous crash with AAL 11, with the ELT being transmitted four minutes before UAL 175 crashed into the South Tower. Interesting there was no ELT transmission activated at the time of the two crashes themselves, which should have happened.  

Furthermore, there is no evidence cited of any ELTs reported for American Airlines Flight 77 or United Airlines Flight 93 at the times of both crashes. This indicates that none of the four planes listed as being involved on 9/11 crashed at any of the named targets in the official 9/11 narrative.

The ELT activated over Ann Arbor, Michigan at 9:53 a.m.

Interestingly, an ELT was transmitted over Ann Arbor in Michigan at 13:53 p.m. PST, 9:53 a.m. EST. This ELT has not been officially related to any of the four alleged planes listed on 9/11. However, according to this evidence it indicates that a plane crashed in Ann Arbor at 9:53 a.m., but has never been accounted for or addressed by the authorities. Note, in the communication between the two controllers it appears there is an audio drop-out, or has been editing done, just after when the controller says "wait that doesn't make sense", and the other controller replies "yes it does, it... (audio drops-out or is edited)". The controller seems to go on to explain something to the other controller, however there's an audio drop-out or edit towards the end? Why was this information omitted? What was being concealed about this ELT occurrence?


Does this indicate that ELTs were being falsely transmitted which were part of the many military war games training exercises taking place on 9/11, where simulated scenarios of plane hijackings were taking place. The Ann Arbor ELT could explain why ELTs were being transmitted too early in the case of AAL 11 and UAL 175, ahead of their alleged crashes?
       
The official ELT evidence alone implies that none of the four planes crashed at their targets. The evidence of ELT signals being transmitted in the New York area before the World Trade Center towers were hit raises serious questions about the official plane’s narrative on 9/11. If ELTs had been activated, this should have been at the times the airplanes crashed into the towers and not several minutes beforehand. But while a number of Air Traffic Controllers (ATC) mentioned the ELT signals in their interviews with the 9/11 Commission, the 9/11 Commission Report offered no explanation for these discrepancies. For example, where the sources of the ELT signals originated from? Or were they from somewhere else? And were the ELT transmitters themselves ever found? After all, according to the FAA, "In most installations the [ELT] is attached to the aircraft structure as far as practicable in the fuselage; or in the tail surface, in such a manner that damage to the beacon will be minimized in the event of a crash impact.
http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgNPRM.nsf/0/ae86aa83c819fdbd86256819006c1c0f!OpenDocument

What we can determine from all the available evidence is, no ELT transmissions were activated at any of the four plane crash impacts on 9/11, which is what should have happened.

Update: Feb 2024

This is document is from the 9/11 Commission investigation files, in relation to an ELT being manually triggered. According to the Commission document, and their experienced pilot testimony of Paul Thumser, ELTs cannot be manually triggered in Boeing 767s.



This is damming evidence, because AA11 which is a Boeing 767 triggered an ELT two minutes too early before it allegedly crashed into the North Tower, which is impossible, but also even more seriously damaging is, there was no ELT at the point of the impact of the plane into the North Tower, where the ELT should have been activated. Also, UA175, which was also a Boeing 767, also triggered an ELT four minutes too early before it allegedly crashed into the South Tower, which again is impossible, and also did not activate an ELT at the point of impact into the South Tower either, which should have happened. Just to add, neither AA77 or UA93 which were Boeing 757s, triggered any ELT either before or at the points of impact which is highly questionable, and seriously damaging for the official plane narratives of the four planes. This calls into question all four plane crash stories, but also indicates that none of the four planes named by authorities crashed into the named targets. Something else took place instead with these four events. The evidence points to this conclusion. 


Friday 28 December 2018

The NORAD tapes are proof 'Delta 89' was not 'Delta 1989' on 9/11


Three minutes after the Pentagon was hit, a strange aircraft with call sign "Delta 89" popped up on the radar screens of air defence Commander Kevin Nasypany's crew. It signaled a hijacking and was tracked by NEADS for three minutes before it suddenly disappeared again.

In the “official” story, Delta 89 doesn't exist. Better to say, for the 9/11 Commission as well as authors Michael Bronner and Lynn Spencer ("Touching History"), the plane tracked by NEADS as Delta 89 was in fact Delta 1989, and nothing more than a case of sloppy communication, however, this is impossible. It is easy to show that, apart from the different call sign, Delta 89's transponder code, flight plan and flight path differed from Delta 1989. The evidence is present on the NORAD tapes, a source of impeccable authenticity because you can virtually look over the shoulder of NEADS technicians while they're tracking Delta 89 on their displays. 

To demonstrate why Delta 89 was not identical with Delta 1989, I shall go through the NORAD tapes step by step and comment on them, however before starting the analysis, we need to get a rough understanding how NEADS radar works, as it is quite different from the FAA radar. Lynn Spencer explains in her book "Touching History" (Pg.32).

Slow and cumbersome, and not nearly as user friendly as more modern equipment, the NEADS monochromic radar displays are not designed to take internal FAA radar data or to identify radar tracks originating from inside the United States. The system offers little, if any, such low-level coverage over the country.

Their radar scopes are filled with hundreds of radar returns not just from aircraft but from weather systems, ground interference. and what's called anomalous propagation - false returns caused by conditions in the atmosphere, or by such obstruction as flocks of birds.

So the NEADS radar screen is filled with countless radar blips from planes - without the identifying data block common to FAA radar, however - as well as irregular radar returns. Only on special occasions like emergency cases, a plane's blip is highlighted and provided with a data tag. Lynn Spencer (Pg. 25/26).
 
Pilots have three special transponder codes that they can dial in: 7500 for hijacking, 7600 for loss of radio, and 7700 for other emergencies. Any of them will cause the airplane's tag to light up on his radar screen, but he doesn't see any such tag.

Now we are ready to start with the analysis. The complete transcripts are here. It is highly recommended to listen to the "original" audio file of the following channels (scroll forward to the respective time).

Channel 4   - 1:14:00
Channel 7   - 1:09:00
Channel 21 - 1:09:00

(Channel 7)
 
9:39:31 Colin Scoggins, Boston Center military. Hijacked aircraft Delta nineteen eighty-nine. I give you the code 1304, presently due south of Cleveland, heading westbound, destination Las Vegas. And is this one a hijack, Sir? We believe it is. Didn't it squawk hijack? We don't umm...I don't know - it's squawking 1304 if you want to crank him up. 767, altitude 350. Where did it take-off? Out of Boston. We're trying to get a tail number on that if you want to get someone up.

90 seconds before Delta 89 appears on stage, NEADS receives a verbal message from Colin Scoggins, the military liaison controller at Boston Center, regarding Delta 1989. The message is affirmed with professional calm. NEADS knows now that one of the many anonymous radar blips near Cleveland is a possible hijack. Note that Scoggins is wrong on the destination of Delta 1989: that was Los Angeles, not Las Vegas.
  
(Channel 4)
 
9:41:00 - Delta 89 is a hijack, they think it's a hijack, south of Cleveland, we have a code on him now

9:41:05 - Good! Pick it up! Find it!

9:41:05 - Another one. I hear someone going from Boston going to Las Vegas - another one

9:41:13 - Eight-nine. Boeing 767 Boston-Las Vegas. Another one - same place - Las Vegas

In striking contrast to Delta 1989, the appearance of Delta 89 causes big excitement among the NEADS crew. It is echoed through all of the channels. Lynn Spencer interprets this passage as a prompt reaction to Scoggins's message, but there are several reasons why this cannot be the case.

The different call sign: needless to say, transmitting the correct call sign of an aircraft is an absolute must in aeronautic communication. No air traffic controller would ever get the idea to abbreviate a flight number by omitting the first two digits because that will automatically lead to massive confusion.

"We have a code on him now" - obviously, the plane has squawked a special emergency code that causes its blip to lighten up on the NEADS radar displays - just as explained above. This is immediately noticed by the NEADS crew and leads to their excited reactions. The data tag informs them about the call sign (Delta 89), the flight plan (Boston-Las Vegas), the type of the plane (Boeing 767) and the cause of the emergency: a hijacking.

"Another one - same place - Las Vegas" - NEADS is already aware of Delta 1989 which was reported 90 seconds ago by Colin Scoggins. Now Delta 89 - "another one" - appears in the same vicinity. So NEADS does not identify Delta 89 with Delta 1989, but views it as a different plane. Delta 89's blip suddenly flashes on the NEADS screens - making it easy to follow - and indicates a hijacking. In contrast, Delta 1989's blip is not spotted yet. 
 
(Channel 21)

9:41:05 - Another one. I hear someone going from Boston going to Las Vegas - another one

9:41:30  - As before is one missing. Start a search. Range 53

9:41:35  - 288 for 92 miles search only

9:41:46 - I have a 280 for 97
 
9:41:58 - I have a 287 for 97

9:42:23 - The two really close together. One used - one has a code of 7112 - the one we are next to him

To understand what's going on here, I cite Lynn Spencer again (Pg. 32).

To identify American 11, the surveillance and ID techs must go through a gruelling process. The technicians must first determine which radar data on their screens is for aircraft, which they do by monitoring its movement, which is distinctive for planes. The technician must observe for at least 36 seconds to a minute just to confirm that a blip is in fact an aircraft track. The tech must attach what's called a tactical display number to it, which tells the computer to start tracking and identifying the target. If the target is in fact a plane, then over a period of 12-20 seconds, the computer will start to generate information on the track: heading, speed, latitude, longitude, and the identifying information being transmitted by the transponder.

The NEADS technicians start a "search" for Delta 89, described by Lynn Spencer as a gruelling process. But in contrast to American 11, which had turned the transponder off, Delta 89 is tagged, enabling them to curtail the procedure. In the course of the search, they detect two planes "really close together" - Delta 89 and Delta 1989 -, and obtain the squawk code of one of them: 7112. This is not Delta 1989's code, which is 1304, so it must be the code of Delta 89. The first digit "7" indicates that it's not the ID code of a usual civilian airliner - they never begin with a 7. Instead, the 7 is reserved for emergency cases like 7500, 7600, or 7700. By squawking 7112, Delta 89 manages to pop up on the NEADS radar screens and signals a hijacking.

(Channel 4)

9:42:43 - Indy Center? Indianapolis Center: Delta eight-nine have you information on that aircraft? I want to give you a heads-up. This is another hijacked aircraft, Boston to Las Vegas with a Mode 3 of 1304. We do have contact. ((Repeats information)).

9:43:04 - I give you a Lat-Long if you need that. Go ahead. 4121 North 08215 West. I'll give you a heads-up that's all we have right now, but he's a confirmed hijack

9:43:16 - (Indianapolis Center) We don't show him in our system at this point - you are tracking him, you say? We have him on the radar, Sir - he's headed your way. He's headed our way, okay.

9:43:35 - (Indianapolis Center) Boston to L-A-S, right? L-A-X. L-A-X? I've got Vegas, Sir, whatever Vegas says. L-A-S, okay, Las Vegas. Okay, cause we don't show him in the system anywhere. Do you have Mode 3 capability or anything? He's on a 1304 code? Okay, we bring that up.

Now NEADS contacts Indianapolis Center to inform them that Delta 89 is heading for their airspace. This is evidence that Delta 89 is flying southwest- or southbound at that point because the boundary to Indianapolis Center runs 40 miles south of Cleveland. In contrast, Delta 1989 never goes south, and especially at 9:43, it is flying westbound (direction 285) according to the Cleveland Center/Delta 1989 transcript:

9:40:57 - (Lorain Radar) delta nineteen eighty nine fly heading two eight five

9:41:00 - (Delta 1989) two eight five delta nineteen eighty nine

The next radio transmission between Cleveland Center and Delta 1989 occurs at 9:44am. In between, there is no order to change the direction, which is proof that Delta 1989 is not heading towards Indianapolis Center at 9:43am like Delta 89 (according to Stacia Rountree from NEADS). 
 
Back to NEADS:

(Channel 4)

9:44:03 - Where did it go? Somebody dropped the aircraft. Who dropped the aircraft? I DON'T KNOW!

(Channel 21)

9:46:25 - (?)52 on a 49 for 59 miles searching. We got a 1304 squawk this time

9:46:53 - The 1304 guy. That's not the guy then

At 9:44, Delta 89 is suddenly "lost". NEADS doesn't know where it's gone and is unable to track it. Obviously the pilot has turned off the transponder, making himself virtually invisible. The radar technicians resume the search. At 9:46:25, they are able to identify an eligible blip, but it's Delta 1989 this time. Their comment: "that's not the guy then" - the 7112 guy they lost and were looking for.

Now it's time to sum up the data:


Did the 9/11 Commission overlook these discrepancies? Unlikely. Did Commission staffers not check Channel 21 with the "code 7112" message? Oh yes, they did! On January 23, 2004, Miles Kara, Kevin Schaeffer, and Geoffrey Brown interviewed Sgt. Susan Marie Rose, whose voice is recorded on Channel 21 as she spots "code 7112":

Commission staff asked Rose is she recalled details on tracking Delta Airlines Flight 1989 or United Airlines Flight 93 (UAL 93). She replied that she and LaMarche tracked a specific suspected hijack that they believe was flight planned from Boston to Las Vegas through Cleveland and Minneapolis Center airspace. This flight, she believed, was headed to a specific airport, and he was manoeuvring to turn into the airport to land.

Rose noted that she is uncertain whether the aircraft reflected in Commission staff's recording was one that was search only or one that was a mode three. She surmised there being two aircraft that they followed based on listening to the tapes in which she pointed out a mode three squawking code 1304. The "surmise" of Susan Marie Rose is certainly correct, but squawk code 7112, evidence for a second plane is simply omitted in the report. Miles Kara and his colleagues don't seem to be interested in this other aircraft, despite the strange code and the fact that it was considered a hijacking. Code 7112 and Delta 89 were simply glossed over.
 
The NORAD tapes belong to the most authentic sources for the events of 9/11, and they are certainly not faked, as everyone will attest who has listened to them. As matters stand, the tapes provide watertight proof that Delta 89 was NOT Delta 1989, Delta 89 being defined as the aircraft that was tracked by NEADS between 9:41 and 9:44.

The analysis must not stop at this point. What kind of plane was this Delta 89? Discarding exotic scenarios like a drunken pilot or a foreign intruder playing games with the air defence, the plane's known attributes allow only one reasonable explanation - Delta 89 was a simulated hijacking as part of a military exercise:

- "Delta 89" was a fake call sign. The regular Delta Airlines Flight 89 was sitting at JFK airport and scheduled to depart for Los Angeles at 3:00 p.m.

- The behaviour of Delta 89 reminds of a hide-and-seek game. To facilitate the catcher's job, it left its cover and "cuckooed" for three minutes before disappearing in the dark again. Note that military exercises are often termed "war games".

- Delta 89 didn't squawk 7500, the emergency code for a "real world" hijacking, but another irregular code - 7112 - that was immediately interpreted as a hijacking by NEADS technicians.

- According to FAA directive 7110.65, certain beacon codes are regularly assigned to planes taking part in NORAD exercises - "7112" seems to have been one of them:
     
- NORAD will ensure exercise FAKER aircraft flight plans are filed containing discrete beacon codes from the Department of Defence code allocation specified in FAAO 7610.4, Special Military Operations, Appendix 8. 


Delta 89 fulfils all conditions for an "exercise faker aircraft" whose job was to simulate a hijacking. Alternative explanations are hard to imagine. Therefore it's time now to establish the central thesis of this text: Delta 89 was a faker hijack exercise.

So what - the interested reader might ask - what impact has this insight on the official story of the 9/11 attacks? Indeed, Michael Ruppert has already pointed out the existence of at least one "live-fly exercise" (with real aircraft involved) in his book Crossing the Rubicon. Lynn Spencer notes: 

"Today's training exercise runs a number of scenarios, including a simulated hijacking in which the perpetrators overtake an aircraft for political purposes, directing it to an island in order to seek asylum". (Pg.24) So is the case of "Exercise Delta 89" important at all?

Yes, it is, because of Delta 1989, which was kind of a "doppelganger" plane with nearly identical call sign (promptly leading to confusion), identical aircraft type (Boeing 767), identical origin airport (Boston), and flying in close vicinity when Delta 89 exposed itself at 9:41. Clearly the designation "Delta 89" was carefully chosen by the war-game designers to create a mix-up with Delta 1989. This is the first indication that the on-going exercises interfered with regular civilian air traffic.

In other words: Delta 1989, in spite of being a regular airliner, played a peripheral role in the exercise. It served as a cover-up for Delta 89. At first, NEADS was alerted by Delta 89, and when this plane stopped squawking and disappeared, the attention shifted to Delta 1989, which was closely observed until its landing in Cleveland.

Half an hour after Delta 1989, another mysterious airliner in distress landed at Cleveland Airport. Just like Delta 89, its existence seems to have been covered-up through "merging" it with Delta 1989 - a doppelganger case again. This naturally leads to the question whether the eerie Cleveland plane was identical to Delta 89. Indeed, there are surprising congruences:

- Both planes were reportedly a 767
- Both planes were reportedly coming from Boston
- Both planes were suspected of being hijacked
- Both planes were covered-up by Delta 1989