Flight profile · SkyWest Airlines
OO5648
Milwaukee (MKE) to Chicago (ORD) · scheduled 5:46 PM – 6:55 PM
How OO5648 performs
894 operations, July 2023 – July 2026.
OO5648 arrived on time 58.3% of the time, against 72.4% for all MKE → ORD flights, so this departure is 14.1 percentage points worse than the route as a whole. Against SkyWest Airlines’ own flights on this route it is 13.8 points worse.
Source: US DOT Bureau of Transportation Statistics · 894 operations, July 2023 – July 2026 · If OO5648 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 OO5648 compares to other flight numbers, not just to itself.
Which day you fly matters unusually much here, a wider weekday spread than 96% of 1,710 comparable flight numbers.
68.5% on time on a typical Saturday, against 48.8% on a Friday.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – 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 OO5648 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 OO5648 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.
Against the rest of the route
| Flight or route | On time | Cancelled | Median delay | Severe | Flights |
|---|---|---|---|---|---|
| OO5648 | 58.3% | 3.36% | 9 min | 15.6% | 894 |
| SkyWest Airlines on MKE → ORD | 72.1% | 2.78% | -3 min | 12.5% | 10,528 |
| All MKE → ORD flights | 72.4% | 2.91% | -3 min | 12.3% | 11,098 |
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
Why OO5648 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 and fueling, all 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 OO5648 on MKE → ORD. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies OO5648 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, OO5648 pushed back an average of 64 minutes late; when it came in on time or early, an average of 1 minute early.
Each departure is matched to the flight the same aircraft flew into MKE just before it, using the tail number in the DOT file, 827 of 864 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
| Share of departures | Inbound landed 15+ late | Left 15+ late after a late inbound | Left 15+ late after an on-time inbound |
|---|---|---|---|
| OO5648 | 29% | 75% | 7% |
| Network, same turn | 18% | 92% | 12% |
The schedule leaves little slack between the inbound landing and this departure, so a late arrival has almost nowhere to go but into the departure.
The network row is every flight with a scheduled turn of 30 to 44 minutes. How often OO5648’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often OO5648 left 15 or more minutes late is lower 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 July 2023 – July 2026
From pushback to gate
When it leaves MKE late, does that still matter by the time it reaches ORD?
OO5648 pushes back an average of 20.5 minutes late and arrives a further 7.1 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 20.6 minutes on the taxiways at MKE, 5.4 minutes longer than a typical MKE departure in the same hour.
On arrival at ORD, OO5648 spends 27.3 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 9.5 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,399 departures from MKE scheduled in the clock hour OO5648 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 OO5648’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
The hour it leaves MKE
Part of any flight’s record belongs to the clock rather than to the flight. OO5648 has one departure time, so this is what that time is worth.
On-time arrival rate. 7,399 departures from MKE are scheduled in the 5 PM–6 PM hour over the period, against 87,869 across the whole day.
OO5648 is scheduled out of MKE at 5:46 PM, in the 5 PM–6 PM bank. Departures from MKE in that hour arrive on time 70.3% of the time against 80.7% across the airport’s whole day — the slot alone is worth 10.5 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from MKE 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 · July 2023 – July 2026 · Hours below 120 departures are not scored.
By day of week
Does OO5648 run worse on particular days?
Saturday is historically the most reliable day and Friday the least, a gap of 19.7 percentage points.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Days with fewer than 120 operations are not scored.
Other routes OO5648 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 |
|---|---|---|---|
| RDM→SFO Redmond to San Francisco | May 6–20, 2026 | 3 | — |
| SAF→DEN Santa Fe to Denver | February 12, 2026 – March 28, 2026 | 45 | — |
| SBN→ORD South Bend to Chicago | January 6, 2026 – February 11, 2026 | 37 | — |
| SFO→OMA San Francisco to Omaha | May 5, 2024 | 1 | — |
| CVG→ORD Cincinnati / Covington to Chicago | April 15–22, 2024 | 2 | — |
Because the same number has served different journeys, the statistics above describe only the route OO5648 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.
99 min late
against a median of 9 min late
OO5648 has an average that understates its risk: a typical arrival is 9 min late, but the worst tenth are 90 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 894 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026
Other flights on this route
Same airports, same journey, different odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| OO5799 | SkyWest Airlines | 85.5% | 19 min early | 718 |
| OO4803 | SkyWest Airlines | 81.1% | 6 min early | 1,001 |
| OO5402 | SkyWest Airlines | 74.7% | 1 min early | 1,058 |
| OO4740 | SkyWest Airlines | 74.1% | 1 min early | 960 |
| OO5648 this flight | SkyWest Airlines | 58.3% | 9 min late | 894 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. OO5648 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 894 records of OO5648 operating MKE → 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