South Queensland Manual of Air Traffic Services Supplementary Procedures. Civil Military Aviation Coordination - 3 (CMAC-3) Air Force Headquarters

Transcription

1 South Queensland Manual of Air Traffic Services Supplementary Procedures Procedure ATS-PROC-0007 Version 24 Effective 3 May 2018 Authorised: Operations Standards & Assurance Manager Civil Military Aviation Coordination - 3 (CMAC-3) Air Force Headquarters ATTENTION Temporary amendments may apply Ensure document is current before use Airservices Australia of 44

2 Change summary South Queensland Manual of Air Traffic Services Supplementary Procedures Version 24: Effective 3 May 2018 Location of change Change description 1.1 Inserted SHN as Sunshine Sector in unit definition NRFC Exception for R644 and R650A relocated to further down in the table no change to procedures or intent procedures amended for R638 A/B/C/D Addition of Military Flying to airspace Change airspace from Firing to Military flying/non flying Clause removed requiring SM2 to advise WLM ATC when R671 is voice released Section amended to incorporate current TLI 17_ Temporary MATS Supp 2017_22 - R650 Transit Routes Military Piot instructions removed as they are included in other internal military documentation. These sections include: Radio failure military aircraft Emergency advice to AMB Clearance Echo clause removed Hung Bomb tracking amended Air test aircraft clause removed New Clauses to incorporate current TLI 17_ Coordination Procedures for Acft Tracking via an RNAV APP into YTWB Coordination and Procedure for RWY29 RNAV YTWB Coordination and Procedure for RWY11 RNAV YTWB Reworded for clarification no change to intent or procedures Star numbers removed to cover STAR changes without requiring an update to Document No Change to intent or procedures Section amended to include TLI 17_0312 (NRFC 36137) - Changes to YBAF Arrivals Procedures Request the corridor section amended removed points a & b 4.2 Military ATS Failure clause added 4.3 Abnormal Operations section added to incorporate TLI 17_0167 This document was created using Air Traffic Services (ATS) Operational Document Template (C-TEMP0256) Version 3. View change summaries for the previous six months 2 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

3 Table of contents 1 Definitions Airservices Defence Operational context Airspace administration Area of Airspace management and release responsibilities , deactivation and release procedures Corridor R662/R671 operations R638 operations SWBTA pilot operations Normal operations Ancillary information Amberley coordination Oakey coordination Military AAR and AEWC Airspace (MAAA) operations Business continuity Civil ATS failure Military ATS Failure Abnormal Operations Contact numbers ATS-PROC-0007 Version 24: Effective 3 May of 44

4 This page is intentionally blank 4 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

5 1 Definitions Airservices Abbreviation AF TWR BAN BAP BAS BDN BDS BN ENR BN SM2 BN TCU BUR DOS GOL GRN INL ORM SHN SM TCU SS Definition Archerfield Tower Brisbane Approach North Brisbane Approach Planner Brisbane Approach South Brisbane Departures North Brisbane Departures South Brisbane En route (all Brisbane ATS sectors excluding BN TCU) Brisbane ATSC Aisle 2 Shift Manager Brisbane Terminal Control Unit comprises of BAN/BAP/BAS/BDN/BDS/SM TCU Burnett Sector Downs Sector Gold Coast Sector Grafton Sector Inverell Sector Operations Room Manager Sunshine Sector Shift manager for BN TCU Systems Supervisor Defence Abbreviation ABCP AMB FHQ FLTCDR OK RCO Definition Air Base Command Post RAAF Amberley Fleet Headquarters Flight Commander Oakey Range Control Officer ATS-PROC-0007 Version 24: Effective 3 May of 44

6 This page is intentionally blank 6 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

7 2 Operational context Airspace administration Purpose Airspace management This document: a) describes airspace management procedures (including operating procedures and services provided to participating and non-participating aircraft); b) describes the role of the Airspace Administrator; and c) nominates the airspace arbiter. References The primary references for airspace and air route information is the Designated Airspace Handbook - DAH (ATS-MAN-0039). Prohibited, Restricted and Danger area (PRD) administration Submit all requests for new PRD and amendments or cancellation of existing PRD to 452SQN AMB FLT (FLTCDR) for recommendation/approval and subsequent processing by OAR. Direct requests for temporary airspace to the OAR. Primary User The 'Primary User' is the Airspace Administrator and will establish a priority for the use of the airspace. The Primary User must only provide access to other users if the Administrator s commitments allow. This may mean the total exclusion of other airspace users. Note: 1) Due to the restrictive nature of this function, the role of Primary User is seldom applied by Airspace Administrators. 2) As an Airspace Administrator, Airservices normally performs the role of 'Airspace Coordinator'. ATS-PROC-0007 Version 24: Effective 3 May of 44

8 Airspace Coordinator As Airspace Coordinator, the Airspace Administrator will: a) designate airspace for its own use; b) coordinate access to other airspace users in a manner which keeps overall inconvenience to a minimum and as far as practical will evenly spread inconvenience among all users; c) make every effort to accommodate activities and adjust procedures and facilities to achieve this; and d) consider the effect of airspace decisions on general and military aviation activities for which airspace is not specifically designated and provide for such activities within the airspace insofar as is practical. Alternatively, minimise airspace activation to reduce its effect on other airspace users. Arbiter The arbiter provides services and day to day management of the airspace and will operate in accordance with the agreed procedures promulgated in Manual of Air Traffic Services (MATS) Supplementary Procedures. The various Airspace Administrators must reach agreement on the management of the designated airspace and operations within it. The Arbiter does not need to be a direct employee of the Airspace Administrator. Area of Dimensions The area of for airspace and airspace management covered by these procedures is delineated as: S E, S E, S E, S E, S E, S E, S E, S E, S E 8 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

