Merge pull request #346 from vatpac-technology/alex-dev

2410 TRT Changes

docs/aerodromes/classc/Curtin.md

@@ -34,10 +34,9 @@ CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`.
 
 The Standard Assignable Level from  **CIN ADC** to **CIN TCU** is the Lower of `F190` or the `RFL`.
 
-### TRT(KIY)
-When CIN TCU is offline, coordination is not required between CIN ADC and TRT(KIY). Aircraft entering TRT(KIY) airspace shall be handed off, and instructed to contact TRT(KIY) for onwards clearance.
+### TRT(ASH)
+When CIN TCU is offline, coordination is not required between CIN ADC and TRT(ASH). Aircraft entering TRT(ASH) airspace shall be handed off, and instructed to contact TRT(ASH) for onwards clearance.
 
 ## Charts
 !!! note
-    Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new}
-
+    Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new}

docs/aerodromes/procedural/Broome.md

@@ -22,24 +22,24 @@ BRM ADC is responsible for the Class D airspace `SFC` to `A055`, as well as the
 Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.
 
 ## Surveillance
-Surveillance coverage can be expected to be available at all levels in the BRM CTR. Although BRM ADC is **not permitted** to use surveillance for separation, TRT(KIY) may assist by establishing surveillance separation standards via coordination
+Surveillance coverage can be expected to be available at all levels in the BRM CTR. Although BRM ADC is **not permitted** to use surveillance for separation, TRT(ASH) may assist by establishing surveillance separation standards via coordination
 
 ## Coordination
 ### Departures
-A 'next' call is made for all aircraft when they are next to depart. BRM ADC must inform TRT(KIY) if the aircraft does not depart within **2 minutes** of the next call.
+A 'next' call is made for all aircraft when they are next to depart. BRM ADC must inform TRT(ASH) if the aircraft does not depart within **2 minutes** of the next call.
 
 !!! example
-    <span class="hotline">**BRM ADC** -> **KIY**</span>: "Next, NWK1653"  
-    <span class="hotline">**KIY** -> **BRM ADC**</span>: "NWK1653, Unrestricted"  
-    <span class="hotline">**BRM ADC** -> **KIY**</span>: "NWK1653"
+    <span class="hotline">**BRM ADC** -> **ASH**</span>: "Next, NWK1653"  
+    <span class="hotline">**ASH** -> **BRM ADC**</span>: "NWK1653, Unrestricted"  
+    <span class="hotline">**BRM ADC** -> **ASH**</span>: "NWK1653"
 
-The Standard Assignable level from BRM ADC to TRT(KIY) is the lower of `A050` or the `RFL`, any other level must be prior coordinated.
+The Standard Assignable level from BRM ADC to TRT(ASH) is the lower of `A050` or the `RFL`, any other level must be prior coordinated.
 
 ### Arrivals/Overfliers
-TRT(KIY) will heads-up coordinate all arrivals/overfliers to BRM ADC
+TRT(ASH) will heads-up coordinate all arrivals/overfliers to BRM ADC
 
 !!! example
-    <span class="hotline">**KIY** -> **BRM ADC**</span>: "Via CIN, ANO332”  
-    <span class="hotline">**BRM ADC** -> **KIY**</span>: "ANO332"  
+    <span class="hotline">**ASH** -> **BRM ADC**</span>: "Via CIN, ANO332”  
+    <span class="hotline">**BRM ADC** -> **ASH**</span>: "ANO332"  
 
-The Standard Assignable level from TRT(KIY) to BRM ADC is `A060`, any other level must be prior coordinated.
+The Standard Assignable level from TRT(ASH) to BRM ADC is `A060`, any other level must be prior coordinated.

docs/enroute/Brisbane Centre/TRT.md

@@ -7,8 +7,10 @@
 ## Positions
 | Name | Callsign | Frequency | Login ID |
 | ---- | -------- | --------- | -------- |
-| **Territory** | **Brisbane Centre** | **133.200** | **BN-TRT_CTR** |
-| Kimberley† | Brisbane Centre | 133.400 | BN-KIY_CTR |
+| **Territory North** | **Brisbane Centre** | **123.850** | **BN-TRT_CTR** |
+| Territory South† | Brisbane Centre | 133.200 | BN-TRS_CTR |
+| Ashmore† | Brisbane Centre | 133.400 | BN-ASH_CTR |
+| Kimberley† | Brisbane Centre | 132.100 | BN-KIY_CTR |
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}
 
@@ -27,34 +29,34 @@ Voice may be used in lieu when applicable.
   <figcaption>Territory Airspace</figcaption>
 </figure>
 
-TRT is responsible for **KIY** when they are offline.  
+TRT is responsible for **TRS**, **ASH**, and **KIY**,  when they are offline.  
 
 ### Reclassifications
 #### BRM CTR
-When **BRM ADC** is offline, BRM CTR (Class D/E `SFC` to `A055`) reverts to Class G, and is administered by KIY. Alternatively, KIY may provide a [top-down procedural service](../../../aerodromes/Broome) if they wish.
+When **BRM ADC** is offline, BRM CTR (Class D/E `SFC` to `A055`) reverts to Class G, and is administered by ASH. Alternatively, ASH may provide a [top-down procedural service](../../../aerodromes/Broome) if they wish.
 
 !!! tip
     If choosing *not* to provide a top down service, consider publishing an **ATIS Zulu** for the aerodrome, to inform pilots about the airspace reclassification. The *More ATIS* plugin has a formatted Zulu ATIS message.
 
 ## Sector Responsibilities
-TRT is responsible for sequencing, issuing STAR Clearances, and issuing descent for aircraft bound for YPDN.  
-KIY is responsible for issuing descent and ascertaining arrival intentions for aircraft bound for YBRM.
-KIY is also responsible for sequencing and issuing descent to aircraft bound for YCIN.
+TRT and TRS are responsible for sequencing, issuing STAR Clearances, and issuing descent for aircraft bound for YPDN.  
+ASH is responsible for issuing descent and ascertaining arrival intentions for aircraft bound for YBRM.
+ASH is also responsible for sequencing and issuing descent to aircraft bound for YCIN.
 
 ## STAR Clearance Expectation
 ### Handoff
 Aircraft being transferred to the following sectors shall be told to Expect STAR Clearance on handoff:
 
 | Transferring Sector | Receiving Sector | ADES | Notes |
 | ---- | -------- | --------- | --------- |
-| STR, KIY | TRT | YPDN | |
+| ASH, KIY | TRT, TRS | YPDN | |
 
 ### First Contact
 Aircraft being transferred from the following sectors shall be given STAR Clearance on first contact:
 
 | Transferring Sector | Receiving Sector | ADES | Notes |
 | ---- | -------- | --------- | --------- |
-| STR, KIY, ISA(ARA) | TRT | YPDN | |
+| KIY, ASH, ISA(ARA/STR) | TRT, TRS | YPDN | |
 
 ## Coordination
 
@@ -96,14 +98,14 @@ All other aircraft going to TRT CTA will be **Heads-up** Coordinated by DN TCU.
 BRM ADC is responsible for the Class D airspace `SFC` to `A055`, as well as the Class E airspace `1200ft AGL` to `A055`, within the BRM CTR.
 
 #### Departures
-Departures from YBRM in to KIY CTA will be coordinated when ready for departure.  
+Departures from YBRM in to ASH CTA will be coordinated when ready for departure.  
 
 !!! example
-    <span class="hotline">**BRM ADC** -> **KIY**</span>: "Next, ANO333"  
-    <span class="hotline">**KIY** -> **BRM ADC**</span>: "ANO333, Unrestricted"  
-    <span class="hotline">**BRM ADC** -> **KIY**</span>: "ANO333"  
+    <span class="hotline">**BRM ADC** -> **ASH**</span>: "Next, ANO333"  
+    <span class="hotline">**ASH** -> **BRM ADC**</span>: "ANO333, Unrestricted"  
+    <span class="hotline">**BRM ADC** -> **ASH**</span>: "ANO333"  
 
-The Standard Assignable level from BRM ADC to TRT(KIY) is the lower of `A050` or the `RFL`, any other level must be prior coordinated.
+The Standard Assignable level from BRM ADC to TRT(ASH) is the lower of `A050` or the `RFL`, any other level must be prior coordinated.
 
 #### Arrivals
 YBRM arrivals shall be heads-up coordinated to **BRM ADC** from TRT prior to **5 mins** from the boundary.
@@ -112,22 +114,22 @@ YBRM arrivals shall be heads-up coordinated to **BRM ADC** from TRT prior to **5
     <span class="hotline">**TRT** -> **BRM ADC**</span>: "Via SAFIR, FD621”  
     <span class="hotline">**BRM ADC** -> **TRT**</span>: "FD621"  
 
-The Standard Assignable level from TRT(KIY) to BRM ADC is `A060`, any other level must be prior coordinated.
+The Standard Assignable level from TRT(ASH) to BRM ADC is `A060`, any other level must be prior coordinated.
 
 ### CIN TCU
 #### Airspace
 The limits of the CIN TCU are `SFC` to `F200` within 25 DME CIN. This may be amended by NOTAM.
 
 #### Arrivals/Overfliers
-The Standard assignable level from TRT(KIY) to CIN TCU is `F130`, tracking via CIN VOR.
+The Standard assignable level from TRT(ASH) to CIN TCU is `F130`, tracking via CIN VOR.
 
 All other aircraft must be voice coordinated to CIN TCU prior to **20nm** from the boundary.
 
 #### Departures
-The Standard Assignable level from CIN TCU to TRT(KIY) is `F190`, and tracking via their planned route.
+The Standard Assignable level from CIN TCU to TRT(ASH) is `F190`, and tracking via their planned route.
 
 #### CIN ADC
-When CIN TCU is offline, coordination is not required between TRT(KIY) and CIN ADC. Aircraft entering CIN ADC airspace shall be handed off, and instructed to contact CIN ADC for onwards clearance.
+When CIN TCU is offline, coordination is not required between TRT(ASH) and CIN ADC. Aircraft entering CIN ADC airspace shall be handed off, and instructed to contact CIN ADC for onwards clearance.
 
 CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`.
 

