Beech A36 Crash Near Murchison, Texas (N3215U) 02/11/2026

On February 11, 2026, a Beech A36 (N3215U) crashed near Murchison, Texas during an attempted emergency landing at Echo Lake Airport (TX40). The pilot and a pilot-rated passenger were fatally injured after the aircraft diverted following an in-flight emergency involving oil on the windscreen. Federal investigators are examining the accident, with particular focus on the reported oil-loss event, engine crankcase damage, and the final approach to TX40.

Accident Summary

What Happened

The airplane was operated as a Part 91 personal cross-country flight, and the pilot’s family reported the trip’s purpose was to visit family in the Dallas, Texas, area. A preliminary review of ADS-B data showed the airplane departed Orlando Executive Airport (ORL) on the morning of the accident, stopped at DeFuniak Springs Airport (54J) in Florida, then stopped again at Center Municipal Airport (F17) in Center, Texas, before departing F17 toward the Tyler, Texas, area. On the final leg, after crossing Lake Palestine, the pilot contacted air traffic control and declared an emergency, stating there was oil on the airplane’s windscreen.

The pilot told the controller he intended to land at Echo Lake Airport (TX40) near Murchison, Texas. ADS-B data showed the airplane flew north of TX40, turned south, and the flight track ended shortly thereafter. During the emergency landing, the airplane impacted pine trees and a power line pole, then came to rest on the eastern side of the airport on the front lawn of a private residence, with the empennage resting on a power line and the airplane in a nose-down attitude of about 45 degrees.

A witness extracted a dog from the airplane; the dog was not injured. The airplane sustained substantial damage to the fuselage and wings. Investigators recovered the wreckage from the accident site and transported it to a secure location for additional examination.

Aircraft and Operational Context

The airplane was manufactured in 1994 and was equipped with a Continental Motors IO-550-B reciprocating engine and a Hartzell PHC-C3YF-1RF three-blade controllable-pitch aluminum propeller. The pilot held an airline transport certificate and multiple instructor ratings; family members reported he was an active flight instructor in Florida and Texas and that the airplane was based at ORL. The pilot-rated passenger held a student pilot certificate and was seated in the rear right seat near the rear entry door.

The airplane carried personal items and baggage, including bags, suitcases, office supplies, and a cooler. The emergency was declared after the pilot reported oil on the windscreen, a condition that can materially reduce forward visibility and increase workload during diversion planning and approach execution. At this stage, the cause of the apparent oil-loss event has not been determined.

Accident Investigation

NTSB investigations develop in stages—from initial documentation and data preservation to component examinations and follow-on factual reporting—before conclusions are reached, as explained in our overview of the NTSB investigation process.

Examination of the wreckage found two holes in the engine crankcase above the locations of the No. 2 and No. 4 cylinders. Investigators observed oil on the windscreen, the area above the windscreen on the fuselage, the left side of the engine, and the underside of the fuselage, and the aircraft was retained for additional examination at a secure facility.

Investigators removed a Garmin GTN 750 unit, a Garmin GDU 1060 unit, and a J.P. Instruments engine data monitor (model not publicly reported) and sent them to the NTSB Vehicle Recorders Laboratory. As the investigation continues, these data sources are typically evaluated alongside ADS-B flight track information and air traffic control communications to refine the timeline and assess what aircraft performance and engine-parameter evidence can be recovered.

Operational and Regulatory Issues

In-flight oil-loss events that result in oil on the windscreen can present both mechanical and operational hazards. Investigators typically examine the source and progression of the oil release, whether any associated engine anomalies were present, and how the emergency affected cockpit workload, visibility, and decision-making during diversion and approach setup, without assuming a cause.

Emergency landings to smaller airports can involve constraints such as runway length, obstructions, and limited margin for maneuvering—particularly if visibility is degraded. Here, the accident sequence included impacts with trees and a power line pole during the attempted emergency landing, and investigators will generally correlate the flight track, approach path, and impact evidence as the factual record develops.

Aviation Accident Litigation

Separate from the safety investigation, fatal general aviation accidents can lead to civil claims that require independent evidence development and expert evaluation, as outlined in our overview of aviation accident litigation.

Depending on the facts established, evaluation may involve aircraft and engine maintenance history, component condition and traceability, and the chain of technical evidence preserved for examination, consistent with issues seen in matters summarized in our representative aviation matters.

Where aviation cases resolve, outcomes commonly turn on technical causation proof and individualized damages evidence, as reflected in our collection of selected aviation verdicts and settlements.

Broader context on how event type and severity can influence civil-case posture over time is discussed in our overview of aviation crash verdict trends.