Flight profile · Alaska Airlines
AS406
Seattle (SEA) to Washington (IAD) · scheduled 10:00 AM – 6:00 PM
How AS406 performs
838 operations, 2023-07-01 to 2026-06-30.
AS406 arrived on time 75.7% of the time, against 81.3% for all SEA → IAD flights — this specific departure is 5.7 percentage points worse than the route as a whole. Against Alaska Airlines’s own flights on this route it is 3.1 points worse.
Source: US DOT Bureau of Transportation Statistics · 838 operations between 2023-07-01 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| AS406 | 75.7% | 1.07% | 0 min | 4.0% | 838 |
| Alaska Airlines on SEA → IAD | 78.8% | 0.47% | -3 min | 3.4% | 2,532 |
| All SEA → IAD flights | 81.3% | 1.12% | -6 min | 5.2% | 6,313 |
Source: FlyerIntel analysis of US DOT BTS data · 2023-07-01 to 2026-06-30
Other routes AS406 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→DTW Seattle to Detroit | 2026-05-13 – 2026-06-09 | 28 | — |
| SEA→GEG Seattle to Spokane | 2026-04-22 – 2026-05-12 | 21 | — |
| GEG→SEA Spokane to Seattle | 2026-03-18 – 2026-03-18 | 1 | — |
| IAD→SEA Washington to Seattle | 2024-02-15 – 2026-03-16 | 381 | 65.7% |
| SEA→PDX Seattle to Portland | 2025-12-02 – 2025-12-17 | 16 | — |
| SEA→MSO Seattle to Missoula | 2025-10-26 – 2025-11-20 | 25 | — |
Because the same number has served different journeys, the statistics above describe only the route AS406 currently operates. Blending them would produce an average of two different flights.
Data and methodology
Calculated by FlyerIntel from 838 records of AS406 operating SEA → IAD, 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.