FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02LA071 · Beech C-24R

24 Mar 2002 · Bayou La Batre, AL, United States

Beech C-24R · Accident: loss of control in flight on approach

From Mobile Downtown Airport (BFM) to Roy E. Ray Airport (5R7)

Report a problem

Event

NTSB case
MIA02LA071
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 C-24R

Aircraft type
Beechcraft C-24
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
N18891
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mobile Downtown Airport (BFM), Mobile, ALTo Roy E. Ray Airport (5R7), Bayou La Batre, AL
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
Approach · VFR go-around
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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Pilot in command › Directional control, not maintained

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

NTSB narrative

According to the pilot, his landing attempt resulted in a high flare, hard touchdown, and bounce. His attempt to go around resulted in a left drift off the left side of the runway and collision with adjacent trees due to his failure to attain the proper climb speed and to maintain directional control.

Probable cause

The pilot's failure to maintain aircraft directional control while executing a go-around, resulting in an inflight collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02LA071
Event ID
20020327X00406
Case number
MIA02LA071
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: ab9da8e4d2554cb681926b0de7501d71890ba4d29cc05139a308da27635b96c0; retrieved 2026-09-22T11:03:29.827Z.