Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Aeroperú Flight 603

Coordinates:11°49′S77°51′W / 11.817°S 77.850°W /-11.817; -77.850
From Wikipedia, the free encyclopedia
1996 aviation accident in the Pacific Ocean

Aeroperú Flight 603
N52AW, the aircraft involved in the accident, pictured in January 1996
Accident
DateOctober 2, 1996 (1996-10-02)
SummaryControlled flight into water following instrumentfailure due to blockedstatic ports[1]: 43 
SitePacific Ocean, 89 km (55 mi) northwest offLima, Peru
11°49′S77°51′W / 11.817°S 77.850°W /-11.817; -77.850[1]
Map
Aircraft
Aircraft typeBoeing 757-23A
OperatorAeroperú
IATA flight No.PL603
ICAO flight No.PLI603
Call signAEROPERU 603
RegistrationN52AW
Flight originMiami International Airport
Miami,Florida, United States
1st stopoverMariscal Sucre International Airport (former)
Quito, Ecuador
Last stopoverJorge Chavez International Airport
Lima, Peru
DestinationArturo Merino Benítez International Airport
Santiago, Chile
Occupants70
Passengers61
Crew9
Fatalities70
Survivors0

Aeroperú Flight 603 (PL603/PLI603) was a scheduled passenger flight fromMiami International Airport in Miami, Florida, United States, toArturo Merino Benítez International Airport in Santiago, Chile, with stopovers inQuito, Ecuador, andLima, Peru. On October 2, 1996, theBoeing 757-23A aircraft flying the final leg of the flight crashed into the Pacific Ocean. There were no survivors among 70 people on board.

Flying over water, at night, with no visual references, the pilots were unaware of their true altitude, and struggled to control and navigate the aircraft. The investigation determined that theair data computers were unable to show correct airspeed and altitude on cockpit displays because a maintenance worker had failed to remove tape covering thepitot-static system ports on the aircraft exterior prior to departure.

Background

[edit]

Aircraft

[edit]

The aircraft, aBoeing 757-23A, was delivered new from Boeing on 2 December 1992, to leasing companyAnsett Worldwide (AWAS).[citation needed] It was leased toAeroméxico on 27 September 1993 and then sub-leased toAeroperú on April 1, 1994.[citation needed] The lease transferred back to AWAS in February 1995, and Aeroperú continued to operate the aircraft until it crashed.[citation needed]

Crew

[edit]

Thecaptain 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).[1] Thefirst 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.[1]: 4–7 

Accident

[edit]

On October 1, 1996, Aeroperú Flight 603 fromMiami International Airport had landed at theLima Airport. There were 180 passengers on the first leg of the flight on a Boeing 757. Of those, 119 had exited the plane, and the remaining passengers were transferred to another Boeing 757.[citation needed] This aircraft took off 42 minutes after midnight (05:42 UTC) on October 2.

The pilots incorrectly believed that they could figure out the actual aircraft altitude by asking the controller, but neither the pilots nor the controller realized that the altitude information displayed on the controller's screen was sent from the aircraft's Mode C Transponder. As the transponder was receiving the same erroneous altitude information being displayed on the aircraft's altimeter, the altitude on the controller's display was also incorrect.

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 were not) and believing that they were at a safe altitude,[1]: 22–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 multiplestalls, resulting in rapid loss of altitude with no corresponding change on the altimeter. While the altimeter indicated an altitude of approximately 9,700 feet (3,000 m), the aircraft's true altitude was much lower, low enough that theground proximity warning system began to send warnings; however, these warnings were not heeded due to the deluge of unreliable warnings.

Theair traffic controller instructed aBoeing 707 to take off and to help guide the 757 in to land, but it was too late. The 757's left wingtip clipped the water approximately 25 minutes after the emergency declaration, tearing off part of the left wing. The pilots desperately clawed for altitude and managed to get the 757 airborne again for 19 seconds, but due to the damage to the left wing the aircraft rolled over and slammed into the water near-inverted.[citation needed] All 70 passengers and crew died and the aircraft was destroyed.[1][2][3]

