ERA22LA101 · Beech B19
Beech B19 · Accident: hard landing
From Tompkinsville Monroe County Airport (TZV) to an unrecorded destination
Event
- NTSB case
- ERA22LA101
- 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
- Event fatalities
- Unknown
- 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 B19
- Aircraft type
- Beechcraft 19
- 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
- N24605
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tompkinsville Monroe County Airport (TZV), Tompkinsville, KYTo not recorded
- Aircraft age
- About 50 years (built 1972)
- 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
- Hard landing
- 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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported to the Federal Aviation Administration (FAA) inspector that he was planning to demonstrate to the student how to land on the numbers for the runway and set up his approach accordingly. He believed that while crossing the road adjacent to the airport, the sun visor slipped down and after seeing a fence, pulled aft on the control yoke but was too late. The student pilot stated that he saw the flight was, “coming down really fast” and he was about to say something to the flight instructor and pull the control yoke but the airplane impacted the fence with the landing gear. The pilot reported that there were no pre-accident mechanical malfunctions or anomalies that would have precluded normal operation.
A post-accident examination revealed substantial damage to the engine mount and wrinkles to the lower and upper skins of the left wing.
Probable cause
The failure of the certified flight instructor to attain the proper glidepath which resulted in a collision with a fence and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA101
- Event ID
- 20220105104491
- Case number
- ERA22LA101
- 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, cause areas. 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: 9fe1b457a54c73dd6ebe1108e04bccab68ceda1bb3fe9daf7760da369e0c537a; retrieved 2026-09-16T14:52:16.742Z.