Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

September 20, 1998 · Piper PA-28-140 · N5817U

Dayton, NV

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 20, 1998
Injury Outcomes
No injuries (2 uninjured)
Location
Dayton, NV
Aircraft
Piper PA-28-140
Tail Number
N5817U
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX98LA300

The pilot had been flying the airplane the previous week with no discrepancies noted with the airplane or engine. He had flown into the airport the day before the accident and had to refuel the airplane with auto fuel because the airport did not provide aviation fuel. The pilot stated that the airplane had been approved to use auto fuel by an STC. The next morning he conducted a run-up with no discrepancies noted. He stated that the takeoff was normal, but at the departure end of the runway the engine stopped. The engine did not sputter or cough, but the rpm's dropped and the engine became quiet. The pilot turned the airplane to the left and made an unsuccessful attempt to restart the engine. Witness to the accident stated that the airplane appeared to be at full power, but airspeed was low and the airplane was not climbing. Following recovery of the airplane, grade 100LL aviation gasoline was put into a tank and plumbed into the airplane fuel system. During the first attempt to start the engine, it ran rough. A second engine run was conducted with no discrepancies noted. The engine was examined with no discrepancies noted. The fuel that was removed from the airplane during recovery was bright yellow mixed with blue. According to the carburetor icing probability chart, conditions were conducive to serious icing or climb power.

NTSB Probable Cause

Loss of engine power for unknown reasons. Factors were conditions conducive to carburetor icing and the use of automotive fuel.

Full Narrative

On September 20, 1998, at 0745 hours Pacific daylight time, a Piper PA-28-140, N5817U, experienced a loss of engine power after takeoff and impacted terrain near the Dayton Valley Airpark, Dayton, Nevada. The aircraft, operated by the pilot under 14 CFR Part 91, sustained substantial damage. The private pilot and one passenger, the sole occupants, were not injured. Visual meteorological conditions existed for the personal cross-country flight and no flight plan was filed. The flight was scheduled to terminate at the Klamath Falls, Oregon, airport. The pilot stated that he and his wife had flown from Oregon to New Mexico where they had spent the week flying and camping. No discrepancies were noted with the airplane during the trip. The day before the accident they had flown to the Dayton airport and spent the night. The pilot stated that he had to refuel the aircraft with auto fuel from a local gas station, as there were no fuel services located at the airport. He stated that the aircraft was approved by the Federal Aviation Administration (FAA) for auto fuel consumption with Supplemental Type Certificate (STC) SA 1963 GE. The terms of the STC require the pilot/operator to determine that the automotive fuel meets certain specifications prior to use. The pilot stated that auto fuel has been used in the aircraft on prior occasions without difficulty. On the morning of the accident, he stated that he conducted an engine run-up per manufacturer's checklist with no anomalies noted. The pilot stated that he leaned the mixture for the high altitude takeoff and the aircraft was halfway down the runway when he lifted off. The pilot reported that the engine was running with no noted discrepancies. At the departure end of the runway, the engine stopped. The pilot stated that the engine did not cough or sputter, but the rpm's dropped and the engine was very quiet. He stated that he turned the aircraft to the left, and made an unsuccessful attempt to restart the engine with the throttle and mixture full forward. The pilot stated that he set up for an emergency landing and collided with sagebrush off the airport. Witnesses to the accident stated that the aircraft appeared to be "laboring" at full power, but with low airspeed and did not appear to be climbing. The airframe and engine were examined by an investigator from the Safety Board following recovery, and included an engine run, and general and fuel system inspections. The throttle cable was restricted due to damage to the engine during the accident sequence. The spark plugs were inspected, and according to Champion's Aviation Check-A-Plug chart were carbon fouled. Aviation gasoline, grade 100LL, was put into a fuel tank and plumbed into the aircraft fuel lines at the wing root fitting. Using the aircraft systems, the engine was started. During this initial engine run at 1000 rpm's, the engine was rough. On the second engine run at 1700 rpm's, the engine ran with no discrepancies. There was a 50-rpm drop on the magneto check, which is in manufacturer limits. The engine and fuel system was inspected with no discrepancies noted. The carburetor was damaged and could not be tested; however, no discrepancies were noted with the components. A fuel sample removed from the aircraft tanks during disassembly was retained by the recovery company and found to be a bright yellow color mixed with blue. According to the carburetor icing probability chart, conditions at the time of the accident were conducive to serious icing during cruise or climb power.

Flight

Event TypeAccident
Event Time07:45 PDT
Nearest AirportDayton Valley Airpark (0nm S)
Runway0
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-140
Tail NumberN5817U
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 51 · Third Class

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point52 / 43 C
Altimeter29.00 inHg
Observation Time14:56
Weather SourceWFAC

Appendix: Source Data