Flight profile · United Airlines
UA2652
Chicago (ORD) to Cleveland (CLE) · scheduled 6:10 PM – 8:35 PM
How UA2652 performs
804 operations, February 2024 – July 2026.
UA2652 arrived on time 68.6% of the time, against 74.5% for all ORD → CLE flights, so this departure is 5.9 percentage points worse than the route as a whole. Against United Airlines’ own flights on this route it is 8.6 points worse.
Source: US DOT Bureau of Transportation Statistics · 804 operations, February 2024 – July 2026 · If UA2652 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where UA2652 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 UA2652 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 |
|---|---|---|---|---|---|
| UA2652 | 68.6% | 0.87% | -1 min | 13.3% | 804 |
| United Airlines on ORD → CLE | 77.2% | 1.11% | -5 min | 8.9% | 6,058 |
| All ORD → CLE flights | 74.5% | 2.08% | -4 min | 10.0% | 11,752 |
UA2652 has cancelled 0.87% of its scheduled departures (7 of 804), against 2.08% for all ORD → CLE flights — this specific departure cancels 1.2 percentage points less often than the route as a whole. Different flight numbers on the same route can carry different aircraft, crews and schedules, so this is a fact about UA2652 specifically, not about the route it flies.
Source: FlyerIntel analysis of US DOT BTS data · February 2024 – July 2026
Why UA2652 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding and fueling, all within the carrier’s control
airspace and airport capacity, including weather-driven flow control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for UA2652 on ORD → CLE. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering February 2024 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA2652 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, UA2652 pushed back an average of 52 minutes late; when it came in on time or early, an average of 4 minutes late.
Each departure is matched to the flight the same aircraft flew into ORD just before it, using the tail number in the DOT file, 732 of 798 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 |
|---|---|---|---|
| UA2652 | 22% | 52% | 10% |
| Network, same turn | 17% | 68% | 9% |
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 60 to 89 minutes. How often UA2652’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often UA2652 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 February 2024 – July 2026
From pushback to gate
When it leaves ORD late, does that still matter by the time it reaches CLE?
On arrival at CLE, UA2652 spends 5.9 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.6 minutes shorter than a typical CLE arrival (8.5 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 CLE. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 81,342 departures from ORD scheduled in the clock hour UA2652 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at CLE (127,091 flights), not just UA2652’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · February 2024 – July 2026
The hour it leaves ORD
Part of any flight’s record belongs to the clock rather than to the flight. UA2652 has one departure time, so this is what that time is worth.
On-time arrival rate. 81,342 departures from ORD are scheduled in the 6 PM–7 PM hour over the period, against 952,802 across the whole day.
UA2652 is scheduled out of ORD at 6:10 PM, in the 6 PM–7 PM bank. Departures from ORD in that hour arrive on time 67.0% of the time against 74.5% across the airport’s whole day — the slot alone is worth 7.5 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from ORD 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 · February 2024 – July 2026 · Hours below 120 departures are not scored.
Other routes UA2652 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 |
|---|---|---|---|
| SAT→ORD San Antonio to Chicago | March 7, 2024 – June 23, 2026 | 44 | — |
| BNA→ORD Nashville to Chicago | March 5, 2026 – May 20, 2026 | 77 | — |
| JAC→ORD Jackson to Chicago | September 25, 2025 – March 4, 2026 | 108 | 78.3% |
| SNA→ORD Santa Ana to Chicago | May 23, 2024 – December 1, 2025 | 71 | — |
| SEA→ORD Seattle to Chicago | August 19, 2025 – September 24, 2025 | 37 | — |
| CVG→ORD Cincinnati / Covington to Chicago | June 26, 2025 – August 18, 2025 | 38 | — |
| ORD→RSW Chicago to Fort Myers | August 1–18, 2025 | 18 | — |
| EWR→TPA Newark to Tampa | July 5–27, 2025 | 7 | — |
| EWR→CLE Newark to Cleveland | July 6, 2025 | 1 | — |
| MCI→ORD Kansas City to Chicago | May 22–31, 2025 | 10 | — |
| TUS→ORD Tucson to Chicago | March 6, 2025 – May 21, 2025 | 77 | — |
| ORD→RIC Chicago to Richmond | May 21, 2025 | 1 | — |
| PNS→ORD Pensacola to Chicago | January 9, 2024 – February 12, 2025 | 93 | 84.4% |
| ORD→LAS Chicago to Las Vegas | January 9, 2024 – February 14, 2024 | 34 | — |
| MCI→DEN Kansas City to Denver | December 21, 2023 – January 8, 2024 | 19 | — |
| ORD→LGA Chicago to New York | November 28, 2023 – December 20, 2023 | 23 | — |
| SMF→ORD Sacramento to Chicago | December 1–20, 2023 | 18 | — |
| DEN→SEA Denver to Seattle | September 5, 2023 – November 27, 2023 | 56 | — |
| SEA→EWR Seattle to Newark | October 2–28, 2023 | 22 | — |
| ORD→ANC Chicago to Anchorage | October 1–22, 2023 | 4 | — |
| SFO→BOS San Francisco to Boston | July 1, 2023 – September 28, 2023 | 90 | 67.0% |
| SEA→SFO Seattle to San Francisco | September 5–28, 2023 | 24 | — |
Because the same number has served different journeys, the statistics above describe only the route UA2652 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.
78 min late
against a median of 1 min early
UA2652 has an average that understates its risk: a typical arrival is 1 min early, but the worst tenth are 79 minutes worse than that. If the trip has something unmissable at the end of it, the median is the wrong number to plan against.
Percentiles over 804 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering February 2024 – July 2026
Other flights on this route
Same airports, same journey, different odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| UA2347 | United Airlines | 73.5% | 2 min early | 684 |
| UA2652 this flight | United Airlines | 68.6% | 1 min early | 804 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA2652 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 804 records of UA2652 operating ORD → CLE, 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