NTSB CAROL · Event
Event ERA19TA105
Aircraft involved
Probable cause & findings
The pilot's failure to maintain airplane control during a simulated single-engine go-around, which resulted in a collision with terrain.
Factual narrative
On February 21, 2019, about 1026 eastern standard time, a Beech 76 airplane, N7KY, collided with terrain during an aborted landing at Capital City Airport (FFT), Frankfurt, Kentucky. The commercial pilot was not injured and a flight instructor incurred minor injuries. The airplane was substantially damaged. The airplane was operated by Nexgen Aviation LLC as a Title 14 Code of Federal Regulations Part 91 instructional flight. Day, visual meteorological conditions prevailed near the accident site, and no flight plan was filed. The flight originated at Blue Grass Airport (LEX), Lexington, Kentucky about 0910, and was destined for FFT. The rated pilot in the left seat was receiving instruction to obtain a commercial multiengine rating. According to the flight instructor in the right seat, a practice localizer approach to runway 25 at FFT was requested and they received vectors for the approach. The instructor briefed for the pilot to perform a simulated left engine out approach to a full stop. The emergency single engine procedure was briefed, the landing gear were lowered and the flaps were confirmed up. The left engine was set to zero thrust. While over runway 25, at a point between the runway numbers and the 1,000 ft mark on the runway, about 20 feet above the landing surface, the pilot under instruction added power to the right engine while below minimum controllable airspeed. This occurred before the flight instructor could stop him. The airplane reacted quickly with a yaw and roll to the left. The airplane contacted the ground between the runway and parallel taxiway, continued across the taxiway, and down an embankment. The airplane came to rest about 150 ft from the taxiway and caught fire. Both pilots egressed the airplane and were met by first responders. The pilot receiving instruction reported that he maneuvered the airplane to an extended final approach to runway 25. Once established on final, he noticed that the altitude was lower than the previous approach. Once he determined that he had the runway "made," he began to reduce power on the right engine. The aircraft "settled low," so he added right throttle to re-establish the glide path. In doing so, he did not add the required control inputs of aileron and rudder. The approach became unstable, and he announced, "go around" and moved the right throttle full forward. The airplane immediately entered an uncontrollable left yaw and roll and struck the ground in a left-wing low attitude. He later reported that there were no mechanical malfunctions or failures that would have precluded normal operation of the airplane. Inspectors with the Federal Aviation Administration responded to the accident site and examined the wreckage. Both wings and the fuselage were structurally damaged from impact and the postaccident fire. The pilot in the left seat was receiving instruction to obtain a commercial multiengine rating and was performing a practice left engine-out approach. He indicated that he determined that he had the runway "made" and reduced throttle on the right engine. He stated that the airplane "settled" too much, and he added throttle without compensating with the appropriate aileron and rudder inputs. The approach became unstable, and he called for a go-around and added full right throttle while the airplane was below minimum controllable airspeed. The instructor indicated that this occurred before he could stop the pilot and that the airplane reacted quickly with a yaw and roll to the left. The airplane collided with the ground in a left-wing-low attitude, caught fire, and sustained substantial damage from the impact forces and postaccident fire. The pilot reported that there were no mechanical malfunctions or failures that would have precluded normal operation of the airplane. 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-Yaw control-Not attained/maintained - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Lateral/bank control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2019_ERA19TA105.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 (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NTSB Aircraft Accident Reports 2021 · Accident report
Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
- NTSB Aircraft Accident Reports 2018 · Accident report
Atlas Air Flight 3591 Boeing 767 Loss of Control (preliminary)
Atlas Air 3591 / Boeing 767-300 / Trinity Bay TX (Feb 23 2019) — preliminary. Preliminary investigation findings; superseded by the AAR-21/01 final report.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
Browse the full corpus — academia portal ↗