The sector is held by Denver Air Connection and Southwest Airlines.
Airport pair · hand carry reference
IND Indianapolis to MCI Kansas City
Indianapolis International, the United States, to Kansas City International, the United States. Computed from the scheduled network held on 2026-09-07.
- Nonstop
- About once a day
- Great circle
- 724 km
- Block, estimated
- 1h 34m
- Door to door
- 8h 19m
What IND to MCI looks like
The IND to MCI sector, the carriers on it and the flying time, before anything is promised to anybody.
Indianapolis IND to Kansas City MCI is a short sector of 724 km by great circle, flown nonstop about once a day.
At the cruise speed this site models for 724 km, 720 km an hour, and thirty minutes of taxi at the two ends, the flight blocks at about 1h 34m.
Indianapolis IND is a large airport in the network held here, 107 scheduled destinations and 171.9 departures a day. Kansas City MCI has 80 destinations and 171.8 departures a day.
Kansas City is one hour behind of Indianapolis all year.
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 IND to MCI from the scheduled route statistics, both directions, with the operating carriers named.
| Direction | Flights a day | Flights a week | Operated by |
|---|---|---|---|
| IND to MCI | 1.29 | 9 | Denver Air Connection, Southwest Airlines |
| MCI to IND | 1.14 | 8 | Southwest Airlines |
Two carriers hold the sector, Denver Air Connection and Southwest Airlines, which gives a missed departure somewhere to go without leaving the nonstop.
Between them the two directions put about 17 departures a week on IND to MCI, 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 34m block time on IND to MCI. Change any of them in the tool further down and the total moves with them.
| Stage | Allowed | Elapsed |
|---|---|---|
| Collection and the run to IND | 90 min | 1h 30m |
| At IND before departure | 180 min | 4h 30m |
| IND to MCI in the air, estimated | 94 min | 6h 04m |
| Formalities at MCI | 90 min | 7h 34m |
| Delivery run in Kansas City | 45 min | 8h 19m |
| Door to door | 499 min | 8h 19m |
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 IND to MCI is 8h 19m.
A courier who leaves Indianapolis at 09:00 local is on the ground in Kansas City at about 09:34 local and at the door by 11:49 the same day.
Working backwards from a six in the evening handover in Kansas City, the last useful departure from Indianapolis is around 15:11 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 IND to MCI.
| Connecting at | IND to hub, flights a day | Hub to MCI, flights a day | Track, km | Estimated, gate to gate |
|---|---|---|---|---|
| Chicago MDW | 2.57 | 6.71 | 911 | 3h 50m |
| Chicago ORD | 18.14 | 14.57 | 933 | 3h 52m |
| Detroit DTW | 7.14 | 4 | 1,380 | 4h 05m |
| Minneapolis MSP | 3.71 | 5.86 | 1,441 | 4h 13m |
| Nashville BNA | 2.71 | 5.29 | 1,191 | 4h 15m |
| Dallas DAL | 1.71 | 5.57 | 1,958 | 4h 54m |
One nonstop a day means one chance a day, so the connections below are what a consignment that arrives at IND in the afternoon actually flies on.
36 airports connect the two ends on the scheduled network held here. The quickest of the dependable ones is Chicago MDW, where the weaker of the two legs still runs about twice a day.
Through MDW the routing covers 911 km against the 724 km nonstop track and takes about 3h 50m in the air and on the ground at the hub, allowing 90 minutes to connect at an airport of that size.
That is only 2h 16m more than the nonstop, which is close enough that a connection is worth taking when the nonstop is full or badly timed.
Behind it, Chicago ORD at 3h 52m and Detroit DTW at 4h 05m 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.
Industry within reach of the two ends
Public manufacturing and research sites whose logistics run through IND or MCI. Listed as industrial geography, not as customers of anyone.
- Eli Lilly, IndianapolisResearch and manufacturing at the group head office. An American cluster with European trial sites. Logistics through Indianapolis IND.
Plan Indianapolis to Kansas City 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 IND to MCI 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 IND and MCI: Atlanta to Indianapolis, Indianapolis to Chicago, Boston to Indianapolis, Detroit to Indianapolis, Indianapolis to Seattle, Indianapolis to San Francisco, New York to Indianapolis, Indianapolis to Houston.