Flight profile · SkyWest Airlines
OO5337
Chicago (ORD) to Roanoke (ROA) · scheduled 1:55 PM – 4:59 PM
How OO5337 performs
518 operations, 2024-05-02 to 2026-06-30.
Source: US DOT Bureau of Transportation Statistics · 518 operations between 2024-05-02 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| OO5337 | 74.7% | 0.97% | -3 min | 8.3% | 518 |
| SkyWest Airlines on ORD → ROA | 75.2% | 1.38% | -4 min | 8.4% | 1,818 |
| All ORD → ROA flights | 75.3% | 2.06% | -4 min | 8.3% | 2,182 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-05-02 to 2026-06-30
Other routes OO5337 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 |
|---|---|---|---|
| ORD→CLE Chicago to Cleveland | 2026-04-30 – 2026-05-20 | 20 | — |
| ORD→ICT Chicago to Wichita | 2026-05-03 – 2026-05-03 | 1 | — |
| IAH→SHV Houston to Shreveport | 2026-01-06 – 2026-03-28 | 82 | — |
| ORD→DAY Chicago to Dayton | 2025-12-02 – 2025-12-17 | 14 | — |
| LAX→SFO Los Angeles to San Francisco | 2025-08-02 – 2025-08-16 | 3 | — |
| ORD→CHA Chicago to Chattanooga | 2025-05-24 – 2025-06-25 | 15 | — |
| OKC→IAH Oklahoma City to Houston | 2025-05-01 – 2025-05-21 | 21 | — |
| BUR→SFO Burbank to San Francisco | 2025-03-30 – 2025-04-30 | 28 | — |
| SAN→SFO San Diego to San Francisco | 2025-04-05 – 2025-04-26 | 4 | — |
| SFO→ONT San Francisco to Ontario | 2023-07-01 – 2025-03-29 | 41 | — |
| IAH→SAT Houston to San Antonio | 2025-03-06 – 2025-03-28 | 23 | — |
| SUN→SFO Hailey to San Francisco | 2025-02-15 – 2025-03-02 | 6 | — |
| GSP→ORD Greenville/Greer/Spartanburg to Chicago | 2025-02-12 – 2025-02-12 | 1 | — |
| ORD→GSP Chicago to Greenville/Greer/Spartanburg | 2024-03-31 – 2024-05-01 | 32 | — |
| IAH→BRO Houston to Brownsville | 2024-03-07 – 2024-03-30 | 18 | — |
| BUF→ORD Buffalo to Chicago | 2024-02-15 – 2024-03-06 | 15 | — |
| ORD→PIT Chicago to Pittsburgh | 2024-02-17 – 2024-03-03 | 6 | — |
| ORD→BNA Chicago to Nashville | 2024-01-13 – 2024-02-10 | 5 | — |
| SFO→FCA San Francisco to Kalispell | 2023-12-23 – 2024-01-07 | 6 | — |
| MAF→IAH Midland to Houston | 2023-12-01 – 2023-12-19 | 14 | — |
| SLC→SFO Salt Lake City to San Francisco | 2023-11-01 – 2023-11-30 | 30 | — |
| PSC→SFO Pasco to San Francisco | 2023-09-29 – 2023-10-28 | 29 | — |
| MCI→SFO Kansas City to San Francisco | 2023-10-21 – 2023-10-21 | 1 | — |
| ORD→SDF Chicago to Louisville | 2023-09-05 – 2023-09-28 | 24 | — |
Because the same number has served different journeys, the statistics above describe only the route OO5337 currently operates. Blending them would produce an average of two different flights.
Why OO5337 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding, fuelling — within the carrier’s control
the inbound aircraft was late, so this flight started late
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 OO5337 on ORD → ROA. A single late flight can carry more than one cause, and only delays of fifteen minutes or more are attributed at all.
Other departures on ORD → ROA
Same airports, same journey — and not the same odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| OO4792 | SkyWest Airlines | 75.9% | 5 min early | 710 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. Schedules change; confirm the departure still operates before booking around this.
Data and methodology
Calculated by FlyerIntel from 518 records of OO5337 operating ORD → ROA, 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