Document Information
Version 1
Created 01/01/2016 00:46
Last Updated 05/18/2018 17:47
by Austin Wilkins

Purpose

This Standard Operating Procedure (SOP) outlines the procedures to be used by all ZSE controllers working the SEA Tower Control position. It ensures that all departures and arrivals are handled in a timely and efficient manner. This SOP shall be maintained, revised, updated or canceled by the Seattle Air Traffic Manager, Deputy Air Traffic Manager, or Training Administrator. Seattle Tower Control shall operate under the call sign as SEA_TWR. The frequency to use is 119.90. I.

Position Description

 Seattle Tower Airspace

SEA_TWR, also known as the Local Controller, owns all the airspace from the ground up to, but not including, 3,000 feet MSL and 5 miles radius from the center of KSEA (see graphic below). Normally, this excludes the areas around KBFI (Boeing Field) and KRNT (Renton Field).  In the absence of the SEA_DEL and SEA_GND,SEA_TWR shall issue all IFR/VFR clearances and taxi instructions.

 

 

 

 

 

 

II. Duties Below are some of the duties of the SEA_TWR controller:[list][*]Determine the position of an aircraft before issuing taxi instructions or takeoff/landing clearance

  1. Maintain proper sequencing and separation of aircraft in the local airspace
  2. Determine runway(s) in use and relay information to SEA_APP or SEA_CTR controller
  3. Coordinate with SEA_GND for ground movements and runway crossings
  4. Coordinate with SEA_APP/SEA_DEP for handoffs

III. Coordination between SEA_TWR and SEA_GND
SEA_TWR and SEA_GND shall exchange information as necessary for the safe and efficient use of airport runways and movement areas. SEA_TWR has primary responsibility for operations conducted on the active runway and must control the use of those runways.

  1. SEA_GND shall notify SEA_TWR of any aircraft taxied to an intersection for takeoff, unless the departure from that intersection is specifically designated via prior coordination.

  2. The SEA_TWR shall coordinate with the SEA_GND before using a runway not previously designated as active.

IV. Runway Selection

Use the runways most nearly aligned with the wind when the wind is 6 knots or more, or the "calm wind" runways (16R and 16C and 16L) when 5 knots or less. For Seattle-Tacoma: South Flow Winds are calm (5 knots or less) or winds are greater than 5kts from a heading of 070° clockwise to 250°

  • 16L and 16C - Departures
  • 16L and 16R - Arrivals

North Flow Winds are 6kts or more from a heading of 251° clockwise to 069°

  • 34R and 34C - Departures
  • 34L and 34R - Arrivals

NOTE- If a pilot prefers to use a runway different from that specified, the pilot is expected to advise ATC. 

V. Seattle Class D Airspace

Seattle Class D (Delta) airspace extends out to 5 miles from the center of the airport and up to 3,000 feet MSL. VFR pilots are required to establish two-way radio communications before entering the Class D airspace. If you respond to their radio call with, "N182D standby," radio communications have been established and the pilot can enter the Class D airspace. If workload or traffic conditions prevent the immediate provision of Class D services, inform the pilot to remain outside the Class D airspace until conditions permit the services to be provided.

SEA_CLS_B_VS_CLS_D

 

Seattle has a VFR “Transition Route" that goes directly over the field at or below 2000 feet MSL. Pilots are required to establish radio communications with SEA_TWR in order to proceed to cross. See Seattle VFR Transitions Document.

VI. Seattle Class B Airspace

This airspace overlies Seattle-Tacoma Intl and several other airports. It is centered on KSEA. The surface area extends out to about 10 miles with two outer layers extending about 20 and 30 miles out with a final ceiling of 10,000 feet MSL. Pilots are required to establish two-way radio communications AND obtain ATC approval before entering the Class B airspace. Seattle_Class_B

Unless prior coordination has been made you must receive approval from SEA_APP or SEA_DEP for VFR aircraft to operate within Seattle Class Bravo airspace. This airspace is the area denoted below the ceiling and above the floor on sectional charts. It is denoted on Terminal Area Charts/Sectionals as 100 Class Bravo Ceiling  30 Class Bravo Floor It is possible for aircraft to operate while under the floor of Class Bravo and not receive ATC approval. If the aircraft will be operating below Class Bravo floor AND inside your 5-mile airspace then it is a good idea to advise SEA_APP or SEA_DEP that you have control of that aircraft.

