USAir Flight 427

USAir Flight 427
N513AU, the aircraft involved in the accident, taxiing at John Wayne Airport in 1989.
Occurrence
Date September 8, 1994 (1994-09-08)
Summary Loss of control due to rudder hardover[1]
Site Hopewell Township,
Beaver County, Pennsylvania
40°36′14″N 80°18′37″W / 40.60393°N 80.31026°W / 40.60393; -80.31026Coordinates: 40°36′14″N 80°18′37″W / 40.60393°N 80.31026°W / 40.60393; -80.31026
Aircraft type Boeing 737-3B7
Operator USAir
Registration N513AU[2]
Flight origin O'Hare International Airport
Stopover Pittsburgh International Airport
Destination West Palm Beach Int'l Airport
Passengers 127
Crew 5
Fatalities 132
Survivors 0

USAir Flight 427 was a scheduled flight from Chicago's O'Hare International Airport to Pittsburgh International Airport, with a final destination of West Palm Beach, Florida. On Thursday, September 8, 1994, the Boeing 737 flying this route crashed while approaching runway 28R of Pittsburgh International Airport, located in Findlay Township, Allegheny County, Pennsylvania, which at the time was the largest hub for the airline.

After the longest investigation in the history of the National Transportation Safety Board (NTSB), it was 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 the pilots were unable to recover. All 132 people on board the aircraft were killed.

Involved

Aircraft

The aircraft involved was a Boeing 737-3B7, registration N513AU, and previously registered as N382AU. The aircraft was delivered in 1987 and was powered by two CFM56-3B2 engines. The aircraft had recorded approximately 16,800 hours of flight time before the crash.[1]:1:6

Crew

The flight crew consisted of Captain Peter Germano, 45, who was hired by USAir in February 1981, and First Officer Charles B. "Chuck" Emmett III, 38, who was hired in February 1987 by Piedmont Airlines (which merged into USAir in 1989). Both were regarded as excellent pilots and they were both very experienced: Captain Germano logged approximately 12,000 flight hours, while First Officer Emmett logged 9,000 flight hours. Flight attendants Stanley Canty and April Slater were hired in 1989 by Piedmont Airlines. Flight attendant Sarah Slocum-Hamley was hired in October 1988 by USAir.[1]:7-11

Crash

During its arrival into 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 miles to Delta 1083, according to radar data.[1]:2 Flight 427 was on approach at 6000 feet altitude, at flaps 1 configuration, and at approximately 190 knots.

At 7:02:57 p.m., the aircraft entered the wake turbulence of the Delta 727 it was sequenced behind, and there were three sudden thumps, clicking sounds, and a louder thump, after which the 737 began to bank and roll to the left.[1]:4 As the aircraft stalled, Germano exclaimed "hold on" numerous times,[1]:138 while Emmett, under physical exertion, said, "oh shit."[1]:143 Germano exclaimed, "what the hell is this?"[1]:6 As air traffic control noticed Flight 427 descending without permission, Germano keyed the mic and stated, "four-twenty-seven, emergency!"[1]:6 The mic was keyed for the rest of the event, resulting in the following exclamations in the cockpit being heard in the tower at Pittsburgh. The aircraft continued to roll while pitched nose-down at the ground, at which point against sharply rising G-forces, Germano yelled "pull" three consecutive times before screaming, during which Emmett stated "God, no" seconds before impact. In an 80-degree nose-down position, banked 60 degrees left and traveling at approximately 300 mph (480 km/h), the 737 slammed into the ground and exploded at 7:03:25 p.m. in Hopewell Township, Beaver County,[3] near Aliquippa approximately 28 seconds after entering the wake turbulence.

The crash site of USAir Flight 427, on March 10, 2018.

Investigation

The National Transportation Safety Board investigated the crash. All 127 passengers and five crew members were killed.[1]:ix For the first time in NTSB history, investigators were required to wear full-body bio-hazard suits while inspecting the accident site.[7] 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 bio-hazard, requiring 2,000 body bags for the 6,000 recovered human remains.[8] USAir had difficulty determining Flight 427's passenger list, facing confusion regarding five or six passengers. Several employees of the U.S. Department of Energy had tickets to take later flights, but used them to fly on Flight 427. One young child was not ticketed.[9] Among the victims of the crash was noted neuroethologist Walter Heiligenberg.[10]

