The Office of Primary Responsibility (OPR) for
this SOP is ZLA1. This SOP was originally proposed by Ryan Fretwell, SOCAL
Approach - San Diego Area Lead, and approved by the Los Angeles Center
Chief (ZLA1), Jeff Clark, on May 11, 2002.
a. San Diego Runway Use program
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.
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.
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. When required, SAN APP should advise CTR of any needed flow restrictions.
b. San Diego Sector Frequency Use
| SOCAL Approach - San Diego Area Combined |
119.60 |
| SOCAL Approach - San Diego Area West |
119.60 |
| SOCAL Approach - San Diego Area East |
124.35 |
| San Diego
Lindbergh Tower |
118.30 |
| San Diego Lindbergh Ground |
123.90 |
| San Diego Lindbergh Clearance
Delivery |
125.90 |
c. San Diego Airspace:
SOCAL Approach - San Diego Area shall own all
airspace at and below 13,000 MSL inside the lateral boundaries as depicted
on the TRACON
Graphic.
d. IFR Departure Traffic
Routing
Aircraft departing Lindbergh Field should generally be routed via one of the SIDs or via a TEC route. Each of the SIDs is pilot nav.
Runway 27 departures may use the BORDR, PEBLE, or POGGI SIDs. Runway 9 departures may use the BORDR or LYNSY SIDs. The LYNSY
SID is valid off runway 27; however, to keep departures separated from arrivals, runway 27 departures requesting the LYNSY
SID should be rerouted via the PEBLE departure.
SAN TWR shall assign IFR departures an initial altitude of 5,000' or their
requested cruise altitude, whichever is lower.
When traffic permits, all IFR departures shall be climbed to 13000' or their
requested cruise altitude, whichever is lower, by SAN DEP/APP and be handed off to the appropriate
Center sector.
e. IFR Arrival Traffic
Routing
1) Baret4 is an arrival from the east
and northeast with transitions from TNP, EED, PKE, and IPL. Aircraft
arriving on the TNP, EED, or PKE transitions will be instructed by
LAX_C_CTR to cross 25 NM northeast of the PGY VOR VORTAC at and
maintain 12,000' MSL. Aircraft arriving on the IPL transition will be
instructed by LAX_E_CTR to cross the PILLO intersection at and maintain
10000'.
2) Hubrd1 is an arrival from the
northwest with transitions from LAX and SXC. LAX_E_CTR will instruct
these arrivals to "CROSS CARDI AT AND MAINTAIN
15,000." SAN_APP has control for descent at CARDI intersection.
3) Shamu1 is an arrival from the northwest. This arrival shall be used when runway 9 is the active
runway for arrivals at San Diego Lindbergh Field. Aircraft will be told by
LAX_E_CTR to cross SHAMU at 15000' and 250 knots. SAN APP has
control for descent on these arrivals inside the lateral confines of the San Diego Sector Airspace.
f. VFR Traffic
VFR traffic departing from the airports within
the San Diego Class Bravo SURFACE area are to be issued a clearance to exit
the San Diego Class Bravo. If VFR aircraft transition between any of the
airports of San Diego Lindbergh Field, San Diego North-Island NAS, San Diego-
Montgomery, San Diego Miramar MCAS, or San Diego- Gillespee Field, a discrete
squawk code need not be issued.
If a VFR aircraft is requesting to climb
through San Diego Class Bravo to any point outside of San Diego Class
Bravo, issue a discrete squawk code prior to departure.
A discrete squawk code shall be assigned to all
other VFR aircraft requesting entry into the San Diego Class Bravo
airspace.
