How Search Filters Shape Your Flight Booking Choices and Delay Rights

Search filters on Google Flights, Skyscanner, and Kayak don't just sort by price or duration—they silently determine whether you're entitled to 600 or nothing when a delay hits. A filter for "two stops" often surfaces self-transfer itineraries on separate tickets, which EU261 treats as independent contracts, meaning the airline owes zero compensation for a missed connection.

This guide maps each filter choice—stop count, booking channel, layover duration—to its legal consequences under EU261, including the 2026 reform (as of July 2026) that maintains the 250–600 baseline.

The Stop-Count Filter: How It Determines Your Compensation Rights

Most travelers assume a two-stop itinerary is a single journey. Under EU Regulation 261/2004, that assumption is worth exactly zero euros if the legs are on separate tickets. The legal definition of a "connection" is a single 13-digit ticket number covering all segments. No shared number, no compensation for a missed connection — regardless of how the search filter displayed the result.

The decision rule is simple: before purchasing any itinerary with two or more stops, verify every leg shares the same ticket number. Click "Booking details" or "Fare rules" on the checkout page. If the airline or booking site cannot show one ticket number for all segments, you are buying separate contracts of carriage. A delay on the first leg that causes you to miss the second leg triggers zero liability from either carrier under EU261.

This is where search filters become a legal trap. A "1 stop" filter on Google Flights or Skyscanner often surfaces itineraries that are self-transfers — separate tickets sold as a single search result. The filter treats the total price and duration as one trip, but the airline treats each leg as an independent flight. One FlyerTalk thread documented a London Heathrow to Munich booking on two separate Lufthansa-issued tickets through an OTA. The first leg was delayed four hours; the second leg departed on time. Compensation was denied because the ticket numbers differed, even though both flights were operated by the same airline.

A concrete scenario: searching London Heathrow to Barcelona with a "1 stop" filter returns a result showing Air France from Heathrow to Paris Charles de Gaulle, then easyJet from Paris to Barcelona. These are separate tickets. If Air France is late, easyJet has no obligation to rebook you, and EU261 does not apply to the missed connection. The 250 to 600 compensation baseline only activates for delays on the specific flight you are on — not for the downstream consequence of a separate booking. According to EU Regulation 261/2004, a missed connection on separate tickets triggers no compensation from either carrier.

Fare class codes visible in advanced search settings — Y, B, M, and others — determine upgrade and refund eligibility but have no effect on statutory delay compensation. None of these amounts apply to a missed self-transfer on separate tickets. The reform also introduced faster refund rules and cabin bag pricing transparency, but it did not change the single-ticket definition of a connection.

The practical action: after any search filter returns a multi-stop result, open the booking details page before entering payment information. Look for a single ticket number — typically a 13-digit code starting with the airline's three-digit prefix. If you see two different numbers, treat the itinerary as two separate trips. Budget for the risk of a missed connection, or rebook on a single ticket even if it costs more. That extra cost is insurance against a denied claim.rs, treat the itinerary as two separate trips. Budget for the risk of a missed connection, or rebook on a single ticket even if it costs more. That extra cost is insurance against a denied claim.rs, treat the itinerary as two separate trips. Budget for the risk of a missed connection, or rebook on a single ticket even if it costs more. That extra cost is insurance against a denied claim.

Who Actually Owes You Money? The Code-Share Trap

Most travelers assume the airline whose name is on the ticket is the one that owes them compensation when a delay hits. That assumption is wrong, and it costs passengers thousands in rejected claims every year. Under EU261, the operating carrier — the airline that actually flies the plane — is the sole entity liable for delay compensation, regardless of what flight number appears in your search results or on your boarding pass. A Delta-coded flight operated by Air France from Paris Charles de Gaulle to New York JFK means you claim against Air France, not Delta. File with the wrong carrier and the response is a form letter denying liability, often with no guidance on where to redirect the claim.

The search filter makes this trap invisible. When you select "United Airlines" on Google Flights or an OTA, the results show United flight numbers. But many of those flights are code-shares — marketing agreements where one airline sells seats on another carrier's aircraft under its own code. According to The Points Guy, the operating carrier is the entity legally responsible under EU261, but the search interface rarely surfaces that distinction. The fix is manual: before clicking "Book," find the "operated by" label on the airline's schedule page. If it is not visible, search the flight number on FlightAware, which reveals the operating carrier in its metadata. One upvoted r/awardtravel thread documented a user who booked a "British Airways" flight from London Heathrow to Chicago O'Hare that was actually operated by American Airlines. When a delay hit, BA denied the claim. The passenger had to refile with AA, losing weeks in the process.

