Accident Details
Probable Cause and Findings
Brief and temporary blockage of the pitot probes in cruise flight, most likely due to ice crystals aloft, leading to erroneous airspeed indications and airplane automation degradation as designed. Contributing to the incidents were design features of the Thales AA probes which left them more susceptible to high altitude ice crystal icing than other approved pitot probe designs.
Aircraft Information
Registered Owner (Current)
Analysis
HISTORY OF FLIGHT
On June 23, 2009, at 0301 coordinated universal time (UTC) an Airbus A330-323, US registration N805NW, manufacturer serial number 552, operated by Northwest Airlines as flight 08 between Hong Kong and Tokyo experienced airspeed and other flight deck anomalies while in cruise flight at FL390, 50 miles southwest of the Kagoshima Airport, Japan.
The flight was passing nearby an area of convective weather activity. The airplane was in level flight, on autopilot, at a speed of mach 0.81, heading approximately 065 magnetic along RNAV (area navigation) route M750. The flight crew was aware of the weather, and reported they were adjusting the airborne weather radar tilt and cycling between MANUAL and AUTO modes in an attempt to get the most complete picture to avoid penetrating the convective activity. Outside (static) air temperature was about -52ºC. They reported that the main cell appeared to be about 25 miles north of their flight path. However, just prior to the event the airplane entered an area of cirrus clouds with light turbulence and moderate rain with a brief period of intense rain, and hail aloft.
The crew received a master warning and master caution alert, and the autopilot (AP), autothrust (ATH) and flight directors disengaged. The crew reported airspeed fluctuations on the Captain’s, First Officer’s (FO), and the standby airspeed indicators. They reported receiving a stall warning, noted the flight law switched to Alternate Law, and saw messages indicating NAV ADR DISAGREE and NAV IAS DISCREPANCY. They reported the airspeed fluctuations and warnings lasted about one minute, and they controlled the airplane by pitch and power reference, per applicable checklist procedures until normal airspeed indications returned. They received ATC clearance to turn farther from the convective area, and after a short period the airspeed fluctuations and messages repeated for a duration of about two minutes. The airspeed indicators returned to normal and the crew re-engaged autopilot and completed the flight in alternate law.
A review of Flight Data Recorder (FDR) and Quick Access Recorder (QAR) information indicated the initial airspeed fluctuation between about 245 knots and 110 knots (Mach 0.81 to Mach 0.35) on the No.1 (Captain) Air Data Reference unit (ADR), followed within one second by the autopilot and autothrust disengagement and a brief stall warning. Note that the No.2 (First Officer) ADR airspeed was not recorded. Flight law switched to alternate law twice in the initial 35 seconds of the event. There were some minor pitch and altitude variations, less than 150 feet from assigned altitude. About 35 seconds after the initial fluctuation the flight control laws returned to normal, and the crew was able to re-engage the autopilot while turning farther from the weather area. About one minute 45 seconds after the initial event, the airspeed began to fluctuate again similarly between 245 and 110 knots on both the No.1 ADR and the standby airspeed. The autopilot again disconnected, and the flight control laws reverted to alternate law. Pitch and altitude excursions resulted in a brief climb of about 250 feet before returning to FL390. The No.1 ADR experienced fluctuations for about 3 minutes, while the standby airspeed dropped to 110 knots for about 30 seconds during the event. After the standby airspeed returned to normal, the crew was able to reengage the autopilot, although flight law remained in alternate for the remainder of the flight. Shortly after the fluctuations on No.1 ADR ceased, the autothrust was also re-engaged and the flight continued to land at Tokyo/Narita with no injuries, damage, or further incident. Post flight maintenance checks on the airspeed system revealed no discrepancies. The investigation of this incident was delegated to the U.S. by the Japan Transport Safety Board (JTSB). Note that this type of airspeed anomaly event is not normally reportable to the NTSB under the provisions of 49 Code of Federal Regulations (CFR) 830.5.
On May 21, 2009, at 2147 eastern daylight time (EDT), an Airbus A330-233, Brazilian registration PT-MVB, manufacturer serial number 238, operated by TAM Airlines as flight 8091 from Miami International Airport, Florida, to Sao Paulo Guarulhos International Airport, Sao Paulo, Brazil, experienced a loss of primary speed and altitude information while in cruise flight at FL370 over international waters, south of Haiti. The flight crew noted an abrupt drop in outside air temperature and observed St. Elmo’s Fire, followed by the loss of the Air Data Reference System, disconnections of autopilot and autothrust, and loss of primary airspeed and altitude. The flight crew continued using backup instruments, and after a short time, primary data was restored. The airplane remained in alternate flight law and displayed a rudder travel limit flag. The crew determined they could not restore normal law and continued the flight under the appropriate procedures. The flight landed at Sao Paulo with no further incident and there were no injuries or damage. The Brazilian Centro de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA), delegated the incident investigation into this event to the NTSB.
A review of recorded flight data indicated that while level at FL370, indicating mach 0.8 (260 knots), and in moderately turbulent conditions with an outside (static) air temperature of -45º C the No.1 ADR airspeed dropped rapidly from about 260 knots to approximately 60 knots for a few seconds, then rose to 100 knots. At the same time, the recorded pressure altitude dropped by about 300 feet. About one minute later, the autothrust and autopilot disengaged, consistent with the pilot report that the co-pilot’s airspeed also began to fluctuate. The Captain took over and began to fly by reference to the standby airspeed and instruments which he reported still appeared normal. Flight law reverted to alternate and the NAV ADR DISAGREE message was displayed.
About 6 seconds after the autopilot disengaged, recorded data indicated two brief re-engagements of the autopilot. Concurrent with the re-engagement, a pitch up to about 7 degrees nose up and slight climb was recorded, and the pilot reported a stall warning. Left side stick pitch inputs were recorded about one second after the autopilot disengaged from the second brief engagement, as the airplane climbed to about 38,000 feet. The autopilot remained disengaged during the remainder of the event, and the crew turned about 60 degrees to the left to diverge from the weather area, and the altitude decreased to about 36,500 feet, before reversing and increasing again. About 3 minutes and 30 seconds after the initial airspeed drop, the No.1 ADR returned to 260 knots, and the 300 foot altitude discontinuity ceased, indicating an altitude of about 37,400 feet. Left nose down stick inputs and a decrease in pitch were concurrent with the altitude returning to 37,000 (FL370). Then autopilot and autothrust were then re-engaged and the flight continued to Sao Paulo in alternate law with no further incident, no injuries, and no damage. Post flight maintenance checks on the airspeed system revealed no discrepancies.
AIRCRAFT INFORMATION
The Northwest airplane, N805NW, operator ship number 3305, was an Airbus A330-323, widebody twin engine long range aircraft. The TAM airplane, PT-MVB, was an Airbus A330-233. Although slightly different variants, the systems relevant to these incidents are nearly identical. Both airplanes were equipped with Pratt & Whitney 4168 engines. N805NW, the -300 series variant, had a longer fuselage and greater seating capacity, while PT-MVB, the -200 series variant, had a greater fuel capacity and range. N805NW was equipped with an optional software feature that was not installed on PT-MVB. The feature detects if a difference of more than 16 knots exists with any of the air data systems and displays a caution message indicating NAV IAS DISCREPANCY, and activates a chime and master caution alert. The only other significant difference was in the variant of pitot probes installed, discussed below.
Airspeed is measured by comparing the difference between total pressure, measured by forward projecting pitot probes, and static air pressure, measured via static ports oriented flush along the airplane surface. The A330 is equipped with three pitot probes and six static pressure ports. The pitot probes are fitted with water drains and electrical anti-ice heating elements. Heating is automatically activated when in flight.
The No.1 and No.2 pitot probes (Captain and First Officer) pneumatic measurements are converted into electrical signals by air data modules which deliver the signals to the Air Data Reference (ADR) units which convert the signals into speed data for display to the pilots, among other aircraft functions. The No.3 (standby) pitot probe also feeds an air data module which delivers the electrical signal to an additional ADR, as well as sending pneumatic information directly to the Integrated Standby Instrument System (ISIS), which is a unit that combines the standby airspeed, altitude and attitude indicators into one instrument.
Air data is used by many functions of the Auto Flight System, which is comprised of two Flight Management Guidance and Envelope Computers (FMGEC), a Flight Control Unit (FCU), which allows the selection of flight parameters, and three Multipurpose Control and Display Units (MCDU), which allow the flight crew to interface with the FMGEC. Each FMGEC includes a Flight Management component, controlling navigation and performance optimization functions among others, a Flight Guidance component which controls the autopilot, flight director (FD) and autothrust (ATHR), and a Flight Envelope component which controls data computation for the flight envelope and speed functions, center of gravity information and other inf...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# DCA09IA064