Official Dulles Control Center Radar Data Confirms American 11 Was ...

Official Dulles Control Center Radar Data Confirms American 11 Was Still Airborne After The Alleged Crash

Astonishingly, it is revealed in the official AAL 11 Dulles Control Center (DCC) radar data evidence, which was only released under a Freedom of Information (FOIA) request by 9/11 Maps (Vincent Moreau) and John Farmer (via CIT/Pentacon), that American 11 flew past the North Tower according to the last known recorded Lat-Long coordinates from the Dulles Control Center (DCC) radar returns. The data also reveals that the radar return was captured at 8: 47 a.m., which is one minute after the crash time of 8:46 a.m. Additionally, American 11’s altitude is stipulated at 29,000 ft, which indicates American 11 did not descend as we have been led to believe and crash into the North Tower according to the official narrative.See below, DCC radar data, highlighted.The official DCC radar data is in complete conflict with the official favoured 84th RADES radar data, which was used in the official plane flight path studies. 84th RADES goes down at the critical time, coincidence or convenient? Thanks to researcher Charlie Kallas, who has conducted extensive studies of the 84th RADES data, Kallas reveals that the North Truro, Massachusetts ARSR-4 radar for the FAA and Air Force went down between 12:12 UTC and 13:13 UTC (8:12 a.m. to 9:13 a.m.) which is the time when American 11 was “allegedly” hijacked, and one minute before United 175 took off. Kallas states in his article…. ”This is significant because this is the critical time frame Flight 11/ Flight 175 take-off, become “hijacked” and lost as primary targets for ATC. I found a possible answer with the insight of Miles Kara. He indicated that the North Truro site went down for maintenance at that time. I didn’t recall that but I was able to find a document supporting that”.Kallas went on to say…. ”What makes this beyond coincidental, aside from the obvious, is that the radar goes down 1 minute before Flight 11 loses contact with ATC. The whole region is down at the most critical point since Pearl Harbor, and we’re suppose to believe its because of “maintenance”. Ironically, it comes back up exactly 10 minutes after the 2nd aircraft hit the WTC.” ”This also means that the 84th RADES data is incomplete and can’t be solely relied upon to verify the flights in question. I was under the impression the 84th RADES data was whole and complete. This is beyond a coincidence. Especially since the war games that were going on were using that radar site at that time”.Source: 84th RADES Data missing from North Truro, MAConclusionI agree with Kalles, it is too coincidental, and very convenient, that the 84th RADES went down at that critical time frame. So my questions are1. What radar data exactly was the flight path studies based on, if they were not in service at that time? 2. Was the 84th RADES data a work of fiction? 3. Was the primary radar returns seen on Air Traffic Control screens inserted simulation blips (the kind used in military training exercises)? 4. Can the 84th RADES data be trusted? After all, the DCC radar completely contradicts the 84th RADES radar data, with the DCC radar data categorically showing American 11 did not descend below 29,000 ft, and flew 2.79 miles past the North Tower, and was over New Jersey. Finally, I shall be doing a detailed article in the coming weeks, covering ALL the supportive evidence, showing neither American 11 or United 175 crashed at the two named targets on 9/11, and were still airborne at the times of the alleged crashes. For further reading and study covering all my research on the alleged 4 flights on 9/11, please follow the links below, covering all my articles on each of the flights. American 11 - https://911planesresearch.substack.com/t/american-11United 175 - https://911planesresearch.substack.com/t/united-175American 77 - https://911planesresearch.substack.com/t/american-77United 93 - https://911planesresearch.substack.com/t/united-93Thanks for reading and still caring!

🔐 Cryptographic Verification

�� CONTENT HASHES: SHA-256: cc0bc5aeb6286c032cab7ec21c5cb86063206300879611521d34075099ac9573 BLAKE2b: 6df00f8b276809c77e3b77990cf7ead9f8dc35c34c6db7c1c19754709a8e3834 MD5: 9e3dd261307a8f137e4e579c5c363b29 �� TITLE HASHES: SHA-256: 35a12a1fde7de29acce0ce9206d90217c6287873468de1c811dae8d0b0174936 BLAKE2b: c408d3f946d0a49ff16573f6041cf5667a8e18581dbe17315a9340c27022728b MD5: d7c676f60dc6eaf233bc2b65a5381208 �� INTEGRITY HASHES: SHA-256: ab7d8499d80939588978e99fe084260b3e513496b3311fac2ee9e8fc88ecb53f BLAKE2b: 17e8cc8eddf8794d354a9cde36a6db5bf5efcd5dc2d9e650fe2134c9b1af0eb0 MD5: c482a71e39d4d09b474ec55bbd59d40c