Fatal accident · United States
USAir Flight 427 dove into terrain near Aliquippa
USAir Flight 427, a Boeing 737-3B7, crashed near Aliquippa, Pennsylvania, on September 8, 1994, while approaching Pittsburgh from Chicago. There were 132 people aboard, and all 132 died. The cause was mechanical failure that led to a loss of control.
This is one of 5 USAir fatal accidents on record. See also all plane crashes in 1994.
Flight 427 lost control on approach to Pittsburgh
Flight 427 was nearing the end of its scheduled trip from Chicago to Pittsburgh when the upset began. During approach, the Boeing 737 was at 6,000 feet when it entered a sudden nose-down dive and crashed in a wooded ravine about 6 miles northwest of Pittsburgh International Airport, near Aliquippa, Pennsylvania.
The impact destroyed the aircraft. Nobody on the ground was killed. This accident is listed as a mechanical failure crash, but the sequence was more specific than a simple component break. The aircraft first became uncontrollable in flight, then descended steeply into terrain.
The rudder moved opposite to the pilots' command
The Boeing 737 involved in Flight 427 was found to have suffered a rudder system malfunction. The loss of control resulted from movement of the rudder to its blowdown limit, or from an uncommanded rudder reversal, with the rudder deflecting in the opposite direction from what the pilots commanded.
The failure centered on the power control unit, often shortened to PCU. Investigators determined that the main rudder PCU servo valve secondary slide jammed in the servo valve housing while offset from neutral, and the primary slide then overtraveled. In simple terms, the valve inside the rudder control system did not return and respond normally, so the rudder could move the wrong way even though the crew's input called for the opposite response.
That kind of failure is especially dangerous because the rudder can create a powerful roll and yaw. On a transport jet, a full or near-full rudder deflection at the wrong moment can overwhelm the airplane before the crew has time to diagnose what happened. For more on that accident category, see loss of control in flight.
A left roll may have triggered the crew's hard right rudder input
Flight 427 most likely reached the final upset through a short chain of events. The rudder PCU servo valve jammed, the crew applied light left rudder, then hard right rudder, and the rudder reversed to full blown-left position instead of following that command.
That reversal rolled the aircraft further left. The airplane then stalled and entered the dive. Contemporary accounts on the sequence say the hard right rudder input may have been prompted by a left roll after the jet encountered the wake vortex of a Boeing 727. Whether wake turbulence actually started the upset was not resolved.
The aircraft was also at a crossover speed of 190 knots with flaps 1. In that condition, using the control wheel alone would not correct a rudder hardover in the usual way. The crew was not blamed. There had been no manufacturer guidance describing this recovery and no training for such an event.
The crash drove wider attention to how probable cause is framed
Near Aliquippa, this accident showed how a single jam inside a flight control unit could lead to a complete loss of the airplane within seconds. The stated cause was mechanical failure, but the detailed explanation traced that failure through the servo valve, the reversed rudder response, and the resulting roll, stall, and dive.
Accident reports often separate the broad category from the technical sequence. A broad label such as mechanical failure tells you the type of failure. The longer finding explains exactly what part failed and how that failure led to impact. That distinction matters when changes are made to design, inspection, training, and procedures. For background on that language, see what probable cause means.
The 737 family was a short- to medium-range airliner used heavily on domestic routes. In that role, approach and landing phases put an aircraft close to the ground, so a sudden control problem leaves very little time and altitude for recovery.
Questions people ask about this accident
What caused USAir Flight 427 to crash?
The crash was caused by a loss of control after the rudder moved opposite to the pilots' command because of a jam in the rudder power control unit servo valve.
Where did USAir Flight 427 crash?
It crashed in a wooded ravine near Aliquippa, Pennsylvania, about 6 miles northwest of Pittsburgh International Airport.
Did wake turbulence bring down USAir Flight 427?
Wake turbulence from a Boeing 727 may have prompted the crew's hard right rudder input, but that was not resolved as the definitive trigger of the upset.
Were the pilots blamed for the loss of USAir Flight 427?
No. The crew was not blamed because there was no manufacturer guidance on this type of recovery and no training for such an occurrence.
Related accidents
No fatalities
1 killed
9 killed
6 killed- 2 killed
Correct this page or send a photo
Spotted a wrong date, registration or number? Have a photo of the aircraft or the site that you took yourself? Send it here. Nothing is published until an editor has checked it.