Where is plane for AY3125 coming from tonight 25/6/17
Jun 25, 2017, 9:24 am
#1
Original Poster
Join Date: Oct 2015
Location: London, UK
Programs: BAEC GGL/GFl, HH Diamond, BW Diamond, Virgin Voyages Deep Blue Extra, Blue Peter Badge Holder
Posts: 3,937
Where is plane for AY3125 coming from tonight 25/6/17
Currently has an 85 minute delay, BA phones AY on my behalf who said it was due to the delay in the inbound aircraft- any way to trace back to the delay cause and see where the plane is arriving from to give me that warm feeling that it has departed for HEL?
Jun 25, 2017, 9:59 am
#2
Moderator, Finnair
Join Date: May 2011
Location: MMX (CPH)
Programs: Eurobonus Diamond, QR Gold, AY+ Platinum, A3*G, Nordic Choice Lifetime Platinum, SJ Prio Black
Posts: 14,174
Well, not sure it will help, but flightaware "tracks" incomming flight. They think AY3125 is supposed to be OH-LXF which arrived HEL 5 hours ago from MAH.
http://flightaware.com/live/flight/FIN3125
http://flightaware.com/live/flight/F...722Z/LEMH/EFHK
So if it really is LXF to LHR then the "delayed incoming" is not correct information.
http://flightaware.com/live/flight/FIN3125
http://flightaware.com/live/flight/F...722Z/LEMH/EFHK
So if it really is LXF to LHR then the "delayed incoming" is not correct information.
Jun 25, 2017, 10:06 am
#3
Join Date: Nov 2005
Programs: BA Gold, TP Silver
Posts: 888
Well, not sure it will help, but flightaware "tracks" incomming flight. They think AY3125 is supposed to be OH-LXF which arrived HEL 5 hours ago from MAH.
http://flightaware.com/live/flight/FIN3125
http://flightaware.com/live/flight/F...722Z/LEMH/EFHK
So if it really is LXF to LHR then the "delayed incoming" is not correct information.
http://flightaware.com/live/flight/FIN3125
http://flightaware.com/live/flight/F...722Z/LEMH/EFHK
So if it really is LXF to LHR then the "delayed incoming" is not correct information.
https://www.flightradar24.com/reg/oh-lxf
Jun 25, 2017, 10:24 am
#4
Moderator, Finnair
Join Date: May 2011
Location: MMX (CPH)
Programs: Eurobonus Diamond, QR Gold, AY+ Platinum, A3*G, Nordic Choice Lifetime Platinum, SJ Prio Black
Posts: 14,174
OK.
And since none of the AY645/646 seems to be delayed, it seems that the ARN rotation wasn't planned for LXF, but something it is doing because of another plane failure.
And indeed AY645 had an equipment swap decided at 9.34 HEL time.
I'd say the "late incoming" is a "beautification" of the truth. They deliberately added a rotation knowing LXF wouldn't be back in time for AY3125.
And since none of the AY645/646 seems to be delayed, it seems that the ARN rotation wasn't planned for LXF, but something it is doing because of another plane failure.
And indeed AY645 had an equipment swap decided at 9.34 HEL time.
I'd say the "late incoming" is a "beautification" of the truth. They deliberately added a rotation knowing LXF wouldn't be back in time for AY3125.
Jun 25, 2017, 11:29 am
#5
Join Date: Mar 2015
Location: HEL
Programs: AY+ Plat and several other cards
Posts: 645
OK.
And since none of the AY645/646 seems to be delayed, it seems that the ARN rotation wasn't planned for LXF, but something it is doing because of another plane failure.
And indeed AY645 had an equipment swap decided at 9.34 HEL time.
I'd say the "late incoming" is a "beautification" of the truth. They deliberately added a rotation knowing LXF wouldn't be back in time for AY3125.
And since none of the AY645/646 seems to be delayed, it seems that the ARN rotation wasn't planned for LXF, but something it is doing because of another plane failure.
And indeed AY645 had an equipment swap decided at 9.34 HEL time.
I'd say the "late incoming" is a "beautification" of the truth. They deliberately added a rotation knowing LXF wouldn't be back in time for AY3125.
Jun 25, 2017, 11:57 am
#6
Moderator, Finnair
Join Date: May 2011
Location: MMX (CPH)
Programs: Eurobonus Diamond, QR Gold, AY+ Platinum, A3*G, Nordic Choice Lifetime Platinum, SJ Prio Black
Posts: 14,174
According to flightstats (which reads filed flightplans?) AY645 was supposed to be a A321 initially, so if that is correct, it can't have been LXF originally.