Piper PA-32R-301 N43156
11 January 2023 · Dayton, Virginia, United States · Fatal
Summary
On 11 January 2023 at about 23:09 local time, a Piper PA-32R-301 registered N43156 was involved in an accident near Dayton, Virginia, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 23:09
- Classification
- Accident
- Location
- Dayton, Virginia, United States
- Coordinates
- 38.5283, -79.1325
- Aircraft
- Piper PA-32R-301
- Registration
- N43156
- Category
- Airplane
- Year built
- 1983
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Winchester → Alabaster
- Aircraft damage
- Destroyed
- Weather
- IMC
- Light
- Night
- NTSB number
- ERA23FA108
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
Probable cause
The pilot’s controlled flight into terrain while descending over mountainous terrain at night.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Piper PA-32R accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 2 Jul 2023 | Piper PA-32R-300 | North Myrtle Beach, South Carolina, United States | - | Fatal | 5 |
| 1 Jan 2023 | Piper PA-32R-301T | Old Bridge, New Jersey, United States | - | No injuries | - |
| 9 Jun 2023 | Piper PA-32R-301 | Stella Maris, Bahamas | - | Fatal | 1 |
| 10 Feb 2024 | Piper PA-32R-301T | Spanish Fork, Utah, United States | - | Minor injuries | - |
| 9 Jun 2022 | Piper PA-32R-301 | Olla, Louisiana, United States | - | Minor injuries | - |
| 5 Jun 2022 | Piper PA-32R-300 | Gettysburg, South Dakota, United States | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 27 Feb 2023 | Cessna 150G | Hillsville, Virginia, United States | - | Fatal | 1 |
| 5 Aug 2023 | Hughes 369 | Elberon, Virginia, United States | Haverfield International Inc | Serious injuries | - |
| 7 Jan 2023 | Piper PA28 | Suffolk, Virginia, United States | - | Fatal | 2 |
| 30 Nov 2023 | Stinson 108-2 | Martinsville, Virginia, United States | - | No injuries | - |
| 3 Dec 2023 | Beechcraft C23 | Midland, Virginia, United States | - | Fatal | 1 |
| 3 Aug 2023 | Boeing 767-322 | Chantilly, Virginia, United States | United Airlines Inc | Unknown | - |