SOCAL Approach Burbank Area (BUR)

POC: Facility Advisory Board	Date: 2008-07-25
Code: ZLA-250	Version: 1.11

1. PURPOSE.

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working SOCAL Approach - Burbank Area to ensure that arrival and departure flows are handled in as efficient and timely a manner as possible. By specifying standard handoff points, departure routes, and arrival routes, coordination between SOCAL Approach and ZLA Center sectors may be greatly reduced.

2. ROLES AND RESPONSIBILITIES.

The Office of Primary Responsibility (OPR) for this SOP is the ZLA Facility Advisory Board. This SOP was originally signed by Paul Biderman, Burbank TRACON Lead, and Jeff Clark, ZLA Chief on 4/21/02, and updated by Jeff Clark on September 30, 2002. This SOP shall be maintained, revised, updated or cancelled by the ZLA Facility Advisory Board or any organization that supersedes, replaces or assumes the FAB responsibilities. Any suggestions for modification/amendment to this SOP should be sent to the FAB for review.

3. DISTRIBUTION.

This SOP is intended for use by controllers staffing SOCAL Approach - Burbank Area, as well as controllers working at SOCAL Approach positions interfacing with SOCAL Approach - Burbank Area.

4. BACKGROUND.

Due to its configuration, surrounding geography, and proximity to LAX, Burbank is one of the more difficult tracons to work in ZLA. Over time, controllers have found that having aircraft arrive and depart via pre-approved routes, either by STAR's (Standard Terminal Arrival Routes), SID's (Standard Instrument Departures) or via vectors through pre-determined procedures, provides for a more orderly traffic flow, and reduces the need for communication between SOCAL Approach - Burbank Area and other SOCAL TRACON Areas and ZLA 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.

5. REQUIREMENTS.

a. Frequency:

SOCAL Approach - Burbank Area shall use 134.2 as its frequency. SOCAL Approach - Burbank Area (BUR_APP) normally will be able to fulfill the duties of Burbank Departure (BUR_DEP) except in heavy traffic situations.

b. Airspace:

SOCAL Approach - Burbank Area shall own the entire airspace labeled as BUR_APP on the TRACON graphic, at and below 13,000' MSL. BUR_APP also owns the area underlying the LAX_APP shelf from the surface to, but not including, 10,000' as shown on the graphic.

c. Special Instructions:

1. Aircraft filing "NO STAR" (or those that have not filed for an approved STAR) or "NO SID" shall be vectored as if on one of the following approved STAR's or SID's. This is CRITICAL for Burbank operations so as to not interfere with other SOCAL TRACON operations.

2. The procedures outlined below assume that all sectors and sub-sectors are open. If any are closed, the controller owning the airspace in question acts according to the SOP for aircraft in his sector.

3. Unless the wake turbulence application would dictate a larger in-trail separation, once established on the BUR 8 localizer, aircraft within SOCAL Approach may use the minimum in-trail separation standard of 3 miles.

d. Burbank Airport Runway Configurations and Procedures:

Acceptable Runway Configurations

The "8/15" configuration:

Runway 8- The ELMOO5 departure may ONLY be issued when weather conditions are equal to or better than a ceiling of 2,100 feet and 2 miles visibility. The VNY7 departure may ONLY be issued when weather conditions are equal to or better than a ceiling of 2,100 feet and 3 miles visibility due to terrain east of the runway. Note that runway 8 may be used at any time for IFR departures! This "rule" only applies to IFR departures who are cleared via a standard DP!

Runway 15- No restrictions.

The "8/33" configuration:

Runway 8- See above IFR restrictions.

Runway 33- Used sometimes for high wind conditions when winds are out of the NE or NW above 10 kts.

The "33/26" configuration:

Runway 26 - Sometimes used for departures of aircraft who park at the gates at the east side of the terminal, such as SWA and AAL flights, even if the winds don't favor this runway. Most of the time, this occurs late at night when the aircraft wants to depart quicker.

Runway 33- Used sometimes for high wind conditions when winds are out of the NE or NW above 10 knots.

The "Straight 33" configuration:

Runway 33 - ONLY used for strong NW winds due to its extreme difficulty to manage. Departures and arrivals may typically get backed up in this configuration.

e. Normal Operations

Departures

1. VNY7 departures have different requirements based on runway in use. However, in ALL cases, staying north of the SADDE6 arrivals into LAX is CRITICAL! Because of this, runway 8 runway 15 departures MUST begin their climbing right turn IMMEDIATELY to a heading of 210. This is the most critical portion of this procedure. All others are expected to execute the SID as published.

2. ELMOO5 departures also have specific requirements based ondeparture runway. Just like the VNY7 procedure, departing aircraft MUST stay north of SADDE6 arrivals. Therefore, departures from runway 15 or 26 MUST begin their climbing left turn to a heading of 110 IMMEDIATELY! All others should expect to fly the SID as published.

3. There are a few VFR "Standard Departures" that pilots familiar with the area may ask for:

