VFR into IMC · NTSB ERA18FA022

PIPER PA32 — Fountain Run, KY

4 fatal Low-time pilotIMC
DateNovember 12, 2017
LocationFountain Run, KY
AircraftPIPER PA32
Purpose of flightPersonal
ConditionsDay · Instrument Meteorological Cond
Phase / occurrenceEnroute-cruise Loss of visual reference
Pilot age41
Pilot total time256 hrs · Low time
Time in type247 hrs
Fatalities4

Probable cause

The noninstrument-rated pilot's intentional visual flight rules flight into instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation. Contributing to the accident was the pilot's self-induced pressure to complete the flight.

NTSB findings

  • Environmental issues-Conditions/weather/phenomena-Ceiling/visibility/precip-Clouds-Decision related to condition - C
  • Environmental issues-Conditions/weather/phenomena-Ceiling/visibility/precip-Clouds-Effect on personnel - C
  • Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
  • Personnel issues-Psychological-Perception/orientation/illusion-Spatial disorientation-Pilot - C
  • Aircraft-Aircraft oper/perf/capability-Performance/control parameters-(general)-Not attained/maintained - C
  • Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • Personnel issues-Psychological-Personality/attitude-Motivation/respond to pressure-Pilot - F

What happened

The noninstrument-rated private pilot did not obtain an official weather briefing or file a flight plan before departing on the cross-country flight with three passengers. About 55 minutes into the flight, while cruising at 5,500 ft and receiving visual flight rules (VFR) flight following services from air traffic control, the pilot advised the controller that he was climbing the airplane to "maintain VFR." Six minutes later, after completing a series of erratic turns between 6,600 and 7,200 ft, the pilot advised the controller that he had encountered instrument meteorological conditions (IMC) and requested vectors to an altitude with "more visibility." The controller advised that the cloud tops were reported about 8,000 ft, and the pilot stated that he would climb the airplane to that altitude; however, the airplane did not begin a climb. Instead, the airplane's radar track showed a series of shallow left and right turns before it depicted a sharp, tightening right turn and a rapid descent before radar contact was lost in the area of the accident site. Postaccident examination of the wreckage revealed no evidence of fire, no pre-impact mechanical anomalies, and a distribution that was consistent with an in-flight breakup.

One witness near the accident site described seeing the airplane as it appeared from beneath the clouds in a vertical descent, heard a "pop," and then watched as the airplane "just blew apart" before it disappeared from view behind trees. The witness stated that the weather at the time of the accident was "solid fog."

It is likely that the pilot's decision to continue the flight into deteriorating weather conditions resulted in his loss of airplane control due to spatial disorientation. The restricted visibility and entry into IMC were conducive to the development of spatial disorientation, and the airplane's erratic flight track, which included altitude and directional changes inconsistent with progress toward the destination, the rapidly descending right turn depicted on radar, and the in-flight breakup are all consistent with the known effects of spatial disorientation.

Despite not being instrument rated, the pilot chose to continue along the flight route as weather conditions deteriorated, rather than diverting, consistent with a common behavioral trap known as "get-there-it is." The spouse of one passenger had planned a surprise party for the afternoon of their return. It is likely that the pilot's desire to get to the destination airport because of the party or another unknown reason contributed to this behavior.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →