FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04IA010 · Beech 58

1 Oct 2003 · Columbus, MS, United States

Beech 58 · Incident: wheels up landing

From Columbus Lowndes County Airport (UBS) to Columbus Lowndes County Airport (UBS)

Report a problem

Event

NTSB case
ATL04IA010
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
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 58

Aircraft type
Beechcraft 58
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
N7219H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Columbus Lowndes County Airport (UBS), Columbus, MSTo Columbus Lowndes County Airport (UBS)
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 · flare/touchdown
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
Wheels up landing
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 › Checklist, not followed
  • Pilot in command › Gear extension, not performed

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

NTSB narrative

Upon returning to the airport the pilot requested a traffic advisory and a glider pilot announced he was in the traffic pattern for runway 36. The pilot announced that he would extend his downwind and base to final to give the glider time to land. He stated that he went through his pre-landing checklist but elected not to lower the gear at that time, instead he lowered the flaps and proceeded to turn base to final. He said that he spotted the glider on the ground about one mile out on final and proceeded to land and forgot that he had not lowered his landing gear until he heard the gear warning horn and landed with the gear retracted. The pilot did not report a mechanical problem with the airplane during the landing. According to the pilot, he had accumulated over 750 landings in retractable geared airplanes and had never forgot to put the gear down until now.

Probable cause

The pilot's failure to follow the pre-landing checklist, and his failure to extend the landing gear which resulted in a wheels up landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04IA010
Event ID
20031016X01745
Case number
ATL04IA010
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: 9143a5cce616ab473436ee51c70df25c9545bc5e284f5054117e89814e2e3a62; retrieved 2026-09-22T08:25:34.364Z.