FlyerIntel Research

Making Up Time in the Air

Every American airline schedule contains minutes that are not flying. The flight that needs them most is the one that gets fewest of them back.

Published September 1, 2026 · Source period July 2023 – August 2026

Summary

Across 18,056,969 completed departures from the 64 airports FlyerIntel covers, departures-weighted throughout, the average flight finished 5.71 min inside its own schedule, and 73.3% of flights beat their block time. Subtract a flight's departure delay from its arrival delay and the schedule falls out of the arithmetic exactly: what is left is the time the aircraft actually took from gate to gate, measured against the time its schedule allowed. That spare time is the reason a departure delay usually shrinks by the time you land. It is not a response to being late. Comparing flights on the same route flown by the same airline, one that pushed back an hour or more late handed back 3.87 min against 6.10 min for the same route leaving on time, 2.23 min less, not more. Effectively none of that difference is in the air: airborne time between the two groups is 1 second apart, in the direction of the late flight being airborne shorter. The pooled figure is itself two small opposite effects cancelling (short sectors airborne slightly longer when late, long ones slightly less), and the larger of them is 2.10 min on a sector where the aircraft is airborne about 290 min. The minutes the late flight loses are spent taxiing, at both ends.

Key findings

  • The average completed departure from a covered airport arrived 5.71 min inside its scheduled gate-to-gate time, departures-weighted; the median beat its schedule by 7 min and 73.3% of flights beat it at all. A mean departure delay of 13.5 min becomes a mean arrival delay of 7.8 min for that reason alone.
  • The spare minutes are not deployed when they are needed. Standardized across 2,272 route-and-carrier pairings, a flight that pushed back an hour or more late gave back 3.87 min against 6.10 min for the same route and carrier leaving on time, and 5.00 min for one leaving 15 to 59 minutes late.
  • Almost none of the difference is in the air. Of the 2.23 min the late flight fails to recover, 2.21 min is extra taxi-out at the origin and 0.36 min is extra taxi-in at the destination; a 0.33 min difference in the scheduled block times themselves pulls the other way, and airborne time accounts for -0.01 min (1 second).
  • Airborne recovery is real only on long sectors, and it is small: between an on-time and an hour-late departure airborne time changes by +0.35 min on flights under 750 miles, +0.02 min on flights of 750–1,499 miles, -1.27 min on flights of 1,500–1,999 miles, -2.10 min on flights of 2,000 miles and over. Even on flights of 2,000 miles and over, where the late aircraft genuinely is airborne 2.10 min less, the 2.59 min it loses taxiing more than cancels it and it still finishes 0.31 min worse against its schedule.
  • The pattern is not an average of opposite behaviors. Every one of the 12 carriers with a comparable set of routes recovers less when it leaves late, and 12 of 12 taxi out longer. The airborne column has no direction at all: 6 carriers are airborne less when late and 6 are airborne more, and the largest movement in either direction is 1.83 min.
  • Practically: 22 minutes is the last whole minute of departure delay at which an on-time arrival is still better than even money, at 50.10%. Route length moves that line by only 4 minutes, from 21 on flights under 750 miles to 25 on flights of 2,000 miles and over, but it matters far more once a flight is properly late: 45 minutes down, 0.59% against 11.51%.

The announcement

There is a sentence every frequent flyer has heard from the flight deck after a long wait at the gate: "We have got a good tailwind today and we will try to make up some of the time in the air." It is reassuring, it is plausible, and it is one of the very few claims an airline makes about its own operation that can be checked exactly, for free, against a public record. The US Department of Transportation publishes, for every flight, the delay at pushback and the delay at the gate on arrival, and separately the minutes spent taxiing at each end. That is enough to say precisely how long the airplane spent in the air, how long its schedule expected it to, and whether the two differ when the flight is running late. This report does that for every flight in the database.

An identity, not an estimate

