Palm Beach Aviation Aero Commander 500 incident
Aero Commander 500 · Incident: airframe, component or system failure during takeoff
From Everglades Airpark (X01) to PBI · W. PALM BEACH, FL
Event
- NTSB case
- MIA93IA083
- 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
- Charter & commuter
- 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
Aero Commander 500
- Aircraft type
- Aero Commander 500
- 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
- N3836C
- Operator
- Palm Beach Aviation
- Onboard fatalities
- Unknown
- Route
- From Everglades Airpark (X01)To PBI · W. PALM BEACH, FL
- 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 135: Air Taxi & Commuter
- 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 · rejected 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
- 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
- Minor
Cause areas
- Propeller system/accessories, hub › Fatigue
Approximate · Estimated position: the centre of Everglades City, FL, the place the record names. Not the accident site.
NTSB narrative
THE AIRLINE TRANSPORT PILOT-IN-COMMAND ABORTED THE TAKEOFF WHEN A PROPELLER BLADE FROM THE RIGHT ENGINE SEPARATED FROM THE RIGHT PROPELLER SYSTEM. EXAMINATION OF THE PROPELLER HUB BY THE NTSB MATERIALS LABORATORY DIVISION REVEALED THE PROPELLER HUB ARM FAILED DUE TO PREEXISTING FATIGUE CRACKING IN THE BEARING RETENTION RADIUS, FROM POLISHING AND WEAR OF THE RADIUS FROM CONTACT WITH THE SPLIT RINGS.
Probable cause
THE PREEXISTING FATIGUE CRACKING OF THE PROPELLER HUB ARM IN THE BEARING RETENTION RADIUS DUE TO POLISHING AND WEAR OF THE RADIUS FROM CONTACT WITH THE SPLIT RINGS, RESULTING IN A PROPELLER BLADE SEPARATING FROM THE PROPELLER HUB ON THE TAKEOFF GROUND RUN, AND SUBSEQUENT ABORTED TAKEOFF.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA93IA083
- Event ID
- 20001211X12020
- Case number
- MIA93IA083
- 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: 8fc7d05335e867284d305bb76252f4f5f25d485bd9ede0c7f2f0c7bb73216288; retrieved 2026-09-18T18:40:33.388Z.