Runway Incursion at Aeroparque Jorge Newbery Leads to Aborted Takeoff

Casualties unknown • Aeropuerto Aeroparque Jorge Newbery (Sabe) (Buenos Aires), AR

A Latam Argentina Airbus 320 aborted its takeoff at Buenos Aires' Aeroparque Jorge Newbery after the crew spotted a towed aircraft crossing the active runway.

What happened

On May 15, 2018, an Airbus 320, registration LV-BOI, operated by Latam Argentina, was preparing for takeoff from runway 13 at Aeroparque Jorge Newbery. Following instructions from the tower control, the aircraft began its takeoff roll. During the acceleration phase, the flight crew observed another aircraft, an Embraer 190 with registration LV-CPK, crossing the active runway via taxiway 3. The aircraft was being towed from the commercial apron to the industrial apron.

Upon identifying the hazard, the crew of LV-BOI successfully aborted the takeoff at approximately 60 knots. The aircraft was brought under control and vacated the runway via taxiway 4. Following the incident, the crew informed the passengers and the rest of the crew about the situation.

The investigation

The investigation focused on the coordination between air traffic control frequencies and the procedures used for runway crossings. Investigators found that the air traffic service provider, EANA, was utilizing two separate frequencies: a primary tower frequency and a surface/taxi frequency. While the primary frequency handled runway operations, the surface frequency managed movements on the apron and taxiways.

It was established that the controller on the surface frequency authorized the towing of LV-CPK to cross the active runway. Simultaneously, the controller on the primary frequency cleared LV-BOI for takeoff. The investigation noted that the surface controller was temporarily absent from their station to check air conditioning equipment in another room, requiring the primary frequency controller to manage both communications.

Findings

  • The use of separate frequencies for runway operations and runway crossings did not align with ICAO Document 9870 recommendations, which suggest that communications regarding runway use should be transferred from ground control to the aerodrome controller before an aircraft enters or crosses a runway.
  • There was a lack of effective coordination between the controllers operating the primary and surface frequencies.
  • The use of different frequencies created a fragmented communication environment, preventing both the flight crew and the towing operators from hearing critical instructions regarding runway occupancy.
  • The procedure for crossing the runway via the surface frequency was an informal practice used by the service provider and had not been formally documented.

Probable cause

The runway incursion was caused by a lack of coordination between the primary tower controller and the surface frequency controller, compounded by the use of separate communication frequencies for runway crossings which prevented the flight crew from receiving information regarding the crossing aircraft.

All Airbus A320-200 accidents →

Frequently asked questions

What happened in the 2018-05-15 AIRBUS A-320 accident near Aeropuerto Aeroparque Jorge Newbery (Sabe) (Buenos Aires), AR?

A Latam Argentina Airbus 320 aborted its takeoff at Buenos Aires' Aeroparque Jorge Newbery after the crew spotted a towed aircraft crossing the active runway.

What aircraft was involved and where did it happen?

The accident on 2018-05-15 involved a AIRBUS A-320, registration LV-BOI, operated by Aviación Comercial, at Aeropuerto Aeroparque Jorge Newbery (Sabe) (Buenos Aires), AR.

What was the probable cause of the accident?

The runway incursion was caused by a lack of coordination between the primary tower controller and the surface frequency controller, compounded by the use of separate communication frequencies for runway crossings which prevented the flight crew from receiving information regarding the crossing aircraft.

Loading the flight search…