FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines Flight 289

4 Aug 2024 · Linneus, MO, United States

Boeing 777-223 · Accident: turbulence encounter en route

From FIUM · Fiumicino to Dallas Fort Worth International Airport (KDFW)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
DCA24LA254
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Boeing 777-223

Aircraft type
Boeing 777
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N793AN
Onboard fatalities
Unknown
Route Possible conflict
From FIUM · FiumicinoTo Dallas Fort Worth International Airport (KDFW), Dallas, TX
Aircraft age
About 24 years (built 2000)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Turbulence encounter
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

American Airlines flight 289 encountered moderate to severe convective turbulence while in cruise flight at flight level (FL) 360 [36,000 feet], enroute from the Leonardo da Vinci (LIRF) Airport, Rome, Italy to the Dallas Fort Worth International Airport (DFW), Dallas-Fort Worth, Texas. As a result of the turbulence, one flight attendant (FA) sustained a serious injury, and another FA and one passenger sustained a minor injury. The aircraft continued to DFW and landed without further incident. The accident occurred while air traffic control (ATC) services were being provided by Kansas City Air Route Traffic Control Center (ZKC). The involved position was R92 (Rivers Sector).

The event flight was operated by three flight crewmembers that consisted of a captain, a first officer (FO), and a relief FO. At the time of the turbulence encounter, the FO was the pilot flying (PF), and the relief FO was the pilot monitoring. There were also eight flight attendants (FAs) on the flight. During the event, four FAs (number 2, 3, 6, and 8) were located in the aft galley, two FAs (number 1, and 5) were located in the business galley, and two FAs (number 4, and 7) were located in the forward galley.

The flight crewmembers reported that the flight had intermittently encountered cirrus clouds with light chop while at FL360. Due to the turbulence, they decided to keep the fasten seatbelt sign illuminated.

About 2256 Coordinated Universal Time (UTC), the flight was near navigational point LOAMY in southwest Missouri and flying through some cirrus clouds. When the flight emerged from the cirrus clouds, the flight crewmembers saw a narrow, towering, cumulus cloud that appeared to be building in front of them. They informed ATC and, immediately turned toward the right to avoid the cloud. They indicated that the airplane caught the upwind edge of the cloud and the flight experienced turbulence for a duration of about 15 seconds.

Although the flight crew had checked in with the R92 controller and was on the R92 controller's frequency for almost ten minutes before they requested to deviate around the cumulus cloud, the R92 controller did not issue the depicted weather that the flight crew had requested to deviate around (see figure 1). The controller also did not request pilot reports (PIREPS) from any flight crews in the sector.

Figure 1. WSR-88D composite radar image at 2257Z with aircraft position and flight track overlay.

The onboard aircraft weather radar system is the primary source for weather avoidance while enroute. The flight crewmembers stated that their aircraft weather radar was on and was not showing any precipitation returns. They also stated that there was no WIFI connectivity, it was placarded “inop”, and therefore inhibited their ability to use the weather applications installed on their electronic flight bag.

After the event, the PF called the galley to check on the FAs and to let them know they were clear of the turbulence. After the PF hung up, the purser called back to inform them of an FA injury. Medical personnel onboard assisted the injured FA. The captain, who was on a crew break in the cabin, called to inform them of the situation in the cabin. After he checked on the injuries he returned to the flight deck. The flight crew declared an emergency and expedited the flight to DFW.

The aft FAs reported that, before the turbulence event, they were preparing to complete the final cabin service of the flight. The fully loaded beverage carts had been positioned in the aft galley and the beverage inserts were on top of the carts. Coffee had just been poured into the coffee thermos containers sitting in the inserts in preparation for service. The number 2 FA was about to load the hot entrees when, suddenly and without warning, the aircraft encountered two “really bad” turbulence events. During the second encounter, the number 3 and number 8 FAs flew up in the air and were slammed to the floor. The number 8 FA sustained a serious injury, and the number 3 FA sustained a minor injury due to hot coffee being spilled on her.

After landing, emergency personnel met the aircraft at the gate and attended to the injured. The number 8 FA was diagnosed with a fractured ankle and the number 3 FA had a burn on her arm. Additionally, one passenger reported a sore ankle.

A post-accident review of meteorology data showed that a convective Significant Meteorological Information (SIGMET) was in effect immediately east of the area and did not extend over the flight track. A review of the satellite and radar imagery showed an area of convective clouds developing over the region at the time of the turbulence event. The Kansas City WSR-88D depicted echoes with maximum reflectivity near 55 dBZ or extreme intensity under the flight track, with echoes of 15 dBZ extending through FL360. While airborne weather radar does not typically detect echoes less than 20 dBZ or light intensity echoes, proper down tilt of the beam would have detected significant echoes developing below the flight path as the they approached the area and air traffic control radar should have observed the echoes and issued advisories. Based on the aircraft location and the echoes over the position, this event was a convectively induced turbulence (CIT) event within the clouds.

Eddy dissipation rate (EDR) is a universal measure of turbulence rate. Recorded data from the airplane revealed that at about 2256 UTC, the EDR indicated values of 0.340 with a peak at 0.9877. The peak value equates to strong turbulence.

Probable cause

An inadvertent encounter with convectively induced turbulence during cruise.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA24LA254
Event ID
20240805194848
Case number
DCA24LA254
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 305e1c5a0e363429859152b123582ae4402d03c77be4276a584f45a307e97155; retrieved 2026-09-16T19:08:05.349Z.