Open Jaw Routing From Europe to Asia With a Stopover: Three Composite Scenarios Where the Math Actually Works

We have a fare rule paragraph in front of us. It is not from any specific carrier filing — it is the generic envelope that every long-haul fare family publishes in some form, under headings like "Stopovers," "Combinations," and "Routings." The text says, roughly: one stopover permitted in the country of the pricing unit's destination at an alliance hub city, combinable with open-jaw constructions on the origin side or the destination side but not both, subject to the maximum permitted mileage under the IATA TPM/MPM tables for the origin-destination city pair. That is the paragraph. Every single decision we are about to walk through turns on whether a specific routing clears those four conditions. The casual reader thinks open-jaw routing is a marketing term. It is not. It is a fare-construction rule that either permits a ticket or does not.

The question we keep getting asked — can I construct an open jaw from Europe to Asia with a stopover and have it actually price? — has the worst answer in this business. It depends. It depends on which alliance you are pricing against, whether your outbound gateway and inbound origin fall inside the same fare pricing zone, whether the stopover city has a permit allowance under the applicable fare family, and whether the routing clears the mileage cap. What we want to do here is walk through three composite scenarios. Three hypothetical travelers, three construction problems, three different outcomes. None of these are real people. They are archetypes. If you recognise yourself in one, the math is the part to copy, not the biography.

Scenario 1: The London Engineer With Family Across Two Indian Cities

Let us say you are based in Zone 1 London. Your parents live in Mumbai. Your sister moved to Bangalore last year for a tech job and you have not seen her new apartment. The constraint is not budget — the constraint is that a single LHR-BOM-LHR round trip forces a separately-ticketed domestic leg to Bangalore that the carrier will not protect. A misconnect on the international inbound creates a domestic ticket problem you alone absorb.

Picture the construction: LHR-BOM on the outbound, a self-booked ground or domestic hop from BOM to BLR, then BLR-LHR on the inbound. This is the canonical open jaw on the destination side — outbound and inbound use different cities within the same pricing zone.

Now the math. Assume the outbound LHR-BOM loads at £520 base fare in a discount economy bucket. Assume the inbound BLR-LHR loads at £540 base in the same booking class family. Open-jaw constructions price the half-round-trip at the higher of the two half-round-trip fares — so the base comes to £540 × 2 = £1,080. Add YQ, the carrier-imposed fuel surcharge, which on UK-India long-haul has loaded in the £180-£260 per direction range for several recent filing periods. Call that £400 total. Add UK APD on the London departure in long-haul economy — use £91 as a placeholder in the range APD has occupied recently. Add Indian departure and security charges on the BLR inbound at roughly £20.

Running total: £1,080 + £400 + £91 + £20 = £1,591.

Compare against the naive alternative: two separate one-way tickets. LHR-BOM one-way rarely prices below 75-80% of the round-trip because carrier pricing is asymmetric — you are paying for the option the one-way preserves. Assume that loads at £890. BLR-LHR one-way at £910. Total one-way stack: £1,800 base, before YQ doubles up and taxes stack. The open jaw saves you roughly £210 over the naive two-one-way build and, more importantly, puts both international legs on a single PNR with through-fare protection.

What the construction does not do: it does not protect the BOM-BLR surface sector. That is your problem. Book it on IndiGo with a 24-hour buffer on the arrival side and assume the domestic segment is entirely on you if anything on the international leg misbehaves.

Scenario 2: The Dubai Consultant With Two Asian Engagements

Imagine a consultant based in Dubai with a contract engagement in Singapore followed by a second engagement in Tokyo. Between the two engagements there are five days of personal time the consultant wants to spend in Singapore, which means a true stopover rather than a same-day connection.

Construction: DXB-SIN on the outbound, stopover in SIN for five days, SIN-HND for the second engagement, HND-DXB on the inbound. The key mechanic is the stopover permit. Most Asia-centric fare families permit exactly one free stopover on the outbound or return, but only if the stopover city is the carrier's operating hub. On Singapore Airlines, a SIN stopover is a permitted free stopover under most published business-class fare families. On Emirates, the same stopover requires routing through a different construction entirely because SIN is not an EK hub.

Math, SQ construction. Call the published J-class round-trip DXB-HND via SIN with SIN stopover at $3,200 base. YQ on Asia routings out of DXB runs lower than Europe-India routings — call it $180 total. Departure taxes on DXB, SIN, HND combined: roughly $90. Total: $3,470.

The separated-ticket alternative: book DXB-SIN round trip and SIN-HND round trip as distinct PNRs. $1,900 base plus $1,600 base = $3,500 base, plus duplicated YQ of $220 and duplicated departure taxes of $140. Total: $3,860. The single-PNR stopover construction saves you roughly $390 and consolidates the trip under one itinerary for expense reporting.

Here is where the Indian comparison matters, and where the foreign perspective is useful. A consultant based in Mumbai doing exactly these two engagements would normally price the trip originating DXB, not DEL or BOM. DEL-SIN-HND-DEL round trips with SIN stopover routinely price at a meaningful premium over DXB originations on the same alliance for the same cabin — the DXB fare filings on Asia routings are simply better. The Indian traveler who repositions to DXB first on a separate ticket and then flies the main construction from DXB is running a well-known arbitrage. Traders in Singapore, Dubai, and London understand this as basic cost-of-origin math. In the Mumbai and Delhi WhatsApp groups where travel hacks circulate, you see the opposite advice — "book direct, avoid connections." That advice is costing people meaningful money on exactly the high-frequency business travel where the arbitrage is cleanest.

