NTSB CAROL · Event
Event GAA19CA226
Aircraft involved
Probable cause & findings
The pilot's improper landing flare during a turning, full-down autorotation, which resulted in a lower-than-normal rotor rpm, a faster-than-normal ground run speed, and the subsequent loss of directional control, a runway excursion, and a roll-over. Contributing to the accident was the flight instructor's delayed remedial action.
Factual narrative
The pilot reported that the purpose of the training flight was to complete multiple simulated, engine failure autorotations without a power recovery (full-down autorotation). After he completed his first right, 180º turn, full-down autorotation, the airspeed was "too slow." He added that the instructor told him to maintain more speed during the right turn of his second attempt, and the pilot focused on maintaining more airspeed, but the descent rate increased "due to the speed." The pilot added that, after he completed the right turn and aligned with the runway centerline, he felt that the airspeed was fast, so he flared to reduce the ground speed and increase the main rotor rpm. However, the helicopter started to sink during the flare, so due to the low altitude, the pilot leveled the helicopter to prevent a tail strike. The helicopter touched down on its skids with "substantial" ground speed and veered slightly right. The pilot applied full left cyclic and pedal input, but the helicopter continued to veer right. The helicopter exited the runway and rolled over on its left side. The fuselage and main rotor blades were substantially damaged. The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation. The flight instructor reported that the 180º right turn aligned the helicopter with the runway centerline but at a lower altitude than was desirable because it prevented the pilot from conducting a normal flare "as the tail would have struck the runway." He added that, a normal flare before touchdown in a full-down autorotation would result in a 30º nose-up attitude, but the pilot was only able to achieve about a 10º nose-up attitude "for fear of damaging the tail." The pilot reported that the purpose of the training flight was to complete multiple simulated, engine failure autorotations without a power recovery (full-down autorotation). After he completed his first right, 180º turn, full-down autorotation, the airspeed was "too slow." He added that the instructor told him to maintain more speed during the right turn of his second attempt, and the pilot focused on maintaining more airspeed, but the descent rate increased "due to the speed." The pilot added that, after he completed the right turn and aligned with the runway centerline, he felt that the airspeed was fast, so he flared to reduce the ground speed and increase the main rotor rpm. However, the helicopter started to sink during the flare, so due to the low altitude, the pilot leveled the helicopter to prevent a tail strike. The helicopter touched down on its skids with "substantial" ground speed and veered slightly right. The pilot applied full left cyclic and pedal input, but the helicopter continued to veer right. The helicopter exited the runway and rolled over on its left side. The fuselage and main rotor blades were substantially damaged. The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation. The flight instructor reported that the 180º right turn aligned the helicopter with the runway centerline but at a lower altitude than was desirable because it prevented the pilot from conducting a normal flare "as the tail would have struck the runway." He added that, a normal flare before touchdown in a full-down autorotation would result in a 30º nose-up attitude, but the pilot was only able to achieve about a 10º nose-up attitude "for fear of damaging the tail." 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 Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Prop/rotor parameters-Not attained/maintained - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- F Personnel issues-Action/decision-Action-Delayed action-Instructor/check pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2019_GAA19CA226.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 (engine failure, runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- arXiv 2022 · arXiv preprint
Multi-level Adaptation for Automatic Landing with Engine Failure under Turbulent Weather
This paper addresses efficient feasibility evaluation of possible emergency landing sites, online navigation, and path following for automatic landing under engine-out failure subject to turbulent wea…
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2019 · Conference Paper
Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios
Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techiques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techniques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
Browse the full corpus — academia portal ↗