2501(?) Sector Audit

docs/aerodromes/classd/Avalon.md

@@ -15,7 +15,7 @@ AV ADC is responsible for the Class D Airspace within the AV CTR `SFC` to `A025`
 ML TCU is responsible for the Class E Airspace to the North, South, and Above the AV CTR.  
 ML TCU is repsonsible for the Class G Airspace to the East of the AV CTR, and to the West of the AV CTR within 30 DME ML.  
 YWE is responsible for the Class G Airspace to the West of the AV CTR outside 30 DME ML.  
-YWE(WON) is responsible for the Class G Airspace to the South East of the AV CTR outside 30 DME ML.
+HUO(WON) is responsible for the Class G Airspace to the South East of the AV CTR outside 30 DME ML.
 
 <figure markdown>
 ![AV ADC Airspace](img/avctr.png){ width="500" }

docs/aerodromes/procedural/Albury.md

@@ -22,24 +22,24 @@ AY ADC is responsible for the Class D airspace in the AY CTR `SFC` to `A045`.
 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 AY CTR. Although AY ADC is **not permitted** to use surveillance for separation, ELW(BLA) may assist by establishing surveillance separation standards via coordination
+Surveillance coverage can be expected to be available at all levels in the AY CTR. Although AY ADC is **not permitted** to use surveillance for separation, BLA may assist by establishing surveillance separation standards via coordination
 
 ## Coordination
 ### Departures
-A 'Next' call is made for all aircraft entering ELW(BLA) CTA when they are next to depart. AY ADC must inform ELW(BLA) if the aircraft does not depart within **2 minutes** of the next call.
+A 'Next' call is made for all aircraft entering BLA CTA when they are next to depart. AY ADC must inform BLA if the aircraft does not depart within **2 minutes** of the next call.
 
 !!! example
     <span class="hotline">**AY ADC** -> **BLA**</span>: "Next, AM324"  
     <span class="hotline">**BLA** -> **AY ADC**</span>: "AM324, Unrestricted"  
     <span class="hotline">**AY ADC** -> **BLA**</span>: "AM324"
 
-The Standard Assignable level from AY TWR to ELW(BLA) is the lower of `A070` or the `RFL`, any other level must be prior coordinated.
+The Standard Assignable level from AY TWR to BLA is the lower of `A070` or the `RFL`, any other level must be prior coordinated.
 
 ### Arrivals/Overfliers
-ELW(BLA) will heads-up coordinate all arrivals/overfliers to AY ADC
+BLA will heads-up coordinate all arrivals/overfliers to AY ADC
 
 !!! example
     <span class="hotline">**BLA** -> **AY ADC**</span>: "Via ARRAN1 Arrival, RXA6783”  
     <span class="hotline">**AY ADC** -> **BLA**</span>: "RXA6783"  
 
-The Standard Assignable level from ELW(BLA) to AY ADC is `A080`, any other level must be prior coordinated.
+The Standard Assignable level from BLA to AY ADC is `A080`, any other level must be prior coordinated.

docs/aerodromes/procedural/Hammo.md

@@ -23,24 +23,24 @@ HM ADC is responsible for the Class D airspace in the HM CTR `SFC` to `A045`.
 Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.
 
 ## Surveillance
-Surveillance coverage can be expected to be not available below `A031` in the HM CTR. Although HM ADC is **not permitted** to use surveillance for separation, KEN(SWY) may assist by establishing surveillance separation standards via coordination
+Surveillance coverage can be expected to be not available below `A031` in the HM CTR. Although HM ADC is **not permitted** to use surveillance for separation, KPL(SWY) may assist by establishing surveillance separation standards via coordination
 
 ## Coordination
 ### Departures
-A 'next' call is made for all aircraft entering KEN(SWY) CTA when they are next to depart. HM ADC must inform KEN(SWY) if the aircraft does not depart within **2 minutes** of the next call.
+A 'next' call is made for all aircraft entering KPL(SWY) CTA when they are next to depart. HM ADC must inform KPL(SWY) if the aircraft does not depart within **2 minutes** of the next call.
 
 !!! example
     <span class="hotline">**HM ADC** -> **SWY**</span>: "Next, QFA797"  
     <span class="hotline">**SWY** -> **HM ADC**</span>: "QFA797, Unrestricted"  
     <span class="hotline">**HM ADC** -> **SWY**</span>: "QFA797"
 
