MIA89LA045 · Piper PA-24-250
Nims Associates Piper PA-24-250 · Accident: airframe, component or system failure en route
From 40J · Perry, FL to Dallas Love Field (DAL)
Event
- NTSB case
- MIA89LA045
- 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
Piper PA-24-250
- Aircraft type
- Piper PA-24
- 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
- N8226P
- Operator
- Nims Associates
- Onboard fatalities
- Unknown
- Route
- From 40J · Perry, FLTo Dallas Love Field (DAL), Dallas, 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
- En route · cruise
- 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
- Other maintenance personnel › Maintenance, installation, improper
- Propeller system/accessories › Fatigue
- Propeller system/accessories › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE IN CRUISE FLT NEAR AN ARPT, THE PROP SEPARATED. PLT WAS GIVEN VECTORS TO ARPT & ENTERED PATTERN FOR LNDG. DOWNWIND LEG WAS EXTENDED DUE TO STRONG TAILWIND. STRONG HEADWIND ON FINAL CAUSED ACFT TO LAND SHORT. DURING LANDING ROLL ACFT COLLIDED WITH TWO FENCES. EXAMINATION OF ACFT REVEALED 6 PROP MOUNT BOLTS FAILED DUE TO FATIGUE AS A RESULT OF IMPROPER PLACEMENT OF PROP MOUNTING SHIM BETWEEN ENGINE CRANKSHAFT FLANGE AND STARTER GEAR FLANGE. ACFT MANUAL STATED PROP MOUNT BOLTS MAY FAIL DUE TO RELATIVE MOVEMENT BETWEEN THE TWO FLANGES IF SHIM IS NOT INSTALLED. CORRECT PLACEMENT OF THE SHIM IS BETWEEN THE PROP FLANGE & THE STARTER GEAR FLANGE. SUDDEN ENG STOPPAGE APROX 45 HRS EARLIER RESULTED IN PROP REMOVAL, OVERHAUL, & REINSTALLATION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA89LA045
- Event ID
- 20001213X27311
- Case number
- MIA89LA045
- 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: c52a1f0fa0d2b4cdab86916fb1089615130ef741626a48572687c05d85aa264e; retrieved 2026-09-23T08:17:09.594Z.