9 Diagram Airspace management and release responsibilities Operating hours AMB ATC hours of operation are published by NOTAM. The Army Aviation Centre hours are published by NOTAM. Airspace requests and NOTAM publication notification Where practical, the Controlling Authority must issue the NOTAM at least eight hours prior to activating. No further notification is required. BN ATC may accept a minimum of two hours notice. Negotiate with BN ATC or ORM if shorter notice is required. Exceptions: R644 and R650A require eight hour notification, short notice activation not available. ATS-PROC-0007 Version 24: Effective 3 May of 44

10 R608 Longreach Military non-flying Senior OPSO 1 RSU RAAF (Primary User) H24 R609 Evans Head Military flying FLTCDR 452SQN Amberley AMB ABCP (Primary User) NOTAM AMB CTR/R625 A/B/C/D Amberley - Military flying FLTCDR 452SQN Amberley (Primary User) NOTAM 30 minutes prior, AMB ATC Advise activation time to BAP, GOL, DOS, AF TWR and OK APP Raise/amend NOTAM if required Five minutes, AMB APP Obtain radar hand-offs/idents from DOS Deactivation Prior to NOTAM expiry At requested deactivation time At NOTAM expiry Five minutes prior, AMB APP Request deactivation from DOS Complete RADAR hand-offs/idents to DOS Remain on duty until DOS accepts. When agreed: a) advise deactivation to BAP, GOL, AF TWR and OK APP; and b) cancel/amend NOTAM if required. Complete radar hand offs/idents to DOS Remain on duty until DOS accepts Advise deactivation to BAP, GOL, AF TWR and OK APP. 10 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

11 R633 A/B Greenbank Military non-flying Army RCO Greenbank (Primary User) R633A-D EXPH or as amended by NOTAM R633B NOTAM. Send the NOTAM request to the NOF R634 A/B Canungra - Military flying/non-flying Communications not required Army RCO Canungra (Primary User) R634A - NOTAM R634B - NOTAM. Send the NOTAM request to the NOF R634B has limited CTA intrusion and does not pose significant problems to the control of air traffic. Communications to commence or cease firing is not required R637 A/B/C/D Amberley Military flying FLTCDR 452SQN Amberley (Primary User) NOTAM R638 A/B/C/D Evans Head - Military flying/non-flying up to FL160 above FL160 Deactivation FLTCDR 452SQN Amberley (Primary User) NOTAM AMB PLNR must advise GRN at least 30 minutes prior NOTAM Issue the NOTAM at least eight hours before activation unless otherwise agreed by BN ATC AMB ATC must advise GRN ATS-PROC-0007 Version 24: Effective 3 May of 44

12 R639 A/B/C/D Amberley - Military flying Deactivation FLTCDR 452SQN Amberley (Primary User) NOTAM If less than eight hours notice is provided, advise OK at least 30 minutes before activation AMB ATC must advise OK if deactivation time differs from NOTAM deactivation time R644 Amberley - Military flying FLTCDR 452SQN AMB (Primary User) NOTAM Only activate this area when there is no other alternative and keep the duration of activation to a minimum Note: This area causes traffic management issues for civil traffic. R647 A/B Wallangarra Military non-flying Thales Duty Officer Army (Primary User) R647A - H24 R647B - NOTAM R650 A/B Amberley - Military flying of R650A FLTCDR 452SQN AMB (Primary User) NOTAM Only activate this area when there is no other alternative and keep the duration of activation to a minimum Note: This area causes traffic management issues for civil traffic. 12 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

13 Oakey CTR/R654 A/B/C Oakey Military Flying Five minutes prior to OK CTR activation, OK ATC Five minutes prior to OK CTR deactivation, OK ATC FLTCDR 452SQN OK (Primary User) NOTAM OK ATC must provide 30 minutes notice of activation to AMB ATC and DOS Obtain radar hand-offs/idents from DOS Complete radar hand-offs/idents with DOS Remain on duty until DOS accepts R662 A/B Amberley - Military flying FLTCDR 452SQN AMB (Primary User) NOTAM R671 A/B Amberley Military flying FLTCDR 452SQN AMB (Primary User) NOTAM R680 Akens Is, R682 Townshend Is, R683 Cape Clinton Military flying/non-flying Army RCO Shoalwater Bay (Primary User FL310 and below) BN ATC (Airspace coordinator above FL310) NOTAM. Send the NOTAM request to the NOF R684 A/B Mt Hummock - Military flying/non-flying R684A - Army RCO Shoalwater Bay (Primary User) R684B - Army RCO Shoalwater Bay (Primary User FL310 and below) - BN ATC (Airspace coordinator above FL310) NOTAM. Send the NOTAM request to the NOF ATS-PROC-0007 Version 24: Effective 3 May of 44

14 R685 A/B Wide Bay - Military flying/non-flying Cease fire Army RCO Wide Bay (Primary User FL150 and below) BN ATC (Airspace coordinator above FL150) NOTAM. Send the NOTAM request to the NOF Consult with BN ORM when activating above FL150 and before submitting the request to the NOF Cease firing on request from BN ORM R686 Triangular Island Military flying/non-flying Army RCO Shoalwater Bay (Primary User) NOTAM. Send the NOTAM request to the NOF R687 A/B Raspberry Creek - Military flying/non-flying R687A - Army RCO Shoalwater Bay (Primary User) R687B - Army RCO Shoalwater Bay (Primary User FL310 and below) R687A - H24 - BN ATC (Airspace coordinator above FL310) R687B - NOTAM. Send the NOTAM request to the NOF R689 Shoalwater Bay - Military flying/non-flying Army RCO Shoalwater Bay (Primary User FL310 and below) BN ATC (Airspace coordinator above FL310) NOTAM. Send the NOTAM request to the NOF 14 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

