LAX99LA109
1999-02-26 · DEATH VALLEY, California, United States · None · 1 aircraft · Status: Completed
Airport L06
Aircraft involved
Probable cause & findings
The pilot's use of an excessive approach reference speed and his misjudged distance/speed relationship to the runway, which resulted in a landing overrun. The pilot's failure to execute a timely go-around was also causal.
Factual narrative
On February 26, 1999, at 1300 hours Pacific standard time, a Cessna 172P, N99269, collided with plastic posts during a landing overrun and came to rest inverted at the departure end of runway 33 at the Furnace Creek Airport, Death Valley, California. The aircraft, operated by Security Aviation and rented by the pilot under 14 CFR Part 91, sustained substantial damage. The private pilot and passenger were not injured. Visual meteorological conditions existed for the personal flight and a visual flight rules (VFR) flight plan was filed. The flight originated at the Hawthorne, California, airport the day of the accident, with intermediate stops in Jean, Nevada, and three stops in California; Shoshone airport, Stovepipe Wells, and Furnace Creek. The flight's ultimate destination was a return back to the Hawthorne airport. The pilot reported the accident to the Safety Board on March 1, 1999. In an interview, the pilot stated that he and his passenger had landed at three other airports without difficulty. The pilot reported that the weather conditions were clear sky, calm winds, and an approximate temperature of 65 degrees Fahrenheit. The pilot reported that he overflew the airport to check the windsock and runway. He stated that he saw what appeared to be a "piece of old runway pavement at the north end of [runway] 33," and thought it was an overrun area. The pilot reported that no problems were encountered during the approach. He did note that on the landing he "was a bit long when I flared." The pilot reported that the aircraft seemed to float more than usual down the runway, and that without visual references, he allowed himself to accept an excessively long float before touchdown. After touchdown, on the 3,065-foot-long runway, he observed that there was not enough runway left to stop or attempt a go-around. He applied brakes and skidded on the runway, but was unable to stop. The aircraft struck plastic posts at the end of the runway and nosed over in the soft dirt. The pilot reported no mechanical anomalies with the aircraft. The pilot overflew the runway to check the windsock and runway and saw what appeared to be an overrun area at the departure end of the runway. He reported that the landing flare was long and the aircraft seemed to float down the runway and was more than half way down the runway before initial touchdown. The pilot stated that lack of visual references and his belief that there was an overrun area led him to accept the excessive float during the landing. After touchdown he noted that there was not enough runway left to attempt a go-around. He applied brakes, but was unable to stop the aircraft before it struck plastic posts at the end of the runway and continued into an area of soft dirt, where the airplane nosed over. The pilot reported that the weather conditions were clear sky, calm winds, and an approximate temperature of 65 degrees Fahrenheit, and no mechanical anomalies were noted. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_LAX99LA109.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…