USAir Flight 427
Boeing B-737-300 · Rudder hardover and loss of control due to design flaw
From Chicago O'Hare International Airport (ORD) to President Donald J. Trump International Airport (PIT)
Event
- NTSB case
- DCA94MA076
- 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
- Event fatalities
- 132 · all aircraft and ground
- Ground fatalities
- 0
- Occupants
- 132
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- 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
- Airline
- 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
Boeing B-737-300
- Flight
- US427
- Aircraft type
- Boeing 737
- 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
- N513AU
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From Chicago O'Hare International Airport (ORD), Chicago, ILTo President Donald J. Trump International Airport (PIT), PITTSBURG, PA
- 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 121: Air Carrier
- 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
- Approach · VFR pattern downwind
- 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
- Airframe, component or system failure
- 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
- Flight control, rudder surface › Uncommanded
- Flight control, rudder › Jammed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
From the Wikipedia article
USAir Flight 427 was a scheduled flight from Chicago's O'Hare International Airport to Palm Beach International Airport, Florida, with a stopover at Pittsburgh International Airport. On Thursday, September 8, 1994, the Boeing 737-300 flying this route crashed in Hopewell Township, Beaver County, Pennsylvania while approaching Runway 28R at Pittsburgh, which was USAir's largest hub at the time.
This accident was the second longest air crash investigation in history. The investigation into USAir 427 helped to also solve the crash of United Airlines Flight 585. The National Transportation Safety Board (NTSB) determined that the probable cause was that the aircraft's rudder malfunctioned and went hard over in a direction opposite to that commanded by the pilots, causing the plane to enter an aerodynamic stall from which Captain Peter Germano and First Officer Charles B. Emmet III were unable to recover. All 132 people on board died, making the accident the deadliest air disaster in Pennsylvania's history. The reports indicated that hot hydraulic fluid entering the rudder's dual servo valve froze, causing the rudder to work in the opposite direction.
Accident
In its arrival phase approaching Pittsburgh, Flight 427 was sequenced behind Delta Air Lines Flight 1083, a Boeing 727-200. At no time was Flight 427 closer than 4.1 mi to Delta 1083, according to radar data. Flight 427 was on approach at 6000 ft altitude, at flaps 1 (eight degrees) configuration, and at approximately 190 kn.
At 19:02:57, the aircraft entered the wake turbulence of Delta 1083, and three sudden thumps, clicking sounds and a louder thump occurred, after which the 737 began to bank and roll to the left. The autopilot disconnected, and First Officer Emmett stomped on the right rudder pedal, and held it there for the remainder of the flight, unaware that the rudder had reversed hard to the left. As the aircraft's heading and bank angle skewed dramatically to the left, Emmett and Germano both rolled their yokes to the right and pulled back on the elevators to counter the gradually decreasing pitch angle, as the stick shaker activated and the airplane entered an aerodynamic stall, caused by the wing's critical high angle of attack.
As the stick shaker activated, Germano exclaimed "Hold on!" frequently, while Emmett, under physical exertion, said, "Oh shit!" Germano exclaimed, "What the hell is this?" As Pittsburgh air traffic control noticed Flight 427 descending without permission, and requested for them to return to 6000 ft, Germano keyed the microphone and stated, "Four-twenty-seven, emergency!" Under duress, Germano left the microphone keyed for the rest of the accident; the ensuing exclamations in the cockpit were heard in the tower at Pittsburgh.
The aircraft completed one full roll, remaining in a nose-down pitch. Trying to counteract sharply rising G-forces, Germano yelled "Pull!" three consecutive times before screaming, during which Emmett stated "God, no" seconds before impact. Pitched 80° nose-down and banked 60° left while traveling at approximately 300 mph, the 737 slammed into a gravel road in a wooded ravine and exploded at 19:03:25 in Hopewell Township, Beaver County, near Aliquippa, approximately 28 seconds after entering the wake turbulence.
At the time of the accident, many people had gathered at the nearby Hopewell Soccer Club Fields for evening soccer practice. These people witnessed the crash of the aircraft and described the plane as suddenly falling out of the sky. The aircraft narrowly missed impacting the I-376 interchange just east of the Green Garden shopping plaza, where some witnesses took cover. Power was knocked out in the Giant Eagle after the crash.
After several failed attempts to raise the downed flight on radar, Pittsburgh air traffic control raised the alarm and local fire companies and EMS were hailed. Upon arriving at the scene, however, the aircraft was found to be obliterated, and not only was it evident that there were no survivors, but the fragmented human remains constituted a bio-hazard.
All 132 aboard Flight 427 were killed, in the state of Pennsylvania's deadliest aviation accident to date.
Investigation and cause
Investigation
The NTSB investigated the crash. All 127 passengers and 5 crew members on board were killed. For the first time in NTSB history, investigators were required to wear full-body biohazard suits while inspecting the accident site. As a result of the severity of the crash impact, the bodies of the passengers and crew were severely fragmented, leading investigators to declare the site a biohazard, requiring 2,000 body bags for the 6,000 recovered human remains. USAir had difficulty determining Flight 427's passenger list, facing confusion regarding five or six passengers. Several employees of the United States Department of Energy had tickets to take later flights, but used them to fly on Flight 427. One young child was not ticketed. Among the victims of the crash was noted neuroethologist Walter Heiligenberg.
Both the cockpit voice recorder (CVR) and flight data recorder (FDR) were recovered and used for the investigation. Because of the limited parameters recorded by the FDR, investigators did not have access to the position of the flight-control surfaces (rudder, ailerons, elevator, etc.) during the accident sequence. However, two parameters recorded were crucial — the aircraft's heading and the pitch-control yoke position. During the approach, Flight 427 encountered wake turbulence from Delta 1083, but the FAA determined "the wake vortex encounter alone would not have caused the continued heading change that occurred after 19:03:00." The abrupt heading change shortly before the dive pointed investigators immediately to the rudder. Without data relating to the rudder pedal positions, investigators attempted to determine whether the rudder moved hard over by a malfunction or by pilot command. The CVR was heavily scrutinized as investigators examined the pilots' words and their breathing to determine whether they were fighting for control over a rudder malfunction or had inadvertently stomped on the wrong rudder pedal in reaction to the wake turbulence. Boeing felt the latter more likely, while USAir and the pilots' union felt that the former was more likely. The FDR revealed that after the aircraft stalled, the plane and its occupants were subjected to a load as high as 4 g throughout the dive until impact with the ground in an 80-degree nose-down attitude at approximately 300 mph under significant sideslip.
Reading the control-yoke data from the FDR revealed that the pilots made a crucial error by pulling back on the yoke throughout the dive, with the stick shaker audible on the CVR from the onset of the dive. This raised the aircraft's angle of attack, removed all aileron authority, prevented recovery from the roll induced by the rudder and caused an aerodynamic stall. Because the aircraft had entered a slip, pulling back on the yoke only further aggravated the bank angle. Boeing's test pilots reenacted the dive in a simulator and in a test 737-300 by flying with the same parameters recorded by the accident FDR, and found that recovery from a fully deflected rudder at level flight, while at 190-knot crossover speed, was accomplished by turning the wheel to the opposite direction of the roll, and not pulling back on the yoke to regain aileron authority. The FAA later remarked that the CVR proved that the pilots failed to utilize proper crew resource management during the upset while continuing to apply full up elevator after receiving a stall warning. The NTSB remarked that no airline had ever trained a pilot to properly recover from the situation experienced by the Flight 427 pilots and that the pilots had just 10 seconds from the onset of the roll to troubleshoot before recovery of the aircraft was impossible.
Investigators later discovered that the recovered accident rudder power control unit was much more sensitive to bench tests than new control units. The exact mechanism of the failure involved the servo valve, which remains dormant and cold for much of the flight at high altitude, seizing after being injected with hot hydraulic fluid that has been in continuous action throughout the plane. This specific condition occurred in fewer than 1% of the laboratory tests, but explained the rudder malfunction that caused Flight 427 to crash. The jam left no trace of evidence after it occurred, and a Boeing engineer later found that a jam under this controlled condition could also lead to the slide moving in the opposite direction than that commanded. Boeing felt that the test results were unrealistic and inapplicable, given the extremes under which the valve was tested. It stated that the cause of the rudder reversal was more likely psychological and likened the event to a circumstance in which an automobile driver panics during an accident and accidentally presses on the gas pedal rather than the brake pedal. The official position of the Federal Aviation Administration (FAA) was that sufficient probable cause did not exist to substantiate the possibility of rudder system failure.
After the longest accident investigation in NTSB history — lasting more than four and a half years — the NTSB released its final report on March 24, 1999. The NTSB concluded that the accident was the result of mechanical failure:
The NTSB concluded that similar rudder problems had caused the previously mysterious March 3, 1991, crash of United Airlines Flight 585 and the June 9, 1996, incident involving Eastwind Airlines Flight 517, both Boeing 737s. The final report also included detailed responses to Boeing's arguments about the causes of the three accidents.
Text from the Wikipedia article “USAir Flight 427” (revision 1363402597, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
The airplane crashed while maneuvering to land at Pittsburgh International Airport. The airplane entered an uncontrolled descent and impacted terrain about 6 miles east of the airport. The airplane struck the ground at an angle of descent of about 80 degrees, in a slight roll to the left, and the airspeed was about 260 knots at impact. The investigation revealed that during the accident sequence, the airplane rudder deflected rapidly to the left and reached its left aerodynamic blowdown limit shortly thereafter. Examination of the rudder system revealed that it is possible, in the main rudder power control unit (PCU) of the airplane (as a result of some combination of tight clearances within the servo valve, thermal effects, particulate matter in the hydraulic fluid, or other unknown factors), the servo valve secondary slide could jam to the servo valve housing at a position offset from its neutral position without leaving any obvious physical evidence and that, combined with rudder pedal input, could have caused the rudder to move opposite to the direction commanded by a rudder pedal input. This condition of the PCU was also consistent with analysis of the cockpit voice recorder, computer simulation, and human performance data, including operational factors
Probable cause
A loss of control of the airplane resulting from the movement of the rudder surface to its blowdown limit. The rudder surface most likely deflected in a direction opposite to that commanded by the pilots as a result of a jam of the main rudder power control unit servo valve secondary slide to the servo valve housing offset from its neutral position and overtravel of the primary slide.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: USAir Flight 427
- Article
- USAir Flight 427
- Revision
- 1363402597 · 2026-07-10 · retrieved 2026-09-18
- Wikidata
- Q929721
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA94MA076
- Event ID
- 20001206X02233
- Case number
- DCA94MA076
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
- Record
- Wikipedia article "USAir Flight 427" (page 22993469, revision 1363402597); merged with NTSB case DCA94MA076 (events / aircraft)
- Date
- NTSB record DCA94MA076: NTSB narrative opening date, consistent with the API date and time (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record DCA94MA076
- Map position
- NTSB record DCA94MA076: events decimal coordinates
- Aircraft, operator and route
- NTSB record DCA94MA076: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record DCA94MA076: operated under Part 121: Air Carrier
- Fatalities
- NTSB record DCA94MA076: NTSB API totalFatal
- Ground fatalities
- NTSB record DCA94MA076: NTSB API ongroundFatal
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "USAir Flight 427" and NTSB case DCA94MA076, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: investigation status. 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.