# NTSB ERA25LA155: Cirrus Design SF50, N56GY, Kissimmee, FL, March 24, 2025 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Preliminary report - Date: March 24, 2025, 08:04 local (12:04 UTC) - Place: Kissimmee, FL - Coordinates: 28.29575, -81.427722 - Nearby events: https://openairdocs.org/map.md?lat=28.2958&lon=-81.4277&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO, Cirrus Aircraft, Williams International - NTSB case key (mKey): 199902 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25LA155 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199902/pdf - Page: https://openairdocs.org/ntsb/ERA25LA155 ## Preliminary report On March 24, 2025 about 0804 eastern daylight time, a Cirrus Design Corporation SF50, N56GY, was substantially damaged when it was involved in an accident at Kissimmee Gateway Airport (ISM), Orlando, Florida. The commercial pilot was not injured. The airplane was operated as a Title 14?Code of Federal Regulations Part 91 executive/corporate flight.? The pilot stated that he performed a standard preflight, utilizing the Federal Aviation Administration (FAA) Approved Airplane Flight Manual external checklist with no discrepancies reported, but he did not check the fuel tanks for contamination, believing that task would be accomplished by Cirrus personnel. One Crew Alerting System (CAS) message associated with engine start volts low was noted before engine start, but the engine started normally, and the message extinguished after engine start. The flight departed from runway 24 about 0725, and after takeoff was flying with the autopilot and autothrottle engaged. According to data downloaded from the recoverable data module (RDM) along with pilot provided information, while climbing at flight level (FL) 198, about 0737:23 the message FADEC NO DISPATCH Caution displayed. He went thru that checklist while continuing to climb and reported the message continued following checklist completion, but continuance of the flight was allowed. About 2 minutes 19 seconds later while flying at FL234, the red FADEC CTRL DEGRADED Warning illuminated. He pulled up that checklist and worked through it but the message continued. He contacted the controller and requested a vector to return to ISM, but did not declare an emergency at that time. He reported performing the FADEC Reset via the multi-function (MFD) display and recalled a warning that the engine power may not be reliable. In going thru that checklist, the engine did not respond to thrust lever change, so he then declared an emergency with the controller. While descending he attempted to slow the airplane using the manual mode of the autothrottle by setting a target speed of 180 knots indicated airspeed (KIAS), but the airplane did not slow, nor did the thrust lever move as expected. At that time the flight was in close proximity to ISM while the thrust remained at + or – 30% so he requested delaying vectors as the flight was fast and close to ISM. He then pushed the thrust lever full forward and the thrust increased to 42%, then brough it back to flight idle and the thrust decreased to 1%, which did not change with further thrust lever advancement. The pilot added that having the thrust go from 30% to 1% added a new level of complexity to the situation. The pilot considered either deploying the Cirrus Airframe Parachute System (CAPS) or gliding to ISM and noted the later was possible. At that point while on the base leg of the airport traffic for runway 6 at ISM, he extended the flaps to 50% and proceeded to the runway lowering the landing gear and flaps to 100% at the last minute. The flight touched downfast 2/3’s down the 5,001 ft long runway and he was unable to stop using normal brakes. The flight rolled off the end of the runway onto grass and collided with an airport boundary fence. He shut down the engine, which occurred at 0804, and evacuated the airplane. A review of the maintenance records revealed that on March 18, 2025, when turning on power a “FADEC No Dispatch and FADEC CTRL Degraded” CAS Messages were displayed. A download of the FADEC was performed and the information was provided to the engine manufacturer. Because the airplane was on a list for replacement of the fuel control unit (FCU) by a Service Bulletin, the FCU was removed and a modified FCU was installed on March 20, 2025. Following the replacement of the FCU maintenance personnel performed acceleration and stability checks with no discrepancies noted. The maintenance was signed off on March 21, 2025, and the accident flight was the 1st flight since the modified FCU was installed. Following postaccident examination of the airframe and engine, the engine was removed and sent to the manufacturers facility for further examination and testing. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340) (defining event); cases with it: [Cirrus Design SF50, 1 case](https://openairdocs.org/ntsb-events/340/sequence.md?model=2130010), [All aircraft, 820 cases](https://openairdocs.org/ntsb-events/340/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cirrus Design SF50, 5 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2130010), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Cirrus Design SF50, 2 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2130010), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) ## Aircraft - Registration: [N56GY](https://openairdocs.org/aircraft/N56GY), registered now, S/N 0324, built 2021 (OpenAirDocs) - Reported make and model: CIRRUS DESIGN CORP SF50 (NO SERIES) - Registry model: [Cirrus Design SF50](https://openairdocs.org/model/cirrus-design-sf50) (registry code 2130010) (OpenAirDocs) - Registry engine: [Williams FJ33-5A](https://openairdocs.org/engine/williams-fj33-5a) (registry code 66015, turbo-fan) (OpenAirDocs) - Category: Airplane - Serial number: 0324 - Year built: 2021 - Airframe hours: 800 - Damage: Substantial damage - Flight: Executive/Corporate, Part 91 - Operator: Galati Yacht Sales, LLC - Registered owner: Gys Enterprises LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 16, 2025, 58 hours before - Destination: JKA, Gulf Shores, AL - Flight plan: IFR - Airport: ISM, Kissimmee Gateway Airport, runway 6, 5,001 × 100 ft, asphalt - Equipment: ADS-B, Stall warning system, Electronic primary flight display, Electronic multifunction display, Electronic flight bag or handheld device, Data recorder, Auto-pilot, Angle of attack indicator, Airframe parachute ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 57 °F, dew point 57 °F - Altimeter: 30.11 inHg - Observed at: KISM, 1 nm away - METAR: KISM 241155Z 00000KT 10SM CLR 14/14 A3011 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20250324003829A](https://openairdocs.org/incident/20250324003829A), Mar 24, 2025: Cirrus Design Corp SF50, Kissimmee, FL, Substantial damage. Pilot reported a throttle control problem on the climb out followed by loss of power (flight idle power). On the emergency return to the airfield, airplane… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.