Piper PA-23 accident near Rochester, Minnesota, June 17, 2010
On June 17, 2010 at about 4:52 am local time, a Piper PA-23, registered N7SE, was substantially damaged in an accident during enroute (cruise) near Rochester, Minnesota (Rochester International Airpor airport). It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of engine power and the pilot's subsequent loss of control for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 17, 2010 · about 4:52 am local time
- Place
- Rochester, Minnesota · Rochester International Airpor · map
- Type
- Accident
- Injuries
- 3 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-23 · all PA-23s on the register
- Registration
- N7SE · registry record · serial 23-1127
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During the night flight, the pilot reported a loss of engine power to air traffic controllers and requested assistance locating the nearest airport. About 18 nautical miles from the airport, the pilot stated to the controllers that the twin engine airplane's left engine had lost power and that he was attempting to maintain altitude. Later, the pilot stated that he was unsure if he would be able to make the airport. The airplane impacted trees and terrain about a mile from the runway. A postaccident examination of the airplane disclosed no anomalies that would explain the loss of engine power.
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) defining event
- Collision with terrain or object (not controlled flight into terrain) during maneuvering
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land
- Flight time: 259 hours in all
- Last flight review: October 3, 2009
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 3,500 lb
- Seats: 4
- Landing gear: retractable
- Engine 1: Lycoming 0-320-A1A (piston); 0 hours total
- Engine 2: Lycoming 0-320 SERIES (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: FCM Minneapolis MN at 4:15 am
- Destination: FCM Minneapolis MN
- Flight plan: none
Weather at the time
- Light: night
- Wind: from 120° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 64°F (18°C), dew point 61°F (16°C)
- Altimeter: 30.02 inHg
- Observation at 4:54 am from RST, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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.