# Incident 19860410027549I: Piper PA32R301T, El Cajon, CA, April 10, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 10, 1986, 20:02 local time
- Place: El Cajon, CA
- Airport: Gillespie
- Phase of flight: Initial Approach-IFR
- Operating rules: Air taxi and commuter (Part 135)
- Operator: LAAA
- Location: 32.8262° N, 116.9724° W: Placed by OpenAirDocs at GILLESPIE FLD (SEE), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.8262&lon=-116.9724&mi=10
- Aircraft: N8197W, registered now (https://openairdocs.org/aircraft/N8197W) (OpenAirDocs)
- Registry model: Piper PA-32R-301T (registry code 7103220, https://openairdocs.org/model/piper-pa-32r-301t) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32R301T
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 17,089 total, 40 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/19860410027549I

## Narrative

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

INSTRUMENT FLIGHT CONDUCTED WITHOUT ACCOMPLISHING AN IFR PART 135 COMPETENCY CHECK.

## Other reports on N8197W (2)

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

- [Accident 20130519008699A](https://openairdocs.org/incident/20130519008699A), May 19, 2013: Piper PA-32R-301T (N8197W), Chandler, AZ, Substantial damage. On 5/19/2013 at 1330, a Piper PA-32R, N8197W, experienced a mechanical irregularity while en-route from brown field san diego California to phoenix ?mesa…
- [Accident 20000612009199A](https://openairdocs.org/incident/20000612009199A), Jun 12, 2000: Piper PA32R301T (N8197W), Wauseon, OH, No damage. (-23) On June 12, 2000, aviation safety inspectors kris palcho (op's), kenneth shauman (a/w), and david pesarchick (avionics) of the cleveland flight standards…

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.