FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02FA041 · Convair Div. of Gen. Dynamics 340-580STC

6 Dec 2001 · Sunny Isles Bch, FL, United States

Trans Air Link Convair Div. of Gen. Dynamics 340-580STC · Accident before flight

From Fort Lauderdale Hollywood International Airport (KFLL) to Miami-Opa Locka Executive Airport (KOPF)

Report a problem

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

Event

NTSB case
MIA02FA041
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
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
Visual Meteorological Cond

Convair Div. of Gen. Dynamics 340-580STC

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
N582HG
Onboard fatalities
Unknown
Route
From Fort Lauderdale Hollywood International Airport (KFLL), Fort Lauderdale, FLTo Miami-Opa Locka Executive Airport (KOPF), Opa-Locka, 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 Possible conflict
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
Prior to flight
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
Miscellaneous/other
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
Fuel exhaustion
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/operator management › Dispatch procedures, inadequate
  • Pilot in command › Aircraft preflight, 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 airline completed weight and balance and dispatch release forms for the initial flight showed an incorrect fuel load at the time the engines were started. The first officer performed a walk-around before the first flight leg which included checking the fuel tanks. A total of 460 gallons of fuel were added to the fuel tanks, and a delay loading cargo occurred. After both engines were started to begin the first flight, the engines remained operated for between 9-10 minutes before they were secured due to a radio problem. Maintenance personnel reracked the VHF radios, and again the engines were started where the airplane remained on the ramp 3-4 minutes before taxiing to the runway. The airplane remained at the runway hold short area for between 20 and 25 minutes before returning to the ramp due to a radio problem. The engines were secured, and a new VHF radio was purchased and installed. The company did not prepare new dispatch release, or weight and balance forms for the flight taking into account the additional fuel consumed with the engines operating. The engines were started, and the airplane was taxied to the runway and departed for the planned first leg. The airplane landed uneventfully at the destination airport where the cargo was offloaded. The first officer performed a walk-around which included checking the fuel tanks; 300 gallons of fuel were added to the fuel tanks (150 gallons in each side). The flight departed to return and when near the coastline, the flight was vectored to an airport other than the planned destination due to a issue with U.S. Customs. The flight landed uneventfully, and experienced a delay clearing customs. While on the ground before departure on the accident flight, the first officer reportedly performed a walk-around which included checking the fuel tanks with the captain looking on. The first officer reported that each fuel tank had approximately 1,100 pounds of fuel, and he and the captain both agreed before takeoff as to the quantity of fuel on-board as indicated by the magna-sticks. No fuel was purchased. Following starting of both engines for the accident flight, the first officer checked the fuel quantity gauges indications against the magna-sticks indications he observed; the fuel quantity gauges indicated approximately 200 pounds more. The flight departed, proceeded eastbound, and climbed to approximately 2,100 feet msl. During a right turn from a southeast to westerly heading, the right engine experienced a loss of horsepower which decreased from 900 to zero. The right engine was secured as a precaution, and priority handling to the destination airport was requested with air traffic control. The left engine horsepower remained the same (900) for a period of 31 seconds following the right engine horsepower decrease, then increased to 2,200, and remained at that value for 1 minute 13 seconds. The left engine horsepower then began to decrease and dropped to zero. The airplane was turned to the east, then turned to the south and ditched. The captain and first officer evacuated but remained with the airplane, and made it to shore where the first officer advised his wife that something was wrong with the fuel gauges. Following recovery of the airplane, pressure testing of the left fuel tank revealed no evidence of preimpact leakage. Pressure testing of the right fuel tank revealed slight leakage past the fuel cap. Boroscope examination of the engines, and functional test of each engine ignition system, fuel control units and fuel pumps revealed no evidence of preimpact failure or malfunction. Examination of the installed magna-sticks revealed no evidence of preimpact failure. The left fuel tank was drained and found to contain 2 gallons of Jet A fuel, while the right fuel tank was drained and found to contain approximately 540 gallons of salt water and 1/2 gallon of Jet A fuel. Fuel consumption calculations performed by FAA personnel revealed that at the time of engine start for the accident flight, the fuel tanks contained approximately 714 pounds of fuel. According to a representative of the engine manufacturer, the amount of fuel drained from the engine components post accident was consistent with, "low residual fuel."

Probable cause

The inadequate dispatch of the airplane by company personnel prior to the first leg of the flight due to failure of company personnel to prepare a new flight release and weight and balance after considerable time on the ground with the engines operating. Also causal, was the inadequate preflight of the airplane by the captain by which he failed to note the low level of fuel in the fuel tanks before departure resulting in total loss of engine power of both engines due to fuel exhaustion and subsequent ditching of the airplane. A finding in the accident was the inaccurate fuel quantity gauges.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02FA041
Event ID
20011213X02394
Case number
MIA02FA041
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-12-07.
  • API snapshot SHA-256: 0645085eb16c18ab9ad7b55ff0696947bc89883d453e8060849b6291e8743301; retrieved 2026-09-21T19:48:22.653Z.