Both the CVR and FDR were recovered and used for the investigation. Due to the limited parameters recorded by the FDR, investigators did not have access to the position of the flight-control surfaces (rudder, ailerons, elevator, etc.) for the accident. However, two parameters recorded by the FDR were crucial, one being the aircraft's heading, the other being the pitch control yoke position. During the approach, Flight 427 encountered wake turbulence from Delta 1083; the FAA, however, determined "the wake vortex encounter alone would not have caused the continued heading change that occurred after 1903:00."[1]:245 The abrupt heading change shortly before the dive pointed investigators immediately to the rudder. Due to the absence of rudder pedal positions from the data, investigators had to determine whether the rudder moved hard-over by a malfunction or by pilot command. This in turn led to the CVR being more heavily scrutinized than most other recordings as statements and breathing from the pilots could potentially tell investigators if they were fighting for control over a rudder malfunction or inadvertently stomped on the wrong rudder pedal in excitement from the wake-turbulence. Boeing felt the latter more likely, while USAir and the Pilot's Union felt the former was more likely.[1][11] The FDR revealed that after the aircraft stalled, it along with the crew and passengers were subjected up to a 4g load throughout the dive until impact with the ground in an 80 degree nose-down attitude traveling at approximately 300 mph under significant sideslip.[1]

Reading the control yoke data from the FDR revealed that the pilots made a crucial error by pulling back on the control 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 aggravated the bank angle further.[11] Boeing's test pilots reenacted the fatal dive in both a simulator, as well as a test 737-300 by flying the same parameters on 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.[11]:153 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.[12] The NTSB remarked that no airline had ever trained a pilot on the proper recovery technique for the situation experienced by the pilots and that the pilots had just 10 seconds from the onset of the roll to troubleshoot before recovery of the aircraft was impossible.[11]:153

Impact crater of USAir Flight 427
Recovered wreckage under examination

Investigators later discovered that the recovered accident rudder PCU was much more sensitive to bench-tests than other new PCU's. 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 lab 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. In light of this, Boeing felt that the test results were not real-world and not applicable due to the extremes under which the valve was tested.[13][11] Boeing stated that the rudder reversal was more likely psychological, likening it to examples when a human panics and intends to step on the brake during an automotive accident, but accidentally presses on the gas pedal instead while under duress.[11] The FAA's official position was that there was not enough evidence for probable cause of rudder system failure.[14]

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.[1][15] The NTSB concluded that the accident was due to mechanical failure:

The National Transportation Safety Board determines that the probable cause of the USAir Flight 427 accident was 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.[1]:ix

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.[1]:292–295

Aftermath

At the time of the crash, Flight 427 was the second-deadliest accident involving a Boeing 737 (all series); as of 2012, it was the sixth deadliest. It was also the seventh-deadliest aviation disaster in the history of the United States, and the deadliest in the US involving a 737; as of 2012, it ranks eleventh.[16] The accident marked USAir's fifth crash in the period from 1989 to 1994.[9] The Commonwealth of Pennsylvania spent approximately $500,000 in recover and cleanup for the accident site.[8]

USAir submitted to the NTSB that pilots should receive training with regard to a plane's crossover speed and recovery from full rudder deflection.[4] As a result, pilots were warned of and trained how to deal with insufficient aileron authority at an airspeed at or less than 190 knots (352 km/h), formerly the usual approach speed for a Boeing 737. Boeing maintained that the most likely cause of the crash was that the co-pilot inadvertently deflected the rudder hard-over in the wrong direction while in a panic and for unknown reasons maintained this input until impact with the ground.[1]:96–100[17] Boeing agreed to redesign the rudder control system with a redundant backup and paid for the retrofit of the entire worldwide 737 fleet.[18] As one of the NTSB's main recommendations, airlines were required to add four additional channels of information — pilot rudder pedal commands — into flight data recorders, with which the FAA gave airlines until August 2001 to comply.[19] In 2016, former investigator John Cox stated that time so far has proven the NTSB correct in their findings due to the absence of a rudder reversal incident since Boeing's redesign.[20]

Following the airline's response to the Flight 427 accident, the United States Congress required airlines to deal more sensitively with the families of crash victims.[21] and US Airways ceased using Flight 427 as a valid flight number. Flight 427 was the second fatal USAir crash in just over two months, the other being Flight 1016 at Charlotte-Douglas Airport in July 1994. The crashes contributed to the financial crisis USAir was experiencing at the time.[22]

The Discovery Channel Canada / National Geographic TV series Mayday (also called Air Crash Investigation or Air Disasters) dramatized the crash of Flight 427 and the NTSB's 737 rudder investigation in a 2007 episode titled Hidden Danger (broadcast in some countries as Mystery Crashes).[7]

