FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20CA296 · Beech 55 95A55

24 Aug 2020 · Nashville, TN, United States

Beech 55 95A55 · Accident: abnormal runway contact during landing

From Music City Executive Airport (XNX) to Nashville International Airport (BNA)

Report a problem

Event

NTSB case
ERA20CA296
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 55 95A55

Aircraft type
Beechcraft 55
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
N8629M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Music City Executive Airport (XNX), Gallatin, TNTo Nashville International Airport (BNA), Nashville, TN
Aircraft age
About 57 years (built 1963)
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
Landing · flare/touchdown
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
Abnormal runway contact
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

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot was on her second flight of multi-engine flight instruction as she completed an approach and flared the airplane for landing. The instructor said his attention was "outside" as he monitored the airplane's height, drift, runway alignment, and guarded the throttles.

The airplane suddenly landed hard, bounced back into the air, and did not respond as expected to the instructor's remedial actions. The engines responded to an increase in throttle for a go-around, but there was no corresponding increase in thrust. The airplane drifted to its left, and the instructor chose to close the throttles, and perform a controlled landing. The airplane departed the runway surface and came to rest in the grass infield with substantial damage to the fuselage forward of the cockpit.

According to the instructor, there were no deficiencies in the performance and handling of the airplane. The student pilot had experienced a negative habit transfer from her experience in the airplane she was accustomed to flying as the configuration of its throttle quadrant differed from the accident airplane and she had inadvertently reduced (feathered) the propellers rather than reducing the throttles while landing.

Probable cause

The pilot's inadvertent feathering of the propellers during the landing flare, which resulted in a hard landing. A factor in the accident was the instructor's failure to fully monitor the pilot's manipulation of the levers in the airplane's non-standard throttle quadrant.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20CA296
Event ID
20200824X70655
Case number
ERA20CA296
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. 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: ac27b3633cfb043f99f83df6693ed5fa0d1376a84055b0c476bf1362619a66e5; retrieved 2026-09-16T12:55:29.894Z.