UA308

UA308 arrived on time 63.4% of the time, against 77.2% for all PHL → ORD flights, so this departure is 13.8 percentage points worse than the route as a whole. Against United Airlines’ own flights on this route it is 16.2 points worse.

Source: US DOT Bureau of Transportation Statistics · 635 operations, June 2024 – July 2026 · If UA308 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.

This flight runs unusually far behind the carrier's own average on this route, worse than 96% of 11,589 comparable flight numbers.

63.4% on time for this specific departure, against 79.6% for the same carrier's other flights on this route.

Source: FlyerIntel analysis of US DOT BTS data · June 2024 – 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.

UA308 has cancelled 1.10% of its scheduled departures (7 of 635), against 2.20% for all PHL → ORD flights — this specific departure cancels 1.1 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 UA308 specifically, not about the route it flies.

Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026

Share of the delay minutes US DOT attributed to each cause for UA308 on PHL → ORD. Only delays of 15 minutes or more are attributed.

Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026

The aircraft flying UA308 came in 15 or more minutes late on 16% of the departures where its previous flight is known. There are not enough departures in both groups to say how the flight left after a late one and after an on-time one.

Each departure is matched to the flight the same aircraft flew into PHL just before it, using the tail number in the DOT file, 618 of 630 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.

Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026

UA308 pushes back an average of 19.4 minutes late and arrives a further 9.1 minutes behind that. This departure loses ground between the two gates rather than recovering it, so a late pushback here tends to get worse on the way, not better. It spends 22.4 minutes on the taxiways at PHL, 1.3 minutes longer than a typical PHL departure in the same hour.

On arrival at ORD, UA308 spends 25.0 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 7.1 minutes longer 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 15,182 departures from PHL scheduled in the clock hour UA308 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 UA308’s own. More on taxi time.

Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026

UA308 is scheduled out of PHL at 5:00 PM, in the 5 PM–6 PM bank. Departures from PHL in that hour arrive on time 66.8% of the time against 76.2% across the airport’s whole day — the slot alone is worth 9.5 points worse before anything about this particular flight is considered.

The two airport figures cover every departure from PHL 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 · June 2024 – July 2026 · Hours below 120 departures are not scored.

Because the same number has served different journeys, the statistics above describe only the route UA308 currently operates. Blending them would produce an average of two different flights.

Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026

Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA308 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.

• AA2095 PHL→ORD American Airlines on the same route, departs 9:19 AM, on time 82.5%
• AA1652 PHL→ORD American Airlines on the same route, departs 6:00 AM, on time 87.9%
• UA1776 ORD→PHL Return trip, ORD to PHL, departs 6:20 PM, on time 64.7%