Flight profile · Alaska Airlines
AS413
Chicago (ORD) to Portland (PDX) · scheduled 7:00 AM – 9:25 AM
How AS413 performs
510 operations, 2024-04-16 to 2026-06-30.
AS413 arrived on time 78.7% of the time, against 75.4% for all ORD → PDX flights — this specific departure is 3.2 percentage points better than the route as a whole.
Source: US DOT Bureau of Transportation Statistics · 510 operations between 2024-04-16 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| AS413 | 78.7% | 0.78% | -4 min | 4.7% | 510 |
| Alaska Airlines on ORD → PDX | 78.3% | 1.34% | -4 min | 5.4% | 1,493 |
| All ORD → PDX flights | 75.4% | 1.01% | -4 min | 8.1% | 7,164 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-04-16 to 2026-06-30
Other routes AS413 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→ANC Seattle to Anchorage | 2026-04-22 – 2026-06-09 | 49 | — |
| PDX→MSP Portland to Minneapolis | 2026-03-18 – 2026-04-21 | 34 | — |
| SLC→PDX Salt Lake City to Portland | 2026-02-12 – 2026-03-16 | 25 | — |
| PDX→SJC Portland to San Jose | 2026-01-07 – 2026-02-11 | 31 | — |
| LAX→IAD Los Angeles to Washington | 2024-03-09 – 2024-03-09 | 1 | — |
| BNA→SEA Nashville to Seattle | 2023-09-06 – 2024-01-08 | 2 | — |
| IAD→SEA Washington to Seattle | 2023-11-17 – 2023-11-17 | 1 | — |
Because the same number has served different journeys, the statistics above describe only the route AS413 currently operates. Blending them would produce an average of two different flights.
Data and methodology
Calculated by FlyerIntel from 510 records of AS413 operating ORD → PDX, 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.