Fresno TRACON
| Date | Code | Version | Contact |
|---|---|---|---|
| 2010-04-26 | SOP-224 | 1.11 | Facility Advisory Board (FAB) |
1. PURPOSE.
This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Fresno Approach, the primary airport KFAT, and satellite airports, to ensure that traffic flows are handled in as efficient and timely a manner as possible. By specifying standard handoff points, departure and arrival routes, coordination between adjacent facilities may be greatly reduced.
2. ROLES AND RESPONSIBILITIES.
The Office of Primary Responsibility (OPR) for this SOP is the ZOA Facility Advisory Board. This SOP shall be maintained, revised, updated or cancelled by the ZOA Facility Advisory Board. 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 positions within Fresno TRACON sector airspace, as well as controllers working at positions interfacing with Fresno TRACON facilities
4. BACKGROUND.
Over time, controllers have found that having aircraft arrive via pre-approved arrival routes, either by STAR?s (Standard Terminal Arrival Routes) or via vectors through pre-determined arrival fixes, provides for a more orderly traffic flow, and reduces the need for communication between Fresno Approach and other Fresno TRACON and ZOA 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.
6. Primary Responsibilities.
The primary responsibilities of Fresno TRACON is the sequencing Fresno area arrivals and separation of Fresno area departures.
6. PROCEDURES.
a. Frequencies and Callsigns
1. Fresno Approach shall use 119.60 as its frequency, FAT_APP as text callsign, and "Fresno Approach" for arriving traffic and "Fresno Departure" for departing traffic as voice callsign.
2. Frequencies for secondary airports should be determined from appropriate publications.
b. Airspace and Sectorization Plan:
1. FAT_APP shall own the airspace within the lateral limits depicted on this graphic, from surface to 10000' MSL, except all actively manned Class D airspace within the lateral limits.
2. No departure control or further sub-sectorization is approved.
3. The Sector files authorized for use in operating this sector is the certified Center sector or the the Fresno Approach sector file available on the "downloads" page of the ZOA ARTCC web site.
c. Release Procedures and Runway Use Plans
1. The active runway plan will be determined by FAT_TWR per SOP-050. Normal prevailing winds are from the West.
2. Departure release procedures with FAT_TWR will only be in use upon request by FAT_APP.
d. Special Instructions:
1. Aircraft arriving with flight plans indicating "NO STAR" (or those that have not filed for an approved STAR) shall be have their clearances amended to approved STAR's listed in this SOP, so that all traffic are placed on consistent arrivals streams.
2. Aircraft filing "NO SID" (or those that have not filed for an approved SID) shall have their clearances amended to approved SID's listed in this SOP, so that all traffic are placed on consistent departure streams.
3. Southbound departures from FAT TRACON to shall be handed off to LAX_A_CTR (south of FAT_APP airspace) or LAX_B_CTR (south and east of FAT_APP airspace).
e. Arrivals and Departures:
1. ALTTA arrivals are received directly from LAX_B_CTR with instructions to descend and maintain 11000. Aircraft shall be instructed to "Cross ALTTA at 4000" and cleared for the approach after ALTTA. When Fresno is landing runways 11L/R, aircraft shall be instructed to continue past ALTTA on the Friant (FRA) 147 radial, and then be turned onto an extended left downwind once north of the CZQ 110 radial. Once on the downwind, continue to descend as per the applicable MVAs north of the airport.
2. GIVEN arrivals are received from OAK_B_CTR prior to TOPPE at 11000, and may or may not have a speed restriction. Aircraft shall be instructed to "Descend and maintain 9000," and continue to be descended via the MEAs on the STAR... Passing TOPPE, the aircraft shall be descended to 7000. Passing the CZQ 077 radial (IMOJU intersection), aircraft shall be descended to 5000. Passing the CZQ 102 radial (IMYOG intersection), aircraft shall be descended to 4000 for vectors to a left downwind runway 11L/R or 3500 for runway 29L/R and vectored to the final approach course. Aircraft vectored off the STAR must be descended via the appropriate MVAs.
3. Missed Approaches can be executed per the published procedures or alternately climbed to 2000 and turned for a right or left downwind to be re-sequenced as appropriate.
4. COALDALE departures shall proceed under pilot navigation and be handed off to OAK_B_CTR.
5. FRESNO departures shall proceed on runway heading to be vectored to the first fix on their route, then handed off as follows: AVE, PXN transitions to OAK_A_CTR (11000 and above) or NLC_APP (10000 and below); all other transitions to OAK_B_CTR, LAX_B_CTR, MOD_APP (SFC-FL190), NLC_APP(SFC-10000), or BFL_APP (SFC-13000) based on cruise altitude and transition waypoint.
g. IFR Low Altitude Routing:
None.
h. Additional Comments:
1. The Clovis Visual Rwy 29R approach shall not be issued, as the required scenery landmarks are not simulated.