docs/terminal/curtin.md

@@ -36,21 +36,20 @@ CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`.
     <span class="hotline">**CIN TCU** -> **CIN ADC**</span>: "ASY404, unrestricted"  
     <span class="hotline">**CIN ADC** -> **CIN TCU**</span>: "ASY404"  
 
-### TRT(KIY)
+### TRT(ASH)
 #### Departures
-Voiceless coordination is in place from CIN TCU to KIY for aircraft:  
+Voiceless coordination is in place from CIN TCU to ASH for aircraft:  
 Planned at or above `F190`: `Assigned F190`  
 Planned below `F190`: `Assigned the RFL`  
 
 Any aircraft not meeting the above criteria must be prior coordinated to ENR.
 
 !!! example
-    <span class="hotline">**CIN TCU** -> **KIY**</span>: "ASY404, with your concurrence, will be assigned F180, for my separation with JTE654"  
-    <span class="hotline">**KIY** -> **CIN TCU**</span>: "ASY404, concur F160"  
+    <span class="hotline">**CIN TCU** -> **ASH**</span>: "ASY404, with your concurrence, will be assigned F180, for my separation with JTE654"  
+    <span class="hotline">**ASH** -> **CIN TCU**</span>: "ASY404, concur F160"  
 
 #### Arrivals
-The Standard assignable level from KIY to CIN TCU is `F130`, and tracking via CIN VOR. All other aircraft must be prior coordinated.
+The Standard assignable level from ASH to CIN TCU is `F130`, and tracking via CIN VOR. All other aircraft must be prior coordinated.
 
 !!! note
-    Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new}
-
+    Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new}

includes/abbreviations.md

@@ -108,6 +108,8 @@
 *[GOL]: Brisbane (Gold Coast) Centre
 *[KPL]: Brisbane (Keppel) Centre
 *[KIY]: Brisbane (Kimberley) Centre
+*[ASH]: Brisbane (Ashmore) Centre
+*[TRS]: Brisbane (Territory South) Centre
 *[MLD]: Brisbane (Maitland) Centre
 *[MNN]: Brisbane (Manning) Centre
 *[MDE]: Brisbane (Mudgee) Centre