FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA04FA049 · Beech C90

31 Jan 2004 · Homestead, FL, United States

Beech C90 · Accident: in flight encounter with weather en route

From Florida Keys Marathon International Airport (KMTH) to Fort Lauderdale Executive Airport (KFXE)

Report a problem

Event

NTSB case
MIA04FA049
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
2 · 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
Instrument Meteorological Cond

Beech C90

Aircraft type
Beechcraft 90
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
N75GC
Operator
Saul Zadik
Onboard fatalities
Unknown
Route
From Florida Keys Marathon International Airport (KMTH), Marathon, FLTo Fort Lauderdale Executive Airport (KFXE), Fort 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 · descent
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 encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › In-flight planning/decision, inadequate

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

NTSB narrative

The instrument rated pilot received three weather briefings on the date of the accident from the Miami Automated Flight Service Station. The pilot obtained his IFR clearance while airborne, was advised to climb to 9000 feet mean sea level (MSL), then later advised to descend and maintain 2000 feet, and to fly heading 030 degrees. Radar data indicates that following the instruction from the controller, the airplane made a right descending turn to a southeasterly heading, followed by a left turn to an easterly heading where the airplane was lost from radar while at 2,200 feet mean sea level. The crash was located 138 degrees and .38 nautical mile from the last radar target. Between 1631:04, and 1631:16, the airplane descended from 7,600 to 6,100 feet. Between 1631:16, and the last radar target 12 seconds later at 1631:28, the airplane descended 3,900 feet. Weather radar data indicates the airplane encountered video integrator and processor (VIP) Level 2, or "moderate intensity" echoes in the area of the in-flight loss of control. Approximately 10 and 20 miles east-northeast through southeast of the accident site, maximum echoes of VIP Level 5 to 6, or "intends to extreme intensity" echoes were noted. The strongest reflectivities were located 20 miles east of the accident site. Disintegration of the airplane was noted; there was no evidence of in-flight, or post crash fire of any recovered components. The full span of the left wing, left aileron, left horizontal, and left elevator were accounted for. A section of the right wing and right outboard flap was identified; the right wing was fragmented. Examination of the engine and propellers revealed no evidence of preimpact failure or malfunction. No determination was made whether the pilot met the instrument recency of experience requirement of 14 CFR Part 61.57 (c).

Probable cause

The pilot's inadequate in-flight planning/decision which resulted in an encounter with rain showers and turbulence, a loss of aircraft control, and overstress of the airframe.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA04FA049
Event ID
20040212X00188
Case number
MIA04FA049
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: 8ee5504c90f346c5c7689176dadfc6c7f4b274bdfde51b1e17f2d77e3db4e1ef; retrieved 2026-09-20T18:35:23.167Z.