Serious incident Airbus A340-313X LV-FPV, Saturday 5 July 2014
ASN logo
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Saturday 5 July 2014
Time:c. 04:50
Type:Silhouette image of generic A343 model; specific model in this crash may look slightly different    
Airbus A340-313X
Owner/operator:Aerolineas Argentinas
Registration: LV-FPV
MSN: 193
Year of manufacture:1997
Engine model:CFMI CFM56-5C4
Fatalities:Fatalities: 0 / Occupants: 348
Other fatalities:0
Aircraft damage: None
Category:Serious incident
Location:Barcelona-El Prat Airport (BCN/LEBL) -   Spain
Phase: Taxi
Nature:Passenger - Scheduled
Departure airport:Barcelona Airport (BCN/LEBL)
Destination airport:Buenos Aires/Ezeiza-Ministro Pistarini Airport, BA (EZE/SAEZ)
Investigating agency: CIAIAC
Confidence Rating: Accident investigation report completed and information captured
On 5 July 2014, at 06:20, the crew of Aerolineas Argentinas Flight AR1163, an Airbus A340-300 (LV-FPV), contacted ground control at Barcelona Airport, Spain to request information and obtain clearance for engine start-up.
At that time the airport was in the preferred nighttime configuration, with landings taking place on runway 02 and takeoffs on runway 07R. At 06:20 the crew contacted ATC, which asked the crew if they needed runway 07L due to its greater length, to which the crew replied in the affirmative.
At 06:39 the crew began the start-up sequence and at 06:40 they were informed that the runway in use would be 07R. At 06:43 they started taxiing to the 07L threshold via taxiways NS, K and D. The first officer was the pilot flying.
At 06:46, as they were taxiing on taxiway D, specifically between points D1 and D2, they were informed they would have to take off from runway 25R.
At that point the captain took over the controls so the first officer could enter the change into the Flight Management System.
While they were taxiing on taxiway D, they were cleared to cross runway 02. At 06:49, the controller asked them to cross runway 02 without stopping, to then turn right onto taxiway M and to stop at holding point M5.
At the same time, the crew of UTAir flight UT5187, a Boeing 767-300 (VQ-BSX), contacted approach control, which cleared it to continue its approach to runway 02. One minute later, at 06:50, they were cleared to land.
Also at 06:50, the crew of flight AR1163 were cleared to cross runway 02 where it intersects taxiway M, so as to continue taxiing to the holding point for runway 25R. At 06:52, the crew called to confirm they could cross the runway, and they were again cleared to do so.
At that point (same time), UT5187 executed a go-around maneuver, its crew reporting this to ATC, which ATC acknowledged.
The minimum horizontal distance separating AR1163 and UT5187 during the runway incursion was 1.15 NM, and the minimum vertical distance was 200 ft.

Causes/Contributing factors
The investigation has concluded that the incident was caused by a series of mistakes made at various control posts that were not detected in time due to a lack of coordination and due to the fact that they occurred during the nighttime to daytime runway configuration change that takes place at the airport every day at 07:00.
Contributing to the incident is the fact that the flight of the airplane with callsign ARG1163 was not scheduled at its usual time, and that the takeoff was from a non-preferred runway, which forced it to cross the active runway on three occasions.

Accident investigation:
Investigating agency: CIAIAC
Report number: IN-015/2014
Status: Investigation completed
Download report: Final report



Ground track of AR1163 (

Figure: CIAIAC


Revision history:

06-Jul-2014 17:41 harro Added
06-Jul-2014 17:41 harro Updated [Date]
06-Jul-2014 18:20 harro Updated [Narrative]
30-Aug-2021 16:22 Anon. Updated [Total occupants]
12-Sep-2021 12:44 harro Updated [Narrative, Photo]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314