Departure delay is the actual gate departure minus the scheduled one. Arrival delay is the actual gate arrival minus the scheduled one. Subtract the first from the second and the two scheduled times collapse into the scheduled block time, the two actual times into the actual block time, and what is left is the difference between them. No timezone enters it, because both delays are differences taken at a single airport. A flight with an arrival delay smaller than its departure delay took less time gate-to-gate than its schedule allowed; the number of minutes is exact and needs no assumption at all. Everything in this report is measured on one basis and one population: one record is one completed flight that departed one of the 64 airports FlyerIntel covers, and every network figure is departures-weighted from summed counts rather than averaged across airport averages. Cancelled flights never left and diverted flights did not arrive where they were scheduled, so neither has a block time and neither is counted. Nothing here is an arrivals measure and no figure mixes the two.

How much of its own schedule a flight gives back

How much of its own schedule a flight gives back
MeasureMinutes against the scheduled block time
Average-5.71
10th percentile (the flights that gained most)-20
25th percentile-14
Median-7
75th percentile0
90th percentile (the flights that lost most)+10
Share finishing inside the scheduled block73.3%
Share finishing 15 or more minutes inside it23.1%
Share finishing over the scheduled block24.2%

Over 18,056,969 completed departures from covered airports. A negative number means the flight took less time gate-to-gate than its schedule allowed. This is not an accusation of padding: a schedule has to cover a bad day as well as a good one, and a block time set at the average would make half of all flights late by construction.

Why a departure delay usually shrinks

The distribution above is the reason a late pushback is not a sentence. Departures-weighted across covered airports, the mean departure delay is 13.47 min and the mean arrival delay 7.76 min: the system gives back 5.71 min of every flight, on average, between the two gates. 73.3% of flights finish inside their scheduled block and 23.1% finish a quarter of an hour or more inside it. So far this is the folklore confirmed, and it is worth saying clearly before the rest of this report complicates it: schedules do contain slack, the slack is large, and it does absorb delay. The question this report exists to answer is a different one: whether the slack is spent because the flight is late.

The raw comparison, before anything is held constant

The raw comparison, before anything is held constant
How the flight pushed backFlightsMean departure delayMean arrival delayMinutes against scheduleMedianTaxi-outTaxi-inArrived on time
Pushed back on time or early14,062,518-2.6 min-8.6 min-5.97-718.4 min8.2 min94.35%
Pushed back 15–59 minutes late2,587,83831.1 min25.8 min-5.28-819.3 min7.8 min31.15%
Pushed back an hour or more late1,406,613141.5 min137.6 min-3.90-720.9 min8.7 min0.03%

All nine columns are departures measures over one population. The taxi-in column is an attribute of these same flights at the far end, not an arrivals average for any airport.

The flight that needs the minutes gets fewer of them

Read the fifth column of that table downwards. A flight that pushed back on time or early finished 5.97 min inside its schedule. One that pushed back between 15 and 59 minutes late finished 5.28 min inside it. One that pushed back an hour or more late finished 3.90 min inside it. The direction is the opposite of the announcement: the later the flight left, the less of its schedule it managed to give back. That raw comparison is not yet worth much, because the three groups are not the same flights. Late departures are concentrated at congested airports, in bad weather, at the worst hours, and on whatever route mix happens to go wrong most. Route length alone changes how many spare minutes a schedule contains. Everything that follows holds those things constant.

Where the minutes actually go

Where the minutes actually go
How the flight pushed backFlights weightedMinutes against scheduleTaxi-outAirborneTaxi-inScheduled block
Pushed back on time or early937,562-6.1018.82 min116.43 min8.51 min149.86 min
Pushed back 15–59 minutes late937,562-5.0020.42 min116.16 min8.45 min150.03 min
Pushed back an hour or more late937,562-3.8721.03 min116.43 min8.87 min150.20 min

Every row is computed inside the same 2,272 (origin, destination, operating carrier) cells, each with at least 200 flights in every one of the three groups, and reweighted onto one common mix, so the rows describe an identical set of routes and airlines rather than three different ones. The airborne and scheduled block columns carry each route's own constant timezone offset, which is why they are only ever compared down a column within this fixed set of routes and never quoted as absolute flying times. The five columns satisfy an exact identity: minutes against schedule = airborne + taxi-out + taxi-in − scheduled block. The generator refuses to publish this report if they do not reconcile.

