Piper PA-32R-300 accident near Evansville, Indiana, October 30, 2022
On October 30, 2022 at about 6:58 pm local time, a 1977 Piper PA-32R-300, registered N349SB, was substantially damaged in an accident during enroute (cruise) near Evansville, Indiana. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured and 2 people had minor injuries; 1 other was unhurt. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The total loss of engine power for reasons that could not be determined based on the available evidence.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 30, 2022 · about 6:58 pm local time
- Place
- Evansville, Indiana · map
- Type
- Accident
- Injuries
- 1 person was seriously injured and 2 people had minor injuries; 1 other was unhurt.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA-32R-300, built 1977 · all PA-32R-300s on the register
- Registration
- N349SB · registry record · serial 32R-7780480
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was conducting a personal cross-country flight. He performed a preflight inspection, and the takeoff and climb were normal. After flying for about 1 hour 10 minutes, the pilot felt the engine shake and noticed some abnormal indications on the engine monitor. He made some adjustments to the engine controls, and the engine smoothed out and ran normally. A few minutes later, the engine surged momentarily to full power and then returned to its previous power setting. The pilot diverted to a local airport, and the engine operated normally as the airplane descended. During the approach, which was conducted in instrument meteorological conditions (IMC), the engine lost total power when the airplane was about 8 miles from the airport. The pilot attempted to restart the engine but was unsuccessful. The airplane exited the IMC and subsequently landed hard on a golf course, which resulted in substantial damage to the fuselage, both wings, and horizontal stabilizer. Postaccident examination of the airplane and extracted engine data revealed no evidence of mechanical malfunctions or failures with the airplane or engine. Given the available evidence for this accident investigation, the reason for the total loss of engine power could not be determined.
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
- Loss of engine power (total) during enroute (cruise)
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
- Unknown or undetermined during unknown defining event
The NTSB's findings
- Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: airline transport pilot, flight instructor
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 9,923 hours in all; 50 in this make and model; 122 in the last 90 days; 37 in the last 30 days; 1,847 as pilot in command; 92 on instruments
- Last flight review: June 12, 2022
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 7,189 hours
- Last inspection: annual inspection, October 6, 2022; 6.8 hours since
- Maximum gross weight: 3,600 lb
- Seats: 7
- Landing gear: retractable
- Engine: Lycoming IO-540-K1G5D (piston); 5,645 hours total
- Operator: Skyband Aviation, LLC
The flight
- Departed from: TAZ Taylorville IL at 12:48 pm
- Destination: XNX Gallatin TN
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 180° at 3 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 1,100 ft; a few clouds at 1,100 ft
- Temperature: 63°F (17°C), dew point 59°F (15°C)
- Altimeter: 29.92 inHg
- Observation at 1:54 pm from KEVV, 2 miles away
Weather report (METAR): KEVV 301854Z 18007KT 10SM OVC011 17/15 A2992 RMK AO2 SLP130 T01720150 $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
8 documents, released by the NTSB on June 28, 2023. 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 | Aircraft Examination Report | PDF, 4 pages | View Download |
| 2 | Engine Monitor Report - NTSB | PDF, 5 pages | View Download |
| 3 | Engine Monitor Data | data file | Download |
| 4 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - Pilot | PDF, 11 pages | View Download |
| 5 | Pilot Statement | PDF, 3 pages | View Download |
| 6 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - Owner | PDF, 9 pages | View Download |
| 7 | Excerpts of Aircraft Records | PDF, 3 pages | View Download |
| 8 | Photo Array | PDF, 5 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N349SB the same tail number, which may have belonged to a different aircraft at the time
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.