AA77 FDR Data, Explained

[DavidJames]

Originally Posted by Anti-sophist

You can't really have it both ways.

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.

[beachnut]

Originally Posted by apathoid

You can download the tabular file here
http://www.hostfiles.org/download.php?id=EC33C56C

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]

Originally Posted by beachnut

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.

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.

[mcMike]

Originally Posted by beachnut

I do not think the FDR recorded position
quick review i did not find GPS or INS information

but I think the track pure FDR data only, relative position calculated just from FDR data, it may not line up exactly with the ground as seen on the Video,

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.

[apathoid]

Originally Posted by beachnut

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 simply opened the file in wordpad. Here is the first plot with the lat/long bolded:

Quote:

08:19:03,1.002,0.000,0.001,40,302.0,0.0,22.2,23.5, 0.0,-0.4,,,SET,NOT SET,,,,,NOT SET,SET,,,,,,,,NOT IN CTL,,,,,NORMAL,NORMAL,,WARN NOT,,NO DISC,ENGA NOT,TRUE,TRUE,FALSE,FALSE,,0.0,-0.1,GROUND,,,DOWN&LOCK,,ENGA NOT,,,ENGA NOT,,NORMAL,ON,,ENGA NOT,,,NORMAL,0.0,0.0,,,NORMAL,1.8,1.0,NORMAL,,NO TRIM DN,,,NO TRIM DN,,,NO TRIM UP,,,NO TRIM UP,,,,21.9,,AGREE,,,,,,,,,0.0,-2.5,INOPER,NO ALERT A,INOPER,0.0,,,,,0.0,,0.0,LOW,LOW,,,ON,ON,OK,,,,,, ,,,-1.0,-1.4,,,OK,OK,391.0,398.0,1.02,1.03,,,1.02,1.03,1152 .0,1152.0,NORMAL,NORMAL,33.5,34.1,53.4,52.9,51.0,5 9.0,35.2,37.1,65.5,64.0,ENG RUN,ENG RUN,NORMAL,NORMAL,0.09,0.26,FALSE,FALSE,1.58,1.58, 53.3,53.6,19.4,19.4,17.6,14.9,0.04,0.04,0.03,0.05, 0.08,0.25,,INOPER,,INOPER,18.1,,,,,,,,,,INOPER,,EN GA NOT,,,,CLOSED,CLOSED,,,DOWN&LOCK,,,DOWN&LOCK,GEN ON,GEN ON,,,,,,0.0,,NOT TRUE,1.0,,ENGA NOT,,,ENGA NOT,,2996.0,3128.0,3048.0,NORMAL,,,INOPER,,ENGA NOT,,,,INOPER,NOT SEL,0.0,TRUE,TRUE,OPEN,,ENGA NOT,,NOT EXT,PART EXT,NOT RETRACT,DOWN,,,,ENGA NOT,,,,,0.0,0.00,,ENGA NOT,,INOPER,,,,,MCL OFF,NO WARN,NO WARN,NOT PRES,,,,NOT OVRSP,ON,Automati,-0.4,,,,,N38°56',W077°48',TRUE,TRUE,NOT TRUE,NOT ENABLE,NOT ENABLE,NOT ENABLE,INOPER,INOPER,TCAS III,OK,0.5,-0.2,,10.0,,0.0,,,NOT TRUE,-0.6,18.8,FALSE,,P T/O ENGA,,,R T/O ENGA,,OPER,STWD/NOTSTWD,STWD/NOTSTWD,LOCK,NOT INTRNS,,TA only,,TRUE,NO INHIBIT,53.3,53.8,NO HOLD,INOPER,INOPER,19.2,1012.0,,-67.9,0.0,292.1,,,,ENGA NOT,,,ENGA NOT,,NOT KEYED,,,0.0,0.0,,,
,1.002,-0.002,0.001,,,,,,0.0,-0.4,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0.0,-0.1,GROUND,,,DOWN&LOCK,,,,,,,,,,,,,,,,,,,,,,,NO TRIM DN,,,NO TRIM DN,,,NO TRIM UP,,,NO TRIM UP,,,,,,,,,,,,,,,0.0,-2.5

[beachnut]

Originally Posted by apathoid

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.

[mcMike]

Originally Posted by apathoid

I simply opened the file in wordpad. Here is the first plot with the lat/long bolded:

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?)

[mcMike]

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 ?)

[beachnut]

Originally Posted by mcMike

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

[apathoid]

Originally Posted by mcMike

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 ?)

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...ad.php?t=65369

