The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB WPR24FA257 · Final report

Pilatus Aircraft LTD PC-12/47E accident near Recluse, Wyoming, July 26, 2024

On July 26, 2024 at about 7:04 pm local time, a 2010 Pilatus Aircraft LTD PC-12/47E, registered N357HE, was destroyed in an accident during maneuvering near Recluse, Wyoming. It was a personal flight under general aviation rules (Part 91). 7 people were killed. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The pilot’s loss of control due to spatial disorientation while operating in instrument meteorological conditions, which resulted in an in-flight breakup. Contributing to the accident was the pilot’s distraction from the autopilot disconnecting due to an updraft from convective activity.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 26, 2024 · about 7:04 pm local time
Place
Recluse, Wyoming · map
Type
Accident
Injuries
7 people were killed.
Weather
visual conditions (good weather)
Aircraft
Pilatus Aircraft LTD PC-12/47E, built 2010
Registration
N357HE · registry record · serial 1203
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot and six passengers departed on a cross-country flight on an instrument flight rules (IFR) flight plan with a planned refueling stop in Montana. The airplane flew on a northwest course consistent with its planned destination. The airplane leveled off at a maximum cruise altitude of about 26,000 ft mean sea level (msl). Satellite imagery indicated that, at the accident site about the time of the accident, cumulus cloud bases were about 10,000 ft msl with rain showers; and the cloud tops were about 28,500 ft msl. The sounding model indicated trace to light icing with a low probability of supercooled large droplets (SLD) along about the last 20 minutes of the airplane’s flight path. The accident airplane was equipped for flight into known icing conditions and likely would not accumulate much, if any, structural icing from trace to light icing. Additionally, SLDs were likely not a factor given their low probability of occurrence and the flight profile of the accident airplane during the last few minutes of flight. During the last portion of the flight, about 15 seconds before the airplane entered an area of precipitation as depicted by weather reflectivity charts, the pilot reported a loss of the autopilot and declared an emergency to the air route traffic control center controller. The controller asked the pilot where he would like to land and the pilot responded that he was trying to get control of the airplane; the controller told the pilot to advise if he required additional assistance. The controller then relayed the minimum IFR altitude and current altimeter setting with no further response from the pilot. Data indicate that shortly after entering the area of precipitation, the airplane maneuvered to the right of course, climbed to about 26,525 ft msl, and entered a 270° right turn. In the first 180° of the turn, the airplane descended to about 25,250 ft msl; however, it climbed to about 27,025 ft msl in the last 90° of the turn. Shortly after, the data showed the airplane made a slight left turn before it began a descending 180° right turn. The last data point showed the airplane on a southerly heading, at an altitude of about 21,900 ft msl, and with a groundspeed of 256 knots. Sound modeling data indicate that rain shower or thunderstorm activity had the potential for an updraft speed of up to 3,346 ft/min. ADS-B data indicated that the autopilot disconnected a few seconds after the airplane encountered the precipitation, likely when the airplane encountered an updraft because the autopilot was unable to counteract an updraft of the strength indicated by the modeling data. The airplane was likely operating in instrument meteorological conditions (IMC) throughout the remainder of the flight. Following the autopilot disengagement, the pilot had to manually maintain control of the airplane while operating in IMC, increasing his susceptibility to spatial disorientation. The airplane’s erratic flight track in the final 2 minutes of flight, culminating in the final rapidly descending right turn, were consistent with the known effects of spatial disorientation. Furthermore, the pilot’s focus to re-engage the autopilot likely created an operational distraction that contributed to a breakdown in his instrument scan. The airplane likely partially broke up at low altitude during its rapid descent to the ground, consistent with an exceedance of the airplane’s maximum operating speed. Pieces of the left wing were found up to 0.82 miles from the main wreckage and exhibited signatures of overload. Impact signatures at the accident site, witness observations, and review of the flight data were all consistent with the pilot losing control of the airplane. Furthermore, postaccident examination of the airplane wreckage revealed no evidence of preimpact failures or malfunctions that would have precluded normal operation. Specifically, while the airplane sustained significant impact damage, the portions of the flight control system that could be examined showed no evidence of disconnections or preimpact failures. In addition, the airplane’s setting for the pitch trim was near neutral and for the roll trim was slightly right wing down.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during maneuvering defining event
  2. Windshear or thunderstorm during enroute (cruise)

The NTSB's findings

  • Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
  • Aircraft › Aircraft systems › Auto flight system › Autopilot system › Capability exceeded
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Effect on personnel
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Lateral/bank control › Not attained/maintained
  • Environmental issues › Conditions/weather/phenomena › Wind › Updraft › Ability to respond/compensate

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,099.3 hours in all; 29.6 in the last 90 days; 8.1 in the last 30 days; 2,054.5 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

Passenger

  • Seat: unk
  • Injury: fatal

Passenger

  • Seat: unk
  • Injury: fatal

Passenger

  • Seat: unk
  • Injury: fatal

Passenger

  • Seat: unk
  • Injury: fatal

Passenger

  • Seat: unk
  • Injury: fatal

Passenger

  • Seat: unk
  • Injury: fatal

The aircraft

  • Seats: 11
  • Landing gear: fixed
  • Engine: P&W Canada PT6A-67P (turboprop); 0 hours total
  • Fire on the ground

The flight

  • Departed from: AFK Nebraska City NE at 5:00 pm
  • Destination: BIL Billings MT
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Wind: from 030° at 10 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 77°F (25°C), dew point 43°F (6°C)
  • Altimeter: 30.05 inHg
  • Observation at 12:53 pm from KGCC, 32 miles away

Weather report (METAR): KGCC 261853Z AUTO 03010KT 10SM CLR 25/06 A3005 RMK AO2 SLP118 T02500056

Injuries

FatalSeriousMinorNone
Flig1
Passengers6

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR24FA257.