FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04IA119 · Beech 200

18 May 2004 · Millington, TN, United States

Beech 200 · Incident: airframe, component or system failure en route

From Walnut Ridge Regional Airport (ARG) to Frederick W. Smith International Airport (MEM)

Report a problem

Event

NTSB case
ATL04IA119
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
Incident
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

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
N500KA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Walnut Ridge Regional Airport (ARG), Walnut Ridge, ARTo Frederick W. Smith International Airport (MEM), Memphis, TN
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
En route · cruise
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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Pilot in command › Emergency procedure, not followed
  • Pilot in command › Gear extension, not attained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While in cruise flight the airplane experienced a complete loss of electrical power. The pilot diverted to an alternate airport to land. While enroute, the pilot lowered the landing gear using emergency extension procedures. In accordance with the Airplane Pilot Operating Handbook, the pilot did not continue pumping the landing gear extension lever until sufficient resistance was felt to ensure the landing gear was down and locked. The main landing gear collapsed on touchdown. A functional test of the landing gear system revealed no anomalies.

Probable cause

The pilots failure to follow the checklist for emergency landing gear extension resulting in the collapse of the main landing gear on touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04IA119
Event ID
20040525X00662
Case number
ATL04IA119
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, coordinates. 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: f7f91ac348f6ec56c4fdbaef5d5e242f3070f9b22d54f0d9a5b047d195f96edd; retrieved 2026-09-22T07:31:58.712Z.