ASP/ISA Extension Rule Removal

docs/controller-skills/extending.md

@@ -4,10 +4,7 @@ title: Extending
 
 --8<-- "includes/abbreviations.md"
 
-As per [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}, Enroute controllers are permitted to *extend* to any adjacent sector, with the exception of:
-
-- ASP, which can only extend to adjacent YMMM (Melbourne Centre) sectors.
-- ISA, which can only extend to adjacent YBBB (Brisbane Centre) sectors.
+As per [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}, Enroute controllers are permitted to *extend* to any adjacent sector. Controllers must ensure that when extending, they update their visibility points and have sufficient visibility coverage to cover the **entirety** of all sectors under their jurisdiction. If this is not possible (due to range limitations), that sector **must not be extended**. 
 
 TCU controllers operating the **Coral** or **Tasmania** TMAs may elect to extend to the adjacent TMA (e.g. HBA extend to LTA) at their discretion.
 
@@ -34,13 +31,13 @@ If you find yourself barely having any time to think in between radio calls, **r
 If the frequency is constantly getting stepped on by multiple aircraft, **relinquish some airspace**.  
 
 !!! tip
-    Stay vigilant for aircraft in your airspace taxiing without calling up. Many aerodromes have Radar/ADSB on the ground, and this can be used in conjunction with the ground radar to check for aircraft movements. If you zoom right in to a Radar/ADSB return on the ground, and it has a velocity vector, time to send a contact me!
+    Stay vigilant for aircraft in your airspace taxiing without calling up. Many aerodromes have Radar/ADSB on the ground, and this can be used in conjunction with the ground radar to check for aircraft movements. If you zoom right in to a Radar/ADSB return on the ground at an aerodrome you are top down to, and it has a velocity vector, time to send a contact me!
 
 ## Remarks
 When extending, include in your remarks, *"Extending to (Sector) (frequency), (Sector) (frequency), etc.* This will have the benefit of:  
 - Helping pilots be aware of whether or not they are in your airspace, so they are less likely to start taxiing without a clearance or traffic statement  
 - Helping pilots know which frequency to use  
-- If entered in this format, display on Volanta the extensions on the ATC map.
+- If entered in this format, display the extensions on certain VATSIM traffic coverage apps.
 
 !!! example
     Melbourne Centre  

docs/enroute/Brisbane Centre/ISA.md

@@ -34,9 +34,8 @@ Voice may be used in lieu when applicable.
 ISA is responsible for **ARA**, **STR**, **WEG**, and **CVN** when they are offline.  
 
 ## Extending
-
 !!! Warning
-    BN-ISA_CTR is only permitted to extend to adjacent **YBBB** sectors.
+    Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety.
 
 ## Sector Responsibilities
 ISA and its subsectors are purely Classes A, E and G of airspace. [Standard separation procedures](../../../separation-standards) apply.

docs/enroute/Brisbane Centre/TRT.md

@@ -38,6 +38,10 @@ When **BRM ADC** is offline, BRM CTR (Class D/E `SFC` to `A055`) reverts to Clas
 !!! 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.
 
+## Extending
+!!! Warning
+    Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety.
+
 ## Sector Responsibilities
 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.

docs/enroute/Melbourne Centre/ASP.md

@@ -43,7 +43,7 @@ When **AS ADC** is offline, AS CTR (Class D and C `SFC` to `F125`) within 80 DME
 
 ## Extending
 !!! Warning
-    ML-ASP_CTR is only permitted to extend to adjacent **YMMM** sectors.
+    Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety.
 
 ## Surveillance Coverage
 Limited surveillance coverage exists in the FOR sector greater than **250nm** from ADSB stations. [Procedural Standards](../../../separation-standards/procedural/) must be implemented **prior** to losing surveillance coverage

docs/enroute/Melbourne Centre/YWE.md

@@ -34,6 +34,10 @@ The CPDLC Station Code is `YYWE`.
   <figcaption>Yarrowee Airspace</figcaption>
 </figure>
 
+## Extending
+!!! Warning
+    Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety.
+
 ## Sector Responsibilities
 ### Yarrowee (YWE)
 YWE is responsible for the final sequencing actions in to YMML.