San Diego Tower Local Control (TWR)

POC: Facility Advisory Board	Date: 2002-07-07
Code: ZLA-401	Version: 1.00

1. PURPOSE.

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working SAN Tower to
ensure that arrivals and departures are handled in as efficient and timely a manner as possible.

2. ROLES AND RESPONSIBILITIES.

The Office of Primary Responsibility (OPR) for this SOP is the Los Angeles Center Chief. This SOP was originally
signed by Jeff Clark, ZLA chief, and seconded by Dane Pennington, VATUSA Western Director on July 07, 2002.

3. DISTRIBUTION.

This SOP is intended for use by controllers staffing SAN Tower.

4. BACKGROUND.

Over time, controllers have found that defining standard procedures to be used by arriving and departing aircraft
provides for a more orderly traffic flow, and reduces the need for communication between SAN Ground, Tower and
Approach..

5. REQUIREMENTS.

a. Frequency:

SAN_TWR shall use 118.30 as it's normal frequency

b. Airspace:

SAN_TWR has been delegated that portion of the San Diego Class B Surface Area that is within 6nm of the SAN
airport, and up to and including 3,500 feet MSL. This delegation does not include airspace delegated to the Mont-
gomery airport or Naval Air Station North Island which lies outside the Class B surface area.

c. Special Instructions:

1. If gate holds are in effect, CD will advise aircraft of the estimated delay, and to contact GC for engine
start time. GC should not normally allow aircraft to start-up until 10 minutes prior to their release time.

2. IFR releases with SAN_APP shall be requested via the landline, specifying the aircraft ID and Departure
Procedure assigned to the aircraft. Releases, when granted, shall be valid for 3 minutes after being granted. If an aircraft fails to commence takeoff roll within 3 minutes of the release time, TWR must request a new release for that
aircraft before clearing it for takeoff.

3. VFR aircraft who are requesting flight following from DEP shall be assigned a squawk code and advised
to contact SAN DEP after departure. J & M class aircraft who are requesting flight following shall require
coordination for a VFR Release with DEP prior to clearing them for takeoff.

d. Runway configurations:

1. Normal configuration at SAN is to use RWY 27 for arrivals and departures, unless the wind is greater
than 15 knots, or the ceiling precludes the use of Runway 27 for instrument arrivals.

2. When wind is consistently greater than 15 knots from the east SAN Tower shall designate runway 9 as
being the active departure runway.

3. If the reported ceiling drops below 660' and/or the visibility decreases below 1 statute mile, then San
Diego will use runway 9 for arrivals. If the reported visibility drops below 300' and/or the visibility below 1 statute
mile, San Diego will use runway 27 for departures.

Note: During this situation, arrivals and departures are both occurring to the west of the field, and severe
delays will be expected. This is a process that must be coordinated with SAN Approach, SAN Departure, and LAX Center.

4. Pilots who are reluctant to accept the "runway in use" for whatever reason may be accommodated on
the opposite direction runway, as long as this is coordinated with approach. (Opposite direction departures cannot
be released automatically, and a specific release must be coordinated with SOCAL). If there will be a delay, advise
the pilot of how long this may be, and do your best to accommodate his/her needs.