CMHMCI
Columbus to Kansas City
Direct and one-stop flights from John Glenn Columbus International Airport (CMH) to Kansas City International Airport (MCI), ranked by how reliably they actually get you there.
Latest official data runs to 27 September 2026. Government on-time statistics are published several weeks after the month ends, so this page shows the past 3 months. Live tracking fills in recent days as it builds up.
Our recommendation
Not enough flight history yet to recommend a journey
We don't have enough flight history yet to recommend a way to fly from Columbus to Kansas City.
Flexible on dates?
Pick a range of up to 14 days and we'll tell you the best day to fly, and the most reliable journey that actually operates on each date.
Every way to fly Columbus to Kansas City
Past 3 months. Direct flights and one-stop journeys, ranked by how reliably they actually got passengers there. A journey is on time if it reached Kansas City within 15 minutes of schedule; a missed connection counts as late.
Live prices aren't connected in this preview yet. When they are, each journey shows its lowest current fare for the date you pick. Prices never affect our recommendation.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Sun
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 1h 34m on average.
- 2h 05m stopover in Atlanta
- Journey
- 6h 07m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 43m on average.
- 3h 17m stopover in Atlanta
- Journey
- 7h 15m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 41m on average.
- 2h 12m stopover in Atlanta
- Journey
- 6h 10m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 36m on average.
- 1h 30m stopover in Nashville
- Journey
- 4h 55m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 4h 33m on average.
- 2h 30m stopover in Baltimore
- Journey
- 6h 55m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 18m on average.
- 2h 20m stopover in Dallas
- Journey
- 6h 45m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 35m on average.
- 2h 18m stopover in Denver · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 7h 24m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 07m on average.
- 1h 00m stopover in Detroit
- Journey
- 4h 21m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 3h 53m on average.
- 1h 35m stopover in Houston
- Journey
- 6h 35m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 24m on average.
- 4h 40m stopover in Detroit
- Journey
- 7h 58m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 31m on average; 1 cancelled.
- 2h 53m stopover in Detroit
- Journey
- 6h 13m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 46m on average; 1 cancelled.
- 4h 29m stopover in Chicago
- Journey
- 8h 08m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 57m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| Southwest Airlines WN3600, WN4524 | No score yet | 100% | 0 of 5 | 0 | — | No ratings yet | — |
On-time record over time
Show as a table
| Week of | Southwest Airlines |
|---|---|
| 17 Aug | 100% (1) |
| 24 Aug | 100% (1) |
| 7 Sept | 100% (1) |
| 14 Sept | 100% (1) |
| 21 Sept | 100% (1) |
Questions travellers ask
Which airlines fly direct from Columbus to Kansas City?
Southwest Airlines (WN3600, WN4524).