Scenario 3: The Paris Traveler Adding Hong Kong as a Bonus

Picture a traveler based in Paris heading to Bangkok for a two-week personal trip. Three days in Hong Kong on the return sounds appealing. They do not want a separate ticket and they do not want to pay two round-trip stacks. This is functionally a stopover on the inbound leg rather than a destination-side open jaw, but the fare-construction logic rhymes.

Construction: CDG-BKK outbound, BKK-HKG on the return with a three-day stopover at HKG, HKG-CDG as the final inbound segment. The question the fare desk asks is whether the fare families published on the CDG-BKK market permit a stopover at an intermediate Asian city on the return, and whether that city must be an operating hub on the direct routing line.

Generic principle: most long-haul Asia-from-Europe fare families permit exactly one free stopover at an alliance hub city, provided the hub lies on a direct routing line between destination and origin. HKG lies on the direct routing line between BKK and CDG for carriers that hub there — Cathay Pacific being the textbook example. So on CX, the construction loads cleanly. On an alliance partner that routes BKK-CDG via the Middle East or via Central Asia, the same construction fails the direct-routing check.

Math, CX J-class. Call the round-trip CDG-BKK with HKG stopover on the return at €3,800 base. YQ on CDG-Asia J-class has been in the €400-€450 range in recent filing periods — use €420. Combined departure taxes across CDG, BKK, HKG: roughly €180. Total: €4,400.

Separated alternative: CDG-BKK round-trip at €3,400 base, plus BKK-HKG round-trip at €850 base. YQ stack: €380 + €220 = €600. Duplicated taxes: €240. Total: €5,090. The single-PNR construction saves roughly €690.

The math hides the real question, though. Is HKG the right stopover? If the traveler actually wants to see HKG, yes. If the stopover is being used purely as a fare-construction device to extract a third destination, it is worth checking whether TPE or ICN load better as a stopover city on a different alliance's filing for the same origin-destination pair. In some filing periods they do. The cheapest stopover city is an empirical question, not a theoretical one, and the answer moves every few months.

What All Three Share

Three different travelers, three different constructions, and the same underlying mechanics. Every one of these routings works because the open-jaw or stopover permit exists inside the fare rule, not because the traveler talked the agent into it. Fare rules are binary. Either the construction prices, or it does not. There is no convincing the GDS.

Every one of them uses a gateway-to-hub-to-destination pattern where the hub is the carrier's own. Route the DXB-HND leg via Bangkok instead of Singapore and the SIN stopover permit disappears because BKK is not an SQ hub. Route the BKK-CDG leg via Dubai and the mileage cap check fails even though the stopover permit would otherwise hold. The hub has to be the right hub.

Every one of them shows savings in the three-digit or low four-digit range of the origin currency. Not alchemy. Not miracle fares. Boring, reliable savings in the £200-£700 range per trip over the naive two-round-trip build. Which is why casual travelers do not bother and why the routing-aware traveler does. The aviation desk reader already knows this — the savings compound across twenty trips a year.

And every one of them requires the traveler to own the surface sector. The BOM-BLR ground transport in the first scenario. The personal-time days in SIN in the second. The three days in HKG in the third. The international fare's delay-protection mechanics do not extend to the surface sector. Build a buffer or accept the risk.

Which Scenario Is You

If you are pricing a family trip where your outbound destination city and your inbound origin city differ but sit in the same pricing zone, you are in Scenario 1. The question to ask first is whether the carrier's open-jaw permit covers the surface distance between your two cities under the fare family you are pricing.

If you are pricing a business trip with bleisure personal time between two work segments, and the stopover city happens to be a carrier hub, you are in Scenario 2. The question to ask is whether the stopover is free or paid under your chosen fare family, and whether the routing must go through the hub or merely may.

If you are pricing a single-destination trip and want to add a bonus city on the return, you are in Scenario 3. The question is whether the bonus city lies on a direct routing line between your destination and origin under the alliance's MPM mileage cap, and whether a different alliance's filing produces a cleaner stopover city.

If none of those fit you, you are probably building a double open jaw, a round-the-world construction, or a mileage run. Those are different articles entirely.

The Honest Limits

This piece did not cover fuel-dumping constructions — the practice of using throwaway segments or hidden-city routings to break the YQ assessment on a fare. That is a separate argument because the ticketing mechanics differ and the contract-of-carriage implications are serious enough that the desk treats them as their own topic.

This piece did not cover round-the-world award ticket constructions on Star Alliance, oneworld, or SkyTeam award charts. Those live in a different framework — mileage accrual versus mileage cap versus segment cap — and they deserve their own walkthrough with their own math.

This piece did not cover the taxation questions that arise when your home tax jurisdiction does not match the ticket's origin. If you are an Indian tax resident buying a ticket that originates London, there are GST input-credit questions on the Indian side that do not apply to a ticket originating India. This desk is not qualified on the UK side to adjudicate those questions and we will not pretend otherwise.

And this piece did not cite specific carrier rule paragraph numbers, because the rule text varies by filing period and by origin-destination market, and fabricating paragraph numbers is exactly the kind of routing-theater this desk refuses to commit. When a real construction is in front of you, pull the rule text for your actual market and filing period. That is the only citation that matters.