# Incident 19860304011909I: Piper PA18150, Spanish Fork, UT, March 4, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 4, 1986, 13:30 local time
- Place: Spanish Fork, UT
- Airport: Springville
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 40.1132° N, 111.6431° W: Placed by OpenAirDocs: center of Spanish Fork, UT, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.1132&lon=-111.6431&mi=10
- Aircraft: N7615Z, registered now (https://openairdocs.org/aircraft/N7615Z) (OpenAirDocs)
- Registry model: Piper PA-18-150 (registry code 7101828, https://openairdocs.org/model/piper-pa-18-150) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA18150
- Fatal injuries: 0
- Pilot flight hours: 80 total, 60 in this make and model, 15 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19860304011909I

## Narrative

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

BOUNCED ON LANDING, LOSS OF DIRECTIONAL CONTROL FOLLOWED. AIRCRAFT GROUND LOOPED.

## Other reports on N7615Z (2)

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

- [Accident 20030901035599A](https://openairdocs.org/incident/20030901035599A), Sep 1, 2003: Piper PA18150 (N7615Z), Midland, VA, Substantial damage. (-23) After departing horse feathers airport (53VA), while in cruise flight, the engine lost power. As the pilot realized that a landing at the airport would…
- [Accident 19820503013929A](https://openairdocs.org/incident/19820503013929A), May 3, 1982: Piper PA18150 (N7615Z), Marfa, TX, Substantial damage. Instructor claims he could not overpower student during takeoff, aircraft ran through fence at end of runway.

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.