FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR16LA019 · American Eurocopter LLC AS350B3

24 Oct 2015 · Folsom, CA, United States

Placer County Sheriff's Department American Eurocopter LLC AS350B3 · Accident: loss of control in flight during landing

From McClellan Airfield (MCC) to Auburn Municipal Airport (AUN)

Report a problem

Event

NTSB case
WPR16LA019
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

American Eurocopter LLC AS350B3

Aircraft type
Eurocopter AS350
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
N911WL
Onboard fatalities
Unknown
Route
From McClellan Airfield (MCC), Sacramento, CATo Auburn Municipal Airport (AUN), Auburn, CA
Aircraft age
About 7 years (built 2008)
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 control in flight
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

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The purpose of the public helicopter flight was to perform a patrol mission with a tactical flight officer onboard, while the flight instructor also trained the pilot under instruction (PUI), who had recently been hired by the sheriff's department. The plan was to perform a routine patrol mission to introduce the PUI to the operation of the helicopter's systems, then practice autorotations, which the PUI had not previously performed in the accident helicopter make and model.

After the patrol, they practiced a series of uneventful autorotations over flat areas. They then conducted an autorotation to a pinnacle in the middle of a peninsula. The flight instructor was flying the helicopter throughout the maneuver; during the power recovery phase of the autorotation, he applied engine power by moving the throttle twist grip from the idle to the flight position as the helicopter passed through 100 ft. The engine did not respond as he expected, and, unable to reach the pinnacle, he maneuvered the helicopter to a forced landing on downsloping terrain. The helicopter landed hard and tipped forward, resulting in substantial damage to the tailboom and aft fuselage structure. Postaccident examination of the engine and airframe did not reveal any anomalies that would have precluded normal operation, and the engine met its nominal performance parameters during a subsequent test run.

The helicopter's flight manual recommended that autorotation training be conducted within gliding distance of a suitable running landing area. The flight instructor's choice of a raised landing area, which was surrounded by soft and rocky downsloping terrain, did not represent a suitable area for such practice. Additionally, the slope did not allow a sufficient maneuvering envelope for the appropriate control inputs required to safely control the helicopter in the event of a delayed engine response or loss of engine power. Also, although physically close to a town, the location was relatively remote, because accessing the site by road would have required a long on- and off-road drive by first response vehicles around the lake. Therefore, the chosen location placed the crew in additional danger should a more serious accident have occurred.

About 3 months before the accident, the helicopter manufacturer issued a safety information notice regarding the high exposure to accidents and incidents during simulated engine-off landing training. The notice issued a series of procedural updates, including a recommendation that minimal crew be onboard, and that power recoveries should be initiated as the helicopter passed through 200 ft above ground level (agl) rather than 70 ft agl, as recommended in the flight manual. The notice reiterated the need to be prepared to conduct an engine-off landing if power recovery was unsuccessful, along with the reminder that a higher gross weight increases the risk of a hard landing. Therefore, the flight instructor's choice of a power recovery initiation altitude (100 ft) lower than recommended left him with a reduced margin for recovery when the anomaly occurred. Further, the decision to keep the tactical flight officer onboard during the autorotation portion of the training represented an unnecessary risk both to him and the mission. The helicopter was loaded near its maximum gross weight, increasing the risk of a hard landing.

The flight instructor did not hold a valid medical certificate at the time of the accident due to a recent Type 1 diabetes diagnosis. However, as a public operation, the sheriff's department was responsible for oversight of its own operation and allowed the instructor to fly with another pilot present. The instructor was not exhibiting any symptoms of the condition, and there was no evidence to suggest his diagnosis contributed to the outcome of the accident.

Probable cause

The flight instructor's failure to perform simulated engine failure training in accordance with manufacturer guidance, including his improper recovery from the maneuver, which resulted in an overshoot of the intended landing zone when the engine did not respond as expected; his selection of an unsuitable landing area; and his decision to perform the maneuver near the helicopter's maximum gross weight, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR16LA019
Event ID
20151029X24739
Case number
WPR16LA019
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. 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: 0c44fc6f8d5f798fe3ce209f724d52f0c2ceed0528cb7e108029eeaaff9830cf; retrieved 2026-09-16T02:56:02.596Z.