It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Some features of ATS will be disabled while you continue to use an ad-blocker.
Originally posted by UnderTow
I'm glad to see some are finally over the whole 'it's fake (as is not from NTSB)' thing. That really just boggled me.
I don't have all the answers yet but I do notice some assumptions still floating around about the animation, NTSB, and the data in general. Such as the continuous misunderstanding of the 173/180 numbers.
As far as anyone can say, the lowest point is about 480Ft MSL from the Altimeter, and 200 something from the Radio Altimeter. Remember both the Ft column and the end of the Animation are not adjusted for local pressure.
But even beyond the Heading/Map rotation problem, there are other problems. The End of Data, Time of Impact, and Altitude. A complicated subject in itself, but again the same problem. If the data ends, you tend to deduce an impact time. Obviously there can not be more valid data After impact. Now look at the altitudes. A conflict again.
What about the CSV Lat/Lon data screw up, it is off by 20 Minutes. An absolutely huge margin. Yet in ReadOut2 we got very good data for this.
There are several more strange oddities of conflict between all the data sets. Again I don't have all the answers yet, but am still working on it. Who knows, someday we may be able to produce our own animation. Just like the Pros at the NTSB.
I'll not be posting much here, so if you would like to discuss anything for your work drop me an email. It's easier for me.
CSV and animation altitude match