FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20LA189 · Aerospatiale SA342J 1708

21 Jun 2020 · Minden, NV, United States

Aerospatiale SA342J 1708 · Accident: loss of engine power (total) on approach

From Carson Airport (CXP) to Minden-Tahoe Airport (MEV)

Report a problem

Event

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

Aerospatiale SA342J 1708

Aircraft type
Aerospatiale SA342
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
N342J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Carson Airport (CXP), Carson City, NVTo Minden-Tahoe Airport (MEV), Minden, NV
Aircraft age
About 41 years (built 1979)
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 final
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 (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft power plant
  • 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

On the day of the accident, the pilot made a series of personal flights that totaled about 1 hour 15 minutes of flying time. During the last flight, he noticed that the engine was operating about 50° higher than it normally did. Immediately after the pilot lowered the collective to descend for a landing, the engine lost total power. When the helicopter was about 25 ft above ground level and at a speed of 10 to 15 knots, the pilot entered an autorotation to land. The combination of altitude and airspeed did not allow the pilot to establish a stabilized autorotation, and the helicopter landed hard, which resulted in a postaccident fire that consumed most of the helicopter.

Postaccident examination of the engine and transmission revealed no mechanical malfunctions or anomalies that would have precluded normal operation. The airframe was thermally destroyed and could not be thoroughly examined, and the engine did not undergo a full tear down. A witness described hearing “three or four pops” and a loud noise, indicating that the engine had surged before it lost total power.

The pilot purchased the helicopter in 2009. A mechanic maintained the helicopter in accordance with an annual maintenance schedule that was similar to the manufacturer’s periodic maintenance schedule and addressed all the manufacturer’s maintenance requirements, including criteria for engine cleaning. The mechanic performed an engine compressor wash and rinse once a year as part of the annual inspection and not according to the number of hours that the helicopter had been flown. He used a non-approved cleaner and non-de-mineralized drinking water and did not run the engine after rinsing it. According to the manufacturer both the infrequent engine cleaning and the use of non-demineralized water could result in higher exhaust temperatures. The last engine wash occurred in July 1019.

According to the maintenance logbook, the pilot had accrued about 167.8 flight hours in the helicopter from 2011 to 2019. This amount of time throughout the 9-year timeframe likely resulted in multiple downtime periods that exceeded 72 hours and would have required an engine cleaning. The helicopter manufacturer published a service letter about engine condition follow-up checks for aging engines, which included the accident engine. According to the mechanic, the owner had performed at least two of the engine aging follow-up checks in the service letter, but there was no documentation of the results of the checks. The absence of these surveillance data precluded a determination of the engine’s condition before the accident. The manufacturer provided other causes for engine performance degradation including erosion of the air ducts, ingestion of foreign objects, vibrations with rubs leading to an abnormal increase of functional clearances, and unbalance caused by the accumulation of foreign objects. None of these examples were cited in the engine examination report. The cause of the engine surge could not be determined with the available evidence from this investigation.

Probable cause

The total loss of engine power due to a surge; the reason for the surge could not be determined based on available information. Contributing to the helicopter damage was the total loss of power while the pilot was transitioning through an altitude and airspeed combination that did not allow for a stabilized autorotation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20LA189
Event ID
20200622X42619
Case number
WPR20LA189
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, 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: 477bf974bfc54ac01086e0c81fc9867e7924d936ca30c07617956eafdfacca2c; retrieved 2026-09-16T11:54:00.955Z.