See also

References

  1. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Aircraft Accident Report – Uncontrolled Descent and Collision With Terrain, USAir Flight 427, Boeing 737-300, N513AU, Near Aliquippa, Pennsylvania, September 8, 1994 (PDF). National Transportation Safety Board. March 24, 1999. Archived (PDF) from the original on March 4, 2016. Retrieved January 17, 2016.
  2. ↑ "FAA Registry (N513AU)". Federal Aviation Administration.
  3. ↑ "28 Seconds of Horror," Pittsburgh Tribune-Review
  4. 1 2 Bertorelli, Paul (October 19, 1997). "USAir 427: US Airways' View of the Accident – AVweb Features Article". Avweb.com. Archived from the original on November 25, 2016. Retrieved December 3, 2016.
  5. ↑ "28 Seconds: Roxie, Trixie and the fat guy 3". Sptimes.com. September 8, 1994. Archived from the original on August 21, 2016. Retrieved December 3, 2016.
  6. ↑ Federal Aviation Administration (September 8, 1994). "Lessons Learned". Lessonslearned.faa.gov. Archived from the original on December 20, 2016. Retrieved December 3, 2016.
  7. 1 2 "Hidden Danger". Mayday. Season 4. 2007. Discovery Channel Canada / National Geographic Channel.
  8. 1 2 "Archived copy" (PDF). Archived from the original (PDF) on September 24, 2017. Retrieved September 23, 2017.
  9. 1 2 "28 Seconds: The Mystery of USAir Flight 427 Part One: Zulu Archived September 12, 2012, at the Wayback Machine.." Retrieved on December 31, 2012.
  10. ↑ "List of Crash Victims." Wilmington Morning Star. September 10, 1994. 4A. Google News (28 of 49). Retrieved on October 3, 2009.
  11. 1 2 3 4 5 6 Adair, Bill (2002). The Mystery of Flight 427: Inside a Crash Investigation. ISBN 1-58834-005-8.
  12. ↑ "Lessons Learned". November 2, 2016.
  13. ↑ "Business - Expert Panel May Have Key To Which 737S Are Most At Risk - Seattle Times Newspaper". community.seattletimes.nwsource.com. Archived from the original on September 28, 2015. Retrieved December 19, 2012.
  14. ↑ "Archived copy" (PDF). Archived from the original (PDF) on February 11, 2017. Retrieved September 23, 2017.
  15. ↑ NTSB Office of Public Affairs (March 24, 1999). "NTSB Concludes Longest Investigation in History; Finds Rudder Reversal was Likely Cause of USAIR Flight 427, A Boeing 737, Near Pittsburgh in 1994" (Press release). National Transportation Safety Board. Archived from the original on April 21, 2016. Retrieved July 18, 2016.
  16. ↑ Ranter, Harro. "ASN Aircraft accident Boeing 737-3B7 N513AU Aliquippa, PA". aviation-safety.net. Archived from the original on June 16, 2013. Retrieved May 27, 2013.
  17. ↑ October 29, 1996  (October 29, 1996). "The Seattle Times: Safety at issue: the 737". Old.seattletimes.com. Archived from the original on June 21, 2017. Retrieved December 3, 2016.
  18. ↑ "Boeing: News Feature -- 737 Rudder Enhancements -- Enhanced Rudder System". January 12, 2008. Archived from the original on 2008-01-12.
  19. ↑ "NTSB Concludes Longest Investigation in History; Finds Rudder Reversal was Likely Cause of USAIR Flight 427, A Boeing 737, Near Pittsburgh in 1994". Ntsb.gov. March 24, 1999. Archived from the original on February 28, 2017. Retrieved July 22, 2017.
  20. ↑ "Fatal Flaws". Why Planes Crash. Season 2. 2016. MSNBC.
  21. ↑ "Remarks from acting NTSB Chairman, 2002". Archived from the original on September 25, 2012.
  22. ↑ Halvonik, Steve. "Disaster only one in a string of setbacks for troubled company." Pittsburgh Tribune-Review. Sunday September 5, 2004. Retrieved on January 1, 2012.

Books

  • Bill Adair, The Mystery of Flight 427: Inside a Crash Investigation, ISBN 1-58834-005-8
  • Gerry Byrne, Flight 427: Anatomy of an Air Disaster, ISBN 0-387-95256-X
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.