LATAM Perú Flight 2213

LATAM Perú Flight 2213 was scheduled to depart Jorge Chávez International Airport in Lima at 14:55 PET (19:55 UTC) and arrive at Inca Manco Cápac International Airport in Juliaca at 16:30 PET (21:30 UTC).[6] The weather at Jorge Chávez Airport at the time reported a 10-knot (19 km/h; 12 mph) southerly wind, visibility of at least 10 km (6.2 mi), and a broken cloud layer at 2,100 ft (640 m).[7]

The aircraft commenced its takeoff roll on runway 16 at 15:11. During the take-off roll, multiple airport crash tenders and fire engines on a planned emergency drill crossed the runway in front of the accelerating aircraft.[1][8] The pilots rejected the takeoff in an attempt to avoid a collision but ended up hitting one of the firetrucks, which had also turned to avoid the collision.[7] A video posted on social media showed the moment the aircraft collided with one of the trucks, with the aircraft's right engine separating and the right landing gear collapsing.[7] Another video posted on social media showed the plane tipped over to its right side as it moved across the runway on fire as it stopped.[9] The aircraft came to rest 2,500 metres (8,200 ft) down the runway.[7] Several photos of the aftermath showed a destroyed fire engine and the aircraft resting on its right wing with fire damage to the rear fuselage.[7]

The aircraft involved in the accident was a five-year-old Airbus A320neo with manufacturer serial number 7864, registered as CC-BHB. It was delivered to LATAM Chile in November 2017. The aircraft was powered by two Pratt & Whitney PW1127G engines. The aircraft was damaged beyond repair and was subsequently written off. It was the first hull loss of an A320neo.[4]

The captain, age 35, had logged 8,229 flight hours, including 3,115 hours on the Airbus A320. The first officer, age 30, had 3,390 flight hours, with 583 of them on the Airbus A320.[10]^: 20–21

As a result of the accident Lima Airport Partners suspended all operations at the airport until they resumed on 20 November.[1][7]

The pilots of the aircraft were arrested soon after the accident and held in custody for 24 hours, prompting the International Federation of Air Line Pilots' Associations (IFALPA) to criticize the Peruvian government for acting contrary to International Civil Aviation Organization guidelines, saying that the arrest and detention were "extremely detrimental to flight safety and can only hinder the investigation." IFALPA said that the arrest could create the public impression that the accident was intentionally caused by the pilots rather than by "technical issues or a string of errors originating from multiple factors."[11]

The Air Traffic Control had given the Airbus Crew Takeoff Clearance. Lima's Airport Authority coordinated an emergency drill with the Air Traffic Authority. The exercise began at 3:10 pm local time, and the LATAM aircraft hit the firetruck at 3:11 pm. ATC confirmed the start of the exercise. The rescue team was under the impression that their drill clearance also included crossing the active runway which wasn't the case.

Firefighter Manuel Villanueva, the only survivor of the three-man fire engine crew, succumbed to his injuries on 17 June 2023, making him the third fatality of the accident.[12]

The accident was investigated by the Commission for the Investigation of Aviation Accidents (CIAA) with assistance from the French Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA).[7][13] The flight recorders will be sent to France for analysis.[14]

In September 2023 the CIAA released their final report, which concluded that the crash had been the result of the emergency vehicles entering the runway without permission. The emergency drill had been poorly planned by the Peruvian Corporation of Commercial Airports and Aviation (CORPAC), and coordination with the airport regarding the drill was poor. The air traffic controllers had only been notified of the drill about an hour before it occurred resulting in them having limited information. In addition, the communication between ATC and emergency responders used nonstandard terminology.[10]

• List of accidents and incidents involving commercial aircraft
• 2017 South Sudan Supreme Airlines Antonov An-26 crash
• Ozark Air Lines Flight 650 – Struck a snowplow on landing, severely damaging aircraft.
• Aeroflot Flight 3352 – Struck maintenance vehicles on landing resulting in crash.
• Western Airlines Flight 2605 – Struck runway construction equipment on landing resulting in crash.
• Singapore Airlines Flight 006 – Struck runway construction equipment on takeoff resulting in crash.