Skip to content
DelayAtlas

Flight number record

UA 2202

United Airlines · Bozeman to Chicago

Route
BZN → ORD
Departs
12:48
Flights
341
Period
September 2025 to August 2026
B+GRADE

Historical statistics for September 2025 to August 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.3%. 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 rests on 341 flights, with a median arrival 4 minutes early.

Key figures

On time

76.3%

Arrivals under 15 minutes late, of 337 completed flights

Avg delay

98 min

Across delayed arrivals only, not all flights

Cancelled

0.59%

National rate is 1.89%

1 hour+ late

11.6%

National rate is 8.3%

These figures cover 341 flights between September 2025 and August 2026. Beyond the headline rate, 11.6% of arrivals land a full hour or more behind schedule, against 8.3% nationally.

Fare search by Aviasales, a Travelpayouts partner. Booking through it may earn this site a commission at no cost to you; it changes no figure here.

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 97 of 341 flights, with 12:50 (50 flights) and 12:45 (37 flights) next.

  • Departs 12:4897 flights28.4%
  • Departs 12:5050 flights14.7%
  • Departs 12:4537 flights10.9%

Scale runs 0% to 100%.

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.3%, and UA 2202 runs 2 points worse at 76.3%. Midday slots inherit some of the morning's delays without yet carrying the full weight of the evening's.

Timetable by Aviasales, a Travelpayouts partner. Booking through it may earn this site a commission at no cost to you; it changes no figure here.

Against the route

UA 2202 next to BZN to ORD

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

UA 2202 against its route and carrier
Compared withFlightsOn timeAvg delayCancelledGrade
UA 2202thin sample34176.3%98 min0.59%B+
All United Airlines on BZN–ORD72077.6%91 min0.97%B+
All carriers on BZN–ORD1,25173.2%88 min0.88%C+
United Airlines, whole network830,82578.8%73 min1.02%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, 75.3% in Apr–Jun 2026 and 75.0% in Jul–Sep 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%
  • Jul–Sep 202662 flights75.0%

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

By weekday, UA 2202 did best on Tuesday at 87.5% on time and worst on Sunday at 67.3%. Each day rests on about 49 flights, so a gap of 20 points is worth noticing but could still narrow in another year.

On-time rate by day of the week79.2Mon87.5Tue70.8Wed79.6Thu77.1Fri72.3Sat67.3Sun
Monday: 79.2 percent on time. Tuesday: 87.5 percent on time. Wednesday: 70.8 percent on time. Thursday: 79.6 percent on time. Friday: 77.1 percent on time. Saturday: 72.3 percent on time. Sunday: 67.3 percent on time

Arrival by arrival

How late UA 2202 runs when it is late

UA 2202 often beats the schedule: 88 of 337 completed flights, 26%, arrived 15 minutes or more early. The 80 late arrivals split 23 under half an hour, 18 between 30 and 60 minutes, and 39 an hour or more.

  • 15+ min early88 flights26.1%
  • Within 15 min169 flights50.1%
  • 15–29 min late23 flights6.8%
  • 30–59 min late18 flights5.3%
  • 1–2 hours late17 flights5.0%
  • 2+ hours late22 flights6.5%

Scale runs 0% to 100%.

Share of 337 completed flights by arrival against schedule.

22 of 80 late departures made up the time and arrived on time, 28% of them. In the other direction, 22 flights left on time yet arrived 15 minutes late or more, so that delay built up after pushback: in the air, in a holding pattern or on the ground at ORD.

The worst days

Worst days for UA 2202

The latest arrival of the period was on 11 June 2026, 18 hours 39 minutes behind schedule; most of its delay minutes were filed as carrier-caused (crew, maintenance, fuelling, baggage). On three of the five worst days the largest share was filed as national airspace system delay.

The latest arrivals of UA 2202 in the period
DateArrived late byLargest filed cause
11 June 202618 hours 39 minutesCarrier
15 March 20265 hours 29 minutesNational Airspace System
7 December 20255 hours 10 minutesLate-arriving aircraft
29 November 20255 hours 5 minutesNational Airspace System
27 July 20264 hours 48 minutesNational Airspace System

Delay causes

Why UA 2202 runs late

National Airspace System accounts for 49% of the 7,799 delay minutes carriers reported here, and the remaining four split what is left.

  • National Airspace System
    49%
  • Late-arriving aircraft
    29%
  • Carrier
    22%
  • Extreme weather
    0%

49% 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 3,848 minutes out of 7,799, against a national NAS share of 21%. The split is drawn from 7,799 delay minutes reported on UA 2202.

Cancellations are rare at 0.59%, below the national 1.89% 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

11.6% of arrivals land a full hour or more behind schedule, against 8.3% nationally. Ninety minutes is the honest minimum for a connection 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.

The same number turns up on four other city pairs in the data, including ORD to IAD (124), ORD to BWI (35) and ORD to CLT (30), 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. 341 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.3% on time with 0.59% cancelled over 341 flights. Those are rates from the past twelve months, not a forecast for any particular day.

Related

Where to go next

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