MIA96LA136 · Beech UC45J
Sky Charters Beech UC45J · Accident: airframe, component or system failure en route
From Miami-Opa Locka Executive Airport (OPF) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- MIA96LA136
- 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 UC45J
- Aircraft type
- Beechcraft 45
- 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
- N64819
- Operator
- Sky Charters
- Onboard fatalities
- Unknown
- Route
- From Miami-Opa Locka Executive Airport (OPF)To Fort Lauderdale Executive Airport (FXE), FT. LAUDERDALE, FL
- 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
- Airframe, component or system failure
- 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
- Company maintenance personnel › Maintenance, inspection, inadequate
- Fluid, fuel › Leak
- Fuel system, line › Rotted/weathered
- Fuel system, line › Ruptured
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During departure, the rubber connector for the fuel supply line to the right engine oil dilution valve split at the dilution valve on the aft side of the firewall. The engine would not operate unless the electric boost pump was turned on. While returning to the departure airport, a fire erupted in the right wheel after the landing gear was extended. The cockpit filled with smoke during the landing rollout, and the pilot lost directional control do to not being able to see. The aircraft rolled into a canal and came to rest. The split rubber fuel line connector was dry and brittle and did not have any fire damage. No other sources of fuel leakage was found.
Probable cause
inadequate inspection of the fuel line connector by company maintenance personnel, and failure of a connector resulting in a fuel leak and fire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96LA136
- Event ID
- 20001208X05830
- Case number
- MIA96LA136
- 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: 2af3a024e0d5f3b1f8b223814aaed4fa7112a0285ef1fa032c7b44d180c70f7d; retrieved 2026-09-22T22:32:50.760Z.