15 R693 Elliott Military flying/non-flying Communications and firing Cease firing Airspace release Fleet HQ Potts Point Navy (Primary User FT and below) BN ATC (Airspace coordinator above FT) OCS must send the request to FHQ who are responsible for buffer calculation and issuing the NOTAM through the NOF. Negotiate with BN ORM to establish an appropriate upper limit. NOTAM Provide a two-way radio link with BN ATC through BN Flightwatch before commencing firing. The Navy OSC must: a) complete a comms check every 30 minutes. This check constitutes a clearance to commence/continue firing from BN ATC; and b) maintain continuous listening watch. Cease firing when: a) contact cannot be made for comms checks. Do not recommence firing until comms are re-established; or b) requested by BN ATC. When firing is finished, release the airspace to BN ATC using the phrase R693 RELEASED to AIR TRAFFIC CONTROL. Call BN using: a) 6610KHz; b) 3452 KHZ; or c) BN SS. R695 A/B/C Herbert Creek Military Flying/non-flying R695 A/B Army RCO Shoalwater Bay (Primary User) R695C Army RCO Shoalwater Bay (Airspace coordinator) R695A H24 R695B NOTAM. Send the NOTAM request to the NOF R695C NOTAM. Send the NOTAM request to the NOF ATS-PROC-0007 Version 24: Effective 3 May of 44

16 R725 Saumarez Military Flying FLTCDR 452SQN AMBERLEY (Primary User) NOTAM, deactivation and release procedures Short notice activations of RAs BN SM2 Shift Manager Notification Advise the BN SM2 when short-notice activation of R609, R625, R637, R638, R639, R650, R654, R662 or R671 is required. Voice deactivation of RAs AMB/OK responsibilities AMB/OK may deactivate the restricted airspace with less than 30 minutes notice. Deactivation may be at the time coordination is received or as specified. There must be no military aircraft in R637, R638, R639, R644, R650, R662 and R671 for them to be voice deactivated. Coordinate deactivation of R637, R638, R639, R644, R650, R662, R671 AMB CTR, R625 OK CTR, R654 With BN SM2 DOS DOS Voice releases of RAs AMB responsibilities AMB must propose the release of R637, R638, R639, R644, R650, R662 and R671 to the BN SM2. BN SM2 responsibilities Advise AMB when: a) you obtain agreement from all affected sectors; or b) if agreement cannot be reached. 16 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

17 Emergencies, weather deviations and airspace releases Airservices responsibilities Airservices may request a release of portions of AMB restricted airspace when there are emergency or severe weather events. Note that a release may not always be available. The following standard releases have been defined to simplify coordination: Airspace release AMB Overland A/B Overland C/D Overwater North Overwater Link Overwater Central Overwater South Dimensions Within 30 NM BN - A070 and above Outside 30 NM BN - A090 and above R639A/B FL210 and above R639C/D FL250 and above R637A/B/C/D FL210 and above R644 FL210 and above R650AB FL210 and above R662A/B/R671 FL210 and above When requesting the release, use the phrase: 'REQUEST RELEASE [Airspace Release(s)]'. AMB responsibilities AMB may offer the above releases to Airservices to assist with traffic management. Do not use this option if it is possible to deactivate airspace that is no longer required. Major Military exercises Defence responsibilities Release all or parts of exercise airspace to Airservices if it: a) is not required for significant periods of time (generally in excess of one hour); and b) cannot be deactivated. Apply vertical buffers within residual airspace to contain military activities. Fax the details of the exercise airspace release to the BN ORM on the pro-forma. Contact the BN ORM to confirm receipt. Complete coordination when resuming airspace with the BN SM2. Advise Airservices when the release is valid to. When the release must be cancelled earlier, provide at least 30 minutes notification. Negotiate with Airservices to resolve traffic issues. Note: 1) The release is automatically cancelled at the advised time. 2) These procedures will be incorporated into the MOU for the exercise. 'Exercise Airspace' includes SBX and any associated temporary restricted airspace. ATS-PROC-0007 Version 24: Effective 3 May of 44

18 Airservices responsibilities BN ORM/SM must advise affected sectors of the airspace releases. You may use the levels advised when airspace is released. Corridor For aircraft within a corridor, AMB ATC must: a) monitor the aircraft within 3 NM of the nominal track using a surveillance system with a lateral separation standard not greater than 5 NM; b) positively control the aircraft; and c) keep the aircraft on frequency. Purpose of and access to corridors Transit corridors have been established to facilitate transit of MIL aircraft to/from AMB and the training areas. Clearances through the corridors may be available from AMB ATC (AMB CEN). Corridors may be active concurrently. Levels shown are usable by corridor aircraft. BN ATC will apply a 5 NM lateral and 1000 FT vertical buffer to the corridors. Corridor waypoints Waypoint Latitude/longitude Waypoint Latitude/longitude SUPER S E BLITZ S E RHINO S E MOSSI E MURJO S E ANSON S E JEZZA S E VIRGE S E ZORRO S E 18 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

19 Corridor dimensions Brisbane Corridor North (BNCORN) 3 NM north to 3 NM south of the track MURJO - ZORRO - JEZZA and 3 NM north to 3 NM south of the track ZORRO - BLITZ - ANSON - MOSSI - BLITZ - ZORRO. FL260 to FL280. Brisbane Corridor Common (BNCORCOM) dimensions 3 NM north to 8 NM south of the track SUPER - MURJO from the AMB airspace boundary to MURJO. FL190 to FL280. Brisbane Corridor South (BNCORS) 3 NM north to 3 NM south of the track MURJO - ZORRO - JEZZA and 3 NM either side of the track ZORRO - VIRGE. FL260 to FL280. ATS-PROC-0007 Version 24: Effective 3 May of 44

20 Diagram of corridors 20 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

