American Airlines Flight 320
McDonnell Douglas DC-9-82 · Accident: loss of control on ground/water during landing
From Dallas Fort Worth International Airport (DFW) to Cleveland Hopkins International Airport (CLE)
Event
- NTSB case
- IAD97FA052
- 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
- Instrument Meteorological Cond
McDonnell Douglas DC-9-82
- Aircraft type
- McDonnell Douglas DC-9
- 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
- N275AA
- Operator
- American Airlines
- Onboard fatalities
- Unknown
- Route
- From Dallas Fort Worth International Airport (DFW), DAL/FORT WORTH, TXTo Cleveland Hopkins International Airport (CLE)
- 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
- Landing · landing roll
- 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
- Loss of control on ground/water
- 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
- Pilot in command › Autopilot, continued
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The DC-9 was number 2 for the ILS approach behind a commuter airplane, and was placed in holding while chemicals were applied to the runway due to snow and slush. The DC-9 captain requested a braking action report, which the tower controller relayed to the commuter airplane that had not yet landed. A braking action report was not received prior to the DC-9 landing. The captain elected to continue the approach with full auto-land selected to a contaminated runway, without a braking action report and a crosswind component of 13 knots. On the runway, the auto-pilot responded and attempted to return the airplane to the centerline of the runway. After 18 seconds and with the airplane's nose drifting left, the captain disengaged the auto-pilot, and applied full right rudder and brake to stop the left drift. The DC-9 departed the left side of the paved runway approximately 5,500 feet down the 8,998 foot runway, and facing 80 degrees left of the runway heading. A review of the manual revealed that the operator's flight manual contain no guidance or limitations for pilots regarding the use of full auto land and roll-out on contaminated runways
Probable cause
The pilot in command did not maintain control while utilizing the full auto-land system. Factors to this accident were a contaminated runway, a crosswind, and inadequate guidance provided in the aircraft manual.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD97FA052
- Event ID
- 20001208X07558
- Case number
- IAD97FA052
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1997-03-06.
- API snapshot SHA-256: 0c14dab7135f8fc69472ade08d55803af0f8d48e7c1ef306a929f8b9d4d08b5d; retrieved 2026-09-18T17:41:18.690Z.