Crash-aerien 02 OCT 1996 d'un Boeing 757-23A N52AW - Lima, Peru
ASN logo
 
 
Statuts:Accident investigation report completed and information captured
Date:mercredi 2 octobre 1996
Heure:01:11
Type/Sous-type:Silhouette image of generic B752 model; specific model in this crash may look slightly different
Boeing 757-23A
Compagnie:AeroPeru
Immatriculation: N52AW
Numéro de série: 25489/505
Année de Fabrication: 1992-11-16 (3 years 11 months)
Heures de vol:10654
Cycles:2673
Moteurs: 2 Pratt & Whitney PW2037
Equipage:victimes: 9 / à bord: 9
Passagers:victimes: 61 / à bord: 61
Total:victimes: 70 / à bord: 70
Dégats de l'appareil: Détruit
Conséquences: Written off (damaged beyond repair)
Lieu de l'accident:89 km (55.6 milles) NW de Lima, Peru (   Océan Pacifique)
Phase de vol: En vol (ENR)
Nature:Transport de Passagers Intern.
Aéroport de départ:Lima-Jorge Chávez International Airport (LIM/SPIM), Pérou
Aéroport de destination:Santiago-Arturo Merino Benitez Airport (SCL/SCEL), Chili
Numéro de vol:PL603
Détails:
AeroPeru Flight 603, a Boeing 757-200, crashed into the sea off Lima, Peru, killing all 70 occupants.
The aircraft performed a regular passenger service from Lima, Peru to Santiago, Chile. The flight took off from runway 15 at Lima Airport at 00:42 hours local time (05:42 UTC).
While climbing through an altitude of approximately 200-300 ft, the pilots noted that the airspeed and altitude indications were too low. In calm winds, the windshear warning suddenly sounded three times. The flight crew then declared an emergency.
The crew also started to receive rudder ratio and mach speed trim warnings, which were repeated throughout the flight, distracting their attention and adding to the problem of multiple alarms and warnings which saturated and bewildered them, creating confusion and chaos.
At 00:53 the flight contacted the Departure controller again, eight minutes after the initial call, reporting they "request vectors from now on". By then the aircraft had climbed over sea and the flight crew were attempting to turn back, while trying to manage all conflicting warnings.
At 00:55:07, the crew radioed: "You're going to have to help us with altitudes and speed if that's possible." And from that moment until the end, the stick shaker, overspeed and "too low – terrain" alarms began to sound.
This caused confusion and the copilot said to the captain: "...right now we're stalling." The captain disagreed: "we're not stalling. it's fictitious, it's fictitious". Referring to the stick shaker, the copilot replies "... how can we not be stalling?".
At 01:04 the flight crew was attempting to maintain 4000 feet, however one minute later they start a measured and continuous descent. The aircraft kept descending and impacted the water with the left wing and no. 1 engine at a 10 degrees angle, at a speed of 260 knots. The aircraft pulled up to about 300 feet and flew for another 17 seconds. It then rolled inverted and crashed. The captain's airspeed indicated 450 knots and altitude 9500 feet.

Investigation results showed that the aircraft's three static ports on the left side were obstructed by masking tape. The tape had been applied before washing and polishing of the aircraft prior to the accident flight.

Probable Cause:

PROBABLE PRINCIPAL CAUSE :

ERROR OF THE MAINTENANCE STAFF INCLUDING THE CREW
It can be deduced from the investigation carried out that the maintenance staff did not remove the protective adhesive tape from the static ports. This tape was not detected during the various phases of the aircraft's release to the line mechanic, its transfer to the passenger boarding apron and, lastly, the inspection by the crew responsible for the flight (the walk-around or pre-flight check), which was carried out by the pilot-in-command, [name], according to the mechanic responsible for the aircraft on the day of the accident.

CONTRIBUTING CAUSES
b.1) PERSONAL ERROR OF THE CREW
The pilot-in-command, Mr [name], made a personal error by not complying with the procedure for GPWS alarms and not noticing the readings of the radio altimeters in order to discard everything which he believed to be fictitious.
b.2) PERSONAL ERROR INCLUDING THE CREW

The co-pilot, Mr [name], made a personal error by not being more insistent, assertive and convincing in alerting the pilot-in-command much more emphatically to the ground proximity alarms.

Accident investigation:

Investigating agency: DGAT Peru
Status: Investigation completed
Accident number: final report
Download report: Final report

Sources:
» SKYbrary 
» Aviation Week & Space Technology 2.12.96 (33)
» Aviation Week & Space Technology 7 October 1996 (21-22)
» Flight International 9-15 October 1996 (8)
» NTSB Safety Recommendation A-96-141
» Scramble 210


Opérations de secours

DGAT Peru issued 34 Safety Recommendations
NTSB issued 1 Safety Recommendation

Show all...

Photos

photo of Boeing-757-23A-N52AW
photo of Boeing-757-23A-N52AW
accident date: 02-10-1996
type: Boeing 757-23A
registration: N52AW
photo of Boeing-757-23A-N52AW
accident date: 02-10-1996
type: Boeing 757-23A
registration: N52AW
 

Plan
Ce plan montre l'aéroport de départ ainsi que la supposée destination du vol. La ligne fixe reliant les deux aéroports n'est pas le plan de vol exact.
La distance entre Lima-Jorge Chávez International Airport et Santiago-Arturo Merino Benitez Airport est de 2452 km (1532 miles).
Accident location: Exact; as reported in the official accident report.

Les informations ci-dessus ne représentent pas l'opinion de la 'Flight Safety Foundation' ou de 'Aviation Safety Network' sur les causes de l'accident. Ces informations prélimimaires sont basées sur les faits tel qu'ils sont connus à ce jour.
languages: languages

Share

Boeing 757

  • 1050 built
  • 4ème loss
  • 4ème accident fatal
  • le accident 3ème le plus grave (à ce moment là)
  • le accident 4ème le plus grave (en ce moment)
» safety profile

 Océan Pacifique
  • le accident 4ème le plus grave (à ce moment là)
  • le accident 5ème le plus grave (en ce moment)
» safety profile

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org