FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DCA24LA328 · Cirrus Design Corp SF50

14 Sept 2024 · Austin, TX, United States

Cirrus Design Corp SF50 · Incident on approach

From Cincinnati Municipal Airport Lunken Field (LUK) to an unrecorded destination

Report a problem

Event

NTSB case
DCA24LA328
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
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
Event fatalities
Unknown
Ground fatalities
Unknown
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
Visual 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
N442CV
Operator
Dee Winston
Onboard fatalities
Unknown
Route
From Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OHTo not recorded
Aircraft age
About 1 year (built 2023)
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
Approach
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
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record DCA24LA328
Event ID
20241017195334
Case number
DCA24LA328
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. 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: 8804b575d969efef113630c1aa0a996d4d5f642fb0d3c5641c0f044607fdb19b; retrieved 2026-09-16T19:23:40.002Z.