Jan 1, 2024, 2:11 am
Last edit by: corporate-wage-slave
Four letter codes are explained in post 1 - kindly read the summary.
FAQ : Reason for flight delay or cancellation - 2024 edition
Feb 6, 2024 | 6:29 am
#226
Join Date: Apr 2005
Location: E14
Programs: BA GGL, Marriott, IHG, Sirius, Dusit, Thai, Virgin, Hyatt, BAA, AS, AA(both)
Posts: 1,407
Just wondering what caused the delay to BA534 05/02/24 LHR to NAPles
LHR 2h 35m flight NAP
London · Mon, 5 Feb
Departed 19:30
Originally scheduled departure: 14:15
Terminal 5 Gate B46
Naples · Mon, 5 Feb
Arrived 23:05 Originally scheduled arrival: 17:55
Terminal -Gate XSCH
This caused the curfew cancellation of BA535 NAP to LHR rescheduled to today 06/02/24 12.40 // 14.25
More than a few rugger buggers affected !!
LHR 2h 35m flight NAP
London · Mon, 5 Feb
Departed 19:30
Originally scheduled departure: 14:15
Terminal 5 Gate B46
Naples · Mon, 5 Feb
Arrived 23:05 Originally scheduled arrival: 17:55
Terminal -Gate XSCH
This caused the curfew cancellation of BA535 NAP to LHR rescheduled to today 06/02/24 12.40 // 14.25
More than a few rugger buggers affected !!
Feb 6, 2024 | 7:01 am
#227
Join Date: Feb 2005
Location: London
Programs: BA Gold
Posts: 333
Good, do hold onto that email. Things have been pulled forward by 30 mins so now targeting 1700 departure with an estimated off blocks time of 1710. Estimated take off time is 17:34 and with 9:28 flight time planned today that is a touch down of 03:02 and with 6 mins taxi in time on stand at 03:08 vs 00:45z scheduled as things stand at the moment. Gate closed at 16:52 so 17:10 off blocks looks good.
EDIT: Estimated off block time now 1715 and a target start up time from ATC of 1728 for a target takeoff time of 1748 or an ETA of 0324 at SEA now. 21 mins extra delay and you’ll have triggered the 3 hour mark so do keep an eye on the doors opening time in SEA.
Further EDIT: the brake recycle has now occurred at 1714. (a method used to break up delay cause allocation) so BA are responsible for 0224 of delay. The root cause is still as per your email and there was no ATC start up delay based on the 1700 and 1710 estimated departure times. The further 5 mins added to make it 1715 triggered the Target start up time of 1728, The flight crew called ready within 4 minutes of that additional 5 mins so 0224 is the BA owned delay. That said do keep an eye on the door opening time as earlier advised. If you go over 3 hours late you’ll have a perfectly valid claim.
EDIT: Estimated off block time now 1715 and a target start up time from ATC of 1728 for a target takeoff time of 1748 or an ETA of 0324 at SEA now. 21 mins extra delay and you’ll have triggered the 3 hour mark so do keep an eye on the doors opening time in SEA.
Further EDIT: the brake recycle has now occurred at 1714. (a method used to break up delay cause allocation) so BA are responsible for 0224 of delay. The root cause is still as per your email and there was no ATC start up delay based on the 1700 and 1710 estimated departure times. The further 5 mins added to make it 1715 triggered the Target start up time of 1728, The flight crew called ready within 4 minutes of that additional 5 mins so 0224 is the BA owned delay. That said do keep an eye on the door opening time as earlier advised. If you go over 3 hours late you’ll have a perfectly valid claim.
Is there a way to get the exact times from somewhere? It's very close, need some data.
Thanks again.
Feb 6, 2024 | 7:46 am
#228
Original Poster
Moderator, Iberia Airlines, Airport Lounges, and Ambassador, British Airways Executive Club
Join Date: Feb 2010
Programs: BA Lifetime Gold; Flying Blue Life Platinum; LH Sen.; Hilton Diamond; Kemal Kebabs Prized Customer
Posts: 66,505
Would you mean the door open time? Usually your watch will do here but there isn't a public published source this information.
Feb 6, 2024 | 8:35 am
#229
Join Date: Feb 2005
Location: London
Programs: BA Gold
Posts: 333
My watch says it was late, but I can just see BA arguing that it was within the 3hrs - since it was late by just a couple of minutes.
Feb 6, 2024 | 3:11 pm
#230
Join Date: Dec 2012
Posts: 3,729
Just wondering what caused the delay to BA534 05/02/24 LHR to NAPles
LHR 2h 35m flight NAP
London · Mon, 5 Feb
Departed 19:30
Originally scheduled departure: 14:15
Terminal 5 Gate B46
Naples · Mon, 5 Feb
Arrived 23:05 Originally scheduled arrival: 17:55
Terminal -Gate XSCH
This caused the curfew cancellation of BA535 NAP to LHR rescheduled to today 06/02/24 12.40 // 14.25
More than a few rugger buggers affected !!
LHR 2h 35m flight NAP
London · Mon, 5 Feb
Departed 19:30
Originally scheduled departure: 14:15
Terminal 5 Gate B46
Naples · Mon, 5 Feb
Arrived 23:05 Originally scheduled arrival: 17:55
Terminal -Gate XSCH
This caused the curfew cancellation of BA535 NAP to LHR rescheduled to today 06/02/24 12.40 // 14.25
More than a few rugger buggers affected !!
The at NAP BA 535 now operated by G-EUUW had by this point a 0510 reactionary or RA delay, and then suffered an Air Bleed maintenance message and hence a technical delay. An extension of 2300 landing into LHR had been granted but was now impossible so the technical delay took 0025 as TD and then the remainder of the delay allocation is 1210 OO or Operations Other.
So either way you are in with a valid claim.
Feb 6, 2024 | 3:13 pm
#231
Join Date: Dec 2012
Posts: 3,729
As painful as this is, BA officially got the job done within 3 hours. Times in Z/UTC/GMT are Landing 0322. Arrival 0330. Pax doors open 0334. The time needed to be breached by doors open was 0345.
Feb 7, 2024 | 9:01 am
#234
Original Poster
Moderator, Iberia Airlines, Airport Lounges, and Ambassador, British Airways Executive Club
Join Date: Feb 2010
Programs: BA Lifetime Gold; Flying Blue Life Platinum; LH Sen.; Hilton Diamond; Kemal Kebabs Prized Customer
Posts: 66,505
Wednesday 7 February 2024
One BA cancellation so far
BA1348 JER = WEAN (chucking down over there, apparently).
And loads of Lufthansa cancellations. Otherwise 311 BA departures today.. Nothing interesting on the ATC report.
One BA cancellation so far
BA1348 JER = WEAN (chucking down over there, apparently).
And loads of Lufthansa cancellations. Otherwise 311 BA departures today.. Nothing interesting on the ATC report.
Feb 7, 2024 | 11:56 pm
#235
Join Date: Dec 2012
Posts: 3,729
Wednesday sweep up
In the end BA 1344 and 1352 both to JER also became WEAN. BA 1346 managed a 2:45 ish block time due to holding and diversion back to LHR on what is a 1:05 scheduled block time.
BA 108 DXB-LHR was also canx due to flight crew sickness. OPEY is the code used.
In the end BA 1344 and 1352 both to JER also became WEAN. BA 1346 managed a 2:45 ish block time due to holding and diversion back to LHR on what is a 1:05 scheduled block time.
BA 108 DXB-LHR was also canx due to flight crew sickness. OPEY is the code used.
Feb 8, 2024 | 3:18 am
#239
Join Date: Nov 2011
Location: LHR Air Traffic Control
Programs: BAEC Silver
Posts: 903
There were two inbound emergency aircraft with ETAs only ten mins apart, so we stopped departing for a time to ease the complexity in the local airspace.
Last edited by Heathrow Tower; Feb 8, 2024 at 3:37 am