[apathoid]

Originally Posted by beachnut

radio alt

I am looking now

think excel is short on columns, not sure

Dont bother, its not there...unfortunately.

[beachnut]

Originally Posted by apathoid

I simply opened the file in wordpad. Here is the first plot with the lat/long bolded:

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

[apathoid]

Originally Posted by beachnut

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 ?

[beachnut]

Originally Posted by apathoid

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

[apathoid]

Originally Posted by beachnut

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 demand ignore answers"..

Believe it or not - thats Johnny D'ohs story and he's sticking to it...

[Anti-sophist]

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.

[beachnut]

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.

[mcMike]

Originally Posted by apathoid

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.

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]

Originally Posted by beachnut

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.

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.

[mcMike]

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.

[Anti-sophist]

Originally Posted by mcMike

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.

The actual impact time, relative to the CVS file is quite difficult to say with certainty. The CTers will have you believe that :45.000000 is the actual impact time. JDX might even admit that it could have impacted as late as :45.999999. He's still not completely correct. The :46 time stamp made it onto the recording media, so the actual window is somewhere between +0 and +2 seconds after the end of the :44 frame.

Notice how careful I am in determining what "time" the :44 frame is. CTers would like to assume that the :44 frame starts at :44.00000 and ends at :44.999999. The chances of that being true are virtually nothing.

[Anti-sophist]

Originally Posted by mcMike

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.

That's actually a really nice graphic. I'm starting to think that this "heading" and "lightpole" issue might need it's own permenant spot on one of the websites as a frequently asked issue.

But yes, this does show fairly conclusively that the NTSB animation had the plane orientated with respect to magnetic north, and the map orientated with respect to true north. Once that correction is made, the animation would be correct. Beware, though, because saying the NTSB is wrong is a slipperly slope into logical fallacy land.


Reproduced, below:

[apathoid]

Originally Posted by beachnut

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.

The position data would either come from the Flight Management System(via IRS), or more likely, the Inertial Reference System itself. The error would probably stem from the way the data was recovered or recorded, and not from the IRU position data itself. There is absolutely no way AA77 would've taken off with that kind of IRS "drift" - trust me

FYI - the 757 RADALT unflags at 2500 ft AGL. So, it should've appeared in the last 30 seconds or so, but it wasnt recorded properly...or couldnt be confirmed as correct(I forget what the NTSBs wording was - I just read that section of the AA77fdr.pdf from 911myths yesterday).

[beachnut]

the plane could be still hitting almost 6000 feet per minute and take out the light posts and hit the pentagon

look for angles of 4 to 6 degrees and you have 4000 to 6000 feet per minute

the heading is right with what happen, witnesses would help if you correlate them to their real positions

unless you really believe the parking lot video show enough for a flatter hit, not sure how you can take a 1 frame or half frame a second video low res far field video and make any decisions at all

if there are only 2 or 3 seconds left and the plane is really at 400 feet or so you would need 6000 feet per minute to fit, which is what the terrorist pilot was doing

The FDR is great for accidents, it shows you what was up, if this was an accident they would know it was not by the final approach and the throttles being pushed up, makes it on purpose

there is enough from the FDR and the video to back up what happen, unless you are a CT guy

then the little errors we live with everyday become some ct, if you are ct

The FDR gives us details now that debunk Charlie Sheen's super pilot theory, the terrorist did nothing a kid off the street could not do as good or better, the terrorist wasted money on training

the FDR debunks the 7 g expert ct guys, the plane barely did 1.7 g max

the final turn was rough, the descent from 7k to 2000 feet was an easy descent for any pilot

the FDR makes the ct world before the FDR look like idiots

So the NTSB used other data to place the plane on course, closer on course, bet they just moved the takeoff of the video over to the airport,

it would be great to have the exact position for the last second of FDR data, that would give us the time to hit, at 771 feet per second plus the final estimated speed at impact

then too you would have a better estimate on the vvi, rate of descent

[beachnut]

Originally Posted by apathoid

The position data would either come from the Flight Management System(via IRS), or more likely, the Inertial Reference System itself. The error would probably stem from the way the data was recovered or recorded, and not from the IRU position data itself. There is absolutely no way AA77 would've taken off with that kind of IRS "drift" - trust me

FYI - the 757 RADALT unflags at 2500 ft AGL. So, it should've appeared in the last 30 seconds or so, but it wasnt recorded properly...or couldnt be confirmed as correct(I forget what the NTSBs wording was - I just read that section of the AA77fdr.pdf from 911myths yesterday).