Passengers

[edit]

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

NationNumber
Chile30
Colombia1
Ecuador2
Italy2
Mexico6
New Zealand1
Peru[a]20
Spain1
United Kingdom2
United States4
Venezuela1
Total70

Of the passengers, 21 originated fromMiami; all of the originating passengers were Chilean. An additional 10 passengers had boarded inQuito. The remaining passengers had boarded inLima.[7] After the crash, recovery crews found nine bodies floating, but 61 bodies had sunk with the aircraft.[4]

Investigation

[edit]

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

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 theNational Transportation Safety Board-appointed investigator, Richard Rodriguez, determined that Fernández Lañas could properly investigate the accident.[4]

ThePeruvian Navy collected the floating wreckage. After the Peruvian authorities asked for assistance, theUnited States Navy provided equipment to locate the underwater wreckage of the Boeing 757 and retrieve itsflight data recorder andcockpit voice recorder.[4]

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

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 inavionics systems.[10]

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.[10]

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 toair 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 ofsituational awareness was revealed by thecockpit voice recorder transcript.[11] 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.[10] The official accident report concluded that the flight crew, distracted by the conflicting warnings, did not heed theGPWS alarm activated by theradar altimeter reading after descending through 2,500 feet (760 m).[1] Paradoxically, the radar altimeter was working correctly since it is independent of the other systems, even the blocked sensors that confused the on-board computer and, of course, thepressure altimeter as well.

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][12] 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 theNTSB said that it was understandable that Schreiber did not find the tape because the maintenance worker had usedduct 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 internationalarbitration inSantiago, for a determination of the damages. The defendants agreed to not contest liability in Chile.[12]

On December 13, 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]Mayday stated that the manner of the crash resulting in the passengers'drowning was responsible for the large settlements.[4]

Criminal prosecution

[edit]
Conviction
Map
AccusedEleuterio Chacaliaza, four others
ConvictedEleuterio Chacaliaza
ChargesNegligent homicide
Verdict *Four others foundnot guilty
SentenceChacaliaza:
2-yearsuspended sentence

Chacaliaza was convicted in Peru fornegligent homicide and given a two-yearsuspended sentence in 1998.[13] 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 tape.[14]

Peruvian air accident investigator Guido Fernández criticized the ruling, stating that the maintenance worker was relatively uneducated and had little understanding of what he did. Fernández argued that his supervisors bore more responsibility, yet Chacaliaza was the one prosecuted by the system.[4]

Aftermath

[edit]

After the accident, Aeroperú changed the number of its evening Miami-Lima-Santiago Boeing 757 service to Flight 691.[15]

In popular culture

[edit]

See also

[edit]

Similar events

[edit]

References

[edit]

Informational notes

  1. ^11 passengers and 9 crew

