What happened
Following several weather briefings that delayed the departure until the afternoon, the pilot began the flight in visual meteorological conditions. During the approach to the destination, air traffic controllers notified the pilot of severe weather, including intense precipitation, along the planned final approach path. The pilot requested an RNAV approach while approaching the final approach fix.
While flying at a low thrust setting, the autopilot attempted to maintain an altitude of 2,000 feet, which resulted in a pitch-up maneuver and a reduction in airspeed to approximately 100 knots, triggering an airspeed warning. As the aircraft entered instrument meteorological conditions, it encountered heavy turbulence and extreme precipitation related to a mature thunderstorm. The pilot subsequently deactivated the autopilot. Following the application of takeoff thrust, the aircraft experienced a climb rate exceeding its performance capabilities, likely due to thunderstorm updrafts.
During the encounter, the High Electronic Stability & Protection (ESP) system engaged, causing a nose-down pitch in conjunction with the pilot's forward control input. The aircraft underwent a sequence of descending and pitching up maneuvers. In response to the situation, the pilot deployed the Cirrus Airframe Parachute System (CAPS). The aircraft descended under the canopy and landed in a marsh, where wind caused the plane to be dragged a short distance.
Findings
Post-accident inspections of the Cirrus aircraft revealed significant damage to the fuselage, specifically to the front pressure bulkhead and the areas immediately behind it. Investigation of the engine and flight controls showed no evidence of mechanical failure or malfunction prior to the impact. Data from the Recoverable Data Module (RDM) indicated that the autopilot and stability protection systems functioned as intended, with no recorded faults until the parachute was activated. While the pilot believed the autopilot was malfunctioning, the data suggests the observed behaviors were likely standard system responses to mode changes. The primary factor in the flight's instability was the encounter with severe thunderstorm updrafts and extreme precipitation.