Incident Overview

Date: Friday 25 November 2022
Aircraft Type: Cirrus SF50 Vision Jet G2+
Owner/operator: Verijet
Registration Number: N15VJ
Location: 1,6 km SW of Indianapolis Regional Airport, IN – ÿ United States of America
Phase of Flight: Initial climb
Status: Substantial
Casualties: Fatalities: 0 / Occupants: 1
Component Affected: Capsulation Activation System (C.A.S.S.)Capsulation Activation System (C.A.S.S.)
Investigating Agency: NTSBNTSB
Category: Accident
A Cirrus SF50 airplane, N15VJ, experienced a significant incident following deployment of the airframe parachute system near Mount Comfort, Indiana. The pilot, Mr. [Pilot Name – Not Provided], was not injured. He engaged autopilot and autothrottle just after takeoff, and subsequently received landing gear warnings and a pitch-up situation. He attempted to disconnect the autopilot and manually override the nose-up pitch and throttle, but resistance in the control yoke prevented successful operation. The airplane descended, deploying the CAPS (Airframe Parachute System) mode, which activated just after takeoff at approximately 226 feet above ground level. The CAPS mode was designed to slow the aircraft by commanding idle thrust with AT, leveling the wings, and increasing the pitch attitude to bring the airspeed within deployment parameters. The pilot’s actions, including attempting to override the autopilot and deploying the CAPS, resulted in a stall and subsequent activation of the CAPS. The pilot’s failure to recognize the CAPS mode and follow procedures led to the uncommanded activation, which was likely due to corrosion in the CAPS activation system’s electrical components. This corrosion caused a transient power or ground interruption, generating a ?CAPS Activated? signal, leading to the unintended activation of the CAPS. The incident was likely caused by the pilot?s failure to identify the CAPS autopilot mode and follow standard procedures.A Cirrus SF50 airplane, N15VJ, experienced a significant incident following deployment of the airframe parachute system near Mount Comfort, Indiana. The pilot, Mr. [Pilot Name – Not Provided], was not injured. He engaged autopilot and autothrottle just after takeoff, and subsequently received landing gear warnings and a pitch-up situation. He attempted to disconnect the autopilot and manually override the nose-up pitch and throttle, but resistance in the control yoke prevented successful operation. The airplane descended, deploying the CAPS (Airframe Parachute System) mode, which activated just after takeoff at approximately 226 feet above ground level. The CAPS mode was designed to slow the aircraft by commanding idle thrust with AT, leveling the wings, and increasing the pitch attitude to bring the airspeed within deployment parameters. The pilot’s actions, including attempting to override the autopilot and deploying the CAPS, resulted in a stall and subsequent activation of the CAPS. The pilot’s failure to recognize the CAPS mode and follow procedures led to the uncommanded activation, which was likely due to corrosion in the CAPS activation system’s electrical components. This corrosion caused a transient power or ground interruption, generating a ?CAPS Activated? signal, leading to the unintended activation of the CAPS. The incident was likely caused by the pilot?s failure to identify the CAPS autopilot mode and follow standard procedures.

Description

A Cirrus SF50 airplane, N15VJ, was substantially damaged following deployment of the airframe parachute system near Mount Comfort, Indiana. The pilot was not injured. The pilot reported that he engaged the autopilot (AP) and autothrottle (AT) just after takeoff. Shortly thereafter, he received landing gear up warnings, and the airplane pitched up and engine thrust reduced uncommanded. He stated that he unsuccessfully attempted to disconnect the autopilot and manually override the nose-up pitch and throttle position, but he felt resistance in the control yoke, and the throttle returned to the idle position when he released it. After receiving a stall warning, he chose to activate the airframe parachute system (CAPS). The CAPS deployed and the airplane descended under canopy, coming to rest in a retention pond. Data recovered from the airplane indicated that the CAPS AP mode activated just after takeoff about 226 ft above ground level (agl). CAPS AP mode is designed to slow the airplane by commanding idle thrust with AT, leveling the wings, and increasing the airplane’s pitch attitude in order to bring the airspeed within CAPS deployment parameters. The landing gear warnings the pilot received were due to the airplane’s low altitude and reduced engine power. Although the pilot reported that he pressed the AP disconnect button on the yoke, recorded data showed that the pilot attempted to override the AP and AT servos with manual inputs to the control yoke and throttle lever, and did not press the AP disconnect button until about 27 seconds after CAPS AP mode activated. By this time, the airplane’s pitch trim was in the full nose-up position, and some aileron trim would have been applied in order to level the wings; this is consistent with the pilot’s statement that the airplane pitched up and rolled, which he interpreted as a stall, and resulted in his decision to activate the CAPS at an altitude about 570 ft above ground level. In CAPS AP mode, manual throttle inputs would not decouple AT, and the AP disconnect button was required to disengage AT. Examination and testing of modules from the CAPS activation system showed corrosion on electronic components. Further testing revealed that a momentary interruption of electrical power or ground to the electronic modules in the CAPS would result in the generation of a ?CAPS Activated’ signal, even if power was restored to the modules. It is likely that the corrosion of electrical components in the CAPS activation system resulted in a transient power or ground interruption, which resulted in generation of the ?CAPS Activated’ signal and subsequent uncommanded activation of the CAPS AP mode. The pilot likely did not recognize the situation, even though the autopilot status bar indicated the autopilot was in CAPS mode and believed that the airplane was in an unrecoverable flight condition, which resulted in his decision to deploy the CAPS. Probable Cause: The uncommanded activation of the CAPS autopilot mode due to corrosion of the system’s electrical components. Contributing to the accident was the pilot’s failure to identify the CAPS autopilot mode and promptly follow the procedures in the airplane flight manual.

Primary Cause

Corrosion of electronic components in the CAPS activation system, resulting in a transient power or ground interruption.Corrosion of electronic components in the CAPS activation system, resulting in a transient power or ground interruption.

Share on:

Leave a Reply

Your email address will not be published. Required fields are marked *