21 Transit route for non-corridor traffic Planning outbound transit routes Aircraft that cannot meet corridor requirements and tracking must plan outbound via: a) R637 via SUPER - MURJO - ZORRO - BLITZ - MOSSI/ANSON above A100; and b) R650 via BN - COODA - BONEY - R650, above A100. Planning inbound transit routes Aircraft that cannot meet corridor requirements and tracking must plan inbound via: a) R637 via ANSON - BN AMB, FL180; and b) R650 via BONEY - SAVER - AMITY - BN - AMB, FL180. Other emergencies Military aircraft If unable to remain in the corridor AMB ATC must advise affected BN sectors if aircraft are unable to remain in the corridor. AMB ATC must provide adjacent sector frequencies to aircraft prior to exiting the corridors. Note: When immediate excursion from the corridor is required, aircraft will contact the affected BN ATC sector and advise intentions. If time does not permit contact with the sector, aircraft will squawk 7700 and transmit intentions on guard frequency. Emergencies Civil aircraft When a civil aircraft emergency requires transit of the corridors, BN ATC must coordinate with AMB ATC (AMB CN) as soon as possible. R662/R671 operations R662/671 clearances/nocom details/sar responsibilities Unless requested by AMB APP, BN ATC is not required to: a) issue clearances to military aircraft to operate within R662/R671; b) hold or request NOCOM details from military aircraft; or c) hold SARWATCH for aircraft operating within R662/R671. ATS-PROC-0007 Version 24: Effective 3 May of 44

22 Flight planning F18S transiting between AMB and R662/R671 when BIG AMB is active: Must plan AMB to R662 R662 to AMB Route ZZ931: AMB - COWIE - MAYSO - LAGOB - CG VOR - FL270 ZZ932: SEMAJ - CG VOR - RISON - PERSA - FL280 F18S transiting between AMB and R662/R671 when LIL AMB is active, or other aircraft that wish to enter R662 that cannot comply with the BYRON ONE level restriction: Must plan AMB to R662 R662 to AMB Route AMB - BAKEL - GAMBL - PIGGY - FL150 Note: Request FL270 on first contact with ZZ932: SEMAJ - CG VOR - RISON - PERSA - FL280 Coded clearance Byron One For aircraft transiting to R662 AMB APP must include '[CLEARED BYRON ONE, FL190]' when coordinating taxi to GOL. Coded clearance BYRON ONE (F18S aircraft) Description Track via ZZ931 (or waypoints as specified) to establish OPS with R662. FL190, reach FL190 by COWIE. Note: BN ATC will assign FL270 when available. Operations complete When operations within R662 are completed: a) contact BN centre on for identification and onwards clearance; b) remain within R662 until clearance is issued; and c) depart R662 at FL280 unless otherwise cleared. Note: Aircraft may be issued reach FL200 X RISON when inbound to AMB. Radio failure Radio failure aircraft within R662/R671 must: 1) squawk 7600; 2) remain within R662 for five minutes if operationally viable; 3) track via ZZ932 route at FL280; 4) from CG descend to FL200, reach FL200 X RISON; 5) from PERSA descend to FL140 direct AMB; and 6) from AMB descend to 5100 FT, direct IAF BIGIX for ILS Y/TACAN Y RWY of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

23 R638 operations R638 clearances/nocom details/sar responsibilities Unless requested by AMB APP, BN ATC is not required to: a) issue clearances to military aircraft to operate within R638; b) hold or request NOCOM details from military aircraft; or c) hold SARWATCH (remains with AMB/RSO). AMB APP may provide transit clearances to non-military aircraft when it is not being used for military operations. When a civil aircraft is cleared to transit R638 on descent, GRN must ensure the descent clearance complies with LSALT requirements in CTA. Flight planning Aircraft transiting between AMB and R638: Must plan AMB to R638 R638 to AMB Route AMB - BAKEL - GAMBL - FL150 PIGGY - GAMBL - BAKEL - FL140 Operations complete When operations within R638 are completed: a) contact BN Centre on for identification and onwards clearance; b) remain in R638 until clearance is issued; and c) depart R638 at FL140 unless otherwise cleared. On completion of OPS departing OCTA, contact BN Centre on for identification, IFR traffic and NOCOM details (if necessary). Radio failure Radio failure aircraft within R638 must: 1) squawk 7600; 2) remain within R638 for five minutes if operationally viable; 3) track JAYDE (S E ) direct YAMB at FL140; and 4) from AMB descend to 5100 FT, direct IAF BIGIX for ILS Y/TACAN Y RWY15. Hung bomb Aircraft with a hung bomb must: a) contact BN CTR on for identification and onwards clearance; and b) track via JAYDE direct YAMB, FL140. ATS-PROC-0007 Version 24: Effective 3 May of 44

24 SWBTA pilot operations Hung bomb Aircraft with a hung bomb, tracking from SWBTA to: a) AMB must track via - ADGAD (S E E), UKAPI (S E ), TAROL (S S E ), AMB; or b) TL must track via - S E , TL. Note: Aircraft with a hung bomb will avoid built-up areas and sharp turns. 24 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

25 3 Normal operations Ancillary information OK/AMB intercom lines are shared BN ATC sectors must prefix any calls with their sector name. Note: These lines are shared by a number of units and a 'tone' will block transmission for the first few seconds of each call. Aircraft operate to the boundary of restricted airspace AMB ATC may operate up to the boundary of AMB CTR and all restricted areas without prior coordination. AMB ATIS ZULU When AMB is not active, ATIS Information ZULU must include the statement: '...FOR CLIMB ABOVE A045 CONTACT BRISBANE CENTRE ON AT TAXI, OR OR AIRBORNE FOR CLEARANCE'. BN ENR planner positions When planner positions are used: a) Fraser and Byron will coordinate when their respective planner positions are opened and closed; b) use the cold-line when coordinating with the planner position; and c) use the hot-line when coordinating with the relevant executive position. Amberley coordination Access to AMB airspace AMB ATC must notify the BN ORM as soon as possible when aircraft on routes transiting AMB airspace must be kept clear of military airspace. AMB ATC must advise the BN SM 2 that exclusive military use of the airspace is required: a) 30 minutes prior to the airspace being resumed; or b) as soon as the need is recognised when the requirement was unforeseen. Note: A number of air routes that transit AMB restricted areas may be unavailable due to exercises or short notice high traffic density. ATS-PROC-0007 Version 24: Effective 3 May of 44

