Washington DC – Charlottesville
Flight / Schedule
Washington DC – Charlottesville
Aircraft
Bae Jetstream 41Registration
N323UE
MSN
41059
Year of Manufacture
1995
Operator
United ExpressDate
December 29, 2000 at 10:34 PM
Type
CRASHFlight Type
Scheduled Revenue Flight
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Crash Location
Charlottesville Virginia
Region
North America • United States of America
Coordinates
38.0293°, -78.4767°
Crash Cause
Human factor
Narrative Report
On December 29, 2000 at 10:34 PM, Washington DC – Charlottesville experienced a crash involving Bae Jetstream 41, operated by United Express, with the event recorded near Charlottesville Virginia.
The flight was categorized as scheduled revenue flight and the reported phase was landing (descent or approach) at a airport (less than 10 km from airport) crash site.
18 people were known to be on board, 0 fatalities were recorded, 18 survivors were identified or estimated. This corresponds to an estimated fatality rate of 0.0%.
Crew on board: 3, crew fatalities: 0, passengers on board: 15, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. The twin-engine turboprop 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 ground speeds 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.
Aircraft reference details include registration N323UE, MSN 41059, year of manufacture 1995.
Geospatial coordinates for this crash are approximately 38.0293°, -78.4767°.
Fatalities
Total
0
Crew
0
Passengers
0
Other
0
Crash Summary
The twin-engine turboprop 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 ground speeds 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.
Cause: Human factor
Occupants & Outcome
Crew On Board
3
Passengers On Board
15
Estimated Survivors
18
Fatality Rate
0.0%
Known people on board: 18
Operational Details
Schedule / Flight
Washington DC – Charlottesville
Operator
United ExpressFlight Type
Scheduled Revenue Flight
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Region / Country
North America • United States of America
