LASPIT
Las Vegas to Pittsburgh
Direct and one-stop flights from Harry Reid International Airport (LAS) to Pittsburgh International Airport (PIT), ranked by how reliably they actually get you there.
Our recommendation
Book Southwest Airlines WN694
- 39% reached Pittsburgh on time
- Direct, so there's no connection to miss
Book Southwest Airlines WN694 (direct). Over this period it reached Pittsburgh on time 39% of the time, with a typical journey of 4h 12m. It flies on Mondays, Thursdays and Fridays.
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 Las Vegas to Pittsburgh
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 Pittsburgh 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
- 4h 12m
- Arrived on time
- 39%
- Flies
- Mon, Thu, Fri
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- 4.7
Based on 28 journeys; it actually took 5h 21m on average; 1 cancelled.
- Journey
- 4h 10m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 8 journeys; it actually took 4h 07m on average.
- 7h 22m stopover in Boston
What this means
A long wait at the airport in Boston. Check whether you can stay airside or need to pass through immigration.
- Journey
- 14h 51m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Tue, Wed
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 15h 00m on average.
- 1h 40m stopover in Atlanta
- Journey
- 7h 03m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 46m on average.
- 4h 24m stopover in Atlanta
- Journey
- 9h 50m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 35m on average.
- 3h 02m 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 43m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 27m on average.
- 4h 24m 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 50m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 43m on average.
- 3h 02m 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 43m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 35m 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 53m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 41m 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 46m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 34m on average.
- 3h 26m 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
- 8h 00m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 52m on average.
- 3h 50m stopover in Nashville
- Journey
- 8h 55m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 55m on average.
- 1h 21m stopover in Boston
- Journey
- 8h 15m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 39m on average.
- 2h 20m stopover in Baltimore
- Journey
- 7h 45m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 43m on average.
- Journey
- 4h 15m
- Arrived on time
- 86%
- Flies
- Sun
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 4h 18m on average.
- Journey
- 4h 10m
- Arrived on time
- 80%
- Flies
- Sun
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 4h 15m on average.
- Journey
- 4h 22m
- Arrived on time
- 78%
- Flies
- Tue, Wed
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 18 journeys; it actually took 4h 26m on average.
- Journey
- 2h 39m
- Arrived on time
- 75%
- Flies
- Wed, Thu, Fri, Sat
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 2h 49m on average.
- Journey
- 4h 10m
- Arrived on time
- 75%
- Flies
- Sat
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 4h 21m on average.
- Journey
- 4h 20m
- Arrived on time
- 75%
- Flies
- Sat
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 4h 44m on average.
- Journey
- 4h 10m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 4h 23m on average.
- Journey
- 4h 15m
- Arrived on time
- 33%
- Flies
- Mon, Thu, Fri
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 15 journeys; it actually took 4h 46m on average.
- Journey
- 4h 15m
- Arrived on time
- 0%
- Flies
- Sun
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 4h 55m on average.
- Journey
- 4h 10m
- Arrived on time
- 0%
- Flies
- Sun
- Price, Fri 20 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 4h 35m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Southwest Airlines WN1262, WN1560, WN2227, WN2414, WN2773, WN3133, WN3477, WN3543, WN421, WN4491, WN505, WN694 | 5.9 | 59% | 44 of 110 | 1 | 51 min | No ratings yet | — |
On-time record over time
Show as a table
| Month | Southwest Airlines |
|---|---|
| Jul 26 | 50% (38) |
| Aug 26 | 59.5% (37) |
| Sept 26 | 69.7% (33) |
| Nov 26 | 50% (2) |
Questions travellers ask
What's the best way to fly from Las Vegas to Pittsburgh?
Book Southwest Airlines WN694 (direct). Over this period it reached Pittsburgh on time 39% of the time, with a typical journey of 4h 12m. It flies on Mondays, Thursdays and Fridays.
Which airline is most on time from Las Vegas to Pittsburgh?
Over the past year, Southwest Airlines had the best record on this route, arriving on time on 59% of 110 flights.
Which airlines fly direct from Las Vegas to Pittsburgh?
Southwest Airlines (WN1262, WN1560, WN2227, WN2414, WN2773, WN3133, WN3477, WN3543, WN421, WN4491, WN505, WN694).