MIA99LA139 · Beech 23
Beech 23 · Accident: in flight collision with object en route
From Cox Airport (NC81) to Orangeburg Municipal Airport (OGB)
Event
- NTSB case
- MIA99LA139
- 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 23
- Aircraft type
- Beechcraft 23
- 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
- N9249S
- Operator
- Dennis Harrell
- Onboard fatalities
- Unknown
- Route
- From Cox Airport (NC81)To Orangeburg Municipal Airport (OGB), Orangeburg, SC
- 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
- In flight collision with object
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had taxied the airplane to runway 09, and planned a short field takeoff. He ran the engine to full power, released the foot brakes, applied full right rudder, in anticipation of the airplane yawing to the left, and applied back pressure on the yoke. As the nose rotated, the stall warning horn sounded and the airplane drifted to the right. The pilot applied left aileron, but never released the right rudder pedal. The airplane continued to drift right until it struck a tree, turning the airplane hard to the right, and striking the next tree with the spinner of the propeller. The airplane came to rest opposite the direction of takeoff, against a clutter of trees, supported by the left wing
Probable cause
the pilot's failure to maintain control of the airplane resulting in the airplane drifting, and subsequently impacting with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA139
- Event ID
- 20001205X00540
- Case number
- MIA99LA139
- 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: eacc093c4d3d590293431ba2aa426232e5df073d20bb54dafc36512f37c7db3d; retrieved 2026-09-21T11:08:20.909Z.