Aeroperú Flight 603

Jump to navigation Jump to search
Aeroperú Flight 603
Aeroperú Boeing 757-200 N52AW MIA 1996-1-8.png
N52AW, the Boeing 757 involved in the accident
Accident
Date2 October 1996 (1996-10-02)
SummaryInstrument failure due to static port obstruction caused by maintenance error; controlled flight into water
SitePacific Ocean
near Pasamayo, Huaral, Peru
12°02′S 77°30′W / 12.033°S 77.500°W / -12.033; -77.500Coordinates: 12°02′S 77°30′W / 12.033°S 77.500°W / -12.033; -77.500
Aircraft
Aircraft typeBoeing 757-23A
OperatorAeroperú
IATA flight No.PL603
ICAO flight No.PLI603
Call signAeroperu 603
RegistrationN52AW
Flight originMiami International Airport
Miami, Florida, U.S.
StopoverJorge Chávez Int'l Airport
Lima, Peru
DestinationComodoro Arturo Merino Benítez International Airport
Santiago, Chile
Occupants70
Passengers61
Crew9
Fatalities70
Survivors0

Aeroperú Flight 603 was a scheduled flight from Miami International Airport in Miami, Florida, US (KMIA), to Comodoro Arturo Merino Benítez International Airport in Santiago, Chile (SCEL), with stopover in Peru. On 2 October 1996, the Boeing 757-23A aircraft flying the final leg of the flight crashed, killing all 70 people aboard.

The investigation determined that the air data computers were unable to show correct airspeed and altitude on cockpit displays, because a maintenance worker had failed to remove tape covering the static ports on the aircraft exterior. Flying at night over water with no visual references, the pilots struggled to control and navigate the aircraft, unaware of their true altitude. The crash resulted after its left wing and № 1 engine hit the surface of the Pacific Ocean.[1]

Overview[edit]

Aircraft[edit]

The aircraft, a Boeing 757-23A was delivered new from Boeing on 2 December 1992, to Ansett Worldwide. It was leased to Aeroméxico on 27 September 1993 and then sub-leased to Aeroperú on 1 April 1994. The lease transferred back to Ansett in February 1995, and Aeroperú continued to operate the aircraft until it crashed.[2][3]

Passengers and crew[edit]

About half of the passengers on the flight were Chileans returning to Chile.[4][5][6]

Country Passengers Crew Total
Chile 30 - 30
Colombia 1 - 1
Ecuador 2 - 2
Italy 2 - 2
Mexico 6 - 6
New Zealand 1 - 1
Peru 11 9 20
Spain 1 - 1
United Kingdom 2 - 2
United States 4 - 4
Venezuela 1 - 1
Total 61 9 70

Of the passengers, 21 originated from Miami; all of the originating passengers were Chilean. An additional 10 passengers had boarded in Quito. The remaining passengers had boarded in Lima.[7]

The captain was 58-year-old Eric Schreiber Ladrón de Guevara, who had logged almost 22,000 flight hours (including 1,520 hours on the Boeing 757),[8] and the first officer was 42-year-old David Fernández Revoredo, who had logged almost 8,000 flight hours, with 719 of them on the Boeing 757.[8](pp4–7)

Accident[edit]

On 1 October 1996, Aeroperú Flight 603 from Miami International Airport had landed at the Lima Airport. One hundred and eighty passengers were on the first leg of the flight on a Boeing 757. One hundred and nineteen had disembarked, and the remaining passengers were transferred to another Boeing 757.[8][9][10][11]

The aircraft took off 42 minutes after midnight (05:42 UTC) on 2 October,[8](p10) and straight away, the Boeing 757 airliner crew discovered that their basic flight instruments were behaving erratically and reported receiving contradictory serial emergency messages from the flight management computer, including the altitude and airspeed indicator, rudder ratio, mach speed trim, overspeed, underspeed and flying too low. The crew declared an emergency and requested an immediate return to the airport.[4]

