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.
altitude (of what kind?) is 238
And the first data frame:
This shows a GMT time of 0:26:49 - translated to EDT (minus 4 hours) this is 8:26:49 PM. Was this a night flight? (first frame of data in "normal" csv - 8:19:01 am)
And the altitude, which is relevant here, is 120 (Dulles elevation about 290-300 feet msl) and the infallible radio altimeter says 8186. Feet above the ground. It's not in the air. And not a temporary glitch. The numbers go up and down one foot either way for many, many frames, indicating still pre-takeoff (which happened around 8:20:30 in the old csv).
The line you have drawn has the aircraft changing almost 4 degrees of pitch in less than a second at over 460 knots. It does not match the pitch data that was recorded in the last second at 4 times per second.
Also, your final line shows almost level at the wall. You are being being deceitful and not representing the data accurately.
The pitch angles you offer and the line you have drawn do not match the data supplied by the NTSB. Ours does.
Originally posted by Caustic Logic
There's no way to directly reconcile the data with the "official" impact, but you could've tried harder.
Now the general altitude must be higher, which helps your too-high thing.
Russ hasn't got a clue? Wow. I'm not saying he''s 100% right or we agree on everything, but with all due respect, that's a pretty dumb statement.