EU-departing, connecting beyond Singapore: does EU261 still reach that far?
A single booking that starts in Vienna or Athens and continues on a Scoot-operated (or partner-operated) leg well beyond Singapore can still carry EU261 protection for that later leg — not through the ordinary direct-departure rule, but through a specific European court doctrine covering connecting journeys, and it's worth understanding as its own distinct mechanism rather than assuming it works the same way as a straightforward missed-connection claim. This guide explains why the doctrine exists and exactly when it applies.
Free eligibility check
Check your case in the form
Enter your route, date and type of disruption. We will check whether your case qualifies for a claim under EU 261/2004 or UK261.
What happened to your flight?
Claim up to €600 for a delayed or cancelled flight.
Choose the situation that applies to your flight:
The court decision behind this: Wegener v Royal Air Maroc
The Court of Justice of the European Union ruled in case C-537/17 that when a passenger holds a single reservation whose first departure is from an EU airport, EU261 protection extends to the entire connecting journey to the final destination — including delays occurring on a later leg well outside the EU, on a carrier that might not otherwise be covered on its own. The regulation follows the booking, not just the first sector.
Why this matters specifically for Scoot
Since Singapore Airlines codeshares Scoot-operated Vienna and Athens sectors under its own SQ flight numbers, and Star Alliance partners hold interline arrangements reaching Scoot via Singapore, there's a real, concrete fact pattern here: a single booking starting in the EU, continuing on a Scoot-operated leg beyond Singapore that Scoot itself wouldn't otherwise bring under EU261's reach for that specific onward sector.
The conditions that actually have to be met
A single, continuous reservation — not separate tickets for each leg. The first departure genuinely from an EU airport, meaning Vienna or Athens in Scoot's case. And a disruption occurring somewhere along that connected journey, even on the final leg well past Singapore.
What this doesn't do
It doesn't extend EU261 to a completely separate booking, even if travelled on the same day and even if you'd have caught the same connection either way. It also doesn't apply if your first departure was from Singapore rather than the EU — the doctrine specifically requires the EU-departing leg to be the start of the single booking, not somewhere in the middle of it.
A worked example
A passenger booked a single Scoot itinerary from Vienna to Singapore, continuing on a further Scoot-operated sector to a different Asian city, all under one booking reference. A delay occurred not on the Vienna-Singapore leg but on the onward sector beyond Singapore, well outside EU airspace, arriving four hours late. Because the whole journey was a single booking with its first departure from an EU airport, the Wegener doctrine extended EU261 protection to that later leg, and the passenger was entitled to compensation despite the disruption itself happening entirely outside Europe.
How do you know if your booking qualifies as "single" for this purpose?
Check whether your entire itinerary carries one booking reference (PNR) across all sectors, rather than separate confirmation numbers for different legs. A booking made in one transaction, even if it spans multiple flight numbers or even multiple operating airlines under a codeshare, generally counts as a single reservation for this purpose.
Does it matter which airline actually operated the disrupted onward leg?
Not for whether the Wegener doctrine applies in principle — what matters is that the whole journey was one booking starting in the EU. It does matter for identifying exactly who's responsible for paying, since the doctrine extends EU261's territorial reach but the disrupted leg's own operating carrier is still who you'd pursue the claim against.
Should you expect Scoot to proactively apply this doctrine, or do you need to raise it yourself?
Raise it explicitly — this is a less commonly understood mechanism than the ordinary direct-departure rule, and it's worth citing the specific case (Wegener, C-537/17) and explaining your single-booking structure clearly when submitting a claim that relies on it, rather than assuming Scoot's own claims processing will automatically recognise the scenario.
Does this doctrine apply the same way for a UK-departing booking?
There's currently no live scenario to test this against, since Scoot has no UK-departing route for a single booking to begin with — see the UK261 guide for the full picture on why UK261 doesn't currently reach Scoot in any direction.
FAQ
What is the Wegener doctrine, in simple terms?
A CJEU ruling holding that EU261 protection extends to an entire single-booking journey, including delays on a later leg outside the EU, as long as the first departure was from an EU airport.
Does this apply to a Scoot booking starting in Vienna or Athens and continuing beyond Singapore?
Yes, potentially, provided the whole journey was one continuous booking rather than separate tickets.
Does the doctrine apply if my first departure was from Singapore, not the EU?
No — it specifically requires the EU-departing leg to be the start of the single booking.
Does it matter which airline operated the disrupted onward leg?
Not for whether the doctrine applies, though it matters for identifying who's actually responsible for the compensation claim.
Should I proactively cite this doctrine when filing a claim that relies on it?
Yes — explicitly reference the single-booking structure and the underlying case, since this mechanism is less commonly recognised than the ordinary direct-departure rule.
Should you keep your full multi-sector booking confirmation as evidence?
Yes — a booking confirmation showing every sector under one reference is the key piece of evidence supporting a Wegener-based claim, so keep the complete document rather than only the boarding pass for the specific disrupted leg.
Does travel insurance interact with this specific doctrine?
No — travel insurance operates separately from EU261 statutory rights regardless of which specific legal mechanism (direct departure or the Wegener connecting-journey doctrine) brings your claim within scope.
Does this doctrine ever apply outside a codeshare or interline context?
The mechanism itself doesn't require a codeshare or interline arrangement to exist — it applies to any single booking starting from an EU airport, regardless of how the later legs happen to be operated. The SIA-Scoot codeshare simply makes this a genuinely common, concrete scenario for Scoot passengers rather than a rare edge case.
Should you expect this doctrine to be widely known among Scoot's own customer service staff?
Not necessarily — this is a more specialised legal mechanism than the ordinary direct-departure rule, so being prepared to explain it clearly, with the case reference, is a reasonable expectation rather than an assumption that staff will recognise it immediately.