9/11: Four Flights, Same Story! - No ELT’s

Source: https://mysticbazaar.substack.com/p/911-four-flights-same-story-no-elts

Welcome to my series Four Flights, Same Story, which shows unusual events, discrepancies and unanswered questions that appear to happen across all four of the 9/11 flights. One unusual occurrence involving one flight might not be much, but when the same thing happens to all four flights, it becomes worth looking into.When you start seeing there are dozens of similar occurrences across the four flights then that really does deserve a closer look. Below are the first 3 articles I have written in this series…Before I start, I would like to credit an amazing research, 9/11 Planes Research, where I first came across the information regarding the ELTs. Please check out his substack, and his latest and more detailed article on what the evidence he uncovered reveals about the ELT signals. An Emergency Locator Transmitter (ELT) is a device which sends out a distress signal following a plane crash which helps rescuers find the location of the crash. Image Recreated by AI from Reuters and Honeywell AerospaceSo what happened to the ELT’s on 9/11?These are the flights that allegedly impacted WTC 1 and WTC2 in New York.The Air Force Rescue Coordination Centre (AFRCC) provided a document to the 9/11 Commission which showed historical satellite searches for ELT signals on 9/11.The search covered a 50 nautical mile radius around JFK and was done between 8am and 10.30am on 9/11. AFRCC 9/11 Commission Document Showing Results for Location of Alleged AA11 and UA175 Impacts - See Full Document HereNo satellite detected any ELT signals within the search area that covered New York during the 8am to 10.30am time period.The same document also provided a search for ELT signals covering a 50 nautical mile radius around Regan National Airport for the same time.AFRCC 9/11 Commission Document Showing Results for ELT signal search in area of AA77s impact into the Pentagon - See Full Document HereAgain no satellite detected ELT signals were found within the Pentagon area during the requested time period.FAA records show that controllers were looking for an ELT signal following a reported sighting of the possible crash of UA93.NYC B1 Position 14 (1 of 3) Fdr- Transcript- ATCSCC Tape Position 14B Parts 1 and 2 ZNY Line 5154 - See full Document HereAt 10.07am an FAA chronology states…No ELT at this time…Once again, no ELT was detected at 10.03am, or in the location of where UA93 allegedly crashed.ATC records record discussions about three possible ELT signals on the morning of 9/11.Two very faint signals were heard in the New York Area and discussed in ATC transcripts. These signals however, were before either AA11 or UA175 had allegedly impacted WTC1 and WTC2.Another ELT signal was reported near Ann Arbor, Michigan, which is a long way from any of the official crash locations and the time it was reported did not match any of the crashes. I will cover this in more detail in a future article but to find out more please go check out the following articles by 9/11 Planes Research who originally found this info.Were any of the ELT systems from the 3 planes recovered?If they were recovered were they examined or tested to see if they were faulty or damaged?Were all of the plane’s ELT maintenance and inspection records checked?Is is a coincidence that no ELT signals were documented for all 4 of the planes, which all allegedly crashed within 77mins of each other?Were the other ELT signals that were discussed and recorded in ATC transcripts ever traced back to their sources?Thanks for reading and please let me know what you think about this in the comments. Leave a commentAlso please join my new Telegram Channel to see more interesting videos, documents and info that I find about 9/11,Mystic Bazaar - TelegramShare

🔐 Cryptographic Verification

Archived URL: https://mysticbazaar.substack.com/p/911-four-flights-same-story-no-elts

�� CONTENT HASHES:
  SHA-256:  6f07de0edcc562bcdc2c925e86eee89029398f5a84e39a635b52cd578ec3a1c8
  BLAKE2b:  236573407f7ce7c126f8b37535f0cff81a0cc10c55458c58672ca4a8a2f9af43
  MD5:      fb23a17760dd69ddc65a09d16a2a6796

�� TITLE HASHES:
  SHA-256:  b1f8cd6a6a63b6a6ba0502531a9dcb5a481177c83d02a34a8a7ded1e34aa2bdb
  BLAKE2b:  418641ab9a37c05e8a8c91b25c2546dc99a3ead35e3ad2e825c403b6f4380b95
  MD5:      52fcbe335164c842687d1cb19b48c688

�� INTEGRITY HASHES:
  SHA-256:  e7785607d68b24d1e4566149f375cd4153acff4988d87520cee18c801e8cec49
  BLAKE2b:  3c71f2bf78409b525c3bd61c18001566751e5884b28a3bed120b64d13d2dcbe8
  MD5:      b4fbc3a5833bf55da07169f88bf684ba

Archived with ArcHive - Client-side cryptographic archival system