WARNING. New South Wales Manual of Air Traffic Services Supplementary Procedures. Temporary amendments may apply. Procedure ATS-PROC-0038.

Transcription

1 Refer Temp MATS Supp 2017_21 or ATS_TLI_17_0341 Refer Temp MATS Supp 2018_03 or ATS_TLI_18_0051 Refer Temp MATS Supp 2018_07 or ATS_TLI_18_0061 New South Wales Manual of Air Traffic Services Supplementary Procedures Procedure Version 37 Effective 21 September 2017 Authorised: Operations Standards & Assurance Manager Airservices Australia Civil Military Aviation Coordination - 3 (CMAC-3) Air Force Headquarters WARNING Temporary amendments may apply Airservices Australia 2009 Ensure document is current before use

2 Change summary New South Wales Manual of Air Traffic Services Supplementary Procedures Location of change Change description Various Incorporated contents of Temp MATS Supp 2017_11/TLI 17_0132 'NSW MATS Supp amendments R418 and Nowra' 2315 NRFC Whole section removed Title changed to reflect new restricted area numbering 2861 Amendment to reflect new restricted area numbering 2861 Note Incorporated contents of Temp MATS Supp 2017_16/TLI 17_0201 'Decommissioning of 3845 WNA' 421 Amendment to reflect new restricted area numbering and removal of NWA CTR 431 Removal of NWA CTR row 437 Addition of radar ident to SRI by WOL when applicable This document was created using Air Traffic Services (ATS) Operational Document Template (C-TEMP0256) Version 2 View change summaries for the previous six months List of effective pages Part Pages Version: Effective date DC Document control 2 ToC Table of contents 2 Version 33: 4 August Definitions 2 2 Operational context 32 3 Normal operations - Williamtown 22 4 Normal operations - Nowra 6 5 Normal operations - Richmond 14 6 Normal operations - Canberra 2 Version 33: 4 August Business continuity 2 8 Contact numbers 2 Index Index 6 DC - 2 2

3 Table of contents Part 1 Part 2 Part 3 Part 4 Definitions Group name abbreviations Abbreviations - Richmond 1-2 Operational context Airspace administration Area of responsibility Airspace management and release responsibilities Transit corridors Civil Jet Corridor (CJC) Flight planning in corridors Airspace releases Naval East Australian Exercise Area (EAXA) procedures R555 Holsworthy procedures 2-26 Normal operations Williamtown Ancillary information Restricted Areas activation and deactivation Activation and deactivation of corridors Standard Oceanic Airspace Releases of R Temporary releases of Restricted Airspace Coordination and control practices - general Coordination and control practice BN ATC to WLM/3CRU Coordination and control practice WLM/3CRU to BN ATC R574 procedures R559 A-F procedures SSR code management 312 Corridor management Military AAR and AEW&C Airspace (MAAA) operations Normal operations - Nowra Ancillary information Restricted Areas activation and deactivation Coordination and control practices 44 Procedures when NWA ATC is not available Version 33: 4 August 2016 ToC - 1

4 Part 5 Part 6 Part 7 Part 8 Normal operations - Richmond Runway and airspace management between RIC and SY Clearances Amended route clearances Richmond arrivals - out of hours Unplanned movements at Richmond during Sydney curfew Training areas Area YARRA NSW Police Force SSR Codes Controlled abandonment of aircraft Airborne fuel dumping 5-13 Normal operations - Canberra RAAF Aircraft operations at Canberra International Airport Defence Firing Areas - adjacent to Canberra International Airport (D457 and D458) 6-2 Business continuity ATS system management Emergency operations 7-1 Contact numbers 8-1 Index Index - 1 ToC Version 33: 4 August 2016

5 Definitions Group name abbreviations 1 Definitions 11 Group name abbreviations Abbreviation Definition RAAF APP(L) WLM Approach (Low) - Terminal Approach APP(H) WLM Approach (High) - formerly WLM CEN Still referred to as CEN for coordination and radiotelephony purposes OPSCDR Operations Commander Navy FHQ Fleet Headquarters FXP Fleet Exercise Programme SO3 MARWKPR Staff Officer 3 Maritime Watchkeeper OCS Officer Conducting Serial ORS Operations Room Supervisor PWO Principal Warfare Officer Army RCO Range Control Officer Airservices ALM ATC Line Manager CNK Cessnock Sector GRN Grafton Sector HWE Howe Sector JVS Jervis Sector MAL Myall Sector MDE Mudgee Sector MLD Maitland Sector NAA Nambucca Sector OCN Ocean Sector ORM Operations Room Manager SAW Sydney Approach West SDS Sydney Departures South SM Shift Manager SNO Snowy Sector 1-1

6 Abbreviations - Richmond Definitions Abbreviation Definition Airservices SOS Sydney Operations Solo SRI Sydney Centre SS Systems Supervisor SYTM Sydney Traffic Manager WOL Wollongong Sector Note: See also Manual of Air Traffic Services (MATS) (NOS-SAF-2000) Part 1 Definitions Abbreviations - Richmond Abbreviation Definition LDD TA Londonderry Training Area LDD DZ Londonderry Drop Zone LFA Low Flying Area NTA Northern Training Area RT Roll Time RV Rendezvous Time STA Southern Training Area TOT Time on Target

7 Operational context Airspace administration 2 Operational context 21 Airspace administration 211 Purpose This document: c) 212 describes airspace management procedures (including operating procedures and services provided to participating and non-participating aircraft); describes the role of the airspace administrator; and nominates the airspace Arbiter References The primary references for airspace and air route information is the Designated Airspace Handbook (DAH) (ATS-MAN-0039) 213 Prohibited, Restricted and Danger (PRD) area administration FLTCDR 453SQN WLM FLT is the Regional Airspace Control Authority (RACA) for Defence administered PRD contained within the airspace described in 22 Area of responsibility Submit all requests for new PRD and amendments or cancellation of existing PRD to FLTCDR 453SQN WLM FLT for recommendation/approval and subsequent processing by OAR Direct requests for temporary airspace to the OAR 214 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 215 Note 1: Due to the restrictive nature of this function, the role of primary user is seldom applied by airspace administrators Note 2: As an airspace administrator, Airservices Australia (Airservices) normally performs the role of 'airspace coordinator' Airspace coordinator As airspace coordinator, the airspace administrator will: c) d) designate airspace for its own use; 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; make every effort to accommodate activities and adjust procedures and facilities to achieve this; and 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 2-1

