Flight profile · United Airlines
UA563
Chicago (ORD) to Newark (EWR) · scheduled 7:10 AM – 10:30 AM
How UA563 performs
972 operations, October 2023 – July 2026.
UA563 arrived on time 90.3% of the time, against 71.7% for all ORD → EWR flights, so this departure is 18.6 percentage points better than the route as a whole. Against United Airlines’ own flights on this route it is 16.1 points better.
Source: US DOT Bureau of Transportation Statistics · 972 operations, October 2023 – July 2026 · If UA563 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
What stands out
How UA563 compares to other flight numbers, not just to itself.
This flight runs unusually far ahead of the ORD → EWR route as a whole, better than 100% of 11,788 comparable flight numbers.
90.3% on time for this specific departure, against 71.7% for every ORD → EWR flight.
Source: FlyerIntel analysis of US DOT BTS data · October 2023 – July 2026 · The one thing about this specific departure that ranks most extreme against every other published flight number, out of everything FlyerIntel checks — shown only when something clears a real statistical bar, not for every flight.
Where UA563 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 UA563 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 |
|---|---|---|---|---|---|
| UA563 | 90.3% | 1.13% | -14 min | 3.1% | 972 |
| United Airlines on ORD → EWR | 74.2% | 2.22% | -7 min | 12.2% | 12,999 |
| All ORD → EWR flights | 71.7% | 2.81% | -5 min | 13.2% | 18,463 |
UA563 has cancelled 1.13% of its scheduled departures (11 of 972), against 2.81% for all ORD → EWR flights — this specific departure cancels 1.7 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 UA563 specifically, not about the route it flies.
Source: FlyerIntel analysis of US DOT BTS data · October 2023 – July 2026
Why UA563 runs late
Where US DOT attributed the delay minutes on this flight.
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
the inbound aircraft was late, so this flight started late
Share of the delay minutes US DOT attributed to each cause for UA563 on ORD → EWR. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering October 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA563 comes in late, and what that does to the departure.
UA563 is usually the aircraft’s first flight of the day: the schedule gives it a median of 7.9 hours on the ground at ORD, so its “inbound” is mostly the aircraft’s arrival the evening before.
When the aircraft came in 15 or more minutes late, UA563 pushed back an average of 2 minutes late; when it came in on time or early, an average of 0 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, 739 of 961 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 |
|---|---|---|---|
| UA563 | 21% | 9% | 7% |
| Network, same turn | 29% | 12% | 9% |
A night on the ground absorbs most of a late arrival, so a late inbound matters far less on a turn this long than on a same-day one.
The network row is every flight with a scheduled turn of 6 hours or more, usually overnight. How often UA563’s aircraft landed 15 or more minutes late is lower than the network’s and, once the aircraft was late, how often UA563 left 15 or more minutes late is about the same as 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 October 2023 – July 2026
From pushback to gate
When it leaves ORD late, does that still matter by the time it reaches EWR?
UA563 pushes back an average of 2.3 minutes late and reaches the gate at EWR an average of 6.9 minutes early. The 9.1 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 23.3 minutes on the taxiways at ORD, 1.0 minutes shorter than a typical ORD departure in the same hour.
On arrival at EWR, UA563 spends 9.6 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 about what any arrival at EWR spends on the ground before reaching the gate.
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 EWR. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 67,479 departures from ORD scheduled in the clock hour UA563 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at EWR (387,854 flights), not just UA563’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · October 2023 – July 2026
The hour it leaves ORD
Part of any flight’s record belongs to the clock rather than to the flight. UA563 has one departure time, so this is what that time is worth.
On-time arrival rate. 67,479 departures from ORD are scheduled in the 7 AM–8 AM hour over the period, against 952,802 across the whole day.
UA563 is scheduled out of ORD at 7:10 AM, in the 7 AM–8 AM bank. Departures from ORD in that hour arrive on time 86.6% of the time against 74.5% across the airport’s whole day — the slot alone is worth 12.1 points better 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 · October 2023 – July 2026 · Hours below 120 departures are not scored.
By day of week
Does UA563 run worse on particular days?
Wednesday is historically the most reliable day and Monday the least, a gap of 8.4 percentage points.
Source: FlyerIntel analysis of US DOT BTS data · October 2023 – July 2026 · Days with fewer than 120 operations are not scored.
Other routes UA563 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 |
|---|---|---|---|
| LAX→TPA Los Angeles to Tampa | March 7–28, 2026 | 4 | — |
| SFO→STL San Francisco to St. Louis | February 14–28, 2026 | 3 | — |
| PBI→IAH West Palm Beach to Houston | February 4, 2026 | 1 | — |
| LAS→ORD Las Vegas to Chicago | May 23, 2025 – June 13, 2025 | 12 | — |
| IAH→TUL Houston to Tulsa | February 15, 2025 – March 1, 2025 | 3 | — |
| IAH→FLL Houston to Fort Lauderdale | November 29–30, 2024 | 2 | — |
| ORD→SAV Chicago to Savannah | June 29, 2024 – August 17, 2024 | 8 | — |
| PHX→ORD Phoenix to Chicago | December 21, 2023 – January 8, 2024 | 19 | — |
| EWR→JAX Newark to Jacksonville | January 1–8, 2024 | 7 | — |
| RDU→IAH Raleigh–Durham to Houston | July 1, 2023 – October 28, 2023 | 119 | 93.3% |
Because the same number has served different journeys, the statistics above describe only the route UA563 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.
14 min late
against a median of 14 min early
Percentiles over 972 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering October 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 |
|---|---|---|---|---|
| UA1658 | United Airlines | 93.4% | 14 min early | 633 |
| UA563 this flight | United Airlines | 90.3% | 14 min early | 972 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA563 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 972 records of UA563 operating ORD → EWR, 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