Airport Connection Time Planner

Introduction: plan a layover you can actually make

A connection can look fine on paper and still fail in practice. Gates move, terminals are far apart, immigration halls fill up when three widebodies land together, and the aircraft door closes before the printed departure time. This planner turns that messy reality into one comparison: is the gap between your scheduled arrival and your scheduled departure at least as large as the time your transfer actually consumes? You supply the two clock times from your itinerary plus the minutes each transfer step is likely to take, and the calculator returns the required connection time, your margin, and the clock time by which you need to be standing at the departure gate.

The goal is not to predict delays. It is to give you a consistent, repeatable framework for judging risk, and to make it obvious which assumption is driving a bad result. If the answer is comfortable only because you assumed a ten-minute immigration hall, you will see that immediately and can retest with a number you actually believe.

What this connection time planner checks (and what it does not)

The tool answers one question: is my scheduled layover at least as long as the time I expect the transfer to need, with the boarding cutoff already set aside? It is most useful when you already have a specific itinerary and want a fast way to test different assumptions. You can see what happens if the immigration queue runs 35 minutes instead of 15, or if the terminal train adds 12 minutes rather than 6.

It does not forecast flight delays, gate holds, de-icing, air traffic flow programmes or irregular operations. It does not know your airport's exact layout, whether your bags are checked through, or whether your two flights are on one ticket. Those details are exactly why every input is editable: you model your own situation instead of trusting a single rule of thumb.

One design decision matters more than any other here. Older layover calculators add walking time and security time on top of the published minimum connection time. That double counts, because the published MCT is already an arrival-to-departure interval that includes the airport's ordinary walking, transfer and processing time. This planner treats MCT as a floor and compares it against a transfer budget you build yourself, taking whichever is larger.

The connection time formula: an MCT floor against your own step budget

Every quantity below is in minutes. First, add up the steps of the transfer itself — everything between the moment your inbound aircraft parks and the moment you arrive at the departure gate:

• D = deplaning, from wheels-stop to walking up the jet bridge
• I = immigration or passport control
• R = baggage reclaim and recheck (zero when bags are tagged through)
• S = security rescreening
• X = inter-terminal transit: train, bus, or an airside shuttle, including the wait
• G = walking and wayfinding inside the terminals: between the steps above and out along the departure pier to the gate

Your transfer must also finish before boarding closes, not before the aircraft pushes back. With a boarding cutoff C and a personal buffer B, the required connection time is:

The scheduled layover L is the number of minutes between the two clock times at the connecting airport. A departure earlier on the clock than the arrival is treated as the next day:

The connection is sufficient when the layover covers the requirement, and the margin is the slack you have left:

Because the formula takes a maximum rather than a sum, the result also tells you which constraint is binding. If the MCT floor is larger, the airport's own published minimum is what limits you and there is little you can do about it besides choosing a longer layover. If your step budget plus the cutoff is larger, the airport minimum is optimistic for your particular itinerary, and the individual steps are worth attacking: bags tagged through, a trusted-traveller lane, or a gate in the same concourse.

How to use the airport connection time planner

1. Enter the scheduled arrival and scheduled departure times exactly as printed on your booking, in local time at the connecting airport.
2. Pick a connection type. Selecting one loads a starting set of step minutes appropriate for that routing; every field stays editable.
3. Enter the published minimum connection time for that airport and airline if you have it. Leave the loaded default if you do not.
4. Adjust the six transfer steps so they match your itinerary. Set baggage recheck to 0 when your bags are checked through.
5. Set the boarding cutoff your airline uses and a buffer that reflects your own tolerance for stress.
6. Select Plan Connection, then change one input at a time to see how sensitive the assessment really is.

When you are comparing two itineraries, keep the buffer identical between runs. Otherwise you are comparing your mood rather than the schedules.

How to choose good step estimates (practical guidance)

The most common reason people get a surprising result is that one component was guessed far too low. Airports are systems with friction: escalators, trains, queues, signage, and a boarding door that closes on a clock nobody shows you. Use minutes that match the specific airport and time of day. If you are unsure, run a best case and a worst case rather than a single middle guess.

