CEN25LA013 · Rotorway EXEC 90
Rotorway EXEC 90 · Accident: system/component malfunction/failure (non-power) on approach
From Plymouth Municipal Airport (C65) to an unrecorded destination
Event
- NTSB case
- CEN25LA013
- 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
Rotorway EXEC 90
- Aircraft type
- Rotorway EXEC
- Category
- Helicopter
- 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
- N314AC
- Operator
- Rutherford Stephen M
- Onboard fatalities
- Unknown
- Route
- From Plymouth Municipal Airport (C65), Plymouth, INTo not recorded
- Aircraft age
- About 20 years (built 2004)
- 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 · VFR pattern base
- Defining eventThe 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft propeller/rotor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter owner/pilot reported that while he and his flight instructor were practicing an autorotation, the flight instructor heard a noise. Shortly thereafter, the helicopter started to yaw to the left and the airspeed decreased. The flight instructor took over control of the helicopter and initiated an autorotation to a corn field. The right skid caught the ground, and the helicopter rolled onto its right side. The main rotor and fuselage sustained substantial damage. A postaccident examination revealed that the forward tail rotor belt broke. The belt was found frayed at the separation point. A review of the tail rotor maintenance records revealed that the tail rotor belts had not been replaced since 2006. The manufacturer recommends tail rotor belt replacement at 250 hours, 2 years, or as needed upon conditional inspections, whichever comes first. The operator reported that before the accident the belts appeared to be in satisfactory condition but acknowledged they were beyond the 2-year service life and should have been replaced.
Probable cause
A loss of control due to the failed forward tail rotor belt as a result of the owner’s failure to follow the helicopter manufacturer’s tail rotor belt replacement recommendations.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA013
- Event ID
- 20241015195315
- Case number
- CEN25LA013
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: ab73f409a7750347d1d39b2c79321d022aac96931b8de7e2f8b0c811adc1c4b8; retrieved 2026-09-16T19:22:55.399Z.