FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA356 · Beech A36

20 Mar 2009 · Charleston, MO, United States

Morley Tower Beech A36 · Accident: landing gear collapse

From Mississippi County Airport (CHQ) to Mississippi County Airport (CHQ)

Report a problem

Event

NTSB case
CEN09CA356
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 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
N451S
Operator
Morley Tower
Onboard fatalities
Unknown
Route
From Mississippi County Airport (CHQ), Charleston, MOTo Mississippi County Airport (CHQ), Charleston, MO
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
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
Landing gear collapse
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 systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that he had landed uneventfully at the conclusion of a local flight. However, during the landing rollout the pilot stated that he mistakenly selected the landing gear handle instead of the flap handle. As a result, the nose landing gear collapsed, damaging the nose gear support fittings and nose gear assembly. The pilot noted that there were no failures or malfunctions associated with the airplane prior to the accident.

Probable cause

The pilot's inadvertent use of the landing gear selector handle instead of the flap handle during landing rollout, which resulted in the collapse of the nose landing gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA356
Event ID
20090615X53614
Case number
CEN09CA356
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: 31689be5a85f17090d1ac948771d13f821294402dc7a473ab105913a97da500d; retrieved 2026-09-15T11:26:28.940Z.