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

Various small changes
vatpac-technology · Sep 10, 2024 · 74eb906 · 74eb906
2 parents 6e4a120 + bb65ce4
commit 74eb906
Show file tree

Hide file tree

Showing 54 changed files with 74 additions and 96 deletions.
diff --git a/docs/aerodromes/classc/Adelaide.md b/docs/aerodromes/classc/Adelaide.md
@@ -17,11 +17,7 @@
 AD ADC is not responsible for any airspace by default.
 
 ## Maneuvering Area Responsibility
-
-<figure markdown>
-![YPAD Maneuvering Area](img/ypad_maneuvring_area.png){ width="500" }
-  <figcaption>YPAD Maneuvering Area</figcaption>
-</figure>
+**ADC** is responsible for the **E2** and **D2** taxiways
 
 !!! note
     Where an aircraft will be taxiing via multiple taxiways of the same lettering (e.g. A6, then A5, then A4, etc), refer to the taxiway by only the letter.  

diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md
@@ -45,7 +45,7 @@ Taxiway Y is to be used in a westerly direction and Taxiway Z in an easterly dir
     A similar conflict may exist between aircraft taxiing inbound via taxiway Zulu and aircraft taxiing outbound for runway 19L. Consider instructing inbound aircraft to hold short of taxiway Y1, allowing the use of Y1 and Charlie in case of a queue for holding point A3.
 
 <figure markdown>
-![YBBN Taxi Route](img/ybbn_taxi_routes.png){ width="500" }
+![YBBN Taxi Route](img/ybbnstdtaxi.png){ width="500" }
   <figcaption>Standard Taxi Routes</figcaption>
 </figure>
 

diff --git a/docs/aerodromes/classc/Canberra.md b/docs/aerodromes/classc/Canberra.md
@@ -55,13 +55,8 @@ City Scenic Flights are available by day and to the west of the aerodrome. Aircr
 | South (clockwise)  | CHARLIE ONE  | CHARLIE TWO          | 
 
 <figure markdown>
-![City Flight One](img/CBCTY1.png){ width="500" }
-  <figcaption>City Flight One</figcaption>
-</figure>
-
-<figure markdown>
-![City Flight Two](img/CBCTY2.png){ width="500" }
-  <figcaption>City Flight Two</figcaption>
+![City Scenic Flights](img/cbcty.png){ width="500" }
+  <figcaption>City Scenic Flights</figcaption>
 </figure>
 
 ### Helicopter Operations

diff --git a/docs/aerodromes/classc/Goldy.md b/docs/aerodromes/classc/Goldy.md
@@ -55,7 +55,7 @@ The crosswind Runways 17/35 may be used at the same time as the main runways.
 
 ### Preferred RWY 14 Approach (All Hours) - Noise Abatement
 The preferred approach for Jet aircraft above 5,700KG MTOW (unless due weather or critical operations requirements) is as follows:  
-<ol><li>RNAV-W (RNP) RWY 14</li><li>RNAV-Y (RNP) RWY 14</li><li>RNAV-Z (GNSS) RWY 14</li><li>VISUAL APCH RWY 14</li><li>ILS RWY 14</li></ol>
+<ol><li>RNP W RWY 14</li><li>RNP Y RWY 14</li><li>RNP Z RWY 14</li><li>VISUAL APCH RWY 14</li><li>ILS RWY 14</li></ol>
 
 ### Circuit Direction
 Circuits are to be conducted at `A010`.  
@@ -75,11 +75,8 @@ Aircraft tracking northbound should contact ADC approaching Cudgen Lake for clea
 Aircraft requiring to transit the CTR coastal will be subject to delays depending on traffic in the Gold Coast CTR.  
 
 ## Helicopter Operations
-Local helicopter operations are conducted on the Western Grass which is the area contained by blue gable markers north of the VOR and west of the runway intersection. This is marked on the aerodrome chart as “HELO OPS”.
-!!! note
-    Western Grass is outside of the maneuvering area and is not controlled by ATC – no take-off or landing clearances shall be provided for this area.
-
-The HLS (Helipad) is located between the GA Apron and Taxiway Golf. 
+Local helicopter operations are conducted on the Western Grass which is the area contained by blue gable markers north of the VOR and west of the runway intersection. This is marked on the aerodrome chart as “HELO OPS”.  
+The HLS (Helipad) is located between the GA Apron and Taxiway Golf.  
 Circuits from the Western Grass are to be made in the same direction as the duty runway.
 
 ## Coordination