26 Training Restricted Areas Prior to aircraft entering AMB training Restricted Areas R637, R638, R639, R644, R650, R662 and R671, BN ENR must: a) confirm that the aircraft has a clearance and provide frequency transfer instructions; or b) instruct the aircraft to remain clear of the restricted area until a clearance has been issued. Note: Not required for aircraft that have departed AMB or are operating within a MAAA. BN ENR must advise the BN SM 2 if aircraft are not in receipt of a clearance. General coordination BN ATC to Amberley Coordination with AMB When coordinating with AMB: a) coordinate aircraft 50 NM or 10 mins (whichever is the lesser) prior to the boundary of AMB airspace; b) coordinate taxi for aircraft within 15 mins flight time or 50 NM (whichever is the lesser) from AMB airspace; and c) relay radar identification for boundary coordination at least 10 NM prior to the boundary. Coordination and Procedure for RWY 29 RNAV YTWB For aircraft arriving at YTWB via the RWY29 RNAV Approach not planned through AMB airspace: 1) DOS will coordinate an ident only to AMB for aircraft tracking for the RWY29 RNAV including any holding requests/requirements; 2) With AMB approval, DOS is responsible for clearing an aircraft through AMB airspace as required for the approach (including holding if required); and 3) AMB must advise if they have any frequency requirements. Variations to coordination Vary coordination in accordance with the following exceptions: 1) Coordination of the STAR clearance is not required; 2) BN ENR must advise AMB APP if aircraft are not on the STAR (excluding RWY01 GLENN arrivals); 3) For aircraft inbound to YBBN via PARRY Y195 coordinate the route to PARRY only; and 4) When Little AMB only is active; i) provide an ident only for aircraft inbound to YBBN; ii) AMB APR will have no vertical restrictions at or above A050 unless advised. 26 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

27 Boundary coordination not required Do not coordinate to AMB ATC aircraft tracking: a) BN IBUNA; b) on or east of the BN 196 VOR Radial; c) on or north of WOODY KEVIE when arriving at YBBN and little AMB is active; or d) BIVAT MESED after departure. General coordination AMB ATC to BN ATC When coordinating with BN ATC: a) if aircraft have previously received a service from BN ATC, coordinate aircraft prior to 10 NM from the boundary; b) coordinate taxi for aircraft originating in Amberley restricted areas; c) AMB ATC must relay radar identification to GOL for aircraft on AMB ATC frequency tracking VONDO-GLENN. Note: General coordination on aircraft previously receiving a Eurocat service can be done in the hand-off. Standard assignable levels between BN ENR and Amberley Assigning sector Standard assignable level Amberley status BN ENR to AMB FL210 Big AMB AMB to BN ENR FL200 BN ENR to AMB A090 Little AMB AMB to BN ENR A080 You do not need to include the standard assignable level when voice coordinating. Hand-offs between BN ENR and Amberley When handing off aircraft: a) clean hand-offs apply between BN ENR and AMB ATC; and b) initiate hand-off prior to 5 NM from the boundary. ATS-PROC-0007 Version 24: Effective 3 May of 44

28 Responsibility of SARWATCH between BN ENR and AMB ATC When an aircraft is subject to SARWATCH: a) AMB ATC is responsible for SARWATCH after hand-off to BN ENR until aircraft reach the boundary of BN ENR airspace; b) BN ENR is responsible for SARWATCH after hand-off to AMB ATC until aircraft reach the boundary of AMB airspace; c) AMB ATC is responsible for SARWATCH of YTWB departures east on receipt of taxi coordination; d) DOS is responsible for SARWATCH for YBWW departures via BIVAT eastbound; and e) negotiate all other SARWATCH on taxi coordination. Note: SARWATCH rests with the group receiving the taxi call until otherwise coordinated/negotiated. Toogoolawah parachuting coordination Requesting airspace release Fraser will coordinate an airspace release as follows: Fraser: 'REQUEST TOOGOOLAWAH [LEVEL]' AMB: 'CONCUR TOOGOOLAWAH [LEVEL]' Parachute aircraft may then operate within 5 NM of Toogoolawah drop zone (coordinates S E) and remain clear of the R625C/D boundary. AMB ATC must separate all traffic within their airspace from the coordinated area. Cancelling airspace release Fraser will cancel the airspace release once parachutes and aircraft have left A085 as follows: Fraser: 'CANCEL TOOGOOLAWAH' AMB: 'CANCEL TOOGOOLAWAH' Amberley departures between the AMB150 and AMB330 radials (clockwise) Unless otherwise instructed by ATC, military aircraft may: a) depart within 10 NM radius of AMB direct to the first waypoint; or b) intercept track within 10 NM. 28 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

29 Coordination BN TCU to AMB ATC (excluding YBAF) BN TCU SM TCU or Flow BAP must advise AMB PLNR If BDS is merged with BAS/BDN when: a) AMB opens; and b) following any subsequent changes. a) Runway in use at YBBN on opening and during periods of BN CATIS failure; and b) BDS position on opening and any subsequent change to BDS position. Coordination for Departure from YBBN via Q237 For departures via GORDY, Brisbane TCU must: a) ensure aircraft reach A070 or above by GORDY; or b) if unable advise AMB ATC prior to 5 NM from the boundary. Taxi coordination to AMB ATC is not required when aircraft have planned via GORDY at A090 or above and Little Amberley is active. Coordination AMB ATC to Brisbane TCU (excluding Archerfield) Aircraft entering BN TCU Tracking Duty RWY at BN North of the AMB GLENN Track On or south of the AMB GLENN TRACK and the aircraft is at (level) AMB must coordinate with and the aircraft is at (level) AMB must coordinate with All CTA Above A075 BDN BAN BDN All CTA Above A075 BDS BAS BDS Exception - KEVIE STAR Coordinate all aircraft on the KEVIE STAR with BAN. AMB departures between the AMB 006 and 137 TACAN radials inclusive that will enter BN TCU AMB APP will coordinate 'NEXT [RUNWAY], [CALLSIGN]' with BAN/BDN/BAS/BDS. When a heading cannot be negotiated, AMB must: a) Keep the aircraft clear of BN TCU airspace; and b) Coordinate a new track or heading when airborne. ATS-PROC-0007 Version 24: Effective 3 May of 44

