Flight number record

UA 2202

United Airlines · Bozeman to Chicago

Route: BZN → ORD
Departs: 12:48
Flights: 279
Period: July 2025 to June 2026

Historical statistics for July 2025 to June 2026, not live status. For today’s UA 2202, check with United Airlines.

UA 2202 lands a B+, about a point worse than the national rate of 77.6%. About one flight in four arrives 15 minutes late or worse, and those flights are late by an hour and a half on average. That is a workable record, not a spotless one. That rests on 279 flights, with a median arrival 5 minutes early.

On time

76.5%

Arrivals under 15 minutes late, of 277 completed flights

Avg delay

98 min

Across delayed arrivals only, not all flights

Cancelled

0.72%

National rate is 1.81%

1 hour+ late

10.8%

National rate is 8.1%

These figures cover 279 flights between July 2025 and June 2026. Beyond the headline rate, 10.8% of arrivals land a full hour or more behind schedule. That is the number that wrecks a connection, and it is not visible in an on-time percentage alone.

Schedule

When UA 2202 flies

UA 2202 flies BZN to ORD without a single fixed slot. Its most common scheduled departure was 12:48, used on 56 of 279 flights, with 12:50 (50 flights) and 12:45 (37 flights) next. Carriers retime flights through the season, so the rates here blend slightly different positions in the aircraft's day.

Departs 12:4856 flights20.1%
Departs 12:5050 flights17.9%
Departs 12:4537 flights13.3%

Scale runs 0% to 100%. Rows with fewer than 30 flights show a dash.

Share of scheduled departures at each local time. Times used on fewer than one flight in ten are not listed.

A 12:48 departure sits in the 11am–2pm window. Across every US flight scheduled in that window the on-time rate is 78.8%, and UA 2202 runs 2 points worse at 76.5%. Midday slots inherit some of the morning's delays without yet carrying the full weight of the evening's.

Against the route

UA 2202 next to BZN to ORD

Every carrier on BZN to ORD combined arrived on time 73.5% of the time across 1,255 flights, so UA 2202 is 3 points ahead of it. United flew 658 flights on the same city pair under all its flight numbers, including this one, and those ran 79.7% on time. Across its whole network United Airlines managed 79.0%, which this flight trails by 3 points.

UA 2202 against its route and carrier
Compared with	Flights	On time	Avg delay	Cancelled	Grade
UA 2202thin sample	279	76.5%	98 min	0.72%	B+
All United Airlines on BZN–ORD	658	79.7%	79 min	1.52%	B
All carriers on BZN–ORD	1,255	73.5%	90 min	1.04%	C
United Airlines, whole network	821,041	79.0%	72 min	1.01%	B

Across the year

UA 2202 quarter by quarter

Quarter by quarter UA 2202 held fairly steady: 75.0% in Oct–Dec 2025, 77.8% in Jan–Mar 2026 and 75.3% in Apr–Jun 2026. A spread of 3 points is about what a sample of this size moves on its own, so the annual figure is a fair summary.

Jul–Sep 20256 flights—
Oct–Dec 202592 flights75.0%
Jan–Mar 202690 flights77.8%
Apr–Jun 202691 flights75.3%

Scale runs 65% to 85%. Rows with fewer than 30 flights show a dash.

By weekday, UA 2202 did best on Tuesday at 90.0% on time and worst on Wednesday at 69.2%. Each day rests on about 40 flights, so a gap of 21 points is worth noticing but could still narrow in another year.

Delay causes

Why UA 2202 runs late

One category carries most of the weight here. National Airspace System accounts for 44% of the 6,342 delay minutes carriers reported, and the remaining four split what is left. The split is by minutes rather than by flights, so a few very long delays count for as much as many short ones.

National Airspace System
44%
Late-arriving aircraft
32%
Carrier
24%
Extreme weather
0%

44% of delay minutes are charged to the National Airspace System: air traffic volume, runway configuration, ground stops. No carrier can price its way out of that, which is why airport choice moves the number here more than carrier choice does. That is 2,786 minutes out of 6,342, against a national NAS share of 21%. The split is drawn from 6,342 delay minutes reported on UA 2202.

Cancellations are rare at 0.72%, below the national 1.81% and low enough to earn the plus on the grade. Roughly one flight in 100 is called off; the risk here is arriving late, not not arriving.

Connections and routes

What a delay on this flight costs

For anyone connecting, the number to weigh is not the on-time rate but the tail behind it. 10.8% of arrivals land a full hour or more behind schedule, against 8.1% nationally. A 45-minute layover does not survive that, and no amount of walking quickly changes it. Ninety minutes is the honest minimum here, and two hours if the onward flight is on a separate ticket.

The 1,185 miles between these two airports put this in the middle of the US network, around two and a half to three hours of block time. That is enough cruise to absorb a ten-minute late pushback and not enough to absorb thirty. It is also long enough that the aircraft usually flies three or four legs a day rather than six, which slows how fast delay compounds.

The same number turns up on six other city pairs in the data, including ORD to IAD (62), ORD to IAH (49) and ORD to CLT (43), but none flew often enough under UA 2202 to report a rate for. Carriers move flight numbers between routes, so the figures on this page apply to BZN to ORD only.

One caution: this is a thin sample. 279 flights over twelve months is enough to clear this site's floor but not enough to pin the rate down tightly, and a single bad week moves it by more than a point. Treat the grade as a rough reading.

What to do with this

Booking UA 2202

For a booking, read UA 2202 as 76.5% on time with 0.72% cancelled over 279 flights. Those are rates from the past twelve months, not a forecast for any particular day.

Where to go next

A flight number here means United Airlines’s own number as it reports to the DOT. How the figures are computed is on the methodology page.

Source: US DOT Bureau of Transportation Statistics, on-time performance data, July 2025 to June 2026. Last updated 15 September 2026; recomputed monthly. How this data is collected.

Key figures