Boeing 737 approaches closed runway at Jorge Chávez International Airport

Casualties unknown • PE

A Copa Airlines Boeing 737-800 inadvertently began an approach to a closed runway at Lima's main airport due to incorrect flight management computer programming.

What happened

On May 23, 2025, a Copa Airlines Boeing 737-8V3, registration HP-1844CMP, was operating flight CMP131 from Panama (MPTO) to Lima (SPJC). At the time of the event, runway 16L at Jorge Chávez International Airport was closed for maintenance work, leaving runway 16R as the only operational runway.

During the arrival phase, Lima Radar authorized the crew to perform an ILS Z approach for runway 16R. However, while on final approach, air traffic controllers at Lima Tower visually observed the aircraft approaching runway 16L, which was the closed runway. The controller immediately instructed the crew to execute a go-around. The crew complied, reconfigured the aircraft for the correct ILS Z approach for runway 16R, and landed safely at approximately 15:49 local time.

The investigation

The CIAA investigation focused on why the aircraft's automated systems guided it toward the closed runway despite the active runway being 16R. The investigation examined the flight management computer (FMC) programming, the operational flight plan (OFP) provided to the crew, and the communication between the cockpit and air traffic control. The investigators also reviewed the clarity of NOTAMs and ATIS information provided to the crew and the effectiveness of the controller's hearback process.

Findings

  • The primary cause was the incorrect programming of the flight management computer (FMC) with an arrival procedure that differed from the operator's operational flight plan, causing the aircraft to automatically follow an approach for the closed runway 16L.
  • The NOTAM regarding the runway closure lacked clarity regarding the specific start and end dates for the second closure window.
  • The runway closure information had limited visual prominence within the operator's flight plan.
  • The airport's parallel runway configuration, which uses similar ILS designations (both using the "Z" variant), increased operational complexity.
  • The crew failed to detect the discrepancy between the programmed runway 16L and the authorized runway 16R during cockpit verification.
  • The ATIS information was incomplete, as it did not explicitly state the current closure of runway 16L.
  • The air traffic controller failed to detect a discrepancy during the hearback process after the crew initially reported an "ILS 16 left" approach.

Probable cause

The incident was caused by an error in the flight management computer (FMC) programming, where an incorrect arrival procedure was entered, leading the aircraft to automatically track the closed runway 16L instead of the authorized runway 16R.

Frequently asked questions

What happened in the 2025-05-23 aircraft accident near PE?

A Copa Airlines Boeing 737-800 inadvertently began an approach to a closed runway at Lima's main airport due to incorrect flight management computer programming.

What aircraft was involved and where did it happen?

The accident on 2025-05-23 involved a aircraft, registration HP-1844CMP, at PE.

What was the probable cause of the accident?

The incident was caused by an error in the flight management computer (FMC) programming, where an incorrect arrival procedure was entered, leading the aircraft to automatically track the closed runway 16L instead of the authorized runway 16R.

Loading the flight search…