VII. Departure Control Procedures

A release from SEA_DEP or SEA_APP control is required for each departure when departure releases are in effect. When the aircraft is “gear up" (starting to climb), instruct the aircraft to contact SEA_DEP or SEA_APP, unless further communication with you is required. Try not to delay the transfer of communications more than about 1/2 mile beyond the runway end. This is to allow for prompt communications with DEP/APP.

VIII. Line up and Wait (aka. Taxi into position and hold)

The intent of taxi into position and hold is to position aircraft for an imminent departure. Authorize an aircraft to taxi into position and hold when takeoff clearance cannot be issued because of traffic (for example, another aircraft just took off and you need to provide spacing). Issue traffic information to any aircraft so authorized. Traffic information may be omitted when the traffic is another aircraft of which has already landed on or just took off the same runway and is clearly visible to the holding aircraft. Do not use conditional phrases such as "behind landing traffic" or "after the departing aircraft." First state the runway number followed by the taxi into position clearance when more than one runway is active.  SEA_TWR: ASA655, runway 16C, lineup and wait, traffic will cross downfield. When an aircraft is authorized to taxi into takeoff position to hold, inform it of the closest traffic that is cleared to land, touch-and-go, stop-and-go, or unrestricted low approach on the same runway or on a close parallel runway. SEA_TWR: ASA655, runway 16C, lineup and wait. Traffic is a Boeing 737, six-mile final for runway 16L. Do not authorize an aircraft to line up and wait at an intersection between sunset and sunrise (local time at the airport in real life). This is because it is very difficult for other aircraft to see each other. When a Tower controller delivers or amends an ATC clearance to an aircraft awaiting departure and that aircraft is holding short of a runway or is holding in position on a runway, an additional clearance shall be issued to prevent the possibility of the aircraft inadvertently taxiing onto the runway and/or beginning takeoff roll. In such cases, append one of the following ATC instructions as appropriate: 1. Hold short of runway 16L 2. Hold in position

IX. Same runway separation

Separate a departing aircraft from a preceding departing or arriving aircraft using the same runway by ensuring that it does not begin takeoff roll until:

  • The other aircraft has departed and crossed the runway end or turned to avert any conflict.
  • A preceding landing aircraft is clear of the runway.
  • Ensure at least 5nm between successive IFR departures.

X. Takeoff Clearance

When more than one runway is active issue the current winds, followed by the runway number, and then the takeoff clearance: SEA_TWR: N7RX, wind 170 at 8, runway 16L, cleared for takeoff When an aircraft is cleared for takeoff, inform it of the closest traffic within 6 miles on final approach to the same runway. Do not forget to subtract 20 degrees from the METAR-reported wind, per the "True vs. Magnetic Wind" Document XI. Landing information for VFR aircraft Provide current landing information, as appropriate, to VFR aircraft that enter the KSEA Class D without talking to SEA_APP. Landing information contained in the ATIS broadcast may be omitted if the pilot states the appropriate ATIS code. [b]If the pilot does not report the current ATIS code, be sure to issue the local altimeter.[/b] Issue landing information by including the following:

  • Specific traffic pattern information for aircraft proceeding visually.

SEA_TWR: N835W, enter left base runway 34L
SEA_TWR: N835W, make straight in runway 34R
SEA_TWR: N835W, enter left downwind runway 16L

  • Surface wind (remember, subtract 20 degrees!)
  • Altimeter setting
  • Any supplementary information. 
  • Runway in use. 
  • Clearance to land or for the "optHandoffion" (when appropriate) 
  • Requests for geographical position reports. Use this cautiously as there are different Flight Simulator versions and/or scenery add-ons out and all may not accurately depict visual checkpoints.