8 Area of responsibility 216 Operational context Arbiter The Arbiter provides services and day to day management of the airspace and will operate in accordance with the agreed procedures promulgated in 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 22 Area of responsibility 221 Dimensions The area of responsibility for airspace and airspace management covered by these procedures is: S E, S E, S E, S E, S E, S E, S E, then along MURRAY RIVER to S E Figure Area of responsibility

9 Operational context Airspace management and release responsibilities Airspace management and release responsibilities 231 Airspace requests and NOTAM publication 2311 R368 Albury Military non-flying (demolition activity) Item Details Controlling authority and NOTAM responsibility ARMY RCO Albury (Army - primary user) Activation and amendments NOTAM The RCO must send the NOTAM request to Albury Tower when open, or the ML ORM when the tower is closed Albury Tower/ ML ORM will arrange for the NOTAM to be published Where practical, issue the NOTAM eight hours prior to commencement of activity If demolition activity is necessary with less than eight hours notice: advise as soon as possible; or determine if activity can be delayed until Albury Tower is open Notify Airservices of any amendments to the hours of activity RCO responsibilities Check the accuracy of the NOTAM before commencing activity Only use the area during the published NOTAM times Ensure that communications during demolition is always available Before commencing demolition: c) establish contact with Albury Tower If no contact, call the ML ORM; advise Albury Tower/ML ORM of the contact phone number and radio net; and confirm the status of Albury Tower Note: Procedures for demolition are dependant on whether Albury Tower is open or not Suspend operations when requested Advise Albury Tower/ML ORM when activities: Albury Tower responsibilities are suspended for at least one hour; or have ceased for the day Approve demolition activity subject to aircraft safety and facilitation of aircraft operations Separate aircraft from R368 when demolition is occurring Cancel the NOTAM when activities have ceased for the day ML ORM responsibilities Cancel the NOTAM when activities have ceased for the day if Albury Tower is not open 2-3

10 Airspace management and release responsibilities Operational context Demolition phraseologies Situation Albury Tower Prior to the commencement of demolition activity, the RCO must attain approval from Albury Tower When aircraft operations permit: DEMOLITION APPROVED ACKNOWLEDGE DEMOLITION APPROVED When Albury Tower: STOP DEMOLITION c) is unable to approve activity; requires temporary suspension; or requires cancellation 2312 ACKNOWLEDGE STOP DEMOLITION R405 A/B Sydney - Helicopters and seaplanes Item Details Controlling authority CASA OAR (airspace coordinator) Activation HJ 2313 RCO response R406 Temora Item Details Controlling authority Temora Historic Flight Club (airspace coordinator) Activation NOTAM 2314 R408/R415 Wagga - Military non-flying Item Details Controlling authority RAAF BCP Wagga (RAAF - primary user) Activation NOTAM 2315 R420F and R421A/B Nowra Item Details Controlling authority and NOTAM responsibility FLTCDR 453SQN NOWRA (NAVY - primary user) Activation NOTAM 2316 R424 Canberra Item Details Controlling authority and NOTAM responsibility School of Radio Physics Sydney University (primary user) Activation H

11 Operational context 2317 Airspace management and release responsibilities 2317 R428/R429 Tidbinbilla - Radiation hazard Item Details Controlling authority CSIRO Tidbinbilla (primary user) Activation H R452 Beecroft Head - Military flying/non-flying Item Details Controlling authority and NOTAM responsibility Fleet HQ Potts Point (NAVY - primary user) Activation NOTAM FHQ is responsible for NOTAM and airspace buffer calculations Activity in R452 takes precedence over the overlapping portions of R453 Communications 2319 The RSO must Monitor 2430 MHz during R452 shore bombardment serials R453 A/B Tasman Sea - Military flying/non-flying Item Details Controlling authority and NOTAM responsibility Fleet HQ Potts Point (NAVY - primary user) Activation NOTAM FHQ is responsible for NOTAM and airspace buffer calculations Activity in R452 takes precedence over the overlapping portions of R R469/R470 Richmond - Military flying Item Details Controlling authority and NOTAM responsibility FLTCDR 453SQN RIC FLT (RAAF - primary user) Activation D (one hour earlier HDS) or as amended by NOTAM RAAF must advise SYTM of any change to the status of R469 and R470 R469 must only be activated/deactivated with R470 R470 may be activated independently 2-5

12 Airspace management and release responsibilities Operational context R473 North Head - Military flying/non-flying Item Details Controlling authority DOTAM NDTAM NSW ACT (ARMY - primary user) Activation NOTAM Army units must provide OPS Support Branch Eastern Region at least two working days notice OPS Support must fax the NOTAM request to the Sydney TCU Traffic Manager The Sydney TCU Traffic Manager must add buffers and fax NOTAM requests to the NOF R485 A/B/C/D/E Tasman Sea - Military flying Item Details Controlling authority and NOTAM responsibility Fleet HQ Potts Point (NAVY - primary user) Activation NOTAM Item FHQ is responsible for NOTAM and airspace buffer calculations R489 Tasman Sea - Military flying/non-flying Details Controlling authority and NOTAM Fleet HQ Potts Point (NAVY - primary user) responsibility FHQ is responsible for NOTAM and airspace buffer calculations Activation NOTAM FHQ has priority for the use of R489 over R574 activities FHQ must advise of R489 activations to the WLM Military Airspace Coordinator (MAC) for tabling at each Weekly Planning Conference for the following week Subsequent changes must be coordinated with the 81 Wing Programming Officer Coordinate with Sydney TCU when affected, and record in the FXP