The pilots knew that they could figure out the actual altitude they were at by asking the controller, but neither the pilots or the controller knew that the altitude on the controller's screen was from the data on the plane.[4]

Faced with a lack of reliable basic flight instrument readings, constant contradictory warnings from the aircraft's flight computer (some of which were valid and some of which were not) and believing that they were at a safe altitude,[8](pp22–23) the crew decided to begin descent for the approach to the airport. Since the flight was at night over water, no visual references were available to convey to the pilots their true altitude or to aid their descent. As a consequence of the pilots' inability to precisely monitor the aircraft's airspeed or vertical speed, they experienced multiple stalls, resulting in rapid loss of altitude with no corresponding change on the altimeter. While the altimeter indicated an altitude of approximately 9,700 feet, the aircraft's true altitude was much lower.[4]

The air traffic controller instructed a Boeing 707 to take off and to help guide the 757 in to land but before the 707 could do so, the 757's left wingtip struck the water approximately 25 minutes after the emergency declaration. By the time they realized that they were too low, it was too late; the pilots struggled with the controls and managed to get airborne again for 17 seconds, but the aircraft crashed inverted into the water. All 70 passengers and crew died.[8][12][13]

Aftermath[edit]

Search, rescue, and recovery[edit]

After the crash, recovery crews found nine bodies floating; the rest of the bodies had sunk with the aircraft.[4]

Investigation[edit]

The Commission of Accident Investigations (CAI) of the Director General of Air Transport (DGAT) of Peru wrote the final accident report.[14]

The chief Peruvian accident investigator, Guido Fernández Lañas, was the uncle of the co-pilot, David Fernández. There were some reservations about the potential conflict of interest, but the National Transportation Safety Board-appointed investigator, Richard Rodriguez, determined that Fernández Lañas could properly investigate the accident.[4]

The Peruvian Navy collected the floating wreckage. After the Peruvian authorities asked for assistance, the United States Navy provided equipment to locate the underwater wreckage of the Boeing 757 and retrieve its flight data recorder and cockpit voice recorder.[4]

Later investigation into the accident revealed that adhesive tape had been accidentally left over some or all of the static ports (on the underside of the fuselage) after the aircraft was cleaned, eventually leading to the crash. Employee Eleuterio Chacaliaza had left the tape on by mistake.[15]

The static ports are vital to the operation of virtually all of those flight instruments that provide basic aerodynamic data such as airspeed, altitude and vertical speed, not only to the pilots but also to the aircraft's computers, which provide additional functions, such as warnings when flight characteristics approach dangerous levels. The blockage of all of the static ports is one of the few common-failure modes resulting in total failure of multiple basic flight instruments and as such is regarded as one of the most serious faults that can occur within the avionics systems.[16]

The design of the aircraft did not incorporate a system of maintenance covers for the static ports. Such covers are commonly employed in aviation for blocking access to critical components when the aircraft is not in operation and are generally a bright color and carry flags (which may have "remove before flight" markings). Instead, the design of the aircraft and the relevant maintenance procedure called for the use of adhesive tape to cover the ports.[16]

As a result of the blocked static ports, the basic flight instruments relayed false airspeed, altitude and vertical speed data. Because the failure was not in any of the instruments, but rather in a common supporting system, thereby defeating redundancy, the erroneous altimeter data was also broadcast to air traffic control, which was attempting to provide the pilots with basic flight data. This led to extreme confusion in the cockpit as the pilots were provided with some data (altitude) which seemed to correlate correctly with instrument data (altimeter) while the other data provided by ATC (approximate airspeed) did not agree. Although the pilots were quite cognizant of the possibility that all of the flight instruments were providing inaccurate data, the correlation between the altitude data given by ATC and that on the altimeter likely further compounded the confusion. Also contributing to their difficulty were the numerous cockpit alarms that the computer system generated, which conflicted both with each other and with the instruments. This lack of situational awareness was revealed by the cockpit voice recorder transcript.[17] That the flight took place at night and over water, thus not giving the pilots any visual references, was also identified as a major factor.[16] The official accident report concluded that the flight crew, distracted by the conflicting warnings, did not heed the radar altimeter reading after descending through 2,500 feet.[8]