Making up time in the air, measured

Holding the route and the operating carrier constant, the effect gets stronger rather than weaker. A flight leaving on time gave back 6.10 min; the same route flown by the same airline leaving an hour or more late gave back 3.87 min. The gap is 2.23 min, and the table above says exactly where every second of it went. Extra taxi-out at the origin: 2.21 min. Extra taxi-in at the destination: 0.36 min. A difference in the scheduled block times themselves, pulling the other way by 0.33 min, because a delayed departure is not drawn evenly from a route's own timetable. And airborne time: -0.01 min, which is 1 second, in the direction of the late flight being airborne shorter. That is the whole of the tailwind. Two further checks say the same thing. Additionally holding the scheduled departure hour constant, so the two groups are drawn from the same slot in the same day, the gap is 0.89 min with airborne time moving -0.45 min; additionally holding the calendar month constant, 2.59 min with airborne time moving 0.50 min.

The same decomposition, by route length

The same decomposition, by route length
Route lengthHow the flight pushed backFlights weightedMinutes against scheduleTaxi-outAirborneTaxi-in
Under 750 milesPushed back on time or early478,202-5.1918.94 min71.62 min8.01 min
Under 750 milesPushed back 15–59 minutes late478,202-3.8120.48 min71.68 min7.92 min
Under 750 milesPushed back an hour or more late478,202-2.6121.05 min71.97 min8.47 min
750–1,499 milesPushed back on time or early346,071-6.6318.20 min137.22 min8.81 min
750–1,499 milesPushed back 15–59 minutes late346,071-5.5619.86 min136.90 min8.79 min
750–1,499 milesPushed back an hour or more late346,071-4.3520.55 min137.24 min9.11 min
1,500–1,999 milesPushed back on time or early64,117-7.7419.43 min205.55 min9.57 min
1,500–1,999 milesPushed back 15–59 minutes late64,117-7.6020.91 min204.31 min9.46 min
1,500–1,999 milesPushed back an hour or more late64,117-6.9621.35 min204.28 min9.68 min
2,000 miles and overPushed back on time or early49,172-9.0521.23 min289.79 min9.94 min
2,000 miles and overPushed back 15–59 minutes late49,172-9.2423.16 min287.80 min9.90 min
2,000 miles and overPushed back an hour or more late49,172-8.7423.77 min287.69 min10.00 min

The same cells as the previous table, split by the length of the route. Airborne minutes carry each route's timezone offset and are comparable only within a band, down the column, never across bands.

The long flight is the exception, and it still does not come out ahead

Pooling the whole country hides two effects that happen to be pointing in opposite directions, and reporting only the pooled figure would be the exact mistake this report is trying to avoid. Split by route length, the airborne column does move, and it moves sensibly: on flights under 750 miles the late aircraft is airborne 0.35 min longer than the on-time one, while on flights of 2,000 miles and over it is airborne 2.10 min shorter. A long sector has enough cruise in it to be flown faster and a short one does not, which is what an operations department would predict. But the size is the point. The largest airborne saving in the table is 2.10 min on flights of 2,000 miles and over, on a sector where the aircraft is airborne roughly 290 min, under one percent of the flight. And it does not survive contact with the ground: on the same band the late flight loses 2.59 min taxiing, so it still finishes 0.31 min worse against its schedule than the on-time flight on the same route. In 2 of the 4 route-length bands the late aircraft is airborne longer, not shorter, and 51.0% of the flights in this comparison are on flights under 750 miles, where there is no recovery to be had at all. This does not show that pilots never make up time. It shows that the amount available to be made up is a rounding error next to the delay it is supposed to fix, and is spent again before the aircraft has left the airfield.

Every carrier with a comparable set of routes

