NYC95IA020 · Cessna 310R
Cessna 310R · Incident: airframe, component or system failure during takeoff
From an unrecorded airport to Syracuse Hancock International Airport (SYR)
Event
- NTSB case
- NYC95IA020
- 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
Cessna 310R
- Aircraft type
- Cessna 310
- 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
- N5494J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Syracuse Hancock International Airport (SYR), Syracuse, NY
- 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 › Separation
- Propeller system/accessories, hub › Fatigue
Approximate · Estimated position: the centre of Rochester, NY, the place the record names. Not the accident site.
NTSB narrative
THE PILOT HEARD A LOUD 'BANG' AFTER HE APPLIED FULL POWER TO BEGIN THE TAKEOFF ROLL. HE THEN NOTICED THAT THE RIGHT PROPELLER HAD SEPARATED FROM THE ENGINE. METALLURGICAL EXAMINATION OF THE PROPELLER HUB REVEALED THAT THE HUB SEPARATED AS A RESULT OF FATIGUE CRACKING THAT INITIATED FROM THE HOLES FOR THE STUDS USED TO ATTACH THE HUB TO THE CRANKSHAFT FLANGE. A SUBSTANTIAL AMOUNT OF FRETTING WAS NOTED ON THE MOUNTING FACE OF THE HUB, INDICATING POSSIBLE LOOSENESS BETWEEN THE HUB AND CRANKSHAFT. THIS IS LIKELY DUE TO INADEQUATE PRELOAD ON THE STUB AS A RESULT OF INADEQUATE ASSEMBLY TORQUE ON THE NUTS.
Probable cause
Inadequate maintenance which resulted in undertorqued bolts, fatigue cracking of the hub, and the separation of the propeller assembly from the engine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95IA020
- Event ID
- 20001206X02502
- Case number
- NYC95IA020
- 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: 6b0e683c18324d8c0f3e0cefacee3006b253ed1770a187768dc47a95745935f9; retrieved 2026-09-18T18:07:29.891Z.