FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL03LA038 · Beech 200

30 Jan 2003 · Jackson, MS, United States

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

From Jackson-Medgar Wiley Evers International Airport (JAN) to Bruce Campbell Field (MBO)

Report a problem

Event

NTSB case
ATL03LA038
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 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
N208F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jackson-Medgar Wiley Evers International Airport (JAN), Jackson, MSTo Bruce Campbell Field (MBO), Madison, MS
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 · climb to 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
Substantial

Cause areas

  • Landing gear › Failure

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

NTSB narrative

The pilot informed the controller after takeoff that he had an unsafe landing gear light on initial climb out. He departed the airport traffic area to conduct the abnormal emergency procedures which were uneventful. The pilot requested to fly by the tower to see if the landing gear was down. The controller informed the pilot during the fly by that the landing gear appeared to be down. The pilot entered the traffic pattern for a visual approach to runway 16L. On touchdown the left and right main landing gear collapsed. Examination of the airplane and the landing gear system revealed no deficiencies.

Probable cause

The failure of the landing gear system for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL03LA038
Event ID
20030203X00144
Case number
ATL03LA038
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-01-31.
  • API snapshot SHA-256: 06999901af0d2960ad9d59c7d98dfa53ed2ffca0e2f58dc5febe4e87b79697b5; retrieved 2026-09-22T09:38:08.054Z.