-The Standard Assignable level from HM ADC to KEN(SWY) is the lower of `A050` or the `RFL`, any other level must be prior coordinated.
+The Standard Assignable level from HM ADC to KPL(SWY) is the lower of `A050` or the `RFL`, any other level must be prior coordinated.
 
 ### Arrivals/Overfliers
-KEN(SWY) will heads-up coordinate all arrivals/overfliers to HM ADC
+KPL(SWY) will heads-up coordinate all arrivals/overfliers to HM ADC
 
 !!! example
     <span class="hotline">**SWY** -> **HM ADC**</span>: "Via OPOSI for the RNP-U RWY 32, JST848”  
     <span class="hotline">**HM ADC** -> **SWY**</span>: "JST848"  
 
-The Standard Assignable level from KEN(SWY) to HM ADC is `A060`, any other level must be prior coordinated.
+The Standard Assignable level from KPL(SWY) to HM ADC is `A060`, any other level must be prior coordinated.

docs/client/cpdlc.md

@@ -59,7 +59,7 @@ Once connected with CPDLC enabled, pilots will connect to the vatACARS plugin vi
 Pilots must still read back their SID, squawk, and bay number on the frequency, even if they have acknowledged receipt of the PDC through vatACARS with the *'Roger'* response.
 
 !!! Note
-    If providing a top-down service as an enroute station, pilots requesting a PDC via CPDLC will be required to connect to your Enroute Station Code; E.g. YISA, YBIK, etc
+    If providing a top-down service as an enroute station, pilots requesting a PDC via CPDLC will be required to connect to your Enroute Station Code; E.g. YISA, YGUN, etc
 
 ## Enroute
 
@@ -96,13 +96,13 @@ Some major enroute positions do not use CPDLC as a primary means of communicatio
 | KEN | YKEN | Voice |
 | TRT | YTRT | **CPDLC** |
 | ASP | YASP | **CPDLC** |
-| BIK | YBIK | Voice |
-| ELW | YELW | Voice |
+| GUN | YGUN | Voice |
+| BLA | YBLA | Voice |
 | HUO | YHUO | Voice |
 | OLW | YOLW | **CPDLC** |
-| PIY | YPIY | Voice |
+| HYD | YHYD | Voice |
 | TBD | YTBD | Voice |
-| YWE | YYWE | Voice |
+| MUN | YMUN | Voice |
 | TSN | YTSN | **CPDLC** |
 | FLD | YFLD | **CPDLC** |
 | IND | YIND | **CPDLC** |

docs/controller-skills/airwork.md

@@ -67,7 +67,7 @@ If an aircraft is to be conducting airwork that does not require them to talk to
 !!! example
     Time is 0648Z  
     **OBF**: "OBF will be conducting Airwork within a 20nm radius of YBLT Not above A050 for the next 60 minutes"  
-    **YWE**: "OBF, No Reported IFR Traffic, Call Ops Normal time 30."  
+    **MUN**: "OBF, No Reported IFR Traffic, Call Ops Normal time 30."  
     **OBF**: "Ops Normal time 30, OBF"
 
 You can then set the timer on the aircraft, by right clicking on the ACID in the Label, and entering the agreed upon time.

docs/controller-skills/coordination.md

@@ -43,16 +43,16 @@ Controlling Sector -> Receiving Sector: "(Position), (Callsign)"
 Receiving Sector -> Controlling Sector: "(Callsign), (Level)"
 
 !!! example
