ZLA Information:
VATSIM Disclaimer
ZLA Home Page
ZLA Crew Roster
ZLA Staff Members
News Archive
Event Archive
VATSIM Awards
Other ARTCCs
ZLA Forum

For Pilots:
Pilot Certifications
VFR/IFR Enroute Maps
Airports & Charts
ZLA TEC Routes
SimRoutes.com
Military Airfields
ZLA Weather
Submit Feedback

For Controllers:
Welcome to ZLA!
Become a Visitor
Training Materials
ATC Downloads
ATC Training Program
ZLA Test Study Guide
SOPs & LOAs
Position Restrictions
Global Rating Airports
TEC Route Lookup
Vectoring Diagrams
Airspace Maps
ZLA Mentor List
Top Ten Controllers
Controller Login




San Diego Tower Local Control (SAN)

POC: Facility Advisory Board

Date: 2008-10-07

Code: ZLA-401

Version: 1.10

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 its 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 Montgomery 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. San Diego Lindbergh Field shall normally use runway 27 for departures and arrivals unless the wind is out of the east at 10 knots or greater, at which time runway 9 shall be the active runway, regardless of visibility.

2. If the reported ceiling drops below 700' and/or the visibility decreases below 2 statute miles, then San Diego shall use runway 9 for arrivals and departures.

3. If the reported ceiling drops below 300' and/or the visibility below 1 statute mile, San Diego will use runway 9 for arrivals and runway 27 for departures. During this situation, arrivals and departures will both occur west of the field, and delays should be expected.



Copyright © laartcc.org 2006-2010. The information contained on all pages of this website is to be used for flight simulation purposes only on the VATSIM network. It is not intended nor should it be used for real world navigation. This site is not affiliated with the FAA, the actual Los Angeles ARTCC or any governing aviation body. All content contained herein is approved only for use on the VATSIM network.


Click here for ZLA Credits, Copyrights and Acknowledgements