BDLBWI
Hartford to Baltimore
Direct and one-stop flights from Bradley International Airport (BDL) to Baltimore/Washington International Thurgood Marshall Airport (BWI), ranked by how reliably they actually get you there.
Our recommendation
Book Southwest Airlines WN667
- 96% reached Baltimore on time
- Direct, so there's no connection to miss
Book Southwest Airlines WN667 (direct). Over this period it reached Baltimore on time 96% of the time, with a typical journey of 1h 25m. It flies on Mondays, Thursdays and Fridays; on other days, Southwest Airlines WN423 (direct) runs daily and was on time 64% of the time. If speed matters most, Southwest Airlines WN1967 (direct) is the quickest at 1h 20m.
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
- This pick is based on 28 journeys, so treat it as an early signal.
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 Hartford to Baltimore
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 Baltimore 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 25m
- Arrived on time
- 96%
- Flies
- Mon, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 8.8
Based on 28 journeys; it actually took 1h 15m on average.
- Journey
- 1h 22m
- Arrived on time
- 93%
- Flies
- Mon, Tue, Wed, Thu, Fri, Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 8.6
Based on 29 journeys; it actually took 1h 20m on average.
- Journey
- 1h 20m
- Arrived on time
- 93%
- Flies
- Mon, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 8.6
Based on 28 journeys; it actually took 1h 19m on average.
- Journey
- 1h 23m
- Arrived on time
- 88%
- Flies
- Sun, Tue, Wed, Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 8.2
Based on 34 journeys; it actually took 1h 20m on average.
- Journey
- 1h 20m
- Arrived on time
- 85%
- Flies
- Mon, Tue, Wed, Thu, Fri, Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 8.2
Based on 53 journeys; it actually took 1h 28m on average.
- Journey
- 1h 24m
- Arrived on time
- 75%
- Flies
- Sun, Mon, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 6.8
Based on 20 journeys; it actually took 1h 30m on average.
- Journey
- 1h 25m
- Arrived on time
- 73%
- Flies
- Tue, Wed, Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 6.8
Based on 26 journeys; it actually took 1h 35m on average; 1 cancelled.
- Journey
- 1h 34m
- Arrived on time
- 64%
- Flies
- Daily
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 5.9
Based on 28 journeys; it actually took 2h 02m on average; 4 cancelled.
- Journey
- 1h 25m
- Arrived on time
- 61%
- Flies
- Mon, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 5.9
Based on 28 journeys; it actually took 1h 46m on average; 2 cancelled.
- Journey
- 1h 27m
- Arrived on time
- 39%
- Flies
- Mon, Tue, Wed, Thu, Fri, Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- 4.5
Based on 28 journeys; it actually took 2h 03m on average; 5 cancelled.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Mon, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 15 journeys; it actually took 1h 15m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 0h 58m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 35m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Tue, Wed
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 17 journeys; it actually took 1h 12m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 8 journeys; it actually took 1h 14m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 35m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 39m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 24m on average.
- Journey
- 1h 33m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 0h 55m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 0h 52m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 09m on average.
- Journey
- 1h 22m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 02m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 29m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 25m on average.
- Journey
- 1h 30m
- Arrived on time
- 100%
- Flies
- Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 11m on average.
- 2h 25m stopover in Atlanta
- Journey
- 6h 54m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 6h 34m on average.
- 3h 08m 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 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 29m on average.
- 5h 58m 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
- 10h 29m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 10h 27m on average.
- 6h 13m stopover in Atlanta · Two airlines: book on one ticket
What this means
A long wait at the airport in Atlanta. 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 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 10h 28m on average.
- 6h 56m 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 24m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 11h 08m on average.
- 1h 31m stopover in Atlanta
- Journey
- 5h 54m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 5h 34m on average.
- 2h 14m 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 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 29m on average.
- 5h 04m 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 29m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 27m on average.
- 5h 19m 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 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 28m on average.
- 6h 02m 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
- 10h 24m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 10h 08m on average.
- 7h 21m stopover in Atlanta · Two airlines: book on one ticket
What this means
A long wait at the airport in Atlanta. 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
- 11h 43m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 11h 45m on average.
- 6h 23m stopover in Atlanta · Two airlines: book on one ticket
What this means
A long wait at the airport in Atlanta. 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 43m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 10h 45m on average.
- Journey
- 1h 25m
- Arrived on time
- 86%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 1h 25m on average.
- Journey
- 1h 25m
- Arrived on time
- 80%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 2h 58m on average.
- Journey
- 1h 20m
- Arrived on time
- 80%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 1h 40m on average.
- Journey
- 1h 20m
- Arrived on time
- 78%
- Flies
- Tue, Wed
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 9 journeys; it actually took 1h 19m on average; 1 cancelled.
- Journey
- 1h 20m
- Arrived on time
- 75%
- Flies
- Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 1h 34m on average.
- Journey
- 1h 20m
- Arrived on time
- 71%
- Flies
- Sun, Tue, Wed
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 14 journeys; it actually took 2h 07m on average.
- Journey
- 1h 25m
- Arrived on time
- 71%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 1h 39m on average.
- Journey
- 1h 20m
- Arrived on time
- 71%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 1h 19m on average.
- Journey
- 1h 25m
- Arrived on time
- 60%
- Flies
- Sun
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 3h 34m on average.
- Journey
- 1h 20m
- Arrived on time
- 50%
- Flies
- Sat
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 1h 51m on average.
- Journey
- 1h 20m
- Arrived on time
- 0%
- Flies
- Thu
- Price, Mon 23 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 6h 52m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Southwest Airlines WN1031, WN105, WN1284, WN1451, WN174, WN179, WN1967, WN2006, WN2122, WN234, WN246, WN2731, WN2927, WN324, WN336, WN342, WN3761, WN4075, WN417, WN420, WN421, WN423, WN4282, WN429, WN437, WN4428, WN445, WN446, WN448, WN449, WN4708, WN5011, WN653, WN667, WN866, WN908 | 8.0 | 80% | 73 of 405 | 7 | 1h 26m | No ratings yet | — |
On-time record over time
Show as a table
| Month | Southwest Airlines |
|---|---|
| Jul 26 | 75.7% (148) |
| Aug 26 | 77.2% (123) |
| Sept 26 | 86.6% (119) |
| Nov 26 | 100% (15) |
Questions travellers ask
What's the best way to fly from Hartford to Baltimore?
Book Southwest Airlines WN667 (direct). Over this period it reached Baltimore on time 96% of the time, with a typical journey of 1h 25m. It flies on Mondays, Thursdays and Fridays; on other days, Southwest Airlines WN423 (direct) runs daily and was on time 64% of the time. If speed matters most, Southwest Airlines WN1967 (direct) is the quickest at 1h 20m.
Which airline is most on time from Hartford to Baltimore?
Over the past year, Southwest Airlines had the best record on this route, arriving on time on 80% of 405 flights.
Which airlines fly direct from Hartford to Baltimore?
Southwest Airlines (WN1031, WN105, WN1284, WN1451, WN174, WN179, WN1967, WN2006, WN2122, WN234, WN246, WN2731, WN2927, WN324, WN336, WN342, WN3761, WN4075, WN417, WN420, WN421, WN423, WN4282, WN429, WN437, WN4428, WN445, WN446, WN448, WN449, WN4708, WN5011, WN653, WN667, WN866, WN908).