ERA19TA105 · Beech 76
Nexgen Aviation Beech 76 · Accident: loss of control in flight on approach
From Blue Grass Airport (LEX) to Capital City Airport (FFT)
Event
- NTSB case
- ERA19TA105
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech 76
- Aircraft type
- Beechcraft 76
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N7KY
- Operator
- Nexgen Aviation
- Onboard fatalities
- Unknown
- Route
- From Blue Grass Airport (LEX), Lexington, KYTo Capital City Airport (FFT), Frankfort, KY
- Aircraft age
- About 40 years (built 1979)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR go-around
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The pilot's failure to maintain airplane control during a simulated single-engine go-around, which resulted in a collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19TA105
- Event ID
- 20190221X55457
- Case number
- ERA19TA105
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e8c71025fed228bdbdd1526ef46b59ca831e0b49119e8681d45984128498f910; retrieved 2026-09-16T08:36:28.688Z.