-    <span class="hotline">**ELW** -> **BIK**</span>: "via CB, VOZ1234"  
-    <span class="hotline">**BIK** -> **ELW**</span>: "VOZ1234, F350"  
+    <span class="hotline">**BLA** -> **GUN**</span>: "via CB, VOZ1234"  
+    <span class="hotline">**GUN** -> **BLA**</span>: "VOZ1234, F350"  
 
 If the level that will be assigned at transfer of jurisdiction is different from the current CFL, the Controlling Sector will use the phrase "Will be assigned (level)".
 
 Once this coordination is completed, the aircraft's level and route is **locked in**. Any further changes must be recoordinated.
 
 !!! example
-    <span class="hotline">**ELW** -> **BIK**</span>: "VOZ1234, requesting DCT RIVET"  
-    <span class="hotline">**BIK** -> **ELW**</span>: "VOZ1234, concur DCT RIVET"  
+    <span class="hotline">**BLA** -> **GUN**</span>: "VOZ1234, requesting DCT RIVET"  
+    <span class="hotline">**GUN** -> **BLA**</span>: "VOZ1234, concur DCT RIVET"  
 
 !!! tip
     In situations where Heads-Up Coordination is required, the best time to do it is when the aircraft first calls you. There's no need to wait until half a mile before when its due, if you can get it done sooner.
@@ -73,8 +73,8 @@ Controlling Sector -> Boundary Sector: "For Ident, (Position), (Callsign), (Deta
 Boundary Sector -> Controlling Sector: "(Callsign), (Restriction)"
 
 !!! example
-    <span class="hotline">**BIK** -> **CBE**</span>: "For Ident, overhead CB, QFA12, do you have any restrictions on descent?"  
-    <span class="hotline">**CBE** -> **BIK**</span>: "QFA12, No restrictions on descent"  
+    <span class="hotline">**GUN** -> **CBE**</span>: "For Ident, overhead CB, QFA12, do you have any restrictions on descent?"  
+    <span class="hotline">**CBE** -> **GUN**</span>: "QFA12, No restrictions on descent"  
 
 The Boundary Sector may omit the restriction and readback the callsign only. This will be taken as the Boundary Sector having **no vertical or lateral restrictions**.
 
@@ -113,12 +113,12 @@ Source: [Annotations](../../controller-skills/annotations)
 *Offering NFR*
 !!! example
     *ABC tracking MNG W663 VINOP*  
-    <span class="hotline">**ELW** -> **YWE**</span>: "via MNG, ABC, if you have no restrictions or requirements, my onwards with OXL"  
-    <span class="hotline">**YWE** -> **ELW**</span>: "ABC, I have no restrictions or requirements, your onwards with OXL"  
-    ELW will put *"YWE NRR"* in the label data  
-    <span class="hotline">**ELW** -> **OXL**</span>: "via MNG, ABC, YWE has no restrictions or requirements"  
+    <span class="hotline">**BLA** -> **YWE**</span>: "via MNG, ABC, if you have no restrictions or requirements, my onwards with OXL"  
+    <span class="hotline">**YWE** -> **BLA**</span>: "ABC, I have no restrictions or requirements, your onwards with OXL"  
+    BLA will put *"YWE NRR"* in the label data  
+    <span class="hotline">**BLA** -> **OXL**</span>: "via MNG, ABC, YWE has no restrictions or requirements"  
     <span class="hotline">**OXL** -> **YWE**</span>: "ABC, F190"  
-    ELW will handoff the aircraft directly to OXL
+    BLA will handoff the aircraft directly to OXL
 
 *Initiating NFR*
 !!! example
@@ -135,7 +135,7 @@ Source: [Annotations](../../controller-skills/annotations)
 
 ## Rules
 ### General
