# Accident 20170408006199A: Piper PA-22-135, Greensburg, IN, April 8, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 8, 2017, 18:30 local time
- Place: Greensburg, IN
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 39.3510° N, 85.5012° W: Placed by OpenAirDocs: center of Greensburg, IN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.3510&lon=-85.5012&mi=10
- Aircraft: N2389A, a cancelled registration (https://openairdocs.org/deregistered/N2389A-2020-01-24) (OpenAirDocs)
- Registry model: Piper PA-22-135 (registry code 7102206, https://openairdocs.org/model/piper-pa-22-135) (OpenAirDocs)
- Registry engine: Lycoming 0-290 series (registry code 41506, https://openairdocs.org/engine/lycoming-0-290-series) (OpenAirDocs)
- Reported make and model: PIPER PA-22-135
- Reported engine: LYCOMING 0-290 SERIES
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot
- Pilot flight hours: 1,048 total, 48 in this make and model, 48 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170408006199A

## Narrative

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

ON APRIL 8, 2017 AT APPROXIMATELY 1835 EASTERN DAYLIGHT TIME, (EDT) (2235Z) N2389A, A PIPER TRI PACER PA 22-135, CRASHED IN A FIELD WEST OF RUNWAY 36 AT GREENSBURG MUNICIPAL AIRPORT (I34), GREENSBURG INDIANA. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE. THE PILOT RECEIVED MINOR INJURIES AND BOTH PASSENGERS WERE UNINJURED. THERE WERE NO INJURIES ON THE GROUND. THE AIRCRAFT IS REGISTERED TO AND OPERATED BY ^PRIVACY DATA OMITTED^ UNDER 14 CFR PART 91. VISUAL DAYLIGHT CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS ON FILE.  THE FLIGHT DEPARTED UPPER CUMBERLAND REGIONAL AIRPORT IN SPARTA, TENNESSEE ENROUTE TO I34 FOR REFUELING.

THE PILOT STATED THAT HE WAS SLOWING THE AIRCRAFT FOR A STRAIGHT IN APPROACH TO RUNWAY 36 AT GREENSBURG (I34) WHEN THE AIRCRAFT BEGAN TO ROLL TO THE LEFT.  THE PILOT APPLIED FULL RIGHT AILERON AND RIGHT RUDDER WITH NO RESPONSE.  HE APPLIED POWER TO INCREASE AIRSPEED AND THE AIRCRAFT BEGAN TO ROLL WINGS LEVEL. THE PILOT ACCOMPLISHED A 360 DEGREE TURN TO THE LEFT AND REALIGNED WITH THE RUNWAY 36. THE PILOT STATED HE KNEW HE WAS HAVING CONTROL PROBLEMS AND NEEDED TO GET THE AIRCRAFT ON THE GROUND.  HE STARTED TO SLOW THE AIRCRAFT AND IT BEGAN TO ROLL TO THE LEFT AGAIN, DRIFTING LEFT OF THE CENTERLINE OF THE RUNWAY. THE AIRCRAFT IMPACTED THE GROUND IN A FIELD APPROXIMATELY 300 FEET WEST OF THE CENTERLINE OF THE RUNWAY.

THE PILOT INDICATED THAT HE STOPPED FOR FUEL PREVIOUSLY AT LAGRANGE, GA AND SPARTA, TN WITH NO FLIGHT CONTROL PROBLEMS.

THE AILERON-RUDDER INTERCONNECT SYSTEM APEARTED TO BE INTACT DURING INSPECTION.  AIRCRAFT DAMAGE PRECLUDED FURTHER INSPECTION OF THE FLIGHT CONTROL SYSTEM.

## NTSB investigation

None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search

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.