Jetstream 4101United Express
Charlottesville, VA, USA · 2000-12-30·N323UE
What happened
NTSB summary, verbatimThe twin-engine turbo-prop airplane touched down about 1,900 feet beyond the approach end of the 6,000-foot runway. During the rollout, the pilot reduced power by pulling the power levers aft, to the flight idle stop. He then depressed the latch levers, and pulled the power levers further aft, beyond the flight idle stop, through the beta range, into the reverse range. During the power reduction, the pilot noticed, and responded to a red beta light indication. Guidance from both the manufacturer and the operator prohibited the use of reverse thrust on the ground with a red beta light illuminated. The pilot pushed the power levers forward of the reverse range, and inadvertently continued through the beta range, where aerodynamic braking was optimum. The power levers continued beyond the flight idle gate into flight idle, a positive thrust setting. The airplane continued to the departure end of the runway in a skid, and departed the runway and taxiway in a skidding turn. The airplane dropped over a 60-foot embankment, and came to rest at the bottom. The computed landing distance for the airplane over a 50-foot obstacle was 3,900 feet, with braking and ground idle (beta) only; no reverse thrust applied. Ground-taxi testing after the accident revealed that the airplane could reach groundspeeds upwards of 85 knots with the power levers at idle, and the condition levers in the flight position. Simulator testing, based on FDR data, consistently resulted in runway overruns. Examination of the airplane and component testing revealed no mechanical anomalies. Review of the beta light indicating system revealed that illumination of the red beta light on the ground was not an emergency situation, but only indicated a switch malfunction. In addition, a loss of the reverse capability would have had little effect on computed stopping distance, and none at all in the United States, where performance credit for reverse thrust was not permitted.
Photographs
6the aircraft, and what the investigators foundPhotographs are NTSB docket attachments — works of the US government, in the public domain. Captions are the Board’s own.
Probable cause
the Board's determinationThe captain's improper application of power after responding to a beta warning light during landing rollout, which resulted in an excessive rollout speed and an inability to stop the airplane before it reached the end of the runway.
Sequence of events
12 timed eventsfrom the FDR factual report · claude-sonnet-5- 11,307.55 secondsLandingp.2Increased activity in the vertical acceleration FDR data indicated initial touchdown occurred
- 11,309.77 secondsLandingp.2Air-Ground Nose discrete changed from "flt" to "grnd"
- 11,309.88 secondsLandingp.2Pitch attitude had decreased to -2.11° nose down
- 11,310.77 secondsLandingp.2Air-Ground Left Main discrete changed from "flt" to "grnd"
- 11,311.77 secondsLandingp.2Air-Ground Right Main discrete changed from "flt" to "grnd"
- 11,324.55 secondsLanding rollp.2Left and right spoiler discretes changed from "stow" to "deploy"
- 11,329.55 secondsLanding rollp.2Left and right spoiler discretes changed back to "stow" where it remained for the rest of the recorded FDR data
- 11,350.77 secondsRunway overrunp.2Air-Ground Nose discrete changed from "grnd" to "flt" where it remained for the rest of the recorded FDR data
- 11,351.77 secondsRunway overrunp.2Air-Ground Left Main discrete changed from "grnd" to "flt"
- 11,352.77 secondsRunway overrunp.2Air-Ground Right Main discrete changed from "grnd" to "flt" where it remained for the rest of the FDR data
- 11,353.77 secondsRunway overrunp.2Air-Ground Left Main discrete changed back to "grnd" where it remained for the rest of the FDR data
- 11,382 secondsEnd of recordingp.2The recorded FDR data ended
NTSB analysis
from the final reportThe twin-engine turbo-prop airplane touched down about 1,900 feet beyond the approach end of the 6,000-foot runway. During the rollout, the pilot reduced power by pulling the power levers aft, to the flight idle stop. He then depressed the latch levers, and pulled the power levers further aft, beyond the flight idle stop, through the beta range, into the reverse range. During the power reduction, the pilot noticed, and responded to a red beta light indication. Guidance from both the manufacturer and the operator prohibited the use of reverse thrust on the ground with a red beta light illuminated. The pilot pushed the power levers forward of the reverse range, and inadvertently continued through the beta range, where aerodynamic braking was optimum. The power levers continued beyond the flight idle gate into flight idle, a positive thrust setting. The airplane continued to the departure end of the runway in a skid, and departed the runway and taxiway in a skidding turn. The airplane dropped over a 60-foot embankment, and came to rest at the bottom. The computed landing distance for the airplane over a 50-foot obstacle was 3,900 feet, with braking and ground idle (beta) only; no reverse thrust applied. Ground-taxi testing after the accident revealed that the airplane could reach groundspeeds upwards of 85 knots with the power levers at idle, and the condition levers in the flight position. Simulator testing, based on FDR data, consistently resulted in runway overruns. Examination of the airplane and component testing revealed no mechanical anomalies. Review of the beta light indicating system revealed that illumination of the red beta light on the ground was not an emergency situation, but only indicated a switch malfunction. In addition, a loss of the reverse capability would have had little effect on computed stopping distance, and none at all in the United States, where performance credit for reverse thrust was not permitted.