FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC82FA174 · Cessna 421A

24 Sept 1982 · Sabetha, KS, United States

Cessna 421A · Accident: main gear collapsed during landing

From C · Topeka, KS to C · Sabetha, KS

Report a problem

Event

NTSB case
MKC82FA174
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 421A

Aircraft type
Cessna 421
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
N2231Q
Operator
Guy E. Counselman · private individual
Onboard fatalities
Unknown
Route
From C · Topeka, KSTo C · Sabetha, KS
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 · landing roll
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
Main gear collapsed
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

  • Reason for occurrence undetermined

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

NTSB narrative

THE PLT STATED THAT THE GEAR INDICATED DOWN AND LOCKED PRIOR TO LANDING AND DURING THE FIRST PART OF THE LANDING ROLL. AFTER ABOUT 1,000 FT OF ROLL THE PLT GOT AN UNSAFE INDICATION AND THE LEFT WING BEGAN TO SETTLE. AFTER THE LEFT GEAR COLLAPSED THE ACFT SWERVED TO THE LEFT OFF THE RWY. THE BOLT, P/N NAS464P4-26, WHICH ATTACHES THE BELLCRANK, PN 5041001-1, TO THE STRUT WAS SHEARED AND ONE SIDE OF THE CLEVIS AT THE LOWER END OF THE BELLCRANK. BOTH OF THESE BROKEN COMPONENTS COULD BE ASSOCIATED WITH OVERLOAD CONDITIONS INDUCED WHEN THE GEAR COLLAPSED AND NEITHER SHOWED EVIDENCE OF PREVIOUS DAMAGE. THERE WAS NO EVIDENCE OF A HARD LANDING. THE LANDING GEAR COMPONENTS APPEARED TO HAVE ADEQUATE LUBRICATION. DUE TO IMPACT DAMAGE THE RIGGING OF THE RETRACTION LINKAGE PRIOR TO THE ACCIDENT COULD NOT BE DETERMINED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MKC82FA174
Event ID
20020917X04965
Case number
MKC82FA174
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: c88360973940732d7b726ba5a16259f00b7abec323b9173eb181dfa9f41fa7e3; retrieved 2026-09-24T00:44:27.114Z.