13 Operational context Airspace management and release responsibilities R494 Richmond - Military flying Item Details Controlling authority and NOTAM FLTCDR 453SQN RIC FLT (RAAF - primary user) responsibility Activation NOTAM Publish the NOTAM and advise SAW at least 30 minutes prior to activation Do not activate R494 unless R470 and R469 are activated Highest useable level Military Operations within R494 FL280 Lowest useable level Civil Operations overflying FL Where specific military circumstances require different altimetry procedures, the highest useable level must be recalculated to ensure that FL290 remains available in overlying CTA R495 A/B/C Tasman Sea - Military flying/non-flying Item Details Controlling authority and NOTAM Fleet HQ Potts Point (NAVY - primary user) responsibility FHQ is responsible for NOTAM and airspace buffer calculations Activation NOTAM R521 Lucas Heights ANSTO Research Reactor Item Details Controlling authority and NOTAM responsibility ANSTO (primary user) Activation H R522 Marrangaroo - Military non-flying Item Details Controlling authority and NOTAM responsibility Army RCO Holsworthy (ARMY - primary user) Activation NOTAM R524 Culgoora - Radio Telescope Item Details Controlling authority and NOTAM responsibility CSIRO Narrabri (primary user) Activation H24 2-7

14 Airspace management and release responsibilities R525 Parkes - Radio Telescope Item Details Controlling authority and NOTAM responsibility CSIRO Parkes (primary user) Activation H Operational context R533 Denman - Military non-flying Item Details Controlling authority and NOTAM Thales Duty Officer (primary user) responsibility Activation H24 R536 A/B/C Orchard Hills - Military non-flying Item Details Controlling authority and NOTAM OIC EODF Orchard Hills (RAAF - primary user) responsibility Activation R536A - HJ or as amended by NOTAM R536B JO (one hour earlier HDS) or as amended by NOTAM R536C - NOTAM R555A/B/C/D/F Holsworthy - Military flying/non-flying R555A Holsworthy Item Details Controlling authority and NOTAM responsibility Army RCO Holsworthy (ARMY - primary user) Activation H R555B Holsworthy - Military flying/non-flying Item Details Controlling authority and NOTAM responsibility Army RCO Holsworthy (ARMY - primary user for aviation activity below 2000 FT ARMY - primary user for non-aviation activity below 2500 FT) (Airservices - airspace coordinator 3000 FT and above) Activation NOTAM Only activate in exceptional circumstances and with prior agreement at the planning stage

15 Operational context Airspace management and release responsibilities R555C Holsworthy - Military flying/non-flying Item Details Controlling authority and NOTAM responsibility Army RCO Holsworthy (ARMY - primary user) Activation D EXPH (one hour earlier HDS) or as amended by NOTAM R555D Holsworthy - Military flying/non-flying Item Details Controlling authority and NOTAM responsibility Army RCO Holsworthy (Airservices - airspace coordinator) Activation NOTAM The RCO: must fax requests to activate R555D to the NOF, and include the word DEMOLITIONS when DEMS2 will be used; and should provide at least one working days notice Note: Activity heights above 3000 FT impact SY ATC operations R555F Holsworthy - Military flying Item Details Controlling authority and NOTAM responsibility 6 AVN Regiment OPSO (ARMY - primary user) Activation JO (one hour earlier HDS) or as amended by NOTAM R559A/B/C/D/E/F Williamtown Military flying Item Details Controlling authority and NOTAM responsibility FLTCDR 453SQN WLM FLT (RAAF - primary user) Activation NOTAM Provide at least two hours notice when activating R559A/B/C/D/E R559B/C/D must only be activated with R559A R559F must only be activated with R559A 2-9

16 Airspace management and release responsibilities Operational context R564 A/B Singleton - Military flying/non-flying Item Details Controlling authority and NOTAM responsibility Army RCO Singleton (R564A ARMY - primary user) (R564B ARMY - airspace coordinator) ATC services are not provided within R564B during military flying activities Activation NOTAM R564A D (one hour earlier HDS) or as amended by NOTAM R564B NOTAM The NOTAM must include details of firing/flying activities in R564B Do not exceed an activity height of FL130 unless mutually agreed by the RCO and BN Aisle 3 Shift Manager or ORM Activation above FL130 When the upper limit is above FL130, activity periods: 1) should not exceed two hours; and 2) must be separated by at least 60 minutes Between 0900 and 1600 local one four hour period is allowed One-off approvals for a higher limit may be negotiated between the RCO or delegate and BN ATC Adjacent PJE operations Brisbane ATC may assign a PJE pilot operating at YCNK/ YEES/YSGT responsibility for not entering R564B R574 Williamtown - Military flying Item Details Controlling authority and NOTAM responsibility FLTCDR 453SQN WLM FLT (RAAF - primary user) Activation NOTAM R578 A/B/C/D/E Williamtown - Military flying Item Details Controlling authority and NOTAM responsibility FLTCDR 453SQN WLM FLT (RAAF - primary user) Activation NOTAM NOTAM to change activity HRS may be requested within two hours notification

17 Operational context Airspace management and release responsibilities R580 Williamtown - Military flying Item Details Controlling authority and NOTAM FLTCDR 453SQN WLM FLT (RAAF - primary user) responsibility Activation NOTAM NOTAM to change activity HRS may be requested within two hours notification R583 A/B Williamtown - Military flying Item Details Controlling authority and NOTAM responsibility FLTCDR 453SQN WLM FLT (RAAF - primary user) Activation NOTAM NOTAM to change activity hours may be requested within two hours notification Item R587 A/B Williamtown - Military flying Details Controlling authority and NOTAM FLTCDR 453SQN WLM FLT (RAAF - primary user) responsibility Activation NOTAM NOTAM to change activity hours may be requested within two hours notification Item R596 Williamtown - Military flying/non-flying Details Controlling authority and NOTAM FLTCDR 453SQN WLM FLT (RAAF - primary user) responsibility Activation NOTAM NOTAM to change activity hours may be requested within two hours notification 2-11

