FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines McDonnell Douglas DC-9-83 accident

26 Dec 2008 · Los Angeles Intl Airport, CA, United States

McDonnell Douglas DC-9-83 · Accident: ground collision during pushback

From Los Angeles International Airport (LAX) to Dallas Fort Worth International Airport (DFW)

Report a problem

Event

NTSB case
DCA09FA022
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
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

McDonnell Douglas DC-9-83

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
N9617R
Onboard fatalities
Unknown
Route
From Los Angeles International Airport (LAX), Los Angeles Intl Airport, CATo Dallas Fort Worth International Airport (DFW), Dallas/Ft Worth, TX
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
Pushback/towing
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
Ground collision
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

  • Personnel issues › Action/decision

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

NTSB narrative

The first officer indicated that he advanced the left engine throttle during the airplane's taxi in order to clear what he suspected was a stuck bleed air valve. Although he suspected that he had only moved the throttle "about an inch", FDR data revealed it had been advanced to and remained at an extremely high power setting for approximately 28 seconds. This action, which occurred without the knowledge of the captain or the tug operator and without application of the parking brakes, resulted in a substantial increase in thrust that overwhelmed the tug's resistance until the airplane impacted the tug.

Probable cause

The first officer's unannounced advancement of the left engine throttle, which led to a sustained application of high thrust that caused the airplane to impact the tug.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA09FA022
Event ID
20081229X80551
Case number
DCA09FA022
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. 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: cebaa93538256638b2ac17af8c6b23d8026734456723d95bedcee58570449ec3; retrieved 2026-09-15T10:38:47.972Z.