tn tcu tweaks

vatpac-technology · Dec 18, 2024 · 603eb70 · 603eb70
1 parent 1ba9f38
commit 603eb70
Show file tree

Hide file tree

Showing 3 changed files with 104 additions and 44 deletions.
diff --git a/docs/aerodromes/classc/Tindal.md b/docs/aerodromes/classc/Tindal.md
@@ -22,7 +22,7 @@ Aircraft planned via **DN**, **LAREB**, **GREGA**, **DOSAM**, **MILIV**, **MIGAX
 Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure.
 
 #### Gate Departures (All Military Aircraft)
-There are 11 gates to facilate departues and arrivals from the TN Training Airspace, based on the TN TACAN. Aircraft can be cleared to track direct to the gate, or allow them to intercept the outbound radial by 10 DME. 
+There are 11 gates to facilate departues and arrivals from the TN Training Airspace, based on the TDL TACAN. Aircraft can be cleared to track direct to the gate, or allow them to intercept the outbound radial by 10 DME. 
 
 | Gate Name | Ident | Bearing (°M) | Distance (nm) | Restricted Area |
 | ------ | ----------| ----------| ----------| ----------|
@@ -87,6 +87,8 @@ The intial point is at A020 on the extended centerline of Taxiway Alpha at 6.5NM
     <span class="hotline">**TN TCU** -> **TN ADC**</span>: "ASY01, Assigned Heading Right 030, unrestricted"  
     <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Assigned Heading Heading Right 030, ASY01"  
 
+The Standard Assignable level from TN ADC to TN TCU is the lower of `F180` or the RFL.
+
 ### TRT(TRS)
 When TN TCU is offline, coordination is not required between TN ADC and TRT(TRS). Aircraft entering TRT(TRS) airspace shall be handed off, and instructed to contact TRT(TRS) for onwards clearance.
 

diff --git a/docs/enroute/Brisbane Centre/TRT.md b/docs/enroute/Brisbane Centre/TRT.md
@@ -15,7 +15,6 @@
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}
 
 ### CPDLC
-
 The Primary Communication Method for ISA is [CPDLC](../../../client/cpdlc).
 
 The CPDLC Station Code is `YISA`.
@@ -38,6 +37,19 @@ 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.
 
+#### TN TCU
+TN TCU being online will activate the following Airspace by default:
+
+- TN MIL CTR `SFC`-`A025`
+- R249A `A015`-`A025`
+- R249B `A025`-`F190`
+- R238 `A035`-`F190`
+
+All of which are reclassified as **Class C** when active, and TN APP has Control Authority of.
+
+!!! note
+    TN APP may negotiate with TRS for an increase to the upper limit of the Restricted Areas and their airspace, if required for military operations. This limit may also be changed by NOTAM.
+
 ## Extending
 !!! warning "Important"
     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.
@@ -125,20 +137,45 @@ The Standard Assignable level from TRT(ASH) to BRM ADC is `A060`, any other leve
 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(ASH) to CIN TCU is `F130`, tracking via CIN VOR.
+The Standard assignable level from 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(ASH) is `F190`, and tracking via their planned route.
+The Standard Assignable level from CIN TCU to ASH is `F190`, and tracking via their planned route.
 
 #### CIN ADC
