ATL83LA190 · Cessna 414
Cessna 414 · Accident: hard landing
From Capital City Airport (FFT) to an unrecorded destination
Event
- NTSB case
- ATL83LA190
- 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
- 0
- 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
Cessna 414
- Aircraft type
- Cessna 414
- 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
- N666JD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Capital City Airport (FFT), Frankfort, KYTo not recorded
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Pilot in command › Compensation for wind conditions, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING ARRIVAL, THE PILOT MADE HIS LANDING APPROACH TO RWY 14 WITH A X-WIND FROM 230 DEG, GUSTING FROM 6 TO 22 KTS. THE AIRPORT WAS ON A KNOLL & THE TERRAIN SLOPED DOWNWARD FROM THE APPROACH END OF THE RUNWAY. THE PLT STATED THAT AS THE ACFT WAS FLYING OVER THE LOW TERRAIN ON FINAL APPROACH, IT ENCOUNTERED A DOWNDRAFT. HE CORRECTED WITH POWER, BUT THE ACFT TOUCHED DOWN ON THE END OF THE RWY, A GUST OF WIND LIFTED THE RIGHT WING, THEN THE LEFT GEAR SLAMMED DOWN & COLLAPSED. SUBSEQUENTLY, THE OTHER 2 GEAR COLLAPSED IN MUDDY TERRAIN BEFORE THE ACFT CAME TO REST.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83LA190
- Event ID
- 20001214X42614
- Case number
- ATL83LA190
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 28b6075342eb68a3870d79c0b4134af213111e4dbf09bb0f13a4786165a6d0e6; retrieved 2026-09-23T22:20:35.525Z.