CEN23FA045 · Cirrus Design Corp SF50
Cirrus Design Corp SF50 · Accident: flight control system malfunction/failure during initial climb
From an unrecorded airport to 3J7 · Greensboro, GA
Event
- NTSB case
- CEN23FA045
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
- Instrument Meteorological Cond
Cirrus Design Corp SF50
- Aircraft type
- Cirrus SF50
- 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
- N15VJ
- Operator
- Verijet
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 3J7 · Greensboro, GA
- Aircraft age
- About 2 years (built 2020)
- 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
- Initial climb
- 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
- Flight control system malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23FA045
- Event ID
- 20221125106361
- Case number
- CEN23FA045
- 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: 451a6a0abe2b1629e062e8da21a8fecfb4db51f8fcc9cd91821402382bebf8d5; retrieved 2026-09-16T16:27:27.546Z.