# Accident 19990226013409A: Cessna 172P, Death Valley, CA, February 26, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 26, 1999, 13:00 local time
- Place: Death Valley, CA
- Airport: Death Valley Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 36.6009° N, 116.8305° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=36.6009&lon=-116.8305&mi=10
- Aircraft: N99269, a cancelled registration (https://openairdocs.org/deregistered/N99269-2013-08-13) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 336 total
- NTSB investigation: [NTSB LAX99LA109](https://openairdocs.org/ntsb/LAX99LA109) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990226013409A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THE AIRCRAFT OVERSHOT THE RUNWAY, CAME TO REST IN SOFT SAND AND FLIPPED OVER. AIRCRAFT REMOVED FROM SCENE PRIOR TO ARRIVAL OF INVESTIGATION.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX99LA109](https://openairdocs.org/ntsb/LAX99LA109), Feb 26, 1999: Cessna 172P (N99269), Death Valley, CA, substantial damage. 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…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.