MIA95LA050 · Beech 95-C55
Beech 95-C55 · Accident: on ground/water encounter with weather during landing
From Leesburg International Airport (LEE) to an unrecorded destination
Event
- NTSB case
- MIA95LA050
- 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
- Instrument Meteorological Cond
Beech 95-C55
- Aircraft type
- Beechcraft 55
- 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
- N546V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Leesburg International Airport (LEE), Leesburg, FLTo not recorded
- 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 · landing roll
- 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 encounter with weather
- 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 › In-flight planning/decision, poor
Approximate · Estimated position: the centre of Arcadia, FL, the place the record names. Not the accident site.
NTSB narrative
THE PILOT OBTAINED A WEATHER BRIEFING FROM THE TV WEATHER CHANNEL BEFORE DEPARTURE AND FOG WAS NOT MENTIONED NOR DID THE PILOT OBTAIN ANY OTHER WEATHER BRIEFING. UPON ARRIVAL AT THE DESTINATION AIRSTRIP HE CIRCLED SEVERAL TIMES UNTIL LIGHT CONDITIONS IMPROVED. HE LANDED WITH THE FLAPS FULLY EXTENDED, ENCOUNTERED FOG, AND DID NOT FULLY APPLY THE NORMAL BRAKES TO STOP. REALIZING THAT THERE WAS INSUFFICIENT RUNWAY REMAINING TO STOP HE APPLIED THROTTLE TO GO AROUND; HOWEVER, HE DID NOT RETRACT THE FLAPS. THE AIRPLANE BECAME AIRBORNE BUT COLLIDED WITH A GATE, TREES, THEN THE GROUND.
Probable cause
POOR IN FLIGHT PLANNING/DECISION BY THE PILOT FOR ELECTING TO LAND WITH FOG ON THE AIRSTRIP. CONTRIBUTING TO THE ACCIDENT WAS FAILURE OF THE PILOT TO OBTAIN A FORMAL PREFLIGHT WEATHER BRIEFING AND HIS FAILURE TO FULLY APPLY THE BRAKES (NORMAL) AFTER LANDING. ALSO CONTRIBUTING TO THE ACCIDENT WAS FAILURE OF THE PILOT TO RETRACT THE FLAPS FROM THE FULLY EXTENDED POSITION DURING THE ABORTED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA95LA050
- Event ID
- 20001206X02777
- Case number
- MIA95LA050
- 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: 8ecb62534fa0230e2a7f551bc3407c74142d209ce43a747b7bd6d7618bae6735; retrieved 2026-09-21T13:28:40.700Z.