NYC91LA153 · Cessna 310R
Cessna 310R · Accident: airframe, component or system failure on approach
From Hartford Brainard Airport (HFD) to an unrecorded destination
Event
- NTSB case
- NYC91LA153
- 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
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
- N3227A
- Operator
- Pedro A. Romero · private individual
- Onboard fatalities
- Unknown
- Route
- From Hartford Brainard Airport (HFD), Hartford, CTTo not recorded
- 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
- Approach · IFR final approach
- 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 › Separation
- Propeller system/accessories, hub › Overtorque
Approximate · Estimated position: the centre of Westerly, RI, the place the record names. Not the accident site.
NTSB narrative
THE CESSNA 310 WAS ON FINAL APPROACH WHEN THE PILOT FELT A BUFFET AND LOST POWER IN THE RIGHT ENGINE. HE MADE A MISSED APPROACH AND DIVERTED TO A VFR AIRPORT. HE LANDED WITH THE RIGHT PROPELLER AND RIGHT MAIN LANDING GEAR MISSING FROM THE AIRPLANE, WHCIH WERE NEVER RECOVERED. POST ACCIDENT INVESTIGATION DISCLOSED THE THREADS OF THE PROPELLER MOUNTING BOLTS CONTAINED THE THREADS FROM THE PROPELLER HUB. THIS IS INDICATIVE OF THE PROPELLER HUB THREADS HAVING BEEN OVER TORQUED AT SOME TIME IN THEIR LIFE. ADDITIONAL INVESTIGATION DISCLOSED THE PROPELLER HAD LAST BEEN INSTALLED 499 HOURS PRIOR TO PROPELLER SEPARATION. THE AIRPLANE HAD BEEN PLACED IN A PROGRESSIVE INSPECTION PROGRAM WITH 50 HOUR INTERVALS FOR A 200 HOUR CYCLE. THE LOG BOOKS INDICATE THE AIRPLANE HAD BEEN 65 HOURS SINCE ITS LAST INSPECTION.
Probable cause
IMPROPER INSTALLATION OF THE RIGHT PROPELLER WHICH RESULTED IN THREAD FAILURE IN THE PROPELLER HUB AND SEPARATION OF THE PROPELLER IN FLIGHT. A FACTOR RELATED TO THE ACCIDENT WAS THE RIGHT PROPELLER STRIKING THE RIGHT MAIN LANDING GEAR CAUSING ITS SEPARATION FROM THE AIRPLANE AS THE PROPELLER DEPARTED THE AIRPLANE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC91LA153
- Event ID
- 20001212X17367
- Case number
- NYC91LA153
- 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: 5a74accbe375187d4cd3791483402fc1516b44ab724dee63e7a1fd77056986d3; retrieved 2026-09-23T04:07:59.901Z.