Skip to content

Commit dbf5d8c

Browse files
chrisg06chrisg06
authoredApr 6, 2024··
Merge pull request #226 from vatpac-technology/alex-dev
2 parents 6dda935 + be82086 commit dbf5d8c

File tree

14 files changed

+196
-183
lines changed

14 files changed

+196
-183
lines changed
 

‎docs/aerodromes/classc/Essendon.md

+18-17
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,17 @@
1212
| Essendon ATIS | | 119.800 | YMEN_ATIS |
1313

1414
## Airspace
15-
EN ADC is responsible for the Class C airspace in the "Coffin" `SFC` to `A015`, and in the "South East Quadrant" `SFC` to `A020`.
15+
EN ADC is responsible for the Class C airspace shown below, `SFC` to `A020`.
1616

1717
<figure markdown>
18-
![EN ADC Airspace](img/ENTWR.png){ width="500" }
19-
</figure>
20-
21-
<figure markdown>
22-
![EN ADC ML Airspace](img/MLTCUairspace.png){ width="500" }
18+
![EN ADC Airspace](img/enadc.png){ width="700" }
2319
</figure>
2420

2521
## Runway Selection
2622
Consideration of the Melbourne duty runway(s) should be made when nominating runways. The effect of Melbourne traffic on a runway selection takes priority over compliance with DAP Noise Abatement Procedures.
2723

24+
The 26A17D runway mode is most optimal for facilitating separation with YMML traffic.
25+
2826
## Departures
2927
IFR flights shall be cleared via:
3028
a) When cloud base and visibility exceeds `A020` and 5 KM, visual departure;
@@ -75,16 +73,16 @@ VFR arrivals from Class G shall be cleared (at not above `A015`) via:
7573
Circuits are to be flown at `A015`
7674

7775
## Separation
76+
EN ADC is responsible for **all separation** with YMML Traffic, including arrivals to RWY34 via the MONTY-SHEED track, and all potential arrivals, departures, and missed approach paths.
77+
Some important points to note are that:
78+
- Aircraft operating on or south of the 08/26 Centreline are separated with YMML 09/27 Traffic at all times
79+
- Aircraft operating on or east of the 17/35 Centreline are **only** visually separated with YMML 16/34 Traffic in **Day VMC**
80+
- Aircraft conducting the ILS 26 Published Missed Approach are **only** visually separated with YMML 16/34 Traffic in **Day VMC**
7881

79-
### Separation with SHEED Track
80-
By day only, ML TCU may require EN ADC to separate aircraft from the MONTY – SHEED track for RWY 34 ML during the Next call. EN ADC shall separate by restricting the departure to `A015` until clear of the MONTY – SHEED track.
82+
EN ADC must assume that **any runway** at YMML may be used for arrival, departure, or a missed approach, **at any time**.
83+
When the cloud base is below **A020**, or the Visibility is below **5000m**, all aircraft operating within **3nm** of the 09/27 or 16/34 extended centreline must be [boundary coordinated](../../../controller-skills/coordination/#boundary) to ML ADC, as prescribed in [Coordination](#ml-adc)
8184

82-
### Additional EN ADC separation requirements
83-
EN TWR shall separate traffic in EN airspace with:
84-
a) ML RWY 27 Arrivals and ML RWY 09 Departures on or north of ML RWY 09 / 27 centreline;
85-
b) ML RWY 34 arrivals and ML RWY 16 Departures on or west of ML RWY 16 / 34 centreline;
86-
c) ML RWY 34 arrivals from overhead EN;
87-
d) EN arrivals from ML TCU inbound via Arrival Gates or as coordinated.
85+
If ML ADC nominates a restriction, and EN ADC determines they **cannot** maintain visual or lateral separation with the YMML traffic, EN ADC must delay the aircraft in their airspace until the separation can be assured.
8886

8987
## Miscellaneous
9088
Traffic in EN ADC airspace shall squawk 0100 unless a discrete code is required.
@@ -95,7 +93,7 @@ EN ADC is responsible for facilitating aircraft requesting city orbits. They sha
9593
`A022` by night
9694