-Coordination must be done on a **point-to-point** basis. Meaning, you can only coordinate with the sector which the aircraft is coming from, or going to, no skipping! This is important to remember, for example, if you are controlling ELW, and you would like to pass an amended route to someone on the ground at YMML. Whilst that may be no issue for ELW, ML SMC and ML ADC, it might not work for ML APP. ML APP would be the sector which the aircraft is coming from, so ELW must talk to them, and it is the responsibility of ML APP to work backwards down the line on a point-to-point basis.
+Coordination must be done on a **point-to-point** basis. Meaning, you can only coordinate with the sector which the aircraft is coming from, or going to, no skipping! This is important to remember, for example, if you are controlling BLA, and you would like to pass an amended route to someone on the ground at YMML. Whilst that may be no issue for BLA, ML SMC and ML ADC, it might not work for ML APP. ML APP would be the sector which the aircraft is coming from, so BLA must talk to them, and it is the responsibility of ML APP to work backwards down the line on a point-to-point basis.
 
 Ensure no coordination is ambiguous in its meaning. Not all coordination can be straight out of the phraseology books, and the reality is, not everyone controlling the airspace is going to be 100% proficient and by the books. When using "plain english", ensure there is no ambiguity, and the message is fully understood by both parties.
 ### ENR/TCU -> Class D TWR
