NTSB CAROL · Event
Event ERA26FA019
Registry · N42BE
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
20121203
ADS-B equipped
Yes — Mode-S A4F964
Registrant of record
LASALLE MANAGEMENT COMPANY LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Factual narrative
On October 21, 2025, about 0944 central daylight time, a Cirrus SR22, N42BE, was destroyed when it was involved in an accident near Ruston, Louisiana. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to preliminary ADS-B and communications data obtained from the FAA, the airplane departed from Huntsville Municipal Airport (UTS), Huntsville, Texas at 0830 with a destination of Ruston Regional Airport (RSN), Ruston, Louisiana. Air traffic control (ATC) cleared the airplane for the RNAV RWY 36 approach, which the pilot acknowledged, but shortly thereafter the pilot requested a go-around. The controller cleared the pilot to climb, maintain 2,000 ft and to turn right to a heading 120°. The controller asked the pilot if the visibility or ceilings were too low and the pilot responded that he was having “a little trouble with my autopilot there getting that programmed in.” The controller asked the pilot to verify the airplane’s heading and provided a low altitude alert. The controller then again asked the pilot to verify the heading and asked the pilot if he was flying using the autopilot or “hand flying.” The pilot responded that he was “hand flying” the airplane. There were no further communications received from the pilot. The accident site was located in heavily wooded terrain 2 1/2 miles southeast from the beginning of runway 36. The airplane first contacted a 60 ft tall tree before contacting three other trees at altitudes of 30 ft, 27ft, and 24 ft, respectively. According to data recovered from the airplane’s recoverable data module (RDM), the airplane was in a left bank and nose low attitude at the time of impact. The impact crater was located 30 ft southeast from the initial tree strike and was 2 ft in depth and 6 ft in circumference. The main debris field was 330 ft long and 60 ft wide and along a 103° heading, with debris extending outwards. A postcrash fire consumed portions of the fuselage, wings, and empennage. Fuel blighting was visible on vegetation throughout the debris field. The engine was impact separated and located beyond the impact crater and to the left side of the main debris path. According to RDM data, the engine was producing 2500 rpm (91% power), and all cylinder head temperatures and exhaust gas temperatures were consistent with normal engine operation at the time of the accident. Both magnetos were impact separated from the engine and were not recovered. A large hole consistent with impact damage was observed on the crankcase above the number 2 and 4 cylinders. One counterweight was visible through the crankcase hole and was unremarkable. A connecting rod was visible through the hole and remained secured to the crankshaft. The top spark plugs sustained impact damage and were removed for further investigation. The no. 4 cylinder top spark plug electrode was absent. The remaining top spark plug electrodes showed wear and coloration consistent with normal engine operation. The oil filter was impact separated from the engine but remained attached to the accessory housing via safety wire and had minor carbon debris was visible within the pleats when examined. The engine would not rotate as a result of impact damage and impacted organic material. All six cylinders had dirt and organic matter pressed between the cooling fins. The intake pipes for all six cylinders were impact separated. The exhaust stacks were impact damaged and impact separated. Cylinders 5 and 6 had impact damage to the cylinder heads and were missing rocker box covers. The propeller and crankshaft flange were separated from the engine and found adjacent to the impact crater. The three-bladed metal propeller displayed “S” bending and rotational scoring consistent with high rpm settings. One propeller blade was missing the blade tip. The spinner dome was missing from the propeller. The airplane was equipped with a Cirrus Airframe Parachute System (CAPS) that was found partially deployed consistent with impact during the accident sequence. The parachute remained packed in its bag, but the parachute cables were extended. The ballistic rocket was found at the furthest end of the debris field, 330 ft from the initial tree impact. The CAPS handle within the cockpit was in the stowed position. The ground safety pin was not installed in the handle. The wreckage was retained for additional examination. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2025_ERA26FA019.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.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, go-around, autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint
ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- arXiv 2024 · arXiv preprint
A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
Browse the full corpus — academia portal ↗