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

February 26, 1999 · Cessna 172P · N99269

Death Valley, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 26, 1999
Injury Outcomes
No injuries (2 uninjured)
Location
Death Valley, CA
Aircraft
Cessna 172P
Tail Number
N99269
Operator
M & S Air Supply
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX99LA109

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.

NTSB Probable Cause

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.

Full 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.

Flight

Event TypeAccident
Event Time13:00 PST
Nearest AirportFurnace Creek (0nm)
Runway33
Runway Length3065 ft
Runway Width70 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172P
Tail NumberN99269
Aircraft CategoryAir
DamageSubstantial
OperatorM & S Air Supply
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-D2J · Reciprocating · 160
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility50 sm
CeilingNone
Temperature / Dew Point70 F / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data