NTSB CAROL · Event
Event CEN24FA073
Registry · N858RC
FAA Aircraft Registry record.
Make / Model
CIRRUS DESIGN SR22
TCDS
A00009CH · CIRRUS DESIGN CORP
Engine
CONT MOTOR IO-550-N (310 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20080206
ADS-B equipped
Yes — Mode-S ABC68A
Registrant of record
TURNER ROGER DEAN
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to attain the runway while landing at night, which resulted in an impact with trees.
Factual narrative
HISTORY OF FLIGHTOn December 26, 2023, about 1813 central standard time, a Cirrus Design Corporation SR22, N858RC, was involved in an accident near Canton, Texas. The pilot was fatally injured and the airplane was destroyed. The airplane was operated under Title 14 Code of Federal Regulations Part 91 as a personal flight. A witness heard radio transmissions from the pilot of the airplane reporting that he was west of Thompson Field Airport (1TA7), Canton, Texas. He then heard additional radio transmissions from the pilot reporting the downwind, base, and final legs for runway 13. The witness stated that radio transmissions were normal. The witness went outside to observe the airplane, but he could not tell if it was lined up with the runway due to his vantage point. The airplane impacted trees, terrain, and came to rest against a house. The main wreckage was located about 960 ft from the approach end of runway 13 on a heading of 116°. METEOROLOGICAL INFORMATIONThe U.S. Naval Observatory reported that sunset was at 1725 and the end of civil twilight was at 1752. Moon rise was at 1801 and the phase of the moon was Waning Gibbous, with 99% of the moon’s visible disk illuminated. WRECKAGE AND IMPACT INFORMATIONThe airplane initially impacted a tree line about 40-50 ft in height that was about 250 ft from the house where the airplane came to rest. The wreckage path from the tree line to the house was approximately 250 ft long and a heading of 146°. The airplane was destroyed by impact forces. Postaccident examination of the airplane confirmed flight control continuity from all control surfaces to the cockpit controls. The wings flaps were in the 50% position. The wreckage path contained the propeller blades, all of which were separated consistent with impact at the blade root. The propeller and propeller spinner displayed rotational and torsional features consistent with engine operation. MEDICAL AND PATHOLOGICAL INFORMATIONAlthough an autopsy was requested by the NTSB, the local Justice of the Peace did not order an autopsy to be performed. Toxicology testing performed at the Federal Aviation Administration Forensic Sciences Laboratory found no drugs of abuse. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Altitude-Not attained/maintained
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
- — Environmental issues-Conditions/weather/phenomena-Light condition-Dark-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2023_CEN24FA073.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.