Southern California Terminal Radar Approach Control and Ontario Airport Traffic LETTER OF AGREEMENT SUBJECT: Interfacility Coordination and Control Procedures Effective: August 16, 2013 1. PURPOSE: This Letter of Agreement establishes responsibilities and procedures for the coordination and control of air traffic between Southern California Terminal Radar Approach Control (TRACON) and Ontario Airport Traffic (Tower). 2. CANCELLATION: This agreement cancels the Southern California Terminal Radar Approach Control and Ontario Airport Traffic Letter of Agreement subject Interfacility Coordination and Control Procedures, dated April 20, 2000 and Notice SCT 7110.366 and ONT 7110.10, dated August 17, 2012. 3. SCOPE: The procedures herein are applicable to all Instrument Flight Rules (IFR), Visual Flight Rules (VFR), and Special VFR (SVFR) operations at Ontario Airport (ONT), and to all IFR arrival/departure operations at Cable Airport (CCB). 4. DEFINITIONS: a. Computer-adapted aircraft types: (1) J Jet/heavy, super or turbojet (2) M Turboprop, 190 kts or greater (3) P Reciprocating engine, 190 kts or greater (4) Q Non-jet, less than 190 kts b. Tower Delegated Airspace: See Attachment 1. 5. RESPONSIBILITIES: Tower has been classified as an Airport Traffic (ATCT) with radar. Tower must use their Certified Tower Radar Display (CTRD) to provide Class C services to aircraft within Tower s delegated airspace and provide separation as described below. a. CTRD operational, Tower is responsible for: (1) Separation of all ONT departures. (2) Separation of all ONT arrivals within Tower delegated airspace. (3) Separation of all ONT arrivals from all ONT departures including Opposite Direction Operations (ODO). [see ODO procedures in Attachment 7] (4) Separation of ONT departures from LaVerne-Brackett Airport (POC) arrivals pointed out to Tower by TRACON. (5) Determining departure order for CCB departures in relation to ONT departures.
(6) Separation of all Ontario departures/missed approaches from CCB departures. b. TRACON is responsible for: (1) Separation of ONT departures from CCB arrivals, and missed approaches. (2) Separation of ONT missed approaches from CCB arrivals, and missed approaches. (3) Separation of ONT missed approaches from POC ILS/LOC/RNAV RWY 26L arrivals. (4) Separation of CCB departures from POC ILS/LOC/RNAV RWY 26L arrivals. (5) Separation of CCB missed approaches from POC ILS/LOC/RNAV RWY 26L arrivals. 6. DELEGATION AND USE OF AIRSPACE: a. Tower is delegated the ONT Class C surface area north of the southern edge of Runway (RWY) 26L, 3000 feet MSL and below (northern half), and from the southern edge of RWY 26L, south to Riverside Drive, 2500 feet MSL and below (southern half). b. Tower is authorized to conduct SVFR operations 3000 feet MSL and below in the ONT Class C Surface Area northern half, and 2500 and below in the ONT Class C surface area southern half delegated to Tower. c. TRACON must restrict IFR aircraft that are not cleared for an Instrument/Contact approach to ONT at least 500 feet (1000 feet for B757s, and heavy jets) above Tower airspace when ONT weather is reported below VFR minimums. d. Transfer of control between TRACON and Tower must occur at the boundary of Tower delegated airspace unless otherwise stated in this letter. e. TRACON has control of departing aircraft on contact. 7. COORDINATION: a. Tower and TRACON must: (1) Provide a full ARTS/STARS data block (FDB) containing aircraft call sign, type a/c, and one of the following, as contained in Attachment 4: (a) The assigned approach and/or assigned runway, if other than that advertised on the Automatic Terminal Information Service (ATIS). (b) Aircraft destination/intentions. (c) Cardinal direction of flight. (2) When making non-automated handoffs in lieu of a FDB, provide the other facility the call sign, type aircraft, and approach request or initial route of flight. 2
(3) When making, point outs, coordination, and non-automated handoffs requiring transfer of radar identification, reference the following fixes: (a) Cable Airport (b) Chino Airport (c) FONTA (d) HAWNN (e) Montclair Plaza (f) NAROD (g) Ontario Airport (h) Paradise VORTAC (i) PETIS (j) Pomona VORTAC (k) Riverside Airport (l) Rialto Airport (4) Use the following interphone phraseology when coordinating climb out for aircraft conducting practice approaches to Runway 26L/R: (a) Low approach Pomona 1. IFR -- fly heading 255, climb and maintain 4000. 2. VFR -- fly heading 235, maintain VFR at or below 3000. (b) Low approach Riverside 1. IFR -- fly direct PDZ, climb and maintain 4000. 2. VFR -- fly heading 140, climb and maintain VFR at or below 3000. (c) Low approach Norton b. Tower must: 1. IFR -- IFR low approaches are not approved to Norton Sector for RWY 26 arrivals. 2. VFR -- fly heading 060. (1) Forward weather observations to the TRACON flight data position via the Systems Atlanta. (2) When the Systems Atlanta is OTS, forward weather observations via FDIO, or interphone. 3
(3) Only disseminate one specific approach at a time on the ATIS. (4) Notify the Empire Area FLM/CIC: (a) Of any changes to the preferred arrival runway or instrument approach in use as disseminated on the ATIS. (b) When the weather changes to above or below basic VFR, any special weather observations taken when weather is below basic VFR. (c) Of runway changes, including CONTRA FLOW, and arrival flow restrictions. (d) Of NOTAMS in effect, equipment outages, DASI correction factor, or other pertinent information. (5) Advise TRACON when conditions are unsatisfactory for the transfer of radar identification via the ARTS/STARS QUICK LOOK FUNCTION; i.e., Tower CTRD status, etc. c. TRACON must: (1) Transfer radar identification of all ONT arrivals and CCB departures to Tower via the ARTS/STARS QUICK LOOK FUNCTION through an ARTS/STARS Full Data Block (FDB). (2) When Tower advises conditions are unsatisfactory for the transfer of radar identification via the ARTS/STARS QUICK LOOK FUNCTION, transfer radar identification of ONT arrivals via ARTS/STARS automated Handoff, and transfer radar identification of CCB departures via verbal coordination. (3) Advise Tower verbally or via modification of the data block when a previously departed IFR aircraft has cancelled IFR. (4) Notify the Tower FLM/CIC: 8. PROCEDURES: (a) Of any pertinent NOTAM in effect, or pertinent equipment outage. (b) When the Empire Area is utilizing Long Range Radar. (c) When TRACON requires a Visual/Instrument Approach Procedure (IAP) to be advertised on the ATIS other than that currently advertised. a. ONT arrivals. (1) IFR arrivals. RWY 26L for ONT west traffic, and RWY 08L for ONT east traffic are the preferred IFR arrival runways at ONT. (a) TRACON must: 4
1. Sequence IFR arrivals to the preferred arrival runway without any flow restrictions. 2. Sequence IFR arrivals to other than the preferred arrival runway in compliance with flow restrictions issued by the Traffic Management Unit (TMU). 3. Complete communications transfer of arriving aircraft prior to the final approach fix for aircraft executing an instrument approach, and prior to Tower delegated airspace for aircraft executing a visual/contact approach. 4. Ensure aircraft conducting visual approaches enter base over or east of the I-15 freeway for RWY 26 operations, or at least 3 NM from the airport for RWY 8 operations. 5. Coordinate contact approaches with Tower prior to issuing a clearance. 6. Advise Tower verbally or via the ARTS/STARS when aircraft request SVFR clearances into/through Tower delegated airspace. 7. Advise Tower verbally, or via the ARTS/STARS when an aircraft is conducting a VFR practice instrument approach. 8. Advise Tower when Missed Approach instructions different than those contained in Attachment 3 have been issued. (b) Tower must: 1. Notify the TRACON TMU of any required flow restrictions for arrivals to other than the preferred arrival runway. 2. Notify the appropriate TRACON departure sector when an IFR aircraft executes an unplanned missed approach. Tower must assign the Missed Approach instructions contained in Attachment 3 to aircraft that do not cancel IFR. 3. Ensure aircraft cancel IFR prior to issuing VFR climb-out instructions. 4. Handle VFR aircraft conducting a practice approach as a Class C departure and issue the aircraft a new VFR flight plan, unless coordinated otherwise with TRACON. 5. Have the authority to initiate a visual approach within Tower delegated airspace and ensure approved separation from all other traffic. (2) VFR arrivals. (a) TRACON must: 5
1. Complete communications transfer of arriving VFR aircraft prior to Tower delegated airspace. 2. Not assign left or right runways for other than straight in approaches. 3. Restrict other than straight in approaches to at or above 3500 feet MSL. 4. Sequence VFR arrivals to RWY 26 as follows: a. Riverside Sector arrivals via the south downwind. b. Pomona Sector arrivals via the north downwind. c. Norton Sector arrivals via straight in to either runway 5. Sequence VFR arrivals to RWY 8 as follows: a. Riverside Sector arrivals via the south downwind. b. Norton Sector arrivals via the north downwind. c. Pomona sector arrivals via straight in to either runway. (b) Tower must coordinate with TRACON when arrival procedures must be modified due to high traffic volume, weather, etc. b. ONT Departure Procedures. (1) IFR Departures. (a) TRACON must: 1. Release departures via the ARTS/STARS Rundown Patch as specified in Attachment 5. 2. Issue any altitude restrictions verbally via the interphone. 3. Provide Tower with a delay estimate for the first aircraft in the Rundown list not released within one minute of the departure request. 4. Place Tower on a verbal call-for-release when required. (b) Tower must: 1. Forward Tower Enroute (TEC) and IFR to VFR on Top (OTP) flight plans to TRACON via FDIO in the format depicted in Attachment 3. 2. Issue the following to departing IFR aircraft: a. Beacon codes on the FDIO strip. b. Initial headings, departure instructions, or the DP to be flown. c. Initial altitudes. 3. Issue one of the following, as appropriate: 6
a. Preferential Departure Route (PDR). b. Appropriate TEC route. c. Other routes in Attachment 3. d. TRACON or Los Angeles Center (ZLA) reroutes. 4. Obtain flow control release times from: a. The appropriate ZLA sector for oceanic flights. b. The appropriate TMU for all aircraft subject to flow control programs. 5. Not release an IFR departure without a discrete beacon code, unless approved by TRACON. 6. Enter a DM message via the FDIO when any non-transponder equipped aircraft departs. 7. Release IFR departures with FDIO generated flight plans by utilizing the ARTS/STARS Rundown Patch procedures specified in Attachment 5. Verbally coordinate for release of IFR departures with the appropriate TRACON departure sector when: a. Instructed by TRACON. b. The ARTS/STARS is out-of-service or use of the Rundown Patch is otherwise not feasible. c. An aircraft has a FDIO generated strip with a revision number. 8. Cancel the departure release of any aircraft that has not departed within three minutes of that aircraft s TRACON verbal or automated release. When multiple aircraft departing to the same TRACON sector are released, subsequent departure releases to the same TRACON sector are void three minutes after the preceding departure to the same TRACON sector begins takeoff roll. 9. Advise the appropriate TRACON sector when a departing aircraft s ARTS/STARS data tag does not acquire within 3 miles of the departure end of the runway. 10. Modify the ARTS/STARS flight plan to the appropriate TRACON sector tab list of any aircraft requesting an opposite direction departure and verbally advise that sector no later than the time the aircraft begins taxi. (2) IFR to VFR OTP Departures. (a) Tower must: 7
1. Enter IFR to VFR OTP flight plans via the FDIO and issue the computer generated beacon code to transponder equipped aircraft. 2. Enter VFR OTP flight plans via the FDIO/ARTS/STARS using ONT as the departure point in a format that will allow for automated handoffs to facilities within and adjacent to TRACON airspace. 3. Ensure the flight plan (ARTS/STARS track file) is in the appropriate TRACON sector tab list prior to departure. 4. Coordinate with the TRACON departure sector when the FDIO/ARTS/STARS procedure in paragraph 7b(2)(a)1. above is not possible. 5. Assign departure instructions as specified in Attachment 3. 6. Release IFR to VFR OTP departures with FDIO generated flight plans by utilizing the ARTS/STARS Rundown Patch procedures specified in Attachment 5. Verbally coordinate for release of IFR to VFR OTP departures with the appropriate TRACON departure sector when: (3) SVFR Departures. a. Instructed by TRACON. b. The ARTS/STARS is out-of-service or use of the rundown patch is otherwise not feasible. c. An aircraft has a FDIO generated strip with a revision number. (a) Tower must: 1. Enter SVFR flight plans via the FDIO for SVFR aircraft requesting Class C services or flight following beyond the Tower s delegated airspace and issue the computer generated beacon code to transponder equipped aircraft. 2. Modify the flight plans (ARTS/STARS track files) to the appropriate TRACON sector tab list prior to departure. 3. Coordinate with the TRACON departure sector when the FDIO/ARTS/STARS procedure in paragraph 8b(3)(a)1. above is not possible. 4. Assign departure instructions in Attachment 3. 5. Release SVFR departures with FDIO generated flight plans by utilizing the ARTS/STARS Rundown Patch procedures specified in Attachment 5. Verbally coordinate for release of SVFR departures with the appropriate TRACON departure sector when: a. Instructed by TRACON. 8
b. The ARTS/STARS is out-of-service or use of the rundown patch is otherwise not feasible. 6. Instruct SVFR aircraft not requesting Class C services or flight following beyond the Tower s delegated airspace to maintain VFR and remain clear of Class C airspace. (4) VFR Departures. (a) Tower must: 1. Enter VFR flight plans via the FDIO/ARTS/STARS for VFR aircraft requesting Class C services or flight following beyond the Tower s delegated airspace and issue the computer generated beacon code to transponder equipped aircraft. 2. Enter VFR flight plans via the FDIO/ARTS/STARS using ONT as the departure point in a format that will allow for automated Handoffs to facilities within and adjacent to TRACON airspace. 3. Modify the flight plans (ARTS/STARS track files) to the appropriate TRACON sector tab list prior to departure. 4. Coordinate with the TRACON departure sector when the FDIO/ARTS/STARS procedure in paragraph 8b(4)(a)1. above is not possible. 5. Assign departure instructions in Attachment 3. 6. Release VFR departures with FDIO/ARTS/STARS generated flight plans by utilizing the ARTS/STARS Rundown Patch procedures specified in Attachment 5. Verbally coordinate for release of VFR departures with the appropriate TRACON departure sector when: a. Instructed by TRACON. b. The ARTS/STARS is out-of-service or use of the Rundown Patch is otherwise not feasible. 7. Instruct VFR aircraft not requesting Class C services or flight following beyond the Tower s delegated airspace to maintain VFR and remain clear of Class C airspace. c. Adjacent Airport Arrival and Departure Procedures. (1) POC Arrival Procedures. TRACON must: (a) Point Out to Tower, POC ILS/LOC/RNAV RWY 26L arrivals within 10 NM of ONT. Tower accepting the Point Out is approval for the POC arrival to enter Tower airspace established on the POC ILS/LOC/RNAV RWY 26L final 9
approach course and descend in accordance with the approach procedure (see Attachment 6). (b) Unless otherwise specifically coordinated, vector POC ILS/LOC/RNAV RWY 26L IFR aircraft to a base leg east of the approach end of ONT runways 26L/R. (2) CCB IFR Arrival Procedures. (a) TRACON must: 1. Point Out to Tower, CCB instrument approaches at least 5 NM from the POM VORTAC. Tower accepting the point out is approval for the CCB arrival to enter Tower airspace on approach/missed approach and descend/climb in accordance with the procedures (see Attachment 6). 2. Advise Tower verbally when ONT IFR departures may be resumed. (b) Tower must discontinue all IFR departures from ONT after approving a TRACON Point Out for a CCB instrument arrival once the CCB arrival reaches POM VORTAC and only resume IFR departures when advised verbally by TRACON to do so. (3) CCB IFR departure procedures. (a) TRACON must: 1. Issue IFR clearances to aircraft departing CCB, and instruct the pilot to contact Tower prior to departure for a release time. 2. Release departures from CCB via the Tower. 3. Have control for climb and vectors in Tower airspace west of the ONT runways. 4. Not vector CCB departures into the previously crossed paths of ONT IFR departures until standard separation is ensured by TRACON. 5. Immediately advise Tower of the position of the CCB departure when the CCB departure is non-arts/stars tracked, displays the wrong beacon code, or when another aircraft has acquired the CCB departure s associated data block. (b) Tower must: 1. Request a verbal release for aircraft departing CCB and advise TRACON of the departure order of the CCB departure in relation to ONT departures. 2. During the release window time frame, not release ONT IFR departures until radar identification of the CCB departure has been established by Tower via the ARTS/STARS QUICK LOOK FUNCTION, or verbal coordination. 10
3. Ensure standard separation between CCB departures and ONT departures. 4. Advise TRACON when verbal coordination is required to release ONT departures reference CCB departures. d. Equipment Outages. Tower and TRACON must advise one another when equipment listed below experiences an outage. (1) Tower FDIO OTS. Tower must: (a) Obtain clearances and/or forward IFR flight plans via the TRACON flight data position. (b) Forward data to the appropriate TRACON sector for all ONT IFR departures. (c) Enter all VFR flight plans into the appropriate sector s tab list for VFR aircraft requesting Class C services or flight following beyond the Tower s delegated airspace. (2) TRACON FDIO OTS. Tower must forward data to the TRACON flight data position for ONT/CCB departures containing the following: (a) Aircraft call sign, type, beacon code, DP, transition, destination, and requested altitude. (b) Route of flight for non-local/otp/tec aircraft and non- POM/HASSA/ONT/PRADO DP aircraft. (3) Tower ARTS/STARS OTS. (a) TRACON must verbally Handoff arrivals. (b) Tower must verbally coordinate all departure releases. (4) TRACON ARTS/STARS OTS. (a) Tower must: 1. Discontinue CONTRA FLOW/ODO. 2. Assign transponder code of 0200 to all IFR aircraft that will enter the TRACON airspace. 3. Discontinue use of the ARTS/STARS Rundown Patch and verbally coordinate for release of all departures. 4. Enter a DM message via the FDIO for all IFR aircraft that depart ONT. (5) Tower CTRD OTS/TRACON utilizing Long Range Radar: Discontinue Class C services within Tower delegated airspace and provide services as a Class D VFR Tower. Additionally, the following procedures must apply: (a) Tower must: 11
1. Verbally coordinate all departure releases. 2. After receiving IFR releases from TRACON, separate successive IFR departures to different sectors utilizing visual separation or non-radar separation procedures specified in FAAO 7110.65. 3. After receiving IFR releases from TRACON, separate IFR arrivals and departures utilizing visual separation or non-radar separation procedures specified in FAAO 7110.65. 4. Ensure SVFR operations are discontinued two (2) minutes prior to the estimated time of an arriving aircraft reaching the airspace boundary for visual/contact approaches and by the final approach fix for instrument approaches, as applicable. 5. Ensure the following information is disseminated via a NOTAM and the ATIS broadcast: Ontario Tower radar is out-of-service. Class Charlie services are not available within the Ontario Class Charlie Surface Area below 3000 feet MSL. Contact So-Cal Approach to enter the Ontario Charlie airspace. (b) TRACON must: 1. Be responsible for the separation of IFR departures to the same sector. 2. Be responsible for separating all IFR arrivals. 3. Forward the following arrival information to Tower: a. A final approach fix estimate at least five (5) minutes prior to the final approach fix for instrument approaches. b. An airspace boundary estimate at least five (5) minutes prior to Tower delegated airspace boundary for visual approaches. 4. Discontinue VFR straight in arrivals, except for J class aircraft. 5. Advise IFR aircraft to contact Tower in the order of approach sequence. 12
ATTACHMENTS: Attachment 1: ONT Tower Delegated Airspace Attachment 2: Empire Area Sector Boundaries Attachment 3: Departure Procedures and Other Routings Attachment 4: ARTS/STARS Abbreviations Attachment 5: ARTS/STARS Rundown Patch Procedures Attachment 6: ARTS Automated Point Out Procedures Attachment 7: Opposite Direction Operations (ODO) 13
SIGNATURE PAGE Approved: Barry J. Davis Air Traffic Manager Southern California TRACON Date Signed Gregory L. Hatcher, Sr. Air Traffic Manager Ontario Tower Date Signed 14
Attachment 1 ONT TOWER DELEGATED AIRSPACE 30 SFC 25 SFC Riverside Drive 1-1
Attachment 2 EMPIRE AREA SECTOR BOUNDARIES NORTON SECTOR POMONA SECTOR NORTON SECTOR ONT WEST RIVERSIDE SECTOR ONT EAST RIVERSIDE SECTOR 2-1
Attachment 3 DEPARTURE PROCEDURES AND TOWER ENROUTE CLEARANCES 1. IFR Departure Procedures. Tower must ensure the following: a. Any required amendments to flight plans and/or routes are amended via the FDIO unless stated otherwise. b. All aircraft must be assigned the applicable Departure Procedure (DP) except: (1) Tower Enroute Clearance (TEC) routes. (a) Burbank, Northwest (CMA, OXR, SBA, etc.), and Coast Areas TEC routes. 1. J, M, P, and Q departures (except ONT east traffic P and Q RWY 8L/R departures) routed through Pomona Sector via V186, V363, and V394, must be assigned a 255 heading, join the applicable TEC route. 2. ONT east traffic P and Q RWY 8L/R departures routed through Pomona Sector via V186, V363, and V394 must be assigned direct PDZ, join the applicable TEC route, and be amended by Tower to the Riverside Sector Tab and Rundown Lists. (b) Arrival Area TEC routes. 1. J, M, P, and Q departures for LAX between 0000L and 0630L must be assigned a 255 heading, RV SMO DIRECT and to expect 7000 feet as a final altitude. These flight plans must not be amended via the FDIO. 2. J, M, P, and Q departures (except ONT east traffic P and Q, RWY 8L/R departures) to LAX from 0630L to 2359L must be assigned a heading of 255, join V363 intercept LAX RWY 24R LOC, Maintain 4000. These flight plans must not be amended via the FDIO. 3. ONT east traffic P and Q RWY 8L/R departures to LAX from 0630L to 2359L must be assigned: Direct PDZ. PDZ270.. LAX RWY 24R LOC, Maintain 4000. Tower must amend these aircraft to the Riverside Sector Tab and Rundown Lists. 4. J, M, P, and Q, departures (except ONT east traffic P and Q RWY 8L/R departures), all aircraft departing to HHR must be assigned an initial departure heading of 255 join V363 intercept HHR LOC. These flight plans must not be amended via the FDIO. 5. ONT east traffic, P and Q RWY 8L/R departures to HHR must be assigned direct PDZ, join the TEC route. Tower must amend these aircraft to the Riverside Sector Tab and Rundown Lists. 3-1
(c) San Diego Area TEC routes. 1. M, P, and Q departures to the San Diego Area via V186 must be assigned direct PDZ, join the applicable TEC route. 2. J departures to the San Diego Area via V186 must be assigned the PRADO DP PDZ to join the applicable TEC route. (2) Aircraft landing airports within Empire area airspace (Local) must be routed as follows: (a) EMT, CCB, and POC: via V363 POM Direct, except ONT east traffic, P and Q RWY 8L/R departures must be routed direct PDZ. PDZ270.. V363. POM Direct. Tower must amend these aircraft to the Riverside Sector Tab and Rundown Lists. (b) All other Empire area airports: via PDZ VORTAC Direct (3) Other destinations outside SCT airspace. (a) All M class, and all RWY 26L/R P and Q class aircraft routed via V186 and V197 must be issued headings of 255, join. These flight plans must not be amended via the FDIO. (b) All other M, P, and Q class departures must be routed via PDZ and (if necessary) be amended to the Riverside Sector Tab and Rundown Lists. (4) Aircraft departing IFR to VFR On Top (OTP) must be routed as follows: (a) RWY 26L/R -- Via the Pomona Sector, heading of 255, join V363 POM. (b) RWY 8L/R -- Via the Riverside Sector, DIRECT PDZ. (c) And must be instructed: Climb to and report reaching VFR OTP. If not OTP at 4000, maintain 4000 and advise. Expect 7000 10 minutes after departure. (5) J, M, P, and Q class aircraft executing a RWY 26L/R IFR missed approach must be assigned climb out instructions as follows: (a) Via the Pomona Sector, heading 255, maintain 4000. (b) Via the Riverside Sector, direct PDZ, maintain 4000. c. Unless otherwise coordinated, all aircraft not assigned a published DP, and all aircraft assigned a departure heading must be assigned an initial altitude of 4000. d. Aircraft departing via a DP must be assigned initial altitudes as follows: (1) POMONA DP 14000 (2) HASSA DP (LAX is east traffic) 10000 3-2
(3) PRADO DP 7000 (4) ONTARIO DP (LAX and ONT are east traffic) 14000 e. Where required, all aircraft must be advised to expect their assigned higher altitude(s) ten minutes after departure. f. All aircraft filed or assigned the HASSA DP with a DAG transition must be rerouted via the HASSA DP PMD transition DIRECT DAG. The DAG transition off of the HASSA DP is not authorized for use. 2. VFR/SVFR Departures. Tower must ensure the following: a. All aircraft departing to destinations to the west through northwest of ONT via the Pomona sector must be assigned an initial departure heading of 285 and be instructed to Maintain VFR/SFVR at or below 3000. b. All aircraft departing to destinations to the southwest of ONT/executing a VFR low approach via the Pomona sector must be assigned an initial departure heading of 235 and be instructed to Maintain VFR/SVFR at or below 3000. c. All aircraft departing to destinations to the south through southeast of ONT/executing a VFR low approach via the Riverside sector must be assigned an initial departure heading of 140 and be instructed to Maintain VFR/SVFR at or below 3000. d. All aircraft departing to destinations to the northeast through east of ONT/executing a VFR low approach via the Norton Sector must be assigned an initial heading of 060 and be instructed to Maintain VFR/SVFR. TRACON must coordinate an altitude restriction when necessary. 3. Tower must assign the following frequencies to all departing aircraft: a. Aircraft departing via the Pomona Sector 125.5 b. Aircraft departing via the Riverside Sector 135.4 c. Aircraft departing via the Norton Sector 127.25 3-3
1. The Primary Scratch Pad Field must: Attachment 4 ARTS/STARS ABBREVIATIONS a. Contain the computer assigned exit fix for aircraft departing or enroute through SCT airspace. b. Contain the three-letter destination airport identifier for both IFR and VFR aircraft landing SCT airspace and must be modified to reflect the appropriate three-letter destination airport identifier when IFR and VFR aircraft change destinations. c. Contain LCL for aircraft with no specific destination and will remain in the local area. 2. The Secondary Scratch Pad Field must contain the following ARTS/STARS abbreviations for silent coordination: a. IFR arrival, IFR Missed Approach, IFR / VFR practice approach symbols. (1) First Letter. Approach symbol. (Must be used for other than the advertised approach, or in conjunction with the second and third letter symbols below for aircraft executing a Missed Approach, or flying practice approaches). Scratch Pad Symbol I R C P G Type Approach ILS VOR CONTACT RNAV (RNP) RNAV (GPS) (2) Second Letter. TRACON Sector symbol for aircraft executing a missed approach or VFR climb out. Scratch Pad Symbol P I N Tracon Sector Pomona Sector Riverside Sector Norton Sector (3) Third Letter. Missed Approach / VFR climb out symbol. L - VFR climb out - back to TRACON. (When this character is used in conjunction with a V in the second line of the FDB, it signifies that the aircraft has received VFR climb out instructions. Without the V in the second line of the FDB, it signifies that the aircraft will cancel IFR with Tower and is requesting VFR climb out from Tower). M - Missed approach IFR (as contained in Attachment 3, or IFR published Missed Approach), back to TRACON. 4-1
T - VFR climb out - remain with Tower or depart class C airspace. (When this character is used in conjunction with a V in the second line of the FDB, it signifies the aircraft is VFR. Without the V in the second line of the FDB, it signifies that the aircraft will cancel IFR with Tower and is requesting VFR climb out from Tower). NOTE: Tower must consider all L, M, and T as requesting the option. (4) Two Letter Symbols. (Must be used for other than the advertised approach). Scratch Pad IL IR VL VR PL PR GL GR Symbol Type Approach ILS RWY 26L Approach. ILS RWY 26R Approach Visual Approach RWY 26L (west traffic) Visual Approach RWY 8L (east traffic) Visual Approach RWY 26R (west traffic) Visual Approach RWY 8R (east traffic) RNP RWY 26L/8L Approach RNP RWY 26R/8R Approach GPS RWY 26L/8L Approach GPS RWY 26R/8R Approach (5) Interstate Visual. Scratch Pad Symbol Type Approach *L Interstate Visual RWY 8L b. VFR Altitudes. Single letter followed by altitude: Character R A B C D Meaning VFR aircraft is issued a specific altitude restriction. May be level at, climbing to, or descending to the altitude VFR aircraft is issued an "at or above" altitude restriction. Aircraft must be at or above the altitude VFR aircraft is issued an "at or below" altitude restriction. Aircraft must be at or below the altitude VFR aircraft has requested a specific altitude. The aircraft may be level at or climbing to the altitude indicated in scratch pad VFR aircraft has requested a specific altitude. The aircraft may be level at or descending to the altitude indicated in scratch pad Examples: 4-2
Scratch Pad Symbols c. Other symbols. Meaning A25 ATC assigned altitude restriction at or above 2500 MSL B30 ATC altitude restriction at or below 3000 MSL C30 Pilot informs ATC Climbing to 3000 MSL D35 Pilot informs ATC Descending to 3500 MSL R45 ATC assigned altitude restriction of 4500 MSL (aircraft may be climbing or descending to reach this altitude) (1) Direction of Flight (no specific destination). -- 1 or 2 letter cardinal direction of flight (SE, S, N, E, W, NE, SW, NW). (2) Following Freeways -- 2 number freeway designator with a 1 letter cardinal direction if desired (60E, 15N, 10W, etc.). (3) Pictures -- (PIX). (4) Special VFR -- SVF 4-3
1. IFR Procedures. a. Tower must: Attachment 5 ARTS/STARS RUNDOWN PATCH PROCEDURES (1) Ensure that all departures are entered into the appropriate sector s Rundown List and that the order of IFR departing aircraft is correct. (2) Depart IFR aircraft after TRACON has released the aircraft for departure by steadying the flash in the tab list or has verbally released the aircraft via the interphone. (3) Remove a departure from the list when that departure is delayed or cancels. (4) Notify TRACON of any changes to the departure sequence either by reentering the applicable aircraft into the rundown list in the correct order or verbally via interphone. (5) Enter the following in the remarks section of the applicable rundown list entry: (a) V459 for any aircraft routed via V459. (b) VT for the Void Time for any aircraft with a Traffic Management issued departure release void time ( VT45 ). (c) Three numbers preceded by the letter H (i.e. H230 ) when requesting a specific departure heading for IFR departures via the ARTS/STARS Rundown Patch. The following procedures apply: 1. TRACON steadying a flash in the departure tab list is approval for Tower to assign the requested heading. 2. Tower must assign 4000 MSL to aircraft released via a departure heading. 3. Tower may only request the following heading via the ARTS/STARS Rundown List: (a) 230 degrees for runway 26L/R departures. (6) Verbally coordinate with TRACON to confirm an aircraft s release status prior to departing an aircraft if: (a) TRACON positions were de-combined and aircraft were inadvertently dropped from the applicable rundown lists. (b) Allowable release window has expired and a previously released aircraft has not yet departed. 5-1
(7) May enter the following in the remarks section of the applicable rundown list entry: (a) The first two digits of an aircraft s assigned final altitude followed by the first letter of the first fix after either the POM or PDZ VORTAC (i.e. 35E, 31G, 33T, etc.). (b) The aircraft s 3 or 4 character location identifier. b. TRACON must: (1) Coordinate with Tower prior to combining or de-combining the Riverside and Pomona sectors to confirm the status of any aircraft in the Rundown lists. (2) Monitor the Rundown Tab List and release aircraft as soon as practical. (3) Acknowledge changes in aircraft sequence initiated by Tower. 2. VFR/SVFR Procedures. a. Tower must: (1) Enter VFR/SVFR aircraft into the Rundown List and include in the remarks section the aircraft s destination prefaced with a V (i.e. VSNA, VLGB, VMYF, VEMT, VSBP, etc.). (2) Depart VFR/SVFR aircraft in any order without regard to their order in the rundown list after initiating the flash for the departing aircraft. (3) When instructed by TRACON, depart VFR/SVFR aircraft only after TRACON steadies the flash. b. TRACON must: (1) Coordinate with Tower prior to combining or de-combining the Riverside and Pomona Sectors to confirm VFR departure status for aircraft already in Rundown Lists. (2) Monitor the Rundown list and acknowledge entries as soon as possible. (3) Advise Tower when TRACON requires Tower to release VFR/SVFR aircraft only after TRACON steadies the flash. 5-2
Attachment 6 ARTS AUTOMATED POINT OUT PROCEDURES 1. TRACON and Tower must adhere to the procedures in this attachment when utilizing the Automated Point Out function. 2. ARTS Automated point Out Procedures apply to the POC ILS/LOC, POC RNAV (GPS) RWY 26L approaches, CCB IFR approaches and to all VFR aircraft. a. Use of the ARTS Automated Point Out function is authorized for IFR operations as described below: (1) Norton, Pomona, and Riverside Sectors are authorized to use the ARTS Automated Point Out function for point outs to Tower for POC arrivals executing the POC ILS/LOC and RNAV (GPS) RWY 26L approaches. Acceptance of the Automated Point Out by Tower authorizes Norton, Pomona, and Riverside Sectors to enter Tower airspace established on the POC ILS/LOC and RNAV (GPS) RWY 26L final approach course and authorizes the aircraft to descend in accordance with the approach procedure. (2) Pomona Sector is authorized to use the ARTS Automated Point Out function for point outs to Tower for CCB arrivals executing the CCB VOR/GPS approaches. Acceptance of the Automated Point Out by Tower authorizes Pomona Sector to enter Tower airspace established on the CCB VOR/GPS approach procedures/missed approach, and for the aircraft to descend/climb in accordance with the procedures. b. Use of the ARTS Automated Point Out function is authorized for VFR operations as described below: (1) VFR altitude information must be forwarded to the receiving controller through the use of secondary scratch pad data or through verbal coordination. (2) After the Automated Point Out is completed, the transferring controller must not modify information contained in the full data block unless it is verbally coordinated. (3) The transferring controller must verbally forward any pertinent information not available from the full data block. (4) The receiving controller must verbally forward any restrictions or pertinent traffic to the transferring controller prior to accepting the point out. (5) Acceptance of the Automated Point Out constitutes approval for transition as specified in the scratch pad, or verbal coordination. 6-1
(6) Acceptance of an Automated Point Out with LCL in the primary scratch pad constitutes approval for maneuvering in the receiving controller s area of jurisdiction. Verbal coordination is required when the operation terminates. c. Tower and TRACON must notify the other facility if Tower or TRACON radar displays become unusable for the purposes of applying Automated Point Out procedures. Verbal coordination in lieu of Automated Point Out procedures will be utilized. 6-2
Attachment 7 OPPOSITE DIRECTION OPERATIONS (ODO) 1. GENERAL PROCEDURES a. Procedures for same runway opposite direction operations are applicable when both opposing aircraft are IFR. b. STANDARD ODO (CONTRA FLOW ) (1) Arrivals: All turbojets must land ONT RWY 26L/R (2) Departures: All turbojets must depart ONT RWY 8L/R c. NON-STANDARD ODO (1) Any other ODO configuration at ONT. NOTE- CONTRA FLOW is IAW ONT ATCT Order 7110.13 ONTARIO AIRPORT NOISE ABATEMENT PROCEDURES and normally in effect daily 2200L to 0700L. d. Traffic advisories must be issued to both the arriving and departing aircraft. EXAMPLE- OPPOSITE DIRECTION TRAFFIC (distance) MILE FINAL, (type aircraft). OPPOSITE DIRECTION TRAFFIC ONE FIVE MILES EAST, (type aircraft). OPPOSITE DIRECTION TRAFFIC DEPARTING RUNWAY (number), (type aircraft). e. Do not allow opposite direction same runway operations with opposing traffic inside the cutoff point unless an emergency situation exists. f. Ensure that opposite direction operations conducted from parallel runways provide for a turn away from the opposing traffic when inside of the cutoff point to the other runway. 2. COORDINATION a. TOWER Local Control and TRACON arrival sector are responsible for initiating coordination required to accomplish an opposite direction arrival or departure. (1) STANDARD ODO apply normal coordination IAW local directives. (2) NON-STANDARD ODO apply the provisions below: (a) TOWER must verbally request opposite direction departures with TRACON. (b) TRACON must verbally request opposite direction arrivals with TOWER. (c) All coordination must be on a recorded line and must state, Opposite Direction, and include call sign, type, and arrival or departure runway. 7-1
NOTE- When CONTRA FLOW is in effect, the coordination prescribed above in 2.a. (2) (a) through 2.a. (2) (c) is not required; normal arrival/departure coordination may be used as prescribed in FAA Order JO 7110.65 and IAW local directives. 3. ARRIVAL VS DEPARTURE a. Tower and TRACON must ensure the departure is airborne and observed turning to avoid conflict prior to the arrival aircraft reaching a ten (10) NM radius from the arrival runway threshold. 4. ARRIVAL VS ARRIVAL a. TRACON arrival sector must ensure the first arrival has crossed the runway threshold prior to the opposing arrival reaching a ten (10) NM radius from the arrival runway threshold. 7-2