FlyerTalk Forums - View Single Post - How does EU261 handle multi day trips?
View Single Post
Old Mar 18, 2024 | 3:33 pm
  #2  
LX53
10 Countries Visited
20 Countries Visited
500k
All eyes on you!
 
Join Date: Nov 2022
Location: GVA/BOS
Programs: LX SEN, AFKL Plat, SK Gold, AA Plat Pro
Posts: 125
Originally Posted by Hipplewm
We are traveling as a family CHS-LHR (3 days) - LHR-BRU-FCO (13 days) - FCO-BRU-JFK - EWR-CHS

It is really only the FCO-BRU-JFK-EWR-CHS I have a question about
FCO-BRU is a Sunday (staying at the airport Sheraton)
BRU-JFK and EWR-CHS is a Monday

Is there any intermediate steps or as long as they get me to CHS on time on Monday they have met the requirements of EU261?

I am not anticipating any issues and would rather not be any issues - this is mainly for my own curiosity....especially if the BRU-JFK plane is late and we can't get to EWR in time for that flight...who is at fault and lord knows what i would have to do to prove it....

Yes, I know it is a train wreck, but trying finding 3 business saver fares for the same days...take what you can get....I am really hoping for schedule changes and get a better routing, but so far nothing....
Assuming the following: You are traveling on a single ticket with departure city CHS and arrival city FCO with a stopover in LON and a long layover in BRU. The answer is quite simple actually. The only two points that matter regarding compensation are 1. Time of arrival at final destination (CHS), and if there was a cancellation, 2. Time of new departure from FCO. Just as a normal EC261 claim.

For the NYC transfer, the min. connecting time (MCT) is 4 hours so if the delay puts you below that threshold just call the Global Services line and they'll sort it out without an issue. And I'm guessing as a GS member, you shouldn't have too many issues getting rebooked even if the delay made the connection time go to 4h05 or something and you misconnected.

Please feel free to PM me with more details though as I haven't been able to replicate the fare on UA and therefore might have made some errors in my assumptions.
LX53 is offline