Citations

  1. ^abcdefg"ACCIDENT OF THE BOEING 757-200 AIRCRAFT OPERATED BY EMPRESA DE TRANSPORTE AÉREO DEL PERÚ S.A. AEROPERÚ"(PDF). Accident Investigation Board, Directorate General of Air Transport, Ministry of Transportation and Communications.Archived(PDF) from the original on 2 December 2012. Retrieved29 December 2018 – via SKYbrary.
  2. ^"Case Study: Aero Peru 603".code7700.com. Retrieved15 May 2020.
  3. ^"70 on Peru Jet Believed Dead After Crash In the Pacific".The New York Times. Associated Press. 3 October 1996.ISSN 0362-4331. Retrieved15 May 2020.
  4. ^abcdefghi"Flying Blind",Mayday [documentary TV series] - Posted on the official verifiedYouTube channel of Wonder Documentaries, a part of Little Dot Studios Network, a subsidiary ofAll3Media. At 3:04 the narrator states "Most [passengers] are Chileans on their way home." The portion where Richard Rodriguez speaks of how he accepted Guido Fernandez's participation is at 33:20/51:42. The part where Rodriguez discusses his view on how Schrieber missed the tape is at 45:28/51:42. Eidson speaks about the manner of death at 49:09/51:42 (theMayday narrator stating that the manner of death caused the large settlement was around 48:30). The part where Fernandez discusses his view of the maintenance worker's culpability is at 46:10/51:42. Rodriguez, Guido Fernandez, and Eidson are shown directly speaking in the documentary.
  5. ^"Searchers comb Pacific for more bodies after Peruvian crash".CNN. 2 October 1996. Archived fromthe original on 22 November 2003. Retrieved11 June 2009.There were 30 Chileans,[...]
  6. ^"Murieron 70 personas en un avión peruano que cayó al mar" [70 people died in a Peruvian plane that fell into the sea].Clarín Digital (in Spanish). 3 October 1996. Archived fromthe original on 8 July 2011. Retrieved11 June 2009.Integraban la lista 30 chilenos,[...]
  7. ^"CRONICA" [CHRONICLE].Consorcio Periodístico de Chile S.A. (in Spanish). 2 October 1996. Archived fromthe original on 13 May 2001. Retrieved11 June 2009.
  8. ^Walters, James M.;Sumwalt III, Robert L. (16 February 2000).Aircraft Accident Analysis: Final Reports.McGraw Hill Professional. p. 98.ISBN 978-0-07-137984-7. Retrieved11 May 2011 – viaGoogle Books.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.
  9. ^"World News Briefs; $29 Million for Victims Of 1996 Peru Air Crash".The New York Times. Reuters. 22 January 1998.ISSN 0362-4331. Retrieved11 June 2009.
  10. ^abcCasey, Steven (2006).The Atomic Chef, Caught on Tape. Santa Barbara: Aegean Publishing Company. p. 131.ISBN 9780963617866.
  11. ^"Close-Up: Aeroperu 603 Voice Recorder Transcription (English Translation)".avweb.com. 28 April 1997. Archived fromthe original on 15 December 2013. Retrieved26 May 2015.
  12. ^ab"Aeroperu Crash Victims Win Landmark Award".Colson Hicks Eidson. Law Firm Colson Hicks Eidson Attorneys. 13 December 1999.Archived from the original on 5 February 2020. Retrieved1 June 2009.
  13. ^"DEUDOS DEL ACCIDENTE AEROPERU PIDEN MAYOR REPARACION CIVIL" [DEBT OF THE AIRCRAFT ACCIDENT REQUEST GREATER CIVIL REPAIR].cdn.preterhuman.net (in Spanish). 11 August 1998. Retrieved15 May 2020.
  14. ^"AEROPERÚ INDEMNIZA VÍCTIMAS DE ACCIDENTE" [AIRPORT INDEMNIFIES VICTIMS OF ACCIDENT].El Tiempo (in Spanish). 22 January 1998. Retrieved15 May 2020.
  15. ^Volando (Aeroperú's inflight magazine), Issue 17, July–August 1997
  16. ^"Flying Blind".Mayday. Season 1. Episode 4. 2003.Discovery Channel Canada /National Geographic Channel.
  17. ^"Who's Flying the Plane?".Mayday. Season 6. Episode 3. 2007.Discovery Channel Canada /National Geographic Channel.
  18. ^"Step inside the cockpit of six real-life air disasters".New York Post. 26 January 2014. Retrieved26 March 2018.

External links

[edit]
External image
image iconairliners.net's Photo gallery
Aviation accidents and incidents in Peru
1960s
1970s
1980s
1990s
2000s
2010s
2020s
Retrieved from "https://en.wikipedia.org/w/index.php?title=Aeroperú_Flight_603&oldid=1324394021"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp