Anchorage ARTCC #

General #

1. The following applies to all domestic areas:
   1. When issuing procedural altitude changes (for example, “Descend via” or “Climb via”), controllers must enter it into the data tag. Ideally, you use the gate altitude. QQ P130 <FLID>
   2. Aircraft arriving at uncontrolled fields shall have their data tags frozen over/near the airport to which they are arriving. This tag will remain in place until the aircraft cancels IFR or reports a missed approach. QH F <location> <FLID> This signifies to you and other controllers that the airspace is “closed”.
   3. Aircraft that get an IFR release from an uncontrolled field shell have data tags created at/near the airport from which they are departing. QT <location> <ACID> This signifies to you and other controllers that the airspace is “closed”.
   4. Aircraft arriving at airports with open towers that lie within terminal approach airspace shall have secondary positions opened so scratchpads can be used to coordinate arrival information with the towers.
   5. Aircraft arriving at uncontrolled fields shall be given the current METAR (minimum wind, visibility, sky conditions and altitude) prior to conducting the approach. Approach requests should be entered into the 4th line. QS ○<free text> <FLID>.
   6. Speed restrictions should be entered into the 4th line of the data tag. QS /<speed> <FLID>.

Areas #

Domestic (PAZA) #

High Area Combinations #

When High area is not staffed, sector 63 will combine with 3 and 13 as defined by their lateral boundaries, and sector 69 will combine to sector 9.

Sector 10 over 9 #

The area of Sector 10 overtop of 9 will be staffed as follows:

• If ZAN_10_FSS is online, they shall control that area, otherwise
• If ANC_69_CTR is online, they shall control that area, otherwise
• It shall be combined with Sector 9’s airspace

Oceanic (PAZO) #

Oceanic are two different sectors/areas that operate independently due to their size and distance apart.

Pacific Area #

Arctic Area #

Position Table #