diff --git a/docs/aerodromes/classc/Sydney.md b/docs/aerodromes/classc/Sydney.md
@@ -99,7 +99,7 @@ Helipad 1 is controlled by **SY ADC** and treated like a runway (landing clearan
 
 ## Maneuvering Area Responsibility
 <figure markdown>
-![YSSY Maneuvering Area](img/yssy_maneuvring_area.png){ width="500" }
+![YSSY Maneuvering Area](img/yssymaown.png){ width="500" }
   <figcaption>Maneuvering Area</figcaption>
 </figure>
 

diff --git a/docs/aerodromes/classc/img/CBCTY1.png b/docs/aerodromes/classc/img/CBCTY1.png
diff --git a/docs/aerodromes/classc/img/CBCTY2.png b/docs/aerodromes/classc/img/CBCTY2.png
diff --git a/docs/aerodromes/classc/img/cbcty.png b/docs/aerodromes/classc/img/cbcty.png
diff --git a/docs/aerodromes/classc/img/ybbn_taxi_routes.png b/docs/aerodromes/classc/img/ybbn_taxi_routes.png
diff --git a/docs/aerodromes/classc/img/ybbnstdtaxi.png b/docs/aerodromes/classc/img/ybbnstdtaxi.png
diff --git a/docs/aerodromes/classc/img/ymmlstdtaxi.png b/docs/aerodromes/classc/img/ymmlstdtaxi.png
diff --git a/docs/aerodromes/classc/img/yssy_maneuvring_area.png b/docs/aerodromes/classc/img/yssy_maneuvring_area.png
diff --git a/docs/aerodromes/classc/img/yssymaown.png b/docs/aerodromes/classc/img/yssymaown.png
diff --git a/docs/aerodromes/classd/Archerfield.md b/docs/aerodromes/classd/Archerfield.md
@@ -11,11 +11,6 @@
 | Archerfield SMC   | Archer Ground  | 129.300         | AF_GND                       |
 | Archerfield ATIS        |                | 120.900          | YBAF_ATIS                                |
 
-<figure markdown>
-![YSBK Maneuvering Area](img/YBAF_ManMapB.PNG){ width="500" }
-  <figcaption>Maneuvering Area</figcaption>
-</figure>
-
 ## Airspace
 AF ADC is responsible for the Class D airspace in the AF CTR `SFC` to `A015`.
 

diff --git a/docs/aerodromes/classd/Bankstown.md b/docs/aerodromes/classd/Bankstown.md
@@ -11,11 +11,6 @@
 | Bankstown SMC   | Bankstown Ground   | 119.900         | BK_GND                       |
 | Bankstown ATIS        |                | 120.900          | YSBK_ATIS                                |
 
-<figure markdown>
-![YSBK Maneuvering Area](img/ysbk_maneuvring_area.png){ width="500" }
-  <figcaption>Maneuvering Area</figcaption>
-</figure>
-
 ## Airspace
 BK ADC is responsible for the Class D airspace in the BK CTR `SFC` to `A015`.
 

diff --git a/docs/aerodromes/classd/Camden.md b/docs/aerodromes/classd/Camden.md
@@ -12,12 +12,6 @@
 | Camden SMC  | Camden Ground   | 121.900          | CN_GND                      |
 | Camden ATIS        |                | 125.100          | YSCN_ATIS                                |
 
-
-<figure markdown>
-![YSCN Maneuvering Area](img/YSCN_ManMap.PNG){ width="500" }
-<figcaption>Maneuvering Area</figcaption>
-</figure>
-
 ## Airspace
 CN ADC is responsible for the Class D airspace in the CN CTR `SFC` to `A020`.
 

diff --git a/docs/aerodromes/classd/Hobart.md b/docs/aerodromes/classd/Hobart.md
@@ -11,11 +11,6 @@
 | Hobart SMC    | Hobart Ground  | 121.700     | HB_GND                  |
 | Hobart ATIS       |                | 128.450          | YMHB_ATIS                                |
 
-## Maneuvering Area Responsibility
-<figure markdown>
-![YMHB Maneuvering Area](img/ymhb_maneuvring_area.png){ width="500" }
-</figure>
-
 ## Airspace
 HB ADC is responsible for the Class D airspace in the HB CTR:  
 North of the Runway Centreline: `SFC` to `A015`  

diff --git a/docs/aerodromes/classd/Jandakot.md b/docs/aerodromes/classd/Jandakot.md
@@ -12,12 +12,6 @@
 | Jandakot SMC  | Jandakot Ground   | 124.300          | JT_GND                       |
 | Jandakot ATIS     |                | 128.650          | YPJT_ATIS                                |
 
-
-<figure markdown>
-![YPJT Maneuvering Area](img/ypjt_maneuvring_area.png){ width="500" }
-  <figcaption>Maneuvering Area</figcaption>
-</figure>
-
 ## Airspace
 JT ADC is responsible for the Class D airspace in the JT CTR `SFC` to `A015`.
 

diff --git a/docs/aerodromes/classd/Launceston.md b/docs/aerodromes/classd/Launceston.md
@@ -11,11 +11,6 @@
 | Launceston ADC    | Launy Tower   | 118.700    | LT_TWR                         |
 | Launceston ATIS       |                | 134.750          | YMLT_ATIS                                |
 
-### Maneuvering Area Responsibility
-<figure markdown>
-![YMLT Maneuvering Area](img/ymlt_maneuvring_area.png){ width="500" }
-</figure>
-
 ## Airspace
 LT ADC is responsible for the Class D airspace in the LT CTR `SFC` to `A015`.
 

diff --git a/docs/aerodromes/classd/Parafield.md b/docs/aerodromes/classd/Parafield.md
@@ -11,12 +11,6 @@
 | Parafield SMC   | Parafield Ground  | 119.900          | PF_GND                       |
 | Parafield ATIS        |                | 120.900          | YPPF_ATIS                                |
 
-
-<figure markdown>
-![YPPF Maneuvering Area](img/yppf_maneuvring_area.png){ width="500" }
-  <figcaption>Maneuvering Area</figcaption>
-</figure>
-
 ## Airspace
 PF ADC is responsible for the Class D airspace in the PF CTR `SFC` to `A015`.
 

diff --git a/docs/controller-skills/military.md b/docs/controller-skills/military.md
@@ -4,12 +4,21 @@ title: Military/Restricted Operations
 
 --8<-- "includes/abbreviations.md"
 
-## Restricted Areas
-Australian airspace is covered in Restricted Areas. Put simply, these are areas where aircraft are not allowed to go. They are shown in vatSys in yellow as below:
+## Special Use Airspace (SUA)
+SUAs, formerly known as Restricted Areas (RAs), are scattered all over Australian airspace. In real life, they can be used for many different purposes, including, but not limited to:
+
+- Military Activity (Most common)
+- Live Firing
+- Airshows
+- Operationally Restricted Airspace
+- Radiation Hazards
+- Rocket Launches
+
+Although the majority of these things don't pose any hazards in the online environment, activations of SUAs should still be simulated on VATSIM, and aircraft should be kept clear of them.
 
 <figure markdown>
-![Restricted Areas on vatSys](img/ra.png){ width="800" }
-  <figcaption>Restricted Areas on vatSys</figcaption>
+![SUAs on vatSys](img/ra.png){ width="800" }
+  <figcaption>SUAs on vatSys</figcaption>
 </figure>
 
 ### Vertical Limits
@@ -36,22 +45,29 @@ You must separate all aircraft in controlled airspace by *half the applicable la
 ### Activation times
 Some Restricted Areas are not always active. Some may be active only on certain days, or certain hours of the day. More info can be found in the [ERSA](https://www.airservicesaustralia.com/aip/aip.asp){target=new}, or on the Restricted Areas window in vatSys
 
-#### NOTAM
+### NOTAM
 Some Restricted Areas will be activated by NOTAM, most commonly for use by RAAF Virtual. These are available on the [VATPAC NOTAMs Page](https://vatpac.org/publications/notam){target=new}. These Restricted Areas will automatically become active on vatSys with AIRAC updates, so they are visually displayed on the screen.
 
-###### Example
+##### Example
 <figure markdown>
 ![Example Restricted Area Activation NOTAM](img/vsoanotam.png){ width="800" }
   <figcaption>Example Restricted Area Activation NOTAM</figcaption>
 </figure>
 
-#### Aircraft operating inside Restricted Area
+### Aircraft operating inside Restricted Area
 Military aircraft are permitted to operate within their designated Restricted Area as per the relevant NOTAM. Even if this Restricted Area is inside your airspace, you have no control authority over it.
 
 !!! example
     **ARA**: "DRGN379, shortly entering R604 Restricted Area, identification and control services terminated, frequency change approved. Contact me prior to leaving for airways clearance"  
     **DRGN379**: "Wilco, DRGN379"
 
+### ATC Activated Military Airspace
+Most Military TCUs and Tower positions, when online, control airspace that correspond to certain Restricted Area Activations. These are prescribed in the Local Instructions.
+
+These Restricted Areas may be activated in vatSys, and the controllers of these positions may inform other surrounding controllers of their activations, so they may use the Resitricted Areas on the screen to visually assess the airspace and separation required for traffic.
+
+Unless otherwise stated in Local Instructions, Restricted Areas activated for control by Military TCUs and Towers, will become **Class C** airspace.
+
 ## Formation Flights
 Reserved.
 

diff --git a/docs/enroute/Brisbane Centre/INL.md b/docs/enroute/Brisbane Centre/INL.md
@@ -228,7 +228,7 @@ Voiceless for all aircraft:
 
 - With ADES **YBRK**; and  
 - Assigned the **ABVAS** or **DADBO** STAR; and  
-- Assigned `A070`
+- Assigned `A090`
 
 All other aircraft coming from KPL CTA must be **Heads-up** Coordinated to RKA prior to **20nm** from the boundary.
 

diff --git a/docs/enroute/Brisbane Centre/KEN.md b/docs/enroute/Brisbane Centre/KEN.md
@@ -184,7 +184,7 @@ Voiceless for all aircraft:
 
 - With ADES **YBMK**; and  
 - Assigned the **DAGSI** or **WELKE** STAR; and  
-- Assigned `A070`
+- Assigned `A090`
 
 All other aircraft coming from SWY CTA must be **Heads-up** Coordinated to MKA prior to **20nm** from the boundary.
 

diff --git a/docs/enroute/Melbourne Centre/PIY.md b/docs/enroute/Melbourne Centre/PIY.md
@@ -19,7 +19,7 @@
 
 ### CPDLC
 
-The Primary Communication Method for ELW is Voice.
+The Primary Communication Method for PIY is Voice.
 
 [CPDLC](../../../client/cpdlc) may be used in lieu when applicable.
 

diff --git a/docs/oceanic/Positions/IND.md b/docs/oceanic/Positions/IND.md
@@ -46,7 +46,7 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR
 
 ## Coordination
 ### Domestic Enroute
-As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
+As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary.
 
 ### IND Internal
 As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary.

diff --git a/docs/oceanic/Positions/TSN.md b/docs/oceanic/Positions/TSN.md
@@ -59,8 +59,8 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR
 | FLD | KEN(All) | YBCS, YBTL | |
 
 ## Coordination
-### Enroute
-As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
+### Domestic Enroute
+As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary.
 
 ### TSN Internal
 As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary.

diff --git a/docs/separation-standards/classd.md b/docs/separation-standards/classd.md
@@ -28,16 +28,26 @@ Although Surveillance standards cannot be used for separation at Class D Towers,
 - Can be applied between departures and arrivals when the departing aircraft's flight path and the arrival aircraft's flight path are at least 45° clear of each other, and, for a straight-in approach, the arriving aircraft is at least **5nm** from the arrival runway threshold
 
 <figure markdown>
-![Segregated Flight Paths - Straight-in](img/sfpsi.png){ width="700" }
-  <figcaption>Segregated Flight Paths - Straight-in</figcaption>
+![Segregated Flight Paths - Straight-in (Prior to 5nm)](img/45segregatedfpsi1.png){ width="700" }
+  <figcaption>Segregated Flight Paths - Straight-in (Prior to 5nm)</figcaption>
+</figure>
+
+<figure markdown>
+![Segregated Flight Paths - Straight-in (After 5nm)](img/45segregatedfpsi2.png){ width="700" }
+  <figcaption>Segregated Flight Paths - Straight-in (After 5nm)</figcaption>
 </figure>
 
 #### Visual, DME/GNSS, Circle to land
 - Can be applied between departures and arrivals when the departing aircraft's flight path and the arrival aircraft's flight path are at least 45° clear of each other, and, for a Visual, DME/GNSS or Circle to land approach, the arriving aircraft is at least **10nm** from the airfield
 
 <figure markdown>
-![Segregated Flight Paths - Visual, DME/GNSS, Circle to land](img/sfpdga.png){ width="700" }
-  <figcaption>Segregated Flight Paths - Visual, DME/GNSS, Circle to land</figcaption>
+![Segregated Flight Paths - Visual, DME/GNSS, Circle to land (Prior to 10nm)](img/45segregatedfpcircle1.png){ width="700" }
+  <figcaption>Segregated Flight Paths - Visual, DME/GNSS, Circle to land (Prior to 10nm)</figcaption>
+</figure>
+
+<figure markdown>
+![Segregated Flight Paths - Visual, DME/GNSS, Circle to land (After 10nm)](img/45segregatedfpcircle2.png){ width="700" }
+  <figcaption>Segregated Flight Paths - Visual, DME/GNSS, Circle to land (After 10nm)</figcaption>
 </figure>
 
 ## Vertical

diff --git a/docs/separation-standards/img/20nmlong.png b/docs/separation-standards/img/20nmlong.png
diff --git a/docs/separation-standards/img/45segregatedfpcircle1.png b/docs/separation-standards/img/45segregatedfpcircle1.png
diff --git a/docs/separation-standards/img/45segregatedfpcircle2.png b/docs/separation-standards/img/45segregatedfpcircle2.png
diff --git a/docs/separation-standards/img/45segregatedfpsi1.png b/docs/separation-standards/img/45segregatedfpsi1.png
diff --git a/docs/separation-standards/img/45segregatedfpsi2.png b/docs/separation-standards/img/45segregatedfpsi2.png
diff --git a/docs/separation-standards/img/5nmlong.png b/docs/separation-standards/img/5nmlong.png
diff --git a/docs/separation-standards/img/arr10nm.png b/docs/separation-standards/img/arr10nm.png
diff --git a/docs/separation-standards/img/d2.png b/docs/separation-standards/img/d2.png
diff --git a/docs/separation-standards/img/d5.png b/docs/separation-standards/img/d5.png
diff --git a/docs/separation-standards/img/d8b.png b/docs/separation-standards/img/d8b.png
diff --git a/docs/separation-standards/img/dep10min.png b/docs/separation-standards/img/dep10min.png
diff --git a/docs/separation-standards/img/dep2min.png b/docs/separation-standards/img/dep2min.png
diff --git a/docs/separation-standards/img/dep4a.png b/docs/separation-standards/img/dep4a.png
diff --git a/docs/separation-standards/img/dep5min.png b/docs/separation-standards/img/dep5min.png
diff --git a/docs/separation-standards/img/dep7a.png b/docs/separation-standards/img/dep7a.png
diff --git a/docs/separation-standards/img/diagonalsep.png b/docs/separation-standards/img/diagonalsep.png
diff --git a/docs/separation-standards/img/sandp.png b/docs/separation-standards/img/sandp.png
diff --git a/docs/separation-standards/img/sfpdga.png b/docs/separation-standards/img/sfpdga.png
diff --git a/docs/separation-standards/img/sfpsi.png b/docs/separation-standards/img/sfpsi.png
diff --git a/docs/separation-standards/img/snp.png b/docs/separation-standards/img/snp.png
diff --git a/docs/separation-standards/img/t7b.png b/docs/separation-standards/img/t7b.png
diff --git a/docs/separation-standards/img/visualfix.png b/docs/separation-standards/img/visualfix.png
diff --git a/docs/separation-standards/parallelapps.md b/docs/separation-standards/parallelapps.md
@@ -19,6 +19,11 @@ The following page applies to Parallel Runway Operations at [YSSY](../../termina
     - **1.5nm** at [YBBN](../../terminal/brisbane/#parallel-runway-operations)  
     - **1nm** at [YSSY](../../terminal/sydney/#parallel-runway-operations)
 
+<figure markdown>
+![Diagonal Separation Diagram](img/diagonalsep.png){ width="700" }
+  <figcaption>Diagonal Separation Diagram</figcaption>
+</figure>
+
 ## Independent Visual Approaches
 - When vectoring an aircraft to intercept the final course, ensure that the final vector permits the aircraft to intercept at an angle not greater than 30 degrees.