# Accident 19961015032379A: Cessna 172P, Kingsburg, CA, October 15, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 15, 1996, 10:05 local time
- Place: Kingsburg, CA
- Damage: Destroyed
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 36.4809° N, 119.5001° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=36.4809&lon=-119.5001&mi=10
- Aircraft: N6187K, a cancelled registration (https://openairdocs.org/deregistered/N6187K-2002-08-05) (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
- Fatal injuries: 0
- Pilot flight hours: 70 total, 70 in this make and model, 70 in the last 90 days
- NTSB investigation: [NTSB LAX97LA018](https://openairdocs.org/ntsb/LAX97LA018) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19961015032379A

## Narrative

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

AT CRUISE ROUGH ENGINE OIL ON SHIELD LOST POWER. HIT TREE AND BUILDING LANDING. PISTON SKIRT FAILED. THRU A ROD.

## 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 LAX97LA018](https://openairdocs.org/ntsb/LAX97LA018), Oct 15, 1996: Cessna 172P (N6187K), Kingsburg, CA, destroyed. Probable cause: the student pilot's use of an excessively lean mixture, which led to engine overheating, detonation, subsequent failure of the number 2 piston, and a forced landing.

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.