18 Transit corridors 2411 Operational context 24 Transit corridors 241 Purpose of and access to Hunter and Nowra Corridors 2411 Military airspace When activated, these corridors effectively become military airspace as described in this MATS Supp Traffic to or from these corridors does not enter BN ENR airspace When referring to the corridors, ensure that the specific name is used 2412 Emergencies and weather deviations Ad hoc requests for transit of the corridors to facilitate traffic management, weather deviations or emergency diversions should be accommodated where possible 2413 Aircraft communications Military aircraft will remain on WLM ATC frequencies when operating within the corridors 242 Corridor dimensions 2421 Hunter Corridor Dimensions Name Dimensions Hunter Corridor - 5 NM either side of the WLM 265 TACAN radial to/from R '48"S '54"E, '45"E, 32 41'43"S 32 47'22"S '30"E, '32"E, 32 45'48"S Note: Vertical limits 32 35'32"S '39"E, 32 51'29"S '54"E FL150 and/or FL160 Other levels or combinations of levels may be negotiated as required for the traffic situation Variations should only be sought and used when operationally necessary Access to the Hunter Corridor for transit to and from R559A is an essential requirement for operations by the Air Combat Group (ACG) Delays to mission-prepared aircraft departing WLM or returning from R559A will involve a significant operational penalty and could have flight safety implications Purpose of the Hunter Corridor The Hunter Corridor should only be requested when the transit of multiple aircraft is required Note: This corridor restricts civil aircraft operations, and use should be limited

19 Operational context Transit corridors Diagram Hunter Corridor 2423 Nowra (NWA) Corridor Dimensions Name Dimensions Vertical limits NWA Corridor - The nominal track is the WLM 150 TACAN radial to 70 TAC (WPT DULCI S E ) and then a track of 181 degrees to enter R495 (at WPT WILKY S E ) 52 degrees from the TACAN until WLM where it intersects a 7 NM tolerance placed either side of the 181 degree track into the Nowra Restricted Areas The dimensions of the NWA Corridor are: 33 54'14"S '52"E, 32 47'49"S '00"E, 33 54'46"S '03"E, 34 43'39"S '17"E, 34 32'44"S '07"E, 33 54'14"S '52"E FL290 - FL350 Do not request the NWA Corridor when R489 is active above FL Aircraft operations Aircraft will normally squawk altitude and travel in trail or close formation at: FL310 with a requirement to reach FL310 before departing R574, southbound from WLM; and FL330 northbound to WLM 2-13

20 Transit corridors Operational context Diagram Nowra corridor

21 Operational context Civil Jet Corridor (CJC) Civil Jet Corridor (CJC) 251 Description The CJC is a permanent airspace release to BN ATC through WLM Restricted Areas and is generally used for traffic tracking on or west of the ENTRA-BANDA track The lateral dimensions are that portion of R587A west of a line 25 NM east of the track ENTRA - BANDA The vertical dimensions are stepped vertical lower limits within R587A The corridor is described in three sections: 2511 Dimensions Name Dimensions Vertical limits CIV JET 01A/1 NPP (A) S E, S E thence FL175 - FL600 along the minor arc of a circle of 625 NM radius centred on S E (original site of SY VOR/DME) to S E S E, thence along the minor arc of a circle of 250 NM radius centred on WLM/TAC to S E CIV JET 01B NPP (B) S E, S E thence FL215 - FL600 along the minor arc of a circle of 925 NM radius centred on S E (original site of SY VOR/DME) to S E S E, thence along the minor arc of a circle of 625 NM radius centred on S E (original site of SY VOR/DME) to S E S E, S E S E CIV JET 01C/1 NPP (C) S E, S E FL265 - FL600 23S E, thence along the minor arc of a circle of 925 NM radius centred on S E (original site of SY VOR/DME) to S E S E, thence along the minor arc of a circle of 250 NM radius centred on WLM/TAC to S E S E Emergencies and weather deviations Ad hoc requests for transit of the CJC to facilitate traffic management, weather deviations or emergency diversions should be accommodated where possible 2513 Arbiter BN ATC is the Arbiter for the CJC 2-15

22 Flight planning in corridors 2514 Operational context 2514 Civil Jet Corridor diagram 26 Flight planning in corridors 261 Military aircraft Aircraft operating solely within WLM Restricted Areas, the NWA, Hunter and CJCs are not required to submit flight plans to BN ATC Note: 262 Unless in an emergency situation, military aircraft will operate their transponder on the normal codes assigned by their control agency Civil aircraft Civil jet aircraft flight plans that transit the CJC are not required by WLM ATC 27 Airspace releases 271 Temporary releases A NOTAM is not required when temporary releases of restricted airspace are arranged