A concrete scenario illustrates the stakes. You filter for "United Airlines" flights from Newark to Frankfurt. The result shows UA 960, but the fine print reads "operated by Lufthansa." If that flight is delayed four hours, your EU261 claim goes to Lufthansa, not United. Save the operating carrier's name at booking — screenshot the schedule page or note it in your trip file. The same logic applies to any code-share: a Japan Airlines flight number operated by American, an Emirates code on Qantas metal, a Delta reservation flown by Virgin Atlantic. The operating carrier is the one that controls the crew, the aircraft, and the delay compensation process. operating carrier's name at booking — screenshot the schedule page or note it in your trip file. The same logic applies to any code-share: a Japan Airlines flight number operated by American, an Emirates code on Qantas metal, a Delta reservation flown by Virgin Atlantic. The operating carrier is the one that controls the crew, the aircraft, and the delay compensation process.

Field threads on FlyerTalk report a common failure mode: passengers who book through an OTA see only the marketing carrier's name and assume that is the liable party. They file a claim, get rejected, and give up. The rejection letter often does not explain the code-share distinction. The practical action: after any search filter returns a result, identify the operating carrier before you pay. If the booking page does not show it, call the airline or check the flight number on FlightAware. That five-minute check is the difference between a 600 claim that lands and one that dies in a customer service black hole.s and one that dies in a customer service black hole.s and one that dies in a customer service black hole.

The Layover Duration Lie: How MCT Defaults Set You Up to Fail

The default layover filter on Google Flights, Kayak, and most OTAs is a trap. It uses the airport's published Minimum Connecting Time (MCT) as a hard floor, but MCT is a legal minimum for a single-ticket connection, not a safe planning window for a self-transfer or a tight terminal change. Search engines often display itineraries with layovers as short as 35 minutes at London Heathrow Terminal 5 to Terminal 5, because the official MCT is 60 minutes for domestic and 90 minutes for international. But that 60-minute figure assumes you never leave the sterile transit area and your inbound flight arrives at the gate on time. Field threads on FlyerTalk document a recurring failure: a passenger books a 55-minute layover at Paris Charles de Gaulle Terminal 2E to 2F. The filter allows it because the generic MCT for CDG is 60 minutes. The airport's own chart, however, lists 75 minutes for that specific terminal transfer. The airline denies boarding on the second leg at check-in, or the passenger misses the connection and has no compensation rights because the itinerary was on separate tickets.

The decision rule is simple but rarely followed: never trust a layover under 90 minutes at a major European hub — CDG, FRA, LHR, AMS — unless both legs arrive and depart from the same terminal and you are on a single ticket. As of July 2026, at London Heathrow, the MCT for Terminal 5 to Terminal 5 is 60 minutes, but Terminal 3 to Terminal 5 requires 90 minutes. A search filter set to "60 min layover" will show invalid itineraries that combine a Terminal 3 arrival with a Terminal 5 departure. The search engine does not check terminal compatibility. It only checks the airport-level MCT. One FlyerTalk thread documented a user who booked a 55-minute layover at CDG Terminal 2E to 2F. The filter allowed it, but the airport's MCT is 75 minutes for that transfer. The airline denied boarding on the second leg. The passenger lost the entire fare and had no claim under EU261 because the two flights were on separate tickets.

The concrete scenario: you filter for "Layover: 1 hour" on a CDG-FRA-MUC itinerary. The first leg arrives at Terminal 2E; the second departs from Terminal 2F. MCT is 75 minutes. Your booking may be rejected at check-in, or you will miss the connection and have no compensation rights. The search filter does not warn you. It treats the 60-minute layover as valid because the airport-level MCT is 60 minutes. The only way to catch this is to check the airport's official MCT chart before booking. Heathrow's chart is published on its website; CDG's is available through the Aéroports de Paris site. Bookmark those pages. Use them as your filter, not the search engine's default. The search filter does not warn you. It treats the 60-minute layover as valid because the airport-level MCT is 60 minutes. The only way to catch this is to check the airport's official MCT chart before booking. Heathrow's chart is published on its website; CDG's is available through the Aéroports de Paris site. Bookmark those pages. Use them as your filter, not the search engine's default.

