Flight profile · Alaska Airlines

AS386

Seattle (SEA) to Minneapolis (MSP) · scheduled 6:45 PM – 11:59 PM

FlyerIntel does not track flights in the air. This page describes how AS386 has historically performed, which is a different and more useful question when you are deciding what to book. For today’s status, check with Alaska Airlines.

How AS386 performs

997 operations, 2023-07-01 to 2026-06-09.

On-time arrivals
77.5%
766 of 988 completed
Cancellation rate
0.90%
9 cancelled
Median arrival delay
-3 min
Average 4.5 min
Severe delays
4.9%
Arrived 60+ minutes late
Delay when late
47 min
Average, when 15+ min late
Departure punctuality
74.3%
Left the gate on time

AS386 arrived on time 77.5% of the time, against 85.8% for all SEAMSP flights — this specific departure is 8.3 percentage points worse than the route as a whole. Against Alaska Airlines’s own flights on this route it is 1.7 points worse.

Source: US DOT Bureau of Transportation Statistics · 997 operations between 2023-07-01 to 2026-06-09

Against the rest of the route

On timeCancelledMedian delaySevereFlights
AS38677.5%0.90%-3 min4.9%997
Alaska Airlines on SEAMSP79.2%0.82%-2 min4.0%2,802
All SEAMSP flights85.8%0.57%-8 min3.3%8,050

Source: FlyerIntel analysis of US DOT BTS data · 2023-07-01 to 2026-06-09

By day of week

Does AS386 run worse on particular days?

Monday77.8%
Tuesday81.2%
Wednesday79.6%
Thursday75.5%
Friday74.3%
Saturday
Sunday74.5%

Tuesday is historically the most reliable day and Friday the least, a gap of 6.9 percentage points.

Source: FlyerIntel analysis of US DOT BTS data · 2023-07-01 to 2026-06-09 · Days with fewer than 120 operations are not scored.

Data and methodology

Calculated by FlyerIntel from 997 records of AS386 operating SEAMSP, 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.

Full methodology · Report a problem