Airport slots: reconcile allocated, scheduled and used capacity
Allocated airport slots, scheduled flights and actual operations are different quantities. A qualifying waiver can protect the historical usage treatment of specified returned slots without producing an actual flight or a seat. Research needs a slot-and-period ledger before turning an airline’s headline utilisation into a claim about capacity or retention.
This guide uses a historical US FAA waiver and fictional arithmetic. The cited seasonal window ended on October 24, 2026. At this article’s October 26 publication, that document is evidence for its stated past window, not proof that equivalent prospective relief remains available. A later season requires its own applicable evidence.
Locate the general rule and the dated exception
The FAA Compliance and Oversight page, last updated February 1, 2021, describes an eighty-percent use requirement and distinguishes the DCA rule from JFK and LGA orders. Its general description does not by itself identify the current version of every airport’s operative order.
The July 23, 2025 staffing-related waiver document, printed pages 9–10, states its airports, seasonal dates, timely-return conditions and treatment of eligible returns as used. Read the actual coverage before applying any relief; the title’s reference to 2026 does not mean every date in that calendar year is covered.
Build the slot-and-event record
For a real case, obtain allocation reference, airport, operating date, local time, holder, relevant evaluation unit and applicable usage rule. Link the corresponding scheduled operation, actual operation, cancellation and any return or relief documentation. A flight number alone can change or recur, so it is not a sufficient slot identifier.
Maintain separate raw-event and classification columns. A cancelled flight remains physically unoperated even if a rule supplies favourable usage treatment. A return submitted but not shown to qualify remains pending in the research register. Neither an airline’s intention to return nor a generic staffing explanation establishes that the specific record met the notice’s conditions.
Rebuild a complete fictional usage ledger
Assume one hundred comparable allocated opportunities within an explicitly defined teaching evaluation record in the historical covered period. Ninety had corresponding scheduled operations and seventy-five actually operated. Of the fifteen scheduled cancellations, ten are expressly assumed to be documented qualifying returns, while five have no relief. Another ten allocated opportunities were not scheduled and have no qualifying relief in the supplied case.
The ledger closes as seventy-five actual operations plus ten qualifying returns plus fifteen other non-operations equals one hundred. Under the notice’s stated treatment of the qualifying returns as used, the illustrative usage numerator is 75 + 10 = eighty-five. Against the assumed hundred-opportunity base, the ratio is 85%; actual operation remains 75%.
| Category | Opportunities | Actual operations | Illustrative usage credit |
|---|---|---|---|
| Operated | 75 | 75 | 75 |
| Qualifying returned | 10 | 0 | 10 |
| Other scheduled cancellations | 5 | 0 | 0 |
| Unscheduled without relief | 10 | 0 | 0 |
| Total | 100 | 75 | 85 |
This is a fully assumed arithmetic model, not a determination for a real carrier. The actual evaluation unit, period and slot-level rules must be established from the applicable instruments. In particular, it does not grant ten credits merely because ten percent of an aggregate airline schedule was cancelled.
Use the treatment the instrument actually specifies
Removing ten from the denominator would instead produce 75 ÷ 90 = 83.33%. That differs from 85%; the two methods are not interchangeable. The cited historical notice says qualifying specified returns are treated as used, so its stated treatment should not silently be replaced by a preferred denominator convention.
For a sensitivity boundary, suppose eight of the ten proposed returns are later found unqualified, leaving only two documented credits. The illustrative numerator becomes seventy-seven and the ratio 77%, rather than 85%. The change comes from eligibility evidence, not from a different physical flight count. While all ten are merely pending, the worksheet should not present them as confirmed credits.
An aggregate airline percentage can also conceal the underlying unit. If two separate evaluation records each contain one hundred opportunities and actual usage of sixty-five and ninety-five, their combined ratio is 80%. That arithmetic does not cure a lower-performing individual record where the operative rule tests slots separately. Obtain the correct unit instead of substituting a portfolio average.
Check airport, season and return scope
The historical decision permits limited returns at JFK and LGA and certain impacted DCA operations involving those airports. It is not general relief for every DCA operation. Its first page also excludes the specified Section 505 slots. Keep these coverage limitations in the relationship table rather than attach one waiver flag to the entire airline.
The document’s return deadlines differ by season, with August 15, 2025 for Winter 2025/2026 and January 15, 2026 for Summer 2026. The relevant specific slots and corresponding scheduled operations must be identified. A timely email about broad schedule reductions does not alone prove that every cancelled operation received the specified treatment.
For the article’s historical summer example, match March 29 through October 24, 2026. An otherwise similar October 25 cancellation falls outside that cited window. Do not extend the end date because the airline continues to experience staffing problems; later relief, if any, needs a separate instrument or case-specific determination.
Keep retained usage and passenger capacity distinct
Suppose the seventy-five actual flights in the main case each carry an assumed 120 seats. Scheduled physical seat capacity actually operated is nine thousand. The ten credited returns contribute no operated seats. Treating eighty-five credited usage opportunities as flights would invent 1,200 seats under those assumptions.
For another aircraft-size boundary, compare one hundred flights with one hundred seats each, ten thousand seats, with seventy-five flights carrying 140 seats each, 10,500 seats. Fewer operations can accompany greater seat capacity. Slot count therefore cannot alone establish passenger throughput, load factor, revenue or profitability.
Actual passengers need occupancy records, and commercial results need matching fare and cost evidence. A historical usage treatment concerns a regulatory allocation question. It does not convert unused flights into transport delivered or establish a product’s economic value merely because an airline retains access to a constrained airport.
Use the slot verification sheet
| Field | Obtain | Check |
|---|---|---|
| Allocation | Airport, holder, reference and date/time | Correct slot and evaluation unit |
| Rule | Applicable order or regulation version | Period and usage test established |
| Schedule | Corresponding scheduled operation | Planned distinct from operated |
| Actual | Operation or cancellation record | Physical event preserved |
| Relief | Specific return and qualification evidence | Airport, window and deadline match |
| Calculation | Actual and deemed-used components | No arbitrary denominator substitution |
Begin with a dated allocation population, then join schedules and actual operations before adding relief classifications. Investigate unjoined records. A slot returned temporarily and an airport permanently relinquished allocation are different events; preserve the stated duration and later disposition rather than label every return a permanent loss of capacity.
When airline, schedule and FAA evidence differ, compare local dates, time changes, allocation identifiers and the exact status being reported. Schedule cancellation is not the same as a filed return, and a filed return is not necessarily a qualifying one. Keep the unknown category until the supporting record is obtained.
New operative orders, specific determinations, allocation amendments or corrected operation records trigger updates. Preserve the historical calculation under its original instrument. For a future season, rebuild the evidence scope before recomputing; a past waiver’s existence does not supply future eligibility or a guarantee of retained slots.
Preserve the document hierarchy in the review packet
The FAA-hosted waiver PDF carries a header about possible publication formatting and editorial changes. Save that supplied document and its identity, and verify the operative published version when resolving an actual legal or administrative case. Hosting on an official site establishes provenance but does not make every general webpage the complete instrument for every evaluation period.
Attach each usage classification to the specific provision and record supporting it. If a later order changes the next season’s treatment, create a new rule relationship rather than overwrite the historical summer calculation. This keeps an October 2026 reader from confusing evidence about a completed window with a currently available cancellation entitlement.
FAQ
Does a qualifying returned slot represent a flight actually operated?
No. Usage treatment and physical operations are separate columns.
Can the cited waiver support relief after October 24, 2026?
Not by its own stated window. A later period requires separate applicable evidence.