Piper PA 23-250 accident near Danville, Virginia, March 27, 2016
On March 27, 2016 at about 8:36 pm local time, a 1970 Piper PA 23-250, registered N22AM, was substantially damaged in an accident during enroute near Danville, Virginia. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 3 others were unhurt. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot’s improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 27, 2016 · about 8:36 pm local time
- Place
- Danville, Virginia · map
- Type
- Accident
- Injuries
- 1 person had minor injuries; 3 others were unhurt.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA 23-250 250, built 1970 · all PA 23-250s on the register
- Registration
- N22AM · registry record · serial 27-4501
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The instrument-rated private pilot departed in instrument meteorological conditions (IMC) with the intention of flying visual flight rules (VFR) to his destination. About 90 minutes into the flight, the pilot advised air traffic control (ATC) that he was having problems with the right engine. The pilot switched fuel tanks, turned on the fuel pumps, and restored power to the right engine. A few minutes later, the pilot stated that he was in IMC and requested assistance. While diverting to another airport, the pilot reported to ATC that he had lost power in both engines. The pilot performed a forced landing on a highway, during which the airplane impacted a tree and came to rest inverted next to the road. No fuel was observed in any of the airplane's fuel tanks during the on-scene examination, nor did the accident site display any signs of fuel spillage or blight. Other that the absence of fuel, no evidence of any preimpact mechanical anomalies were noted with the engines that would have precluded normal operation, and it is likely that the loss of power to both engines was the result of fuel exhaustion.
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
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
- Fuel exhaustion during enroute defining event
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level
- cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 2,200 hours in all
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Last inspection: annual inspection, March 11, 2016
- Seats: 6
- Landing gear: retractable
- Engine 1: Lycoming TI0-540 SER (piston); 0 hours total
- Engine 2: Lycoming TI0-540 SER (piston); 0 hours total
The flight
- Departed from: CHS Charleston SC at 5:30 pm
- Destination: MTN Baltimore MD
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 080° at 5 knots
- Visibility: 9 statute miles
- Sky: overcast at 400 ft
- Temperature: 55°F (13°C), dew point 54°F (12°C)
- Altimeter: 30.13 inHg
- Observation at 8:53 pm from KDAN, 14 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
8 documents, released by the NTSB on July 16, 2018. 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 | Record of Conversation - Pilot | PDF, 1 page | View Download |
| 2 | Record of Conversation - Passenger | PDF, 1 page | View Download |
| 3 | radar Plot | PDF, 1 page | View Download |
| 4 | Air Traffic Control Transcripts | PDF, 50 pages | View Download |
| 5 | Photo Array | PDF, 2 pages | View Download |
| 6 | Mechanic Statement | PDF, 1 page | View Download |
| 7 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 8 | Fuel Totalizer | PDF, 6 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
