CEN24FA073 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: collision during takeoff/landing on approach
From Addison Airport (ADS) to an unrecorded destination
Event
- NTSB case
- CEN24FA073
- 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
- 1 · all aircraft and ground
- 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 SR22
- Aircraft type
- Cirrus SR22
- 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
- N858RC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Addison Airport (ADS), Addison, TXTo not recorded
- Aircraft age
- About 15 years (built 2008)
- 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
- Collision during takeoff/landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was attempting a night visual approach to a private airport that had solar deck lights as runway lights. A witness heard the pilot make radio transmissions for the downwind, base, and final approach legs of the traffic pattern before the airplane impacted trees and terrain east of the runway. The airplane was destroyed by impact forces. Non-volatile data from the airplane showed the approach was approximately parallel to and about 340 ft east of the runway before the tree line, which the airplane struck. The data showed the airplane had minimal altimetry error. The data also showed that the engine operated with no anomalies throughout the approach and impact with terrain. Postaccident examination of the airplane confirmed flight control continuity, as well as rotational and torsional features on the propeller blades and spinner consistent with engine operation. An autopsy was not performed on the pilot, so an incapacitating medical event could not be ruled out. It is likely that pilot performed an inadequate visual approach at night that resulted in a collision with terrain. Based on the available evidence, it was undetermined why the pilot performed an inadequate visual approach.
Probable cause
The pilot’s failure to attain the runway while landing at night, which resulted in an impact with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24FA073
- Event ID
- 20231227193570
- Case number
- CEN24FA073
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2023-12-27.
- API snapshot SHA-256: 4cf751dbb4c1c95266f895b9e7798ab29c2a4c3d89e3eea43cdd63eff1863d9e; retrieved 2026-09-15T08:09:38.039Z.