Originally Posted by
Oxon Flyer
Seems there's a mismatch between the information outside ba.com (e.g. post #2 & flightstats.com), which is showing a delay of 95 minutes, and ba.com itself, which is showing a delay of 1 day and 95 minutes.
From experience of using the flight status information on EF, it may be that one of the issues is that estimated times etc are sometimes (always?) reported as times alone without a date attached to them. Often, it's possible to interpret the detailed information easily, for example if there's a series of times that shows a rolling delay that's built up into something that then runs overnight.
In this case, the EF display is a bit misleading because it only gives a current ETD and ETA, and the limitations of this data may be a possible explanation for the confusion elsewhere too. However, the big clue is that the flight was originally scheduled for yesterday evening, but hasn't yet departed!
Code:
Comments:
"DOBA86/02AUG
* OPERATIONAL FLIGHT INFO * BA 86 -1 SU 02AUG
CITY INFO HOUR (LOCAL)
YVR ESTIMATED TIME OF DEPARTURE 1930
ESTIMATED TIME OF ARRIVAL 1250 LHR
* 1A PLANNED FLIGHT INFO * BA 86 -1 SU 02AUG
APT ARR DY DEP DY CLASS/MEAL EQP GRND EFT TTL
YVR 1755 SU FAJCDRIWETY/M 744 9:20
BHKMLVSNQOG/M
LHR 1115 MO 9:20
COMMENTS-
1.YVR LHR - MEMBER OF ONEWORLD
2.YVR LHR - DEPARTS TERMINAL M
3.YVR LHR - ARRIVES TERMINAL 5
4.YVR LHR - 9/ NON-SMOKING
5.YVR LHR - ET/ ELECTRONIC TKT CANDIDATE
CONFIGURATION-
744 F 14 J 52 W 36 M 235
>"