PPRuNe Forums - View Single Post - Aerolineas Argentina A340 runway incursion BCN video
Old 17th Jul 2014, 09:05
  #120 (permalink)  
Squawk_ident
 
Join Date: Jan 2001
Location: France
Posts: 168
Likes: 0
Received 0 Likes on 0 Posts
Hearing and observing these two sites about this incident may be of interest if you take the time to do it.
On LiveATC the LEBL feed clearly proves that the Ground or TWR controller spoke in Spanish to the ARG crew on the freq. Whether both UTA and ARG ACFT were on the same freq is not clear but it seems it was not the case. Hearing the LiveATC feed is a pain because their scanner grabs all preset active freqs and continuously jumps from on the other in order to avoid blanks. But at no time the 118.1 Barcelona TWR is heard during the UTA5187 (C/S Uniform Tango Alpha 5187) final(s) approach(es). The ACFT behind the UTA is the BCS6304 (Eurotrans 6304) that was vectored behind the UTA and landed on 02. This is the one that we can see on the video during the first approach of the UTA.
One can hear on the APP freq the controller ordering the AAL66 to hold over SLL due to "we are changing runway in use" (0430Z-0500Z +25.45' LiveATC time box). This is issued just after the UTA is going around.
G/A +25.04'
hold +25.45'
LEBL 050430Z 31005KT 9999 FEW030 20/16 Q1015 NOSIG
LEBL 050500Z 33006KT 9999 FEW030 20/15 Q1016 NOSIG

Because the incident occured just before 0500z the dialog between the controller and the ARG can be heard on the subsequent audio archive 0500-0530z.

G/A UTA 0452z
LA UTA 0507
T/O ARG 0509
The last altitude reported by the UTA is 250ft although it is subject to caution because it is not related to the actual pressure but a standard 1013hpa one. At this time QNH is 1016 and the GA may be 250 or less on a standard 1013 setting which was not the case. The accelerated 12x replay doesn't help because data are not reliable at this speed. 3Hpa is about 80 feet and the actual final 250ft indicated is likely to be less than this one.

The abstract of the CIAIAC is appalling. Saying less is saying nothing. Even the indicated time of the incident is wrong. 1652 local time indicated means 0452z/ 0652 local, likely.
Squawk_ident is offline