FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA003 · Piper J3C 65

6 Oct 2018 · Fancy Gap, VA, United States

Piper J3C 65 · Accident: controlled flight into terrain/object (CFIT) en route

From Fayette Airport (WV59) to Twin Lakes Airport (8A7)

Report a problem

Event

NTSB case
ERA19FA003
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 J3C 65

Aircraft type
Piper J3
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
N38811
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fayette Airport (WV59), Fayetteville, WVTo Twin Lakes Airport (8A7), Mocksville, NC
Aircraft age
About 77 years (built 1941)
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
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
Substantial

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The non-instrument-rated private pilot was conducting a visual flight rules (VFR) cross-country flight; instrument meteorological conditions (IMC) were forecast along the route, and the airplane was not equipped for flight in IMC. The pilot had entered a flight plan in the ForeFlight application that noted a cruise altitude of 2,100 ft mean sea level (msl) for the route of flight. Further, the ForeFlight application displayed a terrain cross-section overview which noted that the highest point along the route was 3,800 ft msl and indicated that the planned route and altitude for the flight conflicted with the rising terrain. About 1 hour 15 minutes after departure, the airplane impacted a mountain at 2,766 ft, about 150 ft below the summit. The accident site was about 36 miles from the destination airport along a direct route between the departure and destination airports. Accident site evidence and impact damage to the airplane were indicative of a high-speed impact, with a wreckage path that was oriented roughly opposite to the intended route of flight. Examination of the wreckage revealed no anomalies with the airplane that would have precluded normal operation before the accident.

Weather observations near the departure and destination airports, AIRMETs, and visible satellite weather images all indicated that the pilot likely encountered IMC en route, and based on the direction of the wreckage path relative to the intended route of flight, was likely maneuvering to return to visual meteorological conditions when the airplane collided with terrain. The forecasts warning of IMC were issued prior to the pilot's departure, and while it could not be determined whether the pilot accessed these forecast materials, the flight planning application on his personal electronic device would have allowed him to view this information if an internet connection was available.

Toxicology test results showed that the pilot was taking two antidepressants, indicating that he had significant depression, which can be associated with significant cognitive degradation. The testing also detected the presence of four impairing or sedating medications. The pilot made critical errors in judgment both when he decided to undertake the flight along a route where instrument meteorological conditions were forecast, and when he elected to continue flight after encountering those conditions. It is likely that the combination of his depression and his use of multiple impairing/sedating medications contributed to the pilot's poor decision-making and therefore contributed to the accident.

Probable cause

The non-instrument-rated pilot's improper decision to undertake a flight into forecast instrument meteorological conditions (IMC) and his subsequent decision to continue the flight after encountering IMC, which resulted in controlled flight into terrain. Contributing to the accident were the pilot's depression and use of impairing/sedating medications, which resulted in poor decision-making.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA003
Event ID
20181007X50731
Case number
ERA19FA003
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. 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: 4f313eb173403639aed4ef61f1b61bea9a0a3c4f0a0e4a835842ac5a7b35ab79; retrieved 2026-09-15T06:49:11.730Z.