you mean like KAL707 putting in wrong points or leaving them out'

actually you could safely fly the plane with out the fancy INS, or IRS. you could do it like you do in a C-172,

you do not need all that modern junk, the vor/dme still work and are good enough for flying, gee the road is 8 miles wide

so if it is something the pilots set and they decide to fly the airways using NAV aids and not the nav system of the plane they may have skipped updating the system and just flew the darn plane, you can do it

You would have to fake it if center gave you INS direct, but then pilots can do that also

I would takeoff, who need the fancy junk, just get me close to the airport for takeoff and landing.

lets go fly

[Anti-sophist]

Originally Posted by beachnut

the plane could be still hitting almost 6000 feet per minute and take out the light posts and hit the pentagon

look for angles of 4 to 6 degrees and you have 4000 to 6000 feet per minute

I'm not so sure about that. My calculations put the farthest hit pole about 1200 feet out. That's about 1.5 seconds by my calculations. If you assume a constant 4000 fpm dive, over 1.5 seconds, that's a descent of about 100 feet. Not sure if the top of the farther lightpole is 100 feet (or higher) compared with the final impact point.

However, the moment you don't assume linear trajectory, this entire argument falls apart. Also the fact that the 4000 fpm dive, by most CTers, is totally assigned to the wrong time. That 4000 fpm dive measurement is quite a bit older then they want you to believe. It's probably 3-4 seconds before the time of impact.

[apathoid]

Originally Posted by beachnut

you mean like KAL707 putting in wrong points or leaving them out'

actually you could safely fly the plane with out the fancy INS, or IRS. you could do it like you do in a C-172,

you do not need all that modern junk, the vor/dme still work and are good enough for flying, gee the road is 8 miles wide

so if it is something the pilots set and they decide to fly the airways using NAV aids and not the nav system of the plane they may have skipped updating the system and just flew the darn plane, you can do it

You would have to fake it if center gave you INS direct, but then pilots can do that also

I would takeoff, who need the fancy junk, just get me close to the airport for takeoff and landing.

lets go fly

Well, they could've flown without IRS, but not legally...It would be like an older generation airliner flying without its Vertical/Directional Gyros. Major no-go.
Of course, there are 3 IRUs so the odds of all of them failing are 'powerball lottery' odds.

[beachnut]

Originally Posted by Anti-sophist

I'm not so sure about that. My calculations put the farthest hit pole about 1200 feet out. That's about 1.5 seconds by my calculations. If you assume a constant 4000 fpm dive, over 1.5 seconds, that's a descent of about 100 feet. Not sure if the top of the farther lightpole is 100 feet (or higher) compared with the final impact point.

However, the moment you don't assume linear trajectory, this entire argument falls apart. Also the fact that the 4000 fpm dive, by most CTers, is totally assigned to the wrong time. That 4000 fpm dive measurement is quite a bit older then they want you to believe. It's probably 3-4 seconds before the time of impact.

was looking at the final g readings and trends, I think he could have picked up to 6 or 7000 fpm or better then pulled back to 4000 fpm, he was pushing on the stick again

I think he picked up 6000 or more fpm then pulled out to make the hit

if he had to hit the pole, he had to get down quick at 100 plus fps, unless the plane is lower

need to find a real good altimeter setting for the pentagon at the impact time

wonder how an over speed affect the pitot static system and if Boeing modeled the errors for 463 KIAS,

Does the 757 have accurate altimeter readings at 463 KIAS?

There may not be proper error models in the air data computer for that speed near sea level!

But the darn things are usually so close in normal operations

darn study time, need best info on air data computer for over speed vs altimeter, plus other things

[beachnut]

Originally Posted by apathoid

Well, they could've flown without IRS, but not legally...It would be like an older generation airliner flying without its Vertical/Directional Gyros. Major no-go.
Of course, there are 3 IRUs so the odds of all of them failing are 'powerball lottery' odds.

I call them INS, have not flown a 757

but the pilot, a navy guy ?, navy guys do not use anything, just blue sky and speed,

me not need IRS, me fly by seat of pants

serious, unless you know the plane was devoid of vor and dme, then the pilot could ingnore the offset on the IRS/INS or GPS

you put in the nav aid frequency, dial in the course and fly, I did it, you can do it\

is it against company policy or rules, who knows?

I did not say fly with out the ADI gyros, yes you have to have an ADI gyro unless you know the weather is clear, then you can use gods adi, the earth,