A common tourist mistake is assuming that a longer layover on a single ticket guarantees protection. It does not. If the layover is under the airport's MCT for your specific terminal combination, the airline can refuse to check you in for the second leg, even if you booked on one ticket. The airline's contract of carriage typically states that it will not be liable for missed connections if the layover is below MCT. The search filter does not enforce this. It shows the itinerary, you book it, and the airline rejects it at the airport. The practical action: before you click "Book" on any multi-stop itinerary, open the airport's official MCT chart. Compare your arrival and departure terminals. If the layover is below the chart's number, do not book that itinerary. The airline's contract of carriage typically states that it will not be liable for missed connections if the layover is below MCT. The search filter does not enforce this. It shows the itinerary, you book it, and the airline rejects it at the airport. The practical action: before you click "Book" on any multi-stop itinerary, open the airport's official MCT chart. Compare your arrival and departure terminals. If the layover is below the chart's number, do not book that itinerary. Re-run the search with a 90-minute minimum filter, or manually select a later connection. That five-minute check is the difference between a valid booking and a forfeited fare.

Booking Channel Roulette: Direct vs. OTA and Your Claim Path

Booking through an online travel agency (OTA) like Expedia, Kayak, or Super.com introduces a structural problem for delay claims that most travelers discover only after the flight is gone. The OTA is the merchant of record for the transaction, but the airline is the operator of the flight. EU261 compensation claims must be filed against the operating carrier, not the booking agent. The OTA will tell you to contact the airline. The airline will tell you to contact the OTA. Neither party has a clear incentive to process your claim quickly. A 2022 Which? investigation found that passengers who booked through OTAs waited an average of 14 weeks longer for EU261 claim resolutions compared to direct bookers. The structural issue is that the OTA holds your payment data and itinerary, but the airline holds the operational records — delay codes, crew logs, and maintenance reports — that prove eligibility. Without direct access to those records, your claim stalls.he flight. EU261 compensation claims must be filed against the operating carrier, not the booking agent. The OTA will tell you to contact the airline. The airline will tell you to contact the OTA. Neither party has a clear incentive to resolve the claim quickly, and the passenger becomes the ping-pong ball in the middle.

The decision rule is straightforward but rarely followed: if EU261 compensation is a priority for a given itinerary, book directly with the airline. Direct bookings give you a single 13-digit ticket number that ties all legs together under one contract of carriage. That number is the key that unlocks the airline's statutory obligation to rebook you and pay compensation. Without it, you have no legal connection between the two flights, even if the OTA displayed them as a single itinerary.

If you choose to use an OTA anyway, take one protective step before you close the browser: download a PDF of the full itinerary and the e-ticket receipt. OTA apps and web portals often become inaccessible during network outages, system migrations, or when the booking is transferred to the airline's system. One upvoted thread on r/travelhacks documented a user who booked through Super.com and experienced a five-hour delay. The OTA's app showed a generic "contact the airline" message. The airline's system showed no record of the booking because the OTA had not transmitted the ticket number. The claim was never resolved. The passenger had no PDF, no screenshot, and no written evidence of the itinerary.

The edge case that catches experienced travelers is the "one stop" itinerary that is actually two separate tickets. Expedia and other OTAs sometimes display a self-transfer as a single stop because the search algorithm treats the total travel time as one journey. The booking page may show a single price and a single confirmation number, but the underlying reservation consists of two independent tickets with no legal connection. If the first leg is delayed and you miss the second, the airline will refuse to rebook you because their system does not see the second flight as part of your reservation. The OTA will say the same thing. You are left holding two separate tickets, one of which is now worthless.

A concrete scenario illustrates the trap. You search for a London Heathrow to Munich itinerary on Kayak. The results show a "1 stop" option via Frankfurt with a total price of £180. You book it. The first leg, LHR to FRA, is delayed four hours. You miss the FRA to MUC flight. Kayak's customer service tells you to contact Lufthansa. Lufthansa's check-in desk tells you that your booking shows only the LHR-FRA segment — the FRA-MUC segment is on a separate ticket number that was never linked. Lufthansa has no obligation to rebook you or pay compensation for the missed connection. The OTA's search filter presented the itinerary as a single journey, but the legal reality is two independent contracts. The only way to catch this before booking is to check that all legs share the same 13-digit ticket number. That number appears on the e-ticket receipt, not on the search results page.

