American Airlines McDonnell Douglas DC-9 incident
McDonnell Douglas DC-9 · Incident: in flight collision with object during initial climb
From William P. Hobby Airport (HOU) to Dallas Fort Worth International Airport (DFW)
Event
- NTSB case
- FTW89IA070
- 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
- Incident
- 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 DC-9
- 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
- N447AA
- Operator
- American Airlines
- Onboard fatalities
- Unknown
- Route
- From William P. Hobby Airport (HOU)To Dallas Fort Worth International Airport (DFW), DFW AIRPORT, 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
- Initial climb
- 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
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Copilot/second pilot › Instructions, written/verbal, not followed
- Pilot in command › Instructions, written/verbal, not followed
- Wrong runway › Selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE WAS CLEARED FOR TAKEOFF ON RUNWAY 12R, BUT A TAKEOFF WAS MADE ON RUNWAY 17. THE SOUTH 2,200 FEET OF RUNWAY 17 WAS CLOSED DUE TO CONSTRUCTION. THIS WAS NOTED BY NOTAMS AND ATIS AND THE CREWMEMBERS WERE AWARE OF IT. AS THE AIRPLANE ROTATED, THE LOWER PARTS OF IT IMPACTED SECTIONS OF WOODED BARRIERS THAT HAD BEEN PLACED ACROSS RUNWAY 17. THE CREW WAS IMFORMED OF POSSIBLE DAMAGE AND PROCEEDED TO DESTINATION WHERE EMERGENCY EQUIPMENT WAS WAITING AT LANDING. AIRPLANE DAMAGE WAS MINOR. SEVENTY THREE DAYS PRIOR TO THIS INCIDENT, ANOTHER AIR CARRIER AIRPLANE WAS CLEARED FOR TAKEOFF ON RUNWAY 12R AND ALSO INADVERTENTLY DEPARTED ON RUNWAY 17.
Probable cause
CREW'S FAILURE TO FOLLOW TAXI INSTRUCTIONS AND TO INSURE THAT THEY WERE ON THE PROPER RUNWAY PRIOR TO INITIATION OF THE TAKEOFF ROLL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW89IA070
- Event ID
- 20001213X27893
- Case number
- FTW89IA070
- 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: 9c60b35e6dd8c1770569ae172b363f6a47efc52a64c7a7869309206ed5c9bd1b; retrieved 2026-09-18T19:13:07.079Z.