23 Operational context 272 Airspace releases 2514 Standard Oceanic Releases of R574 Oceanic Releases Release name DONIC - MISLY Release Dimensions A release of the WLM areas E, J, K, N and P and a partial release of areas B, C, D, H, L and M Lateral Limits: 33 32'50"S '52"E, 33 21'06"S '15"E 31 16'29"S '27"E, 32 33'37"S '57"E 33 51'30"S '56"E, 33 51'30"S '57"E 33 32'50"S '52"E Vertical Limits: FT DIPSO - GORDO Release Dimensions A release of the WLM areas E, J, K, N and P Lateral Limits: 33 22'03"S '52"E, 32 52'11"S '26"E 32 35'11"S '45"E, thence along the minor arc of a circle of 25 NM radius centred on 32 32'43"S '11"E to 32 33'37"S '57"E, 33 51'30"S '56"E, 33 51'30"S, '57"E, 33 35'18"S '04"E, 33 23'36"S '59"E thence along the minor arc of a circle of 25 NM radius centred on 33 21'13"S '04"E to 33 22'03"S '52"E Vertical Limits: FT ALLOC GORDO Release Dimensions A release of the WLM areas K, N and P Lateral Limits: 33 49'08"S '15"E, 33 23'32"S '54"E, 33 20'12"S '35"E, thence along the minor arc of a circle of 25 NM radius centred on 33 17'42"S '19"E to 33 18'34"S '08"E, 32 44'09"S '56"E, 32 35'11"S '45"E thence along the minor arc of a circle of 25 NM radius centred on 32 32'43"S '11"E to 32 33'37"S '57"E, 33 51'30"S '56"E, 33 51'30"S '15"E, thence along the minor arc of a circle of 25 NM radius centred on 33 49'00"S '15"E to 33 49'08"S '15"E Vertical Limits: FT 'Echo' Release Dimensions A release of the WLM area E Lateral Limits: S E, S E, S E, S E, S E, then along the minor arc of a circle of 25 NM radius centred on S E to S E, S E Only offered in conjunction with the ALLOC GORDO release Vertical Limits: FT 2-17

24 Airspace releases 2721 Operational context Oceanic Releases Release name VARLY-GORDO Release Dimensions A release of the WLM areas N and P Lateral Limits: 33 49'52"S '29"E, 32 44'09"S '56"E, 32 35'11"S '45"E, thence along the minor arc of a circle of 25 NM radius centred on 32 32'43"S '11"E to 32 33'37"S '57"E, 33 51'30"S '56"E, 33 51'30"S '40"E, thence along the minor arc of a circle of 25 NM radius centred on, 33 49'00"S '40"E to 33 49'52"S '29"E Vertical Limits: FT DIPSO-KEBAB Release Dimensions A release of the WLM areas E, K and P Lateral Limits: 33 35'18"S '04"E, 33 23'41"S '39"E, 33 16'28"S '16"E, thence along the minor arc of a circle of 25 NM radius centred on 33 13'58"S '59"E to 33 15'05"S '39"E, 33 51'30"S '56"E, 33 51'30"S, 52 07'57"E, 33 35'18"S '04"E Vertical Limits: FT ALLOC-KEBAB Release Dimensions A release of the WLM areas K and P Lateral Limits: 33 49'08"S '15"E, 33 23'32"S '54"E 33 16'28"S '16"E, thence along the minor arc of a circle of 25 NM radius centred on 33 13'58"S '59"E to 33 15'05"S '39"E, 33 51'30"S '56"E, 33 51'30"S, 52 40'15"E thence along the minor arc of a circle of 25 NM radius centred on 33 49'00"S '15"E to 33 49'08"S '15"E Vertical Limits: FT VARLY - KEBAB Release Dimensions A release of the WLM area P Lateral Limits: 33 49'52"S '29"E, 33 20'04"S '29"E, 33 16'28"S '16"E, thence along the minor arc of a circle of 25 NM radius centred on 33 13'58"S '59"E to 33 15'05"S '39"E, 33 51'30"S '56"E, 33 51'30"S, 33 18'40"E thence along the minor arc of a circle of 25 NM radius centred on 33 49'00"S '40"E to 33 49'52"S '29"E Vertical Limits: FT 2721 Separation buffers BN ATC must apply the following buffers to the lateral limits of Oceanic releases listed in 272 Standard Oceanic Releases of R574: A 25 NM buffer to all except the DONIC - MISLY release; and A 5NM buffer to the DONIC-MISLY release Note: This will assure 5 NM separation with WLM operations

25 Operational context 273 Airspace releases 2721 Diagrams of Oceanic Releases 2-19

26 Airspace releases Operational context

27 Operational context Naval East Australian Exercise Area (EAXA) procedures Naval East Australian Exercise Area (EAXA) procedures 281 EAXA airspace and uses 2811 Restricted Areas The EAXA airspace consists of Restricted Areas: R452, used for Naval shore bombardment; and R453, R485, R489, and R495, used for firing, bombing and non-firing air activities including: i) military flying training; ii) radar tracking exercises involving single aircraft at low to medium altitudes; iii) air defence involving multiple aircraft conducting low-altitude attacks against surface targets; and iv) intercept exercises involving multiple aircraft conducting high-altitude intercepts Disruptions to military activities may not be easily accommodated and should be limited to legitimate requests Note: 2812 These exercises require months of planning involving numerous units They rely on high-cost limited availability aircraft and may be time critical 'enablers' for subsequent ADF deployments to war-like environments Clearance for exercise aircraft not required Aircraft operating within the EAXA airspace on a Fleet Task (as designated by Fleet Headquarters) do not require an airways clearance to enter EAXA airspace 2813 Operations in NW82 adjacent to R453 When R453 is active, ATC may assign responsibility to remain clear of R453 to military aircraft operating in NW82 ATC will use the phraseology, 'CLEARED TO OPERATE IN NW82, REMAIN CLEAR OF R453' 2814 Operations in CTA adjacent to R485 and R489 Consult with Sydney TCU and BN ATC when planning military operations in controlled airspace adjacent to R485 and R489 The conditions for operations must be agreed to and published 2815 R485 useable levels Restricted Areas Civil Lowest Usable Levels (LUL) Military Highest Usable Level (HUL) R485A 2000 FT 1000 FT R485B 8000 FT 7000 FT R485C 9000 FT 8000 FT R485D FL130 FL120 R485E FL210 FL