Legal settlement[edit]

Mike Eidson, an American attorney, represented 41 passengers and crew in a lawsuit contending that the aircraft's manufacturer, Boeing, bore responsibility for the disaster, as the company ought to have foreseen the misuse of its products.[4][18] The suit was filed against Boeing in federal court in Miami in May 1997. According to the complaint, the flightdeck errors were caused by careless maintenance by Aeroperú and negligence and defective design by Boeing. Boeing argued that it was not at fault, and that responsibility for the accident lay with the employee who did not remove the tape from the static ports, and the aircraft's pilot for not noticing the tape still applied by visual check. Richard Rodriguez of the NTSB said that it was understandable that Schreiber did not find the tape because the maintenance worker had used duct tape instead of the brightly colored tape that he was supposed to use. In addition, Rodriguez said that the pitot-static ports were high above the ground, meaning that Schreiber could not have seen the tape against the fuselage.[4] After extensive[vague] litigation, the parties agreed to transfer the case against Boeing and Aeroperú to an international arbitration in Santiago, for a determination of the damages. The defendants agreed not to contest liability in Chile.[18]

On 13 December 1999, family members of the flight's passengers received one of the largest compensations stemming from an aviation accident outside the United States aboard a non-U.S. carrier, averaging nearly $1 million per victim.[4] Eidson stated that the manner of the crash resulting in the passengers' drowning was responsible for the large settlements.[4]

Aeroperú as a whole[edit]

After the accident, Aeroperú changed the number of its evening Miami-Lima-Santiago Boeing 757 service to Flight 691.[19] The Flight 603 incident contributed to the eventual demise of Aeroperú, which was already plagued with financial and management difficulties.[4] As a result of the crash of Flight 603 and the large amount of money paid for the settlements[failed verification] [20][11] (which had aggravated the already existing financial issues even further), Aeroperú declared bankruptcy and ceased all operations in March 1999.[21][22]

Criminal prosecution[edit]

Chacaliaza was convicted in Peru for negligent homicide and given a two-year suspended sentence in 1998. [23] Four other defendants were acquitted. Chacaliaza said he would appeal the ruling, claiming that sabotage brought down the plane and that he had removed the adhesive tapes.[24]

Peruvian air accident investigator Guido Fernández criticized the move; he argued that Chacaliaza, who was relatively uneducated, had little understanding of what he did, and that his supervisors ultimately bore more responsibility for the crash.[4]

In popular culture[edit]

See also[edit]

Similar events[edit]