-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.
+When CIN TCU is offline, coordination is not required between 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`.
 
 ### TN TCU
-Reserved.
+#### Airspace
+Any airspace releases from the default setup must be coordinated and agreed upon with TRT(TRS). It is also good practice to remind them of any airspace releases that may be active due to NOTAMs.
+
+#### Departures
+Voiceless for all aircraft:
+
+- Tracking via a Procedural SID terminus; and  
+- Assigned the lower of `F180` or the `RFL`
+
+All other aircraft going to TRS CTA must be **Heads-up** Coordinated by TN TCU prior to the boundary.
+
+!!! phraseology
+    <span class="hotline">**TN TCU** -> **TRS**</span>: "DRGN48, request DCT BEBEX"  
+    <span class="hotline">**TRS** -> **TN TCU**</span>: "DRGN48, concur DCT BEBEX"  
+
+#### Arrivals/Overfliers
+Voiceless for all aircraft:
+
+- Tracking via **TN**; and  
+- Assigned the lower of `F130` or the `RFL`.
+
+All other aircraft coming from TRS CTA will be **Heads-up** Coordinated to TN TCU.
+
+!!! phraseology
+    <span class="hotline">**TRS** -> **TN TCU**</span>: "via NOLEK, FD858"  
+    <span class="hotline">**TN TCU** -> **TRS**</span>: "FD858, F150" 
 
 ### IND(INE) (Oceanic)
 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/terminal/tindal.md b/docs/terminal/tindal.md
@@ -11,69 +11,90 @@
 | **Tindal Approach**    | **Tindal Approach**   | **120.95** | **TN_APP** |
 
 ## Airspace
-### Default
-By default, TN TCU owns the airspace within the TN MIL CTR `SFC` to `F190`. This may be amended by NOTAM.
+TN APP being online will activate the following Airspace by default:
 
-!!! note
-    It is the responsibility of the TN TCU controller(s) to negotiate any airspace releases with TRT(All).
+- TN MIL CTR `SFC`-`A025`
+- R249A `A015`-`A025`
+- R249B `A025`-`F190`
+- R238 `A035`-`F190`
+
+All of which are reclassified as **Class C** when active, and TN APP has Control Authority of.
 
-### ADC
-When TN ADC is online, they own the airspace within the TN MIL CTR A (`SFC`-`A025`). This may be amended/released as required between TN ADC and TN TCU.
+!!! note
+    TN APP may increase the upper limit of the Restricted Areas and their airspace. This must be either published by NOTAM, or negotiated with TRT(TRS) if online.
 
 ## 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}
 
-## Coordination
-### TRT(All)
+## Arrival/Departure Gates
+There are 11 gates to facilate departues and arrivals from the TN Training Airspace, based on the TDL TACAN.  
+Departing aircraft will be cleared to track direct to the gate, or allowed to intercept the outbound radial by 10 DME.  
+Arrivals can be cleared via the appropriate gate for their return to YPTN.
+
+| Gate Name | Ident | Bearing (°M) | Distance (nm) | Restricted Area |
+| ------ | ----------| ----------| ----------| ----------|
+| BIAK     | BIA | 320 | 30 | N/A |
+| TOP GATE     | TOP | 300 | 30 | R225D |
+| MOROTAI     | MOR | 270 | 30 | R225D |
+| TADJI     | TAD | 240 | 30 | R225D |
+| TARAKAN     | TAR | 200 | 30 | R225D |
+| BOTTOM GATE     | BOM | 190 | 30 | R225D |
+| NADZAB     | NAD | 150 | 30 | N/A |
+| MILNE     | MIL | 090 | 30 | R226A |
+| WEDGE 1     | W1 | 285 | 16 | R238 |
+| WEDGE 2     | W2 | 260 | 12 | R238 |
+| WEDGE 3     | W3 | 200 | 16 | R238 |
+
+<figure markdown>
+![Tindal Gates](img/../../aerodromes/classc/img/yptngates.png){width="700"}
+  <figcaption>Tindal Gates</figcaption>
+</figure>
+
+!!! phraseology 
+    CLAS35 has completed operations in R225, and is requesting return to YPTN via TARAKAN Gate.  
+    **TN TCU**: "CLAS35, cleared to YPTN via TARAKAN, thence TN. When ready descend to F130"   
+
+Place/Bearing Distance points in the FDR can be used for routing via the gates, with **TN** as the reference point, in the format PPPPBBBDDD.
+
+!!! example 
+    MOROTAI = TN170030  
+    NADZAB = TN150030  
 
+## Coordination
+### TRT(TRS)
 #### Airspace
-Any airspace releases from the default setup must be coordinated and agreed upon with TRT. It is also good practice to remind them of any airspace releases that may be active due to NOTAMs.
+Any airspace releases from the default setup must be coordinated and agreed upon with TRT(TRS). It is also good practice to remind them of any airspace releases that may be active due to NOTAMs.
 
 #### Departures
 Voiceless for all aircraft:
 
 - Tracking via a Procedural SID terminus; and  
-- Assigned the lower of `F190` or the `RFL`
+- Assigned the lower of `F180` or the `RFL`
 
 !!! note
     Aircraft are *not required* to be tracking via the **SID procedure**, simply tracking via any of the terminus waypoints (Regardless of *departure airport* or *assigned SID*) is sufficient to meet the criteria for **voiceless coordination**
 
 All other aircraft going to TRT CTA must be **Heads-up** Coordinated by TN TCU prior to the boundary.
 
-!!! example
-    <span class="hotline">**TN TCU** -> **TRT**</span>: "DRGN48, request DCT BEBEX"  
-    <span class="hotline">**TRT** -> **TN TCU**</span>: "DRGN48, concur DCT BEBEX"  
+!!! phraseology
+    <span class="hotline">**TN TCU** -> **TRS**</span>: "DRGN48, request DCT BEBEX"  
+    <span class="hotline">**TRS** -> **TN TCU**</span>: "DRGN48, concur DCT BEBEX"  
 
 #### Arrivals/Overfliers
 Voiceless for all aircraft:
 
-- With ADES **YPTN**; and  
-- Assigned a STAR; and  
-- Assigned `F115`
+- Tracking via **TN**; and  
+- Assigned the lower of `F130` or the `RFL`.
 
-All other aircraft coming from TRT CTA will be **Heads-up** Coordinated to TN TCU.
+All other aircraft coming from TRT(TRS) CTA will be **Heads-up** Coordinated to TN TCU.
 
-### ADC
-#### Airspace
-TN ADC owns the airspace within the TN MIL CTR A (`SFC`-`A025`). This may be amended/released as required between TN ADC and TN TCU.
+### TN ADC
+'Next' coordination is required from TN ADC to TN TCU for all aircraft.
 
-#### Departures
-'Next' coordination is **not** required from TN ADC to TN TCU for aircraft that are:  
-a) Departing from a runway nominated in the ATIS; and  
-b) Assigned the standard assignable level;  
-c) Assigned a **Procedural** SID  
-
-!!! example
-    <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Next, MVP"  
-    <span class="hotline">**TN TCU** -> **TN ADC**</span>: "MVP, Left Heading 010, Unrestricted"  
-    <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Left Heading 010, MVP"  
-
-The Standard Assignable level from TN ADC to TN TCU is the lower of `F120` or the `RFL`.
-
-#### Arrivals/Overfliers
-Voiceless coordination is in place from TN TCU to TN ADC for arrivals cleared for an approach on to a runway nominated on the ATIS. All other aircraft and all overfliers must be heads-up coordinated as soon as practical.
+!!! phraseology
+    <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Next, ASY01, runway 32"  
+    <span class="hotline">**TN TCU** -> **TN ADC**</span>: "ASY01, Assigned Heading Right 030, unrestricted"  
+    <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Assigned Heading Heading Right 030, ASY01"  
 
-!!! example
-    <span class="hotline">**TN TCU** -> **TN ADC**</span>: "via TN, ZULU, Close formation of 5, do you have any restrictions or requirements?”  
-    <span class="hotline">**TN ADC** -> **TN TCU**</span>: "ZULU, no restrictions or requirements, A025"  
+The Standard Assignable level from TN ADC to TN TCU is the lower of `F180` or the RFL.