LASIND
Las Vegas to Indianapolis
Direct and one-stop flights from Harry Reid International Airport (LAS) to Indianapolis International Airport (IND), ranked by how reliably they actually get you there.
Our recommendation
Book Southwest Airlines WN4376
- 95% reached Indianapolis on time
- Direct, so there's no connection to miss
Book Southwest Airlines WN4376 (direct). Over this period it reached Indianapolis on time 95% of the time, with a typical journey of 3h 48m. It flies on Tuesdays, Wednesdays and Saturdays; on other days, Southwest Airlines WN2246 (direct) runs daily and was on time 90% of the time. If speed matters most, Southwest Airlines WN4032 (direct) is the quickest at 3h 39m.
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 20 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 Las Vegas to Indianapolis
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 Indianapolis 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
- 3h 48m
- Arrived on time
- 95%
- Flies
- Tue, Wed, Sat
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 8.1
Based on 20 journeys; it actually took 3h 36m on average.
- Journey
- 3h 39m
- Arrived on time
- 92%
- Flies
- Sun, Mon, Thu, Fri
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 8.1
Based on 25 journeys; it actually took 3h 32m on average.
- Journey
- 3h 40m
- Arrived on time
- 90%
- Flies
- Daily
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 7.9
Based on 29 journeys; it actually took 3h 39m on average.
- Journey
- 3h 40m
- Arrived on time
- 86%
- Flies
- Mon, Thu, Fri
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 7.6
Based on 28 journeys; it actually took 3h 41m on average.
- Journey
- 3h 39m
- Arrived on time
- 82%
- Flies
- Daily
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 7.4
Based on 33 journeys; it actually took 3h 43m on average.
- Journey
- 3h 37m
- Arrived on time
- 54%
- Flies
- Daily
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 5.6
Based on 61 journeys; it actually took 3h 58m on average; 1 cancelled.
- Journey
- 3h 38m
- Arrived on time
- 52%
- Flies
- Daily
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 5.2
Based on 33 journeys; it actually took 4h 01m on average.
- Journey
- 3h 37m
- Arrived on time
- 48%
- Flies
- Mon, Thu, Fri
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 4.9
Based on 27 journeys; it actually took 4h 27m on average; 1 cancelled.
- Journey
- 3h 37m
- Arrived on time
- 48%
- Flies
- Tue, Wed, Sat
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 4.8
Based on 25 journeys; it actually took 4h 08m on average.
- Journey
- 3h 10m
- Arrived on time
- 37%
- Flies
- Daily
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- 4.7
Based on 43 journeys; it actually took 3h 39m on average.
- Journey
- 3h 44m
- Arrived on time
- 100%
- Flies
- Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 3h 27m on average.
- Journey
- 3h 35m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 3h 27m on average.
- Journey
- 3h 42m
- Arrived on time
- 100%
- Flies
- Sun, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 10 journeys; it actually took 3h 27m on average.
- Journey
- 3h 45m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 3h 25m on average.
- Journey
- 3h 05m
- Arrived on time
- 100%
- Flies
- Mon, Tue, Wed
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 2h 57m on average.
- Journey
- 2h 48m
- Arrived on time
- 100%
- Flies
- Mon, Tue
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 50m on average.
- Journey
- 3h 30m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 3h 29m on average.
- 3h 13m stopover in Atlanta
- Journey
- 8h 31m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 20m on average.
- 1h 51m 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 24m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 12m on average.
- 4h 40m stopover in Atlanta
- Journey
- 9h 59m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 39m on average.
- 3h 18m 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
- 8h 51m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 31m on average.
- 7h 43m 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
- 13h 03m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 12h 39m on average.
- 6h 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 56m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 32m 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
- 11h 47m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 21m on average.
- 6h 20m 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 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 14m on average.
- 7h 48m stopover in Austin · Two airlines: book on one ticket
What this means
A long wait at the airport in Austin. 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
- 13h 02m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 12h 34m on average.
- 6h 28m stopover in Austin · Two airlines: book on one ticket
What this means
A long wait at the airport in Austin. 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 47m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 19m on average.
- 3h 31m stopover in Nashville · 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 45m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 26m on average.
- 5h 45m stopover in Baltimore
- Journey
- 12h 00m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 34m on average.
- Journey
- 3h 38m
- Arrived on time
- 86%
- Flies
- Sat
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 3h 35m on average.
- Journey
- 3h 44m
- Arrived on time
- 86%
- Flies
- Sun
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 3h 53m on average.
- Journey
- 1h 50m
- Arrived on time
- 75%
- Flies
- Sun, Wed, Thu, Fri
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 1h 53m on average; 1 cancelled.
- Journey
- 3h 37m
- Arrived on time
- 71%
- Flies
- Sun
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 3h 48m on average.
- Journey
- 3h 41m
- Arrived on time
- 70%
- Flies
- Sun, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 10 journeys; it actually took 3h 50m on average.
- Journey
- 3h 44m
- Arrived on time
- 50%
- Flies
- Sun
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 4h 19m on average.
- Journey
- 3h 30m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 3h 43m on average.
- Journey
- 3h 35m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 22m on average.
- Journey
- 3h 39m
- Arrived on time
- 25%
- Flies
- Sun
- Price, Sat 21 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 4h 13m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Allegiant Air G42237, G4593, G4597, G46 | 8.5 | 85% | 4 of 26 | 0 | 53 min | No ratings yet | — |
| 2 | Southwest Airlines WN119, WN151, WN1529, WN1584, WN2128, WN2246, WN2248, WN2278, WN229, WN3258, WN3834, WN4032, WN4160, WN4376, WN4446, WN461, WN4706, WN473, WN4786, WN4830, WN5002, WN752 | 6.8 | 68% | 106 of 341 | 2 | 54 min | No ratings yet | — |
On-time record over time
- Allegiant Air
- Southwest Airlines
Show as a table
| Month | Allegiant Air | Southwest Airlines |
|---|---|---|
| Jul 26 | 66.7% (9) | 68.1% (119) |
| Aug 26 | 88.9% (9) | 59.5% (111) |
| Sept 26 | 100% (8) | 78.1% (105) |
| Nov 26 | — | 66.7% (6) |
Questions travellers ask
What's the best way to fly from Las Vegas to Indianapolis?
Book Southwest Airlines WN4376 (direct). Over this period it reached Indianapolis on time 95% of the time, with a typical journey of 3h 48m. It flies on Tuesdays, Wednesdays and Saturdays; on other days, Southwest Airlines WN2246 (direct) runs daily and was on time 90% of the time. If speed matters most, Southwest Airlines WN4032 (direct) is the quickest at 3h 39m.
Which airline is most on time from Las Vegas to Indianapolis?
Over the past year, Allegiant Air had the best record on this route, arriving on time on 85% of 26 flights.
Which airlines fly direct from Las Vegas to Indianapolis?
Allegiant Air (G42237, G4593, G4597, G46), Southwest Airlines (WN119, WN151, WN1529, WN1584, WN2128, WN2246, WN2248, WN2278, WN229, WN3258, WN3834, WN4032, WN4160, WN4376, WN4446, WN461, WN4706, WN473, WN4786, WN4830, WN5002, WN752).
How often are Southwest Airlines flights from Las Vegas to Indianapolis late?
106 of 341 flights arrived more than 15 minutes late over the past year. When late, the typical delay was 54 min.