28 Naval East Australian Exercise Area (EAXA) procedures 2821 Operational context 282 Communications 2821 Normal communications procedure - transit/release requests The ML SS and Sydney TCU Manager must direct coordination for transit/release to: the FXP Cell between local Mon-Fri (excluding PH); or SO3 MARWKPR at other times Pass requests for transit/release of R452, R453, R485 C-E and R495 through the ML SS Pass requests for transit/release of R485 A/B and R489 through the Sydney TCU Manager Pass emergency transit requests to the ML SS as soon as possible Note 1: Direct communications between ATS providers and OCS regarding EAXA airspace are not available Exceptions for R485 A/B and R489 Note 2: FXP and SO3 MARWKPR will relay requests using military communications 2822 Sydney TCU communications with warships Pass requests for transit/release of R489 through the Sydney TCU Manager to the warship When communicating with a warship about transit or airspace releases, ask to speak to the on-watch PWO or the ORS Note 1: The net may be staffed by a junior operator Note 2: Communications may be by phone 283 Airspace release requests and resumption 2831 Reasons for requesting an airspace release Request an airspace release when: 2832 aircraft are subject to an in-flight emergency; or weather deviations are expected Weather deviations - prior notice Advise the FXP Cell or SO3 MARWKPR of likely weather deviations on receipt of forecasts/reports from the Bureau of Meteorology or other sources Where possible, provide at least 30 minutes notice when requesting an airspace release due weather 2833 ATS provider responsibility When requesting an airspace release: c) specify the Restricted Area(s) subdivisions, levels and release period required; do not request the release of an area in its entirety (R452 excepted); and ensure that transits are conducted in the most expeditious manner to minimise the disruption to Defence activities

29 Operational context Naval East Australian Exercise Area (EAXA) procedures 2834 Advise your supervisor when: the transit aircraft has/have vacated and the released airspace is no longer required; and Note: Airspace will be returned to the military and activities may resume aircraft will transit using the emergency transit procedures 2834 FXP cell/so3 MARWKPR responsibility The FXP Cell/SO3 MARWKPR will coordinate with the OCS(s) If a release: is approved, advise the ATS Provider using the phrase: 'PROPOSAL APPROVED FOR ROMEO (specify Restricted Area subdivisions, levels, times, as applicable) REPORT COMPLETE' Note: Note: 284 This indicates that a check-fire is in place and aircraft have been positioned clear of the released airspace; or cannot be approved, advise the ATS provider that 'PROPOSAL DENIED' OCS may be unable to de-conflict the military activity from the requested release Reason for transit of EAXA areas Nothing in these procedures precludes: the pilot-in-command of an aircraft declaring a PAN/MAYDAY when subject to an emergency and transiting active military restricted airspace; or the Air Traffic Services (ATS) provider from requesting a temporary release/ transit of a portion of the EAXA airspace for a legitimate reason Be aware that release/transit will depend on current and pending ADF activities and limitations in military communications capabilities within the EAXA, and requests may not be approved 285 Emergency transit procedures 2851 ATS provider transmissions when transiting EAXA airspace Make the following transmission when emergency transit of the EAXA airspace is required: '(Callsign) ROMEO [452/453/485/495] IS ACTIVE FOR WARSHIP (as advised by FXP Cell or SO3 MARWKPR) HAZARDOUS ACTIVITIES ARE OCCURRING, UNABLE TO ISSUE CLEARANCE PROCEED AT YOUR OWN RISK' Make the following transmission if the pilot-in-command chooses to proceed into the Restricted Area: 'YOU ARE PROCEEDING AT YOUR OWN RISK, SQUAWK 7700 AND BROADCAST ON 1215 (and 2430 if fitted) YOUR CALLSIGN, POSITION, LEVEL AND TRACKING, AND REPORT THAT YOU ARE CONDUCTING AN EMERGENCY TRANSIT OF ROMEO [452/453/485/489/495]' 2-23

30 Naval East Australian Exercise Area (EAXA) procedures Operational context Repeat transmission Instruct the emergency aircraft to: repeat the transmission at regular intervals until direct contact is established with the applicable warship(s); and report when clear of the restricted airspace If the aircraft is unable to broadcast, request another aircraft in the vicinity of the transited airspace to make the broadcast on behalf of the emergency aircraft 2853 Dangers of transiting Ensure that the pilot-in-command is in no doubt of the dangers of transiting active military Restricted Areas without military authority Note: 2854 Many warships have neither the ability to interrogate transponders nor to monitor 1215 MHz Most military aircraft do not have TCAS or air-to-air radar Submit an occurrence report Submit an occurrence report for all emergency deviations into Restricted Areas 286 Transit requests 2861 Transit of R453 A/B Make requests to transit R453A/B through FXP or SO3 MARWKPR irrespective of the status and configuration of R421 A/B and R420 F NWA ATC may be able to assist when aircraft are subject to an emergency Note 1: These areas are allocated to an OCS and there may be delays in communications and in gaining the transit approval Note 2: Generally, R453 A/B will only be NOTAMed simultaneously with R420F and R421 when an increase in safety and protection between other airspace users and the activity conducted is considered necessary 2862 Transit of R485 A/B When transit of R485 A/B is required by civil aircraft, Sydney TCU Manager may request a release of the airspace Make requests by phone when communications are established between Sydney TCU Manager and the OCS When contact between the ship and Sydney TCU cannot be established, Sydney TCU must contact the FXP Cell or SO3 MARWKPR When R485A/B has been allocated for air serials the FXP, warships and aircraft must maintain a listening watch on 1351 MHz, and aircraft in R485 may operate on this frequency

