Use It or Lose It: The 80/20 Airport Slot Rule, Explained
The 80/20 slot rule: fly a slot series 80% of the time or lose it. Where it applies, what COVID changed, ghost flights, and where the rule stands now.
We wrote earlier about what an airport slot is and how it shapes the schedule. This is the data companion: the 2026 numbers on how much of the world’s flying now happens under coordination, and why the schedule you publish and the slots you hold have to tell the same story.
The scale of coordination in 2026
Slot coordination is often treated as a handful of famous chokepoints — Heathrow, JFK, Haneda. The global figures say otherwise. Per IATA, 395 airports are subject to some level of coordination in 2026, and of those, 216 are fully slot-coordinated — the highest category, where every movement needs an allocated slot.
The passenger share is the number that reframes it: roughly 43% of passengers globally depart from a slot-coordinated airport. Nearly half of the world’s departures leave a field where the schedule is not simply “what the airline wants to fly” but “what the airline has been cleared to fly.”
| 2026 slot landscape | Figure |
|---|---|
| Airports subject to coordination | 395 |
| Of which fully slot-coordinated | 216 |
| Passengers departing a coordinated airport | ~43% |
| Coordinated airports in Europe | 104 |
Europe is the densest region for coordination — 104 coordinated airports — a consequence of dense airspace, environmental caps, and long-standing demand-above-capacity at the major hubs. But the picture is genuinely global, and it is growing rather than shrinking.
The rulebook: WASG
The framework underneath all of this is the Worldwide Airport Slot Guidelines (WASG) — jointly stewarded by IATA, ACI, and the Worldwide Airport Coordinators Group. WASG defines the airport categories (from Level 1, schedules-facilitated, up to Level 3, fully coordinated), the historic-precedence “grandfather” rules, the use-it-or-lose-it thresholds, and the twice-yearly slot conferences where seasons are built.
The detail matters less here than the consequence: at a Level 3 airport, an airline’s right to operate a flight is a discrete, allocated thing. The schedule has to be built around those allocations, not the other way round.
At a fully coordinated airport, a flight isn’t valid because it’s in your schedule. It’s valid because you hold the slot that lets it operate.
Why the schedule and the slots must agree
This is where slot coordination becomes a data-integrity problem. An airline holds a set of slots — specific movements at specific times at specific airports. It also publishes a schedule, as an SSIM file, describing what it intends to fly. Those two artefacts are produced by different processes, and they can drift apart.
The failure modes are ordinary and expensive:
- A flight in the schedule with no matching slot at a coordinated airport — a movement that can’t legally operate as timed.
- A slot held but not scheduled — capacity paid for and risked against use-it-or-lose-it thresholds, sitting idle.
- A timing mismatch — the schedule says 0710, the slot is 0725, and at a Level 3 field that fifteen minutes is the difference between operating and not.
- An overlap — two flights timed onto capacity that only supports one, the kind of conflict deconfliction exists to catch.
None of these are visible if you read the schedule alone or the slot list alone. They live in the reconciliation between them — and reconciliation gets harder every time the schedule is rebuilt, which in 2026 is often.
The capacity picture keeps tightening
Coordination doesn’t stand still, and 2026 has a vivid example. The FAA proposed a Summer 2026 daily cap of 2,708 operations at Chicago O’Hare — an explicit administrative limit on how many movements the airport will schedule, imposed to keep published demand within what the field and its airspace can actually handle.
A cap like that is the slot system doing its job in public. It also means every carrier at O’Hare has to fit its schedule inside a hard number, which forces exactly the kind of frequency and timing decisions that produce a new schedule file to check. When the ceiling moves, the schedule underneath it has to move too — and it has to still add up.
Reading the file-half correctly
A slot list lives in the coordination systems; that’s not where SSIM Toolkit operates. What the Toolkit does is get the schedule side of the reconciliation right, locally and deterministically, so you’re arguing from clean data.
Open a schedule and you can explore it flight by flight, station by station — see exactly which movements you’ve published at a coordinated airport and when. Validate it against the SSIM standard so encoding errors don’t masquerade as slot problems. Analyse frequency and capacity per market and the departure and arrival banks at each hub, and run deconfliction to surface overlapping or duplicated movements before they reach operations. The record inspector lets you read a single leg down to the byte when a timing looks off, and you can export any view to CSV, JSON, or Parquet to line it up against your slot holdings in whatever system owns them.
Because SSIM carries no distances and times are local with a UTC-variation field, even lining a schedule up against a slot list in a common frame is a computation — one the Toolkit does the same way every time.
And it runs on your machine. Your schedule data never leaves it; the app does its data work locally and only touches the network for things like licensing and updates. Slot holdings and unpublished schedules are commercially sensitive — keeping the analysis local is the point.
The takeaway
The 2026 slot picture is one of steady, global tightening: 395 coordinated airports, 216 of them fully coordinated, and roughly 43% of passengers departing under coordination. In that environment, the schedule and the slot list are two descriptions of the same operation, and they have to agree. Getting the schedule side exactly right — validated, analysed, and reconcilable — is the half SSIM Toolkit is built to own.
Coordination counts and passenger-share figures are IATA’s 2026 slot data; the O’Hare cap is an FAA proposal cited below. Industry aggregates are revised periodically.
Sources