30 Standard assignable levels between AMB ATC and BN TCU Departures Standard assignable level AMB status AMB to BN TCU FL180 Big AMB BN TCU to AMB FL180 AMB to BN TCU A080 Little AMB BN TCU to AMB A090 Arrivals Tracking via AMB to BN TCU A050 WOODY KEVIE or AMB GLENN landing RWY01 AMB to BN TCU FL130 AMB GLENN landing RWY19 You do not need to include the standard assignable level when voice coordinating. STAR allocation When allocating STARs: a) AMB ATC must issue STARs to aircraft landing YBBN and issued an airways clearance by AMB ATC; and b) DOS must issue STARs to all other aircraft landing YBBN via AMB airspace. Note: BAP will coordinate the appropriate STAR and (if required) feeder fix time Issue the following STARs to aircraft inbound to YBBN: STAR allocation table Tracking via RWY 01 RWY 19 RWY 14 RWY 32 AMB No STAR SINNK (x) arrival GLENN transition No STAR BFL to advise STAR and approach WOODY KEVIE (x) ALPHA KEVIE (x) ALPHA KEVIE (x) ALPHA KEVIE (x) ALPHA Arrival RWY 01 Arrival RWY 19 Arrival RWY 14 Arrival RWY 32 (BFL will advise BAN) 30 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

31 Hand-offs between AMB and BN TCU AMB to BN TCU When handing-off aircraft to BN TCU: a) initiate hand-off prior to 3 NM from the boundary; and b) For aircraft arriving YBBN, BN TCU must apply the following restrictions: i) not below A050; ii) Aircraft tracking AMB-GLENN remain on track; iii) not below A080 when landing RWY 19 YBBN and tracking AMB-GLENN; or iv) not south of the WOODY-KEVIE track if cleared on that track. BN TCU to AMB When BN TCU propose a hand-off for aircraft planned above FL200, AMB APP may: a) instruct BN TCU to transfer the aircraft to the next control unit using the phrase '[CALLSIGN] DIRECT [SECTOR]'; and b) advise the next unit that the aircraft will transfer direct from BN TCU and specify any restrictions. Transfer of SARWATCH Transfer of SARWATCH commences at the: a) BN TCU airspace boundary when AMB hand off aircraft to BN TCU; and b) AMB ATC airspace boundary when BN TCU hand off aircraft to AMB. YBAF coordination departures Taxi advice BN TCU must coordinate taxi advice with AMB APP on all IFR departures planned through AMB airspace. Western departures AMB APP must advise SHN when Western departures are not available by using the phrase 'WESTERN DEPARTURES NOT AVAILABLE'. BN TCU must include 'WESTERN DEPARTURE' in taxi coordination if the aircraft is IFR and will: a) depart in VMC by day; b) will remain clear of BN TCU airspace; and c) depart as a VFR departure if AF TWR is active. Note: Aircraft will contact AMB APP on when established in class G and by 15 minutes from the taxi coordination time. ATS-PROC-0007 Version 24: Effective 3 May of 44

32 AMB APP will identify the aircraft and: a) issue a clearance to keep the aircraft clear of BN TCU Class C airspace if available; or b) provide a SIS on SHN's behalf. If the aircraft has departed using VFR departure procedures, confirm the flight category on first contact. If the aircraft changes to VFR, AMB APP must advise the next sector. YBAF (radar) SID departures BN TCU must provide a next call to AMB APP for IFR aircraft: a) departing on an AF SID (radar) between the AF206 and AF309 tracks (clockwise); and b) coordinate an agreed heading into AMB airspace. When a heading cannot be negotiated, BN TCU must: a) keep the aircraft clear of AMB airspace; and b) coordinate a new track or heading when airborne. AMB ATC is responsible for terrain clearance for aircraft departing on an AF SID (radar) once the aircraft enters AMB Airspace. YBAF coordination arrivals AMB must complete coordination with SHN by 40BN where possible. SHN must advise any tracking or level restrictions and must nominate the agency for hand-off where transfer of control service is required. Standard assignable levels and for further coordination with BN TCU, if required, are as follows: Flight rules Conditions Standard Level Responsibility for other required BN TCU Coordination IFR IMC or at night A034 SHN IFR By day in VMC Establish the aircraft in Class G airspace on entering BN TCU airspace AMB VFR Night A040 SHN VFR Day Establish the aircraft in Class G airspace on entering BN TCU airspace AMB Note: Include in coordination the standard levels for AF arrivals to ensure the expected level is understood. 32 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

