No fatalities

2004-02-20: Learjet 25 (N24RZ) — Skylink Jets — Fort Lauderdale-Executive, United States of America

Fort Lauderdale-Executive, United States of AmericaLanding (descent or approach)

On February 20, 2004, a Learjet 25 (registration N24RZ) operated by Skylink Jets was involved in an aviation accident near Fort Lauderdale-Executive, United States of America during landing or approach. No fatalities were reported. Investigators recorded the probable cause as: The pilot in command's misjudged distance/speed while landing, and the flightcrew's failure to follow prescribed emergency procedures, which resulted in a runway overrun and subsequent collision with a building. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A).

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781200501Data APIEditorial standards
Aircraft registered N24RZ
Aircraft registered N24RZ. Photo: Aeroprints.com / CC BY-SA 3.0, via Wikimedia Commons

A Part 135 charter flight experienced a runway overrun after encountering stronger headwinds, low fuel, and a hydraulic failure that prevented full flap extension and normal brakes. The aircraft struck a fence, crossed a road, and hit a building.

Flight Details

The captain and first officer were conducting a CFR Part 135 on-demand charter flight, returning two passengers to the accident airplane's base airport. The multi-destination flight originated from the accident airport, about 16 hours before the accident.

Fuel Concerns and Priority Landing

On the final leg, the flight encountered stronger than anticipated headwinds. The first officer voiced his concern several times about the airplane's remaining fuel. As the flight approached the destination airport, the captain became concerned about having to fly an extended downwind leg and told the ATCT specialist the flight was low on fuel. The ATCT specialist then cleared the accident airplane for a priority landing.

Hydraulic and Flap Issues

According to cockpit voice recorder (CVR) data, while the crew was attempting to lower the airplane's wing flaps in preparation for landing, they discovered that the flaps would not extend beyond 8 degrees. After the landing gear was lowered, the captain told the first officer, in part: "The gear doors are stuck down.... no hydraulics." The captain added: "Okay, so we're gonna do, this is gonna be a ref and twenty... All right, probably not going to have any brakes..."

Landing and Overrun

According to an ATCT specialist in the control tower, the airplane touched down about midway on the 6,001-foot long, dry runway. It continued to the end of the runway, entered the overrun area, struck a chain link fence, crossed a road, and struck a building.

Emergency Systems and Postaccident Findings

During a postaccident interview, the captain reported that during the landing roll the first officer was unable to deploy the airplane's emergency drag chute. He said that neither he nor the first officer attempted to activate the nitrogen-charged emergency brake system. The accident airplane was not equipped with thrust reversers.

A postaccident examination of the accident airplane's hydraulic pressure relief valve and hydraulic pressure regulator assembly revealed numerous indentations and small gouges on the exterior portions of both components, consistent with being repeatedly struck with a tool. When the hydraulic pressure relief valve was tested and disassembled, it was discovered that the valve piston was stuck open.

The emergency drag chute release handle has two safety latches that must be depressed simultaneously before the parachute will activate. An inspection of the emergency drag chute system and release handle disclosed no preaccident mechanical anomalies.

Probable cause

The pilot in command's misjudged distance/speed while landing, and the flightcrew's failure to follow prescribed emergency procedures, which resulted in a runway overrun and subsequent collision with a building.