# Accident 19901226056149A: Cessna 172N, Yucca Valley, CA, December 26, 1990

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 26, 1990, 13:50 local time
- Place: Yucca Valley, CA
- Airport: Yucca Valley Airport
- Damage: Substantial damage
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 34.1494° N, 116.4109° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.1494&lon=-116.4109&mi=10
- Aircraft: N5258D, a cancelled registration (https://openairdocs.org/deregistered/N5258D-1993-04-01) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYC O320H2AD
- Fatal injuries: 0
- Pilot flight hours: 77 total, 44 in this make and model, 41 in the last 90 days
- NTSB investigation: [NTSB LAX91LA060](https://openairdocs.org/ntsb/LAX91LA060) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19901226056149A

## Narrative

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

TRIED TO LAND DOWNWIND THEN ELECTED GO AROUND,DUMPED FLAPS BY MISTAKE. PUT BACK DOWN,STALLED,IMPACTED. FLIPPED OVER

## 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 LAX91LA060](https://openairdocs.org/ntsb/LAX91LA060), Dec 26, 1990: Cessna 172N (N5258D), Yucca Valley, CA, substantial damage. Probable cause: THE PILOT'S IMPROPER USE OF THE FLAPS. CONTRIBUTING TO THIS ACCIDENT WAS THE LOSS OF CONTROL DURING TAILWIND LANDING, AND HIS TAILWIND AND THE PILOT'S INADEQUATE INFLIGHT PLANNING.

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.
