Originally posted by weedwhacker
No, that is completely incorrect. There is simply no way for an FDR to interface in the same way with a full-motion airliner simulator in the way you
Hey WW, let me clarify this part of my post. I don't mean the FDR as a
physical device; I meant the flight data file may have been created using
a flight sim.
First I've heard of this issue with AA 77.
I may be confusing you. The time/date I'm referring to is the file creation
date of the .fdr file. The FOIA CD-ROM contains the information when
looking at the file details.
This file is created before the report of recovering the FDR in the Pentagon.
Very strange. Even more strange is this contradicts those who state there
was no need to investigate the crash because it was a 'suicide bomber'.
So...why the quick act to download the data?
More important, why does the file date lead the discovery date of the FDR in the building?
Just a few things here that really bother me (and others).
I think I've told you before. It depends greatly on the actual rate of descent at the time, and how fast the Baro set knob is turned. Go
flying to see for yourself.
I agree, however the knob was turned and set approximately 18 minutes
before impact, yet there was no reflection of this calibration in the Pressure
Altimeter gauge (animation).
The common argument to this point is that the animation is a "working copy". If that's the case, then why was the ascending BARO correction
included, and not the descending?
The correction must be applied to the entire data set, not just a few
seconds worth. In other words, if you were to assign (approx. non-linear)
the following values to the BARO parameter, the Pressure Altitude in the
animation would have been more accurate:
Sea level to 5,000 ft_____1.006 in/Hg___994
___5,000 to 10,000______0.862_______1,160
___10,000 to 15,000_____0.740_______1,350
My question is, why did "they" run the animation with only part of the
values corrected? It would take a simple equation to fix this in the CSV
file, and I'm fairly certain the super expensive software can accomplish
this with a few minor inputs.
"white smoke" (if it actually existed) could simply have been a severed fuel or hydraulic line.
Quite possible...however I would have expected a fire. Maybe, maybe not.
I would have also expected the FDR data to support the level flying object
in the DoD video.
Futhermore, I'm not convinced the PA values were severly affected by
overspeed when looking at the rate of change in RAD ALT. If we use
the DME values and a known ground elevation (the highway, or terrain
around the gas station) we can compare the altitudes to find a trend
within 1-2 seconds of 'impact' using the NTSB supplied data, and the
extended decode by Mr. Stutt.
The aircraft was well over Vmo before the Annex and within range of
RAD ALT to trend against Pressure Altitude.
Using DME and RAD ALT alone along the damage path makes it difficult
to support the pole strike theory as-is.