a little tongue in cheek but you can fly very well with the radio nav aids, they still work, and all the procedures to get in and out of airports are based on the radio nav aids, and I was flying in 2001, flew on 9/12 and 9/13 to pick up my fellow worker in OR, and get him back to CA since he was stuck when flying commercial was down for days.

The cops followed me when I got gas at Lincoln, who are u? they asked, guess everyone was real jumpy the next day, or two,

anyway, just junk on flying, but I would not be surprised if they did ignore the IRS,

but then I am an old pilot, but if 77 pilot was navy, he may not of even bothered with the IRS junk, it is extra work anyway, in a way

just my one cent worth, want to go fly?

[apathoid]

Originally Posted by beachnut

I call them INS, have not flown a 757

but the pilot, a navy guy ?, navy guys do not use anything, just blue sky and speed,

me not need IRS, me fly by seat of pants

serious, unless you know the plane was devoid of vor and dme, then the pilot could ingnore the offset on the IRS/INS or GPS

you put in the nav aid frequency, dial in the course and fly, I did it, you can do it\

is it against company policy or rules, who knows?

I did not say fly with out the ADI gyros, yes you have to have an ADI gyro unless you know the weather is clear, then you can use gods adi, the earth,

a little tongue in cheek but you can fly very well with the radio nav aids, they still work, and all the procedures to get in and out of airports are based on the radio nav aids, and I was flying in 2001, flew on 9/12 and 9/13 to pick up my fellow worker in OR, and get him back to CA since he was stuck when flying commercial was down for days.

The cops followed me when I got gas at Lincoln, who are u? they asked, guess everyone was real jumpy the next day, or two,

anyway, just junk on flying, but I would not be surprised if they did ignore the IRS,

but then I am an old pilot, but if 77 pilot was navy, he may not of even bothered with the IRS junk, it is extra work anyway, in a way

just my one cent worth, want to go fly?

"Chic" Burlingame was a Navy guy

There is an alternate mode of IRS operation called "ATT", or Attitude Only, which removes all heading/ position info from the displays and leaves the EADI operable.. I imagine this would be one of the things the FDR would look for. You can probably dispatch a 757 with 2 of 3 IRUs operable, but the inoperable units circuit breaker would be pulled and collared prior to flight, so its invalid data would never have made it to the DFDAU..

[beachnut]

I wonder where they got or calculated that position stuff

[beachnut]

but it would not be legal to fly IFR without the right amount of gyros required per regulations, (not current on them)

I flew some instuments in the weather in a small plane and finally figured out the instrument are junk and that perked up my crosscheck, all of a sudden the ancient instruments became very important, as a cross check of who (instrument) is right and making sure they stay that way

needle, ball, and airspeed

not that you would do it, but if you can ignore the funciton of navigation and live with some offset and still have good gyros it would be safe to fly

you have to know your systems (limitation etc), but I have no idea if all the crap I said would hold up as being relavent in a 757 system better find some facts first before I bore u to death,

I know some current airline guys, but it has been years, I could check, but the time could be weeks for hooking back up

[beachnut]

Originally Posted by Anti-sophist

However, the moment you don't assume linear trajectory, this entire argument falls apart. Also the fact that the 4000 fpm dive, by most CTers, is totally assigned to the wrong time. That 4000 fpm dive measurement is quite a bit older then they want you to believe. It's probably 3-4 seconds before the time of impact.

need 5 or 6 seconds, think you can firm up the frames being stored 4 seconds after happening?

if you move the data into the past 3 or 4 seconds, you are saying the process of getting the data into the survivable part of the FDR, ie the FDR, takes 3 to 4 seconds, which could be possible,

the data is compressed and processed, but why not fast?

if that is true and the plane is at 460 msl at the last FDR entry, then the pilot is trending towards 6000 fpm,

n+1 360 msl 6000 fpm 6 degrees down
n+2 260 msl
n+3 160 msl
n+4 60 msl

I have no problem with 4000 fpm and I think that could have the aircraft hit the lights, 4 degrees would be close with variation, or a lucky pullout if we have more time

need over 4 seconds unless you let him panic dive for a second and recover in a second and then hit at 4 degrees

if the data is stored 3 to 4 seconds late, then you have 5 to 6 seconds and NTSB video path needs to back off the correct distance, not so sure the map is sync in any way

okay, how do you find out how old the stored frame is compared to the end of data etc

(i just remembered how the different clocks at the pentagon had CTers jumping all on time)

I was in the air force, our office clock was set to justify, or rationalize, leaving early or arriving late, end of story!