Every carrier with a comparable set of routes
CarrierRoute cellsAgainst schedule, left on timeAgainst schedule, left an hour lateDifferenceAirborne differenceTaxi-out difference
American Airlines445-6.04-3.82+2.22-0.11+1.64
Southwest Airlines477-7.04-4.69+2.35+0.58+1.52
Delta Air Lines366-6.54-4.20+2.34-0.40+2.74
United Airlines295-6.05-4.34+1.72-0.66+3.02
JetBlue134-6.60-4.37+2.23+0.66+2.81
SkyWest Airlines165-4.07-1.98+2.09+0.19+2.10
PSA Airlines85-4.64-2.45+2.19+0.31+0.79
Frontier Airlines84-4.49-4.28+0.21-0.66+1.68
Republic Airways67-6.05+0.33+6.38+1.23+6.12
Spirit Airlines74-6.60-4.96+1.64-0.20+2.32
Alaska Airlines47-4.22-3.56+0.66-1.17+1.81
Envoy Air25-4.75+1.64+6.38+1.83+3.22

The same standardization, split by operating carrier instead of pooled, for carriers with at least 20 qualifying route cells. Read across a row, not down a column: the level of a carrier's block-time margin reflects how it builds a schedule and which routes it flies, and is not a ranking. The last three columns are what this table is for.

Not an average of opposite behaviors

A pooled result of almost exactly zero invites the suspicion that it is two real effects cancelling, so it is worth checking carrier by carrier as well as by route length. It is not. Every one of the 12 carriers gives back less schedule when it leaves an hour late than when it leaves on time, the same direction every time. All of them taxi out longer when they are late. The airborne column, by contrast, has no direction at all: 6 carriers are airborne less when late and 6 are airborne more, and the largest movement in either direction is 1.83 min (Envoy Air). A real operational practice of flying faster when behind schedule would show up as one sign repeated down that column. What is there instead is noise around zero, in an industry where every carrier has the same incentive and the same fuel bill.

Minutes given back against the scheduled block, by scheduled departure hour

05:00 · 392,952 flights · taxi-out 14.8 min7.6 min
06:00 · 1,065,297 flights · taxi-out 17.1 min6.6 min
07:00 · 1,252,974 flights · taxi-out 18.8 min5.7 min
08:00 · 1,320,273 flights · taxi-out 19.9 min5.9 min
09:00 · 1,090,259 flights · taxi-out 19.8 min5.9 min
10:00 · 1,153,553 flights · taxi-out 19.2 min6.1 min
11:00 · 1,114,826 flights · taxi-out 18.5 min6.0 min
12:00 · 1,011,507 flights · taxi-out 17.8 min5.8 min
13:00 · 1,042,005 flights · taxi-out 18.0 min5.3 min
14:00 · 1,003,125 flights · taxi-out 18.3 min4.8 min
15:00 · 1,030,576 flights · taxi-out 18.6 min4.8 min
16:00 · 1,028,635 flights · taxi-out 19.0 min4.4 min
17:00 · 1,100,330 flights · taxi-out 19.5 min4.5 min
18:00 · 1,085,892 flights · taxi-out 19.7 min5.2 min
19:00 · 1,039,427 flights · taxi-out 19.5 min5.8 min
20:00 · 905,342 flights · taxi-out 19.2 min6.3 min
21:00 · 701,319 flights · taxi-out 18.6 min6.7 min
22:00 · 490,626 flights · taxi-out 17.9 min6.9 min
23:00 · 179,134 flights · taxi-out 17.5 min8.7 min

The spare minutes are spent on the ground

The same quantity across the day makes the mechanism hard to miss, once one hour is handled separately. 23:00 is not an ordinary hour of the schedule: the mean sector there is 1,669 miles against 888 across the day as a whole, because what departs then is the red-eye bank. Route length is the largest single driver of how much schedule a flight carries. Both versions are reported here rather than one. Across all 19 hours the correlation between an hour's margin and its taxi-out is 0.56 and the correlation with its mean route length is -0.61. On those two numbers alone route length is the better explanation and the taxi story should be dropped. Excluding the red-eye hour, the route-length correlation collapses to -0.02 across the remaining 18 hours while the taxi-out correlation holds at 0.57. Within the ordinary working day, then, a flight scheduled out at 05:00 gave back 7.60 min of its schedule and one scheduled at 16:00 gave back 4.39 min, and the shape of that curve tracks taxi-out rather than distance. This is an association across 18 hours, not a measurement of cause, and it rests on excluding an hour, which is why the excluded hour, its size and the figures with it left in are all printed above. It points the same way as the standardized comparison, from a different direction: the slack in a schedule is consumed by the airport surface, and the surface is worst at the hours when flights are already running late.

