United 93 - Things that Don't Make Sense

Well my plan for this article was simple. To find any contradictions or things that don’t add up about United 93 and do a list of these. Well, there was more too it than I thought, and I haven’t even covered the passengers and phone calls in this article.

I’m not going to lie, its driven me batshit crazy going through all the information and trying to make it make sense to myself let alone anyone else. Just as I thought I had got it figured out, I was wrong.

So the clip below, is from an amazing documentary 9/11 Alchemy - Facing Reality - and it gives an easier to understand explanation of what the hell was going on with United 93, before you read the timeline I have put together.

In a nutshell, the math ain’t mathing regarding flight 93. There are many inconsistencies between the 9/11 Commission Official Narrative and the declassified documents and data.

The Impossible Timeline

• 8.28am - Real DataBureau of Transportation Statistics Database (BTS), the Aircraft Communications Addressing and Reporting System (ACARS) both log this as the wheels off time.
• 8.42am - After being delayed for 41mins UA93 took off from Newark - Official Narrative (contradiction)
• 9.40am - Transponder was switched off. UA93 isn’t sending back information but can still be trackable on primary radar.
• 9.55am - The 2nd of two new flight plans was filed to Regan National Airport. Problem - who filed flight plans if the plane was hijacked and invisible to ATC.
• 10.00am - ATC recordings show that UA93 was travelling at 8000ft and was 11miles south of Indian Head, PA, which is just north of Cumberland.
• 10.02am - Transponder is reactivated and stays on for approx 20 seconds. United 93 is observed by Cleveland Centre controllers and is at an altitude of 8,200ft.
• 10.03am - Official Crash Time in Shanksville
• 10.03am - No Emergency Locator Transmitter was activated when UA93 crashed - Problem - all airliners carry ELTs which automatically trigger after an impact.
• 10.05am - Transponder is switched back on and indicates it is heading southeast and is 8200ft. How when it was supposed to be in a field in Shanksville.
• 10.06am - Transponder is switched off and radar contact is lost. Its last position is 15miles southeast of the official crash sight.
• 10.06am - Seismic disturbance recorded but doesn’t match a 757 impact.
• 10.10am - United Airlines are in contact via ACARS as United 93 was still receiving messages. In official ATC recordings controllers discuss last known coordinates. These are 44.34miles past the crash site - Champaign, IL. - HOW if the plane has buried itself in the ground in Shanksville.
• 10.11am - Last ACARS message received from United 93
• 10.22am - WCBC news coverage reported an unidentified plane was approaching either Dulles Airport or Regan National, which is around the time UA93 would have been coming in to land.
• 10.28am - updated flight plan shows this as the landing time at Regan National and the arrivals board shows united 93.
• 10.31am - MAJOR CONTRADICTION - BBC reports a plane has been hijacked and heading to Washington. This lines up with ATC warnings of an inbound hijacked jet toward DC.
• 10.45am - Multiple early reports state that a hijacked plane landed safely at Cleveland Hopkins and was reported as flight 93.

So what I could make of all the inconsistencies was United 93 should have buried itself in the ground in Shanksville by 10.03am. However, at least 2 other planes, calling themselves United 93, were miles away from the crash site, in different places at the same time??? Huh??

What Does This Mean?

Really, I’m not sure. It appears that there is an official narrative, of a plane crashing in shanksville at 10.03am, but we don’t just have one flight93, we have another 2 possibly 3.

One version crashes at 10.03am. Another keeps transmitting and turns on the responder until 10.06am and receives ACARS data until 10.11am, and there is another that is still being tracked by ATC heading towards Washington. Which lines up with exactly when news outlets like BBC and WCBC were reporting a hijacked plane around 10.30am with no mention of a plane crash until after 10.40am on many live news coverages.

When you line up the timelines the official story gets smaller and the contradictions get louder.

Receipts

So below is a map of the places UA93 should be and has been tracked at.

Below is transcript identifying United 93 as being close to Dulles Airport.

Below is another image to prove that United 93 was on the way too Regan International Airport

And below is a news report of United 93 landing at Cleveland Airport.

Why the below Evidence is Important!

The below report shows what officials and the media believed before the narrative became set. This article came out almost 2 hours after the official crash time, however, Clevelands’ Mayor and United Airlines were still identifying a landed aircraft as Flight 93. When you put this with the BBC’s report that a hijacked plane was still heading towards Washington at the same time, it becomes clear that multiple credible sources thought UA93 was still airborne or had landed safely. It doesn’t prove what happened, however it shows the official timeline wasn’t being communicated properly and that raises questions

Other Discrepancies

There are so many other things wrong with this flight, so I will just do a quick list instead of going into too much detail.

Confusion as to whether Flight 93 took off from Gate number 17 or from the tarmac.

Fueler Operative, who worked at Newark, spoke to the co-piolet that morning to inform him he had finished filling up the plane. However, a few weeks later a memorial was held for the staff and passengers of United 93, and the operative did not recognise either the pilot or co-pilot from their photographs so he immediately rang the FBI to tell them he saw another male in the cockpit.

The Emergency Location Transmitter, which automatically sends a signal upon crashing, so rescuers can locate the plane, did not go off.

Thanks to Mark Conlon who has been reading some of the 1,000s of declassified documents he has, this little gem was found. At 10.01am according to the document below, UA93 squawked the 7500 hijacking code, however this information was kept hidden from the public. Why wouldn’t they want the public to know this? See Below

What Does All This Mean?

I think what I am trying to point out with this article, is that no one appears to agree on a narrative for United 93. The official narrative says one thing. The declassified documents say another. The radar / ACARS / Transponder / Logs / ATC Recordings and even the live news reports say something completely different. Did United 93 crash in Shanksville? Probably not. None of it lines up with the 9/11 Commissions version of events, not even close.

Did United 93 crash in Shanksville? - Probably no

Were there duplicate flights? - Maybe

Was United 93 tangled up in a military exercise - Also Possible

After researching this, I am shocked that these contradictions aren’t more widely talked about!! What really happened to United 93. The data around this flight is all over the place, messy and in a lot of cases completely incompatible with the official story. And if you are wondering why I haven’t mentioned the passengers or their phone calls, that’s a whole other article that will be posted soon,

If you came here expecting a neat answer, Sorry, there isn’t one. But at the very least people should know just how scrambled and inconsistent the records are, clearly something isn’t right. I will be diving deeper into United 93 as I’m sure there is much more to uncover.

Let me know what you think in the comments.