Flight profile · Envoy Air
MQ3913
Chicago (ORD) to Wichita (ICT) · scheduled 8:41 PM – 10:19 PM
How MQ3913 performs
166 operations, 2024-06-05 to 2026-06-30.
MQ3913 arrived on time 57.3% of the time, against 69.4% for all ORD → ICT flights — this specific departure is 12.1 percentage points worse than the route as a whole. Against Envoy Air’s own flights on this route it is 14.3 points worse.
Source: US DOT Bureau of Transportation Statistics · 166 operations between 2024-06-05 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| MQ3913 | 57.3% | 4.82% | 10 min | 19.1% | 166 |
| Envoy Air on ORD → ICT | 71.7% | 2.12% | -2 min | 11.1% | 1,603 |
| All ORD → ICT flights | 69.4% | 1.93% | -1 min | 11.9% | 5,395 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-06-05 to 2026-06-30
Other routes MQ3913 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 |
|---|---|---|---|
| CLT→SGF Charlotte to Springfield | 2023-11-05 – 2026-04-06 | 376 | 68.6% |
| TUL→DFW Tulsa to Dallas–Fort Worth | 2026-01-08 – 2026-02-09 | 15 | — |
| SGF→DFW Springfield to Dallas–Fort Worth | 2025-10-06 – 2025-11-01 | 27 | — |
| DFW→SGF Dallas–Fort Worth to Springfield | 2025-10-06 – 2025-11-01 | 26 | — |
| BNA→DFW Nashville to Dallas–Fort Worth | 2025-09-07 – 2025-10-05 | 9 | — |
| OMA→PHX Omaha to Phoenix | 2025-08-06 – 2025-09-02 | 24 | — |
| PHX→OMA Phoenix to Omaha | 2025-08-06 – 2025-09-02 | 23 | — |
| DFW→SAT Dallas–Fort Worth to San Antonio | 2025-08-09 – 2025-08-30 | 4 | — |
| SAT→DFW San Antonio to Dallas–Fort Worth | 2025-08-09 – 2025-08-30 | 4 | — |
| DFW→CHA Dallas–Fort Worth to Chattanooga | 2024-09-04 – 2024-11-04 | 62 | — |
| DFW→MAF Dallas–Fort Worth to Midland | 2024-05-06 – 2024-06-04 | 30 | — |
| MAF→DFW Midland to Dallas–Fort Worth | 2024-05-06 – 2024-06-04 | 30 | — |
| DFW→AUS Dallas–Fort Worth to Austin | 2024-04-04 – 2024-05-05 | 32 | — |
| PHX→SEA Phoenix to Seattle | 2023-10-05 – 2023-11-04 | 31 | — |
| SEA→PHX Seattle to Phoenix | 2023-10-05 – 2023-11-04 | 31 | — |
| DFW→IAH Dallas–Fort Worth to Houston | 2023-09-06 – 2023-10-04 | 5 | — |
| IAH→DFW Houston to Dallas–Fort Worth | 2023-09-06 – 2023-10-04 | 5 | — |
| DFW→MEM Dallas–Fort Worth to Memphis | 2023-09-09 – 2023-09-30 | 4 | — |
| DFW→PNS Dallas–Fort Worth to Pensacola | 2023-07-01 – 2023-09-05 | 63 | — |
| PNS→DFW Pensacola to Dallas–Fort Worth | 2023-07-01 – 2023-09-05 | 63 | — |
Because the same number has served different journeys, the statistics above describe only the route MQ3913 currently operates. Blending them would produce an average of two different flights.
Why MQ3913 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 MQ3913 on ORD → ICT. 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 → ICT
Same airports, same journey — and not the same odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| OO4809 | SkyWest Airlines | 80.0% | 6 min early | 1,031 |
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 166 records of MQ3913 operating ORD → ICT, 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