ERA20CA283 · Beech 36 A36
Beech 36 A36 · Accident: loss of control in flight during landing
From Murray-Calloway County Airport Kyle-Oakley Field (CEY) to Murray-Calloway County Airport Kyle-Oakley Field (CEY)
Event
- NTSB case
- ERA20CA283
- 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 36 A36
- Aircraft type
- Beechcraft 36
- 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
- N312LC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Murray-Calloway County Airport Kyle-Oakley Field (CEY), Murray, KYTo Murray-Calloway County Airport Kyle-Oakley Field (CEY), Murray, KY
- Aircraft age
- About 16 years (built 2004)
- 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
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor and private pilot were practicing a steep spiral that would terminate with a power-off landing. The instructor stated that the pilot had added "quite a bit" of elevator nose-up trim to maintain best glide speed during the spiral maneuver. Right before touchdown, the pilot sensed the airplane had a normal than higher descent rate and increased engine power. When power was added, the airplane’s nose pitched up and the airplane rolled “violently” to the left. The airplane’s left wing struck the runway, substantially damaging it. The flight instructor then assumed control of the airplane and reduced the engine power to idle as it departed the left side of the runway. The pilot subsequently taxied the airplane to the ramp uneventfully. Both pilots reported there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain control of the airplane during the simulated power off landing, and the flight instructor's delayed remedial action, which resulted in a loss of control and the airplane’s left wing striking the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA283
- Event ID
- 20200812X83136
- Case number
- ERA20CA283
- 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: 615f2f07de5e24d5ec5ff0df432ee76bdcc7a4194388526c9e601e36c53f54a2; retrieved 2026-09-16T12:33:01.449Z.