FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA105 · Piper PA-32-260

10 Mar 2024 · Madras, OR, United States

Piper PA-32-260 · Accident: VFR encounter with IMC en route

From Aurora State Airport (KUAO) to Caldwell Executive Airport (KEUL)

Report a problem

Event

NTSB case
WPR24FA105
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
2 · 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
Visual Meteorological Cond

Piper PA-32-260

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
N3264W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Aurora State Airport (KUAO), Aurora State Airport, ORTo Caldwell Executive Airport (KEUL), Caldwell, ID
Aircraft age
About 59 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
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The non-instrument-rated pilot departed into visual meteorological conditions (VMC) on a day cross-country flight. A power utility company experienced a powerline surge and dispatched a maintenance crew to investigate; upon arrival they discovered the wreckage of an airplane and alerted local authorities. Flight track data indicated that, after departure, the airplane proceeded on an easterly heading and ascended to 10,000 ft mean sea level (msl) toward the destination airport. The data indicated that the airplane made a series of altitude changes ranging from 10,000 to 13,300 ft msl and made a right descending turn before the recorded data ended. The airplane impacted sloping terrain in between high-power transmission lines. Witnesses near the accident site reported they observed the airplane descending in a spiraling motion toward the ground. They described the engine as getting louder as the airplane descended or winding up like it was in a dive, like aerobatics at an airshow. A witness noted that the airplane was intact while descending. Another witness reported there were rain showers in the area when they heard the engine. Review of weather information at the time of the accident and near the accident location indicated instrument meteorological conditions (IMC), icing conditions, and updrafts and downdrafts from mountain wave development. It is unknown if the pilot obtained a preflight weather briefing. All major structural components of the airplane were located within the wreckage path. Postaccident examination of the airframe and engine revealed no evidence of any preexisting anomalies that would have precluded normal operation. Toxicological testing of the pilot found no tested-for substances or medications that would have posed a hazard to flight safety or that likely would have contributed to the accident. Due to the condition of the remains, the autopsy did not determine whether any medical conditions were present that may have posed a hazard to flight safety or that may have contributed to the accident. The series of altitude changes were consistent with the pilot attempting to avoid IMC. While the satellite and local weather radar did show some altocumulus clouds and scattered echoes in the vicinity of the accident, the accident airplane was not in any significant echoes at the time the pilot lost control. Satellite imagery depicted the accident site covered by an area of mid-level clouds with cloud tops near the accident airplane’s cruising altitude at 12,500 ft msl. Icing is common near cloud tops, and the cloud top temperature supported the presence of supercooled liquid droplets. The sounding also depicted strong vertical wind shear near the cloud tops, which is a common feature with icing in cloud tops. IFR conditions, mountain obscuration, icing conditions, and strong surface winds were forecast for the period of the accident. Based on the flight and weather data, the pilot was likely attempting to overfly the layer of clouds, entered the upper portion of the clouds, then encountered moderate or greater turbulence and structural icing conditions that resulted in his loss of airplane control.

Probable cause

The pilot’s continued visual flight rules flight into instrument meteorological conditions, which resulted in an encounter with turbulence and structural icing conditions, loss of control, and subsequent impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA105
Event ID
20240311193907
Case number
WPR24FA105
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: 6f882dc36ae8b8fb2b4c7699b765435907926777e6e719d55343f5cd1cfc21df; retrieved 2026-09-15T08:11:37.754Z.