1. PURPOSE.
This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Bakersfield Approach to ensure that arrival flows 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 ZLA Facility Advisory Board (FAB). This SOP was signed and approved by Andrew Cleeremans, ZLA Chief Instructor, and ZLA Facility Chief Marc Sykes on December 30, 2003. This SOP shall be maintained, revised, updated or cancelled by the ZLA FAB or any other organization that supercedes, replaces or assumes the FAB responsibilities. Any suggestions for modification or amendment to this SOP should be sent to the ZLA FAB for review.

3. DISTRIBUTION.
This SOP is intended for use by controllers staffing Bakersfield Approach (BFL_APP)

4. BACKGROUND.
This SOP will be the primary outline of Bakersfield Approach procedures

5. REQUIREMENTS.

1. Frequencies
   
   1. BFL_APP 118.80
   2. BFL_TWR 118.10
   3. BFL_GND 121.70
2. Airspace
   
   1. BFL_APP owns the airspace as shown on the TRACON graphic from SFC-13000’
3. Special Instructions
   
   1. KBFL Runway use program
      
      1. Normal operations use runways 30L/R
      2. East operations use runways 12L/R when the wind is out of the northeast at greater than 10kts
   2. KBFL Arrivals
      
      1. FASTO STAR arrivals are received from LAX_4_CTR descending to 13000’. This arrival is designed to feed the ILS 30R but may be used when aircraft must circle to runway 12L/R
      2. Arrivals from ZOA will be received from OAK_A_CTR descending to 10000’
   3. KBFL Departures
      
      1. Initial climb in BFL_APP airspace is 3000’
      2. MARIC, WRING SID departures are pilot navigated
      3. MEADOWS SID departures must be vectored on course