Every covered airport, as an origin

Every covered airport, as an origin
#AirportCityDeparturesMean route lengthAgainst scheduleTaxi-outLeft on timeLeft an hour lateDifference
1JFKNew York350,4281293 mi-7.9827.4 min-8.62-4.53+4.10
2BWIBaltimore302,008819 mi-7.2615.3 min-7.66-4.32+3.34
3LGANew York450,255766 mi-7.2424.5 min-8.03-3.18+4.84
4EWRNewark385,0881122 mi-7.0324.7 min-7.64-3.63+4.01
5BOSBoston443,5451050 mi-6.8720.9 min-7.24-4.72+2.52
6LASLas Vegas576,522985 mi-6.7818.0 min-6.86-5.59+1.28
7SFOSan Francisco443,6411232 mi-6.6221.2 min-6.54-7.35-0.82
8LAXLos Angeles604,9801311 mi-6.6218.2 min-6.60-6.16+0.44
9ABEAllentown11,869742 mi-6.5915.2 min-7.29-2.37+4.93
10HOUHouston174,359735 mi-6.5512.6 min-6.83-4.07+2.76
11MDWChicago243,496830 mi-6.4414.4 min-6.78-4.22+2.56
12OAKOakland118,967705 mi-6.3612.8 min-6.44-5.23+1.21
13BURBurbank94,807562 mi-6.2817.3 min-6.43-4.62+1.81
14MSPMinneapolis375,927832 mi-6.2318.3 min-6.59-3.49+3.10
15IADWashington172,4261048 mi-6.1221.2 min-6.21-5.81+0.40
16SNASanta Ana139,325797 mi-6.1115.7 min-6.10-5.33+0.78
17DALDallas226,457730 mi-6.1013.0 min-6.44-3.83+2.61
18ONTOntario81,277773 mi-6.0113.6 min-6.12-4.63+1.49
19IAHHouston362,841965 mi-5.9920.1 min-6.10-5.14+0.96
20BNANashville324,097726 mi-5.9916.0 min-6.18-3.54+2.64
21SJUSan Juan110,4871457 mi-5.9215.7 min-5.86-5.76+0.10
22CLECleveland127,569722 mi-5.9115.8 min-6.31-2.39+3.92
23PHLPhiladelphia307,234922 mi-5.9121.5 min-6.42-3.34+3.08
24STLSt. Louis200,977745 mi-5.8412.5 min-6.17-2.93+3.24
25PHXPhoenix607,586952 mi-5.8216.0 min-5.74-5.60+0.14
26CMHColumbus135,318660 mi-5.8215.2 min-6.30-1.56+4.74
27DCAWashington432,368665 mi-5.7921.6 min-6.39-2.76+3.63
28MEMMemphis73,407652 mi-5.7814.7 min-6.17-2.45+3.72
29SLCSalt Lake City362,156825 mi-5.7718.1 min-5.74-5.47+0.28
30ABQAlbuquerque77,267657 mi-5.7414.5 min-5.91-3.69+2.21
31RDURaleigh–Durham180,765672 mi-5.7117.5 min-5.96-3.61+2.35
32SANSan Diego302,5641055 mi-5.5821.2 min-5.67-4.22+1.45
33SMFSacramento175,746784 mi-5.5713.6 min-5.56-4.76+0.80
34SJCSan Jose149,652742 mi-5.5614.1 min-5.58-4.84+0.74
35MKEMilwaukee88,839719 mi-5.5315.3 min-5.98-1.63+4.35
36PITPittsburgh134,106672 mi-5.5315.5 min-5.98-1.59+4.39
37BUFBuffalo65,702603 mi-5.5115.0 min-5.99-1.61+4.38
38AUSAustin276,572936 mi-5.5115.4 min-5.64-4.08+1.57
39INDIndianapolis148,228737 mi-5.4615.4 min-5.91-1.22+4.69
40DENDenver979,616860 mi-5.4619.1 min-5.64-4.63+1.01
41OMAOmaha76,128728 mi-5.4614.9 min-5.76-2.77+2.99
42MSYNew Orleans154,946786 mi-5.4313.2 min-5.62-3.37+2.25
43ANCAnchorage60,2981463 mi-5.4215.3 min-5.21-6.21-1.00
44DTWDetroit392,798728 mi-5.4018.2 min-5.75-2.86+2.89
45SATSan Antonio128,716826 mi-5.3513.1 min-5.46-3.47+1.99
46MYRMyrtle Beach45,455481 mi-5.3513.5 min-5.76-2.67+3.09
47MIAMiami342,7501048 mi-5.3321.2 min-5.74-3.94+1.80
48MCIKansas City154,514783 mi-5.3314.5 min-5.63-2.09+3.54
49FLLFort Lauderdale279,8741051 mi-5.2917.8 min-5.73-3.40+2.33
50ILMWilmington23,752442 mi-5.2717.1 min-5.77-1.96+3.81
51SEASeattle520,1541262 mi-5.2521.6 min-5.15-5.56-0.41
52MCOOrlando501,100970 mi-5.2119.1 min-5.54-3.54+1.99
53TPATampa243,084939 mi-5.1015.8 min-5.38-3.04+2.34
54DFWDallas–Fort Worth964,184811 mi-5.0619.6 min-5.42-3.31+2.12
55CLTCharlotte621,290629 mi-5.0521.2 min-5.33-4.13+1.20
56ORDChicago964,770760 mi-4.9725.6 min-5.47-2.78+2.69
57CHSCharleston77,513601 mi-4.9616.0 min-5.33-1.93+3.40
58JAXJacksonville90,948684 mi-4.8514.4 min-5.12-2.93+2.19
59TUSTucson60,144662 mi-4.8415.4 min-4.93-2.78+2.15
60PDXPortland191,6951072 mi-4.6615.4 min-4.52-4.65-0.13
61RSWFort Myers107,035999 mi-4.4615.5 min-4.88-2.00+2.88
62SBASanta Barbara25,005548 mi-4.4215.7 min-4.73-2.05+2.67
63ATLAtlanta1,023,190698 mi-4.1416.8 min-4.48-1.77+2.72
64HNLHonolulu189,1521355 mi-4.0416.4 min-3.76-7.24-3.48