9795
!!! example
98-
**EOG**: "Essendon Tower, EOG, approaching Williamstown, A015, Requesting 1 left-hand city orbit, in receipt of L"
96+
**EOG**: "Essendon Tower, EOG, approaching WMS, A015, Requesting 1 left-hand city orbit, in receipt of L"
9997
**EN ADC**: "EOG, Essendon Tower, cleared 1 left-hand city orbit A015"
10098
**EOG**: "Cleared 1 left-hand city orbit A015, EOG"
10199
*When orbit is complete and aircraft is leaving CTA laterally:*
@@ -140,6 +138,9 @@ When “The Coffin” is released, ML TCU is required to coordinate any use of R
140138
Any Runway change must be prior coordinated to **ML TCU**
141139

142140
### ML ADC
143-
EN ADC must advise ML ADC when “The Coffin” is activated or deactivated.
141+
EN ADC is responsible for separation with all YMML traffic, and must coordinate any aircraft operating in EN ADC airspace that cannot be visually or laterally separated with the 09/27 or 16/34 Extended Centrelines at YMML.
144142

145-
EN ADC must advise ML ADC, for traffic awareness, when an ad hoc airspace release to EN ADC will cause an aircraft to pass within 3 NM of any runway at ML.
143+
!!! example
144+
<span class="hotline">**EN ADC** -> **ML ADC**</span>: "Boundary Ident, OXG, Published Missed Approach from the ILS 26"
145+
<span class="hotline">**ML ADC** -> **EN ADC**</span>: "OXG, My restriction is QFA451 on a 10nm final RWY 34. Your separation"
146+
<span class="hotline">**EN ADC** -> **ML ADC**</span>: "My separation with QFA451, OXG"

‎docs/aerodromes/classc/Melbourne.md

+45-30
Original file line numberDiff line numberDiff line change
@@ -23,35 +23,6 @@ Except when the traffic situation warrants, taxi clearances shall conform to the
2323
## Airspace
2424
ML ADC is not responsible for any airspace by default.
2525

26-
### Sunbury Corridor
27-
**ML ADC** may request a release of the Sunbury Corridor from ML TCU, to facilitate movements of Day VFR Helicopters.
28-
29-
<figure markdown>
30-
![Melbourne TCU Airspace Administration](img/MLTCUairspace.png){ width="500" }
31-
<figcaption>Melbourne TCU Airspace Administration</figcaption>
32-
</figure>
33-
34-
Due to the close proximity of the airspace to the arrival and departure paths at YMML, controllers should be aware of surrounding traffic before issuing a clearance to helicopters.
35-
36-
!!! example
37-
**HM3:** "Melbourne Tower, HM3, approaching SWT, A020, for YMEN via the Sunbury Corridor, request clearance"
38-
**ML ADC:** "HM3, cleared to YMEN, track Sunbury Corridor, not above A020"
39-
**HM3:** "Cleared to YMEN, track Sunbury Corridor, not above A020, HM3"
40-
41-
If necessary, consider issuing a clearance limit for separation or instruct helicopters to report sighting and to maintain own separation with other aircraft. Alternatively, tower controllers can simulate visual separation provided no risk of collision exists and both aircraft remain in sight of the controller at all times.
42-
43-
!!! example
44-
**ML ADC:** "HM3, report sighting a Jetstar A320, 4nm final runway 16"
45-
**HM3:** "Traffic sighted, HM3"
46-
**ML ADC:** "HM3, pass behind that aircraft, maintain own separation, caution wake turbulence"
47-
**HM3:** "Pass behind the A320, maintain own separation, HM3"
48-
49-
Remember to pass traffic information to both aircraft.
50-
51-
!!! example
52-
**ML ADC:** "JST515, traffic is a helicopter, 2nm northwest of the field, tracking for Essendon and maintaining own separation with you, runway 16, cleared to land"
53-
**JST515:** "Runway 16, cleared to land, JST515"
54-
5526
## Runway Modes
5627
If winds are too great, single runway operations may be necessary (eg, Runway 16 for Arrivals and Departures). However, pending wind limitations (Crosswind <20kts, Tailwind <5kts), the following runway modes are to be used
5728

@@ -125,6 +96,42 @@ Whilst this is used to reduce frequency congestion on SMC in the real world, coo
12596

12697
In light of this, the use of this operational info should be avoided.
12798

