ATL83FA063 · Mitsubishi MU-2B
Mitsubishi MU-2B · Accident: overrun during takeoff
From Louisville, KY to C · Odessa, TX
Event
- NTSB case
- ATL83FA063
- 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
- General aviation
- 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
Mitsubishi MU-2B
- Aircraft type
- Mitsubishi MU-2
- 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
- N5589S
- Operator
- Robert Clark
- Onboard fatalities
- Unknown
- Route
- From Louisville, KYTo C · Odessa, 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 91: General Aviation
- 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
- Takeoff
- 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
- Overrun
- 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 › Aborted takeoff, delayed
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Procedures/directives, not followed
Approximate · Estimated position: the centre of Louisville, KY, the place the record names. Not the accident site.
NTSB narrative
A TAKEOFF WAS INITIATED FROM A 3539 FT WET/UPSLOPING RWY. THE GROSS WT OF THE ACFT WAS ABOUT 9300 LBS (300 LBS UNDER THEMAX GROSS WT). THE PLT STATED THE ACFT ACCELERATED, BUT NEVER REACH '107.' AFTER USING ABOUT 2700 FT, THE PLT DECIDED TO ABORT THE TAKEOFF, HE PUT BOTH PROPS IN REVERSE & APPLIED FULL BRAKES. THE ACFT CONTINUED OFF THE DEPARTURE END OF THE RWY, WENT THRU THE PERIMETER FENCE, CROSSED A 4 LANE ROAD & MEDIAN, HIT A UTILITY POLE & FINALLY IMPACTED A LARGE TREE ABOUT 850 FT FROM THE END OF THE RWY. THE PLT USED A 5 DEG FLAP SETTING. THE PERFORMANCE MANUAL SHOWED THAT A TAKE-OFF DISTANCE TO CROSS OVER A 50 FT OBSTRUCTION WAS 1900 FT. THE MANUAL STATED THAT FOR EITHER 5 OR 20 DEG OF FLAPS, ALLOW THE ACFT TO ACCELERATE TO 70 TO 80 KTS, BEFORE APPLYING BACK PRESSURE ON THE ELEVATOR CONTROL, THEN THE ACFT SHOULD LIFT OFF AT ABOUT 93 TO 96 KTS. AN INVESTIGATION DISCLOSED NO POWER PLANT OR CONTROL MALFUNCTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FA063
- Event ID
- 20020917X04310
- Case number
- ATL83FA063
- 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: 1b974646c1718fab3b7fefa5a84be6f3289f1192362ba3ee5c4c62b1b341612b; retrieved 2026-09-21T18:02:56.804Z.