FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA99LA145 · Beech E33

18 Apr 1999 · Orlando, FL, United States

Beech E33 · Accident: on ground/water collision with object during takeoff

From an unrecorded airport to Shreveport Downtown Airport (DTN)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
MIA99LA145
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 E33

Aircraft type
Beechcraft 33
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
N7204N
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From not recordedTo Shreveport Downtown Airport (DTN), Bossier City, LA
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
Takeoff · roll/run
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
On ground/water collision with object
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 › Aircraft control, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Airport personnel noticed that an airport sign was down, and saw tire tracks leading to the sign, plus there was a wing step found near the sign. The tire marks continued on the grass and tracked back to the runway. The FAA, issued a notice that they were searching for an airplane with a damaged step. The airplane was found at the Marion County Airport, Dunnellon, Florida. The FAA then located the pilot and owner. The pilot said on the takeoff roll the nosewheel lifted off the runway, but the engine lost manifold pressure, and the airplane departed the side of the runway. The pilot stated, '...on takeoff, we experienced a brief loss of power...a drop in airspeed and a cross wind caused aircraft to blow to the left of runway...aircraft began to stall, upon lowering of nose to prevent stall/crash-we struck runway sign...we did not know that aircraft was damaged until 30 minutes into flight...' According to the FAA's report, '...PIC [pilot-in-command] upon attempting a takeoff on runway 07...[about 1,000 feet down the runway, the airplane] departed the runway surface [north side] striking a...information sign, then continued the takeoff...landing at Dunnellon, Florida.'

Probable cause

the pilot's failure to maintain control of the airplane during takeoff, resulting in the airplane departing the runway, and subsequently impacting with an airport sign.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA99LA145
Event ID
20001205X00542
Case number
MIA99LA145
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: 58462a15e1c0fe0759e2b2df93cec7dd72fb1b7f0875bb146f1b4df5e83eb247; retrieved 2026-09-22T15:26:56.939Z.