Minimum Connection Time, Explained

Minimum connection time, usually shortened to MCT, is the shortest gap between two flights at the same airport that an airline or airport will sell as a legal connection. It is set by the airport authority and the airlines operating there, filed into the reservation systems that book tickets, and enforced automatically: if your itinerary's gap is shorter than the filed MCT, most booking systems will not let you book it as a single connecting itinerary at all. What MCT does not tell you is whether that gap is actually comfortable for you on the day, and that gap between "legal" and "comfortable" is where most missed connections and needless airport sprints actually happen.

This guide walks through what sets the number, why it changes by airport and by the kind of connection you are making, and what a traveller should do with that information beyond trusting the booking engine.

What the filed number is actually measuring

An MCT is an operational estimate, built by the airport and the airlines serving it, of the fastest a typical passenger can realistically move from one aircraft to the next at that specific airport: off one aircraft, through any transfer security or immigration step required, across to the next gate, and onto the second aircraft before its doors close. It is not a guess pulled from a general rule of thumb. Airports measure their own transfer distances, their own security and immigration throughput, and their own gate layout, and file a number (or several numbers, split by connection type) into the databases that global distribution systems use to build connecting itineraries. That is why the same two airlines connecting at two different airports can carry two different minimum times: the number describes the airport's own transfer geometry and process, not a fixed industry constant.

Because the number is filed by the airport and airline rather than mandated by a single global regulator, it is also revised. A terminal expansion, a new transfer corridor, or a change in how immigration handles transit passengers can move an airport's own MCT up or down, and the booking systems update accordingly. The number you see quoted in an older forum thread or blog post can be stale for exactly this reason.

Domestic, international, and why the split changes everything

The single biggest driver of how long your connection needs to be is not the airport, it is the kind of connection. A domestic-to-domestic connection, where neither leg crosses a border, usually needs the least time: there is no immigration step, and depending on the airport, checked baggage may already be through-checked to your final destination.

A domestic-to-international or international-to-domestic connection adds an immigration or customs step for at least one leg, and that step is rarely instant, particularly at busier hub airports during peak arrival banks. An international-to-international connection can sometimes stay inside a transit area without a fresh immigration check, which is why some hub airports post their fastest MCT for exactly that combination, and their slowest for the leg that requires stepping through a border control point.

The practical takeaway: never assume the MCT that applied to your last trip through an airport applies to this one, if the type of connection is different. A traveller who habitually flies domestic-to-domestic through a hub and then books one domestic-to-international leg for a trip abroad is comparing two different filed numbers without realising it.

Where the actual number comes from, and why this guide will not quote one

Every airport's minimum connection times, split by connection type and sometimes by terminal, are published in the databases global distribution systems use to build tickets (the IATA minimum connecting times reference is the industry-standard source travel agents and booking engines draw from). In India, the Directorate General of Civil Aviation is the regulator for civil aviation safety and operations, and it issues the Civil Aviation Requirements that govern how Indian carriers and airports run more broadly, though the specific per-airport MCT figure itself, like elsewhere, is filed by the airport and its airlines rather than fixed by regulation. Individual airports and airlines also publish their own transfer guidance for passengers connecting through their hub.

This guide deliberately does not quote a specific number of minutes for any named airport or carrier. MCT figures are filed per airport and per connection type, they are revised without much public notice, and repeating a number here without a verified, dated source for that exact airport and connection type would be more likely to mislead a traveller than help one. If you need the number that applies to your specific itinerary, the authoritative source is the connection time your airline or travel agent's booking system actually enforced when you booked it, or the airport's own current transfer-time guidance, not a general blog post.

Why "legal" and "comfortable" are two different questions

A connection that clears the filed MCT is, by definition, bookable. It is not, by the same definition, comfortable. The filed number is built around a typical passenger moving at a typical pace under typical conditions, and typical is doing a lot of work in that sentence. It generally does not build in slack for your inbound flight landing late, for your gate being at the far end of a terminal from your connecting gate, for a security recheck queue that happens to be long that hour, or for checked baggage that needs to be manually transferred rather than through-checked. Any one of those, on a connection booked at exactly the filed minimum, can turn a legal itinerary into a missed one.

The buffer a traveller should actually want is the filed MCT plus a personal margin for the parts of the journey the filed number does not model: how punctual your specific inbound flight has been running lately, how far apart the two gates are likely to be, and whether either leg involves an immigration or customs step you have not done at that airport before. None of that margin is written into any database. It is the traveller's own judgment, applied on top of a number the system will happily sell you at its bare legal floor.

What a route or airport page can and cannot tell you

An airport page can describe the airport itself: its terminals, its general layout, and what kind of connections it handles. What it will not do, and what no flight-tracking page can honestly promise, is calculate a personalised risk score for your specific connection on your specific day. Whether your inbound flight is running on time, and how much runway that leaves you before your connecting gate closes, is the actual question a tight connection raises, and it is a live, day-of question rather than a static airport fact.

That is exactly the kind of gap between a static schedule and a live situation that a flight tracker is meant to sit in. Our Delhi airport page and Mumbai airport page describe each hub's own layout and connection patterns; a route through a hub like Singapore's is a useful example of an airport built around fast international-to-international transfers specifically because of how much of its traffic is exactly that kind of connection.

How TrackMyWings helps

TrackMyWings™ is a flight-tracking platform in development. A private beta shipped on 2026-08-24, Android only, on the Play internal testing track, with no fixed public launch date yet. The purpose the product is being built toward is the day-of question a filed MCT cannot answer: how much of your connection buffer your specific inbound flight has already used up. Trip management and gate-and-status alerts are planned features for launch, still ahead of us and written here in future tense only: the intent is that a traveller booked on a tight connection will be able to watch the inbound leg the same way they would watch their own boarding gate, rather than finding out the connection is in trouble only after they land.

Common questions

Is minimum connection time the same thing as the airline's official layover minimum?

They are closely related but not identical in every case. The MCT filed into booking systems is what determines whether an itinerary can be sold as a single connection at all. An airline can, and sometimes does, apply its own additional buffer on top of the filed MCT for connections it controls end to end, particularly for its own codeshare or interline partners, so the number an airline's booking flow actually offers you can be equal to or slightly longer than the bare filed MCT.

Why did my connection get booked with less time than I expected?

If the gap between your two flights is at or above the filed MCT for that specific connection type at that airport, the booking system will treat it as valid, even if it feels tight to you personally. The system is checking against the legal floor, not against your comfort level, your bag situation, or how far apart your two gates happen to be that day.

Does a short minimum connection time mean the airport is small or the process is rushed?

Not necessarily. A short MCT usually means the airport has invested in fast transfer infrastructure for that specific connection type, close gate proximity, streamlined security for transiting passengers, or a transit area that avoids a fresh immigration check. A long MCT more often reflects an unavoidable process step, such as full immigration and customs clearance, than a poorly run airport.

Sources

• IATA, Minimum Connecting Times reference (industry-standard source for filed MCT values used by global distribution systems to build connecting itineraries): https://www.iata.org/en/publications/store/minimum-connecting-times/ (captured 2026-09-23).
• Directorate General of Civil Aviation, Government of India (India's civil aviation safety regulator, which issues the Civil Aviation Requirements governing Indian carrier and airport operations): https://www.dgca.gov.in/digigov-portal/ (captured 2026-09-23).