31 Operational context 2863 Naval East Australian Exercise Area (EAXA) procedures 2863 Transit of R485 C, D and E Sydney TCU must contact the FXP Cell or SO3 MARWKPR for requests to transit R485C, D and E 287 Release/transits not approved FHQ must accommodate releases or transits whenever military activities permit When a release/transit cannot be approved, apply alternate measures to ensure traffic remains clear of the active restricted airspace Such measures may include deviations around or over active restricted airspace, or remaining at or returning to the departure aerodrome 288 R489 procedures 2881 Communications and reporting Time The OCS must: At least 30 minutes prior to scheduled time for firing or air serial Establish communications with Sydney TCU via: 1) 1351 MHz; 2) 3) Sydney TCU traffic manager phone; or cooperating aircraft on 1351 MHz, when practical At least five minutes prior Confirm communications prior to commencing firing During firing Maintain a continuous communications watch; and 30 minute scheduled reports The firing or air serial must cease if communications cannot be established or are lost Note: 2882 Reliable communications between the OCS and Sydney TCU are essential whenever air or firing serials are conducted within R489, due to its proximity to Sydney (Kingsford-Smith) Airport Release during delays If a significant delay occurs, the OCS should release R489 to Sydney TCU When released, Sydney TCU must release the portion of R489 within R574 to WLM APR via the BN ATC sector 2883 Resuming after delays The OCS must provide Sydney TCU at least 10 minutes notice when resuming R489 Sydney TCU must advise WLM APR via BN ATC Ocean Sector that the part of R489 within R574 is resumed by OCS 2884 Exercise cancelled/complete OCS must advise Sydney TCU when the exercise is completed or cancelled 2-25

32 R555 Holsworthy procedures 2931 Operational context 29 R555 Holsworthy procedures 291 R555A/B/C/D/F useable levels Restricted Areas Civil LUL Military HUL-flying Military HUL-non-flying R555A 2500 FT 2000 FT AMSL 2500 FT (includes all buffers) R555B/D NOTAM upper limit 1000 FT BLW NOTAM upper NOTAM upper limit (includes limit all buffers) R555C 3000 FT AMSL 2000 FT AMSL 3000 FT AMSL (includes all buffers) R555F 2000 FT 1500 FT AMSL N/A 292 Varying R555 activation times and activity heights If a variation to activation times or activity heights is required, HRC must: obtain approval from the SYTM before commencing firing; and cease firing in R555B and D as soon as practical when requested by the SYTM Advise SYTM when firing has ceased for the day or when activities in portions of R555 has ceased before the NOTAM advice, to allow civil aircraft use of the area 293 R555D firing procedures 2931 NOTAM NOTAM for all field demolitions or live firing will contain the following NOF approved text in Field E: 'R555D ACT [RA2] DUE MIL NON-FLYING' This is to be applied to both 'Limited' and 'Extended' access NOTAM Note that currently Defence will only permit one activity per NOTAM 2932 Coordination between SYTM and RCO When Defence requires access to the whole of R555D, the following coordination will apply: Limited Access Defence accepts, and Airservices may apply, the following conditions with such NOTAM: i) The Defence access requirements are intermittent for the period of the NOTAM with access window duration commensurate with that of DEMS2 activities and will not exceed one 15 min maximum access per hour except in the case of a misfire where the RCO will advise SY ATC of the expected delay; ii) In much the same way as for R555D [DEMOLITIONS] activities, RCO will: obtain approval from SY ATC for each field demolitions or live firing serial; advise SY ATC immediately on completion of each serial; and advise SY ATC when the activity has ceased for the day;

33 Operational context R555 Holsworthy procedures 2941 iii) c) 294 Defence expects reasonable access however accepts that, as airspace arbiter, SY ATC may not be able to accommodate all Defence access requests immediately and that there may be extended delays occasionally Should delays arise, SY ATC should advise the RCO of the estimated time delay so as to enable briefing to the unit conducting the firing/demolitions activity; Extended Access RCO will provide advice to the SYTM NLT five days prior to the NOTAM start date/time that the NOTAM access will be extended/ continuous; and Cease Firing The procedures for a SY ATC initiated cessation of firing/ demolition will be conducted in accordance with 2982 Arbiter R555F activation and release procedures R555F is a designated military flying training area th Aviation Regiment responsibilities 6th Aviation Regiment (6AVN REGT) provides services when there is flying in R555F, and may release the airspace to SYTM when: c) the standard activation period is not required; operations are delayed by more than one hour from 0800 local; and operations are completed before 2359 local R555F may be activated or deactivated outside the standard activity periods if agreed to by SY ATC 2-27

34 R555 Holsworthy procedures Flying activities in R Service provided Operational context Provide Class G airspace services in R555 Flying Operations are VFR unless an IFR service was previously provided by SY ATC 2952 Military restricted-flying zone A military restricted-flying zone is established in R555, ½ NM south of the Bankstown CTR as the area north of the green and white broken line in 29 R555 Holsworthy procedures This restricted flying zone is to segregate military medium and heavy wake turbulence category helicopters from the Bankstown CTR 2953 Pilot Responsibilities When active, aircraft do not require contact with SY ATC When operating within the military restricted-flying zone, the PIC must contact Bankstown Tower and advise when entering and departing the military restricted-flying zone If requesting a clearance to enter Civil CTA/Sydney CTR from R555, you must provide your own separation with all flying and non-flying activity within R Access for Emergency Services aircraft 2961 Access to R555 When Emergency Services aircraft require access to R555, SY ATC must: c) d) contact HRC for access to R555 A/B/C/D via intercom If contact cannot be made, call the: i) RCO; ii) ARCO; and iii) RM contact 6AVN REGT for access to R555F; instruct the aircraft to broadcast on the Holsworthy CTAF on entry and exit; and monitor the CTAF when within If contact cannot be made, advise the PIC that the status of R555 is unknown, and the aircraft must broadcast intentions on the Holsworthy CTAF 2962 Close proximity If operating in close proximity to R555, emergency services aircraft must be instructed to monitor the Holsworthy CTAF, particularly if landing on or immediately east of Heathcote Road