The practical action is simple but requires a habit change. After any OTA search returns a multi-leg itinerary, open the airline's own website and search for the same flights. Compare the ticket numbers. If the airline's site shows a single ticket number for all legs, the OTA's itinerary is likely a protected connection. If the airline's site shows separate ticket numbers, or if the OTA's confirmation page does not display a ticket number at all, treat the itinerary as a self-transfer with zero delay protection. Re-run the search with a direct booking filter, or accept the risk and plan for a long layover that you can afford to lose.

Case Study: The 600 Self-Transfer That Cost a Traveler 1,200

The traveler who searched "BCN to PRG" on Google Flights with a "2 stops" filter thought they had found a smart workaround. The search returned BCN-FRA on Ryanair for 45, FRA-AMS on KLM for 60, and AMS-PRG on easyJet for 50 — a total of 155, compared to 235 for the direct Vueling flight. That 80 savings looked like a win. The traveler booked all three legs through the OTA in a single session, assuming the search filter's "2 stops" label meant the system would protect the connection. It did not.

The first leg, BCN-FRA, was delayed five hours due to a crew shortage. The traveler arrived in Frankfurt after the KLM flight to Amsterdam had already departed and the easyJet flight to Prague was gone. Ryanair paid that claim. But the missed KLM and easyJet flights? Zero compensation. Those were separate tickets, each an independent contract of carriage with no legal connection to the Ryanair delay. The traveler spent 300 on last-minute FRA-PRG tickets and 150 on a hotel in Frankfurt. The net result: 400 received from Ryanair, minus 450 in emergency costs, minus the 80 "savings" that turned out to be a loss. Net loss: 50, plus eight hours of stress.

Option A, what the traveler did, saved 80 upfront and lost 450 in rebooking and hotel costs, with only 400 in compensation. Net loss of 50. Option B, paying 235 for the direct Vueling flight, would have cost 80 more upfront. But if that direct flight had been delayed, the traveler would have claimed 400 under EU261 on a single ticket — a net gain of 165 if delayed, or simply no loss if on time. The direct flight also eliminated the risk of missed connections entirely. The math is not close.

A FlyerTalk sticky on intra-Europe self-transfers distills the decision rule: never self-transfer in Europe unless the savings exceed 200 and you hold travel insurance that covers missed connections. The 80 savings in this case fell far below that threshold. The rule exists because the search filter's "2 stops" label hides the legal structure. The filter treats all three legs as a single journey for display purposes, but the booking system issues separate ticket numbers. Without a single 13-digit ticket number, the airline has no obligation to rebook you or pay compensation for the missed connection. The OTA's search results page will never tell you this.

The edge case that catches repeat travelers is the "savings trap" — a self-transfer that looks cheap on the search results page but fails the 200 threshold test. One upvoted thread on r/travelhacks documented a traveler who booked BCN-PRG via a similar three-leg self-transfer, saved 90, and lost 500 when a strike hit the first leg. The thread's top comment: "You didn't save 90. If the self-transfer does not save at least 200 after that calculation, book the direct flight. Set a calendar reminder to check the ticket numbers on the confirmation page — if they are not all the same 13-digit sequence, the itinerary is a self-transfer, not a connection.

Results: Your Search Filter Checklist for Delay-Proof Booking

Before clicking "Book," the single most important verification step is confirming that every leg on your itinerary shares one 13-digit ticket number. Search filters on Google Flights, Kayak, or Skyscanner will display a "2 stops" result as a single journey, but the booking system may issue separate ticket numbers for each segment. Without a shared ticket number, the airline has zero legal obligation to rebook you or pay compensation if a delay causes you to miss the next flight. The e-ticket receipt shows this number; the search results page never will. If the OTA confirmation page does not display a ticket number, call the airline directly and ask whether the itinerary is a single booking or separate tickets. One upvoted thread on r/travelhacks documented a traveler who booked a three-leg self-transfer through an OTA, saw "2 stops" on the search filter, and assumed the system would protect the connection. The first leg was delayed, the traveler missed the remaining flights, and the airline refused compensation because each leg was on a separate ticket. The search filter had presented the itinerary as a single journey, but the legal reality was three independent contracts.

