Flight profile · Alaska Airlines
AS735
Las Vegas (LAS) to Seattle (SEA) · scheduled 10:00 AM – 12:50 PM
How AS735 performs
514 operations, 2024-03-14 to 2026-06-09.
AS735 arrived on time 86.6% of the time, against 80.1% for all LAS → SEA flights — this specific departure is 6.5 percentage points better than the route as a whole. Against Alaska Airlines’s own flights on this route it is 7.4 points better.
Source: US DOT Bureau of Transportation Statistics · 514 operations between 2024-03-14 to 2026-06-09
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| AS735 | 86.6% | 1.17% | -8 min | 4.3% | 514 |
| Alaska Airlines on LAS → SEA | 79.2% | 1.21% | -5 min | 5.7% | 8,125 |
| All LAS → SEA flights | 80.1% | 0.82% | -7 min | 5.4% | 18,723 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-03-14 to 2026-06-09
Other routes AS735 has flown
A flight number is a slot in a schedule, and carriers reassign it. These are the other city pairs this number served in the analysis period.
| Route | Operated | Flights | On time |
|---|---|---|---|
| PDX→SEA Portland to Seattle | 2025-12-17 – 2025-12-17 | 1 | — |
| PHX→PAE Phoenix to Everett | 2023-10-03 – 2025-12-01 | 21 | — |
| DEN→SEA Denver to Seattle | 2025-08-21 – 2025-10-03 | 44 | — |
| SAN→SEA San Diego to Seattle | 2025-06-12 – 2025-08-19 | 68 | — |
| PHX→SFO Phoenix to San Francisco | 2024-01-08 – 2024-02-12 | 26 | — |
| PAE→PHX Everett to Phoenix | 2023-10-01 – 2023-10-01 | 1 | — |
Because the same number has served different journeys, the statistics above describe only the route AS735 currently operates. Blending them would produce an average of two different flights.
Data and methodology
Calculated by FlyerIntel from 514 records of AS735 operating LAS → SEA, published by the US DOT Bureau of Transportation Statistics. A flight counts as delayed when it arrives 15 or more minutes after schedule. Cancelled and diverted flights are excluded from the on-time rate and reported separately. Flight numbers are resolved as carrier plus number plus route, because the same number serves different routes over time.