35 Operational context 2963 R555 Holsworthy procedures 2963 R555C Heathcote Lucas Area When R555F is active and civil emergency services aircraft require access to the Heathcote Lucas Area, SY ATC must coordinate with 6 AVN REGT When R555F is released or deactivated, the Heathcote Lucas Area is automatically released to SY ATC, SFC to 2500 FT AMSL Heathcote Lucas Area dimensions The Heathcote Lucas Area is the area in R555C bounded by the intersection of Heathcote Rd and the eastern boundary of R555C south along the eastern boundary R555C to R521 then north, remaining east of Heathcote Road, to the intersection of Heathcote Road and R555C This area is not used by Defence for ground training or firing and may be used for flying operations 297 Approved ground activity Only allow blank ammunition and static illumination within R555F Note: Projected pyrotechnics, battle noise simulation or devices including illumination and lasers may be a hazard to low flying aircraft 2-29

36 R555 Holsworthy procedures Demolition activity within R DEMS2 Operational context Use the DEMS2 area when demolition activities require a planned height exceeding 2000 FT The DEMS2 area is centred at S 34o 04' 4190" E 150o 54' 3691" See diagram below:

37 Operational context 2982 R555 Holsworthy procedures 2982 Arbiter SY ATC is the Arbiter for activities within R555 above 2000 FT including demolition activities 2983 Buffers When R555D is active for demolition, SY ATS may use other portions of R555D, and must avoid the displayed DEMS2 area by an additional 1 NM buffer Note 1: The promulgated lateral dimensions do not contain aviation buffers The horizontal area includes allowance for the extreme detonation positions and has been determined as 1100 m from the centre location Note 2: This area is depicted within Eurocat maps as a circle with a 06 NM radius, based on the lat/long The maximum activity height is 1500 m above the impact area 2984 Usable levels When conducting Demolition activities, the LUL by SY ATC is the upper level specified in the NOTAM but must not exceed 6000 FT 2985 Hours of operation The DEMS2 area must only be used when both R555C and D are active 2986 Firing and demolition in R555D When firing and demolition will take place, apply the procedures associated with the activation for R555D Firing 299 Coordination between Sydney TCU and RCO 2991 RCO responsibilities The RCO must: c) d) 2992 establish communications with SYTM; obtain approval for demolition before commencing; obtain individual serial clearances for demolition if required by SYTM; and advise SY ATC when demolitions have ceased for the day Cease firing SY ATC must contact the RCO when a cessation of firing is required Note: Due to the lead times involved in laying charges, the ability to stop a particular demolition is limited The RCO must advise SY ATC: c) the expected delay before firing can cease; when demolitions are rendered safe; and release R555D to SY ATC Once air traffic is separated from the firing area, SY ATC must return R555D to the RCO and approve the resumption of demolition activities 2-31

38 R555 Holsworthy procedures 2992 Operational context This page is intentionally blank

39 Normal operations Williamtown 3 Normal operations Williamtown 31 Ancillary information 311 Communications WLM to Aisle 3 SM Ancillary information Use the telephone when communicating between WLM and the BN SM 3 Only use the SELCAL when the telephone line is not available WLM must advise the SM of daily airspace activation promulgated by NOTAM 312 Hazard alerts WLM supervisor must advise the SM/SS of any hazard alerts and, where able, provide a list of aircraft affected by the hazard alert The SM/SS must: 313 ensure affected aircraft are advised; and advise the WLM supervisor if other aircraft require the hazard alert Diversion airfields WLM ATC must coordinate with the affected sectors when diversion from YWLM is necessary When military aircraft require diversions from YWLM, the following airfields are available for use: 314 1) Richmond; 2) 3) Coffs Harbour, Nowra and Tamworth; and in an emergency, Sydney and Dubbo Division of responsibility WLM ATC is divided into: WLM APP (L), providing services at 5000 FT and below, within 25 NM of WLM; and WLM APP (H), providing services above 5000 FT within 25 NM WLM and all other WLM areas 3-1

40 Restricted Areas activation and deactivation Normal operations Williamtown 32 Restricted Areas activation and deactivation 321 Airspace groupings WLM airspaces are grouped as follows: Airspace Areas 1 WLM CTR 2 WLM CTR, R578A to E 3 Airspace 2 plus R587A active R587A within 25 NM WLM at FL180 and above released to BN ATC R587A outside 25 NM WLM all levels released to BN ATC 4 Airspace 2 plus R580 and R583A 5 Airspace 4 plus R587A, and R574 The CJC is released to Airservices R574 Usable levels in WLM airspace The RAAF may use the following levels: Restricted Areas FL120 R578 B FL120 R578 C 5000 FT FL120 R578 D 3000 FT FL120 R578 E 9000 FT CTR 4000 FT 5000 FT FL120 R583 A FL120 R583 B 9000 FT R587 A/B 22 HUL R578 A R LUL FL130 FL580

41 Normal operations Williamtown 323 Restricted Areas activation and deactivation Activation procedures - WLM airspaces 1-5 At least 30 minutes prior to activation Required action WLM ATC 1) Check and ensure the applicable NOTAM are accurate; 2) 3) Confirm this with the Shift Manager; and For WLM 5, coordinate the WLM 5 Oceanic Release On receipt of activation advice Required action BN SM 3 1) Advise the Sydney Traffic Manager of any changes to the NOTAM; and 2) Advise BN ENR sectors, as appropriate Ocean Sector Check with HWE for traffic MLD Advise SDN if direct tracking is not available At least five minutes prior to activation Required action WLM ATC Contact MLD, NAA, MAL and OCN Sectors for traffic information BN ENR sectors Provide radar ident, after the traffic information call From activation of WLM 3 and 5 Required action Sydney TCU Issue level requirements to CJC traffic that will operate in R587A from advised activation time 324 Activation procedures - R583B, R587B, R559 A-F At least 30 minutes prior to activation Required action WLM ATC 1) Check and ensure the applicable NOTAM are accurate; and 2) Confirm this with the SM On receipt of activation advice Required action BN SM 3 1) Advise the Sydney Traffic Manager of any changes to the NOTAM; and 2) Advise BN ENR sectors, as appropriate At least five minutes prior to activation BN ENR sectors where applicable Required action Provide traffic information and/or radar ident via the WLM CEN hotline 3-3