The tool answers one question: Is the time between my scheduled arrival and scheduled departure at least as large as the time I expect to need?
It is most useful when you already have a specific itinerary in mind and want a quick, repeatable way to test different assumptions.
For example, you can see how the assessment changes if you increase security time from 10 minutes to 25 minutes, or if you decide you want a 30-minute personal buffer.
It does not attempt to forecast flight delays, gate holds, missed approach patterns, de-icing, or irregular operations.
It also does not know your airport’s exact layout, your airline’s boarding cutoff, or whether you must re-check bags.
Those details are why the inputs are editable: you can model your own situation rather than relying on a one-size-fits-all number.
The required connection time T is computed by adding four inputs. All values are in minutes.
- M = minimum connection time (MCT) you want to respect (airport/airline guidance)
- W = walking/transfer time between gates, concourses, or terminals
- S = security re-screening, immigration, or customs time (if applicable)
- B = personal buffer (your safety margin)
Your layover length L is the minutes between your scheduled arrival time and scheduled departure time.
If your itinerary crosses midnight (for example, arrive 23:30 and depart 01:10), the calculator treats the departure as the next day.
The connection is considered sufficient when:
How to use the planner (quick steps)
- Enter the scheduled arrival time and scheduled departure time from your booking.
- Enter minutes for MCT, walking/transfer, security/customs, and your buffer.
- Select Plan Connection to see whether your layover is sufficient and by how much.
- Adjust one input at a time (especially buffer and security/customs) to see how sensitive the result is.
If you are comparing multiple itineraries, keep your assumptions consistent.
For example, use the same buffer across options so you are comparing schedules fairly rather than changing your risk tolerance between flights.
The most common reason people get surprising results is that they underestimate one component.
Airports are systems with friction: walking distances, escalators, trains, queues, and boarding cutoffs.
Use minutes that match your specific airport and itinerary. If you are unsure, start conservative and then test a second scenario.
The goal is not a perfect prediction; it is a clear comparison between your layover and your required time.
- Arrival & departure times: use the scheduled times shown on your ticket. This tool does not forecast delays. If you are often delayed on a route, consider adding that risk into your buffer.
- Minimum connection time (MCT): if your airline/airport publishes an MCT, use it. If not, choose a realistic minimum for your connection type (domestic vs. international, terminal change, baggage re-check, or changing airlines).
- Walking/transfer time: include trains/shuttles and typical waiting time for them, not just walking speed. If you must change terminals, add time for finding signs and navigating unfamiliar areas.
- Security/customs time: include immigration and re-screening when you must exit and re-enter the secure area. If you expect long lines at a particular time of day, model that here.
- Buffer: add time for restroom/food, slower boarding at large gates, traveling with kids, mobility needs, or simply peace of mind. A buffer is also where you can account for “unknown unknowns.”
Worked example (with numbers)
Suppose you arrive at 14:10 and depart at 15:40. Your scheduled layover is L = 90 minutes.
You estimate:
- M (MCT) = 45 minutes
- W (walk/transfer) = 15 minutes
- S (security/customs) = 10 minutes
- B (buffer) = 15 minutes
Required time: T = 45 + 15 + 10 + 15 = 85 minutes.
Since L − T = 90 − 85 = 5 minutes, the connection is sufficient but tight.
In practice, a small delay, a slow deplaning process, or a longer queue could erase that margin.
If you want a more relaxed connection for the same itinerary, the easiest lever is usually the buffer.
For example, increasing the buffer from 15 to 30 minutes raises the required time to 100 minutes, which would make this 90-minute layover look insufficient.
That doesn’t mean the itinerary is impossible; it means it doesn’t meet your preferred comfort level.
Scenario table: how assumptions change the required time
These examples show how the required time T can vary by airport size and international procedures.
Use them as starting points only—your airport and airline rules may require more.
Sample required connection time components (minutes)
| Scenario |
MCT (M) |
Walk/transfer (W) |
Security/customs (S) |
Buffer (B) |
Required time T |
| Domestic, same terminal, small airport |
30 |
5 |
0 |
10 |
45 |
| Domestic, large hub, possible terminal change |
45 |
15 |
10 |
15 |
85 |
| International arrival with immigration/customs |
60 |
20 |
20 |
30 |
130 |
How to interpret the result
The result panel summarizes the required time, your layover length, and an assessment.
Use the assessment as a planning signal rather than a guarantee.
- Comfortable: your layover is well above the required time, leaving room for normal friction.
- Tight: your layover is only slightly above the required time; small disruptions can cause a miss.
- Risk of missing: your layover is below the required time based on your inputs.
If you see “risk of missing,” you can respond in three ways: choose a longer layover, reduce complexity (same terminal, same airline, fewer procedures), or accept the risk.
If you see “sufficient” but the margin is small, consider whether you are connecting to the last flight of the day, whether you have checked bags, and how hard it would be to get rebooked.
Introduction: Common edge cases and planning details
Real itineraries have quirks. The calculator handles overnight connections by treating a negative time difference as “next day,” but there are other practical issues worth considering.
The notes below are not required for the math, but they help you choose inputs that reflect reality.
1) Overnight layovers and date changes
If you land late and depart after midnight, your layover is still positive even though the clock time is smaller.
Example: arrive 23:50 and depart 00:40. The layover is 50 minutes.
This planner accounts for that by adding 24 hours when the departure time is earlier than the arrival time.
If your itinerary spans multiple days (for example, an overnight hotel), this simple time-only model is not intended to represent that.
2) Boarding cutoffs vs. departure time
Many airlines close boarding 10–20 minutes before departure, and some international flights close even earlier.
If you want the planner to reflect that, you can incorporate it by increasing your MCT or buffer.
For instance, if boarding closes 15 minutes before departure, adding 15 minutes to your buffer is a straightforward way to model that policy.
3) Terminal changes, trains, and “hidden” transfer time
A terminal change is rarely just walking. It can include waiting for a train, riding it, walking again, and re-orienting yourself.
If you know you must change terminals, consider using a higher walking/transfer time even if the map distance looks short.
Also remember that arriving at a remote stand (bus gate) can add minutes before you even reach the terminal.
4) International connections and immigration steps
International arrivals can require immigration, customs, and sometimes baggage collection and re-check.
If you must collect bags, your “security/customs” time should include the baggage wait and the re-check process.
If you are transiting within a region with simplified procedures, your security/customs time may be lower—but confirm with airport guidance.
5) Traveling with special needs or a group
If you are traveling with children, elderly relatives, or anyone needing assistance, the buffer is the safest place to reflect that.
Even when the airport is efficient, moving a group through escalators, restrooms, and crowded corridors takes longer.
A larger buffer can turn a stressful sprint into a manageable walk.
Assumptions and limitations
This connection time planner is an informational tool. It helps you structure your thinking, but it cannot guarantee you will make (or miss) a flight.
Keep these limitations in mind when you use the result:
- Scheduled times only: delays, gate changes, and irregular operations are not predicted.
- User-provided estimates: walking and queue times vary widely by time of day, staffing, and airport layout.
- Policy differences: some airports/airlines enforce longer minimums than you expect, and boarding may close earlier than departure.
- Not a guarantee: a “sufficient” result does not guarantee success; an “insufficient” result does not mean success is impossible.
When the stakes are high (last flight of the day, international onward travel, cruises, weddings, or important meetings), choose a longer layover.
When you can tolerate a miss (frequent flights, flexible tickets, easy rebooking), you may accept a tighter connection.
Quick planning checklist (optional, but useful)
After you run the calculator once, use this checklist to decide whether you should adjust inputs or choose a different itinerary.
These items are intentionally practical: they reflect the common reasons people miss connections even when the schedule looks reasonable.
- Is your arrival often delayed? If a route is frequently late, consider adding that typical delay into your buffer (or choose a longer layover).
- Do you need to change terminals? If yes, increase walking/transfer time to include trains, shuttles, and navigation time.
- Do you have checked bags on an international arrival? If you must collect and re-check bags, add time to security/customs.
- Is this the last flight of the day? If missing the connection would force an overnight stay, use a larger buffer.
- Are you traveling with a group or special needs? Increase buffer to reflect slower movement and extra stops.
- Do you need time to eat or use the restroom? Add it to buffer; don’t assume you can do it “on the way” during a tight connection.
- Are you unfamiliar with the airport? Add a small buffer for wayfinding, especially in large hubs.
If your result is borderline, run two more scenarios: a “best case” (lower security time, smaller buffer) and a “worst case” (higher security time, larger buffer).
If the itinerary only works in the best case, it is likely to feel stressful.
