Piper PA-32R-301 accident near Louisville, Kentucky, July 2, 2011
On July 2, 2011 at about 6:30 pm local time, a Piper PA-32R-301, registered N8319N, was substantially damaged in an accident during landing (flare/touchdown) near Louisville, Kentucky (Bowman Field). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper flare and inadequate recovery from a bounced landing, which resulted in a landing gear collapse.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 2, 2011 · about 6:30 pm local time · cases in 2011
- Place
- Louisville, Kentucky · Bowman Field · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32R-301 · all PA-32R-301s on the register
- Registration
- N8319N · registry record · serial 32R-8113029
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot performed a steep descent while on approach, and the airplane touched down on the runway and bounced. The left landing gear collapsed, and the airplane veered off the left side of the runway, where it struck a taxiway sign and sustained substantial damage to its fuselage and both wings. When interviewed after the accident, the pilot did not report experiencing any mechanical malfunctions. However, he subsequently reported that the engine did not respond to a throttle control input after the airplane bounced and that he was not certain whether he experienced any mechanical malfunctions. Examination of the engine did not reveal any preimpact malfunctions. The airplane had been operated for about 20 hours since its most recent annual inspection, which was performed about 4 months prior to the accident.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Hard landing during landing (flare/touchdown) defining event
- Landing gear collapse during landing (flare/touchdown)
- Runway excursion during landing
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 3,800 hours in all; 3,600 in this make and model
- Last flight review: May 30, 2011
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,856 hours
- Last inspection: annual inspection, February 24, 2011; 20 hours since
- Maximum gross weight: 3,600 lb
- Seats: 6
- Landing gear: fixed
- Engine: Lycoming IO-540 SER (piston); 0 hours total
The flight
- Departed from: MLB Melbourne FL at 1:15 pm
- Destination: LOU Louisville KY
- Flight plan: IFR
- Runway 24, 4,326 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 290° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 88°F (31°C), dew point 72°F (22°C)
- Altimeter: 30.09 inHg
- Observation at 6:04 pm from LOU
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
6 documents, released by the NTSB on December 27, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | FAA Inspector Statement | PDF, 2 pages | View Download |
| 3 | Interview Memorandum | PDF, 1 page | View Download |
| 4 | Maintenance Record (Excerpt) | PDF, 1 page | View Download |
| 5 | Photograph # 1 – View of Runway and Airplane as It Came to Rest (Provided by FAA) | PDF, 1 page | View Download |
| 6 | Photograph # 2 – View of Airplane as It Came to Rest (Provided by FAA) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N8319N on the register today · the tail number may have moved to another aircraft since
- Piper PA-32 Cherokee Six, Lance and Saratoga 3,916 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming IO-540 SER 4,223 aircraft carry this series today · as the NTSB recorded it
- Bowman Field · nearest airport
- Melbourne Orlando International · departed from
- Accidents and incidents in Kentucky 702 since 1982 · 111 in the last ten years
- Kentucky 2,981 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA11LA386.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.