FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA04FA107 · Learjet 55

19 Jul 2004 · Fort Lauderdale, FL, United States

Hop A Jet Learjet 55 · Accident: overrun during landing

From Fort Lauderdale Hollywood International Airport (KFLL) to Fort Lauderdale Executive Airport (KFXE)

Report a problem

Event

NTSB case
MIA04FA107
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
Instrument Meteorological Cond

Learjet 55

Aircraft type
Learjet 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
N55LF
Operator
Hop a Jet
Onboard fatalities
Unknown
Route
From Fort Lauderdale Hollywood International Airport (KFLL), Fort Lauderdale, FLTo Fort Lauderdale Executive Airport (KFXE), 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
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
Overrun
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

  • Flightcrew › Flight into adverse weather, continued
  • Flightcrew › In-flight planning/decision, improper

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

NTSB narrative

The flight was a VFR positioning flight from FLL to FXE. Transcripts of the cockpit voice recorder (CVR) showed that while waiting for takeoff from FLL the flightcrew heard the local controller reported to a Delta Airlines flight that was on a seven mile final approach to land on runway 27R that the winds were 250 degrees at 19 knots, gusting to 50 knots. The Delta Airlines flight crew then informed the controller they were making a missed approach. At 1130:05 the captain asks the first officer if "can you see the end of the weather? If we make a hard right turn, can we stay clear of it?" The first officer responded "I believe so." At 1130:06 the local controller reported "wind shear alert. The centerfield wind 230 at 22. Runway 27R departure 25 knot loss one mile departure." The captain stated to the first officer "sweet." At 1132:11 the captain transmitted to the local controller "tower, any chance of Hop-a-Jet 55 getting out of here?" The local controller responded wind 230 at 17, right turn direct FXE approved, runway 27R cleared for takeoff. The captain responded "cleared to go, right turn out." At 1133:10 the captain asks for gear up. At 1133:15 the local controller responded to a Southwest Airlines Flight waiting for takeoff "no, don't look like anyone's gonna go." "The uh, weather is due west moving rapidly to the north. It looks like a few minutes, and you all be in the clear straight out." At 1133:17, the captain stated to the first officer "oh #. Think this was a bad idea." The first officer responded "no airport in sight." At 1133:43 the sound similar to precipitation hitting the windshield is recorded. At 1133:46 the FLL local controller instructs the flight crew to contact FXE Tower. At 1133:54 the CVR records the FXE local controller transmitting "wind 200, variable 250 at 15, altimeter 29.99. Heavy cell of weather to the west moving eastbound. Low level wind shear possible. At 1134:16, the FXE local controller transmits "attention all aircraft, low level wind shear advisories are in effect. Use caution. Wind 240 at 10." At 1134:51, the first officer transmitted to the FXE local controller that the flight was over the shoreline inbound full stop. At 1135:02, the FXE local controller transmitted "Hop-a-Jet 55, Executive tower, wind 210 variable 250 at 35, 35 knots and gusting. Winds are uh, heavy on the field. Low level wind shear advisories are in effect. Heavy rains from the west, eastbound and would you like to proceed inbound and land Executive? Say intentions." The first officer responded "that's affirmative." The local controller responded, "Hop-a-Jet 55 straight in runway three one if able. The winds 230 gusts, correction, winds 230 variable 210 at 25." At 1135:48, the local controller transmitted, "Hop-a-Jet 55, wind 230 variable 300 at 25 gusts 35. Altimeter 30.00. Runways are wet. Traffic is exiting the runway prior to your arrival, a Dutchess. Caution standing water on runways. Low level wind shear advisories in effect, Runway 31. Cleared to land." The first officer responded "cleared to land, Hop-a-Jet 55." At 1136:35, the local controller transmitted "wind 230 at 25, gusts 35." At 1136:58, the CVR records the sound similar to precipitation on the windshield. At 1137:17, the CVR records a sound similar to the aircraft touching down on the runway. At 1137:19, the sound of a repetitive tone similar to the thrust reverser warning starts and continues to the end of the recording. At 1137:23 a loud unidentified roaring sound starts and lasts 8 seconds. At 1137:30, loud rumbling noises similar to the aircraft departing the runway start. At 1137:36, a continuous tone similar to landing gear warning signal sounds and continues to the end of the recording. The rumbling noises stop. At 1137:39 the captain states the thrust reversers didn't stow and at 1138:36, the captain states "I went around and the # TRs stayed. The CVR recording ended. The 1132, Goes-12 infrared image depicts a rapidly developing cumulonimbus cloud between and over the FLL and FXE airports. The top of the cloud over FXE was in the range of 22,000 feet. The top of the cloud southwest of FXE was in the 39,000 feet range. The 1145, Goes-12 infrared image depicts a developing cumulonimbus cloud over FXE with the cloud top in the 42,000 feet range. Data was obtained from the Melbourne, Florida Doppler Weather Radar System, located 118 miles north-northwest of the accident site. The data showed that at FXE, between 1130 and 1145, a VIP Level 1 to 2 echo evolved into a VIP Level 5 "intense" echo at 1135 and a VIP Level 6 "extreme" echo by 1145.

Probable cause

The flight crew's decision to continue the approach into known area of potentially severe weather (Thunderstorm), which resulted in the flight encountering a 30 knot cross wind, heavy rain, low-level wind shear, and hydroplaning on a ungrooved contaminated runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA04FA107
Event ID
20040726X01066
Case number
MIA04FA107
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: d8c7469b107ac5cac7bae858fe4f19d13e698ead86d4a5a82c91d2803326e4e1; retrieved 2026-09-22T07:02:24.124Z.