99+
## Miscellaneous
100+
### Sunbury Corridor
101+
Day VFR Helicopters may request clearance via the **Sunbury Corridor**. It is defined as the corridor 1nm either side of a track from SWT - PWLC - 16/27 Intersection at YMML.
102+
103+
<figure markdown>
104+
![Sunbury Corridor](img/sunburycorridor.png){ width="700" }
105+
<figcaption>Sunbury Corridor</figcaption>
106+
</figure>
107+
108+
Boundary Coordination must be completed to ML TCU for clearances in this airspace
109+
110+
!!! example
111+
<span class="hotline">**ML ADC** -> **ML TCU**</span>: "For Ident, HM3, Sunbury Corridor, not above A020"
112+
<span class="hotline">**ML TCU** -> **ML ADC**</span>: "HM3, No Restrictions"
113+
114+
Due to the close proximity of the airspace to the arrival and departure paths at YMML, controllers should be aware of surrounding traffic before issuing a clearance to helicopters.
115+
116+
!!! example
117+
**HM3:** "Melbourne Tower, HM3, approaching SWT, A020, for YMEN via the Sunbury Corridor, request clearance"
118+
**ML ADC:** "HM3, cleared to YMEN, track Sunbury Corridor, not above A020"
119+
**HM3:** "Cleared to YMEN, track Sunbury Corridor, not above A020, HM3"
120+
121+
If necessary, consider issuing a clearance limit for separation or instruct helicopters to report sighting and to maintain own separation with other aircraft. Alternatively, tower controllers can simulate visual separation provided no risk of collision exists and both aircraft remain in sight of the controller at all times.
122+
123+
!!! example
124+
**ML ADC:** "HM3, report sighting a Jetstar A320, 4nm final runway 16"
125+
**HM3:** "Traffic sighted, HM3"
126+
**ML ADC:** "HM3, pass behind that aircraft, maintain own separation, caution wake turbulence"
127+
**HM3:** "Pass behind the A320, maintain own separation, HM3"
128+
129+
Remember to pass traffic information to both aircraft.
130+
131+
!!! example
132+
**ML ADC:** "JST515, traffic is a helicopter, 2nm northwest of the field, tracking for Essendon and maintaining own separation with you, runway 16, cleared to land"
133+
**JST515:** "Runway 16, cleared to land, JST515"
134+
128135
## Coordination
129136
### Auto Release
130137
!!! important
@@ -171,4 +178,12 @@ The following Standard Assignable Headings may be used for aircraft assigned the
171178
Any runway change must be prior coordinated to **MAE** and **EN ADC**.
172179

