Probable cause
The failure of the two fuel control unit drive bearings for reasons that could not be determined based on the available evidence, which resulted in an uncommanded engine acceleration and subsequent overspeed condition. Contributing to the accident was the pilot’s improper autorotation, which resulted in a hard landing.
NTSB analysis
The commercial pilot and two flight crewmembers were conducting an emergency medical services flight. The helicopter was in cruise flight when the pilot noticed that the rotor rpm had rapidly increased and that the high rotor aural warning had sounded. Despite troubleshooting efforts, the pilot was unable to reduce the rotor rpm, so he performed on autorotation to a field. During the subsequent run-on landing, the helicopter touched down hard. During the landing, the main rotors contacted and partially severed the tailboom.
Disassembly of the fuel control unit (FCU) revealed that the two drive bearings that ensure drive integrity between the FCU and the fuel pump had failed. The failure of the bearings led to excessive wear in the races and degraded the drive shaft such that it could no longer provide positive drive to the FCU, which the FCU interpreted as an underspeed condition. This led the FCU to command more power to the engine and resulted in an engine overspeed condition. Metallurgical testing of the FCU drive bearings did not reveal the reason for their failure. As a result of this accident, the engine manufacturer adjusted the FCU bearing replacement schedule from a one-time replacement to replacement every 600 hours.
Text from the NTSB. Open the NTSB docket for CEN14LA312 for the full record.
Event
- Date
- Jun 23, 2014
- Type
- Accident
- Place
- Texarkana, Texas
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
Airbus Helicopters AS-350B2
- N-number
- N407EM
- Category
- Helicopter
- Year built
- 1986
- Damage
- Substantial
- Operating rule
- Part 135 (charter and commuter)
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.