FlarePath
Cases › CEN10LA363 · Part 121 airline

EMBRAER EMB-145LRAMERICAN EAGLE AIRLINES INC

Pioneer, LA, USA · 2010-06-28·N601DW

0
fatal
2
serious
Serious injury
highest injury
—
damage

What happened

NTSB summary, verbatim

The commercial flight was cruising at an altitude of 38,000 feet when the flight crew made a public announcement to the passengers (and a separate call to the flight attendant) that they may encounter turbulence, and the fasten seatbelt sign was turned on. The captain said they entered clouds and the flight was smooth for about 10 minutes when they noticed a very small red return (thunderstorm cell)on the radar about 5 miles in front of them. The crew did not have enough time to take evasive action and they penetrated the cell, encountering moderate rain with a strong updraft followed by one instance of a severe downdraft. The autopilot disengaged and the captain assumed control of the airplane. Shortly after, the flight attendant called on the interphone and said that she was assisting an elderly passenger in the lavatory when the upset occurred and they were both seriously injured. The captain immediately declared an emergency and landed without further incident. Weather Surveillance Radar (WSR) imagery identified a discrete cell of strong reflectivity values coincident with the airplane's position at the time of the turbulence event. A review of recorded weather data from two separate air traffic control centers handling the flight showed that moderate to extreme intensity precipitation existed ahead of the airplane for an extended period. However, the controllers did not recall seeing any displayed precipitation in the accident location, although they did recall seeing precipitation in other locations around the area. Review of display settings in use by the controllers showed no reason that the weather would not have been displayed, and there was no indication of a system malfunction. Review of ATC communications between the controllers and the flight crew revealed there were no discussions of the precipitation and thunderstorm activity ahead of the flight as required per Federal Aviation Administration (FAA) Order 7110.65, paragraph 2-6-4, "Weather and Chaff Services."

Probable cause

the Board's determination
The inadvertent encounter with convective weather during cruise flight. Contributing to the accident was the flight crew's failure to detect and avoid the thunderstorm cell earlier in the flight, and the failure of air traffic controllers to provide the convective weather information to the flight crew.

Occurrence sequence

2 stepsNTSB coding · CICTT taxonomy
  1. 1 · Enroute-cruise
    Inflight upset
  2. 2 · Enroute-cruise
    Turbulence encounter
    defining event

Findings

3 causal · 0 contributing
  • CAUSE
    Personnel issues › Task performance › Communication (personnel) › Lack of communication — ATC personnel
  • CAUSE
    Personnel issues › Task performance › Planning/preparation › Weather planning — Flight crew
  • CAUSE
    Environmental issues › Conditions/weather/phenomena › Turbulence › Convective turbulence — Effect on operation

Safety recommendations

3 issuedwhat changed because of this accident
  • A-12-018Closed - Unacceptable ActionCLASS IIletter ↗

    TO THE FEDERAL AVIATION ADMINISTRATION: Study the technical feasibility of presenting, through the use of the weather and radar processor system or other means, real-time total lightning data on controller displays at both air route traffic control centers and terminal radar approach control facilities, and, if feasible, incorporate real-time total lightning data on controller displays and in associated weather products for current and future display systems.

  • A-12-019Closed - Unacceptable ActionCLASS IIletter ↗

    TO THE FEDERAL AVIATION ADMINISTRATION: To the extent practicable, incorporate direct center weather service unit briefings on new weather-related air traffic control equipment and information services into controller training.

  • A-12-020Closed - Acceptable ActionCLASS IIletter ↗

    TO THE FEDERAL AVIATION ADMINISTRATION: Incorporate real-time total lightning data into the products supplied to pilots through the flight information services –broadcast data link.

Sequence of events

5 timed eventsfrom the FDR factual report · claude-fable-5-1 (in-session)
  1. SRN 192,940-193,240cruisep.2
    Five-minute event window plotted (figures 1 and 2)
  2. SRN 193,074cruisep.3
    Master warning on for 6 seconds
  3. SRN 193,090cruisep.3
    Master caution on for 10 seconds
  4. SRN 193,091-193,092cruisep.2
    Lowest vertical acceleration about -0.8 g at SRN 193,091, highest about 1.7 g at SRN 193,092
  5. SRN 193,153cruisep.2
    Autopilot disengaged at about 36,750 ft pressure altitude

NTSB analysis

from the final report

The commercial flight was cruising at an altitude of 38,000 feet when the flight crew made a public announcement to the passengers (and a separate call to the flight attendant) that they may encounter turbulence, and the fasten seatbelt sign was turned on. The captain said they entered clouds and the flight was smooth for about 10 minutes when they noticed a very small red return (thunderstorm cell)on the radar about 5 miles in front of them. The crew did not have enough time to take evasive action and they penetrated the cell, encountering moderate rain with a strong updraft followed by one instance of a severe downdraft. The autopilot disengaged and the captain assumed control of the airplane. Shortly after, the flight attendant called on the interphone and said that she was assisting an elderly passenger in the lavatory when the upset occurred and they were both seriously injured. The captain immediately declared an emergency and landed without further incident. Weather Surveillance Radar (WSR) imagery identified a discrete cell of strong reflectivity values coincident with the airplane's position at the time of the turbulence event. A review of recorded weather data from two separate air traffic control centers handling the flight showed that moderate to extreme intensity precipitation existed ahead of the airplane for an extended period. However, the controllers did not recall seeing any displayed precipitation in the accident location, although they did recall seeing precipitation in other locations around the area. Review of display settings in use by the controllers showed no reason that the weather would not have been displayed, and there was no indication of a system malfunction. Review of ATC communications between the controllers and the flight crew revealed there were no discussions of the precipitation and thunderstorm activity ahead of the flight as required per Federal Aviation Administration (FAA) Order 7110.65, paragraph 2-6-4, "Weather and Chaff Services."