33 Corridor management Request the corridor AMB APP will request the corridor at clearance issue. Corridor coordination From To Via Phrase Response AMB DOS H/L or C/L REQUEST BRISBANE CORRIDOR (NORTH/SOUTH) WILL ADVISE DOS BUR/GOL/ SDY H/L REQUEST BRISBANE CORRIDOR (NORTH/SOUTH) CONCUR BRISBANE CORRIDOR (NORTH/SOUTH) [FROM (time)] or WILL ADVISE DOS (after concurrence from BUR/GOL) BAP H/L BRISBANE CORRIDOR (NORTH/SOUTH) ACTIVE [FROM (time)] BRISBANE CORRIDOR (NORTH/SOUTH) [FROM (time)] DOS SM2 Most appropriate means BRISBANE CORRIDOR (NORTH/SOUTH) ACTIVE [FROM (time)] BRISBANE CORRIDOR (NORTH/SOUTH) [FROM (time)] DOS AMB H/L BRISBANE CORRIDOR (NORTH/SOUTH) ACTIVE [FROM (time)] AMB DOS H/L or C/L CANCEL BRISBANE CORRIDOR (NORTH/SOUTH) BRISBANE CORRIDOR (NORTH/SOUTH) ACTIVE [FROM (time)] CANCEL BRISBANE CORRIDOR (NORTH/SOUTH) DOS BUR/GOL/ SDY/BFL/ SM2 H/L CANCEL BRISBANE CORRIDOR (NORTH/SOUTH) CANCEL BRISBANE CORRIDOR (NORTH/SOUTH) Oakey coordination General coordination Fraser to Oakey When coordinating to Oakey: a) coordinate aircraft 50 NM or 15 mins (whichever is the lesser) prior to the boundary of OK airspace; b) coordinate taxi for aircraft within 15 mins flight time or 50 NM (whichever is the lesser) to OK airspace; c) relay radar identification for boundary coordination at least 10 NM prior to the boundary; and d) coordinate requests for approaches that will infringe OK airspace before issuing them to the aircraft. ATS-PROC-0007 Version 24: Effective 3 May of 44

34 Coordination and Procedure RWY 11 RNAV YTWB For aircraft arriving at YTWB via the RWY11 RNAV Approach: 1) DOS will coordinate RWY11 RNAV approach requests to OK APP; 2) On approval from OK APP, DOS must re-clear and hand-off the aircraft to OK APP as coordinated; 3) DOS must pass any known traffic to the aircraft prior to hand-off to OK APP; 4) DOS must advise OK APP of any additional traffic after the aircraft has been transferred; and 5) OK APP must transfer the aircraft directly to the YTWB CTAF unless instructed otherwise, and advise the aircraft to cancel SARWATCH on Variations to coordination Provide OK APP with an ident only for aircraft descending via MATVI LUKEY. Descend aircraft not below A060 or as advised by OK APP until clear of OK airspace. General coordination Oakey to Fraser When coordinating to Fraser: a) If aircraft have previously received a Eurocat service, coordinate aircraft prior to 10 NM from the boundary; and b) Coordinate taxi for aircraft originating in ADATS airspace. Note: General coordination on aircraft previously receiving a Eurocat service can be done in the hand-off. Variations to coordination Unless air-working in OK airspace, Fraser does not require coordination for aircraft: a) previously receiving a Eurocat service; and b) transiting OK to land at YTWB, YBWW, YAGL or YDAY. Standard assignable levels between DOS and OK Sectors DOS/AMB to OK OK to DOS Standard assignable level 500 FT above OK activation level 500 FT below OK activation level Readback standard assignable levels. Arrivals surrounding OK airspace When aircraft are arriving in close proximity to OK: a) OK APP will transfer aircraft descending through their airspace and landing at YTWB, YBWW, YAGL or YDAY; direct to the CTAF; b) DOS will be responsible for SARWATCH; and c) OK APP will advise aircraft to cancel SARWATCH on of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

35 Hand-offs between OK APP and Fraser When aircraft are handed-off: a) clean hand-offs apply from DOS to OK APP unless R639 is active; b) when R639 is active, hand-offs from DOS to OK APP are clean below A100; c) all hand-offs from OK APP to DOS have no restrictions on climb; and d) hand-offs must be initiated prior to 5 NM from the boundary. Responsibility of SARWATCH between DOS and OK APP When an aircraft is subject to a SARWATCH: a) OK APP is responsible for SARWATCH of YTWB departures via MESED on receipt of taxi coordination; and b) Fraser is responsible for SARWATCH for all other aerodromes adjacent to OK (including YBWW). YBWW departures On receipt of taxi coordination for aircraft planned BIVAT - MESED, OK APP may advise '[NO FREQUENCY REQUIREMENTS]'. DOS is then responsible for issuing airways clearance on track BIVAT MESED with any requirements OK APP stipulates on taxi coordination. Military AAR and AEWC Airspace (MAAA) operations Airspace and service Section 24 DAH lists the defined volumes for MAAA operations. Provide services within these volumes as per the extant airspace classification. Defence accepts for separating military traffic within an MAAA and associated Restricted Areas. Operations within AM11, AM13, AM22 and AM24 may occur without activation of R637 and R650. Approving MAAA operations up to the boundary of Restricted Areas Clear AEW&C and tanker aircraft to operate up to the boundary of adjoining Restricted Areas: AEW&C and tanker clearance request (callsign) REQUEST CLEARANCE TO OPERATE IN (MAAA designator) (levels). MARSA WITH AIRCRAFT WITHIN (restricted area designator). ATC response (callsign) CLEARED TO OPERATE IN (MAAA designator) (levels). MARSA WITH AIRCRAFT WITHIN (restricted area designator). Note: All aircraft manoeuvring will be contained within the MAAA. ATS-PROC-0007 Version 24: Effective 3 May of 44

36 Approving MAAA operations to enter adjoining Restricted Areas AEW&C and tanker clearance request Request clearance to exit the MAAA and enter the adjoining restricted area. ATC response (callsign) CLEARED TO EXIT (MAAA designator) FOR (restricted area designator). Note: AEW&C/tanker manoeuvring for the restricted area will be contained within the MAAA and maintains MARSA within aircraft within the restricted area. Approving aircraft within Restricted Areas to operate in adjoining MAAA AEW&C and tanker clearance request (callsign) REQUEST CLEARANCE TO EXIT (restricted area designator) to OPERATE IN (MAAA designator) (levels). If tanker receives request for refuel aircraft to exit the restricted area and enter the MAAA: (callsign) REQUEST TANKING OPS (MAAA designator). (Number of receiving aircraft). ATC response (callsign) CLEARED TO OPERATE IN (MAAA designator) (levels). (callsign) CLEARED TANKING OPS (MAAA designator). ATC is not required to issue MARSA clearances to the tanker or receiving aircraft Note: 1) The tanker will relay the clearance to the aircraft involved. 2) All aircraft will operate MARSA. 3) All manoeuvring will be contained within the MAAA and the Restricted Areas. 4) The tanker will advise ATC that 'TANKING OPS COMPLETE' when the receiving aircraft have re-entered the restricted area. MAAA Flight planning Enter RMK/MARSA (restricted area designator) OPS in the flight plan when AEW&C and tanker aircraft intend to operate within a MAAA and up to the boundary of the adjoining restricted area. MAAA Communications Aircraft operating within an MAAA must maintain primary communications within civil ATC. At least one military aircraft operating within R637 or R650 must monitor the appropriate BN ATC frequency. Note: AMB ATC communications within AM11 are unreliable. 36 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

