The U.S. aircraft register, updated daily
Accidents · NTSB CEN23FA045 · Final report

Cirrus Design CORP SF50 accident near Mount Comfort, Indiana, November 25, 2022

On November 25, 2022 at about 1:00 pm local time, a 2020 Cirrus Design CORP SF50, registered N15VJ, was substantially damaged in an accident during initial climb near Mount Comfort, Indiana (Indianapolis Rgnl airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

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

What the record shows

Date
November 25, 2022 · about 1:00 pm local time
Place
Mount Comfort, Indiana · Indianapolis Rgnl · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cirrus Design CORP SF50, built 2020
Registration
N15VJ · no longer on the register · serial 0215
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

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

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.

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. Flight control sys malf/fail during initial climb defining event

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Understanding/comprehension › Pilot
  • Aircraft › Aircraft systems › (general) › (general) › Fatigue/wear/corrosion
  • Aircraft › Aircraft systems › (general) › (general) › Unintentional use/operation
  • Aircraft › Aircraft systems › Auto flight system › Autopilot system › Incorrect use/operation

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 12,000 hours in all; 200 in this make and model
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Maximum gross weight: 6,040 lb
  • Seats: 7
  • Landing gear: retractable
  • Engine: Williams FJ33-5A (turbofan); 0 hours total

The flight

  • Destination: 3J7 Greensboro GA
  • Flight plan: IFR
  • Runway 25, 6,005 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 300° at 7 knots
  • Visibility: 7 statute miles
  • Sky: overcast at 1,200 ft
  • Temperature: 45°F (7°C), dew point 45°F (7°C)
  • Altimeter: 30.17 inHg
  • Observation at 7:56 am from KMQJ, 1 miles away

Weather report (METAR): METAR KMQJ 251256Z AUTO 30007KT 7SM OVC012 07/07 A3017 RMK AO1=

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

9 documents, released by the NTSB on February 20, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.