ERA26FA019 · Cirrus SR22
Lasalle Management Cirrus SR22 · Accident: controlled flight into terrain/object (CFIT) while maneuvering
From Huntsville Regional Airport (UTS) to an unrecorded destination
Event
- NTSB case
- ERA26FA019
- 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
- Ongoing
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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
- Instrument Meteorological Cond
Cirrus 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
- N42BE
- Operator
- Lasalle Management
- Onboard fatalities
- Unknown
- Route
- From Huntsville Regional Airport (UTS), Huntsville, TXTo not recorded
- Aircraft age
- About 13 years (built 2012)
- 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
- Maneuvering
- 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
- Controlled flight into terrain/object (CFIT)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA26FA019
- Event ID
- 20251021201906
- Case number
- ERA26FA019
- 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, coordinates. 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: 047bcaebb7a3192e3bcd8d3655bf92d6aad9c09e0ef325d53a6204981992313a; retrieved 2026-09-15T09:10:24.655Z.