Flight number record

UA 630

United Airlines · Chicago to Madison

Route: ORD → MSN
Departs: 21:20
Flights: 290
Period: July 2025 to June 2026

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

UA 630 draws a D. Roughly one flight in three arrives at least 15 minutes late, and the typical late arrival is about an hour behind schedule. Build slack into anything you connect to. That rests on 290 flights, with a median arrival 6 minutes late.

The national on-time rate over the same period is 77.6%, so UA 630 runs 17 points behind the country as a whole. Across a thousand flights that is about 166 extra late arrivals.

On time

61.0%

Arrivals under 15 minutes late, of 282 completed flights

Avg delay

66 min

Across delayed arrivals only, not all flights

Cancelled

2.76%

National rate is 1.81%

1 hour+ late

14.9%

National rate is 8.1%

These figures cover 290 flights between July 2025 and June 2026. Beyond the headline rate, 14.9% 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 630 flies

UA 630 flies ORD to MSN without a single fixed slot. Its most common scheduled departure was 21:20, used on 44 of 290 flights, with 20:00 (37 flights) and 19:35 (36 flights) next. Carriers retime flights through the season, so the rates here blend slightly different positions in the aircraft's day.

Departs 21:2044 flights15.2%
Departs 20:0037 flights12.8%
Departs 19:3536 flights12.4%

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 21:20 departure sits in the 8pm–5am window. Across every US flight scheduled in that window the on-time rate is 70.5%, and UA 630 runs 10 points worse at 61.0%. By that time of day most aircraft have flown several legs already, and whatever went wrong earlier is still in the schedule.

Against the route

UA 630 next to ORD to MSN

Every carrier on ORD to MSN combined arrived on time 71.4% of the time across 4,029 flights, so UA 630 is 10 points behind it. United flew 936 flights on the same city pair under all its flight numbers, including this one, and those ran 68.7% on time. Across its whole network United Airlines managed 79.0%, which this flight trails by 18 points.

UA 630 against its route and carrier
Compared with	Flights	On time	Avg delay	Cancelled	Grade
UA 630thin sample	290	61.0%	66 min	2.76%	D
All United Airlines on ORD–MSN	936	68.7%	70 min	2.03%	C
All carriers on ORD–MSN	4,029	71.4%	82 min	3.80%	C−
United Airlines, whole network	821,041	79.0%	72 min	1.01%	B

Across the year

UA 630 quarter by quarter

Quarter by quarter UA 630 held fairly steady: 62.0% in Jul–Sep 2025, 57.9% in Oct–Dec 2025, 64.2% in Jan–Mar 2026 and 59.3% in Apr–Jun 2026. A spread of 6 points is about what a sample of this size moves on its own, so the annual figure is a fair summary.

Jul–Sep 202573 flights62.0%
Oct–Dec 202577 flights57.9%
Jan–Mar 202684 flights64.2%
Apr–Jun 202656 flights59.3%

Scale runs 50% to 70%. Rows with fewer than 30 flights show a dash.

By weekday, UA 630 ranged from 56.4% on Sunday to 67.6% on Thursday. With about 41 flights behind each day, a spread of 11 points is inside normal variation, so the day you fly is not worth changing for this flight.

Delay causes

Why UA 630 runs late

One category carries most of the weight here. Late-arriving aircraft accounts for 59% of the 7,286 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.

Late-arriving aircraft
59%
Carrier
20%
National Airspace System
11%
Extreme weather
10%

59% of delay minutes trace back to a late-arriving aircraft, meaning the plane was already behind before it got here. That is a cascade, and cascades start small and grow through the day. Across 7,286 reported delay minutes here, that single category outweighs weather by 6 to one. It is the strongest argument for booking the first departure of the morning, when the aircraft has been sitting at the gate overnight with nothing to inherit. The split is drawn from 7,286 delay minutes reported on UA 630.

Cancellations run at 2.76%, against 1.81% nationally. That is roughly one flight in 40 cancelled outright. A cancelled flight is invisible in every on-time figure on this page, so the punctuality numbers above describe only the flights that actually operated.

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. 14.9% 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 same number turns up on seven other city pairs in the data, including RDU to ORD (93), BUF to ORD (72) and PHX to ORD (58), but none flew often enough under UA 630 to report a rate for. Carriers move flight numbers between routes, so the figures on this page apply to ORD to MSN only.

One caution: this is a thin sample. 290 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 630

For a booking, the cancellation rate is the figure to plan around on UA 630: 2.76% of its 290 scheduled flights did not operate. A late arrival costs about an hour, but a cancellation costs the day, so leave a later option open.

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