FlyerTalk Forums - View Single Post - The 2023 BA compensation thread: Your guide to Regulation EC261 / UK261
Old Oct 4, 2023 | 8:49 am
  #2039  
flarmip
10 Countries Visited
100k
50 Countries Visited
5 Years on Site
 
Join Date: May 2019
Location: FL390 or the iron way
Programs: For now: BA GGL, SAS EBG, AF Plat & LH SEN
Posts: 3,331
Originally Posted by navylad
Do they protest too much? Flight was 8 minutes delayed out of SFO as rain was coming in to the aircraft when connecting to the jet bridge (they had cabin crew at the door and towels on the floor), would have been 8 minutes late at the other end too, but the go around due to a bird strike in a preceding aircraft caused this to rise to a 26 minutes delay. To be fair, there was a 40 minute ground delay at JFK, but that isn’t that unusual for the airport.

I had already been rebooked prior to our decent (IFL can and found me to let me know) so they coudldn’t blame that but I am very intrigued by their answer- as far as we are aware, til BA have said otherwise, there were no effects on slots of high winds- and no evidence of an effect of these on flight radar.

I’d put in a claim to see what what happened, given the misconnect resulted in a 4 hour delay.
Your post is a little cryptic - but I take it that you were booked to travel SFO (?)-JFK-LHR-JER, presumably departing on 28 Sep and arriving on 29 Sep, and the late arrival of BA182 (JFK-LHR for those not in the know) caused you to miss your connection onto the JER flight?

What JER flight were you originally booked on - BA1344? If so this would have been a 60 min connection (11:00-12:00), so the 33 minute delay in BA182's arrival on stand (at a B gate) would normally have made it impossible to make BA1344.

However the latter ended up leaving 55 minutes late, so actually you should have been given a chance to try and make it, particularly if you were HBO. BA1344's aircraft (G-EUPR) didn't even arrive on stand until 12:01, so it was always going to be delayed by at least 40-50 minutes, and the gate couldn't possibly have closed on time.

The go-around on BA182 cost it about 13 minutes, and it got a pretty direct routing into LHR (only one 270° turn, not even a hold), so I would have thought most of the delay was attributable to the late departure and a slightly slower than usual tailwind across the Atlantic.

It seems like this could be one worth challenging (probably through CEDR), but we'd need a few more details to confirm.
flarmip is offline