Flight profile · United Airlines
UA1776
Chicago (ORD) to Philadelphia (PHL) · scheduled 6:20 PM – 9:35 PM
How UA1776 performs
930 operations, November 2023 – July 2026.
UA1776 arrived on time 64.7% of the time, against 72.1% for all ORD → PHL flights, so this departure is 7.4 percentage points worse than the route as a whole. Against United Airlines’ own flights on this route it is 9.5 points worse.
Source: US DOT Bureau of Transportation Statistics · 930 operations, November 2023 – July 2026 · If UA1776 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where UA1776 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 UA1776 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 |
|---|---|---|---|---|---|
| UA1776 | 64.7% | 1.08% | 3 min | 13.4% | 930 |
| United Airlines on ORD → PHL | 74.2% | 0.97% | -4 min | 9.7% | 5,170 |
| All ORD → PHL flights | 72.1% | 2.05% | -3 min | 11.7% | 14,168 |
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
Why UA1776 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 UA1776 on ORD → PHL. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering November 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA1776 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, UA1776 pushed back an average of 56 minutes late; when it came in on time or early, an average of 7 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, 825 of 921 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 |
|---|---|---|---|
| UA1776 | 25% | 63% | 15% |
| 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 UA1776’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often UA1776 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 November 2023 – July 2026
From pushback to gate
When it leaves ORD late, does that still matter by the time it reaches PHL?
On arrival at PHL, UA1776 spends 6.7 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 1.5 minutes shorter than a typical PHL arrival (8.2 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 PHL. 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 UA1776 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at PHL (305,143 flights), not just UA1776’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
The hour it leaves ORD
Part of any flight’s record belongs to the clock rather than to the flight. UA1776 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.
UA1776 is scheduled out of ORD at 6:20 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 · November 2023 – July 2026 · Hours below 120 departures are not scored.
By day of week
Does UA1776 run worse on particular days?
Tuesday is historically the most reliable day and Sunday the least, a gap of 13.6 percentage points.
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026 · Days with fewer than 120 operations are not scored.
Other routes UA1776 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 |
|---|---|---|---|
| SLC→ORD Salt Lake City to Chicago | May 21–31, 2026 | 11 | — |
| MSY→ORD New Orleans to Chicago | March 29, 2026 – April 25, 2026 | 7 | — |
| PSP→ORD Palm Springs to Chicago | February 12, 2026 – March 28, 2026 | 45 | — |
| SFO→PSP San Francisco to Palm Springs | February 12, 2026 – March 4, 2026 | 21 | — |
| MCO→ORD Orlando to Chicago | December 18, 2025 – January 5, 2026 | 19 | — |
| PNS→ORD Pensacola to Chicago | October 26, 2025 – December 1, 2025 | 36 | — |
| LAS→ORD Las Vegas to Chicago | March 6, 2025 – July 29, 2025 | 48 | — |
| RSW→ORD Fort Myers to Chicago | March 30, 2025 – May 21, 2025 | 53 | — |
| PHL→ORD Philadelphia to Chicago | July 1, 2023 – July 6, 2024 | 345 | 83.1% |
| ORD→OMA Chicago to Omaha | October 30, 2023 – November 27, 2023 | 21 | — |
| MCO→IAH Orlando to Houston | November 26, 2023 | 1 | — |
Because the same number has served different journeys, the statistics above describe only the route UA1776 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.
79 min late
against a median of 3 min late
UA1776 has an average that understates its risk: a typical arrival is 3 min late, but the worst tenth are 76 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 930 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering November 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 |
|---|---|---|---|---|
| AA1854 | American Airlines | 85.4% | 10 min early | 600 |
| AA1941 | American Airlines | 70.6% | 1 min early | 602 |
| UA1776 this flight | United Airlines | 64.7% | 3 min late | 930 |
| AA2840 | American Airlines | 62.1% | 7 min late | 996 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA1776 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 930 records of UA1776 operating ORD → PHL, 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