FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Air Network Gates Learjet 25C accident

30 Aug 2002 · Lexington, KY, United States

Gates Learjet 25C · Accident: overrun during landing

From Marco Island Executive Airport (MKY) to Blue Grass Airport (LEX)

Report a problem

Event

NTSB case
NYC02FA177
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
1 · 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
Charter & commuter
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

Gates Learjet 25C

Aircraft type
Learjet 25
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
N45CP
Onboard fatalities
Unknown
Route
From Marco Island Executive Airport (MKY), Marco Island, FLTo Blue Grass Airport (LEX), Lexington, KY
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 135: Air Taxi & Commuter
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
Destroyed

Cause areas

  • Pilot in command › Improper use of equipment/aircraft

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

NTSB narrative

Shortly before landing, the crew confirmed that the hydraulic and emergency air pressures were "good", and that the circuit breakers on the "right and left" were in. In addition, the first officer reported "arming one and two." The airplane landed 1,000 - 1,500 feet from the landing threshold of runway 04, which was 7,003 feet in length. The captain utilized aerodynamic braking during part of the landing roll. About 3 seconds after touchdown, the first officer stated, "they're not deployed, they're armed only." About 6 seconds after touchdown, there was an increase in engine rpm. Shortly after that, there was an expletive from the captain. One and a half seconds later, there was another expletive. Slightly less than 2 seconds later, the captain told the first officer to "brake me," and 2.7 seconds after that, stated "emergency brake." About 4 seconds later, there was a "clunk", followed by a decrease in engine rpm 1 second later. Immediately after that, the captain stated, "we're going off the end." The airplane subsequently dropped off an embankment at the end of the runway, impacted and descended through a localizer tower, then impacted the ground and slid across a highway. The airplane had been fitted with a conversion that included thrust reversers. An examination of the wreckage revealed that the thrust reversers were out of the stowed position, but not deployed. The drag chute was also not deployed. Brake calipers were tested with compressed air, and operated normally. Brake disc pads were measured, and found to be within limits. According to an excerpt from the conversion maintenance manual, reverser deployment was hydraulically actuated and electrically controlled. There was also an accumulator which allowed deploy/stow cycling in the event of hydraulic system failure. Interlocks were provided so that the reverser doors could not be deployed until the control panel ARM switch was on, the main throttle levers were in idle position, and the airplane was on the ground with the squat switches engaged. The previous crew reported no mechanical anomalies. Runway elevation rose by approximately 35 feet during the first 2/3 of its length, then decreased until it was 8 feet lower at its departure end. Winds were reported as being from 050 degrees true at 7 knots. At the airplane's projected landing weight, without the use of thrust reversers, the estimated landing distance was about 2,850 feet with the anti-skid operative, and 3,400 feet with the anti-skid inoperative.

Probable cause

The captain's addition of forward thrust during the landing rollout, which resulted in a lack of braking effectiveness and a subsequent runway overrun. A factor was the captain's inability to deploy the thrust reversers for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC02FA177
Event ID
20020916X01611
Case number
NYC02FA177
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: 1dee3d75bf9ae6ad720baa949d8479e1e557d3698b58d7a6bc192fc2c91541b4; retrieved 2026-09-18T13:04:13.314Z.