ERA19FA118 · Hughes 369 D
Rotor Blade Hughes 369 D · Accident: system/component malfunction/failure (non-power) while maneuvering
From Talking Rock, GA to Talking Rock, GA
Event
- NTSB case
- ERA19FA118
- 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
- 1 · 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
Hughes 369 D
- Aircraft type
- Hughes 369
- 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
- N89ZC
- Operator
- Rotor Blade
- Onboard fatalities
- Unknown
- Route
- From Talking Rock, GATo Talking Rock, GA
- Aircraft age
- About 38 years (built 1981)
- 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 133: Rotorcraft Ext. Load
- 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
- Maneuvering · low-altitude flying
- 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 propeller/rotor
- Aircraft › Aircraft structures
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The helicopter pilot was using an aerial saw to trim trees along power lines. A witness reported that the pilot performed one pass, then returned for the second pass when the helicopter began to spin counterclockwise around its main rotor mast. During the second rotation, the helicopter impacted trees and terrain before coming to rest on its right side. Postaccident examination revealed a fracture of the overrunning clutch outer race and cracks on three of the engine mounts. While two of the three engine mounts cracks were likely a result of impact forces, the cracks on a third engine mount were likely present prior to the accident. The failure of the overrunning clutch subassembly outer race resulted in a loss of power to the main rotor system. Given the helicopter's low altitude and airspeed at the time of the loss of power, the pilot was likely unable to successfully initiate and perform an autorotative landing.
Before its installation onto the helicopter, the overrunning clutch subassembly had been repaired, which included the installation of a new outer race. The accident helicopter operated with the overrunning clutch subassembly for about 33 flight hours until the accident occurred. Examination of the fracture surfaces revealed signatures consistent with fatigue and subsequent overload. The orientation of the crack in the circumferential plane was consistent with an anomalous bending load, such as an angular misalignment of the drivetrain, that drove fatigue crack initiation.
Directionality of the deformation and fracture of the center engine mount was primarily in the vertical direction and the fracture surfaces exhibited evidence of oxidation, indicating that the cracks were present before the accident. Therefore, it is likely that the damaged center engine mount was the source of the anomalous bending loads that led to fatigue crack initiation and subsequent failure of the overrunning clutch outer race.
The 100-hour/annual inspection of the engine mounts could be performed with the engine installed on the airframe, and the operator had done so; however, the presence of the engine could present difficulties for a mechanic in performing a visual inspection, particularly of the forward side of the center engine mount, where the cracks were located. Maintenance records indicated that, in the 9 months preceding the accident, the engine mounts were inspected six times with no anomalies observed. However, when the engine mount cracks may have developed and whether they would have been visible during any of the previous inspections could not be determined based on the available information..
Probable cause
A fatigue failure of the overrunning clutch subassembly due to abnormal bending loads due to cracks on the center engine mount, which resulted in an inflight loss of power. Contributing to the accident was the helicopter's low altitude and airspeed when the loss of power occurred, which precluded the pilot from successfully performing an autorotation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19FA118
- Event ID
- 20190305X64637
- Case number
- ERA19FA118
- 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, coordinates. 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: 1925f450d99bfaf888779fa77a483cb76d03738bf2a5bc4c58baf21fb0bb59eb; retrieved 2026-09-15T06:55:00.845Z.