37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 939052 |
Time | |
Date | 201103 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Component | |
Aircraft Component | Airspeed Indicator |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer |
Experience | Flight Crew Last 90 Days 76 Flight Crew Total 13000 Flight Crew Type 1879 |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Multiengine Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 8500 Flight Crew Type 3000 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Speed All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
Cruising at FL320 in the clouds with constant light chop/turbulence with a tat around -24C; we suddenly had the #2 autopilot disconnect and the aircraft rapidly pitched over toward 7 1/2 degrees nose down and autothrottles were rapidly advancing forward. I took the control wheel and made sure the autopilot and autothrottles were disconnected; no trim wheel movement was noticed though it was trimmed fairly nose down. We thought we had encountered clear air turbulence/mountain wave from the thunderstorms in the area that we were diverting around. First officer immediately notified ATC that we had lost altitude from mountain wave activity. I was slowly pulling the nose up (the nose was extremely heavy) and reducing power when I saw that my airspeed was rapidly bleeding off and going through the hook/stall; to 80 KIAS. This wasn't adding up in my mind as I saw that we had lost 1;000 ft of altitude and we were in a nose low attitude then the mach over-speed warning sounded. Checking the standby attitude indicator also showed nose low and I quickly looked over at the first officer flight instruments and they showed the nose low but airspeed in the zipper around 320-330 KIAS. I told the first officer that his instruments were correct and that he had the airplane and that it was extremely nose heavy and that I had pulled the throttles toward idle. We eventually had lost 1;200 ft down to FL308 before climbing back up to FL320. At first we both thought it was mountain wave/clear air turbulence but with the airspeed at 80 KIAS and no ECAM failures initially showing; I still suspected an air data computer #1 failure and switched the capt air data computer and FD to system 2. Later tried the captain back on air data computer 1 and the airspeed went back to 80 KIAS but none of the other air data computer 1 systems showed any failure; altimeter ok; pitch trim; yaw dampers and ats levers had all stayed engaged. By now we noticed the ECAM showed 'auto trim tk sys inop' and all the trim tank fuel had been sent forward to the center tank (+7000 pounds of fuel) and the cg was now at 24.1 percent; it had been 32 percent; aircraft gross weight about 305;000 pounds; also noted at FL308 that the tat was indicating -9C and sat -24C. This too didn't make sense so I asked ATC for a tat and/or sat reading from any aircraft in our area and altitude. Those reported readings matched what we had before the pitch over and loss of altitude. There weren't any pitot heat failures indicated on the overhead panel or ECAM. As we climbed back toward FL320 with the aircraft trimmed and stabilized the airspeed we tried to re-engage #2 autopilot; it immediately went into a pitch over again. We stabilized the aircraft again and tried engaging the autothrottles and they rapidly advanced toward maximum power. Also while this occurred if we varied altitude by 50 ft from FL320 the altitude alerter would sound off like it does at the 300 ft off alert. Notified ATC that we thought we might have air data computer and autopilot failures and needed to descend out of rvsm; down to FL280. About twenty minutes after the autopilot had disconnected and pitched over we were able to re-engage the #2 autopilot and ats #1 lever and maintain stabilized flight. There had been two previous write-ups about air data computer #1 and autopilot three days prior descending into ZZZ and the next flight on pushback. The sign- offs had been rnr air data computer 1 and later rnr fwc 1. The airplane seemed to have flown several legs since then with no write-ups. We had discussed these problems and write-ups prior to departure. We had two crew members jump seating with us; a current airbus captain and a previous flight standards airbus captain that we asked to come up front once things were stable to see if they had any ideas or suggestions and to assist us in communicating with the company via ACARS. Dispatch and maintenance were notified enroute and entries into the logbook were made. No circuit breakers were tripped and no failures other than the ECAM on the autotrim tank inoperative were observed.
Original NASA ASRS Text
Title: A300 flight crew experiences autopilot disconnect and aircraft pitch-down at FL320; with auto throttles retarding. Captain's airspeed indicates 80 KIAS while First Officer's airspeed indicates 320+ KIAS with the overspeed sounding. The First Officer's airspeed indications are deemed correct and control is passed to him and recovery is initiated.
Narrative: Cruising at FL320 in the clouds with constant light chop/turbulence with a TAT around -24C; we suddenly had the #2 autopilot disconnect and the aircraft rapidly pitched over toward 7 1/2 degrees nose down and autothrottles were rapidly advancing forward. I took the control wheel and made sure the autopilot and autothrottles were disconnected; no trim wheel movement was noticed though it was trimmed fairly nose down. We thought we had encountered clear air turbulence/mountain wave from the thunderstorms in the area that we were diverting around. First Officer immediately notified ATC that we had lost altitude from mountain wave activity. I was slowly pulling the nose up (the nose was extremely heavy) and reducing power when I saw that my airspeed was rapidly bleeding off and going through the hook/stall; to 80 KIAS. This wasn't adding up in my mind as I saw that we had lost 1;000 FT of altitude and we were in a nose low attitude then the mach over-speed warning sounded. Checking the standby attitude indicator also showed nose low and I quickly looked over at the First Officer flight instruments and they showed the nose low but airspeed in the zipper around 320-330 KIAS. I told the First Officer that his instruments were correct and that he had the airplane and that it was extremely nose heavy and that I had pulled the throttles toward idle. We eventually had lost 1;200 FT down to FL308 before climbing back up to FL320. At first we both thought it was mountain wave/clear air turbulence but with the airspeed at 80 KIAS and no ECAM failures initially showing; I still suspected an ADC #1 failure and switched the Capt ADC and FD to system 2. Later tried the Captain back on ADC 1 and the airspeed went back to 80 KIAS but none of the other ADC 1 systems showed any failure; Altimeter ok; Pitch Trim; Yaw Dampers and ATS levers had all stayed engaged. By now we noticed the ECAM showed 'Auto Trim Tk Sys Inop' and all the trim tank fuel had been sent forward to the Center Tank (+7000 LBS of fuel) and the CG was now at 24.1 percent; it had been 32 percent; aircraft Gross Weight about 305;000 LBS; also noted at FL308 that the TAT was indicating -9C and SAT -24C. This too didn't make sense so I asked ATC for a TAT and/or SAT reading from any aircraft in our area and altitude. Those reported readings matched what we had before the pitch over and loss of altitude. There weren't any Pitot Heat failures indicated on the overhead panel or ECAM. As we climbed back toward FL320 with the aircraft trimmed and stabilized the airspeed we tried to re-engage #2 autopilot; it immediately went into a pitch over again. We stabilized the aircraft again and tried engaging the autothrottles and they rapidly advanced toward maximum power. Also while this occurred if we varied altitude by 50 FT from FL320 the altitude alerter would sound off like it does at the 300 FT off alert. Notified ATC that we thought we might have ADC and autopilot failures and needed to descend out of RVSM; down to FL280. About twenty minutes after the autopilot had disconnected and pitched over we were able to re-engage the #2 autopilot and ATS #1 lever and maintain stabilized flight. There had been two previous write-ups about ADC #1 and autopilot three days prior descending into ZZZ and the next flight on pushback. The sign- offs had been RNR ADC 1 and later RNR FWC 1. The airplane seemed to have flown several legs since then with no write-ups. We had discussed these problems and write-ups prior to departure. We had two crew members jump seating with us; a current Airbus Captain and a previous Flight Standards Airbus Captain that we asked to come up front once things were stable to see if they had any ideas or suggestions and to assist us in communicating with the company via ACARS. Dispatch and Maintenance were notified enroute and entries into the logbook were made. No circuit breakers were tripped and no failures other than the ECAM on the autotrim tank inoperative were observed.
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.