FLLBNA
Fort Lauderdale to Nashville
Direct and one-stop flights from Fort Lauderdale Hollywood International Airport (FLL) to Nashville International Airport (BNA), ranked by how reliably they actually get you there.
Our recommendation
Book Southwest Airlines WN1774
- 96% reached Nashville on time
- Direct, so there's no connection to miss
Book Southwest Airlines WN1774 (direct). Over this period it reached Nashville on time 96% of the time, with a typical journey of 2h 16m. It flies on Sundays, Tuesdays and Wednesdays; on other days, JetBlue B6681 (direct) runs daily and was on time 64% of the time. If speed matters most, Southwest Airlines WN2283 (direct) is the quickest at 2h 15m.
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 25 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 Fort Lauderdale to Nashville
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 Nashville 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
- 2h 16m
- Arrived on time
- 96%
- Flies
- Sun, Tue, Wed
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 8.8
Based on 25 journeys; it actually took 2h 09m on average.
- Journey
- 2h 15m
- Arrived on time
- 93%
- Flies
- Mon, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 8.6
Based on 28 journeys; it actually took 2h 14m on average.
- Journey
- 2h 16m
- Arrived on time
- 83%
- Flies
- Sun, Mon, Tue, Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 7.7
Based on 29 journeys; it actually took 2h 24m on average.
- Journey
- 2h 26m
- Arrived on time
- 64%
- Flies
- Daily
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 6.6
Based on 91 journeys; it actually took 2h 47m on average.
- Journey
- 2h 27m
- Arrived on time
- 64%
- Flies
- Daily
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 6.5
Based on 67 journeys; it actually took 2h 38m on average; 6 cancelled.
- Journey
- 2h 26m
- Arrived on time
- 57%
- Flies
- Daily
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 6.1
Based on 90 journeys; it actually took 2h 47m on average; 4 cancelled.
- Journey
- 2h 17m
- Arrived on time
- 55%
- Flies
- Sun, Mon, Tue, Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 5.9
Based on 47 journeys; it actually took 3h 28m on average.
- Journey
- 2h 23m
- Arrived on time
- 42%
- Flies
- Sun, Mon, Thu, Fri, Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 4.6
Based on 24 journeys; it actually took 2h 55m on average.
- Journey
- 2h 17m
- Arrived on time
- 38%
- Flies
- Mon, Tue, Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 4.5
Based on 24 journeys; it actually took 2h 47m on average; 1 cancelled.
- Journey
- 2h 20m
- Arrived on time
- 33%
- Flies
- Sun, Mon, Tue, Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 4.5
Based on 54 journeys; it actually took 2h 48m on average.
- Journey
- 2h 15m
- Arrived on time
- 32%
- Flies
- Mon, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 4.3
Based on 28 journeys; it actually took 3h 33m on average.
- Journey
- 2h 21m
- Arrived on time
- 33%
- Flies
- Sun, Mon, Thu, Fri, Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- 4.2
Based on 24 journeys; it actually took 3h 03m on average; 1 cancelled.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 11m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 17m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 10m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 2h 10m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 13m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 07m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 2h 05m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 11m on average.
- Journey
- 2h 23m
- Arrived on time
- 100%
- Flies
- Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 20m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 51m on average.
- 2h 16m 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
- 5h 54m
- 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 52m on average.
- 7h 18m 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 55m
- 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 10h 39m on average.
- 2h 35m 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
- 5h 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 5h 44m on average.
- 7h 38m 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 47m
- 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 10h 31m on average.
- 7h 48m 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 00m
- 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 10h 52m on average.
- 5h 48m stopover in Atlanta
- Journey
- 9h 00m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 9h 04m on average.
- 6h 55m 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 08m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 9h 36m on average.
- 7h 25m 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 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 10h 12m on average.
- 6h 25m 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
- 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 12m on average.
- 3h 22m stopover in Austin · 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 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 8h 27m on average.
- 2h 10m stopover in Austin
- Journey
- 7h 10m
- 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 14m on average.
- 4h 40m stopover in Boston
- Journey
- 10h 50m
- 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 10h 27m on average.
- Journey
- 2h 20m
- Arrived on time
- 88%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 8 journeys; it actually took 2h 13m on average.
- Journey
- 2h 15m
- Arrived on time
- 85%
- Flies
- Mon, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 13 journeys; it actually took 2h 20m on average; 1 cancelled.
- Journey
- 2h 15m
- Arrived on time
- 83%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 6 journeys; it actually took 2h 14m on average.
- Journey
- 2h 15m
- Arrived on time
- 75%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 2h 15m on average.
- Journey
- 2h 20m
- Arrived on time
- 75%
- Flies
- Sun
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 8 journeys; it actually took 2h 27m on average.
- Journey
- 2h 25m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 2h 31m on average.
- Journey
- 2h 25m
- Arrived on time
- 56%
- Flies
- Tue, Wed
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 9 journeys; it actually took 2h 49m on average.
- Journey
- 2h 35m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 3h 04m on average.
- Journey
- 2h 20m
- Arrived on time
- 25%
- Flies
- Sat
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 3h 03m on average.
- Journey
- 2h 20m
- Arrived on time
- 22%
- Flies
- Tue, Wed
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 9 journeys; it actually took 3h 09m on average; 1 cancelled.
- Journey
- 2h 15m
- Arrived on time
- 20%
- Flies
- Sun
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 3h 02m on average.
- Journey
- 2h 22m
- Arrived on time
- 20%
- Flies
- Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 6h 31m on average.
- Journey
- 2h 17m
- Arrived on time
- 14%
- Flies
- Sun
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 3h 23m on average.
- Journey
- 2h 13m
- Arrived on time
- 0%
- Flies
- Thu
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 3h 48m on average.
- Journey
- 1h 48m
- Arrived on time
- 0%
- Flies
- Fri
- Price, Sun 22 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 10m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | JetBlue B62481, B62581, B6681 | 6.3 | 63% | 78 of 236 | 10 | 1h 10m | No ratings yet | — |
| 2 | Southwest Airlines WN1067, WN1705, WN1715, WN1732, WN1774, WN1775, WN1777, WN1850, WN1852, WN1932, WN1935, WN1955, WN2283, WN245, WN2595, WN2754, WN395, WN4021, WN4029, WN406, WN408, WN4630, WN4638, WN4708, WN4778, WN5065, WN521, WN642, WN755 | 5.9 | 59% | 140 of 350 | 2 | 1h 03m | No ratings yet | — |
| 3 | Allegiant Air G41952, G4493, G4499, G4534 | 2.0 | 20% | 12 of 15 | 0 | 1h 42m | No ratings yet | — |
| NetJets 1I335 | No score yet | 0% | 1 of 1 | 0 | 22 min | No ratings yet | — |
On-time record over time
- NetJets
- JetBlue
- Allegiant Air
Show as a table
| Month | NetJets | JetBlue | Allegiant Air |
|---|---|---|---|
| Jul 26 | — | 52.2% (69) | 0% (9) |
| Aug 26 | — | 63.4% (93) | 40% (5) |
| Sept 26 | — | 73.5% (68) | — |
| Nov 26 | 0% (1) | 50% (6) | 100% (1) |
Questions travellers ask
What's the best way to fly from Fort Lauderdale to Nashville?
Book Southwest Airlines WN1774 (direct). Over this period it reached Nashville on time 96% of the time, with a typical journey of 2h 16m. It flies on Sundays, Tuesdays and Wednesdays; on other days, JetBlue B6681 (direct) runs daily and was on time 64% of the time. If speed matters most, Southwest Airlines WN2283 (direct) is the quickest at 2h 15m.
Which airline is most on time from Fort Lauderdale to Nashville?
Over the past year, JetBlue had the best record on this route, arriving on time on 63% of 236 flights.
Which airlines fly direct from Fort Lauderdale to Nashville?
JetBlue (B62481, B62581, B6681), Southwest Airlines (WN1067, WN1705, WN1715, WN1732, WN1774, WN1775, WN1777, WN1850, WN1852, WN1932, WN1935, WN1955, WN2283, WN245, WN2595, WN2754, WN395, WN4021, WN4029, WN406, WN408, WN4630, WN4638, WN4708, WN4778, WN5065, WN521, WN642, WN755), Allegiant Air (G41952, G4493, G4499, G4534), NetJets (1I335).
How often are Allegiant Air flights from Fort Lauderdale to Nashville late?
12 of 15 flights arrived more than 15 minutes late over the past year. When late, the typical delay was 1h 42m.