Flight profile · United Airlines
UA630
Chicago (ORD) to Madison (MSN) · scheduled 9:20 PM – 9:05 PM
How UA630 performs
315 operations, 2025-05-01 to 2026-06-30.
UA630 arrived on time 60.9% of the time, against 73.8% for all ORD → MSN flights — this specific departure is 12.9 percentage points worse than the route as a whole. Against United Airlines’s own flights on this route it is 8.7 points worse.
Source: US DOT Bureau of Transportation Statistics · 315 operations between 2025-05-01 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| UA630 | 60.9% | 2.54% | 6 min | 15.0% | 315 |
| United Airlines on ORD → MSN | 69.6% | 1.51% | 0 min | 11.5% | 1,985 |
| All ORD → MSN flights | 73.8% | 2.47% | -4 min | 10.6% | 8,585 |
Source: FlyerIntel analysis of US DOT BTS data · 2025-05-01 to 2026-06-30
Other routes UA630 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.
| Route | Operated | Flights | On time |
|---|---|---|---|
| RDU→ORD Raleigh–Durham to Chicago | 2026-03-05 – 2026-06-30 | 93 | 48.9% |
| ORD→PDX Chicago to Portland | 2026-05-21 – 2026-06-24 | 35 | — |
| SFO→RDU San Francisco to Raleigh–Durham | 2026-03-29 – 2026-04-29 | 32 | — |
| PHX→ORD Phoenix to Chicago | 2026-01-06 – 2026-03-04 | 58 | — |
| GTF→DEN Great Falls to Denver | 2025-12-18 – 2026-01-05 | 19 | — |
| PBI→ORD West Palm Beach to Chicago | 2025-10-26 – 2025-12-17 | 52 | — |
| BUF→ORD Buffalo to Chicago | 2023-07-01 – 2025-10-24 | 542 | 56.7% |
| ORD→SAN Chicago to San Diego | 2025-05-22 – 2025-06-25 | 34 | — |
| ORD→FSD Chicago to Sioux Falls | 2025-03-06 – 2025-04-30 | 56 | — |
| ORD→DSM Chicago to Des Moines | 2024-08-19 – 2025-02-12 | 161 | 68.6% |
| ORD→SEA Chicago to Seattle | 2024-05-23 – 2024-08-18 | 88 | — |
| PWM→ORD Portland to Chicago | 2024-07-05 – 2024-07-26 | 4 | — |
| IAD→MIA Washington to Miami | 2024-03-31 – 2024-05-22 | 53 | — |
| ORD→IND Chicago to Indianapolis | 2024-03-08 – 2024-03-29 | 4 | — |
| ORD→RDU Chicago to Raleigh–Durham | 2024-03-07 – 2024-03-07 | 1 | — |
| FLL→ORD Fort Lauderdale to Chicago | 2023-10-29 – 2024-01-08 | 69 | — |
| IAH→BTR Houston to Baton Rouge | 2023-09-24 – 2023-09-24 | 1 | — |
Because the same number has served different journeys, the statistics above describe only the route UA630 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.
69 min late
against a median of 6 min late
UA630 is a flight whose average understates its risk: a typical day arrives 6 min late, but the worst tenth of days are 63 minutes worse than that. If the day has something unmissable in it, the median is the wrong number to plan against.
Percentiles over 315 operations. Cancelled and diverted flights have no arrival time and are counted separately rather than as very late arrivals.
Why UA630 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding, fuelling — within the carrier’s control
airspace and airport capacity, including weather-driven flow control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for UA630 on ORD → MSN. A single late flight can carry more than one cause, and only delays of fifteen minutes or more are attributed at all.
Data and methodology
Calculated by FlyerIntel from 315 records of UA630 operating ORD → MSN, 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 · Report a problem
Analysis last recomputed