@@ -243,8 +243,8 @@ For any aircraft transiting **to or from** Uncontrolled airspace (ie: Class G, V
 Receiving a handoff means you are permitted to turn an aircraft **45 degrees left or right**, and **climb/descend it to any level** without coordination. Do not handoff an aircraft to another sector if a turn of 45 degrees or a change of level would cause a conflict with any of your own aircraft. Or alternatively, you can nominate a restriction prior to handoff.
 
 !!! example
-    <span class="hotline">**YWE** -> **TBD**</span>: "ABC, my restriction is DEF, calls you now"  
-    <span class="hotline">**TBD** -> **YWE**</span>: "ABC, restriction is DEF, calls me now"
+    <span class="hotline">**MUN** -> **TBD**</span>: "ABC, my restriction is DEF, calls you now"  
+    <span class="hotline">**TBD** -> **MUN**</span>: "ABC, restriction is DEF, calls me now"
 
 Upon receipt of a handoff, once the aircraft is established **half the applicable lateral standard** (2.5nm for ENR, 1.5nm for ADC/TCU) within your airspace, you are free to turn the aircraft as much as you like. If you need to turn them more than 45 degrees earlier than that, simply ask!
 

docs/controller-skills/extending.md

@@ -21,7 +21,7 @@ Here are tips to help manage frequencies when extending:
     - An aircraft on the TBD frequency would have `TBD` in the label.
     - An aircraft on the ARL frequency would have `ARL` in the label.
 - *Optional:* When transferring an aircraft to its final frequency in your airspace, you can remove the frequency designator from the label
-- *Optional:* Prior to handing off an aircraft to another ENR sector that is extending to at least 2 sectors that the aircraft will fly through, put the frequency designator of the frequency you are telling the aircraft to call in the label. eg, controlling **ELW**, transferring aircraft bound for YPAD to **YWE**, who is also extending to **TBD**: Put `YWE` in label prior to handoff.
+- *Optional:* Prior to handing off an aircraft to another ENR sector that is extending to at least 2 sectors that the aircraft will fly through, put the frequency designator of the frequency you are telling the aircraft to call in the label. eg, controlling **BLA**, transferring aircraft bound for YPAD to **MUN**, who is also extending to **TBD**: Put `MUN` in label prior to handoff.
 
 ## Workload
 Extending to adjacent sectors **must** be done with traffic levels and complexity in mind. It is very easy to start controlling to several adjacent sectors when traffic is calm, then it slowly builds up without you noticing, and all of a sudden everyone is receiving a sub-par service. A great way to see this coming is from your **Preactive** and **Announced** strip windows. The more full they are, the busier you'll be in the next 10-60 minutes.
@@ -41,6 +41,6 @@ When extending, include in your remarks, *"Extending to (Sector) (frequency), (S
 
 !!! example
     Melbourne Centre  
-    Extending to HUO 122.6, YWE 134.325, BIK 129.8.  
+    Extending to HUO 122.6, MUN 132.6, GUN 128.4.  
     Charts - vats.im/pac/charts  
     ATC feedback - helpdesk.vatpac.org

docs/controller-skills/hoto.md

@@ -37,9 +37,9 @@ Anything else they need to know?
 ## Example
 !!! example
     "**Runway** 16 for arrivals, 27 for departures at YMML. Runway 34L and 34R at YSSY. Runway 35 at YSCB. Runway 25 at YMAY.  
-    **Airspace**, We're controlling ELW, extending to BIK, providing top-down at YMML, YSSY and YSCB. AY TWR is online, and YWE is online, extending to ARL and HUO. Airspace releases all normal.  
+    **Airspace**, We're controlling BLA, extending to GUN, providing top-down at YMML, YSSY and YSCB. AY TWR is online, and MUN is online, extending to ARL and HUO. Airspace releases all normal.  
     **Weather** is mostly normal, Area QNHs are high, except for a small part to the east of Area 30.  
     **Frequencies** active are 123.75 and 129.8.  
-    **Traffic**, QFA428 is taxiing 34L at YSSY, WOL2 departure for YMML. No other calls on the ground at YSSY, YSCB or YMML. VOZ831 is on climb, coordination to YWE is done. LPD has clearance to leave controlled airspace descending. QJE1721 and UAL19 are both estimating LIZZI at the same time, will need some sequencing. JST528 and BNZ192 are coming in from the north, haven't yet assessed if they're in conflict.  
+    **Traffic**, QFA428 is taxiing 34L at YSSY, WOL2 departure for YMML. No other calls on the ground at YSSY, YSCB or YMML. VOZ831 is on climb, coordination to MUN is done. LPD has clearance to leave controlled airspace descending. QJE1721 and UAL19 are both estimating LIZZI at the same time, will need some sequencing. JST528 and BNZ192 are coming in from the north, haven't yet assessed if they're in conflict.  
     No other **outstanding instructions** other than frequency transfers and handoffs.  
     Any questions?"  

docs/controller-skills/sequencing.md

@@ -144,19 +144,19 @@ Holding is the final delaying action, useful for when a delay of 6 minutes or mo
 Typically 1 standard holding pattern takes 6 minutes.
 
 !!! example
-    **YWE:** "BNZ135, hold at APPLE, maintain FL200."  
+    **MUN:** "BNZ135, hold at APPLE, maintain FL200."  
     **BNZ135:** "Hold at APPLE, maintain FL200, BNZ135"  
     ...  
-    **YWE:** "BNZ135, cancel hold, cleared APPLE, ARBEY, to rejoin the STAR, when ready, descend via STAR to A090, QNH 1013"  
+    **MUN:** "BNZ135, cancel hold, cleared APPLE, ARBEY, to rejoin the STAR, when ready, descend via STAR to A090, QNH 1013"  
     **BNZ135:** "Cancel hold, cleared APPLE, ARBEY, to rejoin the STAR, when ready, descend via STAR to A090, QNH 1013, BNZ135" 
 
 Although the phraseology *"Hold at (waypoint)"* is standardised from the AIP `AIP GEN 3.4`, it could mean pilots who are not familiar with published holding patterns do not fly the hold you were expecting them to. In this case, use specific instructions which gives more detail about the holding pattern. This is also applicable to holding at fixes where there is no published hold.
 
 !!! example
-    **ELW:** "VOZ888, hold at NABBA, inbound track 224 degrees, left hand pattern, outbound time 2 minutes, maintain FL200."  
+    **BLA:** "VOZ888, hold at NABBA, inbound track 224 degrees, left hand pattern, outbound time 2 minutes, maintain FL200."  
     **VOZ888:** "Hold at NABBA, inbound track 224 degrees, left hand pattern, outbound time 2 minutes, maintain FL200,VOZ888"  
     ...  
-    **ELW:** "VOZ888, Cancel hold, cleared NABBA, BULLA, TAREX, LIZZI, to rejoin the STAR, maintain F300"  
+    **BLA:** "VOZ888, Cancel hold, cleared NABBA, BULLA, TAREX, LIZZI, to rejoin the STAR, maintain F300"  
     **VOZ888:** "Cancel hold, cleared NABBA, BULLA, TAREX, LIZZI, to rejoin the STAR, maintain F300, VOZ888"
 
 It may be prudent to use another form of delaying action, other than holding, with aircraft that appear to be unable to fly a hold (use vectors).