Every column is a departures measure over flights that left this airport, including the taxi-out column. Airports with at least 5,000 completed departures, ranked by how much of their schedule their flights give back. The mean route length column is there because it is the confound for the rest of the table.

What the weighting does, and one explanation that did not survive

Two housekeeping results, both of which happen to be undramatic and are reported anyway. First, the weighting. Averaging the 64 airport averages together, one airport one vote, gives -5.71 min; weighting each airport by the departures it actually operated gives -5.71 min. On this particular quantity the choice barely matters, which is worth stating precisely because on other quantities in this dataset it decides the answer outright. Every network figure in this report is the departures-weighted one. The late-versus-on-time gap behaves the same way: 2.10 min weighted against 2.21 min unweighted, and 59 of the 64 airports show the late departure recovering less than the on-time one. Second, an explanation that looked good and is mostly false. JFK (New York) gives back the most schedule of any covered airport at 7.98 min, and it has a taxi-out of 27.4 min; HNL (Honolulu) gives back the least at 4.04 min on a taxi-out of 16.4 min. The tempting reading is that airlines pad their schedules where the ground is slow, and across all 64 airports the correlation is -0.29, which looks like support. But the airports with slow surfaces also fly longer average sectors (-0.18 between margin and mean route length), and route length is the dominant driver of margin. Restate every airport's margin and taxi-out onto one common route-length mix (the national one, the same standardization used earlier in this report) and the correlation falls to -0.17 across the 39 airports that qualify in every one of the 4 route-length bands. Computed separately inside each band it is -0.08 on under 750 miles, -0.24 on 750–1,499 miles, 0.06 on 1,500–1,999 miles, -0.27 on 2,000 miles and over, which is the more informative result: it is weaker than the headline number, and it is not the same strength twice. Roughly half of the apparent relationship was route mix and what is left is weak and unstable across route lengths. Something may genuinely be there. It is not enough for this report to claim that airlines pad schedules where the ground is slow, so that claim is not made.

