NTSB CAROL · Event
Event ERA20FA085
Aircraft involved
Probable cause & findings
The pilot's exceedance of the airplane's critical angle of attack, which resulted in an aerodynamic stall and subsequent loss of control at low altitude.
Factual narrative
HISTORY OF FLIGHT
On January 25, 2020, about 0930 eastern standard time, a Piper PA32-260, N55455, was destroyed when was involved in an accident near Lake City, Florida. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. A witness stated that the pilot flew to Cannon Creek Airpark (15FL), Lake City, Florida, the weekend before the accident. At that time, the pilot said the engine “cut out” on short final approach to the runway; however, after landing, the pilot performed an engine run-up, and the engine performed normally. The pilot and the witness subsequently opened the engine cowling and observed an oil leak. The pilot contacted a local mechanic to fix the oil leak. A couple of days later, the pilot ran the engine, and no oil leaks were noted. The night before the accident flight, the pilot and the witness taxied the airplane to the fuel tank and topped off the wing tanks and left-wing tip tank, but they did not put fuel in the right-wing tip tank because it had a fuel leak. On the morning of the accident, the witness and pilot performed a preflight inspection of the airplane and noted no anomalies. The witness watched the airplane take off from runway 36 and noticed that the pilot “turned hard left” after the airplane cleared the trees, which was earlier than normal. The witness returned to his vehicle when he heard a loud bang and saw smoke. He drove over to the smoke and saw that the airplane was engulfed in flames.
WRECKAGE AND IMPACT INFORMATION
The airplane came to rest on the side of a house in a subdivision about 1,000 ft to the west side of the midpoint of the runway. The wreckage was oriented on a heading of 215° and there was no discernable horizontal wreckage path. A postaccident fire consumed the airplane, and only the tail section remained intact and undamaged by fire. The cockpit, instrument panel, firewall, fuselage, and wings were all destroyed by the fire, and the engine accessory case was consumed by fire; the magnetos, fuel pump, carburetor, vacuum pump, and oil filter were destroyed. All major components of the airplane were accounted for at the scene. Control cable continuity was confirmed to the respective controls. Postaccident examination of the engine revealed the engine crankcase and cylinders were intact. The top spark plugs were removed, and a borescope examination of the cylinder walls, exhaust, intake valves and piston heads revealed no anomalies. The engine’s crankshaft was rotated by hand and thumb compression was established on all cylinders. Valve train continuity was established throughout the engine by observing movement of the rocker arms and rear accessory case gears. Both propeller blades remained attached to the hub. One blade was bent aft about midblade, and both blades were twisted near the tip. A witness near the airport captured the airplane engine noise on a video camera. The airplane was not captured by the video, and its position, ground track, speed, and therefore at what point during the accident sequence the captured audio occurred could not be determined. A sound spectrum analysis of the audio by the National Transportation Safety Board Vehicle Recorders Laboratory revealed that during the time audio from the accident airplane’s engine was recorded, the engine rpm was approximately 2,584 rpm, which was slightly below the maximum rated 2,700 rpm.
MEDICAL AND PATHOLOGICAL INFORMATION
An autopsy performed on the pilot by the Office of the Office of the Medical Examiner, Jacksonville, Florida, reported the cause of death as blunt force trauma. Toxicology testing performed at the FAA Forensic Sciences Laboratory found no tested-for drugs or alcohol. A witness described that, when the pilot arrived at the airport several days before the accident, the airplane’s engine “cut out” while on final approach to the runway. After landing uneventfully, the pilot had a mechanic service the airplane, and the engine performed normally. On the day of the accident, as the airplane departed, the witness reported that he watched the airplane turn “hard left” after it cleared trees near the runway. He later heard a loud bang, then saw smoke. He drove over to the smoke and saw that the airplane was completely engulfed in flames. The airplane came to rest in the yard of a residence about 1,000 feet left of the runway’s midpoint. Postaccident examination of the airplane was limited due to impact and postcrash fire damage; however, no defects consistent with a preimpact failure or malfunction of either the airframe or engine were observed. Additionally, a sound spectrum analysis of the audio from a video recording showed that the engine was likely running slightly below full throttle before the accident. Given this information, there was no evidence that a loss of engine power preceded the accident. The witness’s description that the airplane was in a “hard left” turn, the location of the accident site relatively close to the runway, the lack of a discernable horizontal wreckage path, and little fragmentation of the wreckage to suggest a high-energy impact, were consistent with the airplane impacting the ground in a near-vertical descent at a relatively low speed. Thus, it is likely that the pilot exceeded the airplane’s critical angle of attack during the steep, low-altitude turn shortly after takeoff, which resulted in an aerodynamic stall and loss of airplane control at an altitude too low for recovery. 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).
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained
Verbatim from NTSB's published report. Source file
NTSB_2020_ERA20FA085.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 ↗