Bakersfield Approach (BFL)

POC: Facility Advisory Board	Date: 2004-05-03
Code: ZLA-BFL	Version: 2.00

1. PURPOSE.

This Standard Operating Procedure (SOP) outlines the general procedures to be used by controllers working any Bakersfield TRACON positions to ensure safe and efficient handling of air traffic into, out of and through the Bakersfield airspace. By specifying standard phraseology and procedure, this SOP provides for the use of common air traffic handling language and operations.

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 TRACON positions.

4. REQUIREMENTS.

a.) Frequencies

Bakersfield Approach (if combined) (BFL_APP) 118.80

Bakersfield North Approach (North of EHF) (BFL_N_APP) 118.90

Bakersfield South Approach (South of EHF) (BFL_S_APP) 118.80

b.) Airspace:

Bakersfield TRACON shall own all airspace of 13,000' MSL and below to it's lateral boundaries as depicted Los Angeles ARTCC TRACON map .

Relevant Neighboring Facilities

Los Angeles Center Sector(s)	Frequency
LAX_A_CTR	135.3
LAX_B_CTR	127.1
Approach Control Sector(s)	Frequency
Joshua Approach (EDW_APP)	124.55
Tower, Ground, and Delivery	Frequency
Bakersfield Tower Class D SFC-3,000' MSL	118.1
Bakersfield Ground	121.7 or 128.4

5. OPERATING PROCEDURES.

a.) Normal Operations

Runway Configuration

• Wind from any direction below 10kts or from the Southwest greater than 10kts, Runway 30L/R shall be in use. This shall be known as the Default Configuration.
• Wind greater than 10kts from the Northeast, example 120 at 12kts, Runway 12L/R shall be in use. This shall be known as the East Configuration.

IFR Arrival Traffic Routing

ARVIN1: Non-profile arrival from the South/Southeast. All aircraft are received from LAX_B_CTR. Aircraft on the LHS/GMN transition will be descending to 13,000' MSL, GMN/LHS aircraft shall be given descent instructions on initial contact to maintain 9,000' MSL. Aircraft on the PMD transition will be descending to cross KELEN at 10,000' MSL. PMD aircraft can be given a ILS approach from AMONT, LHS/GMN aircraft can be given a ILS approach from NILEY.. Controllers are warned that this arrival is for when Runway 30L/R is in use, however Circle To Land Runway 12L/R can be issued.

IFR Departure Routing

i.) Initial Climbs

All departures from all runways at BFL shall climb to the lower of the initial altitude of 3,000 feet, or their requested cruise altitude

ii.) Final Climbs

After the initial climb to 3,000 feet, and when traffic permits, all departures shall be climbed to the lower of 13,000'MSL or their requested cruise altitude, and shall be handed off to the appropriate Center sector.

iii.) Pilot Nav Departure Procedures

All Pilot Nav Departure Procedures irrespective of their specific departure procedure are handled the same way. Upon radar contact, climb them if, and as able to the lower of the BFL TRACON ceiling or their requested cruise altitude. Pilot Nav Departure Procedures are the MARIC3 and WRING3.

iv.) Obstacle Departure Procedure ( Bakersfield Published Departure Procedure)

"All aircraft climbing right turn direct EHF VOR. Aircraft departing EHF R-180 clockwise R-350 climb on course. All others continue climb northwest-bound via EHF R-324, then climbing left turn to cross EHF VOR at or above, EHF R-110 clockwise R-179, 3,000' MSL ; EHF R-351 clockwise R-109, 4,000' MSL."

v.) Vectored Departure Procedures

All Vectored Departure Procedures are handled as shown on the chart with all relevant turns completed PRIOR to the handoff of radio communications to LA Center. This stating that you shall clear the aircraft to their requested fix.

All pilots that do not file for a Departure Procedure should be asked if they have them on board before providing a radar vector departure. The Vector Departure Procedure is the MEADOWS1.

Pilots that do not have the charts, are not willing to download them, or file NO DP's in the flight plans shall be vectored to their appropriate departure gate and transferred to Center, transfer communications to Center earlier than the pilots that file for DP's to ensure Center has enough time to properly route the aircraft along the rest of their route.

b.) VFR Traffic

VFR Traffic requesting flight following shall need to provide Approach control the following information; Full Callsign, Type Aircraft, Position, Altitude, Destination ; if a pilot fails to give Approach the information Approach shall request the needed information then assign a discrete squawk code. Note; Equipment type is required to be given if the pilot requests to pick up a IFR clearance en-route with BFL_APP.

VFR Traffic at a improper VFR traveling altitude for direction of flight shall be advised of the improper altitude.

BFL operates right traffic for runway 30R/12R and left traffic for runway 30L/12L.

VFR Traffic departing BFL shall be issued a stage of the traffic pattern departure, ie: Right Crosswind Departure, Straight Out Departure etc.