Muckus

Thanks. I wonder why it wasn't just delayed. The aircraft and crew have to fly back eventually; presumably later today. For the passengers that's tremendous number of people to accommodate on other flight. Plus, it's the last flight to LHR fron LAX each day, so no alternatives until the next afternoon. Anyway, it sounds very inconvenient.. .

mikeyfly

Presume it’ll knock on to an A380 service today? They don’t have much slack in the schedule?

i_concur

I am told it is known as the 26-LATE by the staff who work it.

I have had a totally nonsensical refusal of 261 claim by BA for the 268 last month (now with CEDR) which caused me to look at the tracking data. Its not good. It must be costing them a fortune in compensation. It was completely full when we flew, 5 CW seats out of action. I am sure there are cleverer people than me who know about scheduling but it just felt very disorganised to me.

Carfield

G-XLEE was scheduled to operate this flight. The aircraft made it to LA more or less on time, so it might be crew issue (someone can get sick and unable to operate the return flight) or a maintenance issue. I looked at expertflyer and there was no further information on the reason for the cancellation.

It looked like that it was a rather slow travel day so BA was able to accommodate most passengers on today's flight. BA 282 the 3:45pm flight was 100% full but the next BA flight BA 280 and 268 all showed availability in most cabin classes except first class. Both AA first class flights on Jan 29 still has first class seats available.

About BA and EU261, just be persistence and gave them all the facts so they will not dare to challenge you.

I have to argue hard for a delay years ago and went all the way back to tracing the aircraft used on my flight, and even the movement of the plane in the apron throughout the day using flightradar24. The aircraft was delayed because there was no staff to tow the plane to the gate. There was no reason for the delay except it was BA's fault.

I got the money in the end but it was a tough fight.

Carfield

bmiStar

Any update as to the reason why?

Pilot37

Aircraft seems to have gone tech as it only left LAX this morning (UK time - 2am-ish L.A. time) and is currently on it's way back to LHR under a strange JFK-LHR flight number (BA174)

Pilot37

bmiStar

Now showing as BA9609, west of Montreal as I post.

lukegb

BA2203 2023-01-30 LGW to CUN got hugely delayed (I'm actually on the eastbound leg, CUN to LGW, which is obviously now hugely delayed because the inbound flight... definitely won't arrive in time).

Any way I can learn why? I'm curious if it was equipment failure or missing crew (perhaps the crew member arrested the other day?), or one of the many number of other things that can go wrong... Partly so I can assess my likelihood of getting a successful UK261 claim in

marconess

Not sure reason but notice a change of equipment at16:51

mikeyfly

Make sure when the captain does his welcome, when he explains the reason(s) for delay you takes notes of exactly what was said. You may need this if a 261 claim is made and it’ll be easier than trying to remember details!

crazy8534

ZY (delayed inbound/rotational) / ZO (operational) delay.

And the return now ETD 0224

Schind

I don't know if this helps but the aircraft operating that route today, G-YMME, landed at LGW at 08:28 this morning, so it doesn't appear to be due to a delay from a previous flight.

redpalmetto

Can anyone check why BA207 to MIA on 2 Feb was cancelled? Obviously the return BA206 also cancelled.
thanks

corporate-wage-slave

This is an A380 - it started with an operational delay, and it looks like creeping delay until, i suspect, the crew went out of hours around 3pm. BA seems to be about a A380 out of sync at the moment, the rolling delays end up with a service being cancelled, so SFO then JNB and now MIA.

cheesebag

Anybody know the reason?