The U.S. aircraft register, updated daily
Accidents · NTSB ERA23FA108 · Final report

Piper PA-32R-301 accident near Dayton, Virginia, January 11, 2023

On January 11, 2023 at about 11:09 pm local time, a 1983 Piper PA-32R-301, registered N43156, was destroyed in an accident during enroute (change of cruise level) near Dayton, Virginia. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot’s controlled flight into terrain while descending over mountainous terrain at night.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 11, 2023 · about 11:09 pm local time
Place
Dayton, Virginia · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-32R-301, built 1983 · all PA-32R-301s on the register
Registration
N43156 · no longer on the register · serial 32R-8313028
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot departed on the visual flight rules (VFR) cross-country flight at night. Shortly after departing, the pilot established the airplane along a course directly toward the destination airport, climbed to a cruise altitude of about 6,500 ft mean sea level (msl), and contacted air traffic control to request flight following services. About 10 minutes later, the pilot advised the controller that he was descending to 5,500 ft msl, and the controller advised the pilot to “maintain VFR.” No further transmissions were received from the pilot. The airplane descended below 4,500 ft and deviated about 20° left of its previously established course. The airplane continued its steady descent until it impacted mountainous terrain at an elevation about 4,000 ft msl. The accident site was located less than 500 ft horizontally and 100 ft vertically from the airplane’s last ADS-B-observed position, and the debris path was oriented roughly along the airplane’s previously established course line. The length of the debris path, impact signatures observed on the wreckage, and the degree of fragmentation of the wreckage were all consistent with a controlled flight into terrain-type impact. Examination of the airframe and engine displayed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. The accident pilot held a private pilot certificate and had accumulated nearly 1,800 total hours of flight experience, but did not hold an instrument rating. Review of forecast and observed weather conditions revealed that light rain and overcast clouds prevailed along the route of flight, and that the airplane many have been flying through light rain showers around the time when the pilot advised air traffic control that he was descending. AIRMETS valid at the time of the accident warned of mountain obscuration, and surface observations from nearby airports confirmed that there was likely an overcast cloud ceiling around 5,000 ft msl in the area; however, based on the available weather information, it could not be determined whether the pilot encountered instrument meteorological conditions (IMC) in flight or was descending in order to avoid IMC when the impact with terrain occurred. Given the night lighting conditions and the lack of ambient cultural lighting available in the area of the accident site, it is likely that the pilot was unable to see the terrain below. Postmortem examination of the pilot’s remains identified no significant natural disease. Toxicology testing detected likely subtherapeutic concentrations of the sedating antihistamine, cetirizine, in his blood; however, side effects from low levels of this over-the-counter allergy medication would not likely influence his decision-making ability or his ability to control the airplane. The pilot’s use of cetirizine was likely not a factor in this 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

  1. Controlled flight into terrain or object (CFIT) during enroute (change of cruise level) defining event

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Response/compensation
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Awareness of condition
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,772 hours in all; 1,693.7 in this make and model; 1,723 as pilot in command
  • Last flight review: August 24, 2021
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 2,894.7 hours
  • Last inspection: annual inspection, June 28, 2022; 165.2 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 7
  • Landing gear: retractable
  • Engine: Lycoming IO-540K1G5D (piston); 2,748 hours total

The flight

  • Departed from: OKV Winchester VA at 10:39 pm
  • Destination: EET Alabaster AL
  • Flight plan: none

Weather at the time

  • Light: night
  • Wind: from 190° at 7 knots
  • Visibility: 7 statute miles
  • Sky: broken clouds at 3,800 ft
  • Temperature: 39°F (4°C), dew point 34°F (1°C)
  • Altimeter: 30.13 inHg
  • Observation at 5:55 pm from KVBW, 13 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

21 documents, released by the NTSB on July 8, 2025. 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.

#DocumentWhat it is
1 Accident Site Diagram PDF, 3 pages · our copy View Download
2 Investigative Photographs PDF, 22 pages · our copy View Download
3 Memorandum for Record - Wreckage Examinations PDF, 4 pages · our copy View Download
4 Electronic Devices - Specialist's Factual Report PDF, 7 pages · our copy View Download
5 Meteorology Factual Report PDF, 23 pages · our copy View Download
6 ATC - Group Chairman's Factual Report PDF, 14 pages · our copy View Download
7 ATC - Attachment 1 - ATC Audio Recording audio View Download
8 ATC - Attachment 2 - ADS-B Data data file · our copy Download
9 ATC - Attachment 3 - FAA Aircraft Accident Package PDF, 78 pages · our copy View Download
10 ATC - Attachment 4 - Interview Transcripts PDF, 311 pages · our copy View Download
11 ATC - Attachment 5 - Facility-event Logs and Records PDF, 35 pages · our copy View Download
12 ATC - Attachment 6 - Facility Admin and Documentation PDF, 458 pages · our copy View Download
13 ADS-B Data (Kmz Format) map file · our copy Download
14 Sectional Aeronautical Chart PDF, 1 page · our copy View Download
15 Pilot's Personal Flight Log (Excerpt) PDF, 1 page · our copy View Download
16 Medical Factual PDF, 3 pages · our copy View Download
17 Toxicological Report PDF, 1 page · our copy View Download
18 Certification of Party Representatives - Lycoming and Piper PDF, 2 pages · our copy View Download
19 Certificate of Party Representative - Natca PDF, 13 pages · our copy View Download
20 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download
21 Evidence Control Documentation PDF, 1 page · our copy View Download

The same 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.