The sector is held by Southwest Airlines.
Airport pair · hand carry reference
MCI Kansas City to MDW Chicago
Kansas City International, the United States, to Midway International, the United States. Computed from the scheduled network held on 2026-09-07.
- Nonstop
- 6.9 times a day
- Great circle
- 650 km
- Block, estimated
- 1h 27m
- Door to door
- 8h 12m
What MCI to MDW looks like
The MCI to MDW sector, the carriers on it and the flying time, before anything is promised to anybody.
Kansas City MCI to Chicago MDW is a short sector of 650 km by great circle, flown nonstop 6.9 times a day.
At the cruise speed this site models for 650 km, 720 km an hour, and thirty minutes of taxi at the two ends, the flight blocks at about 1h 27m.
Kansas City MCI is a mid sized airport in the network held here, 80 scheduled destinations and 171.8 departures a day. Chicago MDW has 208 destinations and 305.1 departures a day.
Kansas City and Chicago keep the same clock all year, so the arrival time is the departure time plus the block and nothing else.
The pair sits inside the Americas, a corridor where the site already publishes 13 written lanes that go into customs and ground detail this page does not.
Who flies the sector, and how often
Average daily frequencies on MCI to MDW from the scheduled route statistics, both directions, with the operating carriers named.
| Direction | Flights a day | Flights a week | Operated by |
|---|---|---|---|
| MCI to MDW | 6.86 | 48 | Southwest Airlines |
| MDW to MCI | 6.71 | 47 | Southwest Airlines |
One carrier holds the sector, Southwest Airlines, so a cancellation has no second nonstop behind it and the connections below stop being theoretical.
At 6.9 times a day there is usually another departure within a few hours, which is what makes a same day booking on this pair realistic.
Between them the two directions put about 95 departures a week on MCI to MDW, which is the number that decides whether a seat can be found today or on Thursday.
The clock from collection to signature
The same ground timings the route calculator starts from, applied to the 1h 27m block time on MCI to MDW. Change any of them in the tool further down and the total moves with them.
| Stage | Allowed | Elapsed |
|---|---|---|
| Collection and the run to MCI | 90 min | 1h 30m |
| At MCI before departure | 180 min | 4h 30m |
| MCI to MDW in the air, estimated | 87 min | 5h 57m |
| Formalities at MDW | 90 min | 7h 27m |
| Delivery run in Chicago | 45 min | 8h 12m |
| Door to door | 492 min | 8h 12m |
On the desk standard ground timings, ninety minutes to collect and reach the airport, three hours at the airport before departure, ninety minutes of arrival formalities and a forty five minute delivery run, the door to door figure for MCI to MDW is 8h 12m.
A courier who leaves Kansas City at 09:00 local is on the ground in Chicago at about 10:27 local and at the door by 12:42 the same day.
Working backwards from a six in the evening handover in Chicago, the last useful departure from Kansas City is around 14:18 local.
When the nonstop does not work
Every airport that joins the two ends, ranked by when they land, among the ones whose weaker leg is dependable enough to plan on. Connection time is allowed for the size of the hub. 36 of them join MCI to MDW.
| Connecting at | MCI to hub, flights a day | Hub to MDW, flights a day | Track, km | Estimated, gate to gate |
|---|---|---|---|---|
| Milwaukee MKE | 1.29 | 3.71 | 830 | 3h 13m |
| St Louis STL | 3.14 | 6.29 | 784 | 3h 25m |
| Indianapolis IND | 1.14 | 2.57 | 985 | 3h 42m |
| Minneapolis MSP | 5.71 | 9.14 | 1,193 | 4h 00m |
| Detroit DTW | 3.86 | 6.14 | 1,376 | 4h 04m |
| Nashville BNA | 4.14 | 8 | 1,426 | 4h 36m |
With 6.9 times a day on the nonstop, a connection here is a disruption plan rather than a routing, and it is listed because a closed runway or a cancellation wave is exactly when nobody has time to work it out.
36 airports connect the two ends on the scheduled network held here. The quickest of the dependable ones is Milwaukee MKE, where the weaker of the two legs still runs about once a day.
Through MKE the routing covers 830 km against the 650 km nonstop track and takes about 3h 13m in the air and on the ground at the hub, allowing 60 minutes to connect at an airport of that size.
That is only 1h 46m more than the nonstop, which is close enough that a connection is worth taking when the nonstop is full or badly timed.
Behind it, St Louis STL at 3h 25m and Indianapolis IND at 3h 42m hold the same connection, so a booking has three hubs to try before it has to wait for the nonstop.
If nothing suitable leaves Kansas City, Omaha OMA is 244 km away by great circle and carries 109 scheduled destinations of its own, which is usually a shorter road transfer than a lost day.
If nothing suitable leaves Chicago, Chicago ORD is 25 km away by great circle and carries 295 scheduled destinations of its own, which is usually a shorter road transfer than a lost day.
Plan Kansas City to Chicago yourself
The same tool the dispatchers use, open to anybody and free. It is loaded with this pair already. Change either end, add a stopover or a preferred airline, and it works out the connection, the transit and the door to door clock, with the real departures underneath. Put it on your own site if it is useful to you.
Restrictions
Where this came from, and where to look next
- Carriers and frequencies: AeroDataBox scheduled route statistics, retrieved 2026-09-07. Average daily flights, not a timetable.
- Distances: great circle from published coordinates. They read short against a flown track, which is why the block time above applies a factor to them.
- Block and connection times: the same model the route calculator lower down this page runs, at the same rounding.
- Restrictions: the airport notes file, checked 2026-09-07.
- Industrial sites: public company information. Nothing here says or implies that any company named is a customer of any courier operator.
Who publishes this. OnBoard Courier is a placement desk in Dubai. An assignment is carried out by a vetted partner operator, with the desk as the single point of contact from the quote to the signature. This page exists because our own dispatchers need the answer for MCI to MDW in the twenty minutes before a promise is made, and a reference only one operator can read is not a reference. Free to read, quote and cite. Found an error? Tell us and we will correct it.
If you need something moved rather than looked up, the desk prices a hand carry in fifteen minutes.
More pairs through MCI and MDW: Detroit to Kansas City, Phoenix to Kansas City, San Diego to Kansas City, Charlotte to Kansas City, Denver to Kansas City, Indianapolis to Kansas City, Las Vegas to Kansas City, New York to Kansas City.