NTSB CAROL · Event
Event CEN20LA134
Aircraft involved
Probable cause & findings
The pilot’s inadvertent exceedance of the airplane’s critical angle of attack for undetermined reasons, which resulted in an aerodynamic stall, loss of control, and subsequent impact with terrain.
Factual narrative
On March 29, 2020, at 1518 central daylight time, a Muse P51D airplane, N151JD, was destroyed when it was involved in an accident near Mesquite, Texas. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Witnesses reported that the pilot took off and turned to a right crosswind in the traffic pattern, followed shortly thereafter by a turn to downwind. The airplane then entered a gradually steepening right turn before transitioning to a steep nose down attitude which continued until impact with terrain. A review of Automated Dependent Surveillance – Broadcast (ADS-B) data revealed that the airplane entered a right traffic pattern after takeoff and leveled off about 1,800 ft mean sea level (msl) on crosswind before beginning a turn to downwind. About 1518:47, the airplane entered a descending right turn from about 1,700 ft msl. The final data point was recorded at 1518:53; the altitude was about 900 ft msl. The average descent rate over the last 6 seconds of data was approximately 8,000 ft per minute. A postaccident examination of the airframe and engine did not reveal any anomalies consistent with a preimpact failure or malfunction. However, the examination was limited by the extent of the impact and postimpact fire damage. Toxicology testing performed at the Federal Aviation Administration Forensic Sciences Laboratory found no drugs of abuse. The owner/builder reported the accident occurred during the third flight of the airplane. The plan was for the pilot to conduct airwork in the local area and to gather data to assist in determining airplane fuel consumption. After the second flight, the pilot informed the builder that he had inadvertently moved the fuel selector to the OFF position while attempting to change tanks. He was able to correct the situation and had no further difficulties. A friend of the pilot reported that the pilot had cut the second flight short because continuous right rudder input was required. For the accident flight, the pilot took off with full right rudder trim to counter act the right turning tendency. Witnesses reported that the pilot took off and turned to a right crosswind in the traffic pattern, followed shortly thereafter by a turn to downwind. The airplane then entered a gradually steepening right turn before transitioning to a steep nose down attitude which continued to impact with terrain. Automated Dependent Surveillance – Broadcast (ADS-B) data revealed that the airplane entered a right traffic pattern after takeoff and leveled off about 1,800 ft mean sea level (msl) on a crosswind leg before beginning a turn to a downwind leg. The airplane subsequently entered a steep, descending right turn until impact. The average descent rate over the last 6 seconds of the flight was about 6,000 ft per minute. The airplane was destroyed by impact forces and the postaccident fire. A postaccident examination of the airframe and engine did not reveal any anomalies consistent with a preimpact failure or malfunction. However, the examination was limited by the extent of the impact and postimpact fire damage. For the accident flight, the pilot had planned to proceed to the practice area to conduct airwork; however, he elected to remain in the airport traffic pattern for unknown reasons. Full right rudder trim was set before takeoff in order to counteract engine torque. Based on the available information, the pilot inadvertently entered an aerodynamic stall from which he was unable to recover. The yaw induced by the full right rudder trim aggravated the stall and made recovery more difficult. The reason for the loss of control could not be determined with the available information. 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).
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
- — Not determined-Not determined-(general)-(general)-Unknown/Not determined
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained
Verbatim from NTSB's published report. Source file
NTSB_2020_CEN20LA134.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, loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- 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 …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- arXiv 2025 · arXiv preprint
Quadratic Programming Approach to Flight Envelope Protection Using Control Barrier Functions
Ensuring the safe operation of aerospace systems within their prescribed flight envelope is a fundamental requirement for modern flight control systems.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
Browse the full corpus — academia portal ↗