# Accident 19950816024189A: Cessna 172P, Hesperia, CA, August 16, 1995

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 16, 1995, 14:40 local time
- Place: Hesperia, CA
- Airport: Hesperia Air Lodge Airport
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 34.3599° N, 117.3191° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.3599&lon=-117.3191&mi=10
- Aircraft: N5462K, a cancelled registration (https://openairdocs.org/deregistered/N5462K-2015-05-15) (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
- Reported engine: LYC O320D2J
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 5,920 total, 2,500 in this make and model, 48 in the last 90 days
- NTSB investigation: [NTSB LAX95LA296](https://openairdocs.org/ntsb/LAX95LA296) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19950816024189A

## Narrative

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

LOST POWER. LANDED DOWNWIND DOWN SLOPE. OVERRAN RUNWAY. PULLED UP OVER FENCE. LANDED IN BRUSH. CONNECTING ROD BROKE

## 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 LAX95LA296](https://openairdocs.org/ntsb/LAX95LA296), Aug 16, 1995: Cessna 172P (N5462K), Hesperia, CA, substantial damage. Probable cause: The failure of the connecting rod due to the rod bolt backing off, and the pilot's misjudging the distance and altitude.

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.