Airline Schedule Padding: Why On-Time Stats Mislead
Learn how airline schedule padding changes A14 results, why D0 measures a different event, and what transport event-contract traders should check.
Last updated
The schedule is part of the measurement
An airline timetable looks like a neutral reference: the flight leaves at one published time and arrives at another. But those two times are the benchmark that punctuality is measured against. Change the benchmark and the same operation can give a different on-time result.
The time from scheduled gate departure to scheduled gate arrival is the scheduled block time. It includes the expected taxi-out and taxi-in time as well as the time in the air. Airlines need some margin because those parts vary from day to day. When the published block time is deliberately set above the typical operating time to absorb routine disruption, that margin is called schedule padding.
Padding doesn’t make a flight faster or remove operational risk. It changes how much delay can build up before the published arrival threshold is crossed. So a flight can leave late, make up time while taxiing or in the air, and still reach the destination gate before the arrival cutoff.
EUROCONTROL describes a growing pattern: more flights depart late but still arrive on time, because carriers build buffers into their schedules. The agency also notes that too much buffer can lower aircraft utilisation and cause capacity imbalances when flights arrive earlier than planned.
For traders, this means on-time performance doesn’t purely measure how fast or well an airline operates. It measures performance against a schedule the carrier wrote itself.
A14 and D0 answer different questions
Two punctuality labels are easy to mix up:
| Metric | Test | What it measures |
|---|---|---|
| A14 | Actual gate arrival is no more than 14 minutes after scheduled gate arrival | Arrival performance within the standard 15-minute reporting window |
| D0 | Actual gate departure is at or before scheduled gate departure | Exact departure punctuality with no positive grace period |
The U.S. Bureau of Transportation Statistics states that arrival performance is based on arrival at the gate and departure performance on departure from the gate. Under the BTS convention, a flight is on time when it operates less than 15 minutes later than the scheduled time shown in the carrier’s reservation system. In the data, a 14-minute arrival delay is on time and a 15-minute one is delayed.
D0 asks a stricter question at the origin: did the aircraft leave the gate by the scheduled minute? The IATA Airline Cost Management Group instructions define D0 as “On-Time Departure” and report D15 as a separate measure. A flight that departs one minute late fails D0 even if it later passes A14. So the BTS departure convention of less than 15 minutes late isn’t D0. The two metrics look at different events, at different points in the journey, with different tolerances.
Take a scheduled 10:00 departure and 12:00 arrival:
- The aircraft leaves the gate at 10:08 and arrives at 12:09. It fails D0 but passes A14.
- It leaves at 10:00 and arrives at 12:16. It passes D0 but fails A14.
- It leaves at 10:12 and arrives at 11:58. It fails D0 and passes A14, arriving early against the published schedule.
These examples are arithmetic, not forecasts. They show why you can’t use an arrival statistic in place of a departure statistic in a threshold-based market.
How schedule padding changes the apparent signal
Say two flights on the same route usually need about the same block-to-block time. One schedule allows two hours and the other allows two hours and fifteen minutes. If both get the same taxi and airborne conditions, the second has fifteen more minutes before its published arrival threshold is tested.
That extra margin can improve reported A14 without any matching improvement in the operation itself. It can also widen the gap between departure and arrival punctuality. EUROCONTROL’s Performance Review Report 2024 explicitly links the widening gap between those metrics to airlines adding time buffers to support on-time arrivals and schedule reliability.
A14 is still a valid measure. It measures how well a flight keeps to its published arrival schedule, and that schedule may include padding. This matters when you compare:
- the same route across different carriers;
- one carrier’s seasonal schedules;
- morning flights with later rotations;
- airport pairs with very different taxi-time distributions;
- historical performance after a timetable change.
Raw on-time percentages are still useful context. The mistake is to treat them as if the schedule had no effect. For the wider statistical picture, see Gaduin’s airline on-time performance rankings. This article covers how to read the benchmark behind those figures and doesn’t repeat the carrier table.
Read the timetable before reading the percentage
Better analysis starts with the individual flight and works outward. These steps keep the schedule definition in view.
1. Identify the event timestamp
Check whether the contract is resolved on gate departure, takeoff, landing or gate arrival. BTS arrival and departure data use gate events. Data based on runway times would answer a different question.
2. Confirm the threshold and boundary
There’s no universal rule for “on time”. A14 and D0 have different boundaries, and an event contract may use yet another. Check whether the threshold is inclusive or exclusive and how minutes are rounded. On a GADUIN flight market, for example, Delayed means more than 15 minutes after the scheduled arrival, so an arrival exactly 15 minutes late counts as on time.
3. Calculate scheduled block time
For each flight, subtract scheduled departure from scheduled arrival, adjusting for time zones and overnight flights. Then compare that figure with the same route, direction, season and aircraft pattern where the data allow.
4. Separate schedule changes from operating changes
An A14 improvement after scheduled block time went up is a different signal from an improvement on an unchanged timetable. Look at both:
- schedule variance: how the published block time changed;
- operating variance: how actual block time and its distribution changed.
5. Examine the distribution, not only the average
Threshold outcomes depend on the flights near the cutoff. An average can hide a cluster of flights with 14–16 minutes of arrival delay. For an A14 position, that cluster may matter more than many very early or very late flights.
6. Control for route and time-of-day effects
Taxi congestion, airport capacity, weather patterns, curfews and knock-on delay can differ by direction and departure wave. If you pool flights that aren’t alike, padding can look more or less effective than it really is for the flight you’re looking at.
Where padding matters for transport event contracts
In a threshold event contract, a small move around the cutoff can change how the market settles. Schedule padding matters most when the threshold is based on the scheduled arrival and the estimated arrival is close to it.
For an A14-style contract:
- Read the contract terms and the official record it settles on.
- Note the scheduled gate-arrival time that record uses.
- Work out the exact point where a flight becomes delayed.
- Compare the current estimated gate arrival with that point. Flight status shows the latest reported times.
- Check again when the schedule, the operating status or the official time changes.
A padded schedule can give a late departure more room to still produce an On time arrival. It doesn’t remove the risk of severe weather, airport constraints, technical problems, a late inbound aircraft or cancellation. And don’t count padding twice, once in the published arrival time and again as extra recovery time you assume the flight will make up.
D0-style contracts need a different approach. The arrival buffer barely affects whether the aircraft left the origin gate by the scheduled minute. Turnaround progress, inbound aircraft timing, gate readiness, boarding, crew availability and local restrictions matter more for that.
Gaduin is a transport event-contract exchange with outcomes such as On time, Delayed and Cancelled. Markets settle automatically from the official record named in the market’s rules, with settlement and balances in USDT. The outcome label doesn’t tell you everything. Traders and institutional hedgers should check each market’s stated timestamp, threshold, data and settlement conditions before taking a position. This material is general information and is not financial advice.
A better punctuality checklist for traders
Before you use airline on-time statistics to form a view on a market, ask:
- Is the metric A14, D0 or another definition?
- Does it use gate times, runway times or another operational event?
- Which scheduled time does settlement use?
- Has scheduled block time changed for this route or season?
- Is the comparison specific to the route, direction and time of day?
- How many flights land close to the contract threshold?
- Are cancellations and diversions counted separately from delays?
- Could a late inbound aircraft cause knock-on delay?
- Am I counting schedule buffer as if it were extra recovery time?
Treat the timetable as an input that the airline chose. A14 tells you whether the aircraft reached the gate within an arrival window. D0 tells you whether it left the gate by the scheduled minute. Schedule padding can change the first result a lot and leave the second untouched, so keep them separate when you read a threshold market.
Sources
- Bureau of Transportation Statistics: Airline On-Time Performance and Causes of Flight Delays
- Bureau of Transportation Statistics: Airline Service Quality Performance 234
- Bureau of Transportation Statistics: Technical Directive No. 40 — On-Time Performance Reporting for 2026
- IATA Airline Cost Management Group: FY2021 Instructions Manual
- EUROCONTROL Aviation Trends: Airlines’ Schedules — A Balancing Act
- EUROCONTROL Performance Review Report 2024
- EUROCONTROL Think Paper: Arriving on Time — The Passenger Priority
Checking a flight?
Look up flight status by flight number. The methodology explains scheduled, estimated and actual times.
Related markets
- Flight delay markets
Live prices on whether each flight arrives on time. Settles on the official arrival record.
- Open markets
Everything you can trade right now.