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

November 1, 2000 · Piper PA-32R-301 · N8139A

Dayton Valley, NV

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 1, 2000
Injury Outcomes
No injuries (2 uninjured)
Location
Dayton Valley, NV
Aircraft
Piper PA-32R-301
Tail Number
N8139A
Operator
Union Flights
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX01LA030

While attempting to land, the airplane collided with desert brush short of the runway, shearing off the nose landing gear, damaging both wings, and twisting the fuselage. Arrival at the airport was after sunset. The airport does not have runway lights available for night flights. The pilot indicated that he oriented himself to the runway utilizing the surrounding ground lighting and lights from the company's open hangar. On final approach during the first landing, the pilot initiated a go-around because he was not set up properly and did not like the visual reference of the approach. On the second approach, he lined up with what he believed was the centerline of the runway. He looked down to verify that the landing gear extended lights were illuminated. When he looked back outside, his vision was obscured. Another go-around was initiated; however, the airplane touched down. The pilot heard a loud noise and then saw the desert brush. The pilot reported there were no mechanical anomalies with the airplane. Official sunset was at 1703.

NTSB Probable Cause

The pilot's failure to attain a proper glide path during the final approach resulting in an undershoot of the runway. Factors were the lack of runway lights and night lighting condition.

Full Narrative

On October 31, 2000, at 1746 hours Pacific standard time, a Piper PA-32R-301, N8139A, undershot the runway and collided with desert brush at the Dayton Valley Airpark Airport, Dayton Valley, Nevada. The airplane, operated by Aero Leasing, d.b.a. Union Flights, under the provisions of 14 CFR Part 91, sustained substantial damage. The commercial pilot and pilot rated passenger were not injured. Visual meteorological conditions prevailed for the business flight that departed the Redding Municipal Airport, Redding, California, at 1645, and no flight plan was filed. The flight was scheduled to terminate at the Dayton Valley Airpark. In an interview with a Safety Board investigator, the pilot stated that he and the passenger, who is a mechanic for Union Flights, had flown to Redding earlier in the day to work on a company airplane. No abnormalities were noted on the flight to Redding or the return trip to Dayton. He noted that the arrival to Dayton was after sunset, and reported that the airport does not have lighting. In the pilot's written statement to the Safety Board, he reported that he oriented himself to runway 23 utilizing the surrounding ground lighting and lights from the company's open hangar. He indicated that he did not like what he saw on the first approach and initiated a go-around. On final for the second approach, at 200 feet above ground level (agl), he verified that there was a three green light indication on the instrument panel, confirming that the landing gear was in the down and locked position. When he looked outside he stated that the "lights were fuzzy and not sharp." He thought he had flown through a dust cloud. The next thing he remembered was the passenger stating that they had just crashed. The pilot further reported that the weather was clear and the winds were calm. According to a Sun and Moon program utilized by the Safety Board, official sunset was 1703.

Flight

Event TypeAccident
Event Time17:46 PST
Nearest AirportDayton Valley Airpark (0nm)
Runway23
Runway Length5351 ft
Runway Width75 ft
Flight Plan FiledCvfr
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32R-301
Tail NumberN8139A
Aircraft CategoryAir
DamageSubstantial
OperatorUnion Flights
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-540-K165D · Reciprocating · 300
Seats6

People & Injuries

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

Conditions

ConditionsVMC
LightDusk
Wind330° @ 6 kt
Visibility10 sm
CeilingBroken clouds 25000 ft
Temperature / Dew Point12 C / 66 F
Altimeter30.00 inHg
Observation Time01:56
Weather SourceWFAC

Appendix: Source Data