How often a late departure still arrived on time

How often a late departure still arrived on time
Route lengthLast minute late that is still better than even money30 minutes late45 minutes late60 minutes late
Under 750 miles21 min15.2%0.59%0.02%
750–1,499 miles22 min25.0%2.69%0.09%
1,500–1,999 miles23 min33.2%5.99%0.74%
2,000 miles and over25 min38.7%11.51%2.13%

Share of flights that pushed back this many minutes late and still arrived within fifteen minutes of schedule, at one-minute resolution over the whole period. A minute is shown only where the band recorded at least 120 flights at exactly that departure delay. The second column is the last whole minute at which the share is still above half; by the following minute it is below.

22 minutes

The practical version of all of this is a single number. Across every covered airport, a flight that pushed back 22 minutes late arrived on time 50.10% of the time. That is the last whole minute of delay at which the odds are still on your side, and the point at which a departure delay stops being absorbed and starts being inherited. Route length moves that line, but much less than the folklore suggests: from 21 minutes on flights under 750 miles to 25 on flights of 2,000 miles and over, a difference of 4 minutes. What route length really buys is not a later crossing but a longer tail beyond it. At 30 minutes down, 15.2% of flights under 750 miles still arrived on time against 38.7% of flights of 2,000 miles and over; at 45 minutes down it is 0.59% against 11.51%. A transcontinental flight does not give you meaningfully more grace before the odds turn against you. It gives you a real chance of recovery in a situation where a short hop has none, which is the same finding as the airborne table above, seen from the passenger's side.

What this is not

Four limits, in descending order of how much they could matter. First, this report measures flights that finished. A flight that gives up and lands somewhere else leaves the population, and it does so more often the later it departed: 0.22% of flights pushing back on time were diverted against 0.61% of those pushing back an hour or more late. Those are small numbers, but they are removed disproportionately from the group that is already doing worst, which means the recovery figures for late departures are if anything flattering. Second, the airborne column is derived from three reported fields rather than observed directly, and it inherits whatever the carrier reported for taxi-out and taxi-in; it is also block time minus taxi rather than wheels-off to wheels-on as an air traffic system would define it. Third, the scheduled block time carries each route's timezone offset, so it is only ever compared within a route and never quoted as an absolute. Within a route it still varies, because carriers retime flights across three years, which is why it is a measured column in the decomposition rather than an assumed constant. Fourth, this dataset contains no winds, no aircraft type, no cruise altitude and no flight plan. It can say that airborne time does not change when a flight is late; it cannot say whether a particular crew asked for a shortcut and got one.

What to do with this

The slack in an airline schedule is real and it is generous: 5.71 min on the average flight, 73.3% of flights finishing inside their block time. Treat it as a standing discount rather than a rescue service. It is already priced into the departure delay you are looking at on the app, it does not get larger because your flight is in trouble, and on the evidence here it gets smaller. Three things follow. If you are watching a delay grow and doing connection arithmetic, the realistic expectation is that you will land about 3.87 min better than the departure delay you can see, not the half hour the announcement implies. Past 22 minutes down, more than half of these flights arrive late. If the leg in trouble is a short hop, assume no recovery at all; the aircraft is airborne no less time than usual and will taxi longer at both ends. And if you have a choice between two itineraries with the same total delay exposure, the one whose long sector is the one at risk is the better bet, because that is the only place in this data where an airplane measurably makes up time. None of this predicts an individual flight. It describes what happened to 18,056,969 of them.

