NTSB CAROL · Event
Event WPR20LA237
Aircraft involved
Probable cause & findings
The pilot’s failure to maintain airspeed and his exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall at too low of an altitude to recover.
Factual narrative
HISTORY OF FLIGHTOn July 24, 2020, about 1159 Pacific daylight time, a Vans RV-8, N138PM, was substantially damaged when it was involved in an accident near Tehachapi Municipal Airport (TSP), Tehachapi, California. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Witnesses reported that the accident airplane made a straight-in approach to land. The airplane touched down onto the runway tailwheel first and oscillated between its tailwheel and main landing gear several times. It then tipped up onto the left main gear and turned toward the right edge of the runway. The airplane appeared to slow when the pilot transmitted “going around.” The witness reported the pilot applied the engine power so abruptly that the engine “coughed” a number of times before it smoothed out. The airplane lifted off quickly but made a "perceivably slow" turn to a left crosswind. The nose of the airplane was "alarmingly" high, and the airplane did not appear to be accelerating. The left turn steepened as the airplane descended behind buildings in a nose up attitude with the wings wobbling. The engine "cut out," and, almost immediately thereafter, they heard the impact. Video taken from a security camera showed the airplane in a descending left turn just prior to impact. Its left wing appeared to raise slightly before it descended behind a building roofline. Immediately thereafter, dirt and debris were observed. A distant away video of the runway showed the accident airplane come into land on the runway before taking off again. The airplane started a shallow climb, then initiated a nose high, left turn. About halfway through the turn, the nose of the airplane lowered, and the airplane descended toward the ground left wing low. A different video showed the airplane in a descent. Its left wing appeared to raise slightly before it descended behind a building roofline. Immediately thereafter, dirt and debris were observed. The Advanced Flight Systems multifunction display recorded data from the entire flight. Data recovered revealed that the airplane’s airspeed decreased to 47 knots during the landing roll at TSP. The engine power and airspeed then increased, and the airplane lifted off about 10 seconds later at an airspeed of about 64 knots. The airplane continued to climb as it entered a left bank. The airplane’s maximum rate of climb was 760 ft/min at an airspeed of 64 knots while in a 38° left bank. About 6 seconds later, while still at 64 knots, the airplane entered a descent and the left bank had increased to about 50°. The last data recorded showed the airplane in a 2,180-fpm descent while in a 83.5° left bank at an altitude of 3,970 ft above mean sea level. The airplane had gained about 200 ft in altitude after it took off prior to entering the descent. The data indicated the engine was operating at a maximum of 67% following the aborted landing. WRECKAGE AND IMPACT INFORMATIONThe airplane breached the roof of a building about 350 yards southwest of the departure end of the runway. The airplane entered the roof, went through the upper portion of one wall, and came to rest on top of a second wall. Both wings were bent aft, and the left wing was found positioned lower than the right. The aft fuselage and empennage extended upward and remained above the roofline. Postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation. Both wings were bent aft and partially separated from the fuselage. The left wing outboard leading edge was crushed aft and upward; and the right wing inboard leading edge was crushed aft. The fuel caps remained secured on the left- and right-wing fuel tanks; however, the tanks themselves were breached and no fuel was noted. Flight control continuity was established from the forward control stick to both the left and right aileron bellcranks. The aileron surfaces themselves were fracture separated. Rudder and elevator control continuity was established from their cockpit controls to their respective flight control surfaces. The throttle and mixture controls in the cockpit remained secured to their respective control arms on the fuel servo. The upper spark plugs were removed from the engine and their appearance was consistent with normal operations. All engine fuel lines remained secured. The fuel pump, fuel servo, and fuel divider were disassembled and unremarkable. The engine was borescoped; the cylinder walls, piston heads, valves, and lower spark plugs were all consistent with normal operations. The engine was rotated by hand at the propeller hub. Thumb compression was established on all cylinders and drivetrain continuity was established to the accessory section. The magnetos remained secured on their mounting pads and spark was obtained on all ignition leads. MEDICAL AND PATHOLOGICAL INFORMATIONThe Kern County Sheriff’s Office, Bakersfield, California performed an autopsy of the pilot. The pilot’s cause of death was multiple blunt force trauma. The Federal Aviation Administration (FAA) Forensic Sciences Laboratory performed toxicological testing on specimens from the pilot with a positive result for Tamsulosin (Flomax) in urine. Tamsulosin is acceptable for FAA medical certification. Witnesses reported that the accident airplane made a straight-in approach to land. The airplane touched down onto the runway tailwheel first and oscillated between its tailwheel and main landing gear several times. It then tipped up onto the left main gear and turned toward the right edge of the runway surface. The pilot initiated an aborted landing and according to a witness, the airplane lifted off quickly but made a "perceivably slow" turn to a left crosswind. The nose of the airplane was "alarmingly" high, and the airplane did not appear to be accelerating. The left turn steepened as the airplane descended behind buildings in a nose-up attitude with the wings wobbling. The engine "cut out" and, almost immediately thereafter. they heard the impact. The airframe and engine examination did not reveal any anomalies that would have precluded normal operation. Recorded data from the airplane was consistent with what the witnesses reported. The engine power never exceeded 67%, which is likely why the airplane did not appear to accelerate during the takeoff; however, this would not have resulted in the loss of control. Given the reported nose-high attitude and steep left turn, it is likely the pilot exceeded the airplane’s critical angle of attack and that it stalled at an altitude too low for the pilot to recover before it impacted the building. 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
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Capability exceeded
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained
Verbatim from NTSB's published report. Source file
NTSB_2020_WPR20LA237.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 ↗