Flight profile · United Airlines

UA1673

Cleveland (CLE) to Chicago (ORD) · scheduled 6:00 PM – 6:26 PM

This page describes how UA1673 has historically performed, which is a different and more useful question when you are deciding what to book. The live position below is a reading from receivers on the ground, not flight status. For today’s status, check with United Airlines.

How UA1673 performs

860 operations, January 2024 – July 2026.

On-time arrivals
60.6%
511 of 843 completed
Cancellation rate
1.98%
17 cancelled
Median arrival delay
7 min
Average 24.0 min
Severe delays
12.0%
Arrived 60+ minutes late
Delay when late
67 min
Average, when 15+ min late
Departure punctuality
78.8%
Left the gate on time

UA1673 arrived on time 60.6% of the time, against 80.0% for all CLE → ORD flights, so this departure is 19.4 percentage points worse than the route as a whole. Against United Airlines’ own flights on this route it is 22.3 points worse.

Source: US DOT Bureau of Transportation Statistics · 860 operations, January 2024 – July 2026 · If UA1673 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 UA1673 compares to other flight numbers, not just to itself.

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

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

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

Where UA1673 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 UA1673 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.

Against the rest of the route

Against the rest of the route
Flight or routeOn timeCancelledMedian delaySevereFlights
UA167360.6%1.98%7 min12.0%860
United Airlines on CLE → ORD82.9%1.19%-7 min5.8%6,065
All CLE → ORD flights80.0%2.28%-7 min7.8%11,745

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

Why UA1673 runs late

Where US DOT attributed the delay minutes on this flight.

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

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

Does a late aircraft delay this flight?

How often the plane that flies UA1673 comes in late, and what that does to the departure.

Inbound aircraft late
19%
157 of 821 departures came in 15+ minutes late
Scheduled time on the ground
66 minutes
Median at CLE between the inbound and this departure
Left 15+ late after a late inbound
76%
157 departures
Left 15+ late after an on-time inbound
8%
664 departures

When the aircraft came in 15 or more minutes late, UA1673 pushed back an average of 65 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 CLE just before it, using the tail number in the DOT file, 821 of 844 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

UA1673 against all flights with a scheduled turn of 60 to 89 minutes
Share of departuresInbound landed 15+ lateLeft 15+ late after a late inboundLeft 15+ late after an on-time inbound
UA167319%76%8%
Network, same turn17%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 UA1673’s aircraft landed 15 or more minutes late is about the same as the network’s and, once the aircraft was late, how often UA1673 left 15 or more minutes late is higher 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 January 2024 – July 2026

From pushback to gate

When it leaves CLE late, does that still matter by the time it reaches ORD?

Leaves the gate
16.4 minutes late
Average over 844 pushbacks
Taxi out at CLE
17.4 min
16.0 min for the airport in this hour
Taxi in at ORD
26.0 min
17.8 min for a typical ORD arrival
Reaches the gate at ORD
24.0 minutes late
Average over 843 arrivals

UA1673 pushes back an average of 16.4 minutes late and arrives a further 7.6 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 17.4 minutes on the taxiways at CLE, 1.3 minutes longer than a typical CLE departure in the same hour.

On arrival at ORD, UA1673 spends 26.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 8.2 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 7,272 departures from CLE scheduled in the clock hour UA1673 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 UA1673’s own. More on taxi time.

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

The hour it leaves CLE

Part of any flight’s record belongs to the clock rather than to the flight. UA1673 has one departure time, so this is what that time is worth.

UA167360.6%
All CLE departures, 6 PM–7 PM69.4%
All CLE departures, whole day80.9%

On-time arrival rate. 7,272 departures from CLE are scheduled in the 6 PM–7 PM hour over the period, against 126,883 across the whole day.

UA1673 is scheduled out of CLE at 6:00 PM, in the 6 PM–7 PM bank. Departures from CLE in that hour arrive on time 69.4% of the time against 80.9% across the airport’s whole day — the slot alone is worth 11.5 points worse before anything about this particular flight is considered.

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

By day of week

Does UA1673 run worse on particular days?

Monday65.6%
Tuesday58.5%
Wednesday56.5%
Thursday57.9%
Friday63.3%
Saturday—
Sunday51.2%

Monday is historically the most reliable day and Sunday the least, a gap of 14.4 percentage points.

Source: FlyerIntel analysis of US DOT BTS data · January 2024 – July 2026 · Days with fewer than 120 operations are not scored.

Other routes UA1673 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.

Other routes UA1673 has flown
RouteOperatedFlightsOn time
ORD→DFW Chicago to Dallas–Fort WorthMarch 31, 2024 – July 31, 202638460.5%
IAD→CLE Washington to ClevelandMarch 29, 2026 – April 29, 202627—
EWR→CLE Newark to ClevelandOctober 26, 2025 – December 17, 202546—
ORD→SFO Chicago to San FranciscoOctober 28, 2023 – November 15, 20254—
PIT→ORD Pittsburgh to ChicagoSeptember 25, 2025 – October 24, 202526—
SFO→CLE San Francisco to ClevelandAugust 19, 2025 – September 24, 202537—
ORD→SNA Chicago to Santa AnaJuly 2, 2023 – July 31, 202517091.5%
ORD→PDX Chicago to PortlandMay 22, 2025 – June 25, 202535—
ORD→LAX Chicago to Los AngelesMay 1–21, 202521—
RSW→CLE Fort Myers to ClevelandDecember 19, 2024 – January 6, 202519—
ORD→MSY Chicago to New OrleansOctober 27, 2024 – December 2, 202435—
ORD→LGA Chicago to New YorkSeptember 26, 2024 – October 26, 202431—
IAH→CLE Houston to ClevelandSeptember 26, 2024 – October 26, 202426—
BNA→ORD Nashville to ChicagoNovember 28, 2023 – December 20, 202320—
ORD→JAX Chicago to JacksonvilleOctober 29, 2023 – November 27, 202328—
MSN→ORD Madison to ChicagoJuly 2–31, 202324—

Because the same number has served different journeys, the statistics above describe only the route UA1673 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.

One arrival in ten is worse than

74 min late

against a median of 7 min late

Arrived an hour or more late12.0%
Typical delay when late67 min
Cancelled1.98%
Landed somewhere else0.00%

UA1673 has an average that understates its risk: a typical arrival is 7 min late, but the worst tenth are 67 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 860 operations; cancelled and diverted flights are counted separately.

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

Other flights on this route

Same airports, same journey, different odds of arriving on time.

Other flights on this route
FlightAirlineOn timeMedian arrivalOperations
UA609United Airlines90.0%12 min early826
UA1673 this flightUnited Airlines60.6%7 min late860

Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA1673 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 860 records of UA1673 operating CLE → 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