# Incident 20111017030059I: Luscombe 8A, Perryville, KY, October 17, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 17, 2011, 18:20 local time
- Place: Perryville, KY
- Airport: Battle Field
- Damage: Minor damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: General operating rules (Part 91)
- Location: 37.6611° N, 84.9926° W: Placed by OpenAirDocs at Battle Field, closed, within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.6611&lon=-84.9926&mi=10
- Aircraft: N2613K, registered now (https://openairdocs.org/aircraft/N2613K) (OpenAirDocs)
- Registry model: Luscombe 8A (registry code 8190104, https://openairdocs.org/model/luscombe-8a) (OpenAirDocs)
- Registry engine: Continental A&C65 series (registry code 17003, https://openairdocs.org/engine/continental-a-c65-series) (OpenAirDocs)
- Reported make and model: LUSCOMBE 8A
- Reported engine: CONT MOTOR A&C65 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,105 total, 328 in this make and model, 40 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20111017030059I

## Narrative

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

AFTER LANDING AT BATTLE FIELD, A 940 FOOT GRASS AIRFIELD, IN PERRYVILLE, KY, THE PILOT ATTEMPTED TO DEPART AND STRUCK WHAT HE DESCRIBED AS "SOME SAPLINGS" WITH THE LEFT WING OF THE AIRCRAFT.  THE PILOT LOST DIRECTIONAL CONTROL, WHICH RESULTED IN THE AIRCRAFT LEAVING THE RUNWAY AND BEING DAMAGED UPON IMPACT WITH THE SURROUNDING VEGETATION.  THE PILOT PURCHASED THE AIRCRAFT IN 2010, BUT IT WAS STILL REGISTERED TO THE PREVIOUS OWNER AT THE TIME OF THE INCIDENT.  THIS INCIDENT WAS DISCOVERED BY PERSONNEL FROM THE LOUISVILLE FSDO WHILE CONDUCTING AN INVESTIGATION OF LOW FLYING AIRCRAFT IN THE VICINITY OF BATTLE FIELD ON DECEMBER 21, 2011.  THE IDENTITY OF THE PILOT AND THE AIRCRAFT INVOLVED WERE NOT VERIFIED UNTIL JANUARY 10, 2012.  ENFORCEMENT ACTION HAS BEEN INITIATED FOR SEVERAL REGULATORY VIOLATIONS AND REEXAMINATION OF THE PILOT'S COMPETENCY IS BEING CONSIDERED.

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.