# NTSB IAD01FA021: Jetstream 4101, N323UE, Charlottesville, VA, December 30, 2000 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Field investigation · Final report - Date: December 29, 2000, 22:34 local (Dec 30, 2000, 03:34 UTC) - Place: Charlottesville, VA - Coordinates: 38.133335, -78.449996 - Nearby events: https://openairdocs.org/map.md?lat=38.1333&lon=-78.4500&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor, 17 uninjured - Status: Completed, report August 26, 2002 - Report: Approved by Office Director - Parties: FAA, Atlantic Coast Airlines dba United Express, Air Line Pilots Association - NTSB case key (mKey): 51185 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD01FA021 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/51185/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=51185 - Page: https://openairdocs.org/ntsb/IAD01FA021 ## Probable cause The 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 In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Overrun, landing - roll - annunciator panel light(s) - activated - remedial action - improper, pilot in command (cause) ## Analysis The 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. ## Factual narrative HISTORY OF FLIGHT On December 29, 2000, at 2234 eastern standard time, a Jetstream 4101, N323UE, operated by Atlantic Coast Airlines as flight 331, was substantially damaged when it departed the runway after landing at the Charlottesville/Albermarle Airport (CHO), Charlottesville, Virginia. Two flight crewmembers, 1 flight attendant, and 14 passengers were uninjured. One passenger received minor injuries. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the scheduled passenger flight. The flight originated at the Washington-Dulles International Airport (IAD), Washington, DC, and was conducted under 14 CFR Part 121. After landing on runway 21, the airplane rolled out to the end, turned left onto the last taxiway, then continued onto a grass apron, and down a 60-foot embankment. In a telephone interview about 1 hour after the accident, the captain was asked to describe what happened. He stated: "I couldn't tell you. It was a textbook landing. We landed in the touchdown zone, on speed. I pulled both throttles to idle and got a bad reverser on the right side. I got a red beta light. It's policy not to use reverse when you get the red light. I got on the wheel brakes harder, and the brakes didn't slow us down. I just decided to do a high-speed turn off onto the taxiway. I didn't get any other bad indications. I didn't get any with the anti-skid, but the plane just wouldn't slow down." On December 30, 2000, about 1400, the flight crew was interviewed in person. The captain again provided his recollection of events. He said: "It was a textbook visual approach and landing in VMC conditions. It was on speed, in the touchdown zone, and on centerline, with the throttles at idle. At touchdown, I was on the brakes with light toe pressure; I pulled the finger lift, and got a red attention-getter. I went to the annunciator, and had a red beta. Coming back up over the stop, the red beta went out. I saw the red beta went out, but I never saw the green. I said, 'We have a bad beta'. I was hard on the brakes. The airplane veered right, and I was on the tiller to steer back to the centerline. We were not slowing down. The [runway lights] were changing, so I knew we were near the end. I did a high-speed taxi off the side to avoid all the metal off the end. We got about 90 degrees [through the turn], but we couldn't make it, and went down over the embankment. We egressed, counted everybody, and waited for someone to realize what was happening." The captain was asked what the computed approach speed was for the flight, and the range of speeds for minimum weight to maximum allowable gross weight. He was also asked what the computed accelerate/stop and landing distances were for the flight. The captain said he could not recall the answers to any of the questions. However, he explained that tabular charts determined all distances and speeds. The charts converted all parameters (wind speed and direction, runway condition, etc.) to a weight value, and these values were added to the total aircraft weight. When the total weight value was below the maximum allowable for the proposed flight, the flight was completed, and the charts provided takeoff, approach, and landing speeds. The captain was asked if he felt he could explain the accident. He stated: "I really don't know. When we were on the brakes, it just didn't seem to be slowing down like a normal Jetstream. We were hard on the brakes, but the brakes just didn't seem to be slowing us down." When interviewed, the first officer explained that it was the responsibility of the pilot-not-flying (PNF) to determine the landing weight of the airplane, based on the tabular data, and choose the card that provided the correct approach and landing speeds. He stated: "It was a VFR approach to runway 21. I made the 1,000-foot call, and the 500-foot call. I called [speeds] plus 15, plus 10, REF, and we touched down on centerline. I didn't see the red beta light, but the captain said, 'We have a bad beta, we're not gonna use reverse, we're gonna use the brakes.' I called 70 knots, and moved the condition levers to taxi. I looked out and could see the end of the runway was getting closer. When we were in the final turn, I applied some brake pressure because we were a little fast." When asked whose responsibility it was to move the condition levers from the flight position (100 percent rpm), to the taxi position (72 percent rpm), the first officer explained that the pilot flying the airplane controls the power levers, and the pilot not flying (PNF) moves the condition levers. The accident occurred during the hours of darkness, at 38 degrees, 08 minutes north latitude, and 078 degrees, 27 minutes west longitude. PERSONNEL INFORMATION The captain held an airline transport pilot certificate with ratings for airplane multi-engine land. The captain's most recent first-class medical certificate was issued September 6, 2000. The captain reported 4,050 hours of flight experience, all of which were in multi-engine airplanes. He reported 1,425 hours of experience in the Jetstream 4100, 400 hours of which were as captain. The captain also reported he had 45 hours of flight experience in the 30 days prior to the accident. The first officer held an airline transport pilot certificate with ratings for airplane single engine land, multi-engine land, and instrument airplane. The first officer's most recent first-class medical certificate was issued November 7, 2000. The first officer reported 4,818 hours of flight experience, 950 hours of which were in multi-engine airplanes. He reported 68 hours of flight experience in the Jetstream 4100, 32 hours of which were in the 30 days prior to the accident. He reported 4 hours of experience in the 24 hours prior to the accident. AIRCRAFT INFORMATION The airplane was a 1995 Jetstream Aircraft Limited Model 4101, and was registered in the transport category. It was powered by two Allied Signal TPE-331 turbo-shaft engines. The airplane had accrued 14,456 hours of total flight time. It was on a continuous airworthiness inspection program, and its most recent inspection was completed on December 29, 2000. METEOROLOGICAL INFORMATION The weather reported at Charlottesville included calm winds with a broken cloud layer at 12,000 feet. The temperature was 24 degrees Fahrenheit and the dewpoint was 15 degrees Fahrenheit. AERODROME INFORMATION The Charlottesville-Albermarle Airport was at a field elevation of 639 feet mean sea level (msl), and had a single grooved runway. Runway 03/21 was 6,001 feet long and 150 feet wide. Six perpendicular taxiways, designated A thru F, connected the runway to the parallel taxiway, designated north/south. The runway surface, which was inspected approximately 4 hours after the accident, was clean and dry. FLIGHT RECORDERS On January 4, 2001, data from the airplane's Flight Data Recorder (FDR) was retrieved and graphed by a Safety Board recorder specialist. According to the specialist's factual report: "For the accident landing, the increased activity in the vertical acceleration FDR data, at approximately 11,307.55 seconds, indicated initial touchdown occurred. At the time of this initial touchdown, the magnetic heading was approximately 210°, the indicated airspeed was approximately 98.5 knots, the pitch attitude was 2.58° nose up, and the roll attitude was 1.25° right wing down. Approximately 2.2 seconds later, the "Air-Ground Nose discrete" changed from "flight" to "ground" (at 11,309.77 seconds). Less than a second later, at 11,309.88 seconds, the pitch attitude had decreased to -2.11 degrees nose down. One second after the Air-Ground Nose discrete changed from "flight" to "ground", the Air-Ground Left Main discrete changed from "flight" to "ground" (at 11,310.77 second ## Aircraft - Registration: [N323UE](https://openairdocs.org/deregistered/N323UE-2001-12-03), registration cancelled 2001-12-03, S/N 41059, built 1995 (OpenAirDocs) - Reported make and model: Jetstream 4101 - Registry model: [Jetstream JETSTREAM 4101](https://openairdocs.org/model/jetstream-jetstream-4101) (registry code 1500501) (OpenAirDocs) - Registry engine: [AiResearch TPE331 series](https://openairdocs.org/engine/airesearch-tpe331-series) (registry code 01514, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 41059 - Airframe hours: 14456 - Engines: Garrett TPE33114GR807 1500 horsepower turbo prop; Garrett TPE33114HR807 1500 horsepower turbo prop - Damage: Substantial damage - Flight: Part 121 - Registered owner: Atlantic Coast Airlines - Airworthiness certificate: Standard, Transport - Last inspection: Continuous airworthiness, December 11, 2000, 104.2 hours before - Departed: IAD, Washington, DC - Destination: CHO, Charlottesville, VA - Flight plan: IFR - Airport: CHO, Charlottesville-Albermarle, runway 21, 6,001 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 38; injuries: none; airline transport; airplane ratings: multi-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; last flight review June 10, 2000; seat: left; flight hours: 4,050 total, 1,425 in this make and model, 1,900 as pilot in command, 120 in the last 90 days, 45 in the last 30 days, 4 in the last 24 hours - Co-pilot; age 44; injuries: none; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, valid medical--w/ waivers/lim; seat: right; flight hours: 4,818 total, 68 in this make and model, 4,500 as pilot in command, 68 in the last 90 days, 32 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night/dark - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: 12,000 ft broken - Temperature: 25 °F, dew point 16 °F - Altimeter: 29.84 inHg - Observed at: CHO, 1 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20001229043439A](https://openairdocs.org/incident/20001229043439A), Dec 29, 2000: Jetair JETSTM4101, Charlottesville, VA, Substantial damage. (-23) On December 29, 2000, at 2232 local, united express (atlantic coast airlines) flight 7331, a jetstream 41 aircraft, landed on runway 21 at… ## Docket (16 files) The files NTSB released with the investigation on July 31, 2002, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=51185. 8.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 626 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445264&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - NTSB Recorders Group (CVR) Chairman's Report (item 2, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445262&FileExtension=.PDF&FileName=NTSB%20Recorders%20Group%20(CVR)%20Chairman%27s%20Report-Redacted.PDF - NTSB Recorders Group (FDR) Chairman's Report (item 3, .PDF, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445263&FileExtension=.PDF&FileName=NTSB%20Recorders%20Group%20(FDR)%20Chairman%27s%20Report-Redacted.PDF - Summaries of Interview with Captain (item 4, .PDF, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445265&FileExtension=.PDF&FileName=Summaries%20of%20Interview%20with%20Captain-Redacted.PDF - Summary of Interview with First Officer (item 5, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445266&FileExtension=.PDF&FileName=Summary%20of%20Interview%20with%20First%20Officer-Redacted.PDF - Summary of Flight Tests from Atlantic Coast Airlines (item 6, .PDF, 195 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40163821&FileExtension=.PDF&FileName=Summary%20of%20Flight%20Tests%20from%20Atlantic%20Coast%20Airlines-Master.PDF - Landing Distance Calculations from British Aerospace (E-mail) (item 7, .PDF, 69 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445267&FileExtension=.PDF&FileName=Landing%20Distance%20Calculations%20from%20British%20Aerospace%20(E-mail)-Redacted.PDF - Statement from Safety Board Performance Engineer (item 8, .PDF, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445268&FileExtension=.PDF&FileName=Statement%20from%20Safety%20Board%20Performance%20Engineer-Redacted.PDF - Statement of Party Representatives to NTSB Investigation (item 9, .PDF, 82 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445269&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 10, .PDF, 125 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445270&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF - Photo 1 - View of runway facing the landing direction (item 11, .PDF, 574 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40163839&FileExtension=.PDF&FileName=Photo%201%20-%20View%20of%20runway%20facing%20the%20landing%20direction-Master.PDF - Photo 2 - View of skid marks at departure end of runway (item 12, .PDF, 251 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40163840&FileExtension=.PDF&FileName=Photo%202%20-%20View%20of%20skid%20marks%20at%20departure%20end%20of%20runway-Master.PDF - Photo 3 - View skid marks off taxiway onto grass apron (item 13, .PDF, 688 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40163841&FileExtension=.PDF&FileName=Photo%203%20-%20View%20skid%20marks%20off%20taxiway%20onto%20grass%20apron-Master.PDF - Photo 4 - View of airplane as found (item 14, .PDF, 818 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40163842&FileExtension=.PDF&FileName=Photo%204%20-%20View%20of%20airplane%20as%20found-Master.PDF - Photo 5 - View of damaged landing gear and #2 propeller (item 15, .PDF, 561 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40163844&FileExtension=.PDF&FileName=Photo%205%20-%20View%20of%20damaged%20landing%20gear%20and%20%232%20propeller-Master.PDF - Photo 6 - View of shaved landing gear tire (item 16, .PDF, 902 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40163845&FileExtension=.PDF&FileName=Photo%206%20-%20View%20of%20shaved%20landing%20gear%20tire-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.