FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Aeroperú Flight 603

2 Oct 1996 · Pacific Ocean, 55 mi northwest off Lima, Peru

Boeing 757-23A · Controlled flight into water following instrument failure due to blocked static ports

From Miami International Airport (MIA) to Comodoro Arturo Merino Benítez International Airport (SCL)

Report a problem

Event

NTSB case
DCA97RA001
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
Unknown · led by another country; figures from NTSB notifications
Event fatalities
70 · all aircraft and ground
Ground fatalities
Unknown
Occupants
70
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
Not recorded

Boeing 757-23A

Flight
PL603
Aircraft type
Boeing 757
Category
Airplane · from aircraft type
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
N52AW
Operator
Aeroperú
Onboard fatalities
70
Route
From Miami International Airport (MIA)To Comodoro Arturo Merino Benítez International Airport (SCL)
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 129: Foreign
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
Not recorded
Defining eventThe 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
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Not recorded

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft systems
  • Personnel issues › Psychological

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Aeroperú Flight 603 was a scheduled passenger flight from Miami International Airport in Miami, Florida, United States, to Arturo Merino Benítez International Airport in Santiago, Chile, with stopovers in Quito, Ecuador, and Lima, Peru. On October 2, 1996, the Boeing 757 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 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 pitot–static system ports on the aircraft exterior prior to departure.

Accident

On October 1, 1996, Aeroperú Flight 603 from Miami International Airport had landed at Jorge Chávez International 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. This aircraft took off 42 minutes after midnight (05:42 UTC) on October 2, and the crew immediately 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.

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, 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 ft, the aircraft's true altitude was much lower, low enough that the ground proximity warning system began to send warnings; however, these warnings were not heeded due to the deluge of unreliable warnings.

The air traffic controller instructed a Boeing 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. All 70 passengers and crew perished and the aircraft was completely destroyed.

Investigation and cause

Investigation

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

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.

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.

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 and polished, eventually leading to the crash. Employee Eleuterio Chacaliaza had left the tape on by mistake.

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 in avionics systems.

Boeing's design of the 757-200 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, Boeing designed the 757-200 to rely on a maintenance procedure that called for the use of adhesive tape to cover the ports.

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 design flaw resulted in a correlation between the altitude data given by ATC and that on the altimeter, which 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 destruction of the flight crew's ability to maintain situational awareness was revealed by the cockpit voice recorder transcript. 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. The official accident report concluded that the flight crew, distracted by the conflicting warnings, did not heed the GPWS alarm activated by the radar altimeter reading after descending through 2,500 ft. 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, the pressure altimeter as well.

Text from the Wikipedia article “Aeroperú Flight 603” (revision 1373840150, 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

Sources

Wikipedia article: Aeroperú Flight 603
Article
Aeroperú Flight 603
Revision
1373840150 · 2026-09-08 · retrieved 2026-09-18
Wikidata
Q381615
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA97RA001
Event ID
20001208X06864
Case number
DCA97RA001
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
Record
Wikipedia article "Aeroperú Flight 603" (page 398368, revision 1373840150); merged with NTSB case DCA97RA001 (events / aircraft)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA97RA001
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Aeroperú Flight 603" and NTSB case DCA97RA001, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • No bulk values were replaced by the NTSB case API.