• Deplaning: 5 minutes from a front row on a regional jet, 15 to 25 from the back of a widebody, and more from a remote stand where you also ride a bus to the terminal.
• Immigration: US Customs and Border Protection publishes historical passport-control processing times by airport and hour; many large airports average around 15 to 20 minutes, with peaks far above that. Automated kiosks and trusted-traveller programmes cut it substantially.
• Baggage reclaim and recheck: only applies when you must collect bags at the first port of entry. Budget the belt wait plus the walk to the recheck desk. Enter 0 when your bags are tagged to the final destination and you stay airside.
• Security rescreening: standard lanes commonly run 10 to 30 minutes at busy US airports, while expedited lanes are usually under 10. Model the lane you will actually be in, not the one you hope for.
• Inter-terminal transit: include the wait as well as the ride. A train on a six-minute headway costs an average of three minutes of waiting before you even board, and landside transfers can require leaving and re-entering security.
• Walking and wayfinding: count the walking between every step, not just the last leg. Long piers at large hubs can be a 10 to 15 minute walk from the checkpoint on their own, and moving walkways only help when they are running in your direction.
• Boarding cutoff: use your airline's published gate deadline. Fifteen minutes before departure is a common domestic figure; long-haul international flights often close earlier.
• Buffer: restrooms, food, a gate change, travelling with children or with mobility needs, and plain unfamiliarity all live here.

Worked example: a 95-minute international connection at a large hub

Suppose you land at 14:10 on an inbound international flight and your onward flight departs at 15:45. The scheduled layover is L = 95 minutes. The airline publishes an international-to-domestic MCT of M = 75 minutes for that airport, boarding closes C = 15 minutes before departure, and you want a B = 15 minute buffer. Your step estimates are:

• D deplaning = 12 minutes (mid-cabin on a widebody)
• I immigration = 20 minutes
• R baggage reclaim and recheck = 18 minutes
• S security rescreening = 12 minutes
• X inter-terminal train = 8 minutes including the wait
• G walk to the gate = 8 minutes

The step budget is P = 12 + 20 + 18 + 12 + 8 + 8 = 78 minutes. Adding the boarding cutoff gives P + C = 93 minutes, which is larger than the 75-minute MCT floor, so the binding constraint is your own transfer rather than the airport minimum. The required connection time is T = max(75, 93) + 15 = 108 minutes. Since L − T = 95 − 108 = −13 minutes, the connection is 13 minutes short of your own standard, and you should be at the gate by 15:30.

Notice what the naive additive model would have said. Adding the MCT to walking and security time gives 75 + 8 + 12 + 15 = 110 minutes, an answer that looks similar but is right by accident: it double counts the walk and the checkpoint that the 75-minute MCT already covers, while completely ignoring the 18 minutes of baggage recheck that actually breaks this itinerary. Drop the recheck by checking bags through to the final destination and the budget falls to P = 60, T = max(75, 75) + 15 = 90, and the same 95-minute layover becomes workable with 5 minutes to spare.

Scenario table: how step budgets change the required time

These rows show how the binding constraint moves between the MCT floor and the step budget. Use them as starting points only; the published minimum for your airport and airline is the number that governs a ticketed itinerary.

Reading the connection assessment

The result panel reports the required time, the layover, the margin, the binding constraint, and the gate-close clock time. Treat the verdict as a planning signal, not a promise.

• Comfortable: the layover clears the requirement with real room, so ordinary friction will not sink it.
• Tight: the layover clears the requirement by only a few minutes. A slow deplaning or one long queue erases the margin.
• Risk of missing: the layover is below the required time on your own inputs. Either the airport minimum or your step budget does not fit.

If you see a shortfall, three responses are available: choose a longer layover, remove a step (bags through, same terminal, same airline, expedited screening), or accept the risk knowingly. When missing the connection means an unplanned overnight, an onward cruise, or a wedding, the sensible answer is almost always the longer layover.

Edge cases: midnight rollovers, boarding cutoffs and terminal changes

