FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines McDonnell Douglas MD-80 accident

12 Sept 1989 · Chicago, IL, United States

McDonnell Douglas MD-80 · Accident: airframe, component or system failure en route

From Frederick Douglass Greater Rochester International Airport (ROC) to an unrecorded destination

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
CHI89FA183
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
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
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

McDonnell Douglas MD-80

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
N244AA
Onboard fatalities
Unknown
Route
From Frederick Douglass Greater Rochester International Airport (ROC), Rochester, NYTo not recorded
Aircraft age
Not recorded
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 · descent
First occurrenceThe 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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Company maintenance personnel › Maintenance, replacement, not performed
  • Hydraulic system › No pressure
  • Pilot in command › Directional control, not maintained
  • Pilot in command › Powerplant controls, improper use of

Approximate · Estimated position: the centre of Chicago, IL, the place the record names. Not the accident site.

NTSB narrative

DURING DESCENT A COMPLETE HYDRAULIC SYSTEM FAILURE OCCURRED. DURING THE LANDING ROLLOUT THE AIRPLANE RAN OFF THE SIDE OF THE RUNWAY & COLLIDED WITH A MANHOLE COVER COLLAPSING THE NOSE GEAR. THE POWER TRANSFER UNIT SHUTOFF VALVE, P/N 240695, FAILED; ONE OF THE DUAL VALVE BODY HALVES SEPARATED AT THE MOUNTING PLATE. THE VALVE HAD A KNOWN HISTORY OF FAILURES, AND A KIT VERSION OF A 'FIX' TO THE VALVE HAD BEEN AVAILABLE BY THE MANUFACTURER. THE FLIGHT MANUAL CAUTIONS THAT FOR LANDING WITH NO HYDRAULIC POWER, INCREASING AMOUNTS OF REVERSE THRUST SIGNIFICANTLY REDUCES RUDDER EFFECTIVENESS, AND IN THE EVENT OF DIRECTIONAL CONTROL PROBLEMS TO REDUCE REVERSE THRUST AS REQUIRED AND SELECT FORWARD IDLE IF NECESSARY TO MAINTAIN OR REGAIN CONTROL. DFDR READOUT SHOW THE APPLICATION OF THRUST GREATER THAN IDLE REVERSE DURING THE THE LANDING ROLLOUT.

Probable cause

A LOSS OF HYDRAULIC SYSTEM PRESSURE DUE TO THE OPERATOR'S FAILURE TO REPLACE A SYSTEM COMPONENT THAT HAD A KNOWN HISTORY OF FAILURES, AND THE PILOT'S IMPROPER USE POWERPLANT CONTROLS RESULTING IN A DEGRADATION OF RUDDER EFFECTIVENESS. A CONTRIBUTING FACTOR WAS THE FAILURE OF THE POWER TRANSFER UNIT SHUTOFF VALVE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI89FA183
Event ID
20001213X29315
Case number
CHI89FA183
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 2e9b76845c88ec498febb9ee348b31f31ca15f22a55dbdb52aded136800e5af5; retrieved 2026-09-18T19:08:24.938Z.