Pilot reports in without acknowledging the current ATIS code SEA_TWR: N835W, wind 140 at 4, Seattle altimeter 2998, enter right downwind runway 16C. Pilot reports in with the current ATIS code SEA_TWR: N835W, wind 140 at 4, enter right downwind runway 16C. NOTEi - At some locations, VFR checkpoints are depicted on sectional aeronautical and terminal area charts. In selecting geographical fixes, depicted VFR checkpoints are preferred unless the pilot exhibits a familiarity with the local area.

XII. Same runway separation

Separate an arriving aircraft from another aircraft using the same runway by ensuring that the arriving aircraft does not cross the landing threshold until one of the following conditions exists:[list][*]The other arriving aircraft has landed and is clear of the runway.

  • The other aircraft has departed and crossed the runway end. 
  • When the succeeding aircraft is a helicopter, visual separation may be applied in lieu of using distance minima.

XIII. Wake Turbulence

Issue wake turbulence advisories, and the position, altitude if known, and the direction of flight.

  • a heavy jet or B757 to aircraft landing behind a departing or arriving heavy jet or B757 on the same or parallel runways separated by less than 2,500 feet. (KSEA's runways are separated by 600 feet.)
  • a large aircraft to a small aircraft landing behind a departing or arriving large aircraft on the same or parallel runways separated by less than 2,500 feet.

SEA_TWR: COA534, wind 340 at 10, runway 34C, cleared to land, caution wake turbulence, heavy Boeing 747 departing runway 34C. SEA_TWR: COA534, wind 340 at 10, runway 34L, cleared to land. Number two following a Boeing 757 on two-mile final, caution wake turbulence.

XIV. Landing clearance

Issue landing clearance, including the winds. Restate the landing runway whenever more than one runway is active, or an instrument approach is being conducted to a closed runway. Multiple active runways in use SEA_TWR: S1212, wind calm, runway 16R, cleared to land

XV. Runway exiting

After landing advise the aircraft to hold short of a runway or taxiway if required for traffic. Handoff to Ground once the aircraft is clear of all active runways. Runway exiting or taxi instructions should not normally be issued to an aircraft prior to, or immediately after, touchdown. NOTE:

  1. An aircraft is expected to taxi clear of the runway unless otherwise directed by ATC. Pilots shall not exit the landing runway on to an intersecting runway unless authorized by ATC. In the absence of ATC instructions, an aircraft should taxi clear of the landing runway by clearing the hold position marking associated with the landing runway even if that requires the aircraft to protrude into or enter another taxiway/ramp area. This does not authorize an aircraft to cross a subsequent taxiway or ramp after clearing the landing runway.
  2. The pilot is responsible for ascertaining when the aircraft is clear of the runway by clearing the hold position marking associated with the landing runway.

SEA_GND and SEA_TWR shall protect a taxiway/runway/ramp intersection if an aircraft is required to enter that intersection to clear the landing runway.
Request a readback of runway hold short instructions when not received from the pilot. SEA_TWR: NWA27, hold short runway 34C, traffic departing NWA27: Roger SEA_TWR: NWA27, please read back hold short instructions Read back hold instructions phraseology may be initiated for any point on a movement area when the controller believes the readback is necessary. Once the runway is clear, instruct the holding aircraft to cross the active runway. SEA_TWR: NWA27, cross runway 34R, then contact Ground on 121.70, good day. Handoff aircraft to Ground once they are clear of all active runways. If no holds are anticipated then instruct the aircraft to cross all active runways then contact Ground. SEA_TWR: JBU466, cross runway 34R, then contact Ground on 121.70, good day.

XVI. Missed approach/go around procedures

A pilot on an IFR flight plan making an instrument approach may execute a missed approach if they are unable to safely descend to the runway due to weather or other factors. If a pilot reports a missed approach, instruct the pilot as follows: SEA_TWR: COA134, fly runway heading, climb and maintain 5,000, contact Approach on 119.20. A pilot on a VFR flight or IFR flight performing a visual approach may initiate a go-around procedure if they are unable to safely descend to the runway. Such aircraft should be instructed to over-fly the field and maintain runway heading. All aircraft calling for a missed approach or a go-around at KSEA shall be given runway heading and to climb to 5000 ft and then handed over to Departure/Approach for re-sequencing.