37 SAR Scenario Aircraft operating within military Restricted Areas and receiving aircraft involved in AAR within a MAAA AEW&C/tanker aircraft operating within a MAAA SAR Military BN ATC When a military aircraft declares an emergency on the civil frequency, relay the details to AMB ATC. ATS-PROC-0007 Version 24: Effective 3 May of 44

38 This page is intentionally blank 38 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

39 4 Business continuity Civil ATS failure Eurocat degraded modes If there is an unplanned outage of Eurocat equipment, the BN ORM may advise that they are operating in 'degraded mode'. When Eurocat is not functioning normally expect: a) start clearances may be required (contact SM TCU); b) delays; c) voice coordination of estimates, level and route; and d) requests for radar separation. Contingency procedures When an ATS contingency affects Airservices Australia administered airspace, the ORM or Contingency Response Manager will forward a checklist appropriate to the contingency to the relevant Defence unit(s) by fax or . Defence will use the checklist to respond to the ATS contingency. Military ATS Failure In the event of a total evacuation of a military ATS facilities, the relevant facility will coordinate an airspace release with DOS. DOS will inform BN SM2 who will notify all affected Brisbane ATS units. Abnormal Operations Applicable Restricted Areas This section is applicable to the following restricted areas only: a) R637 A/B/C/D; b) R638 A/B/C/D; c) R639 A/B/C/D; d) R650 A/B; e) R662 A/B; and f) R671 A/B. ATS-PROC-0007 Version 24: Effective 3 May of 44

40 Likelihood of deviations The likelihood of aircraft deviating into active restricted areas due to weather will be defined by status levels. Status Level definitions Amber Red Adverse weather is forecast but the impact is expected to be minor. No significant impact on the compatibility of civil operations with military activity is expected. Short term deviations around isolated thunderstorms or similar is considered likely. A manageable increase in coordination is likely, however the increase in workload should always remain manageable. Adverse weather is forecast for the near future. The severity and position of the weather hazard is expected to significantly impact on the compatibility of civil operations with military activity. Widespread off track deviations have or are anticipated to commence. Increased coordination is required and controller workload will be abnormally high. Assessment of status level BN SM2 will assess the status of the airspace by 0000Z and 0400Z daily and at any time it is considered necessary due current weather conditions. If Status Level is assessed as Red or Amber, following consultation and agreement between BN SM2 and AMB ASPR the following procedures are to apply: Status Amber a) When the level is determined to be Amber BN SM2 or appropriate OCA holder will: i) review acceptance rate; ii) consider implications of weather and traffic management; iii) review sectorisation and the use of Planner consoles to maximise existing sector capacity; iv) consider alternative route clearances for aircraft arriving and departing aircraft; v) notify external agencies via the NCC as per National ATS Administration Manual (NAAM) (ATS-MAN-0013) clause 2.4; and vi) facilitate the short-term activation of restricted airspace in consultation with 452SQN AMB FLT where it is practical to do so. b) When the level is determined to be AMBER 452SQN AMB FLT will initiate contact with flying SQN requesting them to: i) review current and planned flying activity; ii) identify periods that may facilitate airspace releases to Airservices; iii) assess the feasibility of using alternate airspace for planned military operations to facilitate civil deviations; and iv) provide BN SM2 an initial assessment within 20 minutes. 40 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

41 Status Red a) When the level is determined to be Red BN SM2 or appropriate OCA holder will: i) implement traffic management procedures; ii) request airspace releases from 452SQN AMB FLT as appropriate for traffic management purposes; iii) review expected delays against document En Route Supplement Australia - ERSA (ATS-MAN-0038) and NOTAM information and initiate hazard alerting; iv) update notification to external agencies via NCC as per NAAM clause 2.4; and v) consult with 452SQN AMB FLT at agreed time intervals until the conditions improve and status is assessed as Amber or better. b) When the status level is determined to be Red 452SQN AMB FLT will: i) contact the flying SQN executive to determine options to delay, redirect or cancel as appropriate; ii) determine the ability to de-conflict military operations from potential diverting civil aircraft; iii) provide BN SM2 an initial assessment within 10 minutes; and iv) implement appropriate weather releases. ATS-PROC-0007 Version 24: Effective 3 May of 44

42 This page is intentionally blank 42 of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007

43 5 Contact numbers Contact Phone number Army R633 Greenbank RCO R634 Canungra RCO Oakey ATC Oakey ATC Flight Commander R685 Wide Bay RCO Shoalwater Bay Training Area RCO Navy FHQ FXP Watchkeeper RAAF Amberley Switch 1300 DEFENCE Amberley aircraft emergency Amberley Fire Tower Amberley Base Command Post/Duty Officer Amberley ATC Approach Supervisor Amberley ATC Operations Commander (OPSCDR) Amberley ATC Flight Commander SQN Operations XO 6 SQN SQN Operations XO 1 SQN SQN Mission Support XO 33 SQN SQN Operations XO 36 SQN ATS-PROC-0007 Version 24: Effective 3 May of 44

44 Contact Phone number Brisbane Centre ORM SS SM TCU SM Aisle NOF Ph: Fax: of 44 Version 24: Effective 3 May 2018 ATS-PROC-0007