Airport-change connections: how much time you really need in Paris, London, and Tokyo

1. A layover and an airport change are not the same thing

TL;DRA layover means changing gates within the same terminal or airport, with checked bags through-tagged to the final destination. An airport change means leaving the international zone, collecting your bag, taking city transit, and checking in again at another building, sometimes in another city within the same city.

Anyone who's made a one-hour connection in Frankfurt or Guarulhos knows the drill: get off the plane, walk to the next gate, board. The whole system, from baggage handling to the minimum connection time the airline calculates, exists for that logic. When the two flights depart from different airports, that system simply doesn't apply. You become an ordinary passenger leaving one airport and arriving at another, starting from zero, as if you were heading downtown to visit a friend.

The confusion starts because price comparison sites show CDG and Orly, or Guarulhos and Congonhas, as if they were interchangeable within the same itinerary. Technically they are: both cities have two airports each, and a flight landing at one doesn't rule out another taking off from the other the same day. The problem is "the same day" turning into "the same hour and a half," which is the typical gap someone leaves between two flights on a normal layover.

The table below summarizes the physical distance and real transit time for the five most common pairs sold as connections in international and domestic itineraries.

Airport pair	Distance	Drive time (no traffic)	Drive time (rush hour)	Public transit
CDG → Orly (Paris)	34 km	40-50 min	1h15-1h30	1h-1h20 (RER B + tram/OrlyVal)
Heathrow → Gatwick (London)	70 km	1h-1h15	1h45-2h+	1h15-2h (coach or train via Croydon)
Narita → Haneda (Tokyo)	85 km	1h15-1h30	2h-2h30	1h30-2h (Skyliner/Keikyu + monorail)
Fiumicino → Ciampino (Rome)	45 km	45min-1h	1h15-1h30	1h-1h45 (via Roma Termini)
Guarulhos → Congonhas (São Paulo)	40 km	50min-1h	1h30-2h15	1h-1h20 (Airport Bus Service)

None of these routes fit inside a one-and-a-half-hour buffer. That's the starting point for the rest of this article.

---

2. CDG-Orly: Paris has two airports and no train between them

TL;DRCharles de Gaulle and Orly sit 34 km apart, the closest pair on this list, but there's no direct train linking the two. The RER B plus tramway T7 or OrlyVal combination eats up 1h to 1h20, and a taxi runs between €55 and €75 in 2026, subject to périphérique traffic.

It's tempting to assume that, being the closest airports on this list, CDG and Orly are a quick fix. They aren't, because Paris's rail network wasn't designed to link airport to airport: it was designed to link airport to city center. That means any route between the two involves, in practice, a transfer somewhere along RER line B, followed by a second leg, whether that's tramway T7 to Orly or the automated VAL shuttle from Antony.

Driving or taking a taxi is the most direct option, looping around via the A86 or the A6, and takes between 40 and 50 minutes off-peak. The problem is that "off-peak" in Paris means before 7am or after 9pm. The rest of the day, especially between 4pm and 7pm, the trip easily stretches to 1h15 or more, and there's no shoulder lane or alternative: anyone stuck on the périphérique stays stuck.

Private bus operators, usually FlixBus or local competitors, run the direct route in about 1h15 to 1h45, but with few departures per day, which makes the service useless if your connection window is tight. Travelers who build this kind of itinerary themselves, buying two separate tickets on the assumption that "it's the same city," typically block off 2 hours between flights. That's not enough. The responsible minimum, factoring in traffic surprises and check-in lines at the second airport, is 4 hours.

---

3. Heathrow-Gatwick: the worst combination within London

TL;DRHeathrow and Gatwick sit 70 km apart, linked by the M25, the most congested motorway in Greater London. The coach or train trip takes anywhere from 1h15 under ideal conditions to over 2 hours during rush hour or an incident on the road.

London has six airports, and Heathrow-Gatwick is the most commonly sold combination in itineraries that mix low-cost carriers with legacy airlines, since many European budget carriers operate out of Gatwick while flag carriers operate out of Heathrow. National Express runs a direct coach between the two terminals, with a stated time of 1h15, but that figure assumes a clear M25, which rarely happens during business hours.

There's no direct train without a transfer. Options involve going into central London (Paddington or Victoria) and back out, which easily tops 2 hours, or routes via West Croydon, which skip the center but still require changing trains. Neither is fast.

Mode	Stated time	Realistic time with traffic/delays
Direct National Express coach	1h15	1h45-2h15
Train via central London (Paddington/Victoria)	1h30-1h45	2h-2h30
Train via West Croydon	1h20-1h40	1h45-2h
Private taxi	1h-1h20	1h30-2h+

