The U.S. aircraft register, updated daily
Accidents · NTSB WPR20LA189 · Final report

Aerospatiale SA342J accident near Minden, Nevada, June 21, 2020

On June 21, 2020 at about 8:30 pm local time, a 1979 Aerospatiale SA342J (helicopter), registered N342J, was destroyed in an accident during approach (VFR pattern final) near Minden, Nevada (Minden-Tahoe airport). It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 21, 2020 · about 8:30 pm local time
Place
Minden, Nevada · Minden-Tahoe · map
Type
Accident
Injuries
2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Aerospatiale SA342J 1708, built 1979 · all SA342Js on the register
Registration
N342J · no longer on the register · serial 1708
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Autorotation Hard landing
  2. Loss of engine power (total) during approach (VFR pattern final) defining event

The NTSB's findings

  • Aircraft › Aircraft power plant › Power plant › (general) › Failure
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Attain/maintain not possible
  • Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: multi-engine land; multi-engine sea; single-engine land; rotorcraft: helicopter
  • Flight time: 2,548.9 hours in all; 245.5 in this make and model; 5.1 in the last 90 days; 2.4 in the last 30 days; 2,548.9 as pilot in command
  • Last flight review: January 19, 2019
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: rgt
  • Injury: minor injuries

Passenger

  • Seat: left
  • Injury: minor injuries

The aircraft

  • Last inspection: annual inspection, July 5, 2019
  • Seats: 5
  • Landing gear: fixed
  • Engine: Astazou 14H (turboshaft); 5,274 hours total
  • Fire on the ground

The flight

  • Departed from: CXP Carson City NV at 7:00 pm
  • Destination: MEV Minden NV
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 260° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 90°F (32°C), dew point 25°F (-4°C)
  • Altimeter: 30.06 inHg

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

16 documents, released by the NTSB on September 7, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.