Real itineraries have quirks. The calculator handles the common ones directly, but a few deserve explanation because they change which minutes you should type in.

1) Overnight connections and date changes

If you land at 23:50 and depart at 00:40, the layover is 50 minutes even though the clock time got smaller. The planner adds 1,440 minutes whenever the raw difference is negative. A layover of exactly zero minutes is reported as zero rather than as a full day, and anything beyond a single rollover — an overnight hotel, a next-day flight — is outside this time-only model.

2) Boarding cutoffs are the real deadline

The departure time on your ticket is when the aircraft is scheduled to push back, not when you can still be let on. Carriers publish a gate deadline, commonly 15 minutes before departure for domestic flights and earlier for long-haul departures. Because the planner reserves the cutoff inside the required time, it can also tell you the exact clock time by which you must be at the gate, which is the number worth writing on your boarding pass.

3) Terminal changes and hidden transfer time

A terminal change is rarely just walking. It is walking, then waiting for a train on its headway, then riding, then walking again and re-orienting in an unfamiliar concourse. Some transfers are landside, which forces you back through security and turns a five-minute hop into a half-hour exercise. Model the wait explicitly in the inter-terminal transit field.

4) International arrivals and the first port of entry

Many countries require every arriving passenger to clear immigration and customs at the first point of entry, even when the ticket continues onward the same day. Published border-agency wait times generally measure passport control only; they exclude the walk from the gate, the baggage belt, and the recheck desk, so those minutes belong in separate fields here.

5) Groups, children and mobility needs

Moving several people through escalators, restrooms and crowded corridors takes longer than moving one person with a backpack. The buffer is the honest place to reflect that, and wheelchair assistance in particular can add a wait at both ends of the transfer.

Assumptions and limitations of this layover estimate

This connection time planner is an informational tool. It structures your thinking; it cannot guarantee that you will make or miss a flight. The limitations that matter most:

• Scheduled times only: inbound delays, gate holds and irregular operations are not predicted, and a single late arrival invalidates every number on the page.
• User-supplied estimates: queue times vary enormously by airport, hour, staffing and season. The output inherits the quality of your inputs.
• One-ticket assumption: the model says nothing about who rebooks you. On separate tickets the onward carrier generally has no obligation after an inbound delay.
• Published minimums govern tickets: a reservation system will refuse to sell a connection below the filed MCT regardless of what this page says, and some airlines file exceptions longer than the station standard.
• Steps assumed sequential: the budget adds steps end to end. In practice a little overlap exists, which makes the estimate mildly conservative — usually a feature.
• Not a guarantee: a comfortable result can still fail, and a short result can still work out.

Quick planning checklist

Once you have run the calculator, use this checklist to decide whether to adjust inputs or pick a different itinerary. Each item is a common reason people miss connections that looked reasonable on the schedule.

• Is your inbound route often late? If so, fold the typical delay into the buffer or choose a longer layover outright.
• Do you change terminals? Add the train or bus wait, not just the ride.
• Are bags checked through? If not, baggage reclaim and recheck is usually the single largest step in the budget.
• Is this the last flight of the day? A miss becomes an overnight, so raise the buffer accordingly.
• One ticket or two? Separate tickets remove your protection and your bag transfer at the same time.
• Do you know the gate deadline? Enter it as the cutoff and note the gate-close clock time the planner returns.
• Have you run a worst case? If the itinerary only works with optimistic queues, it will feel like a sprint.

Frequently asked questions about airport connections

Sources: the definition and arrival-to-departure basis of minimum connecting time come from IATA SSIM Chapter 8, Presentation, Application and Transfer of Minimum Connecting Time (MCT) Data and the IATA Station Standard Minimum Connecting Time product page; historical passport-control processing times by airport and hour are published by U.S. Customs and Border Protection Airport Wait Times, which explicitly excludes baggage collection and airport navigation; security screening guidance and expedited-lane expectations come from the Transportation Security Administration; and a representative published gate deadline is documented in United Airlines check-in and boarding times. Always confirm the official MCT and gate deadline for your own airport and airline before booking a tight itinerary.