DavidJames
Penultimate Amazing
He's a CTist, all evidence supports his CT, if not, it's either ignored or reinterpreted so that it does.
I suspect he's also an unemployed sock pilot, or at the very least lives in the same drawer.
AA77 FDR Data, Explained
- Thread starter Anti-sophist
- Start date
-
- Tags
- aa77 flight data recorder
I suspect he's also an unemployed sock pilot, or at the very least lives in the same drawer.
did you find lat and long or position information it the tab file?
I had the same file already, could not find lat and long, what column is it in
I already have it in excel, but one column did you find location in?
I think you can just feed a few variables, heading, speed, roll, yaw, etc into a program and get the video, you do not need position you calculate it as you go
I thought they just correlated the start point and let it go.
Anti-sophist
Graduate Poster
- Joined
- Sep 15, 2006
- Messages
- 1,542
My guess is there would have to be more information then that. The high frequency information in those variables is lost, and by the end it would be way off. You'd need some kind of outside verification of location, over time, to keep the errors under control.
Well, this was my initial thoughts also. Like I said I couldn't locate any gps-coords in CVS-file either and assumed the path is build from start with speed, accel, heading, etc. This will make absolute-positional errors bigger towards end of the path. Short term inspection of relative-path is accurate but not absolute.
I simply opened the file in wordpad. Here is the first plot with the lat/long bolded:
good job, it must be truncated in excel, need a longer excel sheet.
It appears to get lost when imported directly to Excel. That's the reason I couldn't locate it either. (hmm. that was the thing excel reported during importing. Maybe there are too many columns for import?)
Could someone explain more precisly JDX's latest claim about the altitude? What is the reference-alt on Pentagon? To what direcetion we need to compensate Pressure-ALT to make it relative to Pentagon? What is the estimated end of recording? (T-2 or T-3 ?)
pa, you need the altimeter setting at the Pentagon, but the correct could be 300 feet, it was in the morning when it took off from Dullas? sp
but is there a radio altimeter, that shows distance from the wheels to the ground you can count down the feet for the pilot as you land, 10, 5 , touchdown, just to help out
radio alt
I am looking now
think excel is short on columns, not sure
D'oh claims that rate of descent(66 ft/sec) in the last couple of seconds would put the plane over the poles working backwards form the Pentagon with the known terrain elevation, pole height, and elevation of the Pentagon itself. Very nice, but that argument assumes that the last plot on the CSV represents the exact impact time, which is not the case.
Radar data shows that AA77 impacted at approximately 09:37:45, while the last plot is for :44. That is at least one second, or 780 ft of AA77s travel.
ETA: Check this post by Anti-S which covers D'ohs arguments.
http://www.internationalskeptics.com/forums/showthread.php?t=65369
Last edited:
Dont bother, its not there...unfortunately.
the lat and long i plotted are miles away from the pentagon, anyone else find the data useful?
I am going to plot that first point next, and if it is not near the airport this lat long is not very good,
but still looking
Yup, its 20 miles off from start to finish....conspiracy ?
but you know if you take the first point and last point, plot, then line up the first point on Dullas, the second point in very close to the pentagon
or are the coordinates for DC off to put the cruise missilse in to my house at Star Flower Dr! darn
I am moving! or did i do that back wards
yep the plane missed by 20 miles, the terrorist missed his plane and the pentagon
Obviously the data is totally faked and the gumberment NTSB employee felt guilty about participating in the conspiracy, so he put in certain easter eggs(like the plane being 500 ft too high at impact, or position being off by miles) for CTers to find so that they can "ask questions and
Believe it or not - thats Johnny D'ohs story and he's sticking to it...
Anti-sophist
Graduate Poster
- Joined
- Sep 15, 2006
- Messages
- 1,542
I don't know of reasonable explaination for why the position is shifted by 20 minutes. I am reasonably positive, though, that it wasn't the recorder, and must have either been an error in the instrument or an error in the extraction. If anyone finds a reasonable explaination, or even has a good hypothesis, I'm all ears.
the data was so far to the right in the data field it is adjusting itself (who said the ct world had fantasy better than I)
What is the source for the lat and long?
anyone find a radio altimeter setting, it would only be on low to the ground, 1000 feet or so, not sure if it like the KC-135 but Radio ALT would show relative height above the ground.
What is the source for the lat and long?
anyone find a radio altimeter setting, it would only be on low to the ground, 1000 feet or so, not sure if it like the KC-135 but Radio ALT would show relative height above the ground.
So we assume that FDR ends to T-1 ? I tought it was more since I saw some references to T-2 or even T-3. Could remember wrong though.
Anti-sophist
Graduate Poster
- Joined
- Sep 15, 2006
- Messages
- 1,542
The RADALT data was not published in the FOIA request.
http://www.ntsb.gov/info/foia_fri.htm
The report on AA77's FDR has the list of parameters included, and those that are not included. You will find RADALT in the list not included.
15 posts finally. Now the link and point I was trying to make.
This:
http://img223.imageshack.us/img223/841/headingwr1.jpg
Since we can clearly see from FDR the heading is stable for last 10 seconds. It's kinda safe to assume that the plane was heading in direction of RED path or otherwise it would've missed the Pentagon alltogether.
I am trying to point out that the NTSB-animation and "wrong-path" can be debunked with heading alone. The absolute-positional information is apparently wrong and there are multiple reasons for this. But the heading should be quite accurate (in those speeds the wind doesn't matter a lot so the bearing and heading is about the same).
Any claims for "eyewitness"-path would require the plane to fly in 20-degree yaw which is quite impossible in that speed.
This:
http://img223.imageshack.us/img223/841/headingwr1.jpg
Since we can clearly see from FDR the heading is stable for last 10 seconds. It's kinda safe to assume that the plane was heading in direction of RED path or otherwise it would've missed the Pentagon alltogether.
I am trying to point out that the NTSB-animation and "wrong-path" can be debunked with heading alone. The absolute-positional information is apparently wrong and there are multiple reasons for this. But the heading should be quite accurate (in those speeds the wind doesn't matter a lot so the bearing and heading is about the same).
Any claims for "eyewitness"-path would require the plane to fly in 20-degree yaw which is quite impossible in that speed.