If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
A343 / B763, Barcelona Spain, 2014
From SKYbrary Wiki
|On 5 July 2014, an Airbus A340-300 taxiing for departure at Barcelona was cleared across an active runway in front of an approaching Boeing 767 with landing clearance on the same runway by a Ground Controller unaware that the runway was active. Sighting by both aircraft resulted in an accelerated crossing and a very low go around. The Investigation noted the twice-daily runway configuration change made due to noise abatement reasons was imminent. It was also noted that airport procedure involved use of stop bars even on inactive runways and that their operation was then the responsibility of ground controllers.|
| Actual or Potential
|GND, HF, RI|
|Type of Flight||Public Transport (Passenger)|
|Origin||Barcelona/El Prat Airport|
|Intended Destination||Ezeiza/Ministro Pistarini International Airport|
|Take off Commenced||Yes|
|Type of Flight||Public Transport (Passenger)|
|Origin||Moscow/Domodedovo International Airport|
|Intended Destination||Barcelona/El Prat Airport|
|Take off Commenced||Yes|
|Location - Airport|
|Airport||Barcelona/El Prat Airport|
|Tag(s)|| Extra flight crew (no training),|
Inadequate ATC Procedures
|Tag(s)|| ATC clearance error,|
ATC Unit Co-ordination
|Tag(s)|| Aircraft / Aircraft conflict,|
ATC clearance error
|Tag(s)|| ATC error,|
Incursion pre Take off,
"Change of Runway Status" is not in the list of possible values (ATC error, Accepted ATC Clearance not followed, Incursion pre Take off, Incursion after Landing, Runway Crossing, Intersecting Runways, Intersecting extended centrelines, Towed aircraft involved, Near Miss, Ground Collision, Phraseology, Intentional Premature Rotation, Vehicle Incursion, Visual Response to Conflict, R/T Response to Conflict, No Single Runway Occupancy Frequency, Change of Active Runway Configuration, Conditional Clearance, Wrong Active Runway) for this property.,
Visual Response to Conflict
|Damage or injury||No|
|Causal Factor Group(s)|
|Group(s)||Air Traffic Management|
On 5 July 2014, an Airbus A340-300 (LV-FPV) being operated by Aererolineas Argentinas on a scheduled passenger flight from Barcelona to Buenos Aires as ARG 1163 taxied across runway 02 en route to its departure runway in front of a Boeing 767-300 being operated by UTair on a passenger flight from Moscow Domodedovo to Barcelona which was on short final to land on the same runway. On sighting of the conflict, which occurred in day VMC, the 767 initiated a low go around as the A340 accelerated to expedite vacating the runway.
An Investigation was carried out by the Spanish Civil Aircraft Accident and Incident Investigation Commission (CIAIAC). By the time the event was reported, "it was no longer possible to obtain information from the FDR/CVR of either aircraft". However all relevant ATC recordings were available and were considered sufficient.
Both the aircraft involved were carrying augmented flight crews. The A340 crew was under the command of a 52 year old Captain with 17,376 hours total flying experience which included 966 hours on type. The 38 year old First Officer had 3,831 hours total flying experience which included 885 hours on type. The other two pilots were a 34 year old with 4,787 hours total flying experience which included 2,766 hours on type and a 43 year old with 5,560 hours total flying experience which included 1,163 hours on type. The 767 crew was under the command of a 49 year old Captain with 13,500 hours total flying experience which included 4163 hours on type of which 1,977 had been as Captain. The 55 year old First Officer had 9,938 hours total flying experience which included 3274 hours on type. The other two pilots were a 52 year old with 5,756 hours total flying experience which included 4,125 hours on type and a 42 year old with 2,173 hours total flying experience, all on type.
The five controllers on duty at the time were all Spanish native speakers and were as follows:
- a 55 year old Supervisor located in the Main (East) TWR; she had 22 years experience including 10 at Barcelona and a valid level 4 English language proficiency
- a 44 year old TWR controller in the Main (East) TWR; he had 14 years experience including 4 at Barcelona TWR and a valid level 5 English language proficiency
- a 38 year old Central GND controller located in South TWR; he had 5 years experience all at Barcelona and a valid level 5 English language proficiency
- a 37 year old South GND controller located in the Main(East) TWR; she had 7 years experience including 3½ years at Barcelona and a valid level 5 English language proficiency
- a 37 year old North GND controller located in the South TWR; she had 5 years experience, all at Barcelona and a valid level 5 English language proficiency
It was established that preparations were being made for the routine 0700L runway configuration change from 'night' to 'day' operations required to mitigate noise over sensitive areas around the airport. The A340 was usually an evening rather than an early morning departure but it was delayed inbound. It was initially cleared to taxi to runway 07L, an exception to the usual use of runway 07R for night departures due to the need for longer TODA of 07R. With the First Officer as PF, they began to taxi as shown on the diagram below. Then, when on taxiway 'D', ATC GND advised that take off would be on the opposite direction 25R (since the change to day time runway configuration would have taken place by the time take off would occur). The Captain took over control temporarily so that the First Officer could reprogram the FMS. They were asked to "cross runway 02 without stopping and then to turn right onto taxiway M and to stop at holding point M5".
One minute after this, the 767 crew were cleared to land on runway 02 by TWR at exactly the same time as GND cleared the A340 to "cross runway 02 where it intersects taxiway M" so as to continue taxiing towards the holding point for runway 25R. Two minutes after this, the A340 crew had reached M5 but, since the stop bar was lit, queried this with GND. In response, the controller switched off the stop bar and cleared the aircraft to continue. As the aircraft entered the runway, the Captain reported having switched on the strobe lights and asked the crew to check if they were "clear" since "with the 110º angle between taxiway M and runway 02, he was unable to see clearly to their right". At that moment, he stated that the First Officer and the relief pilot who was occupying the supernumerary crew seat behind him (i.e. the two pilots were on the right hand side of the flight deck) warned him of an approaching aircraft on short final. He stated that this had "caused him to accelerate his crossing of the runway" and noted that "the (same) two pilots then told him that the aircraft had gone around". The rest of the taxi to holding point M1 for runway 25R, was reported to have been "uneventful, with no remarks from GND control".
The 767 Captain subsequently stated that in the vicinity of 1,000 feet aal, "he had noticed an Airbus A-340 approach the holding point for runway 02" i.e. to the left of the runway. He reported that "when he realised the A340 was not going to hold short of the runway and that it was continuing to taxi, he decided to go around" and that ATC had been notified accordingly. He estimated that they had been "between 200 and 300 ft agl" at the time a go around was initiated but with no FDR data, there was no data on the actual separation achieved. The Investigation noted that the height of the A340 tail plane is just over 55 feet. Radar recorded position data showed that "the minimum horizontal distance separating (the two aircraft)" as the A340 began to enter the runway during the incursion was 1.15 nm and the minimum vertical distance separating them at that time was 200 feet. The TWR controller in position at the time stated that "when (the 767) was over the threshold, he saw it go around and as he followed it visually, he stood up and looked to his right. It was then that he saw (the A340) crossing runway 02 where it intersects with taxiway M". He added that "he was shocked and he even became upset and let out a scream when he realised what had happened". It could not be established exactly where the 767 had commenced its go around but landing performance assumes that aircraft will be at 50 feet above the runway as they cross the threshold.
Much of the Investigation was taken up with a detailed review of ATC procedures, especially since there had been a very similar runway incursion incident in 2012 at the time of the morning runway configuration change at Barcelona it when a GND controller had also cleared a departing aircraft to cross runway 02 as another aircraft was about to land on it with corresponding Safety Recommendations made. Also, another very similar incident had occurred since this one - a 2015 event in which a GND controller had again cleared a departing aircraft to cross runway 02 as another aircraft was about to land on it but in this case, had not switched off the stop bar when the aircraft crew stopped at the stop bar and queried the clearance.
The Investigation was advised by the ANSP that "consideration is being given to allowing only the (TWR- runway) controller to turn off the stop bars" but this statement did not clarify whether the idea was to pass control of stop bars on non-active runways to these controllers or cease their use for such runways.
The Investigation formally concluded that the Cause of the Serious Incident had been "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 night time to day time runway configuration change that takes place at the airport every day at 07:00".
Two Contributory Factors were also identified:
- that the (Aerolineas Argentinas) flight was not scheduled at its usual time
- that the takeoff (of the Aerolineas Argentinas aircraft) was (to be from) a non-preferred runway, which the forced it to cross the active runway on three occasions.
No Safety Recommendations were made as a result of the Investigation because although "a number of areas for improvement that would normally be the subject for safety recommendations" were identified, it was considered that both Airport Operator AENA and ANSP ENAIRE had already implemented the changes that would have been the subject of such recommendations. Nevertheless, the Investigation decided to publish the text of the 7 Safety Recommendations which, had it not been for the action taken whilst the Investigation was in progress, would have been issued for information purposes. They were as follows:
- that AENA analyse the possibility of changing the parking stands allocated to larger aircraft so as to minimize the number of times these aircraft must cross the runways en route to the thresholds for takeoff.
- that ENAIRE establish mechanisms to physically prevent someone other than the Local Controller from being able to operate the stop bar lights for the active runway.
- that ENAIRE review the location of all the control posts to ensure that the local controller has an unimpeded view of all the intersections where the various taxiways cross the active runway.
- that ENAIRE study the possibility of integrating the lighting display system into the Automated Air Traffic Control System (SACTA).
- that ENAIRE modify the Training and Qualification Plans for the Barcelona Tower to include specific training for supervisors to underscore the importance of proper coordination, in keeping with procedures, during the night time to day time runway configuration changes at the Barcelona-El Prat Airport.
- that ENAIRE analyse the possibility of having only the Supervisor sectorise each post, instead of letting the controllers sectorise their own posts before going on watch.
- that ENAIRE modify the Training and Qualification Plans for the Barcelona Tower to include specific training for air traffic control personnel to underscore the importance of proper use of standard aeronautical phraseology during communications.
The Final Report was approved on 26 October 2015 and subsequently made available in English translation.