12/1/2020 SOP Updates

Official news announcements from ZSE Staff

Moderator:ZSE Administrative Staff

Post Reply
Matthew Woerly
ZSE Air Traffic Manager
ZSE Air Traffic Manager
Posts:10
Joined:Tue Feb 11, 2014 3:18 pm
12/1/2020 SOP Updates

Post by Matthew Woerly » Mon Nov 30, 2020 4:34 pm

New SOP_104 for ZSE-P80 procedures.
The new ZSE SOP sets a standard for how aircraft should be handed off from ZSE to P80, and from P80 to ZSE. It should be mostly familiar from typical operations.

Updates to SOP_102 for the P80 are as follows:
  • T/P Category weights clarified to be maximum takeoff weight
  • T class clarified to also apply to aircraft with a MTOW of exactly 12,500 lb
  • Additional aircraft examples provided
  • Add airspace boundary section for consistency
  • PDX_TWR frequency changed from 123.775 to 123.770 to align with network rules
  • For closed traffic, coordinate with TWR before approving, and issue beacon code
  • All VUO departures to be cleared via “radar vectors BTG, then as filed”
  • Aircraft may push at pilot’s discretion unless they will be pushing onto an active taxiway or other movement area
  • Recommend heavy jets use 10R/28L for departure due to extra length
  • Change runway configuration criteria to be less restrictive and favor consistency along with TAF
  • Added scratchpad conventions for arrivals
  • VUO departures to be issued ODP if on board, otherwise via heading 360

Updates to SOP_103 for the S46 are as follows:
  • Weights clarified to be maximum takeoff weight
  • T class clarified to also apply to aircraft with a MTOW of exactly 12,500 lb
  • Additional aircraft examples provided
  • Define Seattle Local airspace as surface to 3000
  • Also use climb via SID for SUMMA (north flow)
  • For closed traffic, coordinate with TWR before approving, and issue beacon code
  • Departures only need a heading if they are not on any SID, including non-RNAV ones
Other minor wording, consistency, and formatting changes have also been incorporated.

Post Reply