FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR14TA370 · Eurocopter AS 350 B3

4 Sept 2014 · Lincoln, CA, United States

California Highway Patrol Eurocopter AS 350 B3 · Accident: loss of engine power (partial) during landing

From Auburn Municipal Airport (AUN) to Lincoln Regional Karl Harder Field (LHM)

Report a problem

Event

NTSB case
WPR14TA370
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
Unknown
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
Government
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

Eurocopter AS 350 B3

Aircraft type
Eurocopter AS-350
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
N217HP
Onboard fatalities
Unknown
Route
From Auburn Municipal Airport (AUN), Auburn, CATo Lincoln Regional Karl Harder Field (LHM), Lincoln, CA
Aircraft age
About 12 years (built 2002)
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
Public Aircraft
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
Landing · flare/touchdown
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
Loss of engine power (partial)
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The purpose of the public helicopter flight was to provide recurrent emergency procedures and night vision goggle training for the commercial pilot. Both the pilot and the flight instructor were active pilots for the law enforcement agency and current in the accident helicopter type.

Preflight checks and initial training maneuvers were uneventful. During the power recovery phase of a practice autorotation, the flight instructor applied engine power by moving the throttle twist grip from the idle to the flight position; however, the engine did not respond as expected, the rotor rpm decayed, and the helicopter landed hard. The helicopter sustained substantial damage to the tailboom; neither occupant was injured.

Immediately following the hard landing, the flight instructor observed that the rotor rpm was still low and that the amber-colored governor and twist grip warning lights, which should have extinguished during the power recovery, were still illuminated. He manipulated the throttle twist grip multiple times between the idle and flight detents in an attempt to extinguish the lights and increase the rotor speed without success. With the twist grip in the "flight" position, he then reached up and recycled the start selector switch on the roof panel, and the lights extinguished. After the flight instructor exited the helicopter and examined the damage, he got back in the helicopter, and the pilot then shut down the engine.

This was the first training flight (requiring an autorotation with power recovery) since the helicopter manufacturer had issued a service bulletin (SB), which recommended modifying the engine control logic. The SB was issued following multiple reports of engines remaining at idle power during practice autorotation power recoveries despite the twist grip being moved to the "flight" position. Although this was similar to the accident scenario, maintenance records revealed that the SB was accomplished about 46 flight hours before the accident, and postaccident examination revealed that the SB had been complied with correctly.

During the postaccident airframe examination, a small amount of play was observed in the twist grip on the flight instructor's side, which sometimes caused the governor and twist grip amber caution lights to not extinguish when the grip was in the flight detent. Wiggling the twist grip while in the flight detent resolved the issue, which the operator's chief pilot reported was not uncommon throughout the agency's fleet, and the pilots were accustomed to it. The flight instructor did not recall the status of the amber lights during the recovery phase before the hard landing. The flight procedures for autorotation training called for a confirmation that these lights were extinguished during the power recovery phase; however, the chief pilot stated that, given the minimal altitude (70 ft above ground level [agl]) that was recommended by the helicopter's manufacturer to initiate the power recovery, pilots were taught to focus on flying the helicopter and not on the lights.

Ten months after the accident, the helicopter manufacturer issued a safety information notice regarding simulated engine-off landing training, which referenced the high exposure to accidents and incidents during engine-off landings, and issued a series of procedural updates, including advising that power recoveries be initiated as the helicopter passed through 200 ft agl rather than 70 ft agl.

The status of the lights during the maneuver could not be determined; however, if they were illuminated, the engine would have been operating in "mixed" mode and would have exhibited a very slight delay in power recovery. A postaccident engine run revealed that the engine responded within specifications in mixed mode and in a series of other modes under multiple load conditions. Following the run, the engine's hydromechanical unit was removed and tested. It was slightly outside of specification for the "P3" module check, which affected operation in mixed mode. However, because the engine test run was successful, this adjustment variance was not considered causal to the engine providing insufficient power during the accident sequence. Additionally, the engine manufacturer stated that it was not unusual for this module to go out of adjustment in the field.

A failure-mode analysis was performed in an effort to determine why the engine would not resume flight power after the hard landing and whether this was related to the engine's failure to provide sufficient power when commanded by the pilot during the power recovery phase of the practice autorotation. The results revealed that the behavior could be duplicated if the throttle input lever had become declutched from the load limiter inside the hydromechanical unit. However, for this condition to have occurred, the pilots would had to have performed a highly unusual series of nonstandard procedures before the accident. It is also possible that, if declutching occurred, it could have been caused by the hard landing, in which case, it would not explain what happened in the accident. Therefore, the reason that the engine did not provide sufficient power when commanded by the pilot during the power recovery phase of the practice autorotation could not be determined.

Probable cause

The failure of the engine to provide sufficient power when commanded by the pilot during the power recovery phase of a practice autorotation for reasons that could not be determined because postaccident examination revealed no mechanical malfunctions or failures that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14TA370
Event ID
20140909X94230
Case number
WPR14TA370
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2014-09-05.
  • API snapshot SHA-256: c14e10588b182d7edad959b5d17272a74703914c30668f94c3580ee9db60f3db; retrieved 2026-09-16T01:44:22.501Z.