Changes 3

vatpac-technology · Dec 17, 2023 · 9e33a50 · 9e33a50
1 parent 4bb5d19
commit 9e33a50
Show file tree

Hide file tree

Showing 5 changed files with 21 additions and 21 deletions.
diff --git a/docs/aerodromes/Amberley.md b/docs/aerodromes/Amberley.md
@@ -32,7 +32,7 @@ Visual Departures are commonly requested which are often in the form of a coded
 Aircraft will make a visual departure in the circuit direction and fly overhead YAMB to begin tracking for their initial waypoint.
 
 !!! example
-    CRNG21 plans to enter R637 via the gate Mossi for Military Training.
+    CRNG21 plans to enter R637 via the gate MOSSI for Military Training.
     **AM ADC**: "CRNG21, Cleared to YAMB via MOSSI, Flight Planned Route. Runway 15, Northern 1 Departure. Climb to `F190`. Squawk 3601, Departure Frequency 126.20"  
 
 !!! example
@@ -73,7 +73,7 @@ The Circuit Area Airspace is allocated to be within 5nm of the YAMB ARP from `SF
 | 22     | Left |
 
 ## Coordination
-### AMB TCU
+### AM TCU
 
 'Next' coordination is required from AM ADC to AM TCU for all aircraft.
 

diff --git a/docs/aerodromes/Oakey.md b/docs/aerodromes/Oakey.md
@@ -10,6 +10,7 @@
 | ------------------ | -------------- | ---------------- | --------------------------------------|
 | Oakey ADC    | Oakey Tower  | 120.100         | OK_TWR        |
 | Oakey SMC    | Oakey Ground  | 121.900      | OK_GND        |
+| Oakey ATIS   |               | 124.300      | YBOK_ATIS     |
 
 ## Airspace
 
@@ -46,5 +47,4 @@ The standard circuit direction is to the north of the field.
     <span class="hotline">**OK TCU** -> **OK ADC**</span>: "MRCH01, Make Right Turn, unrestricted"  
     <span class="hotline">**OK ADC** -> **OK TCU**</span>: "Make Right Turn, MRCH01"  
 
-### Level Assignment
 The Standard Assignable level from **OK ADC** to **OK TCU** is the lower of `F120` or the `RFL`.
diff --git a/docs/enroute/Brisbane Centre/INL.md b/docs/enroute/Brisbane Centre/INL.md
@@ -179,12 +179,16 @@ Any aircraft that will enter CFS ADC airspace, and not landing at YCFS, must be
 By default, **OK TCU** owns the airspace within the **R654A-D** restricted areas, and **AMB TCU** owns the airspace within the **R625A-D** restricted areas, unless stated otherwise by ad-hoc release or NOTAM.
 
 #### Departures
-Departures from YBOK and YAMB in to GOL/DOS/BUR Class C will be coordinated at taxi, and will be requesting a level.
+All aircraft from AM/OK TCU to INL(All) require Heads-up coordination prior to the boundary, however as soon as practical (when is the aircraft becomes airborne) is prefered.
 
 !!! example
-    <span class="coldline">**OK TCU** -> **DOS**</span>: "Taxi, VLAN48 for YBOK via MATVI, Requesting F140"  
-    <span class="coldline">**DOS** -> **OK TCU**</span>: "VLAN48, F140"  
-    <span class="coldline">**OK TCU** -> **DOS**</span>: "F140, VLAN48"  
+    <span class="hotline">**AM TCU** -> **BN TCU**</span>: "via BN, DRGN02"  
+    <span class="hotline">**BN TCU** -> **AM TCU**</span>: "DRGN02, `F180`"  
+
+!!! example
+    BUCK03 is assigned the BYRON 7 coded departure. 
+    <span class="hotline">**AM TCU** -> **NSA**</span>: "via COWIE, BUCK3."  
+    <span class="hotline">**NSA** -> **AM TCU**</span>: "BUCK03, `F190`"  
 
 #### Arrivals/Overfliers
 All aircraft transiting from GOL/DOS/BUR to **OK TCU** and **AMB TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **OK TCU** and **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the GOL/DOS/BUR and **WLM TCU** controller agree on.

diff --git a/docs/terminal/amberleyoakey.md b/docs/terminal/amberleyoakey.md
@@ -14,6 +14,7 @@
 | Amberley TCU   | Amberley Approach   | 126.200        | AM_APP                                   |
 | Oakey TCU   | Oakey Approach | 125.400        | OK_APP                                   |
 
+AM APP is expected to extend to OK APP when they are offline. No frequency cross coupling is required. 
 
 
 ## Airspace
@@ -111,7 +112,6 @@ Aircraft will make a visual departure in the circuit direction and fly overhead
 #### Departures
 All aircraft from AM/OK TCU to INL(All) and BN TCU require Heads-up coordination prior to the boundary, however, as soon as practical (when is the aircraft becomes airborne) is prefered.
 
-#### Level Assignment
 The Standard Assignable Level from  **AM ADC** to **AM TCU** is:  
 a) The Lower of `F180` or `RFL` for Aircraft assigned via Procedural or RNAV SID.  
 b) `F190` for Aircraft assigned a Coded Departure.
@@ -124,11 +124,11 @@ The Standard Assignable from **OK ADC** to **OK TCU** is the lower of `F120` or
 
 !!! example
     BUCK03 is assigned the BYRON 7 coded departure. 
-    <span class="hotline">**AM TCU** -> **NSA**</span>: "BUCK03, with your concurrence assigned `F190`, Byron 7 departure."  
+    <span class="hotline">**AM TCU** -> **NSA**</span>: "via COWIE, BUCK3."  
     <span class="hotline">**NSA** -> **AM TCU**</span>: "BUCK03, `F190`"  
 
 #### Arrivals/Overlfies
-All aircraft transiting from GOL/DOS/BUR and **BN TCU** to **AM TCU** and **OK TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the GOL/DOS/BUR and **AM TCU**/**OK TCU** controller agree on.
+All aircraft transiting from GOL/DOS/BUR to **AM TCU** and **OK TCU** must be heads-up coordinated prior to **20nm** from the boundary and aircraft from **BN TCU** to **AM TCU** only prior to the boundary. Operations within **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the GOL/DOS/BUR and **AM TCU**/**OK TCU** controller agree on.
 
 !!! example
     <span class="hotline">**GOL** -> **AMB TCU**</span>: "via HUUGO, PUMA11, will be assigned A090"  

diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md
@@ -180,22 +180,18 @@ VFR aircraft require a level readback.
     <span class="hotline">**AF ADC** -> **BN TCU**</span>: "UJE, visual approach"
 
 ### AMB TCU
-
-#### Departures
-Departures from YAMB in to BN TCU Class C will be coordinated at taxi, and will be requesting a level.
+All aircraft transiting from **BN TCU** to **AM TCU** and vice versa must be heads-up coordinated prior to the boundary. 
 
 !!! example
-    <span class="coldline">**AMB TCU** -> **BN TCU**</span>: "Taxi, FALC22 for YSRI via GOMOL, Requesting F340"  
-    <span class="coldline">**BN TCU** -> **AMB TCU**</span>: "FALC22, F180"  
-    <span class="coldline">**AMB TCU** -> **BN TCU**</span>: "F180, FALC22"  
+    <span class="hotline">**AM TCU** -> **BN TCU**</span>: "via BN, DRGN02"  
+    <span class="hotline">**BN TCU** -> **AM TCU**</span>: "DRGN02, `F180`"  
 
-#### Arrivals/Overfliers
-All aircraft transiting from BN TCU to **AMB TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the BN TCU and **AMB TCU** controller agree on.
+For aircraft arriving into AM TCU there is no standard assignable level and simply is what ever the controllers agree upon.
 
 !!! example
-    <span class="hotline">**BN TCU** -> **AMB TCU**</span>: "via WACKO, STAL13, what level can I assign?"  
-    <span class="hotline">**AMB TCU** -> **BN TCU**</span>: "STAL13, A050"  
-    <span class="hotline">**BN TCU** -> **AMB TCU**</span>: "A050, STAL13"  
+    <span class="hotline">**BN TCU** -> **AM TCU**</span>: "via WACKO, STAL13, what level can I assign?"  
+    <span class="hotline">**AM TCU** -> **BN TCU**</span>: "STAL13, `A050`"  
+    <span class="hotline">**BN TCU** -> **AM TCU**</span>: "`A050`, STAL13"  
 
 ### SU ADC
 BN TCU Class G shares a tiny border with **SU ADC**, however there are no SIDs, STARs, or airways through this gap. The only possible way for an aircraft to directly enter SU ADC airspace from BN TCU's jurisdiction, is from Class G, and as such, no coordination is required to **SU ADC**. However, ensure the aircraft is transferred to the ADC at least **10nm** prior to the boundary, to facilitate their airways clearance.