# Incident 20020715020689I: Piper PA28181, Miamisburgh, OH, July 15, 2002

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 15, 2002, 20:00 local time
- Place: Miamisburgh, OH
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 39.6309° N, 84.2707° W: Placed by OpenAirDocs: center of Miamisburg, OH, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.6309&lon=-84.2707&mi=10
- Aircraft: N2566U, registered now (https://openairdocs.org/aircraft/N2566U) (OpenAirDocs)
- Registry model: Piper PA-28-181 (registry code 7102807, https://openairdocs.org/model/piper-pa-28-181) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA28181
- Reported engine: LYC O360A4M
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 2,312 total, 500 in this make and model, 5 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020715020689I

## Narrative

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

(-23) AIRCRAFT WAS IN A HOLDING PATTERN AT 3000 FEET AGL WHEN PIC NOTICED THAT THE ENGINE WAS BEGINNING TO RUN ROUGH AND A BAD VIBRATION. THE PIC CUT THE FUEL TO THE ENGINE AND LOCATED A LARGE BEAN FIELD TO LAND IN. NO DAMAGE WAS CAUSED TO THE AIRCRAFT BECAUSE OF THE FORCED LANDING. PRELIMINARY FINDINGS ARE THAT THE NUMBER 3 CYLINDER FAILED IN FLIGHT.

## Other reports on N2566U (1)

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

- [Incident 19990604014789I](https://openairdocs.org/incident/19990604014789I), Jun 4, 1999: Piper PA28161 (N2566U), Banner Elk, NC, Minor damage. Pilot prepared for landing on runway 30 at the Elk River Airport. Pilot overshot runway and first touchdowned approximately 1,000 feet from end of runway. The…

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.