173180
### Departures Controller
174-
Refer to [Melbourne TCU Airspace Division](../../../terminal/melbourne/#airspace-division) for information on airspace divisions when **MDN** and/or **MDS** are online.
181+
Refer to [Melbourne TCU Airspace Division](../../../terminal/melbourne/#airspace-division) for information on airspace divisions when **MDN** and/or **MDS** are online.
182+
183+
### EN ADC
184+
EN ADC is responsible for separation with all YMML traffic, and will coordinate any aircraft operating in EN ADC airspace that cannot be visually or laterally separated with YMML traffic.
185+
186+
!!! example
187+
<span class="hotline">**EN ADC** -> **ML ADC**</span>: "Boundary Ident, OXG, Published Missed Approach from the ILS 26"
188+
<span class="hotline">**ML ADC** -> **EN ADC**</span>: "OXG, My restriction is QFA451 on a 10nm final RWY 34. Your separation"
189+
<span class="hotline">**EN ADC** -> **ML ADC**</span>: "My separation with QFA451, OXG"

‎docs/aerodromes/classc/img/enadc.png

65.2 KB
Loading

‎docs/aerodromes/classc/img/sunburycorridor.png

74.4 KB
Loading

‎docs/controller-skills/milkrun.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The job of the ACD controller during Milk Run is a fairly straight-forward one,
1212
Ensure that all flight plans are correct, nothing like `DOSEL DCT RIVET`, `GPS DIRECT`, or anything else unusual like that, just stick to the pre-approved Jet and Non-Jet routes. This helps reduce workload on Enroute controllers down the line.
1313

1414
### 16 Off Mode Departures at YMML
15-
A Reminder that [Off Mode Departures from Runway 16](../../aerodromes/classc/Melbourne/#off-mode-departures) during the 16A27D Runway Mode must be assigned the **ISPEG** SID, **NOT** the DOSEL SID. The **ISPEG** SID deconflicts concurrent 16 and 27 departures, whereas the DOSEL SID does not.
15+
A Reminder that [Off Mode Departures from Runway 16](../../aerodromes/classc/Melbourne/#off-mode-departures) to the North East and North West during the 16A27D Runway Mode must be assigned the **ISPEG** SID, **NOT** the DOSEL SID. The **ISPEG** SID deconflicts concurrent 16 and 27 departures, whereas the DOSEL SID does not.
1616

1717
## SMC
1818
### Standard Taxi Routes

‎docs/terminal/brisbane.md

+24-24
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,30 @@ See also: [CG ADC Offline](#cg-adc-offline).
3434
### Airspace Structural Arrangements
3535
Pursuant to Section 3 of the [VATPAC Air Traffic Services Policy](https://cdn.vatpac.org/documents/policy/Controller+Positions+and+Ratings+Policy+v5.2.pdf), **“North”**/**”West”** positions shall assume the airspace of corresponding **“South”**/**”East”** positions when the latter are inactive (e.g. **BAN** assumes **BAS** airspace), and vice versa.
3636

37+
### Airspace Division
38+
The divisions of the airspace between **BAN**, **BAS**, **BDS**, **BDN**, and **BAC** change based on the Runway Mode.
39+
40+
!!! note
41+
The following diagrams do not include non BN TCU areas of responsibility such as AF CTR or CG ADC
42+
43+
#### 01 PROPS
44+
<figure markdown>
45+
![01 PROPS TCU Structure](img/bn01props.png){ width="700" }
46+
<figcaption>01 PROPS TCU Structure</figcaption>
47+
</figure>
48+
49+
#### 19 PROPS
50+
<figure markdown>
51+
![19 PROPS TCU Structure](img/bn19props.png){ width="700" }
52+
<figcaption>19 PROPS TCU Structure</figcaption>
53+
</figure>
54+
55+
#### SODPROPS
56+
<figure markdown>
57+
![SODPROPS TCU Structure](img/bnsodprops.png){ width="700" }
58+
<figcaption>SODPROPS TCU Structure</figcaption>
59+
</figure>
60+
3761
## Parallel Runway Operations
3862
Refer to [Parallel Runway Separation Standards](../../separation-standards/parallelapps) for more information
3963
### Runway Selection
@@ -80,30 +104,6 @@ Due to the low level of CTA (`A035`) in the CG CTR when **CG ADC** is offline, i
80104
**BN TCU**: "JST446, Cleared to YSSY via APAGI, Flight Planned Route. Climb to A060"
81105
**JST446**: "Cleared to YSSY via APAGI, Flight Planned Route. Climb to A060, JST446"
82106

83-
## Airspace Division
84-
The divisions of the airspace between **BAN**, **BAS**, **BDS**, **BDN**, and **BAC** change based on the Runway Mode.
85-
86-
!!! note
87-
The following diagrams do not include non BN TCU areas of responsibility such as AF CTR or CG ADC
88-
89-
### 01 PROPS
90-
<figure markdown>
91-
![01 PROPS TCU Structure](img/bn01props.png){ width="700" }
92-
<figcaption>01 PROPS TCU Structure</figcaption>
93-
</figure>
94-
95-
### 19 PROPS
96-
<figure markdown>
97-
![19 PROPS TCU Structure](img/bn19props.png){ width="700" }
98-
<figcaption>19 PROPS TCU Structure</figcaption>
99-
</figure>
100-
101-
### SODPROPS
102-
<figure markdown>
103-
![SODPROPS TCU Structure](img/bnsodprops.png){ width="700" }
104-
<figcaption>SODPROPS TCU Structure</figcaption>
105-
</figure>
106-
107107
## Coordination
108108
### Enroute
109109
#### Departures

‎docs/terminal/coral.md

+1
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ MKA may extend to RKA and vice versa, callsigns remain the same. See [Controller
2424
<figure markdown>
2525
![Coral Combined Airspace](img/coraltcusetup.png){ width="1000" }
2626
</figure>
27+
2728
## Coordination
2829

2930
### Enroute

‎docs/terminal/darwin.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ DN TCU is also responsible for Active Restricted Area R264 A-K and R230 A-F
2121

2222
DAW may request DN TCU (`SFC`–`F240`) from TRT to facilitate military transits to/from R264 A-K and R230 A-F
2323

24+
### Airspace Division
2425
When both DN TCU positions are opened, DN TCU is split east and west along the runway 18/36 extended centreline. DAW owns the airspace to the west of the line and DAE owns the airspace to the east of the line
2526

2627
<figure markdown>
@@ -29,7 +30,6 @@ When both DN TCU positions are opened, DN TCU is split east and west along the r
2930
</figure>
3031

3132
### ADC
32-
3333
ADC owns the airspace within the DN CTR (`SFC`–`A010`). This airspace is designed to facilitate the processing of helicopter scenic flights and low-level helicopter circuits.
3434
The CTR extends 7NM from the thresholds of runways 11 and 29 but does not including the Robertson Barracks transit zone.
3535

‎docs/terminal/img/16PROPS.png

268 KB
Loading

‎docs/terminal/img/enadc.png

65.2 KB
Loading

‎docs/terminal/melbourne.md

+42-49
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,6 @@
1717

1818
## Airspace
1919
The Vertical limits of the ML TCU are `SFC` to `F245`.
20-
ML TCU is responsible for the Melbourne TCU, except:
21-
a) The Sunbury Corridor, when **ML ADC** is online
22-
b) The South East Quadrant, when **EN ADC** is online
23-
c) The Coffin, when **EN ADC** is online, and the airspace has been released to **EN ADC**
24-
25-
<figure markdown>
26-
![Melbourne TCU Airspace Administration](img/MLTCUairspace.png){ width="500" }
27-
<figcaption>Melbourne TCU Airspace Administration</figcaption>
28-
</figure>
29-
30-
!!! note
31-
The released airspace of the Sunbury Corridor and South East Quadrant is only from the lower level of CTA. ML TCU still owns the Class G airspace beneath it.
3220

3321
### Reclassifications
3422
#### MB CTR
@@ -41,6 +29,42 @@ AV CTR Class D `SFC` to `A007` reverts to Class G and `A007` to `A025` to Class
4129

4230
See also: [AV ADC Offline](#av-adc-offline).
4331

32+
### Airspace Division
33+
The divisions of the airspace between **MAE**, **MDN**, and **MDS** change based on the Runway Mode.
34+
35+
!!! note
36+
The following diagrams do not include non ML TCU areas of responsibility such as MB CTR or AV ADC
37+
38+
#### 09
39+
<figure markdown>
40+
![09 TCU Structure](img/ML09annotated.png){ width="700" }
41+
<figcaption>09 TCU Structure</figcaption>
42+
</figure>
43+
44+
#### 09A16D
45+
<figure markdown>
46+
![09A16D TCU Structure](img/ML09A16Dannotated.png){ width="700" }
47+
<figcaption>09A16D TCU Structure</figcaption>
48+
</figure>
49+
50+
#### 16 / 16A27D
51+
<figure markdown>
52+
![16 / 16A27D TCU Structure](img/ML16annotated.png){ width="700" }
53+
<figcaption>16 / 16A27D TCU Structure</figcaption>
54+
</figure>
55+
56+
#### 27 / 27AD34D
57+
<figure markdown>
58+
![27 / 27AD34D TCU Structure](img/ML27annotated.png){ width="700" }
59+
<figcaption>27 / 27AD34D TCU Structure</figcaption>
60+
</figure>
61+
62+
#### 34
63+
<figure markdown>
64+
![34 TCU Structure](img/ML34annotated.png){ width="700" }
65+
<figcaption>34 TCU Structure</figcaption>
66+
</figure>
67+
4468
## Departure Procedures
4569
### ML (RADAR) SID
4670
The **ML (RADAR) SID** is used for all non-jet IFR departures (and certain jet aircraft) from YMML. Unlike at other aerodromes, **ML ADC** does *not* need to coordinate these departures with a 'Next' call, provided they are assigned the standard assignable level and a [Standard Assignable Heading](#standard-assignable-headings).
@@ -158,42 +182,6 @@ Due to the low level of CTA surrounding YMMB, it is best practice to give airway
158182
**ML TCU:** "AAC, cleared to YBLT via SAMIG, flight planned route, climb to A040"
159183
**AAC:** "Cleared to YBLT via SAMIG, flight planned route, climb to A040, AAC"
160184

161-
## Airspace Division
162-
The divisions of the airspace between **MAE**, **MDN**, and **MDS** change based on the Runway Mode.
163-
164-
!!! note
165-
The following diagrams do not include non ML TCU areas of responsibility such as MB CTR or AV ADC
166-
167-
### 09
168-
<figure markdown>
169-
![09 TCU Structure](img/ML09annotated.png){ width="700" }
170-
<figcaption>09 TCU Structure</figcaption>
171-
</figure>
172-
173-
### 09A16D
174-
<figure markdown>
175-
![09A16D TCU Structure](img/ML09A16Dannotated.png){ width="700" }
176-
<figcaption>09A16D TCU Structure</figcaption>
177-
</figure>
178-
179-
### 16 / 16A27D
180-
<figure markdown>
181-
![16 / 16A27D TCU Structure](img/ML16annotated.png){ width="700" }
182-
<figcaption>16 / 16A27D TCU Structure</figcaption>
183-
</figure>
184-
185-
### 27 / 27AD34D
186-
<figure markdown>
187-
![27 / 27AD34D TCU Structure](img/ML27annotated.png){ width="700" }
188-
<figcaption>27 / 27AD34D TCU Structure</figcaption>
189-
</figure>
190-
191-
### 34
192-
<figure markdown>
193-
![34 TCU Structure](img/ML34annotated.png){ width="700" }
194-
<figcaption>34 TCU Structure</figcaption>
195-
</figure>
196-
197185
## Coordination
198186

199187
### Enroute
@@ -242,7 +230,12 @@ The following Standard Assignable Headings may be used for aircraft assigned the
242230

243231
### EN ADC
244232
#### Airspace
245-
EN ADC is responsible for the Class C airspace in the "Coffin" `SFC` to `A015`, and in the "South East Quadrant" `SFC` to `A020`.
233+
EN ADC is responsible for the Class C airspace shown below, `SFC` to `A020`.
234+
235+
<figure markdown>
236+
![EN ADC Airspace](img/enadc.png){ width="700" }
237+
<figcaption>EN ADC Airspace</figcaption>
238+
</figure>
246239

247240
#### Start Clearance
248241
When an aircraft requests start clearance, the EN SMC controller shall coordinate with ML TCU to obtain the start clearance.

‎docs/terminal/perth.md

+18-18
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,24 @@ JT CTR reverts to Class G when **JT ADC** is offline, and is administered by the
2626

2727
See also: [JT ADC Offline](#jtpea-adc-offline).
2828

29+
### Airspace Division
30+
The divisions of the airspace between **PHA**, and **PHD** change based on the Runway Mode.
31+
32+
!!! note
33+
The following diagrams do not include non PH TCU areas of responsibility such as JT CTR or PEA APP
34+
35+
#### 03/06
36+
<figure markdown>
37+
![03/06 TCU Structure](img/PH0306annotated.png){ width="700" }
38+
<figcaption>03/06 TCU Structure</figcaption>
39+
</figure>
40+
41+
#### 21/24
42+
<figure markdown>
43+
![21/24 TCU Structure](img/PH2124annotated.png){ width="700" }
44+
<figcaption>21/24 TCU Structure</figcaption>
45+
</figure>
46+
2947
## Runway Modes
3048
Generally, YPPH operates on either the Southwest or Northeast runway plan, as below. Where strong winds dictate the use of only a single runway, this shall be nominated in the ATIS.
3149

@@ -98,24 +116,6 @@ Aircraft departing the TMA to the south planned at `F130` or above will likely l
98116
**PHD**: "RXA2125, leave and re-enter controlled airspace on climb to F180, no reported IFR traffic"
99117
**RXA2125**: "Leave and re-enter controlled airspace on climb to F180, RXA2125"
100118

101-
## Airspace Division
102-
The divisions of the airspace between **PHA**, and **PHD** change based on the Runway Mode.
103-
104-
!!! note
105-
The following diagrams do not include non PH TCU areas of responsibility such as JT CTR or PEA APP
106-
107-
### 03/06
108-
<figure markdown>
109-
![03/06 TCU Structure](img/PH0306annotated.png){ width="700" }
110-
<figcaption>03/06 TCU Structure</figcaption>
111-
</figure>
112-
113-
### 21/24
114-
<figure markdown>
115-
![21/24 TCU Structure](img/PH2124annotated.png){ width="700" }
116-
<figcaption>21/24 TCU Structure</figcaption>
117-
</figure>
118-
119119
## Coordination
120120

121121
### Enroute

‎docs/terminal/sydney.md

+42-42
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,48 @@ SRI is responsible for the provision of FIS in Class G airspace within the SY TM
5959
!!! example
6060
During a busy event, Sydney Departures is experiencing a high workload and wishes to delegate the SRI role to another TMA controller who isn't as busy. SAN's sector is quiet, so they elect to perform the role.
6161

62+
### Airspace Division
63+
The divisions of the airspace between **SAN**, **SAS**, **SDS**, **SDN**, **SFW** and **SFE** change based on the Runway Mode.
64+
65+
!!! note
66+
The following diagrams do not include non SY TCU areas of responsibility such as BK CTR or CN CTR
67+
68+
#### Side Profile
69+
<figure markdown>
70+
![SY TCU Side Profile](img/syside.png){ width="700" }
71+
<figcaption>SY TCU Side Profile</figcaption>
72+
</figure>
73+
74+
#### 07
75+
<figure markdown>
76+
![07 TCU Structure](img/sy07.png){ width="700" }
77+
<figcaption>07 TCU Structure</figcaption>
78+
</figure>
79+
80+
#### 16 PROPS
81+
<figure markdown>
82+
![16 PROPS TCU Structure](img/sy16PROPS.png){ width="700" }
83+
<figcaption>16 PROPS TCU Structure</figcaption>
84+
</figure>
85+
86+
#### 25
87+
<figure markdown>
88+
![25 TCU Structure](img/sy25.png){ width="700" }
89+
<figcaption>25 TCU Structure</figcaption>
90+
</figure>
91+
92+
#### 34 PROPS
93+
<figure markdown>
94+
![34 PROPS TCU Structure](img/sy34PROPS.png){ width="700" }
95+
<figcaption>34 PROPS TCU Structure</figcaption>
96+
</figure>
97+
98+
#### SODPROPS
99+
<figure markdown>
100+
![SODPROPS TCU Structure](img/sySODPROPS.png){ width="700" }
101+
<figcaption>SODPROPS TCU Structure</figcaption>
102+
</figure>
103+
62104
## Arrival Procedures
63105
### STAR and Runway Assignment
64106
Sequencing of arrivals into YSSY is a joint responsibility of ARL and BIK, with input from SY TCU.
@@ -266,48 +308,6 @@ Due to the low level of CTA (`A015`) in the BK CTR when **BK ADC** is offline, i
266308
**SY TCU**: "LOA, cleared to YSHL via ANKUB, flight planned route, Bankstown 8 Departure, climb via SID A030"
267309
**LOA**: "Cleared to YSHL via ANKUB, flight planned route, Bankstown 8 Departure, climb via SID A030, LOA"
268310

269-
## Airspace Division
270-
The divisions of the airspace between **SAN**, **SAS**, **SDS**, **SDN**, **SFW** and **SFE** change based on the Runway Mode.
271-
272-
!!! note
273-
The following diagrams do not include non SY TCU areas of responsibility such as BK CTR or CN CTR
274-
275-
### Side Profile
276-
<figure markdown>
277-
![SY TCU Side Profile](img/syside.png){ width="700" }
278-
<figcaption>SY TCU Side Profile</figcaption>
279-
</figure>
280-
281-
### 07
282-
<figure markdown>
283-
![07 TCU Structure](img/sy07.png){ width="700" }
284-
<figcaption>07 TCU Structure</figcaption>
285-
</figure>
286-
287-
### 16 PROPS
288-
<figure markdown>
289-
![16 PROPS TCU Structure](img/sy16PROPS.png){ width="700" }
290-
<figcaption>16 PROPS TCU Structure</figcaption>
291-
</figure>
292-
293-
### 25
294-
<figure markdown>
295-
![25 TCU Structure](img/sy25.png){ width="700" }
296-
<figcaption>25 TCU Structure</figcaption>
297-
</figure>
298-
299-
### 34 PROPS
300-
<figure markdown>
301-
![34 PROPS TCU Structure](img/sy34PROPS.png){ width="700" }
302-
<figcaption>34 PROPS TCU Structure</figcaption>
303-
</figure>
304-
305-
### SODPROPS
306-
<figure markdown>
307-
![SODPROPS TCU Structure](img/sySODPROPS.png){ width="700" }
308-
<figcaption>SODPROPS TCU Structure</figcaption>
309-
</figure>
310-
311311
## Coordination
312312
### Enroute
313313
#### Departures

‎includes/abbreviations.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -247,4 +247,7 @@
247247
*[BFL]: Brisbane Flow
248248
*[CSF]: Cairns Flow
249249
*[CBF]: Canberra Flow
250-
*[PFL]: Perth Flow
250+
*[PFL]: Perth Flow
251+
*[PWLC]: Powerline Crossing
252+
*[LUY]: Latrobe University
253+
*[WMS]: Williamstown

0 commit comments

Comments
 (0)
Please sign in to comment.