References[edit]

  1. ^ Ranter, Harro. "ASN Aircraft accident Boeing 757-23A N52AW Lima, Peru". aviation-safety.net. Retrieved 2019-06-04.
  2. ^ "N52AW Aeroperú Boeing 757-200". www.planespotters.net. Retrieved 2020-05-15.
  3. ^ "AeroPeru N52AW (Boeing 757 - MSN 25489) (Ex XA-SKR XA-SME)". www.airfleets.net. Airfleets aviation. Retrieved 2020-05-15.
  4. ^ a b c d e f g h i j k l m "Flying Blind", Mayday [documentary TV series]
  5. ^ "Searchers comb Pacific for more bodies after Peruvian crash." CNN. October 2, 1996. Retrieved on 11 June 2009.
  6. ^ "Murieron 70 personas en un avión peruano que cayó al mar." Clarín Digital. October 3, 1996. Retrieved on 11 June 2009.
  7. ^ "CRONICA" (http://web.archive.org/web/20010513232451/http://www.copesa.cl/DE/1996/_Des1996/10_02/cronica.html Archive]). Consorcio Periodístico de Chile S.A. 2 October 1996. Retrieved on 11 June 2009.
  8. ^ a b c d e f g "ACCIDENT OF THE BOEING 757-200 AIRCRAFT OPERATED BY EMPRESA DE TRANSPORTE AÉREO DEL PERÚ S.A. AEROPERÚ" (PDF). www.skybrary.aero. Retrieved 2018-12-29.
  9. ^ "#OnThisDay in 1996, Aeroperú Flight 603 crashes into the ocean off Pasamayo, Peru". AIRLIVE. AirCrashMayday. 2016-10-02. Retrieved 2020-05-15.
  10. ^ "Seconds from disaster - AeroPeru Flight 603 Flying Blind - video dailymotion". Dailymotion. Retrieved 2020-05-15.
  11. ^ a b "10 Controversial Cases Of Negligent Homicide". Listverse. 2014-04-21. Retrieved 2020-05-15.
  12. ^ "Case Study: Aero Peru 603". code7700.com. Retrieved 2020-05-15.
  13. ^ "70 on Peru Jet Believed Dead After Crash In the Pacific". The New York Times. Associated Press. 1996-10-03. ISSN 0362-4331. Retrieved 2020-05-15.
  14. ^ Walters, James M. and Sumwalt III, Robert L.. "Aircraft Accident Analysis: Final Reports." McGraw-Hill Professional, 2000. p. 98. Retrieved from Google Books on 11 May 2011. ISBN 0-07-135149-3, ISBN 978-0-07-135149-2. "Robles, Ricardo, Presidente, Commission of Accident Investigations (CAII), Director General of Air Transport (DGAT) of Peru. 1996. Final report, Boeing 757-200 Accident, Aeroperu, 2 October 1996. Lima, Peru."
  15. ^ "World News Briefs; $29 Million for Victims Of 1996 Peru Air Crash". The New York Times. Reuters. 22 January 1998. ISSN 0362-4331. Retrieved 11 June 2009.
  16. ^ a b c Casey, Steven. The Atomic Chef, Caught on Tape. Aegean Publishing Company, 2006: Santa Barbara. p. 131 ISBN 9780963617866
  17. ^ "Close-Up: Aeroperu 603 Voice Recorder Transcription (English Translation)". avweb.com. Retrieved 26 May 2015.
  18. ^ a b "Aeroperu Crash Victims Win Landmark Award." Colson Hicks Eidson. December 13, 1999. Retrieved on June 1, 2009.
  19. ^ Volando (Aeroperú's inflight magazine), Issue 17, July–August 1997
  20. ^ "Aeroperu Crash Victims Win Landmark Award in FL". Colson Hicks Eidson. Retrieved 2020-05-15.
  21. ^ "Information about Aeroperú". Aero Transport Data Bank. Retrieved 29 December 2018.
  22. ^ "World Airline Directory". Flight International. 21 March 2000: 55. Retrieved 29 December 2018.
  23. ^ "DEUDOS DEL ACCIDENTE AEROPERU PIDEN MAYOR REPARACION CIVIL" [DEBT OF THE AIRCRAFT ACCIDENT REQUEST GREATER CIVIL REPAIR]. cdn.preterhuman.net (in Spanish). 1998-08-11. Retrieved 2020-05-15.
  24. ^ "AEROPERÚ INDEMNIZA VÍCTIMAS DE ACCIDENTE" [AIRPORT INDEMNIFIES VICTIMS OF ACCIDENT]. El Tiempo (in Spanish). 1998-01-22. Retrieved 2020-05-15.
  25. ^ "Flying Blind". Mayday. Season 1. Episode 4. 2003. Discovery Channel Canada / National Geographic Channel.
  26. ^ "Who's Flying the Plane?". Mayday. Season 6. Episode 3. 2007. Discovery Channel Canada / National Geographic Channel.
  27. ^ "Step inside the cockpit of six real-life air disasters". New York Post. January 26, 2014. Retrieved March 26, 2018.

External links[edit]

External image
airliners.net's Photo gallery