Buying two separate tickets landing at Heathrow and departing from Gatwick with less than 4 hours between them is, in practice, betting against the M25. Anyone who's driven that road on a Friday knows it loses badly.

---

4. Narita-Haneda: Tokyo has two airports by design, not by accident

TL;DRNarita and Haneda sit 85 km apart, the longest distance on this list, and the trip by limousine bus or train ranges from 1h30 under good conditions to over 2h30 on a Friday afternoon. A taxi costs between ¥20,000 and ¥30,000 in 2026 and isn't any faster than the train.

Tokyo deliberately separated its two airports: Haneda sits close to the city center and handles mostly domestic flights plus a growing share of international ones, while Narita sits out in Chiba, almost at the edge of the metropolitan area, and carries the bulk of historic international traffic. The distance between them isn't a map quirk, it's an urban planning decision from decades ago, and the result is that no one in Tokyo treats this switch as trivial, not even locals.

The Keisei Skyliner takes 41 minutes from Narita to Nippori, but from there you still need another train to Haneda, usually via the Yamanote line and then the Tokyo Monorail, or a Keikyu-Keisei combination that bypasses the center. Add waiting and transfer time, and the total trip runs between 1h30 and 2 hours on a good day. The limousine bus is more comfortable, but it's subject to the same Chiba-to-center traffic, which easily blows past 2h30 on a Friday afternoon.

A taxi is expensive and doesn't solve the time problem: at ¥20,000 to ¥30,000 (something like US$130 to US$200 in 2026), the trip still takes 1h30 to 2 hours, because the bottleneck is distance and traffic, not the mode of transport. Blocking off less than 4 hours between a flight landing at Narita and another departing from Haneda is the most common recipe for a missed connection among everything covered here.

5. Fiumicino-Ciampino: Rome looks easy and isn't

TL;DRFiumicino and Ciampino sit roughly 45 km apart around the Grande Raccordo Anulare, Rome's ring road, and the trip ranges from 45 minutes off-peak to over 1h30 during heavy traffic. There's no direct train: the most reliable route runs through Roma Termini.

Both airports sit on the same side of the city, to the south and southeast, which creates a false impression of proximity. In practice, the Grande Raccordo Anulare is a ring road with unpredictable traffic, and the direct route between the two is rarely a straight line: shuttles like Terravision cover the direct trip in about 1h to 1h20, with limited departure times.

Travelers who prefer the train need to take the Leonardo Express from Fiumicino to Roma Termini, 32 minutes, then continue by regional train or bus to Ciampino, another 30 to 45 minutes. Total: 1h15 to 1h45, not counting waiting time between connections. That means going by train, despite feeling like the "safe" option in a city tourists already know, actually eats up as much time as driving during a bad traffic window.

The classic mistake here is blocking off 2 hours between a flight landing at Fiumicino, which receives the bulk of international traffic, and another departing from Ciampino, the historic hub for Ryanair and other budget carriers. Two hours looks generous for 45 km on paper. In practice, after deplaning, baggage claim, and the check-in line on the Ciampino side, little to no real transit time is left.

---

6. Guarulhos-Congonhas: the Brazilian version of the same problem

TL;DRGuarulhos and Congonhas sit 40 km apart, crossing São Paulo from end to end, and the drive ranges from 50 minutes in the early hours to over 2 hours between 5pm and 7pm. The Airport Bus Service links the two directly in about 1h to 1h20, subject to the same traffic.

São Paulo has no train or subway connecting Guarulhos to Congonhas. The only direct line is the Airport Bus Service executive coach, with regular departures and a stated time of roughly 1 hour. That figure holds up off-peak. Between 5pm and 7pm, or on any Friday afternoon, the Marginal Tietê and the Rodovia dos Bandeirantes/Anhanguera, depending on the route the driver picks, can stretch that trip past 2 hours.

São Paulo's traffic pattern has a quirk that catches both foreign visitors and Brazilians from other states off guard: there's no guaranteed "quiet hour" like in smaller cities. Accidents, roadwork, and events in the expanded downtown area can wreck the trip's predictability from one day to the next. Travelers who separately book an international flight landing at Guarulhos and a domestic flight departing from Congonhas, a common move for those connecting to destinations like inland São Paulo state, Minas Gerais, or the South, need to treat that window as inherently unpredictable, not as a fixed number on a map.

The practical rule from people who make this trip often is to never leave less than 4 hours between landing at Guarulhos and departing from Congonhas, and that's assuming the international flight lands on time. An arrival delay eats through that buffer fast.

---

7. What non-through-checked baggage means, and why it changes everything

TL;DRNon-through-checked baggage means your bag doesn't travel straight to the final destination: it's only checked as far as the first airport. You have to collect it from the carousel, physically carry it to the second airport, and check in again with a new tag, as if it were a separate trip.

