Flight profile · Alaska Airlines

AS334

Seattle (SEA) to Atlanta (ATL) · scheduled 6:30 AM – 6:32 PM

FlyerIntel does not track flights in the air. This page describes how AS334 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 AS334 performs

851 operations, 2023-07-01 to 2026-06-30.

On-time arrivals
77.1%
642 of 833 completed
Cancellation rate
1.53%
13 cancelled
Median arrival delay
-4 min
Average 2.1 min
Severe delays
4.0%
Arrived 60+ minutes late
Delay when late
41 min
Average, when 15+ min late
Departure punctuality
78.2%
Left the gate on time

AS334 arrived on time 77.1% of the time, against 82.0% for all SEAATL flights — this specific departure is 5.0 percentage points worse than the route as a whole.

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

Against the rest of the route

On timeCancelledMedian delaySevereFlights
AS33477.1%1.53%-4 min4.0%851
Alaska Airlines on SEAATL77.4%0.88%-3 min4.4%3,053
All SEAATL flights82.0%0.76%-7 min4.6%10,247

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

Other routes AS334 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.

RouteOperatedFlightsOn time
ATLSEA Atlanta to Seattle2023-07-012025-08-1915854.9%
SEASFO Seattle to San Francisco2025-03-192025-03-191

Because the same number has served different journeys, the statistics above describe only the route AS334 currently operates. Blending them would produce an average of two different flights.

Data and methodology

Calculated by FlyerIntel from 851 records of AS334 operating SEAATL, 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