Pages for what this report covers

Methodology

Calculated by FlyerIntel from 22,316,707 individual flight records in the US Department of Transportation Bureau of Transportation Statistics Reporting Carrier On-Time Performance dataset, covering July 2023 through August 2026. Following BTS methodology, a flight counts as delayed when it arrives 15 or more minutes after its scheduled arrival time. Cancelled and diverted flights have no arrival time and are excluded from on-time rates rather than counted as late; cancellation rates are reported separately. Full definitions are published at /methodology/. Every figure in this report is a departures measure: one record is one completed flight that departed one of the 64 airports FlyerIntel covers, and every network figure is departures-weighted from summed counts rather than averaged across airport averages. Nothing here is measured on arrivals. The report's central quantity is a flight's arrival delay minus its departure delay, which is identically the actual gate-to-gate block time minus the scheduled one; because both delays are differences taken at a single airport, no timezone or clock arithmetic enters it. Cancelled and diverted flights have no block time and are excluded, and the share excluded is reported rather than assumed harmless. Airborne minutes are derived as the scheduled block time plus that overrun, less reported taxi-out and taxi-in; scheduled block time is taken from the two local clock fields and therefore carries the route's own constant timezone offset, so both quantities are compared only within a single origin-destination pair, where that offset cancels exactly, and are never quoted as absolute flying times. The standardized comparisons are direct standardizations: each is computed inside one (origin, destination, operating carrier) cell with at least 200 flights in every one of the three departure groups, then reweighted onto the hour-or-more-late group's own mix so all three groups describe an identical set of routes and airlines; the pooled table, the route-length table and the carrier table are computed from one pass over that single cell set. The two further checks additionally hold the scheduled departure hour, and then the calendar month, constant, at 100 flights per group per cell. A carrier is shown only above 20 qualifying route cells; an airport only above 5,000 completed departures; a departure-delay minute in the arrival-odds table only above 120 flights at exactly that minute. Where the report correlates figures across the hours of the day, hours whose mean sector exceeds 1.5 times the day's own mean (the red-eye bank, which is a different product flown over a different distance) are reported separately rather than dropped, and the correlations are published both with and without them. Where it correlates figures across airports, each airport is restated onto the national route-length mix by the same direct standardization, using only airports with at least 1,000 departures in every route-length band. The five columns of the decomposition satisfy an exact identity and the generator refuses to publish if they fail to reconcile to within a thousandth of a minute.

Limitations

The source dataset covers scheduled domestic flights operated by carriers above the DOT reporting threshold; smaller carriers and international flights are not included. Flights sold under a mainline brand but flown by a regional carrier are attributed to the operating carrier, which is how the DOT records them. Past performance describes what has happened and is not a prediction about any individual flight. This report measures flights that completed, and diverted flights are removed from it disproportionately from the group that departed latest, so the recovery figures quoted for late departures are a best case rather than a neutral one. Airborne time is derived from reported block and taxi figures rather than observed, inherits any error in the carrier's taxi reporting, and is block time less taxi rather than wheels-off to wheels-on. Scheduled block time carries each route's timezone offset and is meaningful only as a comparison within one route; it also varies within a route as carriers retime flights across three years, which is why it appears as a measured column rather than a constant. The dataset contains no winds aloft, aircraft type, cruise altitude, routing or flight plan, so it can establish that airborne time does not change materially when a flight is running late but cannot describe what any individual crew did about it. Schedule margin is not evidence of padding for its own sake: a block time has to cover a bad day as well as a good one, and one set at the average would make half of all flights late by construction. Figures are averages across three years, every season and every airport, and describe what has happened rather than what will happen to any particular flight.

Sources

  • FlyerIntel analysis — FlyerIntel · source
  • Reporting Carrier On-Time Performance — US Department of Transportation, Bureau of Transportation Statistics · source

Full FlyerIntel methodology · Report a problem with this analysis