# Incident 19861125070219I: Cessna 172P, Fresno, CA, November 25, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 25, 1986, 13:30 local time
- Place: Fresno, CA
- Airport: Fresno Air Terminal
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 36.7477° N, 119.7724° W: Placed by OpenAirDocs: center of Fresno, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.7477&lon=-119.7724&mi=10
- Aircraft: N65813, registered now (https://openairdocs.org/aircraft/N65813) (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: 1
- Fatal injuries: 0
- Pilot flight hours: 160 total, 70 in this make and model, 20 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19861125070219I

## Narrative

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

DETERIORATING WEATHER CAUSED VFR PILOT TO REQUEST LANDING ASSISTANCE. PILOT NOT FAMILIAR WITH RADIO LIGHT SWITCH.

## Other reports on N65813 (2)

Matched to the same aircraft by N-number and date.

- [Incident 20190702008839I](https://openairdocs.org/incident/20190702008839I), Jul 2, 2019: Cessna 172P (N65813), Corvallis, OR, Minor damage. Pilot in command lost control of the CE-172 airplane during a planned touch and go maneuver on runway 35 at Corvallis Municipal Airport (kcvo). The airplane…
- [Accident 20150430006549A](https://openairdocs.org/incident/20150430006549A), Apr 30, 2015: Cessna 172P (N65813), Pacoima, CA, Substantial damage. The accident occurred during the student pilot?s first solo flight. The student flew with the flight instructor for about one hour the day of the accident.…

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.