Flight profile · SkyWest Airlines
OO3715
Detroit (DTW) to Omaha (OMA) · scheduled 7:45 PM – 8:54 PM
How OO3715 performs
617 operations, June 2024 – July 2026.
OO3715 arrived on time 71.3% of the time, against 78.2% for all DTW → OMA flights, so this departure is 6.9 percentage points worse than the route as a whole. Against SkyWest Airlines’ own flights on this route it is 6.0 points worse.
Source: US DOT Bureau of Transportation Statistics · 617 operations, June 2024 – July 2026 · If OO3715 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where OO3715 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 OO3715 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 |
|---|---|---|---|---|---|
| OO3715 | 71.3% | 0.81% | -1 min | 12.2% | 617 |
| SkyWest Airlines on DTW → OMA | 77.3% | 0.54% | -5 min | 9.9% | 3,154 |
| All DTW → OMA flights | 78.2% | 0.51% | -5 min | 9.4% | 3,326 |
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
Why OO3715 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding and fueling, all within the carrier’s control
weather severe enough to stop this flight specifically
airspace and airport capacity, including weather-driven flow control
Share of the delay minutes US DOT attributed to each cause for OO3715 on DTW → OMA. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies OO3715 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, OO3715 pushed back an average of 62 minutes late; when it came in on time or early, an average of 6 minutes late.
Each departure is matched to the flight the same aircraft flew into DTW just before it, using the tail number in the DOT file, 582 of 613 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 |
|---|---|---|---|
| OO3715 | 24% | 70% | 12% |
| Network, same turn | 18% | 85% | 10% |
The schedule leaves a normal turn: enough time to clean and board if the aircraft is on time, little to spare if it is not.
The network row is every flight with a scheduled turn of 45 to 59 minutes. How often OO3715’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often OO3715 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 June 2024 – July 2026
From pushback to gate
When it leaves DTW late, does that still matter by the time it reaches OMA?
OO3715 pushes back an average of 22.3 minutes late and reaches the gate at OMA an average of 20.4 minutes late. The 2.0 minutes between those two figures are slack the published schedule already carries, which is why a late pushback on this flight does not reliably become a late arrival. It spends 21.3 minutes on the taxiways at DTW, 3.5 minutes longer than a typical DTW departure in the same hour.
On arrival at OMA, OO3715 spends 5.6 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 about what any arrival at OMA spends on the ground before reaching the gate.
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 OMA. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 15,218 departures from DTW scheduled in the clock hour OO3715 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at OMA (75,011 flights), not just OO3715’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
The hour it leaves DTW
Part of any flight’s record belongs to the clock rather than to the flight. OO3715 has one departure time, so this is what that time is worth.
On-time arrival rate. 15,218 departures from DTW are scheduled in the 7 PM–8 PM hour over the period, against 388,632 across the whole day.
OO3715 is scheduled out of DTW at 7:45 PM, in the 7 PM–8 PM bank. Departures from DTW in that hour arrive on time 70.7% of the time against 79.6% across the airport’s whole day — the slot alone is worth 8.9 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from DTW 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 · June 2024 – July 2026 · Hours below 120 departures are not scored.
Other routes OO3715 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 |
|---|---|---|---|
| DTW→PWM Detroit to Portland | May 3, 2026 | 1 | — |
| PWM→DTW Portland to Detroit | May 3, 2026 | 1 | — |
| DTW→ROC Detroit to Rochester | April 6, 2024 – December 19, 2025 | 36 | — |
| ROC→DTW Rochester to Detroit | November 9, 2025 – December 19, 2025 | 35 | — |
| MSN→DTW Madison to Detroit | July 12, 2025 – August 9, 2025 | 5 | — |
| MCI→MSP Kansas City to Minneapolis | May 10, 2025 – June 7, 2025 | 6 | — |
| MSP→MCI Minneapolis to Kansas City | May 10, 2025 – June 7, 2025 | 6 | — |
| SJC→SLC San Jose to Salt Lake City | December 19, 2024 – January 5, 2025 | 14 | — |
| SLC→SJC Salt Lake City to San Jose | December 19, 2024 – January 5, 2025 | 14 | — |
| ATL→XNA Atlanta to Fayetteville/Springdale/Rogers | November 9, 2024 | 1 | — |
| JFK→ORD New York to Chicago | May 7, 2024 – June 6, 2024 | 31 | — |
| ORD→JFK Chicago to New York | May 7, 2024 – June 6, 2024 | 31 | — |
| LGA→MKE New York to Milwaukee | April 9, 2024 – May 6, 2024 | 28 | — |
| LGA→SDF New York to Louisville | March 10, 2024 – April 8, 2024 | 26 | — |
| MSP→CMH Minneapolis to Columbus | September 10, 2023 – March 8, 2024 | 110 | 87.3% |
| CMH→MSP Columbus to Minneapolis | December 7, 2023 – March 8, 2024 | 59 | — |
| AGS→ATL Augusta to Atlanta | December 17, 2023 – January 1, 2024 | 16 | — |
| ATL→AGS Atlanta to Augusta | December 17, 2023 – January 1, 2024 | 16 | — |
| EUG→SLC Eugene to Salt Lake City | October 28, 2023 – November 4, 2023 | 8 | — |
| GRR→MSP Grand Rapids to Minneapolis | September 9–30, 2023 | 2 | — |
| MSP→GRR Minneapolis to Grand Rapids | September 9–30, 2023 | 2 | — |
| IDA→SLC Idaho Falls to Salt Lake City | September 5–8, 2023 | 4 | — |
| LAX→RNO Los Angeles to Reno | July 1, 2023 – September 4, 2023 | 66 | — |
Because the same number has served different journeys, the statistics above describe only the route OO3715 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.
75 min late
against a median of 1 min early
OO3715 has an average that understates its risk: a typical arrival is 1 min early, but the worst tenth are 76 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 617 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026
Other flights on this route
Same airports, same journey, different odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| OO4055 | SkyWest Airlines | 81.5% | 8 min early | 648 |
| OO3889 | SkyWest Airlines | 74.9% | 4 min early | 677 |
| OO3715 this flight | SkyWest Airlines | 71.3% | 1 min early | 617 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. OO3715 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 617 records of OO3715 operating DTW → OMA, 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