Flight profile · Alaska Airlines
AS734
Salt Lake City (SLC) to Seattle (SEA) · scheduled 3:39 PM – 4:54 PM
How AS734 performs
295 operations, 2025-06-12 to 2026-06-30.
AS734 arrived on time 65.8% of the time, against 81.0% for all SLC → SEA flights — this specific departure is 15.2 percentage points worse than the route as a whole. Against Alaska Airlines’s own flights on this route it is 9.5 points worse.
Source: US DOT Bureau of Transportation Statistics · 295 operations between 2025-06-12 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| AS734 | 65.8% | 1.02% | 2 min | 4.5% | 295 |
| Alaska Airlines on SLC → SEA | 75.2% | 1.43% | -3 min | 4.5% | 3,717 |
| All SLC → SEA flights | 81.0% | 0.69% | -7 min | 4.1% | 11,934 |
Source: FlyerIntel analysis of US DOT BTS data · 2025-06-12 to 2026-06-30
Other routes AS734 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 |
|---|---|---|---|
| SEA→OAK Seattle to Oakland | 2026-04-22 – 2026-06-09 | 49 | — |
| ANC→PDX Anchorage to Portland | 2026-02-12 – 2026-03-17 | 34 | — |
| SEA→LAS Seattle to Las Vegas | 2023-10-01 – 2025-04-21 | 370 | 64.1% |
| LAS→SEA Las Vegas to Seattle | 2023-11-15 – 2024-09-30 | 171 | 70.6% |
| PAE→PHX Everett to Phoenix | 2023-11-23 – 2024-03-13 | 29 | — |
| PAE→LAS Everett to Las Vegas | 2024-01-11 – 2024-02-12 | 20 | — |
Because the same number has served different journeys, the statistics above describe only the route AS734 currently operates. Blending them would produce an average of two different flights.
Data and methodology
Calculated by FlyerIntel from 295 records of AS734 operating SLC → 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.