When a ticket is a single booking, even with an airline change in the middle, baggage is usually tagged through to the final destination, provided there's an interline agreement between the airlines involved and the connection happens at the same airport or one with automated baggage transfer. That's what lets someone land in Frankfurt from São Paulo and board a flight to Prague without ever touching their own bag.

Switching airports breaks that system entirely, regardless of whether the ticket is single or separate. There's no shared baggage carousel between CDG and Orly, between Heathrow and Gatwick, or between Guarulhos and Congonhas. The bag comes out on the first airport's carousel, and it's on the passenger to carry it, cross the city, and present it again at the check-in counter of the second airport, within that airline's cutoff, usually between 45 minutes and 1 hour before a domestic or regional flight, more for international ones.

This has a practical implication that often goes unnoticed: the buffer can't just account for transit between airports. It has to add baggage claim (10 to 30 minutes, depending on the airport and flight volume), the transit itself, and check-in and bag-drop time at the second airport, which at busy international terminals like Heathrow or Narita easily eats another 45 minutes to 1 hour, especially if the passenger needs to declare items at customs or clear immigration again.

---

8. Separate tickets: the detail that decides who eats the loss

TL;DRA single ticket, even across different airlines, obligates the airline to rebook the passenger if they miss the connection because of its own delay. Separate tickets, bought as independent bookings, create no such obligation: missing the second flight because the first ran late means buying a new one from scratch, at whatever the current price is.

This is the most underrated distinction in the entire process of building a trip with an airport change. A single ticket, identified by one booking reference (or by linked references via an interline agreement), puts the responsibility for the connection in the airline's hands. If the flight is delayed and the connection is missed, even if the second leg is operated by a different carrier, there's a contractual obligation to rebook the passenger on the next available flight, often at no extra cost.

When a passenger builds their own itinerary by buying two separate tickets, each one becomes an isolated transaction in the eyes of the law and the airline. There's no recognized MCT (minimum connection time) between them, because, formally, there's no connection at all: they're two distinct trips that happen to fall in sequence by date. If the first flight is delayed and the passenger misses the second, the second airline treats it as a no-show, meaning as if the passenger simply never showed up. No refund, no automatic rebooking.

EU Regulation (EC) 261/2004, which requires airlines to compensate for delays and cancellations, only applies within a single contract of carriage. Brazil's ANAC follows equivalent logic: rights to assistance and rebooking exist when the airline sold the connecting leg, not when the passenger decided, on their own, to chain together two separate purchases.

Situation	Single ticket (same booking reference)	Separate tickets
First flight delay breaks the connection	Airline rebooks at no cost	Passenger pays full price for a new flight
Baggage	Through-checked to final destination (same airport)	Manual collection at each airport
Right to assistance (hotel, meals)	Yes, if the delay is the airline's fault	No
Travel insurance covers the gap	Generally unnecessary	Only with a policy specifically covering "separate ticket protection"

Some travel insurance policies include a specific clause for this scenario, generally called separate ticket protection, that reimburses the cost of the second leg missed because of the first flight's delay. It's worth checking for that clause specifically, because most generic travel insurance doesn't cover this kind of loss by default.

---

9. How much time to block off, in practice

TL;DRThe practical rule for any airport change is to double the ground transit time and add 1 hour for baggage claim and re-check-in. That gives a minimum of 4 hours for the closest pairs, like CDG-Orly or Fiumicino-Ciampino, and 5 to 6 hours for Heathrow-Gatwick or Narita-Haneda.

Everything covered above converges on a practical number, not a theoretical one. Use the rush-hour transit time, not the ideal early-morning figure, because flights run late and tend to land right during the busiest hours of the day. Add 30 minutes for baggage claim, plus 45 minutes to 1 hour for check-in and bag-drop at the second airport, plus a safety margin of at least 30 minutes for the unexpected, whether that's an immigration line or unforeseen traffic.

For CDG-Orly and Fiumicino-Ciampino, that works out to a minimum of 4 hours between the first flight's landing time and the second flight's departure time. For Guarulhos-Congonhas, the same figure applies, with extra caution around Fridays and São Paulo rush hour. For Heathrow-Gatwick, the number climbs to 5 hours, given the M25's track record for congestion. For Narita-Haneda, the riskiest combination on this list, the responsible minimum is 6 hours, especially for flights landing in the afternoon.

Anyone with less time available than that minimum faces an honest choice: pay more for an itinerary operated by airlines with an interline agreement departing from the same airport, or accept the calculated risk of separate tickets, and in that case buy insurance with specific coverage for this scenario. What doesn't pay off is pretending that 2 hours can cover a distance that, best case, eats up twice that.