Direct flights from Seattle (SEA) to Sitka (SIT): 7 nonstop departures observed each week across 1 airline. The nonstop covers 1,384 km, an estimated 2 hours 16 minutes in the air. Measured by Pro Flight Search from live flight boards at Seattle and Sitka. Updated 28 October 2026 at 23:22 UTC.
The SEA board at 16:22 shows departure at 16:25 instead of 15:47, gate C15.
Checked SEA board 16:22
route health from live SEA and SIT delay boards
Each mark is a scheduled departure at its origin-local time, observed operating in the last 7 days. Today is highlighted.
Flights AS67 15:47 daily
next sweep in 120s
Pro Flight Search records official board updates for nonstop SEA to SIT flights through the day: schedules, estimates, gate pushes and actual departures. The verdict above comes from operated flights, so it reflects what this route does rather than what the timetable promises.
Planning around a delay? Live airport delays · Weather delay risk map · Will a delayed flight be cancelled? · Do planes make up time in the air? · How we measure
Journalists, bloggers, and researchers may cite this page with attribution and a link to Pro Flight Search.
Pro Flight Search — Seattle (SEA) to Sitka (SIT) route reliability, measured from operated flights on official airport boards.
https://proflightsearch.com/search-flights/SEA-SIT
Mostly on schedule. The departure side at SEA is the weaker end, route health score 80/100. The airports section above carries the live status and delay window at both ends.
Great-circle distance is 1,384 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 128–149 min gate-to-gate on this route.
Alaska Airlines runs the route with about 7 flights a week (daily). Since one carrier owns the route, a single disruption tends to ripple through the day.
A blend of departure-side delay at SEA and arrival-side delay at SIT, computed from rolling delay windows (refreshed every 40 minutes) with a daily-rollup fallback. Current MVFR, IFR, or LIFR endpoint weather caps the score when flight rules can limit throughput. Higher is healthier: 100 means operations are clean at both ends.
.