FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Butler Aviation Beech 200 accident

10 Dec 2009 · St. Louis, MO, United States

Beech 200 · Accident: landing gear not configured

From Charles B. Wheeler Downtown Airport (MKC) to St. Louis Lambert International Airport (STL)

Report a problem

Event

NTSB case
CEN10LA076
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
Charter & commuter
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 200

Aircraft type
Beechcraft 200
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
N411BL
Onboard fatalities
Unknown
Route
From Charles B. Wheeler Downtown Airport (MKC), Kansas City, MOTo St. Louis Lambert International Airport (STL), St. Louis, 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 135: Air Taxi & Commuter
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
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 not configured
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 › Task performance

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

NTSB narrative

The pilot reported that the landing gear failed to extend prior to landing. His attempts to manually extend the landing gear in accordance with the manual extension procedure from the airplane flight manual were not successful. He subsequently executed an emergency gear-up landing. A postaccident inspection revealed that the emergency gear engagement handle was not in the engaged position. When the handle was engaged, subsequent movement of the extension lever manually lowered the landing gear. Further examination revealed that the landing gear motor circuit breaker was open (popped). The landing gear motor and circuit breaker were located under the cabin floor aft of the forward wing spar. When the circuit breaker was reset and electrical power applied to the airplane, the landing gear was successfully extended using the normal procedure.

Probable cause

The pilot's failure to properly follow the manual landing gear extension procedure, resulting in a gear-up landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10LA076
Event ID
20091215X64622
Case number
CEN10LA076
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-12-11.
  • API snapshot SHA-256: 9eded510a9a27da059316833e68ff3c02e23fbef111d9b62cc156f81f10ecdcc; retrieved 2026-09-15T13:34:26.451Z.