ATL82FKQ16 · Beech 58
Victor Airways Beech 58 · Accident: hard landing
From Bruce Campbell Field (MBO) to Bruce Campbell Field (MBO)
Event
- NTSB case
- ATL82FKQ16
- 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
- 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 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
- N1808L
- Operator
- Victor Airways
- Onboard fatalities
- Unknown
- Route
- From Bruce Campbell Field (MBO), Madison, 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
- 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
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Diverted attention
- Pilot in command › Level off, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT DURING FLIGHT, THE RIGHT FRONT DOOR SUDDENLY OPENED AFTER LIGHT TURBULENCE WAS ENCOUNTERED. THE PILOT FOLLOWED THE PROCEDURE, AS PRESCRIBED BY THE OWNER'S MANUAL, TO SECURE AND CLOSE THE DOOR. AS A PRECAUTION, HE CANCELED THE REMAINDER OF THE FLIGHT, AND RETURNED TO THE AIRPORT TO LAND. JUST BEFORE TURNING FROM DOWNWIND TO BASE LEG, THE DOOR SUDDENLY OPENED AGAIN. THE PILOT ELECTED TO CONTINUE THE APPROACH WITHOUT RECLOSING THE DOOR. THE DOOR BEGAN TO BUFFET AND LEFT RUDDER WAS USED TO COMPENSATE FOR YAW AND DRAG. WHILE LANDING, THE AIRCRAFT TOUCHED DOWN HARD AND BOUNCED. POWER WAS APPLIED TO CORRECT THE SITUATION. THE PLANE RESPONDED IN A SEVERE NOSE HIGH ATTITUDE WHILE SIMULTANEOUSLY BANKING SHARPLY TO THE LEFT. THE AIRCRAFT CRASHED TO THE LEFT OF THE RUNWAY. AS THE OCCUPANTS EGRESSED FROM THE PLANE, IT BEGAN TO BURN AND WAS DESTROYED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82FKQ16
- Event ID
- 20020917X02876
- Case number
- ATL82FKQ16
- 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. 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: 742fc7a1795b7e197be2c3a85f371407642fdff9ee37b64b899dfee81e846f0b; retrieved 2026-09-24T02:48:49.748Z.