BUFMDW
Buffalo to Chicago
Direct and one-stop flights from Buffalo Niagara International Airport (BUF) to Chicago Midway International Airport (MDW), ranked by how reliably they actually get you there.
Our recommendation
Book Southwest Airlines WN766
- 77% reached Chicago on time
- Direct, so there's no connection to miss
Book Southwest Airlines WN766 (direct). Over this period it reached Chicago on time 77% of the time, with a typical journey of 1h 37m. It flies on Sundays, Mondays, Tuesdays, Wednesdays, Thursdays and Fridays. If speed matters most, Southwest Airlines WN280 (direct) is the quickest at 1h 35m.
Know your rights. US DOT passenger rights covers this trip: US law does not require airlines to pay compensation for delays or cancellations. What you can claim
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 Buffalo to Chicago
Past year. Direct flights and one-stop journeys, ranked by how reliably they actually got passengers there. A journey is on time if it reached Chicago 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 37m
- Arrived on time
- 77%
- Flies
- Sun, Mon, Tue, Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 7.7
Based on 78 journeys; it actually took 1h 55m on average; 2 cancelled.
- Journey
- 1h 35m
- Arrived on time
- 79%
- Flies
- Mon, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 7.4
Based on 28 journeys; it actually took 1h 42m on average.
- Journey
- 1h 35m
- Arrived on time
- 65%
- Flies
- Tue, Wed, Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 6.4
Based on 26 journeys; it actually took 1h 46m on average; 1 cancelled.
- Journey
- 1h 37m
- Arrived on time
- 48%
- Flies
- Mon, Tue, Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 5.4
Based on 46 journeys; it actually took 2h 08m on average.
- Journey
- 1h 40m
- Arrived on time
- 46%
- Flies
- Sun, Mon, Tue, Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 5.1
Based on 37 journeys; it actually took 2h 02m on average; 3 cancelled.
- Journey
- 1h 40m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 27m on average.
- Journey
- 1h 40m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 1h 26m on average.
- Journey
- 1h 40m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 8 journeys; it actually took 1h 45m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 25m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 18m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 33m on average.
- 1h 14m stopover in Atlanta
- Journey
- 5h 24m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 02m on average.
- 2h 50m stopover in Atlanta
- Journey
- 6h 59m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 39m on average.
- 5h 20m stopover in Atlanta · 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
- 9h 30m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 29m on average.
- 7h 10m stopover in Atlanta
What this means
A long wait at the airport in Atlanta. Check whether you can stay airside or need to pass through immigration.
- Journey
- 11h 18m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 02m on average.
- 2h 15m stopover in Atlanta · 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
- 6h 31m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 14m on average.
- 3h 00m stopover in Atlanta · 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 09m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 21m on average.
- 7h 29m stopover in Atlanta
What this means
A long wait at the airport in Atlanta. Check whether you can stay airside or need to pass through immigration.
- Journey
- 11h 38m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 22m on average.
- 5h 21m stopover in Atlanta · 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
- 9h 37m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 21m on average.
- 6h 01m stopover in Boston · Two airlines: book on one ticket
What this means
A long wait at the airport in Boston. Check whether you can stay airside or need to pass through immigration.
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
- 10h 08m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 52m on average.
- 4h 15m stopover in Boston · 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
- 8h 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 08m on average.
- 6h 10m stopover in Baltimore
What this means
A long wait at the airport in Baltimore. Check whether you can stay airside or need to pass through immigration.
- Journey
- 9h 45m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 28m on average.
- 4h 40m stopover in Baltimore
- Journey
- 8h 15m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 58m on average.
- Journey
- 1h 40m
- Arrived on time
- 93%
- Flies
- Mon, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 15 journeys; it actually took 1h 31m on average; 1 cancelled.
- Journey
- 1h 40m
- Arrived on time
- 89%
- Flies
- Tue, Wed
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 9 journeys; it actually took 1h 34m on average.
- Journey
- 1h 35m
- Arrived on time
- 89%
- Flies
- Sun, Tue
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 9 journeys; it actually took 1h 43m on average.
- Journey
- 1h 35m
- Arrived on time
- 75%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 1h 47m on average.
- Journey
- 1h 40m
- Arrived on time
- 60%
- Flies
- Sun
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 1h 59m on average.
- Journey
- 1h 40m
- Arrived on time
- 50%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 2h 07m on average.
- Journey
- 1h 40m
- Arrived on time
- 25%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 2h 37m on average.
- Journey
- 1h 45m
- Arrived on time
- 0%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 3h 41m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Southwest Airlines WN1045, WN1058, WN205, WN2125, WN280, WN3295, WN3614, WN383, WN3853, WN3991, WN4154, WN484, WN4911, WN594, WN726, WN766, WN768, WN845, WN982 | 7.0 | 70% | 78 of 272 | 5 | 1h 04m | No ratings yet | — |
On-time record over time
Show as a table
| Month | Southwest Airlines |
|---|---|
| Jul 26 | 65.9% (91) |
| Aug 26 | 62.5% (88) |
| Sept 26 | 78.2% (87) |
| Nov 26 | 100% (6) |
Questions travellers ask
What's the best way to fly from Buffalo to Chicago?
Book Southwest Airlines WN766 (direct). Over this period it reached Chicago on time 77% of the time, with a typical journey of 1h 37m. It flies on Sundays, Mondays, Tuesdays, Wednesdays, Thursdays and Fridays. If speed matters most, Southwest Airlines WN280 (direct) is the quickest at 1h 35m.
Which airline is most on time from Buffalo to Chicago?
Over the past year, Southwest Airlines had the best record on this route, arriving on time on 70% of 272 flights.
Which airlines fly direct from Buffalo to Chicago?
Southwest Airlines (WN1045, WN1058, WN205, WN2125, WN280, WN3295, WN3614, WN383, WN3853, WN3991, WN4154, WN484, WN4911, WN594, WN726, WN766, WN768, WN845, WN982).