LAX01LA030
2000-10-31 · DAYTON VALLEY, Nevada, United States · None · 1 aircraft · Status: Completed
Airport A34
Aircraft involved
Probable cause & findings
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.
Factual 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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_LAX01LA030.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…