Flight profile · United Airlines
UA516
Atlanta (ATL) to Chicago (ORD) · scheduled 3:30 PM – 4:51 PM
How UA516 performs
989 operations, September 2023 – July 2026.
UA516 arrived on time 78.3% of the time, against 74.1% for all ATL → ORD flights, so this departure is 4.2 percentage points better than the route as a whole. Against United Airlines’ own flights on this route it is 1.3 points worse.
Source: US DOT Bureau of Transportation Statistics · 989 operations, September 2023 – July 2026 · If UA516 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where UA516 is right now
A live reading, only if you ask for it. It is not part of the reliability record above.
Ask for the position of UA516 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.
Against the rest of the route
| Flight or route | On time | Cancelled | Median delay | Severe | Flights |
|---|---|---|---|---|---|
| UA516 | 78.3% | 0.91% | -6 min | 9.4% | 989 |
| United Airlines on ATL → ORD | 79.6% | 1.24% | -5 min | 7.9% | 4,914 |
| All ATL → ORD flights | 74.1% | 1.68% | -3 min | 9.5% | 18,588 |
Source: FlyerIntel analysis of US DOT BTS data · September 2023 – July 2026
Why UA516 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
airspace and airport capacity, including weather-driven flow control
crew, maintenance, boarding and fueling, all within the carrier’s control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for UA516 on ATL → ORD. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering September 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA516 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, UA516 pushed back an average of 71 minutes late; when it came in on time or early, an average of 6 minutes late.
Each departure is matched to the flight the same aircraft flew into ATL just before it, using the tail number in the DOT file, 968 of 981 departures in all. A departure is left out when that flight is unknown, was cancelled or diverted, or the aircraft had sat for more than 12 hours. A flight the airline cancelled never left and is not in the count, and one flown by a substitute aircraft is matched to the aircraft that flew it, not to the one first planned.
Against the network at the same turn length
| Share of departures | Inbound landed 15+ late | Left 15+ late after a late inbound | Left 15+ late after an on-time inbound |
|---|---|---|---|
| UA516 | 15% | 76% | 7% |
| Network, same turn | 18% | 85% | 10% |
The schedule leaves a normal turn: enough time to clean and board if the aircraft is on time, little to spare if it is not.
The network row is every flight with a scheduled turn of 45 to 59 minutes. How often UA516’s aircraft landed 15 or more minutes late is about the same as the network’s and, once the aircraft was late, how often UA516 left 15 or more minutes late is lower than the network’s.
More: Which Flight Numbers Pay for a Late Aircraft lists the flight numbers that pass a late aircraft on.
Source: US DOT Bureau of Transportation Statistics · Data covering September 2023 – July 2026
From pushback to gate
When it leaves ATL late, does that still matter by the time it reaches ORD?
UA516 pushes back an average of 18.1 minutes late and reaches the gate at ORD an average of 14.8 minutes late. The 3.3 minutes between those two figures are slack the published schedule already carries, which is why a late pushback on this flight does not reliably become a late arrival. It spends 20.7 minutes on the taxiways at ATL, 3.6 minutes longer than a typical ATL departure in the same hour.
On arrival at ORD, UA516 spends 15.3 min taxiing from touchdown to the gate — ground time a connecting passenger sits through before they can even leave the aircraft, on top of however late the flight itself ran. That is 2.5 minutes shorter than a typical ORD arrival (17.8 min).
Departure delay is averaged over every pushback and arrival delay over every completed arrival, so the two counts differ by the flights that never reached ORD. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 72,506 departures from ATL scheduled in the clock hour UA516 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at ORD (952,666 flights), not just UA516’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · September 2023 – July 2026
The hour it leaves ATL
Part of any flight’s record belongs to the clock rather than to the flight. UA516 has one departure time, so this is what that time is worth.
On-time arrival rate. 72,506 departures from ATL are scheduled in the 3 PM–4 PM hour over the period, against 1,012,247 across the whole day.
UA516 is scheduled out of ATL at 3:30 PM, in the 3 PM–4 PM bank. Departures from ATL in that hour arrive on time 75.8% of the time against 78.7% across the airport’s whole day, so the hour UA516 leaves in is an ordinary one for ATL and explains nothing about its record either way.
The two airport figures cover every departure from ATL to every destination, so they describe the slot rather than this journey — the like-for-like comparison against the route is above. Hours are scheduled local, and a number whose schedule moved between banks inside the period has no single hour and is not described here at all. Why the hour matters.
Source: FlyerIntel analysis of US DOT BTS data · September 2023 – July 2026 · Hours below 120 departures are not scored.
By day of week
Does UA516 run worse on particular days?
Saturday is historically the most reliable day and Thursday the least, a gap of 15.5 percentage points.
Source: FlyerIntel analysis of US DOT BTS data · September 2023 – July 2026 · Days with fewer than 120 operations are not scored.
Other routes UA516 has flown
A flight number is a slot in a schedule, and carriers reassign it. These are the other city pairs this number served in the analysis period.
| Route | Operated | Flights | On time |
|---|---|---|---|
| ORD→BDL Chicago to Hartford | March 5, 2026 – July 31, 2026 | 143 | 47.9% |
| ORD→JAX Chicago to Jacksonville | July 4, 2026 | 1 | — |
| ORD→ONT Chicago to Ontario | December 18, 2025 – January 5, 2026 | 19 | — |
| ORD→TVC Chicago to Traverse City | October 26, 2025 – December 17, 2025 | 52 | — |
| RSW→IAD Fort Myers to Washington | November 27, 2025 | 1 | — |
| ORD→SNA Chicago to Santa Ana | August 19, 2024 – October 24, 2025 | 91 | 78.7% |
| ORD→DFW Chicago to Dallas–Fort Worth | December 3, 2024 – July 31, 2025 | 169 | 57.2% |
| SRQ→ORD Sarasota/Bradenton to Chicago | December 21, 2023 – March 29, 2025 | 42 | — |
| ORD→DEN Chicago to Denver | November 30, 2024 – December 1, 2024 | 2 | — |
| ORD→LAS Chicago to Las Vegas | June 27, 2024 – August 18, 2024 | 52 | — |
| ORD→PHX Chicago to Phoenix | May 23, 2024 – June 26, 2024 | 35 | — |
| EWR→ATL Newark to Atlanta | May 2–22, 2024 | 18 | — |
| ORD→BZN Chicago to Bozeman | May 2–22, 2024 | 18 | — |
| ORD→DSM Chicago to Des Moines | December 21, 2023 – March 6, 2024 | 40 | — |
| IAH→MFE Houston to McAllen | January 13, 2024 | 1 | — |
| ORD→CHS Chicago to Charleston | November 23, 2023 | 1 | — |
| ORD→CID Chicago to Cedar Rapids | September 29–30, 2023 | 2 | — |
| ORD→SMF Chicago to Sacramento | September 7–28, 2023 | 13 | — |
| LGA→DEN New York to Denver | September 9–23, 2023 | 3 | — |
| CLT→EWR Charlotte to Newark | July 1, 2023 – September 4, 2023 | 66 | — |
Because the same number has served different journeys, the statistics above describe only the route UA516 currently operates. Blending them would produce an average of two different flights.
When it goes wrong
The average describes a usual day. This is the day that ruins a connection.
54 min late
against a median of 6 min early
Percentiles over 989 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering September 2023 – July 2026
Other flights on this route
Same airports, same journey, different odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| DL1178 | Delta Air Lines | 88.3% | 5 min early | 916 |
| DL1147 | Delta Air Lines | 80.4% | 3 min early | 1,054 |
| UA516 this flight | United Airlines | 78.3% | 6 min early | 989 |
| DL1199 | Delta Air Lines | 73.9% | 2 min early | 732 |
| DL1477 | Delta Air Lines | 72.4% | 0 min early | 977 |
| DL2738 | Delta Air Lines | 68.7% | 3 min late | 1,028 |
| UA1046 | United Airlines | 68.2% | 4 min late | 939 |
| DL2879 | Delta Air Lines | 54.7% | 11 min late | 887 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA516 is placed in the same ordering rather than left out of it; the rows around it are the most punctual departures on the route, not all of them, so this is a comparison and not a rank. Schedules change; confirm the departure still operates before booking around this.
Data and methodology
Calculated by FlyerIntel from 989 records of UA516 operating ATL → ORD, published by the US DOT Bureau of Transportation Statistics. A flight counts as delayed when it arrives 15 or more minutes after schedule. Cancelled and diverted flights are excluded from the on-time rate and reported separately. Flight numbers are resolved as carrier plus number plus route, because the same number serves different routes over time.
Full methodology · Data sources · Report a problem
Related research: Most and Least Reliable Flight Numbers · The Delay You Inherit · Making Up Time in the Air
Analysis last recomputed