LASCOS
Las Vegas to Colorado Springs
Direct and one-stop flights from Harry Reid International Airport (LAS) to City of Colorado Springs Municipal Airport (COS), ranked by how reliably they actually get you there.
Our recommendation
Book Southwest Airlines WN2147
- 96% reached Colorado Springs on time
- Direct, so there's no connection to miss
Book Southwest Airlines WN2147 (direct). Over this period it reached Colorado Springs on time 96% of the time, with a typical journey of 2h. It flies on Tuesdays, Wednesdays and Saturdays; on other days, Southwest Airlines WN4326 (direct) runs daily and was on time 85% of the time.
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 26 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 Colorado Springs
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 Colorado Springs 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 00m
- Arrived on time
- 96%
- Flies
- Tue, Wed, Sat
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- 8.7
Based on 26 journeys; it actually took 1h 50m on average.
- Journey
- 1h 51m
- Arrived on time
- 85%
- Flies
- Daily
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- 8.0
Based on 33 journeys; it actually took 1h 51m on average.
- Journey
- 1h 55m
- Arrived on time
- 75%
- Flies
- Mon, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- 7.0
Based on 28 journeys; it actually took 1h 58m on average.
- Journey
- 1h 52m
- Arrived on time
- 71%
- Flies
- Mon, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- 6.8
Based on 28 journeys; it actually took 2h 00m on average; 1 cancelled.
- Journey
- 2h 25m
- Arrived on time
- 68%
- Flies
- Mon, Thu, Fri, Sat
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- 5.8
Based on 22 journeys; it actually took 2h 42m on average.
- Journey
- 1h 54m
- Arrived on time
- 54%
- Flies
- Mon, Tue, Wed, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- 5.5
Based on 24 journeys; it actually took 2h 18m on average.
- Journey
- 1h 55m
- Arrived on time
- 50%
- Flies
- Mon, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- 5.3
Based on 28 journeys; it actually took 2h 21m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Sat
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 39m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 1h 43m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 32m on average.
- Journey
- 2h 00m
- Arrived on time
- 100%
- Flies
- Sun
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 43m on average.
- Journey
- 1h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 42m on average.
- Journey
- 1h 50m
- Arrived on time
- 100%
- Flies
- Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 56m on average.
- 6h 44m 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 50m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 13h 34m on average.
- 5h 22m 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
- 12h 43m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 12h 27m 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
- 13h 40m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 13h 10m on average.
- 6h 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
- 13h 10m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 12h 40m on average.
- 7h 30m stopover in Dallas
What this means
A long wait at the airport in Dallas. Check whether you can stay airside or need to pass through immigration.
- Journey
- 12h 00m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 11h 47m on average.
- 2h 45m stopover in Dallas
- Journey
- 7h 20m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 07m on average.
- 1h 21m stopover in Denver
- Journey
- 4h 18m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 4h 09m on average.
- 3h 14m stopover in Denver
- Journey
- 6h 04m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 5h 53m on average.
- 1h 29m stopover in Denver
- Journey
- 4h 19m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 4h 08m on average.
- 7h 03m stopover in Denver · Two airlines: book on one ticket
What this means
A long wait at the airport in Denver. 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 04m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 59m on average.
- 7h 56m stopover in Denver
What this means
A long wait at the airport in Denver. Check whether you can stay airside or need to pass through immigration.
- Journey
- 10h 56m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 10h 51m on average.
- 2h 25m stopover in Denver
- Journey
- 5h 23m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 06m on average.
- Journey
- 1h 55m
- Arrived on time
- 80%
- Flies
- Sun
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 5 journeys; it actually took 1h 57m on average.
- Journey
- 1h 55m
- Arrived on time
- 75%
- Flies
- Sat
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 4 journeys; it actually took 1h 44m on average.
- Journey
- 1h 52m
- Arrived on time
- 61%
- Flies
- Tue, Wed
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 18 journeys; it actually took 2h 05m on average.
- Journey
- 1h 52m
- Arrived on time
- 57%
- Flies
- Sun
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 2h 15m on average.
- Journey
- 1h 45m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 01m on average.
- Journey
- 1h 50m
- Arrived on time
- 43%
- Flies
- Sun
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 7 journeys; it actually took 2h 20m on average.
- Journey
- 1h 50m
- Arrived on time
- 0%
- Flies
- Sun
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 12m on average.
- Journey
- 1h 50m
- Arrived on time
- 0%
- Flies
- Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 3h 28m on average.
- Journey
- 1h 45m
- Arrived on time
- 0%
- Flies
- Fri
- Price, Tue 24 Nov
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 06m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Southwest Airlines WN1564, WN161, WN1719, WN2016, WN2140, WN2147, WN2214, WN225, WN2315, WN2782, WN3127, WN3223, WN3798, WN382, WN4036, WN4326, WN4487, WN467, WN4847, WN4850, WN626, WN868 | 6.9 | 69% | 72 of 237 | 1 | 50 min | No ratings yet | — |
On-time record over time
Show as a table
| Month | Southwest Airlines |
|---|---|
| Jul 26 | 72% (75) |
| Aug 26 | 59.5% (79) |
| Sept 26 | 77.6% (76) |
| Nov 26 | 57.1% (7) |
Questions travellers ask
What's the best way to fly from Las Vegas to Colorado Springs?
Book Southwest Airlines WN2147 (direct). Over this period it reached Colorado Springs on time 96% of the time, with a typical journey of 2h. It flies on Tuesdays, Wednesdays and Saturdays; on other days, Southwest Airlines WN4326 (direct) runs daily and was on time 85% of the time.
Which airline is most on time from Las Vegas to Colorado Springs?
Over the past year, Southwest Airlines had the best record on this route, arriving on time on 69% of 237 flights.
Which airlines fly direct from Las Vegas to Colorado Springs?
Southwest Airlines (WN1564, WN161, WN1719, WN2016, WN2140, WN2147, WN2214, WN225, WN2315, WN2782, WN3127, WN3223, WN3798, WN382, WN4036, WN4326, WN4487, WN467, WN4847, WN4850, WN626, WN868).