Set a minimum layover of 90 minutes at European hubs regardless of what the search filter suggests. The filter's default layover duration is often the airport's Minimum Connecting Time, which is the shortest legal connection — not a safe one. For London Heathrow, Paris Charles de Gaulle, and Frankfurt, set the minimum to 120 minutes. Check the airport's official MCT chart for your specific terminals, because a connection between Terminal 1 and Terminal 5 at Heathrow can require 90 minutes alone. The search filter will happily offer you a 45-minute layover at CDG if the MCT allows it, but a 45-minute connection leaves no buffer for taxi delays, gate changes, or slow immigration. FlyerTalk threads on intra-Europe connections consistently report that travelers who accepted the filter's default layover missed their connection at rates far higher than those who manually set a 90-minute minimum. The filter is optimizing for total travel time, not for your legal protection.

Identify the operating carrier for every code-share flight on your itinerary. Search filters display the marketing carrier's flight number — the brand you see on the search results page — but the operating carrier is the entity legally responsible for delay compensation under EU261. A flight marketed as British Airways flight BA123 may actually be operated by American Airlines, and if that flight is delayed, you claim against American Airlines, not British Airways. Save a screenshot of the "operated by" line on the booking page. This screenshot is your evidence when filing a claim, because the operating carrier's customer service may deny responsibility if you cannot prove they operated the flight. One practitioner on Reddit described a scenario where a traveler booked a code-share flight through an OTA, the operating carrier delayed the flight by four hours, and the OTA's customer service directed the traveler to the marketing carrier, who then redirected to the operating carrier. The traveler spent three weeks identifying the correct entity to claim against. The screenshot of the "operated by" line would have resolved this in five minutes.

Download a PDF of your itinerary and e-ticket receipt immediately after booking. OTA apps can go down during network outages, and your booking confirmation may become inaccessible when you need it most — during a disruption at the airport. The PDF serves as timestamped proof of the booking, which is critical for EU261 claims because the regulation requires evidence of the confirmed itinerary. The airline's app is a more reliable source for real-time updates, but the PDF is your backup if the app fails. Enable push notifications from the airline's app, not the OTA's, for schedule changes. These notifications serve as timestamped evidence of when a delay was officially communicated, which is critical for EU261 claims because the compensation clock starts from the scheduled arrival time, not from when you learned of the delay. A FlyerTalk sticky on EU261 claims notes that travelers who relied on OTA notifications often missed the three-year filing deadline because the OTA's notification was delayed or never sent. The airline's app notification is the authoritative source.

If you must self-transfer despite the risks, buy travel insurance that explicitly covers missed connections due to delay. Standard EU261 does not cover separate-ticket itineraries, and standard travel insurance often excludes missed connections unless you purchase a specific add-on. The search filter's "2 stops" label hides this legal gap. The insurance policy must state in writing that it covers missed connections on separate tickets. One common regret reported in field threads is the traveler who assumed their credit card's travel insurance covered self-transfers, only to discover the policy excluded "consequential losses from delays on separate bookings." The practical action before booking any self-transfer: read the insurance policy's definition of "missed connection" and confirm it applies to separate tickets. If the policy does not explicitly cover this scenario, the self-transfer is an uninsured risk.

Decision rule summary: Filter for non-stop or single-ticket itineraries only. If you see "2 stops" or "self-transfer" on the search results page, assume zero delay rights and price the risk accordingly. The search filter is a convenience tool, not a legal advisor. It will show you the cheapest option without disclosing that the cheapest option may leave you with no compensation if a delay hits. The concrete action you can take today: before your next multi-leg search, open the airline's own website and search for the same flights. Compare the ticket numbers. If the airline's site shows a single ticket number for all legs, the OTA's itinerary is likely a protected connection. If the airline's site shows separate ticket numbers, treat the itinerary as a self-transfer with zero delay protection. Re-run the search with a direct booking filter, or accept the risk and plan for a long layover that you can afford to lose.

What to do next

Navigating flight filters and statutory delay rights requires a methodical approach before you finalize any purchase. Use the actionable steps below to verify your ticket details, identify operating carriers, and protect your eligibility for compensation.

Also worth reading: Understanding Air India's Flight Delay Compensation A Guide to Real-Time Flight Status Tracking and Passenger Rights · Flight Delay Compensation Booking Records And Your Full Entitlement · JetBlue Flight Delay Claims Understanding Your Rights · Delta Flight Delay Compensation What EU Regulation 261/2004 Means for Your Travel Rights

Sources: going, transportation, fastcompany, travelbinger, transavia