Antonov AN-26B-100 Runway Excursion at Jorge Chávez International Airport

Casualties unknown • PE

An Antonov AN-26B-100 cargo aircraft experienced a runway excursion during takeoff at Callao, Peru, resulting in an aircraft fire and several serious injuries.

What happened

On March 15, 2005, at approximately 12:21 UTC, an Antonov AN-26B-100, registration OB-1778-P, operated by Aero Transportes S.A. (ATSA), was preparing for a cargo flight from Jorge Chávez International Airport to Andoas, Peru. The flight was operating under IFR flight rules in CAVOK weather conditions.

During the takeoff roll on runway 33, the pilot applied a slight nose-up attitude prior to reaching V1 to relieve pressure on the nose gear. Upon reaching rotation speed (VR) of 207 km//h, the pilot increased the pitch. As the aircraft reached V2 speed (242 km/h) and the landing gear was retracted, the aircraft lost altitude at approximately 5 meters above the ground. Despite having sufficient engine power, the lower fuselage and the propeller tips of the number one engine made contact with the runway surface. The aircraft slid approximately 200 meters along the pavement, causing friction that ignited a fire. The crew successfully evacuated the aircraft after the engines were shut down.

The investigation

The CIAA investigation focused on the sequence of events leading to the loss of altitude and the subsequent impact. Investigators examined the aircraft's weight and balance records, the crew's use of checklists, and the configuration of the aircraft at the time of takeoff. The investigation also reviewed the maintenance of flight recorders and the operational procedures used by the operator regarding dispatch and flight planning.

Findings

  • The aircraft was operating at an overweight condition, with a takeoff weight of 25,798 kg, exceeding the maximum allowable takeoff weight of 25,000 kg.
  • The aircraft was configured with 0° of flaps, whereas the flight manual required 15° of flaps for the specified weight.
  • The crew failed to abort the takeoff despite the failure of the configuration warning alarm.
  • There were deficiencies in the crew's dispatch, planning, execution of checklists, and Crew Resource Management (CRM).
  • The takeoff weight error was attributed to a single crew member performing both dispatcher and navigator duties, failing to follow company maintenance and operational procedures.
  • The checklists used by the crew did not align with the order of procedures specified in the aircraft's Flight Manual.

Probable cause

The accident was caused by the crew's failure to properly manage takeoff configuration and weight, specifically initiating takeoff with an overweight load and incorrect flap settings, compounded by poor checklist execution and a failure to abort the takeoff when the configuration warning failed.

Frequently asked questions

What happened in the 2005-03-15 aircraft accident near PE?

An Antonov AN-26B-100 cargo aircraft experienced a runway excursion during takeoff at Callao, Peru, resulting in an aircraft fire and several serious injuries.

What aircraft was involved and where did it happen?

The accident on 2005-03-15 involved a aircraft, registration OB-1778-P, at PE.

What was the probable cause of the accident?

The accident was caused by the crew's failure to properly manage takeoff configuration and weight, specifically initiating takeoff with an overweight load and incorrect flap settings, compounded by poor checklist execution and a failure to abort the takeoff when the configuration warning failed.

Loading the flight search…