Happy 2010 everyone!
I'm cross-posting this from the ATS forum. It's relevant to the recent discussion here...
I'll revisit the altimeter lag argument shortly, if anything just to tie up the loose ends from this discussion. I believe lag played a large part in the error of the pressure altitude in the final moments, but showing "proof positive" that lag caused the error is unnecessary. Here's why...
A short dialog with Warren Stutt, in reference to PfT's pressure altitude argument, got me thinking along some different lines. I suppose I knew all along that the 757's Air Data Computing/Pitot-Static System wasn't designed for such a flight profile as AA77s final "attack run", but I didn't think I could demonstrate such without information not currently at my disposal. A question from Warren about a parameter - Total Pressure(which I'll refer to as Pt)- got me digging in the manual about pressure limits. Long story short, I found a few things that should bury the
"pressure altitude reads too high" issue for any rational mind.
I'll show the following:
- AA77 was travelling at 488 knots True Air Speed(TAS) at the end of data, some
141 knots above the 757's max operating speed(VMO). This obviously means that AA77 was operating well beyond the 757 flight envelope; meaning that the Air Data system was never tested, calibrated, or certified for such extreme conditions.
- The Total Pressure(Pt) at the end of data exceeded 42 in/Hg, resulting in a differential pressure of over 12 in/Hg between Total Pressure(Pt) and Static Pressure(Ps) This is important because, as I'll show, the 757 Maintenance Manual states that differential pressures over 10 in/Hg can cause damage to the Pitot-Static System. Enough said.
- The Air Data Computer is never tested for anything approaching the pressures that AA77 experienced approaching impact. As I'll show, pitot and static(speed and altitude) pressures are tested in pairs(this is because the Air Data Computer is calibrated to condition raw static/altitude data with different airspeeds, angle of attack, and air temperatures) which check only low speed/low altitude and progress in a linear fashion to high speed/ high altitude. High speed/low altitude profiles are not tested, and we can assume that the ADC is not calibrated to be accurate in such a regime, especially given how far beyond the flight envelope AA77 was.
- Finally, and probably most importantly: The 'Air Data Accuracy Test' allowable errors pertain to test conditions only, and don't include error from
"..the aerodynamic effects of flight". Rob Balsamo will try to have you believe that the error pertains to flight conditions. I'll
show that it doesn't.
757 Flight Envelope/VMO
Reference:
757 Air Data Accuracy Test
The far right hand column is the computed VMO(or Velocity, Maximum Operating) based on input pressures which simulate a range of airspeeds and altitudes. You'll notice that from 0' up to 18,000', the 757's VMO is 347 knots. The speed at the end if data is 488 knots, some 141 knots over VMO. That's not barely past the envelope; its into uncharted territory. No 757 has flown that far beyond VMO and lived to tell the story.
Why is any of that trivial information important? Because Air Data Computing Systems are only designed, tested, and calibrated for conditions within the airplanes performance envelope and perhaps even
slightly beyond.
Differential Pressure Beyond Damage Threshold.
Reference:
757 Air Data Accuracy Test(from Boeing's Maintenance Manual.)
FDR Decode - Airspeed and Total Pressure(Pt) Fields at End Of Data
Total Pressure Conversion
Note the large bolded text at the beginning of the procedure which states:
"MAKE SURE THE DIFFERENCE BETWEEN TOTAL PRESSURE AND STATIC PRESSURE DOES NOT EXCEED 10 IN/HG....THIS WILL PREVENT DAMAGE TO THE PITOT-STATIC SYSTEM"
What that means is you cannot supply too high of an airspeed for a given altitude, or damage can occur. I've actually damaged and Air Data Computer once by not heeding a similar warning. The system is designed for only a certain range of pressures and up to a delta of 10 in/Hg between altitude and airspeed. This was grossly exceeded in the final moments of AA77's existence, as you will see.
Note the FDR Decode link above shows that Total Pressure(Pt) as 1442 mB's at the end of data. The Static Pressure(Ps) parameter is unavailable; however its not needed as we know that a pressure altitude of -99' MSL, AA77's altitude at end of data,
is equivalent to 30.030 in/Hg. Since we have a mix of units, and we are looking for both units to be in in/Hg - we have to convert the 1442mB. Note the Total Pressure Conversion above and we'll see that 1442 mB is equal to 42.58 in/Hg. So we have:
a Total Pressure of: 42.58 in/Hg
a Static Pressure of: 30.03 in/Hg
..giving us a difference in pressure of 12.55 in/Hg. What did that note say again?
"MAKE SURE THE DIFFERENCE BETWEEN TOTAL PRESSURE AND STATIC PRESSURE DOES NOT EXCEED 10 IN/HG....THIS WILL PREVENT DAMAGE TO THE PITOT-STATIC SYSTEM"
There ya go, moving on...
Air Data Computer Test Range
Reference:
757 Air Data Accuracy Test
Note the Maintenance Manual figure above. With a given set of test pressures(at left), you'll see the output altitudes and speeds with an accuracy figure and "delta" figure. The thing that's important here is the range that is being checked, note that the only airspeed checked with 0' altitude is 150 kts. The full range goes like this:
0' 150 kts
10,000' 200 kts
20,000' 300 kts
30,000' Mach 0.75
35,000' Mach 0.80
40,000' Mach 0.85
This is the calibration range that is tested for accuracy. Note that there is no 0' 490 kts test point, or anything remotely close to it. As I mentioned, the Air Data Computer is calibrated over the normal flight envelope, and this test shows that there are no tests for any speed/altitude combination outside that flight envelope. Actually, it even shows that only a relatively small range within the flight envelope is checked for accuracy - that being only the typical airspeeds for the given altitude.
The other thing to notice, again, is the difference between Total and Static Pressures(these are at left). You can see that over the test range, the maximum difference is about 4.8 in/Hg. Recall what AA77 was experiencing in the final moments; 12.55 with 10.0 being the damage threshold.
Air Data Computer Accuracy
Reference:
757 Air Data Accuracy Test
I'll keep this point short. Just note the highlighted portion at the bottom..
"..the aerodynamics of flight do not contribute to the tolerance allowance"
So, at 0' and 150 kts, a tolerance under test conditions of +/- 25' and +/- 2.0 kts is allowed. That is, to re-iterate, under perfect test conditions - not subect to aerodynamic disturbances. Rob will have you believe that the tolerance is for flight conditions, it's not. This renders any argument to the effect of
"the accuracy for an altimeter at 0' MSL is +/-25', so AA77 is still (x)' too high." ...completely void, especially given how far beyond the flight envelope AA77 was.
I hope some of you found this to be enlightening. Most aviation experts here already kinda know most of this, but I thought showing it would be a good idea since these claims keep persisting. If anyone has any specific problems or corrections to the above, I'll gladly discuss them.
The meta-argument of whether or not the altimeter was slightly lagging behind is sort of moot, but I'll dig up some stuff on the ADC's Pt and Ps transducers for you, Tino. I've looked quickly through the 'Functional Test'(bench test) for those sensors and there isn't a test for lag, just accuracy tests, leak rate tests, and latency tests for the output ARINC data words. IIRC, these were something like 250,000-1,000,000 nanoseconds. But that's obviously not related to the lag I was talking about.