our watches were on by a second since 1978! unless you had an air force issue wind up, we did save you guys the bucks!

CT guys are funny

– need to verify data age and storage, if it is 3 to 4 seconds old, and the final time stamp is impact time or earlier, you have it

plus the position error, and ground sync error

do I have to read all of your stuff to see if you already said it is 3 or 4 seconds (firm), I know you talked about those things but with UT, not so sure if he was on the same page or just like me, looked it up and getting hung up on details and not making correct judgments when required to compare what you said with what he is learning or what he knows

would be cool if he said which he has, recent learning, or he knows the stuff all along!

I am a pilot, and I have instructed in the AF, but I have to look it up and get back to you, if I was in the nuts and bolts of the FDR.

Need to hire Boeing

[mcMike]

Did I understood this correctly? Nobody knows (not even NTSB) when the last frame was recorded prior to impact? They just adjusted the timescale in FDR-data to match T-1 or T-0 before impact?

If this is true then there can be even 5 seconds missing from FDR and we nor JDX can't say or analyse anything for the last altitudes, accelerations etc. So the whole FDR-thingy is pointless for any argument?

[beachnut]

unless you believe flight 77 is still airborne, the last atltiude could be 460 feet msl and the pentagon is at 38 I think, have to check

there are two time stamps empty on the FDR

9:37:440.6630.1320.0311730.6180.1410.0110.6270.137-0.1760.6860.134-0.0220.7570.6130.7160.6189:37:459:37:46

the 173 is final altitude based on 2992, the local was 30.20 or so you have to add 300 feet or so

[beachnut]

that came out bad


9:37:44 this had data but the next two time stamps had nothing

9:37:45
9:37:46

[apathoid]

Originally Posted by beachnut

not that you would do it, but if you can ignore the funciton of navigation and live with some offset and still have good gyros it would be safe to fly

you have to know your systems (limitation etc), but I have no idea if all the crap I said would hold up as being relavent in a 757 system better find some facts first before I bore u to death,

I know some current airline guys, but it has been years, I could check, but the time could be weeks for hooking back up

I'm not a B757 pilot, but I'm probably the closest thing to a 757/767 expert here

This is from the 757 MEL. You do need 2 of 3 IRUs operable to dispatch. Also, the inop unit must be deactivated(breaker pulled, collared and placarded). I'm leaning toward the position error being introduced sometime after the data was sampled, possibly after the data was recovered.

Originally Posted by beachnut

okay, how do you find out how old the stored frame is compared to the end of data etc

That is a great question and if I read A-S correctly, its really difficult to say from what we have(the CSV). I just want to know in what friggin box the time stamp takes place in. Ive read(through) 400 pages of FDR/FDAU manuals and cant find a single mention of it.

[apathoid]

Originally Posted by beachnut

that came out bad


9:37:44 this had data but the next two time stamps had nothing

9:37:45
9:37:46

Wow, I never noticed that. There goes the whole argument down the drain. Ballgame!

[mcMike]

Originally Posted by beachnut

that came out bad
9:37:44 this had data but the next two time stamps had nothing
9:37:45
9:37:46

Indeed. That proves that the last frame is at least impact-3 seconds.

[beachnut]

not to lay down too much BS

I was trying to say the position could be off by what we see, yet the gyros are good

My navigator load the our INS with 17 south instead of 7 south, we were, 600 miles off, he got pissed and dumped it

he could of left it running and used it as a rough offset to back up his cel nav,,,,,,,,,

so if it is possible to have the nav system align offset and stay, and the pilots either entered the beginning start point 20 miles in error, but they are not using the internal navigation but the vor radio nav aids which they have to use anyway, why waste time on your computer nav

this would account for the 20 mile offset

I know the nav system can be set up at the wrong initial point, my crew did it, now is that possible with this system?

I understand what you have on the go no go, and you are correct but it does no preclude setting up the wrong inial point in the nav computer, the gyros do not care, that much

our INS need 20 minutes running in one spot to work best, and yes, when you set it up 600 miles wrong, there are some problems and error modeling in the software i imagine will not work very well but the ins gyros are still good for attitude.

I think it is possible to align 20 miles off, not sure if it would hold, but that would account for our offset in the FDR, and it was relative in error if you move the takeoff point back to the real airport, placing the takeoff at the correct airport and the end point over the pentagon

and I think it bears more time to investigate, and I do agree with your chart, it is the chart and I do not believe it precludes the pilots setting or accepting a 20 mile offset error in the nav system

does this make sense