Southern California Terminal Radar Approach Control and Ontario Airport Traffic Control Tower
|
|
- Karin Cole
- 5 years ago
- Views:
Transcription
1 Southern California Terminal Radar Approach Control and Ontario Airport Traffic LETTER OF AGREEMENT SUBJECT: Interfacility Coordination and Control Procedures Effective: August 16, 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 and ONT , dated August 17, 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 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.
2 (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 (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 VFR -- fly heading 235, maintain VFR at or below (b) Low approach Riverside 1. IFR -- fly direct PDZ, climb and maintain VFR -- fly heading 140, climb and maintain VFR at or below (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
4 (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
5 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
6 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 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 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
7 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
8 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 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 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
9 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 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
10 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
11 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
12 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 After receiving IFR releases from TRACON, separate IFR arrivals and departures utilizing visual separation or non-radar separation procedures specified in FAAO 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
13 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
14 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
15 Attachment 1 ONT TOWER DELEGATED AIRSPACE 30 SFC 25 SFC Riverside Drive 1-1
16 Attachment 2 EMPIRE AREA SECTOR BOUNDARIES NORTON SECTOR POMONA SECTOR NORTON SECTOR ONT WEST RIVERSIDE SECTOR ONT EAST RIVERSIDE SECTOR 2-1
17 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 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 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
18 (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 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 (b) Via the Riverside Sector, direct PDZ, maintain 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 d. Aircraft departing via a DP must be assigned initial altitudes as follows: (1) POMONA DP (2) HASSA DP (LAX is east traffic)
19 (3) PRADO DP 7000 (4) ONTARIO DP (LAX and ONT are east traffic) 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 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 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 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 b. Aircraft departing via the Riverside Sector c. Aircraft departing via the Norton Sector
20 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
21 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
22 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) 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
23 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
24 (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
25 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
26 (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
27 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 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
28 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 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
Southern California TRACON and Lindbergh Tower LETTER OF AGREEMENT SUBJECT: INTER-FACILITY COORDINATION AND CONTROL PROCEDURES
Southern California TRACON and Lindbergh Tower LETTER OF AGREEMENT EFFECTIVE: September 13, 2012 SUBJECT: INTER-FACILITY COORDINATION AND CONTROL PROCEDURES 1. PURPOSE. This agreement establishes procedures
More informationVATUSA PHOENIX TRACON and VATUSA PHOENIX ATCT LETTER OF AGREEMENT. SUBJECT: Interfacility Coordination Procedures
VATUSA PHOENIX TRACON and VATUSA PHOENIX ATCT LETTER OF AGREEMENT EFFECTIVE: 01/08/08 SUBJECT: Interfacility Coordination Procedures 1. PURPOSE. This Letter of Agreement establishes procedures for coordinating
More informationVATUSA C90 TRACON AND O HARE ATCT LETTER OF AGREEMENT
VATUSA C90 TRACON AND O HARE ATCT LETTER OF AGREEMENT EFFECTIVE: 02/01/2019 SUBJECT: INTERFACILITY COORDINATION 1. PURPOSE: This agreement establishes coordination procedures and defines delegation of
More informationU. S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIA1-ION ADlWlNlSTRATlON Southern California TRACON SUBJ: Inter-Facility Coordination Procedures Southern California TRACON and John Wayne Tower Letter of Agreement
More informationGreenville Spartanburg International
ZTL ARTCC Greenville Spartanburg International Airport Traffic Control Tower Standard Operating Procedures GSP 7110.65B Effective: May 1, 2011 1 CHAPTER 1. GENERAL CONTROL SECTION 1. EQUIPMENT 2-1-1. Callsign
More informationPiedmont Triad International Airport
ZTL ARTCC Piedmont Triad International Airport Airport Traffic Control Tower Standard Operating Procedures GSO 7110.65B Effective: May 1, 2011 1 CHAPTER 1. GENERAL CONTROL SECTION 1. EQUIPMENT 1-1-1. Callsign
More informationCharlotte - Douglas International Airport Traffic Control Tower
Charlotte - Douglas International Airport Traffic Control Tower Standard Operating Procedures CLT ATCT 7110.65D Effective: May 1, 2011. 1 1-1-1. Callsign Usage and Frequency Delegation: CHAPTER 1. GENERAL
More informationZTL ARTCC. Asheville Regional. Air Traffic Control Tower. Standard Operating Procedures AVL B. Effective: May 1, 2011
ZTL ARTCC Asheville Regional Air Traffic Control Tower Standard Operating Procedures AVL 7110.65B Effective: May 1, 2011 CHAPTER 1. GENERAL CONTROL SECTION 1. EQUIPMENT 1 1-1-1. Callsign Usage and Frequency
More informationZTL ARTCC. Augusta Regional
ZTL ARTCC Augusta Regional Air Traffic Control Tower Standard Operating Procedures AGS 7110.65B Effective: May 1, 2011 1 CHAPTER 1. GENERAL CONTROL SECTION 1. EQUIPMENT 1-1-1. Callsign Usage and Frequency
More informationERIE ATCT STANDARD OPERATING PROCEDURES
ORDER ERI ATCT 7110.10I ERIE ATCT STANDARD OPERATING PROCEDURES August 1, 2014 VATUSA CLEVELAND ARTCC VIRTUAL AIR TRAFFIC SIMULATION NETWORK VIRTUAL AIR TRAFFIC SIMULATE NETWORK UNITED STATES DIVISION
More informationBurlington ATCT Standard Operating Procedures
This air traffic control procedural document is provided for virtual air traffic control in the ZBW ARTCC of the VATSIM network only. It is not for real-world ATC use. These procedures are approved for
More informationSOUTHERN CALIFORNIA TRACON LOS ANGELES AREA STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC
SOUTHERN CALIFORNIA TRACON LOS ANGELES AREA STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC 1 Table of Contents SECTION 1. GENERAL 4 1-1. PURPOSE 4 1-2. SCOPE OF
More informationSOUTHERN CALIFORNIA TRACON BURBANK AREA STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC
SOUTHERN CALIFORNIA TRACON BURBANK AREA STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC 1 Table of Contents SECTION 1. GENERAL 3 1-1. PURPOSE 3 1-2. SCOPE OF RESPONSIBILITIES
More informationNOTAM AIRCRAFT OWNERS AND PILOTS ASSOCIATION (AOPA) FLY-IN CHINO AIRPORT (CNO) CHINO, CALIFORNIA
NOTAM AIRCRAFT OWNERS AND PILOTS ASSOCIATION (AOPA) FLY-IN CHINO AIRPORT (CNO) CHINO, CALIFORNIA EFFECTIVE 12:00 NOON LOCAL FRIDAY, SEPTEMBER 19, 2014 UNTIL 6:00 PM LOCAL SATURDAY, SEPTEMBER 20, 2014 TEMPORARY
More informationVIRTUAL AIR TRAFFIC SIMULATION NETWORK UNITED STATES DIVISION. SUBJ: Phoenix (PHX) Air Traffic Control Tower (ATCT) Standard Operating Procedures
VIRTUAL AIR TRAFFIC SIMULATION NETWORK UNITED STATES DIVISION ALBUQUERQUE ARTCC ORDER PHX ATCT v7110.1a Effective Date: Sept. 18, 2014 SUBJ: Phoenix (PHX) Air Traffic Control Tower (ATCT) Standard Operating
More informationDenver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES
Denver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES OCTOBER 7, 2018 Definition of Airspace Colorado Springs Class C airspace is defined as show in Appendix 1. Definition of Positions
More informationVirtual Jacksonville Air Route Traffic Control Center Tallahassee ATCT Standard Operating Procedures
Virtual Jacksonville Air Route Traffic Control Center Tallahassee ATCT Standard Operating Procedures TLH 7110.65 Effective Date: May 11, 2015 Chapter 1. General 1 1. General Information obtained in this
More informationProvidence ATCT Standard Operating Procedures
This air traffic control procedural document is provided for virtual air traffic control in the ZBW ARTCC of the VATSIM network only. It is not for real-world ATC use. These procedures are approved for
More informationRALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES
RALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES January 3, 2017 BULLETIN NUMBER RECORD OF CHANGES SUBJECT AUTHORIZED BY DATE ENTERED DATE REMOVED 7110.100 Initial RR 1/3/17 3/25/17 7110.101 Added
More informationThis section sets forth all Los Angeles World Airports (LAWA) noise abatement procedures, restrictions, and regulations involving aircraft operations.
This section sets forth all Los Angeles World Airports (LAWA) noise abatement procedures, restrictions, and regulations involving aircraft operations. 13.1. Aircraft Noise Abatement 13.1.1. All aircraft
More informationBOSTON ARTCC (vzbw) STANDARD OPERATING PROCEDURE KALB) ALBANY APPROACH (ALB
BOSTON ARTCC (vzbw) STANDARD OPERATING PROCEDURE ALBANY ATCT (KALB( KALB) ALBANY APPROACH (ALB APP) RELEASE RECORD Version Date Author Notes 1.0 24 April 2009 Initial Release 1.1 30 Jan 2015 BN Match ALB5
More informationAlbany ATCT Standard Operating Procedures
Albany ATCT Standard Operating Procedures This air traffic control procedural document is provided for virtual air traffic control in the ZBW ARTCC of the VATSIM network only. It is not for real-world
More informationSOUTHERN CALIFORNIA TRACON STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC
SOUTHERN CALIFORNIA TRACON STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC 1 SUBJ: Standard Operating Procedures VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES
More informationORDER MSY V. New Orleans. Standard Local Operating Procedures. Rev 3 December 7, 2011
ORDER MSY 7110.1V New Orleans Standard Local Operating Procedures Rev 3 December 7, 2011 Foreword This order defines the duties and responsibilities for personnel providing air traffic control services
More informationSection 5. Radar Separation
7/24/14 JO 7110.65V CHG 1 4/3/14 JO 7110.65V Section 5. 5 5 1. APPLICATION a. Radar separation must be applied to all RNAV aircraft operating at and below FL450 on Q routes or random RNAV routes, excluding
More informationCape Area Airports Standard Operating Procedures
Cape Area Airports Standard Operating Procedures This air traffic control procedural document is provided for virtual air traffic control in the ZBW ARTCC of the VATSIM network only. It is not for real-world
More informationZTL ARTCC / CLT ATCT LETTER OF AGREEMENT. EFFECTIVE: July 10, SUBJECT: APPROACH CONTROL SERVICE
ZTL ARTCC / CLT ATCT LETTER OF AGREEMENT EFFECTIVE: July 10, 2010. SUBJECT: APPROACH CONTROL SERVICE 1. PURPOSE: To delegate authority and responsibility for approach control services in the airspace described
More informationStandard Operating Procedures Atlanta Intl Airport (ATL) Air Traffic Control
SUBJ: Air Traffic Control This order prescribes air traffic control procedures and phraseology for use by personnel providing air traffic control services. Controllers are required to be familiar with
More informationCharlotte - Douglas International
Charlotte - Douglas International Standard Operating Procedures CLT TRACON 7110.65D Effective: May 1, 2011. 1 CHAPTER 1. Departure/Satellite Radar SECTION 1. EQUIPMENT 1-1-1. Callsign Usage and Frequency
More informationVATUSA-VATNZ-VATPAC OCEANIC PARTNERSHIP OAKLAND OCEANIC FSS GENERAL SOP 1 OCT 2012
VATUSA-VATNZ-VATPAC OCEANIC PARTNERSHIP EFFECTIVE OAKLAND OCEANIC FSS GENERAL SOP 1 OCT 2012 I. PURPOSE With the establishment of the VATNZ division of the Oceania Region on 1 January 2007, the Oakland
More informationFEDERAL AVIATION ADMINISTRATION CENTRAL EN ROUTE AND OCEANIC AREA OPERATIONS FORT WORTH ARTC CENTER, MAJORS ATCT, AND SKYDIVE TANDEM GREENVILLE, LLC
FEDERAL AVIATION ADMINISTRATION CENTRAL EN ROUTE AND OCEANIC AREA OPERATIONS FORT WORTH ARTC CENTER, MAJORS ATCT, AND SKYDIVE TANDEM GREENVILLE, LLC LETTER OF AGREEMENT Effective: April 10,2012 SUBJECT:
More informationChapter 6. Nonradar. Section 1. General DISTANCE
12/10/15 JO 7110.65W Chapter 6. Nonradar Section 1. General 6 1 1. DISTANCE Use mileage based (DME and/or ATD) procedures and minima only when direct pilot/controller communications are maintained. FIG
More informationNATIONAL BUSINESS AVIATION ASSOCIATION (NBAA) CONVENTION
NATIONAL BUSINESS AVIATION ASSOCIATION (NBAA) CONVENTION LAS VEGAS, October 10 12, 2017 In anticipation of a large number of aircraft operating to and from the Las Vegas area in conjunction with the 2017
More information9/23/2010 RDU B. Raleigh-Durham Air Traffic Control Tower. Standard Operating Procedures
Raleigh-Durham Air Traffic Control Tower Standard Operating Procedures 1) Purpose This order defines duties and responsibilities, depicts areas of airspace, runways, and taxiways allocated to each position
More informationUSE OF RADAR IN THE APPROACH CONTROL SERVICE
USE OF RADAR IN THE APPROACH CONTROL SERVICE 1. Introduction The indications presented on the ATS surveillance system named radar may be used to perform the aerodrome, approach and en-route control service:
More informationNOTAM. Aircraft Owners and Pilots Association (AOPA) Fly-In Colorado Springs Airport (COS) Colorado Springs, CO SPECIAL FLIGHT PROCEDURES
NOTAM Aircraft Owners and Pilots Association (AOPA) Fly-In Colorado Springs Airport (COS) Colorado Springs, CO SPECIAL FLIGHT PROCEDURES EFFECTIVE 12:00 Noon Local Friday, September 25, 2015 Until 6:00
More informationUnderstanding Role of Flight Data Processing Across NAS Operational Domains
Understanding Role of Data Processing Across NAS Operational Domains Elvan McMillen August 24, 1999 Organization: F062 Project: 02991204-O5 2 Context Presentations such as this can be used: - For developing
More informationINTERNATIONAL VIRTUAL AVIATION ORGANISATION CANADIAN AIR TRAFFIC CONTROL PHRASEOLOGY ATC OPERATIONS DECEMBER 2016 BY: MATHIEU LAFLAMME
INTERNATIONAL VIRTUAL AVIATION ORGANISATION CANADIAN AIR TRAFFIC CONTROL PHRASEOLOGY ATC OPERATIONS DECEMBER 2016!1 GENERAL Proper use of phraseology is one of the most important thing in aviation and
More informationVirtual Jacksonville Air Route Traffic Control Center Daytona Beach ATCT Standard Operating Procedures
Virtual Jacksonville Air Route Traffic Control Center Daytona Beach ATCT Standard Operating Procedures DAB 7210.3E Effective Date: May 11, 2015 Chapter 1. General 1 1. General Information obtained in this
More informationJACKSONVILLE CENTER AND SAVANNAH TRACON. LETTER OF AGREEMENT EFFECTIVE: December 22, 2006
SUBJECT: APPROACH CONTROL SERVICE EFFECTIVE: December 22, 2006 1. PURPOSE. This agreement between Jacksonville Center and SAV TRACON covers approach control service for airports within TRACON delegated
More informationD01 TERMINAL RADAR APPROACH CONTROL
Order D01 7110.65A D01 TERMINAL RADAR APPROACH CONTROL December 5, 2016 VATSIM D01 7110.65A Effective Date: Denver TRACON December 5, 2016 Northwest Mountain District VATUSA Subject: D01 Air Traffic Control
More informationStandard Operating Procedures
Allentown TRACON Standard Operating Procedures General This document describes the standard operating procedures for controlling at any of the positions within the Allentown TRACON and the airports it
More informationH O M E C O M I N G. NOTAM Aircraft Owners and Pilots Association (AOPA) Fly-In Frederick Municipal Airport (FDK) Frederick, MD
F L Y - I N AOPA H O M E C O M I N G FREDERICK, MD NOTAM Aircraft Owners and Pilots Association (AOPA) Fly-In Frederick Municipal Airport (FDK) Frederick, MD SPECIAL FLIGHT PROCEDURES EFFECTIVE 1200 NOON
More informationFrom: Commanding Officer, Naval Air Station Pensacola. Subj: NAVAL AIR STATION PENSACOLA CLOSED CONTROL TOWER AIRFIELD OPERATIONS
DEPARTMENT OF THE NAVY COMMANDING OFFICER NAS PENSACOLA 150 HASE ROAD STE-A PENSACOLA, FLORIDA 32508-1051 NAVAL AIR STATION PENSACOLA INSTRUCTION 3710.1 NASPCOLAINST 3710.1 N32 From: Commanding Officer,
More informationLETTER OF AGREEMENT (LOA)
LETTER OF AGREEMENT (LOA) East Hampton Airport (revision 1) EFFECTIVE: July 16, 2012 SUBJECT: VISUAL FLIGHT RULES (VFR)/SPECIAL VFR (SVFR) HELICOPTER OPERATIONS TO/FROM EAST HAMPTON AIRPORT 1) PURPOSE:
More informationPTK AIR TRAFFIC CONTROL TOWER OPERATION GOOD CHEER PROCEDURES 2018 (rev A, 12/05/18)
PTK AIR TRAFFIC CONTROL TOWER OPERATION GOOD CHEER PROCEDURES 2018 (rev A, 12/05/18) TABLE OF CONTENTS GENERAL INFORMATION.. 1 o Phone Numbers o Frequencies PREFLIGHT PLANNING o IFR Aircraft 2 o VFR Aircraft.3
More informationCHAPTER 5 SEPARATION METHODS AND MINIMA
CHAPTER 5 SEPARATION METHODS AND MINIMA 5.1 Provision for the separation of controlled traffic 5.1.1 Vertical or horizontal separation shall be provided: a) between IFR flights in Class D and E airspaces
More informationFederal Aviation Administration. Air Traffic 101. By: Michael Valencia & Dianna Johnston Date: Feb. 26, 2017
Presented to: UC Davis Aviation Symposium By: Michael Valencia & Dianna Johnston Date: Overview Part 1 Air Traffic Controllers History Safety and Navigation Terminology Air Traffic Facility Types Equipment
More informationLetter of Agreement by and between Jacksonville ARTCC and Miami ARTCC
Letter of Agreement by and between Jacksonville ARTCC and Miami ARTCC Effective Date: 1 November 2007 0400Z I. Scope: This agreement is made by and between Miami ARTCC (herein ZMA) and Jacksonville ARTCC
More informationVersion O January 21, 2019
Bradley ATCT and Y90 TRACON Standard Operating Procedures This air traffic control procedural document is provided for virtual air traffic control in the ZBW ARTCC of the VATSIM network only. It is not
More informationSID/STAR phraseology FAQ Canadian implementation April 27, 2017
SID/STAR phraseology FAQ Canadian implementation April 27, 2017 The International Civil Aviation Organization (ICAO) has developed harmonized phraseology for Standard Instrument Departures (SIDs) and Standard
More informationAnchorage ARTCC Phraseology Guide. Clearance Delivery Operations
Anchorage ARTCC Phraseology Guide Clearance Delivery Operations Initial Contact: The first time an aircraft calls you, you MUST identify your position, i.e. AWE123 Anchorage Delivery. Clearance Delivery:
More information1.2 An Approach Control Unit Shall Provide the following services: c) Alerting Service and assistance to organizations involved in SAR Actions;
Section 4 Chapter 1 Approach Control Services Approach Control Note: This section should be read in conjunction with Section 2 (General ATS), Section 6 (Separation Methods and Minima) and Section 7 (ATS
More informationPITTSBURGH ATCT STANDARD OPERATING PROCEDURES
ORDER PIT ATCT 7110.1I PITTSBURGH ATCT STANDARD OPERATING PROCEDURES August 1, 2014 VATUSA CLEVELAND ARTCC VIRTUAL AIR TRAFFIC SIMULATION NETWORK VIRTUAL AIR TRAFFIC SIMULATE NETWORK UNITED STATES DIVISION
More informationRELEASE RECORD. Version Date Author Notes Dec 2006 SK Initial Release
BOSTON ARTCC (vzbw) STANDARD OPERATING PROCEDURE BOSTON ARTCC (ZBW) RELEASE RECORD Version Date Author Notes 1.0 10 Dec 2006 SK Initial Release 2.0 01 Oct 2011 DO Major update, transformed from more of
More informationCLEARANCE INSTRUCTION READ BACK
CLEARANCE INSTRUCTION READ BACK 1. Introduction An ATC clearance or an instruction constitutes authority for an aircraft to proceed only in so far as known air traffic is concerned and is based solely
More information- Updated formatting - Re-drawn airspace delegation diagram
Z D C A R T C C - Updated formatting - Re-drawn airspace delegation diagram Change Log... 2 Table of Contents... 3 Chapter 1. Positions... 4 Chapter 2. Clearance Delivery... 5 Chapter 3. Ground Control...
More informationVATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT
VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT SUBJECT: TERMINAL AREA CONTROL SERVICE EFFECTIVE: September 1, 2016 1. PURPOSE. This agreement delegates authority and establishes procedures
More informationUNIVERSITY OF ALABAMA FOOTBALL
UNIVERSITY OF FOOTBALL SPECIAL AIR TRAFFIC PROCEDURES TUSCALOOSA, AL September 16, 2017 November 18, 2017 The following procedures will be implemented to enhance safety and minimize delays during the following
More informationATLANTA ARTC CENTER AND CHARLOTTE TOWER LETTER OF AGREEMENT
ATLANTA ARTC CENTER AND CHARLOTTE TOWER LETTER OF AGREEMENT EFFECTIVE: March 1, 2011 SUBJECT: APPROACH CONTROL SERVICE 1. PURPOSE: To delegate authority and responsibility for approach control services
More informationFLIGHT ADVISORY WASHINGTON D.C. SPECIAL FLIGHT RULES AREA LEESBURG MANUVERING AREA
FLIGHT ADVISORY WASHINGTON D.C. SPECIAL FLIGHT RULES AREA LEESBURG MANUVERING AREA EFFECTIVE October 11, 201609 0400 This Notice does not supersede restrictions pertaining to the use of airspace contained
More informationInstrument Refresher Course. Airfield Operations Flight Tower 412 OSS/OSAT
Instrument Refresher Course Airfield Operations Flight Tower 412 OSS/OSAT Overview Mission Priorities Class D Airspace Tower Services Traffic Patterns IFR Departures Lakebed Ops Miscellaneous Special Procedures
More informationTABLE OF CONTENTS. 3 Airport Managers Notice, Arlington Airport Closures. 4 Air Show Operations, Arlington Area Frequencies
2 In anticipation of the large number of aircraft operating to and from Arlington Municipal Airport during the Arlington Fly-In, the following procedures will be used to enhance safety and minimize air
More informationEFFECTIVE NOTAM KGON 10/06 SPECIAL FLIGHT PROCEDURES GROTON, CT
KGON GROTON-NEW LONDON AIRPORT GROTON, CT 17 10/06 10/07 NOTAM SPECIAL FLIGHT PROCEDURES EFFECTIVE 12:00 Noon EDT until 6:00 PM EDT Thursday, October 5, 2017 7:00 AM EDT until 6:00 PM EDT Friday, October
More informationVIRTUAL AIR TRAFFIC SIMULATION NETWORK CARIBBEAN DIVISION ZSU SAN JUAN CERAP
VIRTUAL AIR TRAFFIC SIMULATION NETWORK CARIBBEAN DIVISION ZSU SAN JUAN CERAP ORDER SJU 7110.1T SUBJ: San Juan Luis Muñoz Marín International Airport Air Traffic Control Tower Standard Operating Procedures
More informationThe NOTAM described will replace previously issued FDC NOTAMs 6/2550 and 7/7778 for the DC ADIZ/FRZ.
This advisory covers published NOTAMs 7/0206 for the DC ADIZ, 7/0211 for the DC FRZ and FDC 7/0204 for the outer speed restriction. WARNING This document only contains an overview of the new rules for
More informationEFFECTIVE NOTAM KOUN SPECIAL FLIGHT PROCEDURES 09/08 NORMAN, OK
KOUN WESTHEIMER AIRPORT NORMAN, OK 17 09/08 09/09 NOTAM SPECIAL FLIGHT PROCEDURES EFFECTIVE 12:00 Noon CDT until 7:30 PM CDT Thursday, September 7, 2017 7:00 AM CDT until 7:30 PM CDT Friday, September
More informationBOSTON ARTCC (vzbw) TRAINING SYLLABUS LEVEL: Center Controller (C1)
BOSTON ARTCC (vzbw) TRAINING SYLLABUS LEVEL: Center Controller (C1) I have lots more to do, a lot more to keep track of, so I ll do it right the first time and won t suck at it. (vzbw Center Controller
More informationVATUSA Approval 3/21/18
PANC SOP beta 1.0 2/30/2018 Ted Stevens Anchorage International Airport - PANC Air Traffic Control Tower STANDARD OPERATING PROCEDURES SUBJ: PANC SOP This order provides direction and guidance for the
More information2018 ARLINGTON FLY-IN JULY 6-8, 2018
0 2018 ARLINGTON FLY-IN JULY 6-8, 2018 Control Tower Hours and Airshow Closures 2 Frequency and Contact Guide 3 Communicating with ATC 4 VFR Route Planning to Green Valley 5 General Arrival Procedures
More informationSECTION 4 - APPROACH CONTROL PROCEDURES
SECTION 4 - APPROACH CONTROL PROCEDURES CHAPTER 1 - PROVISION OF SERVICES 1.1 An approach control unit shall provide:- a) Approach control service. b) Flight Information service. c) Alerting service. RESPONSIBILITIES
More informationJACK EDWARDS NATIONAL AIRPORT (JKA) GULF SHORES, AL
OCTOBER 26-27, 2018 JACK EDWARDS NATIONAL AIRPORT (JKA) GULF SHORES, AL SPECIAL FLIGHT PROCEDURES EFFECTIVE: Thursday Oct 25, 2018 12:00 NOON CDT until 6:00 PM CDT Friday Oct 26, 2018 7:00 AM CDT until
More informationPilot Information Packet
Pilot Information Packet Including Special Flight Procedures Chino, CA September 20, 2014 Airworthy using the most detailed, historically accurate and talented restorationists in the world. Welcome to
More informationCHAPTER 4 AIR TRAFFIC SERVICES
CHAPTER 4 AIR TRAFFIC SERVICES 4.1 Objectives of the air traffic services 4.1.1 The objectives of the air traffic services shall be to: a) prevent collisions between aircraft; b) prevent collisions between
More informationSECTION 6 - SEPARATION STANDARDS
SECTION 6 - SEPARATION STANDARDS CHAPTER 1 - PROVISION OF STANDARD SEPARATION 1.1 Standard vertical or horizontal separation shall be provided between: a) All flights in Class A airspace. b) IFR flights
More informationEXPLANATION OF TPP TERMS AND SYMBOLS
U.S. TERMINAL PROCEDURES PUBLICATION 52 EXPLANATION OF TPP TERMS AND SYMBOLS The discussions and examples in this section will be based primarily on the IFR (Instrument Flight Rule) Terminal Procedures
More informationJacksonville ARTCC. F11 TRACON Standard Operating Procedures
Document Number ZJX-10 Version A Effective Date 9/19/2018 Purpose Document Information ZJX 10A establishes procedures for staffing of the Central Florida TRACON radar positions (herein referred to as F11
More informationVFR Arrival and Departure Procedures Rocky Mountain Airshow 2012 Rocky Mountain Metropolitan Airport (KBJC)
VFR Arrival and Departure Procedures Rocky Mountain Airshow 2012 Rocky Mountain Metropolitan Airport (KBJC) Revision Date 07/26/2012 The Rocky Mountain Airshow will be held at Rocky Mountain Metropolitan
More informationAIR TRAFFIC ROUTE CONTROL CENTER
JACKSONVILLE AIR TRAFFIC ROUTE CONTROL CENTER KCHS CHARLESTON AFB/INT L AIRPORT STANDARD OPERATING PROCEDURES CHS 7110.65 TABLE OF CONTENTS CHAPTER 1 General... 4 1.1 Purpose... 4 1.2 Positions... 4 1.3
More information40 BEALEAFBI OCTOBER Chapter 8 RQ-4 OPERATIONS
40 BEALEAFBI11-250 1 OCTOBER 2012 Chapter 8 RQ-4 OPERATIONS 8.1. CERTIFICATE OF AUTHORIZATION. Pilots will comply with each COA and LOA in effect between Beale and other Air Traffic Control (ATC) facilities.
More informationVirtual Air Traffic Simulation Network (VATSIM) United States Division Fort Worth vartcc (ZFW)
Virtual Air Traffic Simulation Network (VATSIM) United States Division Fort Worth vartcc (ZFW) KDAL Dallas Love International Airport ATCT Standard Operating Procedures Rev. December 17, 2014 Approved:
More informationSan Juan CERAP. Standard Operation Procedures. Version 2.2 May 5th, Welcome to San Juan CERAP (ZSU ARTCC, TJZS FIR)
San Juan CERAP Standard Operation Procedures Version 2.2 May 5th, 2013 Welcome to San Juan CERAP (ZSU ARTCC, TJZS FIR) You are entering one of the most fascinating Combined Enroute Radar Approach Control
More informationOakland Air Route Traffic Control Center, Northern California Terminal Radar Approach Control, and Pacific Soaring Council LETTER OF AGREEMENT
Oakland Air Route Traffic Control Center, Northern California Terminal Radar Approach Control, and Pacific Soaring Council LETTER OF AGREEMENT SUBJECT: Pyramid and Minden Glider Area Operations EFFECTIVE:
More informationHOUSTON AIR ROUTE TRAFFIC CONTROL CENTER VATSIM United States Division. Letter of Agreement. Revised: July 25, 2004 Effective: July 25, 2004
HOUSTON AIR ROUTE TRAFFIC CONTROL CENTER VATSIM United States Division Letter of Agreement Revised: July 25, 2004 Effective: July 25, 2004 Purpose Scope This Letter of Agreement (LOA) establishes operating
More informationSANTA FE MUNICIPAL AIRPORT (SAF) SANTA FE, NM
SEPTEMBER 13-15, 2018 SANTA FE MUNICIPAL AIRPORT (SAF) SANTA FE, NM SPECIAL FLIGHT PROCEDURES EFFECTIVE: Thursday Sept 13, 2018 12:00 NOON MDT until 7:00 PM MDT Friday Sept 14, 2018 7:00 AM MDT until 7:00
More informationOptimization of Airspace and Procedures in the Metroplex
Optimization of Airspace and Procedures in the Metroplex Administration SoCal Metroplex Project Overview Brief To: By: Los Angeles World Airport Rob Henry, Manager SoCal Metroplex Jose Gonzalez, SoCal
More informationIFR SEPARATION WITHOUT RADAR
1. Introduction IFR SEPARATION WITHOUT RADAR When flying IFR inside controlled airspace, air traffic controllers either providing a service to an aircraft under their control or to another controller s
More informationIVAO Switzerland Division
IVAO ATC Operations Zurich Tower Date Updated by Update description 08.01.2016 CH-TC Document Creation 30.10.2017 CH-AOC Document Revision 1 Contents 1-Objective... 3 2-Zurich Tower LSZH_TWR... 4 3-Operating
More informationVATUSA CHICAGO ARTCC AND C90 TRACON LETTER OF AGREEMENT
VATUSA CHICAGO ARTCC AND C90 TRACON LETTER OF AGREEMENT EFFECTIVE: 01/16/2019 SUBJECT: INTERFACILITY COORDINATION 1. PURPOSE: This agreement establishes coordination procedures and defines delegation of
More informationMAR-A-LAGO TFR PROCEDURES
MAR-A-LAGO TFR PROCEDURES PBI PLAYBOOK Presented to: Pilots and Stakeholders By: USSS and FAA Date: PBI Departure PBI Arrival BCT CAYSL Arrival BCT Departure Traffic 12-26-2016 2 Table of Contents Chapter
More information- Initial. - Added MCRAY and new PDC s. - General update. - Added ATIS frequency - Added gate diagram appendix - Typo fixes - Minor formatting changes
Z D C A R T C C - Initial - Added MCRAY and new PDC s - General update - Added ATIS frequency - Added gate diagram appendix - Typo fixes - Minor formatting changes - Added altitude restrictions to nearby
More informationSULAYMANIYAH INTERNATIONAL AIRPORT MATS CHAPTER 11
KURDISTAN REGIONAL GOVERNMENT SULAYMANIYAH INTERNATIONAL AIRPORT MATS CHAPTER 11 SEPARATION STANDARDS & APPLICATIONS International and Local Procedures ( First Edition ) April 2012 Ff Prepared By Fakhir.F.
More informationAERONAUTICAL INFORMATION CIRCULAR 18/18
NAV CANADA 19 JUL 18 AERONAUTICAL INFORMATION CIRCULAR 18/18 GUIDANCE FOR STANDARD TERMINAL ARRIVAL (STAR) PROCEDURES The guidance currently published in the Transport Canada Aeronautical Information Manual
More informationRWY 24. Designator Route Remarks. All traffic shall initially climb to 4000FT QNH with climb gradient 3.3% MNM, unless instructed otherwise by ATC.
AD 2.ELLX-15 DISKI 2Y GTQ 7X GTQ 7Y MMD 7X RAPOR 4X 3.2.2 Climb Requirements RWY 24 Designator Route Remarks R-238 LUX to 8 DME LUX, RT to intercept R-222 NTM to 24 DME NTM, RT R-156 DIK, LT R-115 LUX
More informationKTPF PETER O. KNIGHT AIRPORT TAMPA, FL 10/27 NOTAM SPECIAL FLIGHT PROCEDURES EFFECTIVE
KTPF PETER O. KNIGHT AIRPORT TAMPA, FL 10/27 17 10/28 NOTAM SPECIAL FLIGHT PROCEDURES EFFECTIVE 12:00 Noon EDT until 7:00 PM EDT Thursday, October 26, 2017 7:00 AM EDT until 7:00 PM EDT Friday, October
More informationR-2515 R-2508 COMPLEX
R-2515 R-2508 COMPLEX Edwards AFB PPR Briefing Edwards AFB and Edwards Class D Surface Area lie within Restricted Area 2515: R-2515 and Edwards Class D Surface Area contain many flight hazards for aircrews
More informationSTANDARD OPERATING PROCEDURES (CLE SOP) December 3, 2016
ORDER VATSIM CLEVELAND ATCT ORDER CLE ATCT CLEVELAND HOPKINS INTERNATIONAL AIRPORT 7110.65I STANDARD OPERATING PROCEDURES (CLE SOP) December 3, 2016 Order CLE ATCT 7110.65I Standard Operating Procedures
More informationCOLLEGE FOOTBALL PLAYOFF NATIONAL CHAMPIONSHIP
2017 College Football Playoff National Championship Notices to Airmen COLLEGE FOOTBALL PLAYOFF NATIONAL CHAMPIONSHIP SPECIAL AIR TRAFFIC PROCEDURES TAMPA, January 8 10, 2017 In anticipation of a large
More informationCHICAGOLAND SPEEDWAY NASCAR RACES
CHICAGOLAND SPEEDWAY NASCAR RACES JUNE 28 THROUGH JULY 2, 2018 In anticipation of a significant number of aircraft traveling to the Chicago, Illinois, area during the Chicagoland Speedway NASCAR races,
More informationSEATTLE AIR ROUTE TRAFFIC CONTROL CENTER SEATTLE GLIDER COUNCIL LETTER OF AGREEMENT. EFFECTIVE: June 1, 2015
SEATTLE AIR ROUTE TRAFFIC CONTROL CENTER SEATTLE GLIDER COUNCIL LETTER OF AGREEMENT EFFECTIVE: June 1, 2015 SUBJECT: GLIDER OPERATIONS WITHIN CLASS A AIRSPACE 1. PURPOSE. This Letter of Agreement establishes
More information