FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23FA108 · Piper PA-32R-301

11 Jan 2023 · Dayton, VA, United States

Piper PA-32R-301 · Accident: controlled flight into terrain/object (CFIT) en route

From Winchester Regional Airport (OKV) to Shelby County Airport (EET)

Report a problem

Event

NTSB case
ERA23FA108
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Piper PA-32R-301

Aircraft type
Piper PA-32
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N43156
Operator
Unknown
Onboard fatalities
Unknown
Route
From Winchester Regional Airport (OKV), Winchester, VATo Shelby County Airport (EET), Alabaster, AL
Aircraft age
About 40 years (built 1983)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · change of cruise level
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

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.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23FA108
Event ID
20230112106565
Case number
ERA23FA108
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 91e6a7f5242a042591016979a22fdde1181ec0ec6e9f9c880ea86f0381b48741; retrieved 2026-09-15T07:55:55.855Z.