It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
originally posted by: cardinalfan0596
a reply to: Jacobu12
He is misrepresenting facts and his big "point" about north of/south of actually means zilch.
originally posted by: cardinalfan0596
a reply to: bloodymarvelous
OR, they started moving before the INS was fully aligned.
Pilots for 911 Truth, was run off of ATS long ago because there are too many aviation professionals on here that called them on their BS....ESPECIALLY on their attempts to portray the FDR data the way they do.
originally posted by: cardinalfan0596
a reply to: GBP/JPY
The gear was not down. Why would you think it would make marks on the concrete?
This is based on the pressure reader showing 29.92 inHg.
originally posted by: samkent
a reply to: bloodymarvelous
This is based on the pressure reader showing 29.92 inHg.
Are you aware that upon reaching 18,000 feet ALL aircraft altimeters are set to 29.92 ?
Only when descending below 18K are they reset to local conditions.
Do you think HH bothered to ask for current barometer settings on a VFR day???
Please look beyond conspiracy sites for data before shouting conspiracy.
This altitude has been determined to reflect Pressure altitude as set by 29.92 inHg on the Altimeter. The actual local pressure for DCA at impact time was 30.22 inHg. The error for this discrepancy is 300 feet. Meaning, the actual aircraft altitude was 300 feet higher than indicated at that moment in time. Which means aircraft altitude was 480 feet above sea level (MSL, 75 foot margin for error according to Federal Aviation Regulations). You can clearly see the highway in the below screenshot directly under the aircraft. The elevation for that highway is ~40 feet above sea level according to the US Geological Survey. The light poles would have had to been 440 feet tall (+/- 75 feet) for this aircraft to bring them down. Which you can clearly see in the below picture, the aircraft is too high, even for the official released video of the 5 frames where you see something cross the Pentagon Lawn at level attitude. The 5 frames of video captured by the parking gate cam is in direct conflict with the Aircraft Flight Data Recorder information released by the NTSB. More information will be forthcoming as we come to our conclusions on each issue. We have contacted the NTSB regarding the conflict between the official story and the FDR. They refuse to comment. For further details, please see our Technical Paper here and Press Release here outlining our findings.
originally posted by: samkent
a reply to: Jacobu12
When it hit the wall you should able to see a blur or outline of the plane.
Are you basing this belief on cartoons you have watched ?
originally posted by: cardinalfan0596
a reply to: bloodymarvelous
No, Flight 77's pilots reset the altimeter on their climb out from Dulles. Hani, didn't bother to reset it on his descent.
Position report errors
The data file shows that the course position error at take-off from Dulles is much greater than the error at the end of the final flight. The large error at the beginning may have resulted from drift of the inertial navigation system while the plane was on the ground. These errors are apparently largely corrected during flight, presumably by reference to Distance Measuring Equipment (DME) and VHF Omnidirectional Radio Range (VOR), which provide distance and direction from ground stations. Also available at the time was the Global Positioning System (GPS). Significant position errors were nevertheless noticed in the data from most of the normal landings described above, and corrections were made. It was noticed that the errors became larger while the plane was taxiing toward its parking spot, at which time it would presumably be too low to receive DME and VOR correcting signals. It may seem surprising that GPS was not correcting drift, but the NTSB has released a document which lists GPS as “not working or unconfirmed”.28
The errors in the data file position reports were corrected by creating a file consisting of every fifth position report and applying the positions to Google Earth maps. In the case of the 11 landings prior to flight 77, each plot was inspected to identify the position where the plane turned off the runway onto a taxiway. The differences in latitude and longitude between the plotted position where the plane turned and the junction with the taxiway were used to adjust the data file values. Only landings in which the turn off position could be clearly established were used in this work. The average latitude error was 329 feet and the maximum error was 1197 feet. The average longitude error was 663 feet, maximum error 1410 feet. It is clear from this study that the position reports produced by this aircraft were prone to error, producing recorded tracks which were parallel with, but offset from, their real tracks. It is therefore not surprising that this was also found to be the case with the final flight.
Summary and Conclusion
In response to FOIA requests the NTSB provided a CSV file and a coded FDR file. All contradictions between the official account of the course of flight AA 77 and these files appear to be traceable to missing data. In the case of the CSV file the data stopped about four seconds short of the impact. In the case of the FDR file the final frame was not initially decoded. Some researchers recognized that data was missing, while others claimed that the files proved the official account was false, as it appeared the flight terminated at a point too high to have created the observed damage trail on the ground.
Previous analyses were further confounded by uncertainty of the position of the last data point; failure to consider possible calibration errors in the pressure altimeter data, caused by high speed and low altitude; and false information in the NTSB flight animation.
The recent complete decoding of the FDR file has enlarged and clarified the information available and has thereby enabled resolution of the contradictions. It is clear that this file supports the official account of the course of flight AA 77 and the consequent impact with the Pentagon. The file thus also supports the majority of eyewitness reports.
originally posted by: Jacobu12
originally posted by: samkent
a reply to: Jacobu12
When it hit the wall you should able to see a blur or outline of the plane.
Are you basing this belief on cartoons you have watched ?
It's a commercial airliner with a long wing span. The wing span it's not going to be pushed inwards on approach, the wing should be closer or visually easier to see and closein more to the camera. The video was tampered with.
originally posted by: GBP/JPY
@Jacobu12..... Yes, and no landing gear marks on the concrete floor going in.....
Stuff like that, turbines ,too.......no marks.....men
originally posted by: cardinalfan0596
a reply to: bloodymarvelous
No, Flight 77's pilots reset the altimeter on their climb out from Dulles. Hani, didn't bother to reset it on his descent.
originally posted by: neutronflux
a reply to: neutronflux
So you go from you cannot tell it's a jet to you can pick detailed wing positions from a blurred photo captured with a wide angle lens.
Zero credibility..... zero consistency....
No, neutron baby......not a vinyl covered floor....
originally posted by: neutronflux
originally posted by: GBP/JPY
@Jacobu12..... Yes, and no landing gear marks on the concrete floor going in.....
Stuff like that, turbines ,too.......no marks.....men
You do understand that buildings usually don't have bare concrete floors. Somebody played this game in a another thread asking if there was damage to the concrete from posted pictures of the pentagon.
Again, the concrete would have been covered by some sort of flooring.
Who knows how many layers of flooring ended up covering the concrete over the years.
When you zoomed in on the pictures, you could see were the concrete had chunks missing.
Epic fail playing "but it's not in this picture I posted with no dates nor context". Another game conspiracists like to play.