| Version | 1 |
| Created | 03/19/2016 03:50 |
| Last Updated | 09/04/2016 05:31 by Blake Nahin |
2009-06-01
SOP-304
1.10
Facility Advisory Board (FAB)
This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working S46 TRACON Seattle Approach (SEA_Y_APP), the primary airport KSEA, and satellite airports, to ensure that traffic flows are handled in as efficient and timely a manner as possible. By specifying standard handoff points, departure and arrival routes, coordination between adjacent facilities may be greatly reduced.
The Office of Primary Responsibility (OPR) for this SOP is the ZSE Facility Advisory Board. This SOP shall be maintained, revised, updated or cancelled by the ZSE Facility Advisory Board. Any suggestions for modification / amendment to this SOP should be sent to the FAB for review.
This SOP is intended for use by controllers staffing positions within S46 TRACON sector airspace, as well as controllers working at positions interfacing with S46 TRACON sector facilities.
Over time, controllers have found that having aircraft arrive via pre-approved arrival routes, either by STAR (Standard Terminal Arrival Routes) or via vectors through pre-determined arrival fixes, provides for a more orderly traffic flow, and reduces the need for communication between S46 TRACON and ZSE Center positions. It is also vitally important that all facilities understand what an airplane is going to do (i.e., what altitude he has been cleared to) when he approaches an adjacent controller's airspace. These procedures outline what instructions pilots will be issued as they go from controller to controller.
1. During Normal (South) operations separate Departures, sequence S46 Satelite airport Arrivals, and handle Tower operations for designated airports.
2. During North operations separate Departures, sequence S46 Satelite airport Arrivals, and handle Tower operations for designated airports.
a. Frequencies and Callsigns
1. Seattle Yankee Sector Approach/Departure (SEA_Y_APP) sector shall use 120.40 as its frequency and SEA_Y_APP as text callsign.
2. When handling arrivals and transitions, S46 TRACON shall use "Seattle Approach" as voice callsign. When handling departures, S46 TRACON shall use "Seattle Departure" as voice callsign.
3. Frequencies for secondary airports should be determined from appropriate publications.
b. Airspace and Sectorization Plan:
1. SEA_Y_APP shall own the airspace within the lateral limits depicted on the S46 TRACON, SEA_Y_APP shall own all airspace not owned by other sectors of S46 Approach.
2. The Sector file authorized for use in operating this sector is the certified S46 PRO or ZSE Center sector file available on the "downloads" page of the ZSE ARTCC web site.
3. In a two person split of S46 TRACON;
a. SEA_W_APP shall operate SEA_E_APP and SEA_F_APP sectors as well still using the text callsign of SEA_W_APP
b. SEA_Y_APP shall operate SEA_Y_APP sector.
c. Release Procedures and Runway Use Plans
1. The active runway plan will be determined by SEA_TWR and BFI_TWR per SOP_100. Normal operations during calm winds shall be to land south unless winds greater than 5 knots exist.
2. S46 TRACON may require IFR departure releases to be requested by a TWR inside S46.
d. Special Instructions:
1. Aircraft arriving on flight plans indicating NO STAR (or those that have not filed for an approved STAR) shall have their clearances amended to approved STAR listed in this SOP, so that all traffic is placed on consistent arrivals streams.
2. Aircraft filing NO SID (or those that have not filed for an approved SID) shall be have their clearances amended to approved SID listed in this SOP, so that all traffic is placed on consistent departure stream.
3. If SEA_TWR is not online, SEA_Y_APP shall assume control of the SEA_TWR position.
4. If BFI_TWR is not online, SEA_Y_APP shall assume control of the BFI_TWR position.
e. Normal / South Flow Operations - Arrivals:
1. Satelite Airport arrivals are received from SEA_A_CTR. Aircraft shall be vectored and sequenced into arrival airport. Point-outs may be requested from SEA_Y_APP to feeder sectors.
SPECIAL NOTE: If conditions exist that BFI is landing North while Seattle is landing South, BFI arriving aircraft for Runway 31 shall be handled by SEA_Y_APP.
2. SEA Missed Approaches are passed by SEA_TWR to SEA_Y_APP for resequencing. SEA_Y_APP shall coordinate with SEA_F_APP to vector aircraft in proper position for a handoff to SEA_F_APP.
3. BFI Missed Approaches Landing South when SEA also landing South are passed by BFI_TWR to SEA_Y_APP for resequencing. SEA_Y_APP shall coordinate with SEA_F_APP to vector aircraft in proper position for a handoff to SEA_F_APP. BFI_TWR must immediately let SEA_F_APP and SEA_TWR know of an aircraft declaring missed approach due to conflict it causes with Seattle Arriving aircraft. SEA_TWR may issue go-arounds with climbouts or SEA_F_APP may cancel approach clearances and resequence aircraft to avoid conflict.
a. BFI Missed Approaches Landing North when SEA is landing South are passed by BFI_TWR to SEA_F_APP for vectoring clear of arriving aircraft and shall coordinate with SEA_Y_APP to vector aircraft in proper position for a handoff to SEA_Y_APP. BFI_TWR must immediately let SEA_F_APP and SEA_TWR know of an aircraft declaring missed approach due to conflict it causes with Seattle Arriving aircraft. SEA_TWR may issue go-arounds with climbouts or SEA_F_APP may cancel approach clearances and resequence aircraft to avoid conflict.
f. Normal (South Flow) Operations - Departures:
1. BANGR#, ELMAA#, HAROB#, SUMMA# departures may proceed via pilot navigation. Departures shall be monitored to avoid conflict with arriving aircraft. If conflict is unavoidable, vector the departure aircraft off of the procedure to avoid conflict, leaving the arriving aircraft on proper course inbound, and then vector departure aircraft back to rejoin procedure.
2. SEATL# and MTN# departures are vector procedures. SEA_Y_APP shall vector and clear departing aircraft direct to assigned fix (even if outside of S46 airspace), ensuring separation while in S46. If SEA_Y_APP is unable to clear aircraft direct to assigned fix due to on course heading would cause conflict, aircraft shall be given best possible heading in direction of fix. SEA_Y_APP shall let SEA_A_CTR know that aircraft has not been cleared direct assigned fix due to possible conflict.
3. BFI KENNT# Departures(or NEEDL# if in North Ops) are vector procedures. SEA_Y_APP shall vector and clear departing aircraft direct to assigned fix (even if outside of S46 airspace), ensuring separation while in S46. If SEA_Y_APP is unable to clear aircraft direct to assigned fix due to on course heading would cause conflict, aircraft shall be given best possible heading in direction of fix. SEA_Y_APP shall let SEA_A_CTR know that aircraft has not been cleared direct assigned fix due to possible conflict.
g. North Flow Operations - Arrivals:
1. Satelite Airport arrivals are received from SEA_A_CTR. Aircraft shall be vectored and sequenced into arrival airport. Point-outs may be requested from SEA_Y_APP to feeder sectors.
SPECIAL NOTE: If conditions exist that BFI is landing South while Seattle is landing North, BFI arriving aircraft for Runway 13 shall be handled by SEA_Y_APP.
2. SEA Missed Approaches are passed by SEA_TWR to SEA_Y_APP for resequencing. SEA_Y_APP shall coordinate with SEA_F_APP to vector aircraft in proper position for a handoff to SEA_F_APP.
3. BFI Missed Approaches Landing North when SEA also landing North are passed by BFI_TWR to SEA_Y_APP for resequencing. SEA_Y_APP shall coordinate with SEA_F_APP to vector aircraft in proper position for a handoff to SEA_F_APP. BFI_TWR must immediately let SEA_Y_APP and SEA_TWR know of an aircraft declaring missed approach due to conflict it causes with Seattle Departing aircraft. SEA_TWR may cancel takeoff clearances or SEA_Y_APP may immediately vector departing aircraft upon radar contact to avoid conflict.
a. BFI Missed Approaches Landing South when SEA is landing North are passed by BFI_TWR to SEA_F_APP for vectoring clear of arriving aircraft and shall coordinate with SEA_Y_APP to vector aircraft in proper position for a handoff to SEA_Y_APP. BFI_TWR must immediately let SEA_Y_APP and SEA_TWR know of an aircraft declaring missed approach due to conflict it causes with Seattle Departing aircraft. SEA_TWR may cancel takeoff clearances or SEA_Y_APP may immediately vector departing aircraft upon radar contact to avoid conflict.
h. North Flow Operations - Departures:
1. BANGR#, HAROB#, SUMMA# departures may proceed via pilot navigation. Departures shall be monitored to avoid conflict with arriving aircraft and BFI aircraft. If conflict is unavoidable, vector the departure aircraft off of the procedure to avoid conflict, leaving the arriving aircraft on proper course inbound, and then vector departure aircraft back to rejoin procedure.
2. SEATL# and MTN# departures are vector procedures. SEA_Y_APP shall vector and clear departing aircraft direct to assigned fix (even if outside of S46 airspace), ensuring separation while in S46. If SEA_Y_APP is unable to clear aircraft direct to assigned fix due to on course heading would cause conflict, aircraft shall be given best possible heading in direction of fix. SEA_Y_APP shall let SEA_A_CTR know that aircraft has not been cleared direct assigned fix due to possible conflict.
3. BFI NEEDL# Departures(or KENNT# if in South Ops) are vector procedures. SEA_Y_APP shall vector and clear departing aircraft direct to assigned fix (even if outside of S46 airspace), ensuring separation while in S46. If SEA_Y_APP is unable to clear aircraft direct to assigned fix due to on course heading would cause conflict, aircraft shall be given best possible heading in direction of fix. SEA_Y_APP shall let SEA_A_CTR know that aircraft has not been cleared direct assigned fix due to possible conflict.
4. KMORE# and KTSAP# departures may proceed via pilot navigation. Departures shall be monitored to avoid conflict with arriving aircraft and BFI aircraft. If conflict is unavoidable, vector the departure aircraft off of the procedure to avoid conflict, leaving the arriving aircraft on proper course inbound, and then vector departure aircraft back to rejoin procedure. NOTE: THESE DEPARTURE PROCEDURES ARE TO BE USED DURING NOISE ABATEMENT HOURS ONLY.
i. Charted Visual Approaches:
Charted Visual Approaches may be used as needed depending on traffic levels and weather conditions. SEA_W_APP and SEA_E_APP must coordinate any charted visual approach clearances with SEA_F_APP. SEA_F_APP may not allow Charted Visual approaches at any time due to traffic levels or other factors.
j. Additional Comments:
1. 2 CONTROLLER SECTORIZATION OF S46 MUST BE APPROVED BY CIC OR ATM FOR AUTHORIZED EVENT OR HIGH LEVELS OF TRAFFIC. SEA_W_APP AND SEA_Y_APP ARE TO BE USED IN 2 CONTROLLER SECTORIZATION WHERE SEA_W_APP ALSO HAS SEA_E_APP AND SEA_F_APP SECTORS.
2. 4 CONTROLLER SECTORIZATION IS TO BE ONLY APPROVED BY ATM FOR EVENTS OR OTHER PURPOSE.