# NTSB ERA26FA019: Cirrus SR22, N42BE, Ruston, LA, October 21, 2025 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Preliminary report - Date: October 21, 2025, 09:44 local (14:44 UTC) - Place: Ruston, LA - Coordinates: 32.472805, -92.572294 - Nearby events: https://openairdocs.org/map.md?lat=32.4728&lon=-92.5723&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Defining event: [Maneuvering: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: Fatal - Injuries: 1 fatal - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO, Cirrus Aircraft - NTSB case key (mKey): 201906 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA26FA019 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/201906/pdf - Page: https://openairdocs.org/ntsb/ERA26FA019 ## Preliminary report 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 colorationconsistent 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. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-IFR final approach: Navigation error](https://openairdocs.org/ntsb-events/280); cases with it: [Cirrus Design SR22, 1 case](https://openairdocs.org/ntsb-events/280/sequence.md?model=2130001), [All aircraft, 21 cases](https://openairdocs.org/ntsb-events/280/sequence.md) - [Maneuvering: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Cirrus Design SR22, 12 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=2130001), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Aircraft - Registration: [N42BE](https://openairdocs.org/aircraft/N42BE), registered now, S/N 3903 (OpenAirDocs) - Reported make and model: CIRRUS SR22 - Registry model: [Cirrus Design SR22](https://openairdocs.org/model/cirrus-design-sr22) (registry code 2130001) (OpenAirDocs) - Registry engine: [Continental IO-550-N](https://openairdocs.org/engine/continental-io-550-n) (registry code 17215, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 3903 - Year built: 2012 - Airframe hours: 1487.1 - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Operator: Lasalle Management Company LLC - Registered owner: Lasalle Management Company LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 15, 2025 - Departed: UTS, Huntsville, TX - Destination: Same as departure - Flight plan: IFR - Airport: RSN, Ruston Rgnl, runway 36, 6,002 × 100 ft, asphalt - Equipment: Angle of attack indicator, Auto-pilot, Data recorder, Electronic multifunction display, Electronic primary flight display, Stall warning system, ADS-B, Airframe parachute ## Weather - Conditions: Instrument (IMC), Day - Wind: 340° at 9 knots - Visibility: 7 statute miles - Lowest ceiling: 2,100 ft broken - Temperature: 68 °F, dew point 68 °F - Altimeter: 30.08 inHg - Observed at: RSN, 3 nm away - METAR: KRSN 211435Z AUTO 34009KT 7SM -RA FEW004 BKN021 OVC033 20/20 A3008 RMK AO2 RAB1431 CIG 016V025 PRESRR P0000 T01960196= ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20251021020129A](https://openairdocs.org/incident/20251021020129A), Oct 21, 2025: Cirrus Design Corp SR22, Ruston, LA, Destroyed, 1 fatal. According to preliminary flight track data, the airplane departed from huntsville municipal airport (uts), huntsville, Texas at 0830 with a destination of… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.