Piper PA-32R-300 accident near Charlottesville, Virginia, December 10, 2006
On December 10, 2006 at about 6:28 pm local time, a Piper PA-32R-300, registered N8349C, was destroyed in an accident near Charlottesville, Virginia (Charlottesville-Albemarle airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 10, 2006 · about 6:28 pm local time
- Place
- Charlottesville, Virginia · Charlottesville-Albemarle · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32R-300 · all PA-32R-300s on the register
- Registration
- N8349C · no longer on the register · serial 32R-7680098
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While on approach to the destination airport, the pilot reported to the air traffic control tower controller that, "his engine was out," but that he was going to try to land at the airport. The pilot was subsequently cleared to land on runway 3, and responded, "I don't know if I can make it there." A witness, who was the pilot of an emergency services (EMS) helicopter, heard communications on the tower frequency regarding an airplane in distress, and followed the airplane to provide assistance. The witness noted that the airplane was "extremely low," and the propeller was not turning. The aircraft cleared a tree line about 200 yards south of the crash site and continued descending into a clearing. Several seconds later, the airplane entered an approximate 20 degree bank to the left, impacted trees and "exploded." An open field was noted adjacent to the wooded area, which the airplane impacted. The engine was completely disassembled after the accident and no pre-impact anomalies were observed. The engine accessories were all severely fire-damaged and could not be tested. Examination of the engine logbook revealed the engine was 511 hours and approximately 1 year past the engine manufacturer's recommended time between overhauls.
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
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 213 hours in all
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: unk
- Injury: fatal
The aircraft
- Airframe total time: 4,645 hours
- Last inspection: annual inspection, July 1, 2006
- Landing gear: retractable
- Engine: Lycoming TIO-540 (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: FCI Richmond VA
- Destination: CHO Charlottesville VA
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 190° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 57°F (14°C), dew point 21°F (-6°C)
- Altimeter: 30.37 inHg
- Observation at 5:53 pm from CHO
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
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.