# Incident 19860305009329I: Piper PA22160, San Luis Obispo, CA, March 5, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 5, 1986, 15:45 local time
- Place: San Luis Obispo, CA
- Airport: San Luis Obispo
- Damage: Minor damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 35.2373° N, 120.6426° W: Placed by OpenAirDocs at SAN LUIS OBISPO COUNTY RGNL (SBP), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.2373&lon=-120.6426&mi=10
- Aircraft: N8830D, a cancelled registration (https://openairdocs.org/deregistered/N8830D-2023-02-15) (OpenAirDocs)
- Registry model: Piper PA-22-160 (registry code 7102214, https://openairdocs.org/model/piper-pa-22-160) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA22160
- Reported engine: LYC O320B2A
- Fatal injuries: 0
- Pilot flight hours: 15,000 total, 100 in this make and model, 255 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19860305009329I

## Narrative

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

ENGINE QUIT AFTER GO AROUND. MADE RUNWAY BUT RAN OFF INTO SOFT DIRT. PROBABLE CARBURETOR ICING.

## Other reports on N8830D (2)

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

- [Accident 20100318029769A](https://openairdocs.org/incident/20100318029769A), Mar 18, 2010: Piper PA-22-160 (N8830D), Mesa, AZ, Substantial damage. On March 18, 2010 at approximately 1658Z (0958 MST), N8830D, a Piper model PA-22 aircraft received substantial damage when it ground looped at Phoenix-Mesa…
- [Incident 19870416018299I](https://openairdocs.org/incident/19870416018299I), Apr 16, 1987: Piper PA22160 (N8830D), San Luis Obispo, CA, Minor damage. Ground looped on landing causing minor damage.

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.