• Golden State Departure: Clearance should read "After departure intercept and parallel the Golden State Freeway North westbound until advised. Keep the freeway off your right at all times. Departure frequency 134.2, squawk xxxx"
• Rose Bowl Departure: Clearance should read "After departure, proceed on course southeast bound. Maintain VFR at or below 2,500 until advised. Departure frequency 134.2 squawk xxxx"
• Mendenhall Departure: Clearance should read "After departure proceed northbound direct Mendenhall peak". This procedure is only assigned when the pilot requests.

IFR arrival traffic routing

1) FERN STAR is an arrival from the north-west, received from LAX_A_CTR, crossing PIRUE/BAILL at 11,000', or CANYN at 9,000'.

2) LYNXX STAR is an arrival from the north-east, received from LAX_B_CTR, crossing JANNY at 8,000'.

3) KIMMO STAR arrivals to LAX and SMO will be received from B_CTR. Aircraft on the LHS transition will be assigned 14,000'. Aircraft on the PMD transition will be assigned an altitude between 8000' and 14,000'.

f. Burbank Airport Missed Approach Procedures:

1. Missed approaches should be instructed to fly heading 210, and climb to 3000'. This is CONTRARY to some of the published approaches, but is necessary to avoid conflicts with LAX APP. There is an LOA between B90 tracon and Burbank Tower regarding this issue.

g. LAX CASTA departures and aircraft bound for the LAX R-323 / V23:

CASTA departures from LAX will be flying a pilot navigated route and only need to be climbed to 13,000'. Aircraft bound for the LAX R-323 shall be handed to BUR APP from LAX_DEP heading 360 climbing to or level at 6,000. BUR APP shall vector aircraft to join the LAX R-323/V23 and climb aircraft to 13,000 or their requested cruise altitude, whichever is lower.

h. Santa Monica Arrivals

1. Burbank approach shall control all VOR-A approaches into SMO.

2. Before granting VOR-A approach clearance Burbank must receive a pointout from Departure and SoCal Approach (North) sectors.

3. SoCal Approach (North) handles all Santa Monica aircraft executing the visual approach. SoCal Approach (North) shall obtain a pointout from Burbank sector prior to giving approach clearance. No VOR-A approaches are authorized from this time until Santa Monica Tower advises wheels down. Burbank sector must approve this pointout prior to approach clearance being given by North approach.

4. Santa Monica Tower shall advise wheels down for all IFR arrivals into SMO to Burbank sector.

i. Delegation of Airspace for Santa Monica Tower

During times when Santa Monica Tower is not staffed the responsibilities of Santa Monica will be delegated in the following manner:

All aircraft transitioning through Santa Monica Airspace heading toward Los Angeles shall be handled by Los Angeles Tower. If Los Angeles Tower is not online, the controller responsible for Los Angeles Tower shall handle transitions. Los Angeles Tower shall ensure that transitioning aircraft remain clear of the traffic flows of Santa Monica, it is recommended that transitioning aircraft are instructed to over fly Santa Monica airport at 2500'. Los Angeles Tower has a pointout for these aircraft as long as the aircraft are preceding either direct to Santa Monica Airport or from the airport along the miniroute at 2500 or above, these transitions need not be coordinated.

All other responsibilities shall be delegated to the following controllers, in the order that they are online.

SoCal Approach (North)
SoCal Approach (Combined)
Los Angeles Center

j. Coliseum VFR transition

1. Burbank sector is responsible for coordinating all southbound transitions through the Los Angeles Class Bravo airspace via the Coliseum route.

2. Aircraft requesting this route should be radar identified then cleared into the Class Bravo airspace via the coliseum route at 9500'. This route tracks the VNY125/SLI306. Radial. These aircraft should be handed off to SoCal approach (north).

3. Northbound Coliseum transitions will not talk to Burbank sector unless requesting flight following.

4. This transition requires Los Angeles to be in Normal or Noise Ops.

k. Hollywood Park VFR transition

1. Burbank sector is responsible for coordinating all southbound transitions through the Los Angeles Class Bravo airspace via the Hollywood park route.

2. Aircraft requesting this route should be radar identified then cleared into the Class Bravo airspace via the Hollywood Park route at an altitude between 7000-10000'. This route tracks the VNY140 Radial outbound. Aircraft should be handed off to SoCal approach (North).

3. Northbound Hollywood Park transitions will not talk to Burbank sector unless requesting flight following.

4. This transition requires Los Angeles to be in Normal or Noise Ops.

l. Shoreline VFR transition

1. Burbank sector is responsible for coordinating all southbound transitions through the Los Angeles Class Bravo airspace via the shoreline route.

2. Aircraft requesting this route should be radar identified then cleared into the Class Bravo airspace via the Shoreline route at 5500'. This route tracks the LAX323 Radial to LAX. Aircraft should be handed off to SoCal departure.

3. Northbound Coliseum transitions will not talk to Burbank sector unless requesting flight following.

4. This transition requires Los Angeles to be in Normal or Noise Ops.

m. Additional comments:

1. BUR_APP is affected by both permanent pointouts and prearranged pointouts; see the pointout SOP for more information.