Cirrus Design CORP SF50 incident near Austin, Texas, September 14, 2024
On September 14, 2024 at about 5:48 pm local time, a 2023 Cirrus Design CORP SF50, registered N442CV, suffered minor damage in an incident during approach near Austin, Texas (Austin-Bergstrom Intl airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this incident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 14, 2024 · about 5:48 pm local time
- Place
- Austin, Texas · Austin-Bergstrom Intl · map
- Type
- Incident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SF50, built 2023
- Registration
- N442CV · registry record · serial 0442
- Damage
- Minor damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On September 14, 2024, at 1248 central daylight time, a Cirrus SF50, N442CV, experienced an uncommanded activation of its emergency automatic landing system soon after the airplane was struck by an unknown object during approach into Austin Bergstrom International Airport (AUS), Austin, Texas. The airplane sustained minor damage due to the impact and the pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight from Cincinnati Municipal Airport/Lunken Field (LUK), Cincinnati, Ohio to AUS. Object Strike According to the pilot, during approach into AUS, he thought a bird struck the right windscreen and damaged the interior sun visor near the top. However, a photograph provided by the airplane manufacturer, Cirrus Aircraft, showed scraping and blue, red, and white color transfer marks that extended diagonally from the bottom of the right windscreen near the center post toward the top and outboard side the windscreen, see figure 1. The pilot reported that after landing, he wiped the airplane down and noted there was an “oily residue” on the windscreen. He did not retain any samples of the residue. Figure 1. - Scrape and color transfer on windscreen (Source: Cirrus Aircraft). Emergency Autoland The pilot stated that the impact resulted in the activation of the airplane’s Emergency Autoland (EA) sequence. Preliminary information recovered from the airplane’s central maintenance computer indicated that at 1248, while about 1,540 ft above ground level and at a speed of 167 knots, the “Emergency Autoland Activating” warning message was presented in the cockpit for 10 seconds, followed by activation of the EA, which lasted for about 10 seconds before it was deactivated. About 4-5 seconds later, the “Emergency Autoland Activating” warning message was again presented for 10 seconds, before the EA activated for the 2nd time. EA was deactivated 9 seconds later and remained deactivated. After which the pilot was able to land the airplane uneventfully at AUS. The Emergency Autoland system is designed to land the airplane automatically in the event the pilot becomes incapacitated. The system can be activated: 1) by pressing a pushbutton located in the center of the overhead console (about 2 ft aft of the top of the windscreen – see figure 2), 2) if the Automatic Level mode is engaged for 1 minute, or, 3) if the Emergency Descent Mode is active and the airplane descends through 15,000 ft. Figure 2 . – Yellow arrow shows location of Autoland pushbutton (Source: Cirrus Aircraft). Once activated, the system enters a 10 second waiting period and provides visual and aural warnings of the impending EA sequence. The system can be deactivated at any time (during the waiting period or after) with the red autopilot disconnect button, located on the pilot side stick. After the waiting period, it will provide information on the instrument displays, tune the communication radios and broadcast automated messages, set the transponder to 7700, select a destination airport and generate a route to that airport. On approach, it will deploy the flaps, extend the landing gear and follow GPS guidance to the runway. After touchdown it will de-rotate the airplane and apply the wheel brakes. Data files were downloaded from the airplane’s on-board Recoverable Data Module by the airframe manufacturer and forwarded to the NTSB for examination. National Transportation Safety Board systems and recorder specialists were assigned to assist in the investigation of the incident. Parties to the investigation are the Federal Aviation Administration and Cirrus Aircraft. The investigation is continuing.
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
- Unknown or undetermined during approach defining event
The aircraft
- Seats: 7
- Landing gear: retractable
The flight
- Departed from: LUK Cincinnati OH
Weather at the time
- Light: daylight
- Wind: from 200° at 10 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 25,000 ft; a few clouds at 15,000 ft
- Temperature: 91°F (33°C), dew point 70°F (21°C)
- Altimeter: 29.91 inHg
- Observation at 12:53 pm from KAUS, 9 miles away
Weather report (METAR): METAR KAUS 141753Z 20010KT 10SM FEW150 BKN250 33/21 A2991 RMK AO2 SLP115 T03330211 10339 20233 58004=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number DCA24LA328.
