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

Beech A36 accident near Tonopah, Nevada, May 30, 2018

On May 30, 2018 at about 6:08 pm local time, a 1979 Beech A36, registered N191HL, was substantially damaged in an accident during enroute (climb to cruise) near Tonopah, Nevada (Tonopah 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 pilot's failure to properly lean the fuel/air mixture and to monitor critical engine parameters during the en route climb to cruise level, which resulted in excessive engine heat and oil starvation and the subsequent catastrophic engine failure.

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

What the record shows

Date
May 30, 2018 · about 6:08 pm local time
Place
Tonopah, Nevada · Tonopah · map
Type
Accident
Injuries
2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Beech A36, built 1979 · all A36s on the register
Registration
N191HL · no longer on the register · serial E-1437
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The private pilot reported that, after the airplane reached about 8,000 ft mean sea level for the personal, cross-country flight, he began to smell smoke and then heard a popping sound. The engine then began to lose power, and he initiated a return to the airport. During the descent, the engine lost all power, and the pilot maneuvered the airplane to land on a highway. Due to obstructions, the pilot subsequently landed the airplane on a highway median. The airplane landed hard, which resulted in substantial damage to the fuselage and wings. Examination of the engine revealed signatures consistent with detonation, which led to the failure of the No. 4 piston, the crankcase becoming pressurized, oil being pumped overboard, and the eventual oil starvation of the engine components. A review of data from the engine data monitor (EDM) revealed that, during the flight that occurred earlier that day, the fuel flows and engine temperatures were appropriate. However, the EDM data for the accident flight revealed that the fuel flow was significantly lower during the takeoff and en route climb portions of the flight and that the cylinder head, turbine inlet, and oil temperatures reached extremely high values. The pilot stated that he could not specifically recall the steps he took to manage the fuel/air mixture during the flight. The low fuel flow recorded on the EDM along with the excessive temperatures suggests that the mixture was set lean. Additionally, following the accident, the mixture control appeared to be leaned for cruise flight, rather than at full rich. However, the aircraft flight manual specified that the fuel mixture should be set to full rich during all operational phases from engine start through cruise climb. Given the evidence, it is likely that the pilot improperly leaned the fuel/air mixture and that he did not adequately monitor critical engine parameters via the cockpit gauges, which led to the high engine temperatures going undetected and resulted in oil starvation and the subsequent catastrophic engine failure.

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. Miscellaneous/other during enroute (climb to cruise)
  2. Loss of engine power (total) during enroute (climb to cruise) defining event
  3. Off-field or emergency landing during landing
  4. Hard landing during landing

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Pilot
  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Incorrect use/operation
  • cause Aircraft › Fluids/misc hardware › Fluids › Oil › Not specified

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 225 hours in all; 99 in this make and model
  • Last flight review: August 20, 2017
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,384 hours
  • Last inspection: annual inspection, May 18, 2018; 3 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Continental Motors IO-520-BB (piston); 3,280 hours total

The flight

  • Departed from: TPH Tonopah NV at 6:48 pm
  • Destination: DDC Dodge City KS
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 37°F (3°C)
  • Altimeter: 29.87 inHg
  • Observation at 5:56 pm from KTPH, 3 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

10 documents, released by the NTSB on September 11, 2019. 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.