BOEING 777-223AMERICAN AIRLINES INC
What the docket says, assembled. No language model is involved, so nothing on this page can be invented — every line traces to a recorder, a report page or the Board's own record.
Ask the docket
passages, not paraphrasesEvery answer is a passage of the docket with the page it came from, or the words “not in the docket”. Nothing is summarised or reasoned for you — read the source.
One timeline
0 timed factsthe recorder events from the FDR report, with the transcript's warnings, callouts, the words nearest each event and the final seconds — on one clock, as printed in each reportNo timed facts: this docket has no extracted recorder sequence and no transcript.
- 0630 UTC (approximately)Accident flight departed
- 0658:38 UTC (approximately)Upset event occurred during climb
- 0700 UTCAmerican Airlines Flight 170 experienced severe turbulence during climb over international waters about 194 nautical miles east of Narita, Japan
- Enroute-climb to cruise: Turbulence encounter
Precedents
8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded- BOEING 777-200 · United Airlines Inc.,New Market, VA
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter - BOEING 737-8H4 · Southwest Airlines CoWaycross, GA
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter - BOEING 747-422 · United AirlinesTangshan, CN
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter - BOEING 767-224 · CONTINENTAL AIRLINES INCBavaro, DO
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter - BOEING 737-7CT · SOUTHWEST AIRLINES COGulf of America, GM
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter - BOEING 737-8 · American Airlines IncMiami, FL
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter - BOEING 777-223 · AMERICAN AIRLINES INCAtlantic Ocean, AO
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter - BOEING 787 · UNITED AIRLINES INCClaveria, OF
- ●Environmental issues › Conditions/weather/phenomena › Turbulence
Turbulence encounter
What the record says
a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable cause- 8 of 8Environmental issues › Conditions/weather/phenomena › Turbulencecited here too
- 8 of 8Turbulence encounter
- Conditions/weather/phenomena › Turbulence
- —
- —
A teaching device, not a verdict: what the record would have looked at, next to what the Board found.
- DCA10FA0122009-11-19 · BOEING 777-200 · United Airlines Inc.,
The flight crew’s inadvertent encounter with a small area of cumulous clouds at night that resulted in moderate to severe convectively induced turbulence.
- DCA19CA1512019-05-25 · BOEING 737-8H4 · Southwest Airlines Co
an encounter with convectively induced turbulence while penetrating cumulus clouds during descent.
- DCA11FA0912011-07-29 · BOEING 747-422 · United Airlines
an inadvertent encounter with convectively induced turbulence likely due to radar limitations and convective weather developing upwards into the flight path.
- DCA09IA0712009-08-03 · BOEING 767-224 · CONTINENTAL AIRLINES INC
The flight crew's inadvertent flight through the top of a convective updraft that resulted in an encounter with convective induced turbulence. Contributing to the severity of the incident was the unrestrained status of several passengers, contrary to the lighted seat belt sign.
- DCA24FA1432024-04-03 · BOEING 737-7CT · SOUTHWEST AIRLINES CO
The pilot’s inadvertent encounter with convectively induced turbulence from a broken line of embedded thunderstorms moving across the region. Contributing to the accident was the failure of the air traffic controller to issue pertinent weather information along the airplane’s route of flight due, in part, to the sector over-saturation and frequency congestion caused by damaged communication equipment and the inability to split the sector to alleviate some of the traffic volume.
This is the pattern in the NTSB’s own record across similar accidents — which findings it cited, what it coded, what it recommended. It is drawn from the record, not written about this case, and it never assigns blame: investigations exist to prevent the next accident (ICAO Annex 13).