ERA18FA022 · Piper PA32 260
Piper PA32 260 · Accident: VFR encounter with IMC en route
From Everett-Stewart Regional Airport (UCY) to Lake Cumberland Regional Airport (SME)
Event
- NTSB case
- ERA18FA022
- 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
- 4 · 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 PA32 260
- Aircraft type
- Piper PA32
- 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
- N3371W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Everett-Stewart Regional Airport (UCY), Union City, TNTo Lake Cumberland Regional Airport (SME), Somerset, KY
- Aircraft age
- About 52 years (built 1965)
- 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 · cruise
- 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
- VFR encounter with IMC
- 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 › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA18FA022
- Event ID
- 20171112X72518
- Case number
- ERA18FA022
- 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: fe23f4cd69568a07f6db5c85205710a1519f09c9e3f2d30fe62794a5e03d5119; retrieved 2026-09-15T06:24:51.753Z.