diff --git a/docs/aerodromes/Albury.md b/docs/aerodromes/Albury.md index c2be4fa54..549201c23 100644 --- a/docs/aerodromes/Albury.md +++ b/docs/aerodromes/Albury.md @@ -20,8 +20,14 @@ Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -AY ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the AY CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm of the aerodrome. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. +Surveillance coverage can be expected to be available at all levels in the AY CTR. Although AY ADC is **not permitted** to use surveillance for separation, ELW(BLA) may assist by establishing surveillance separation standards via coordination + +!!! example + **AY ADC** -> **BLA**: "Can you advise when QLK206D is 5nm clear of DSB?" + **BLA** -> **AY ADC**: "Wilco" + + **BLA** -> **AY ADC**: "QLK206D 5nm clear of DSB" + **AY ADC** -> **BLA**: "QLK206D 5nm clear of DSB, thanks" ## Coordination ### Departures diff --git a/docs/aerodromes/Alice.md b/docs/aerodromes/Alice.md index 3543f39cb..1a7b75f4b 100644 --- a/docs/aerodromes/Alice.md +++ b/docs/aerodromes/Alice.md @@ -21,8 +21,8 @@ AS ADC is responsible for the Class D airspace `SFC` to `A045`, as well as the C Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -AS TWR is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the AS CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. +Surveillance coverage can be expected to be available at all levels in the AS CTR. Although AS ADC is **not permitted** to use surveillance for separation, ASP may assist by establishing surveillance separation standards via coordination + ## Coordination ### Departures Departures from YBAS in to ASP Class C will be coordinated when ready for departure. diff --git a/docs/aerodromes/Amberley.md b/docs/aerodromes/Amberley.md index 46a4a1361..f39f5bda3 100644 --- a/docs/aerodromes/Amberley.md +++ b/docs/aerodromes/Amberley.md @@ -8,16 +8,16 @@ | Name | Callsign | Frequency | Login Identifier | | ------------------ | -------------- | ---------------- | --------------------------------------| -| Amberley ADC | Amberley Tower | 118.300 | AM_TWR | -| Amberley SMC | Amberley Ground | 129.350 | AM_GND | -| Amberley ACD | Amberley Delivery | 134.600 | AM_DEL | +| Amberley ADC | Amberley Tower | 118.300 | AMB_TWR | +| Amberley SMC | Amberley Ground | 129.350 | AMB_GND | +| Amberley ACD | Amberley Delivery | 134.600 | AMB_DEL | | Amberley ATIS | | 123.300 | YAMB_ATIS | ## Airspace -AM ADC owns the Class C airspace **in the AM CTR** within 10nm of the YAMB ARP from `SFC` to `A015`. This airspace is primarily used for military circuits and initial and pitch approaches. +AMB ADC owns the Class C airspace **in the AMB CTR** within 10nm of the YAMB ARP from `SFC` to `A015`. This airspace is primarily used for military circuits and initial and pitch approaches. ## YAMB Aerodrome @@ -33,11 +33,11 @@ Aircraft will depart the circuit visually and track overhead YAMB to begin track !!! example 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" + **AMB 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 WOLF03 was assiged the BYRON7 departure with their initial clearance. - **AM ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff" + **AMB ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff" **WOLF03**: "Make left turn, reach `F190` by COWIE, cleared for takeoff, WOLF03" | Departure | Initial Constraint | Route | @@ -50,7 +50,7 @@ Aircraft will depart the circuit visually and track overhead YAMB to begin track Charts for the Coded Departures may be in YAMB AD2 Supplements 6.2.25.11 available here: [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new} !!! note - Since the Coded Departures are not SIDs, AM ACD needs to write the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route to include all relevant tracking points. + Since the Coded Departures are not SIDs, AMB ACD needs to write the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route to include all relevant tracking points. ### Runway Operations @@ -73,16 +73,16 @@ The Circuit Area Airspace is allocated to be within 5nm of the YAMB ARP from `SF | 22 | Left | ## Coordination -### AM TCU +### AMB TCU -'Next' coordination is required from AM ADC to AM TCU for all aircraft. +'Next' coordination is required from AMB ADC to AMB TCU for all aircraft. !!! example - **AM ADC** -> **AM TCU**: "Next, ASY01, runway 33" - **AM TCU** -> **AM ADC**: "ASY01, Assigned Heading Right 030, unrestricted" - **AM ADC** -> **AM TCU**: "Assigned Heading Heading Right 030, ASY01" + **AMB ADC** -> **AMB TCU**: "Next, ASY01, runway 33" + **AMB TCU** -> **AMB ADC**: "ASY01, Assigned Heading Right 030, unrestricted" + **AMB ADC** -> **AMB TCU**: "Assigned Heading Heading Right 030, ASY01" ### Level Assignment -The Standard Assignable Level from **AM ADC** to **AM TCU** is: +The Standard Assignable Level from **AMB ADC** to **AMB 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. diff --git a/docs/aerodromes/Broome.md b/docs/aerodromes/Broome.md index 26f9aad79..32be4c16d 100644 --- a/docs/aerodromes/Broome.md +++ b/docs/aerodromes/Broome.md @@ -20,8 +20,8 @@ Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -BRM ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the BRM CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. +Surveillance coverage can be expected to be available at all levels in the BRM CTR. Although BRM ADC is **not permitted** to use surveillance for separation, TRT(KIY) may assist by establishing surveillance separation standards via coordination + ## Coordination ### Departures A 'next' call is made for all aircraft when they are next to depart. BRM ADC must inform TRT(KIY) if the aircraft does not depart within **2 minutes** of the next call. diff --git a/docs/aerodromes/Cairns.md b/docs/aerodromes/Cairns.md index 97695fa9a..6497a0caa 100644 --- a/docs/aerodromes/Cairns.md +++ b/docs/aerodromes/Cairns.md @@ -123,7 +123,7 @@ ACFT planning to enter the CS CTR between: *Mt Gorton*, CGF and Upolo Cay at `A0 ## ATIS ### Approach Types -**Approach Expectation shall be `Expect Instrument Approach` when:** +**Approach Expectation shall be `EXP INST APCH` when:** | Time | Runway 15 | Runway 33 | | ------| -------------- | -------------------------------------| @@ -166,4 +166,4 @@ b) Aircraft using a runway not on the ATIS ### CS FLW FLW must advise ADC of any sequence changes within 36 Miles CS. -All requests for non-duty runway arrivals must be approved by ADC. \ No newline at end of file +All requests for non-duty runway arrivals must be approved by ADC. diff --git a/docs/aerodromes/Coffs.md b/docs/aerodromes/Coffs.md index 3fc61fd7a..56134c2e4 100644 --- a/docs/aerodromes/Coffs.md +++ b/docs/aerodromes/Coffs.md @@ -19,17 +19,7 @@ Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -CFS ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be not available below `A028` in the CFS CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. - -CFS ADC must establish a [Procedural Standard](../../controller-skills/classdtwr/#standards) prior to losing surveillance identification of an aircraft. - -!!! caution - A procedural and/or visual standard **must** be put in place for all aircraft below `A028`. -## Instrument Approaches -Only one aircraft is permitted to conduct an instrument approach at any time, due to limited surveillance coverage. CFS ADC must ensure that all aircraft are procedurally separated from any portion of an instrument approach and missed approach that is conducted below `A028`. - -If required, CFS ADC can pass amended tracking/level instructions to an aircraft for a missed approach for separation purposes, as long as the aircraft can be issued **uninterrupted climb** to the LSALT/MSA once identified. +Surveillance coverage can be expected to be not available below `A028` in the CFS CTR. Although CFS ADC is **not permitted** to use surveillance for separation, ARL(MNN) or INL may assist by establishing surveillance separation standards via coordination ## Coordination ### Departures diff --git a/docs/aerodromes/Curtin.md b/docs/aerodromes/Curtin.md new file mode 100644 index 000000000..2586e593f --- /dev/null +++ b/docs/aerodromes/Curtin.md @@ -0,0 +1,46 @@ +--- + title: Curtin (YCIN) +--- + +--8<-- "includes/abbreviations.md" + +## Positions + +| Name | Callsign | Frequency | Login Identifier | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| Curtin ADC | Curtin Tower | 118.300 | CIN_TWR | +| Curtin SMC | Curtin Ground | 126.200 | CIN_GND | +| Curtin ACD | Curtin Delivery | 136.800 | CIN_DEL | +| Curtin ATIS | | 134.800 | YCIN_ATIS | + +## Airspace +CIN ADC owns the Class C airspace **within the CIN CTR** from `SFC` to `A035`. + +## Surveillance +Surveillance coverage can be expected to be available at all levels in the CIN CTR. Although CIN ADC is **not permitted** to use surveillance for separation, CIN TCU or TRT(KIY) may assist by establishing surveillance separation standards via coordination + +## Circuit Direction + +| Runway | Direction | +| ------ | ----------| +| 29 | Left | +| 11 | Right | + +## Coordination +### CIN TCU +'Next' coordination is required from CIN ADC to CIN TCU for all aircraft. + +!!! example + **CIN ADC** -> **CIN TCU**: "Next, ASY404, runway 29" + **CIN TCU** -> **CIN ADC**: "ASY404, unrestricted" + **CIN ADC** -> **CIN TCU**: "ASY404" + +The Standard Assignable Level from **CIN ADC** to **CIN TCU** is the Lower of `F190` or the `RFL`. + +### TRT(KIY) +When CIN TCU is offline, coordination is not required between CIN ADC and TRT(KIY). Aircraft entering TRT(KIY) airspace shall be handed off, and instructed to contact TRT(KIY) for onwards clearance. + +## 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} + diff --git a/docs/aerodromes/Hammo.md b/docs/aerodromes/Hammo.md index 53644168a..e81d2c24c 100644 --- a/docs/aerodromes/Hammo.md +++ b/docs/aerodromes/Hammo.md @@ -23,18 +23,7 @@ HM ADC is responsible for the Class D airspace in the HM CTR, `SFC` to `A045`. Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -HM ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be not available below `A031` in the HM CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. - -HM ADC must establish a [Procedural Standard](../../controller-skills/classdtwr/#standards) prior to losing surveillance identification of an aircraft. - -!!! caution - A procedural and/or visual standard **must** be put in place for all aircraft below `A031`. - -## Instrument Approaches -Only one aircraft is permitted to conduct an instrument approach at any time, due to limited surveillance coverage. HM ADC must ensure that all aircraft are procedurally separated from any portion of an instrument approach and missed approach that is conducted below `A031`. - -If required, HM ADC can pass amended tracking/level instructions to an aircraft for a missed approach for separation purposes, as long as the aircraft can be issued **uninterrupted climb** to the LSALT/MSA once identified. +Surveillance coverage can be expected to be not available below `A031` in the HM CTR. Although HM ADC is **not permitted** to use surveillance for separation, KEN(SWY) may assist by establishing surveillance separation standards via coordination ## Coordination ### Departures diff --git a/docs/aerodromes/Karratha.md b/docs/aerodromes/Karratha.md index d8eed86f1..20a2ac269 100644 --- a/docs/aerodromes/Karratha.md +++ b/docs/aerodromes/Karratha.md @@ -21,8 +21,8 @@ Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -KA ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the KA CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. +Surveillance coverage can be expected to be available at all levels in the KA CTR. Although KA ADC is **not permitted** to use surveillance for separation, OLW may assist by establishing surveillance separation standards via coordination + ## Coordination ### Departures A 'next' call is made for all aircraft when they are next to depart. KA ADC must inform OLW if the aircraft does not depart within **2 minutes** of the next call. diff --git a/docs/aerodromes/Learmonth.md b/docs/aerodromes/Learmonth.md new file mode 100644 index 000000000..2ce016b6f --- /dev/null +++ b/docs/aerodromes/Learmonth.md @@ -0,0 +1,44 @@ +--- + title: Learmonth (YPLM) +--- + +--8<-- "includes/abbreviations.md" + +## Positions + +| Name | Callsign | Frequency | Login Identifier | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| Learmonth ADC | Learmonth Tower | 118.300 | LM_TWR | +| Learmonth SMC | Learmonth Ground | 126.200 | LM_GND | +| Learmonth ATIS | | 123.300 | YPLM_ATIS | + +## Airspace +LM ADC owns the Class C airspace **within the LM CTR** from `SFC` to `A025`. + +## Surveillance +Surveillance coverage can be expected to be available at all levels in the LM CTR. Although LM ADC is **not permitted** to use surveillance for separation, LM TCU or OLW may assist by establishing surveillance separation standards via coordination + +## Circuit Direction + +| Runway | Direction | +| ------ | ----------| +| 36 | Right | +| 18 | Left | + +## Coordination +### LM TCU +'Next' coordination is required from LM ADC to LM TCU for all aircraft. + +!!! example + **LM ADC** -> **LM TCU**: "Next, QFA1601, runway 36" + **LM TCU** -> **LM ADC**: "QFA1601, Right heading 060 Visual, unrestricted" + **LM ADC** -> **LM TCU**: "Right heading 060 Visual, QFA1601" + +The Standard Assignable Level from **LM ADC** to **LM TCU** is the Lower of `F270` or the `RFL`. + +### OLW +When LM TCU is offline, coordination is not required between LM ADC and OLW. Aircraft entering OLW airspace shall be handed off, and instructed to contact OLW for onwards clearance. + +## 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} \ No newline at end of file diff --git a/docs/aerodromes/Mackay.md b/docs/aerodromes/Mackay.md index 4d9ebe1d2..04593f1be 100644 --- a/docs/aerodromes/Mackay.md +++ b/docs/aerodromes/Mackay.md @@ -20,9 +20,6 @@ MK ADC is responsible for the Class D airspace in the MK CTR `SFC` to `A010`. Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. -## Surveillance -MK ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the MK CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. ## Coordination ### Departures A 'next' call is made for all aircraft when they are next to depart. MK ADC must inform KEN(SWY) if the aircraft does not depart within **2 minutes** of the next call. diff --git a/docs/aerodromes/Melbourne.md b/docs/aerodromes/Melbourne.md index 9e87085bf..9173a0025 100644 --- a/docs/aerodromes/Melbourne.md +++ b/docs/aerodromes/Melbourne.md @@ -34,17 +34,17 @@ ML ADC is not responsible for any airspace by default. 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. !!! example - **HEMS3:** "Melbourne Tower, HEMS3, approaching SWT, A020, for YMEN via the Sunbury Corridor, request clearance" - **ML ADC:** "HEMS3, cleared to YMEN, track Sunbury Corridor, not above A020" - **HEMS3:** "Cleared to YMEN, track Sunbury Corridor, not above A020, HEMS3" + **HM3:** "Melbourne Tower, HM3, approaching SWT, A020, for YMEN via the Sunbury Corridor, request clearance" + **ML ADC:** "HM3, cleared to YMEN, track Sunbury Corridor, not above A020" + **HM3:** "Cleared to YMEN, track Sunbury Corridor, not above A020, HM3" 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. !!! example - **ML ADC:** "HEMS3, report sighting a Jetstar A320, 4nm final runway 16" - **HEMS3:** "Traffic sighted, HEMS3" - **ML ADC:** "HEMS3, pass behind that aircraft, maintain own separation, caution wake turbulence" - **HEMS3:** "Pass behind the A320, maintain own separation, HEMS3" + **ML ADC:** "HM3, report sighting a Jetstar A320, 4nm final runway 16" + **HM3:** "Traffic sighted, HM3" + **ML ADC:** "HM3, pass behind that aircraft, maintain own separation, caution wake turbulence" + **HM3:** "Pass behind the A320, maintain own separation, HM3" Remember to pass traffic information to both aircraft. diff --git a/docs/aerodromes/Rockhampton.md b/docs/aerodromes/Rockhampton.md index 02180e021..84c54b272 100644 --- a/docs/aerodromes/Rockhampton.md +++ b/docs/aerodromes/Rockhampton.md @@ -21,9 +21,6 @@ RK ADC is responsible for the Class D airspace in the RK CTR `SFC` to `A010`. Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. -## Surveillance -RK ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the RK CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. ## Coordination ### Departures A 'next' call is made for all aircraft when they are next to depart. RK ADC must inform rka if the aircraft does not depart within **2 minutes** of the next call. diff --git a/docs/aerodromes/Scherger.md b/docs/aerodromes/Scherger.md new file mode 100644 index 000000000..dc0065ce9 --- /dev/null +++ b/docs/aerodromes/Scherger.md @@ -0,0 +1,43 @@ +--- + title: Scherger (YBSG) +--- + +--8<-- "includes/abbreviations.md" + +## Positions + +| Name | Callsign | Frequency | Login Identifier | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| Scherger ADC | Scherger Tower | 118.300 | SG_TWR | +| Scherger SMC | Scherger Ground | 126.200 | SG_GND | +| Scherger ATIS | | 134.800 | YBSG_ATIS | + +## Airspace +SG ADC owns the Class C airspace **within the SG CTR** from `SFC` to `A040`. + +## Surveillance +Surveillance coverage can be expected to be available at all levels in the SG CTR. Although SG ADC is **not permitted** to use surveillance for separation, SG TCU or ISA(ARA) may assist by establishing surveillance separation standards via coordination + +## Circuit Direction +| Runway | Direction | +| ------ | ----------| +| 30 | Right | +| 12 | Left | + +## Coordination +### SG TCU +'Next' coordination is required from SG ADC to SG TCU for all aircraft. + +!!! example + **SG ADC** -> **SG TCU**: "Next, ASY219, runway 30" + **SG TCU** -> **SG ADC**: "ASY219, unrestricted" + **SG ADC** -> **SG TCU**: "ASY219" + +The Standard Assignable Level from **SG ADC** to **SG TCU** is the lower of `F240` or the `RFL`. + +### ISA(ARA) +When SG TCU is offline, coordination is not required between SG ADC and ISA(ARA). Aircraft entering ISA(ARA) airspace shall be handed off, and instructed to contact ISA(ARA) for onwards clearance. + +## 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} \ No newline at end of file diff --git a/docs/aerodromes/Sunshinecoast.md b/docs/aerodromes/Sunshinecoast.md index 85c14f33f..094370830 100644 --- a/docs/aerodromes/Sunshinecoast.md +++ b/docs/aerodromes/Sunshinecoast.md @@ -21,20 +21,11 @@ Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -SU ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be not available below `A012` in the SU CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within the `SFC` to `A045` Class D step (7nm from RWY thresholds). Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. +Surveillance coverage can be expected to be not available below `A012` in the SU CTR. Although SU ADC is **not permitted** to use surveillance for separation, INL(NSA) may assist by establishing surveillance separation standards via coordination -SU ADC must establish a [Procedural Standard](../../controller-skills/classdtwr/#standards) prior to losing surveillance identification of an aircraft. - -!!! caution - A procedural and/or visual standard **must** be put in place for all aircraft below `A012`. - -## Instrument Approaches -Only one aircraft is permitted to conduct an instrument approach at any time, due to limited surveillance coverage. SU ADC must ensure that all aircraft are procedurally separated from any portion of an instrument approach and missed approach that is conducted below `A012`. - -If required, SU ADC can pass amended tracking/level instructions to an aircraft for a missed approach for separation purposes, as long as the aircraft can be issued **uninterrupted climb** to the LSALT/MSA once identified. ## Runway Configuration Pilots with old simulators/scenery may not have the newer Runway 13/31 config (replacing the old 18/36 config). If a pilot reports this to be the case, try to facilitate their flight as best as possible, whilst giving them lower priority to other traffic. Coordinate as you deem necessary with adjacent units. + ## SID Selection Jet Aircraft planned via **MOOLO** or **TAPET**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint, unless the pilot indicates they are unable to accept a Procedural SID. diff --git a/docs/aerodromes/Tamworth.md b/docs/aerodromes/Tamworth.md index 39796c370..554d9d406 100644 --- a/docs/aerodromes/Tamworth.md +++ b/docs/aerodromes/Tamworth.md @@ -23,18 +23,7 @@ TW ADC is responsible for the Class D airspace in the TW CTR, as well as the Cla Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. ## Surveillance -TW ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be not available below `A034` in the TW CTR. -For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base. - -TW ADC must establish a [Procedural Standard](../../controller-skills/classdtwr/#standards) prior to losing surveillance identification of an aircraft. - -!!! caution - A procedural and/or visual standard **must** be put in place for all aircraft below `A034`. - -## Instrument Approaches -Only one aircraft is permitted to conduct an instrument approach at any time, due to limited surveillance coverage. TW ADC must ensure that all aircraft are procedurally separated from any portion of an instrument approach and missed approach that is conducted below `A034`. - -If required, TW ADC can pass amended tracking/level instructions to an aircraft for a missed approach for separation purposes, as long as the aircraft can be issued **uninterrupted climb** to the LSALT/MSA once identified. +Surveillance coverage can be expected to be not available below `A034` in the TW CTR. Although TW ADC is **not permitted** to use surveillance for separation, ARL/MDE may assist by establishing surveillance separation standards via coordination ## Local Lateral Separation Points diff --git a/docs/aerodromes/Woomera.md b/docs/aerodromes/Woomera.md new file mode 100644 index 000000000..cb96be8fd --- /dev/null +++ b/docs/aerodromes/Woomera.md @@ -0,0 +1,28 @@ +--- + title: Woomera (YPWR) +--- + +--8<-- "includes/abbreviations.md" + +## Positions + +| Name | Callsign | Frequency | Login Identifier | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| Woomera ADC | Woomera Tower | 118.300 | WR_TWR | +| Woomera ATIS | | 118.100 | YPWR_ATIS | + +## Airspace +By default, WR ADC owns the **R222F** Restricted Area. This airspace has vertical limits of `SFC` to `F120`. When WR ADC is active, this airspace is classified as Class D. + +Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information. + +## Surveillance +Surveillance coverage can be expected to be available at all levels in the WR CTR. Although WR ADC is **not permitted** to use surveillance for separation, ASP(WRA) may assist by establishing surveillance separation standards via coordination + +## Coordination +### ASP(WRA) +Coordination is not required between WR ADC and ASP(WRA). Aircraft entering ASP(WRA) airspace shall be handed off, and instructed to contact ASP(WRA) for onwards clearance. + +## 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} \ No newline at end of file diff --git a/docs/controller-skills/callsigns.md b/docs/controller-skills/callsigns.md index 58fefedfe..0dc559eb1 100644 --- a/docs/controller-skills/callsigns.md +++ b/docs/controller-skills/callsigns.md @@ -23,7 +23,7 @@ This page lists some of the most commonly used callsigns in Australia. | BNZ | BONZA | | CFH | CAREFLIGHT | | FD | FLYDOC | -| HM | HEMS | +| HM | HM | | HND | HINTERLAND | | JTE | JETEX | | JST | JETSTAR | @@ -64,6 +64,7 @@ This page lists some of the most commonly used callsigns in Australia. | AZG | SILK WEST | Azerbaijan | | BAV | BAMBOO | Vietnam | | BAW | SPEEDBIRD | United Kingdom | +| BTK | BATIK | Indonesia | | CBJ | CAPITAL JET | China | | CCA | AIR CHINA | China | | CEB | CEBU | Philippines | @@ -73,7 +74,7 @@ This page lists some of the most commonly used callsigns in Australia. | CSN | CHINA SOUTHERN | China | | CXA | XIAMEN AIR | China | | DAL | DELTA | United States | -| DLH | Lufthansa | Germany | +| DLH | LUFTHANSA | Germany | | ETD | ETIHAD | United Arab Emirates | | FJI | FIJI | Fiji | | GCR | BOHAI | China | diff --git a/docs/controller-skills/vatsys.md b/docs/controller-skills/vatsys.md index 95e737d81..99f74ae1d 100644 --- a/docs/controller-skills/vatsys.md +++ b/docs/controller-skills/vatsys.md @@ -31,7 +31,7 @@ Strips: **STATE** ### Tools Velocity Vector: **2 MINS** Short Route Probe: **OFF** (Toggled on for non-identified tracks) -History Trails: **OFF** +History Trails: **9** FPASD: **ON** Extended Labels: **ON** ### Info @@ -48,7 +48,7 @@ Strips: **BEACON** ### Windows displayed **ADEP (Towered airports in airspace)** **Other** -**ARRIVAL LIST** (if airport is busy, eg during events) +**ARRIVAL LIST** **All ATISes** in your airspace ### Maps **Dynamic Infill** @@ -59,16 +59,15 @@ Strips: **BEACON** #### Local **XX_COAST** **XX_(RWY CONFIG)** -**XX_(RWY CONFIG)_NAMES** +**XX_RTCC** **XX_TCU** ### Tools Velocity Vector: **1 MIN** Short Route Probe: **OFF** -History Trails: **OFF** +History Trails: **5** FPASD: **ON** Extended Labels: **OFF** (Toggled on for aircraft not arriving at main airport) ### Info -**AREA QNH** **TFMS** (if airport is busy, eg during events) **AIS DISPLAY** for major airports in your airspace @@ -97,7 +96,7 @@ Strips: **BEACON** ### Tools Velocity Vector: **1 MIN** Short Route Probe: **OFF** (Toggled on for non-identified tracks) -History Trails: **OFF** +History Trails: **5** FPASD: **ON** Extended Labels: **OFF** (Toggled on for aircraft not arriving at main airport) ### Info diff --git a/docs/enroute/Brisbane Centre/ARL.md b/docs/enroute/Brisbane Centre/ARL.md index 370d6bd45..ff478aa79 100644 --- a/docs/enroute/Brisbane Centre/ARL.md +++ b/docs/enroute/Brisbane Centre/ARL.md @@ -185,7 +185,7 @@ The Standard Assignable level from MNN to **CFS ADC** is `A080`, any other level Any aircraft that will enter CFS ADC airspace, and not landing at YCFS, must be Heads-up coordinated prior to **5 mins** from the boundary. !!! example - **MNN** -> **CFS ADC**: "via CFS, GNP, Overflier" + **MNN** -> **CFS ADC**: "via CFS, GNP" **CFS ADC** -> **MNN**: "GNP, A030" ### WLM TCU diff --git a/docs/enroute/Brisbane Centre/INL.md b/docs/enroute/Brisbane Centre/INL.md index 18141765f..9cfdf6b86 100644 --- a/docs/enroute/Brisbane Centre/INL.md +++ b/docs/enroute/Brisbane Centre/INL.md @@ -137,7 +137,7 @@ The Standard Assignable level from NSA to **SU ADC** is `A060`, any other level Any aircraft that will enter SU ADC airspace, and not landing at YBSU, must be Heads-up coordinated prior to **5 mins** from the boundary. !!! example - **NSA** -> **SU ADC**: "via HOLIS, CXB, Overflier" + **NSA** -> **SU ADC**: "via HOLIS, CXB" **SU ADC** -> **NSA**: "CXB, A025" ### RKA @@ -176,24 +176,24 @@ Any aircraft that will enter CFS ADC airspace, and not landing at YCFS, must be **INL** -> **CFS ADC**: "via CFS, XFC, Overflier" **CFS ADC** -> **INL**: "XFC, A040" -### OK TCU / AM TCU +### OK TCU / AMB TCU #### Airspace -By default, **OK TCU** owns the airspace within the **R654A-D** restricted areas, and **AM TCU** owns the airspace within the **R625A-D** restricted areas, unless stated otherwise by ad-hoc release or NOTAM. +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 -All aircraft from AM/OK TCU to INL(All) require Heads-up coordination prior to the boundary. Expect this coordination to be completed a short time after the aircraft becomes airborne (pending controller workload). +All aircraft from AMB/OK TCU to INL(All) require Heads-up coordination prior to the boundary. Expect this coordination to be completed a short time after the aircraft becomes airborne (pending controller workload). !!! example - **AM TCU** -> **NSA**: "via COWIE, BUCK03." - **NSA** -> **AM TCU**: "BUCK03, `F190`" + **AMB TCU** -> **NSA**: "via COWIE, BUCK03." + **NSA** -> **AMB TCU**: "BUCK03, `F190`" #### Arrivals/Overfliers -All aircraft transiting from INL(All) to **OK TCU** and **AM TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **OK TCU** and **AM TCU** are fairly ad-hoc, so there are no standard assignable levels. ENR and TCU controllers should coordinate to determine the most suitable level. +All aircraft transiting from INL(All) 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. ENR and TCU controllers should coordinate to determine the most suitable level. !!! example - **GOL** -> **AM TCU**: "via HUUGO, STAL13, what level can I assign?" - **AM TCU** -> **GOL**: "STAL13, `A090`" - **GOL** -> **AM TCU**: "`A090`, STAL13" + **GOL** -> **AMB TCU**: "via HUUGO, STAL13, what level can I assign?" + **AMB TCU** -> **GOL**: "STAL13, `A090`" + **GOL** -> **AMB TCU**: "`A090`, STAL13" ### TSN(FLD/HWE) (Oceanic) As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary. \ No newline at end of file diff --git a/docs/enroute/Brisbane Centre/ISA.md b/docs/enroute/Brisbane Centre/ISA.md index 5f3c13946..5bf10db42 100644 --- a/docs/enroute/Brisbane Centre/ISA.md +++ b/docs/enroute/Brisbane Centre/ISA.md @@ -32,6 +32,7 @@ ISA is responsible for **ARA**, **STR**, **WEG**, and **CVN** when they are offl ## Sector Responsibilities ISA and its subsectors are purely Classes A, E and G of airspace. [Standard separation procedures](../../../separation-standards) apply. +ARA is responsible for sequencing and issuing descent to aircraft bound for YBSG. ## STAR Clearance Expectation ### Handoff @@ -50,6 +51,16 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR ### Enroute As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary. +### SG TCU +The Standard assignable level from ARA to SG TCU is `F130`, tracking via WP VOR. + +All other aircraft must be voice coordinated to SG TCU prior to **20nm** from the boundary. + +The Standard Assignable level from SG TCU to ARA is `F240`, and tracking via their planned route. + +#### SG ADC +When SG TCU is offline, coordination is not required between ISA(ARA) and SG ADC. Aircraft entering SG ADC airspace shall be handed off, and instructed to contact SG ADC for onwards clearance. + ### ISA Internal As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary. ### TSN(COL) (Oceanic) diff --git a/docs/enroute/Brisbane Centre/KEN.md b/docs/enroute/Brisbane Centre/KEN.md index a9a7fe55f..c28775eec 100644 --- a/docs/enroute/Brisbane Centre/KEN.md +++ b/docs/enroute/Brisbane Centre/KEN.md @@ -127,7 +127,7 @@ The Standard Assignable level from KEN(SWY) to HM ADC is `A060`, any other level Any aircraft that will enter HM ADC airspace, and not landing at YBHM, must be Heads-up coordinated prior to **5 mins** from the boundary. !!! example - **SWY** -> **HM ADC**: "via OVRON, KNV, Overfleir" + **SWY** -> **HM ADC**: "via OVRON, KNV" **HM ADC** -> **SWY**: "KNV, A030" ### TSN(FLD) (Oceanic) diff --git a/docs/enroute/Brisbane Centre/TRT.md b/docs/enroute/Brisbane Centre/TRT.md index 64d7b55bf..444b983e1 100644 --- a/docs/enroute/Brisbane Centre/TRT.md +++ b/docs/enroute/Brisbane Centre/TRT.md @@ -23,6 +23,7 @@ TRT is responsible for **KIY** when they are offline. ## Sector Responsibilities TRT is responsible for sequencing, issuing STAR Clearances, and issuing descent for aircraft bound for YPDN. KIY is responsible for issuing descent and ascertaining arrival intentions for aircraft bound for YBRM. +KIY is also responsible for sequencing and issuing descent to aircraft bound for YCIN. ## STAR Clearance Expectation ### Handoff @@ -82,6 +83,16 @@ Any aircraft that will enter BRM ADC airspace, and not landing at YBRM, must be **KIY** -> **BRM ADC**: "via CIN, NQC" **BRM ADC** -> **SWY**: "NQC, A045" +### CIN TCU +The Standard assignable level from TRT(KIY) 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. + +The Standard Assignable level from CIN TCU to TRT(KIY) is `F190`, and tracking via their planned route. + +#### CIN ADC +When CIN TCU is offline, coordination is not required between TRT(KIY) and CIN ADC. Aircraft entering CIN ADC airspace shall be handed off, and instructed to contact CIN ADC for onwards clearance. + ### IND(INE) (Oceanic) As per [Standard Coordination Procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary. ### International (WAAF) diff --git a/docs/enroute/Melbourne Centre/ASP.md b/docs/enroute/Melbourne Centre/ASP.md index 33c31a0e1..ff7ed6831 100644 --- a/docs/enroute/Melbourne Centre/ASP.md +++ b/docs/enroute/Melbourne Centre/ASP.md @@ -26,6 +26,8 @@ **AS ADC** is responsible for the Class D airspace `SFC` to `A045`, as well as the Class C airspace `A045` to `A065`, within the AS CTR. +### Reclassifications + When **AS ADC** is offline, AS CTR (Class D and C `SFC` to `F125`) within 80 DME AS reverts to Class G, and AS CTR (Class C `F125` to `F245`) within 80 DME AS reverts to Class E, and both are administered by ASP. Alternatively, ASP may provide a [top-down procedural service](../../../aerodromes/Alice) if they wish. ## Extending @@ -76,5 +78,8 @@ Any aircraft that will enter AS ADC airspace, and not landing at YBAS, must be H **ASP** -> **AS ADC**: "via AS, JDS" **AS ADC** -> **ASP**: "JDS, A060" +### WR ADC +Coordination is not required between ASP(WRA) and WR ADC. Aircraft entering WR ADC airspace shall be handed off, and instructed to contact WR ADC for onwards clearance. + ### IND(INS) (Oceanic) As per [Standard Coordination Procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary. \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/BIK.md b/docs/enroute/Melbourne Centre/BIK.md index b018edc0e..4ba7d8faf 100644 --- a/docs/enroute/Melbourne Centre/BIK.md +++ b/docs/enroute/Melbourne Centre/BIK.md @@ -99,7 +99,7 @@ The Standard Assignable level from SY TCU to WOL is the lower of `F280` or the ` Refer to [Sydney TCU Airspace Division](../../../terminal/sydney/#airspace-division) for information on airspace divisions when **SAS**, **SDN**, **SDS** and/or **SRI** are online. ### CB TCU -The Standard assignable level from WOL to CB TCU is `F130`, and assigned the RAZZI STAR, BUNGO STAR, or AVBEG STAR STAR. +The Standard assignable level from WOL to CB TCU is `F130`, and assigned the RAZZI STAR, BUNGO STAR, or AVBEG STAR. All other aircraft must be voice coordinated to CB TCU prior to **20nm** from the boundary. @@ -123,7 +123,6 @@ Departures from YSNW in to WOL Class C will be coordinated at taxi, and will be !!! example **NW TCU** -> **WOL**: "Taxi, PSDN18 for YMCO via URBOB, Requesting F130" **WOL** -> **NW TCU**: "PSDN18, F130" - **NW TCU** -> **WOL**: "F130, PSDN18" #### Arrivals/Overfliers All aircraft transiting from WOL to **NW TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **NW TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the WOL and **NW TCU** controller agree on. diff --git a/docs/enroute/Melbourne Centre/ELW.md b/docs/enroute/Melbourne Centre/ELW.md index f5002dcf8..67cdaade8 100644 --- a/docs/enroute/Melbourne Centre/ELW.md +++ b/docs/enroute/Melbourne Centre/ELW.md @@ -106,23 +106,22 @@ That being said, it is *advised* that ELW/BLA/SNO give **Heads-up Coordination** - BLA to ELW for aircraft **not** on the Q29 or V169 airway (Changes permitted up to boundary for sequencing/descent purposes) - SNO to BLA for all aircraft -### ESL TCU +### ES TCU #### Airspace -By default, **ESL TCU** owns the airspace within 30nm ESL, `SFC` to `F200`, unless stated otherwise by ad-hoc release or NOTAM. +By default, **ES TCU** owns the airspace within 30nm ESL, `SFC` to `F200`, unless stated otherwise by ad-hoc release or NOTAM. #### Departures -Departures from YMES in to ELW(All) Class C will be coordinated at taxi, and will be requesting a level. +Departures from **ES TCU** in to ELW(All) CTA will be coordinated at taxi, and will be requesting a level. !!! example - **ESL TCU** -> **SNO**: "Taxi, ALDN14 for YSWG via VALDU, Requesting F210" - **SNO** -> **ESL TCU**: "ALDN14, F210" - **ESL TCU** -> **SNO**: "F210, ALDN14" + **ES TCU** -> **SNO**: "Taxi, ALDN14 for YSWG via VALDU, Requesting F210" + **SNO** -> **ES TCU**: "ALDN14, F210" #### Arrivals/Overfliers -All aircraft transiting from ELW(All) to **ESL TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **ESL TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the ELW(All) and **ESL TCU** controller agree on. +All aircraft transiting from ELW(All) to **ES TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **ES TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the ELW(All) and **ES TCU** controller agree on. !!! example - **ELW** -> **ESL TCU**: "via MNG, BFRT21, will be assigned F220, BLA and myself have no restrictions on descent" - **ESL TCU** -> **ELW**: "BFRT21, F220" + **ELW** -> **ES TCU**: "via MNG, BFRT21, will be assigned F220, BLA and myself have no restrictions on descent" + **ES TCU** -> **ELW**: "BFRT21, F220" ### AY ADC #### Airspace @@ -142,7 +141,7 @@ YMAY arrivals shall be heads-up coordinated to **AY ADC** from BLA prior to **5 !!! example **BLA** -> **AY ADC**: "via VEGRU1 arrival, QLK38" - **AY ADC** -> **BLA**: "QLK38" + **AY ADC** -> **BLA**: "QLK38, VEGRU1 arrival" The Standard Assignable level from BLA to **AY ADC** is `A080`. diff --git a/docs/enroute/Melbourne Centre/OLW.md b/docs/enroute/Melbourne Centre/OLW.md index 15b665427..56373140f 100644 --- a/docs/enroute/Melbourne Centre/OLW.md +++ b/docs/enroute/Melbourne Centre/OLW.md @@ -27,10 +27,11 @@ OLW is responsible for **POT**, **PAR**, **NEW**, **MEK**, **MTK** and **MZI** w ### Reclassifications #### KA CTR -When **KA ADC** is offline, KA CTR (Class D `SFC` to `A055`) reverts to Class G, and is administered by OLW. Alternatively, OLW may provide a [top-down approach service](../../../terminal/canberra) if they wish. +When **KA ADC** is offline, KA CTR (Class D `SFC` to `A055`) reverts to Class G, and is administered by OLW. Alternatively, OLW may provide a [top-down procedural service](../../../aerodromes/Karratha) if they wish. ## Sector Responsibilities OLW is responsible for issuing descent and ascertaining arrival intentions for aircraft bound for YPKA. +OLW is also responsible for sequencing and issuing descent to aircraft bound for YPLM. ## STAR Clearance Expectation ### Handoff @@ -74,5 +75,15 @@ Any aircraft that will enter KA ADC airspace, and not landing at YPKA, must be H **OLW** -> **KA ADC**: "via BORAT, QQK" **KA ADC** -> **OLW**: "QQK, A030" +### LM TCU +The Standard assignable level from OLW to LM TCU is `F130`, tracking via LM VOR. + +All other aircraft must be voice coordinated to LM TCU prior to **20nm** from the boundary. + +The Standard Assignable level from LM TCU to OLW is `F240`, and tracking via their planned route. + +#### LM ADC +When LM TCU is offline, coordination is not required between OLW and LM ADC. Aircraft entering LM ADC airspace shall be handed off, and instructed to contact LM ADC for onwards clearance. + ### IND,INE (Oceanic) As per [Standard Coordination Procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary. \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/YWE.md b/docs/enroute/Melbourne Centre/YWE.md index 35831df29..4ccc990a1 100644 --- a/docs/enroute/Melbourne Centre/YWE.md +++ b/docs/enroute/Melbourne Centre/YWE.md @@ -103,20 +103,19 @@ The Standard Assignable level from SY TCU to KAT is the lower of `F280` or the ` Refer to [Sydney TCU Airspace Division](../../../terminal/sydney/#airspace-division) for information on airspace divisions when **SAS**, **SDN**, **SDS** and/or **SRI** are online. -### ESL TCU +### ES TCU #### Airspace -By default, **ESL TCU** owns the airspace within 30nm ESL, `SFC` to `F200`, unless stated otherwise by ad-hoc release or NOTAM. +By default, **ES TCU** owns the airspace within 30nm ESL, `SFC` to `F200`, unless stated otherwise by ad-hoc release or NOTAM. #### Departures -Departures from YMES in to WON Class C will be coordinated at taxi, and will be requesting a level. +Departures from **ES TCU** in to WON CTA will be coordinated at taxi, and will be requesting a level. !!! example - **ESL TCU** -> **WON**: "Taxi, ALDN16 for YFLI DCT, Requesting F230" - **WON** -> **ESL TCU**: "ALDN16, F230" - **ESL TCU** -> **WON**: "F230, ALDN16" + **ES TCU** -> **WON**: "Taxi, ALDN16 for YFLI DCT, Requesting F230" + **WON** -> **ES TCU**: "ALDN16, F230" #### Arrivals/Overfliers -All aircraft transiting from WON to **ESL TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **ESL TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the WON and **ESL TCU** controller agree on. +All aircraft transiting from WON to **ES TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **ES TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the WON and **ES TCU** controller agree on. !!! example - **WON** -> **ESL TCU**: "via ANTLA, BFRT23, will be assigned F220, I have no restrictions on descent" - **ESL TCU** -> **WON**: "BFRT23, F220" \ No newline at end of file + **WON** -> **ES TCU**: "via ANTLA, BFRT23, will be assigned F220, I have no restrictions on descent" + **ES TCU** -> **WON**: "BFRT23, F220" \ No newline at end of file diff --git a/docs/pacific/New-Caledonia/TCU.md b/docs/pacific/New-Caledonia/TCU.md index 3f5b73b84..af29b8c47 100644 --- a/docs/pacific/New-Caledonia/TCU.md +++ b/docs/pacific/New-Caledonia/TCU.md @@ -8,14 +8,19 @@ | Name | ID | Callsign | Frequency | Login Identifier | | ------------------ | --------------| -------------- | ---------------- | --------------------------------------| -| Tontouta Approach South|NWWWA| Tontouta Approach | 128.300 | NWWW_APP | +| **Tontouta Approach South**|**NWWWA**| **Tontouta Approach** | **128.300** | **NWWW_APP** | +| Tontouta Approach (TMA 1.1)†|NWWWT| Tontouta Approach | 119.700 | NWWW-T_APP | -## Airspace +† *Non-standard positions* may only be used in accordance with [VATPAC Ratings and Controller Positions Policy](https://vatpac.org/publications/policies){target=new} + +## Airspace The vertical limits of the Tontouta TCU are `SFC` to `F245`. When NWWM ADC is offline, the NWWM CTR (`SFC` to `A015`) reverts to Class G and is administered by the relevant TCU controller. +When NWWWT is online, the TCU is split down the NWWW 11/29 Extended Centreline, with NWWWA owning the northern portion, and NWWWT owning the southern portion. + ## Coordination ### NWWW TCU / ENR diff --git a/docs/separation-standards/classd.md b/docs/separation-standards/classd.md index 667ab9805..4a542722f 100644 --- a/docs/separation-standards/classd.md +++ b/docs/separation-standards/classd.md @@ -12,8 +12,15 @@ Remember that in [Class D Airspace](../../controller-skills/classofairspace), IF
Class D Tower Airspace Diagram
-## Procedural Separation -At [Tamworth](../../aerodromes/tamworth), [Coffs Harbour](../../aerodromes/Coffs), [Hamilton Island](../../aerodromes/Hammo), and [Sunshine Coast](../../aerodromes/sunshinecoast) Towers, surveillance coverage cannot be guaranteed at all levels. Therefore, [Procedural Separation](../procedural) must be implemented prior to losing surveillance identification of an aircraft, if [Visual Separation](../visual) cannot be assured below the height at which surveillance coverage will be lost. For more information, refer to Local Instructions. +## Surveillance +Although Surveillance standards cannot be used for separation at Class D Towers, overlying TCU/Enroute controllers can use their surveillance standards to help Class D towers achieve separation, when procedural separation is a bit awkward or impractical. + +!!! example + **AY ADC** -> **BLA**: "Can you advise when QLK208D is 5nm clear of DSB?" + **BLA** -> **AY ADC**: "Affirm, will do" + ... + **BLA** -> **AY ADC**: "QLK208D, 5nm clear of DSB" + **AY ADC** -> **BLA**: "QLK208D, 5nm clear of DSB, thanks" ## Lateral diff --git a/docs/separation-standards/img/dep2min.png b/docs/separation-standards/img/dep2min.png new file mode 100644 index 000000000..37503b433 Binary files /dev/null and b/docs/separation-standards/img/dep2min.png differ diff --git a/docs/separation-standards/procedural.md b/docs/separation-standards/procedural.md index 1361c67ee..e55a2ad30 100644 --- a/docs/separation-standards/procedural.md +++ b/docs/separation-standards/procedural.md @@ -5,6 +5,13 @@ title: Procedural --8<-- "includes/abbreviations.md" ## Departures +### 2 min +| Conditions | | +| ------------- | ------------------ | +| a) The aircraft are climbing to vertically separated levels;
b) Both aircraft report reaching the cruising level;
c) If the following aircraft is climbing to a lower level than the preceding aircraft, and reaches that level first, apply another form of separation immediately; and
d) climb and cruising IAS of the following aircraft is at least 10 kt slower and not more than 90% of the climb and cruising IAS or Mach number of the leading aircraft. |
+![2 min Departure Standard Diagram](img/dep2min.png){ width="600" } +
| + ### 5 min | Conditions | | | ------------- | ------------------ | @@ -116,14 +123,13 @@ Where a difference 15 minutes does not exist at the crossing point, vertical sep ### Conflict Area - The Quickest and easiest way to assess lateral conflict scenarios is with the *Conflict Area tool*. Unfortunately, whilst its quick and easy to *use*, it's fairly complex and long to understand the rules and concepts. The first thing to note, is that there are many different unusual remarks and equipment codes that pilots file on VATSIM, primarily because not everyone knows what they mean. A little bit of background knowledge is required to understand these concepts. #### NAVCAPs All aircraft have a NAVCAP, associated with a ***Circular Error of Position***. This determines which number to select when using the Conflict Area Tool: -| NAVCAP Code | Meaning | Cicular Error of Position (CEP) | +| NAVCAP Code | Meaning | Circular Error of Position (CEP) | | ---- | ----------- | -------- | | A | All | 7nm | | 2 | RNP2 | 7nm | diff --git a/docs/separation-standards/runway.md b/docs/separation-standards/runway.md index f9432618a..69d2f5a0f 100644 --- a/docs/separation-standards/runway.md +++ b/docs/separation-standards/runway.md @@ -79,13 +79,10 @@ title: Runway | Lead Aircraft | Following Aircraft | Time (min) | Distance (nm)| | ------------- | ------------------ | ---------- | ---------- | -| Super (A380) | Super | - | - | -| | Heavy | 2 | 6 | +| Super (A388/A225) | Heavy | 2 | 6 | | | Medium | 3 | 7 | | | Light | 3 | 8 | | Heavy | Heavy | - | 4 | | | Medium | 2 | 5 | | | Light | 2 | 6 | -| Medium | Heavy | - | - | -| | Medium | - | - | -| | Light | 2 | 5 | \ No newline at end of file +| Medium | Light | 2 | 5 | \ No newline at end of file diff --git a/docs/terminal/amberleyoakey.md b/docs/terminal/amberleyoakey.md index b8276dffa..6745082b7 100644 --- a/docs/terminal/amberleyoakey.md +++ b/docs/terminal/amberleyoakey.md @@ -2,25 +2,22 @@ title: Amberley / Oakey TCU --- ---8<-- "includes/abbreviations.md" - - --8<-- "includes/abbreviations.md" ## Positions | Name | Callsign | Frequency | Login Identifier | | ------------------ | -------------- | ---------------- | --------------------------------------| -| Amberley TCU | Amberley Approach | 126.200 | AM_APP | +| Amberley TCU | Amberley Approach | 126.200 | AMB_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. +AMB APP is expected to extend to OK APP when they are offline. No frequency cross coupling is required. ## Airspace -### AM TCU +### AMB TCU #### Restricted Areas -By default, AM APP owns all of the R625 Restricted Areas, as detailed below: +By default, AMB APP owns all of the R625 Restricted Areas, as detailed below: - R625A (`A015`-`A085`) - R625B (`A025`-`A085`) @@ -28,7 +25,7 @@ By default, AM APP owns all of the R625 Restricted Areas, as detailed below: - R625D (`A085`-`F210`) ### Optional, as required -AM APP can negotiate further airspace releases from surrounding ENR sectors to facilitate planned military operations of the following Restricted Areas: +AMB APP can negotiate further airspace releases from surrounding ENR sectors to facilitate planned military operations of the following Restricted Areas: - R650A (`A050`-`A100`) - R650B (`A050`-`F600`) @@ -43,12 +40,12 @@ AM APP can negotiate further airspace releases from surrounding ENR sectors to f #### Diagram
-![AM TCU Airspace Diagram](img/amtcu.png){ width="952" } -
AM TCU Airspace Diagram
+![AMB TCU Airspace Diagram](img/amtcu.png){ width="952" } +
AMB TCU Airspace Diagram
-### AM ADC -AM ADC owns the Class C airspace in the AM CTR within 10nm of the YAMB ARP from `SFC` to `A015`. +### AMB ADC +AMB ADC owns the Class C airspace in the AM CTR within 10nm of the YAMB ARP from `SFC` to `A015`. ### OK TCU #### Restricted Areas @@ -79,7 +76,7 @@ Aircraft will make a visual departure in the circuit direction and fly overhead !!! example WOLF03 was assiged the BYRON7 departure with their intial clearance. - **AM ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff" + **AMB ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff" **WOLF03**: "Make left turn, reach `F190` by COWIE, cleared for takeoff, WOLF03" | Departure | Initial Constraint | Route | @@ -92,7 +89,7 @@ Aircraft will make a visual departure in the circuit direction and fly overhead Charts for the Coded Departures may be in YAMB AD2 Supplements 6.2.25.11 available here: [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new} !!! note - AM ACD will record the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route with all necessary tracking points. + AMB ACD will record the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route with all necessary tracking points. ## Charts !!! note @@ -101,35 +98,35 @@ Aircraft will make a visual departure in the circuit direction and fly overhead ## Coordination ### AM/OK ADC -'Next' coordination is required from AM ADC to AM TCU for all aircraft. +'Next' coordination is required from AMB ADC to AMB TCU for all aircraft. !!! example - **AM ADC** -> **AM TCU**: "Next, ASY01, runway 33" - **AM TCU** -> **AM ADC**: "ASY01, Assigned Heading Right 030, unrestricted" - **AM ADC** -> **AM TCU**: "Assigned Heading Heading Right 030, ASY01" + **AMB ADC** -> **AMB TCU**: "Next, ASY01, runway 33" + **AMB TCU** -> **AMB ADC**: "ASY01, Assigned Heading Right 030, unrestricted" + **AMB ADC** -> **AMB TCU**: "Assigned Heading Heading Right 030, ASY01" ### INL / BN TCU #### 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. +All aircraft from AMB/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. -The Standard Assignable Level from **AM ADC** to **AM TCU** is: +The Standard Assignable Level from **AMB ADC** to **AMB 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. The Standard Assignable from **OK ADC** to **OK TCU** is the lower of `F120` or `RFL`. !!! example - **AM TCU** -> **BN TCU**: "via BN, DRGN02" - **BN TCU** -> **AM TCU**: "DRGN02, `F180`" + **AMB TCU** -> **BN TCU**: "via BN, DRGN02" + **BN TCU** -> **AMB TCU**: "DRGN02, `F180`" !!! example BUCK03 is assigned the BYRON 7 coded departure. - **AM TCU** -> **NSA**: "via COWIE, BUCK3." - **NSA** -> **AM TCU**: "BUCK03, `F190`" + **AMB TCU** -> **NSA**: "via COWIE, BUCK3." + **NSA** -> **AMB TCU**: "BUCK03, `F190`" #### Arrivals/Overlfies -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 **AM TCU** are fairly ad-hoc, so there are no standard assignable levels. GOL/DOS/BUR and **AM TCU**/**OK TCU** controller must agree on a suitable level during coordination. +All aircraft transiting from GOL/DOS/BUR to **AMB TCU** and **OK TCU** must be heads-up coordinated prior to **20nm** from the boundary and aircraft from **BN TCU** to **AMB TCU** only prior to the boundary. Operations within **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels. GOL/DOS/BUR and **AMB TCU**/**OK TCU** controller must agree on a suitable level during coordination. !!! example - **GOL** -> **AM TCU**: "via HUUGO, PUMA11, will be assigned A090" - **AM TCU** -> **GOL**: "PUMA11, A090" + **GOL** -> **AMB TCU**: "via HUUGO, PUMA11, will be assigned A090" + **AMB TCU** -> **GOL**: "PUMA11, A090" diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md index 9a9b11543..a314cd99a 100644 --- a/docs/terminal/brisbane.md +++ b/docs/terminal/brisbane.md @@ -179,19 +179,19 @@ VFR aircraft require a level readback. **BN TCU** -> **AF ADC**: "via TVT for the visual approach, UJE" **AF ADC** -> **BN TCU**: "UJE, visual approach" -### AM TCU -All aircraft transiting from **BN TCU** to **AM TCU** and vice versa must be heads-up coordinated prior to the boundary. +### AMB TCU +All aircraft transiting from **BN TCU** to **AMB TCU** and vice versa must be heads-up coordinated prior to the boundary. !!! example - **AM TCU** -> **BN TCU**: "via BN, DRGN02" - **BN TCU** -> **AM TCU**: "DRGN02, `F140`" + **AMB TCU** -> **BN TCU**: "via BN, DRGN02" + **BN TCU** -> **AMB TCU**: "DRGN02, `F140`" -For aircraft arriving into AM TCU there is no standard assignable level and simply is what ever the controllers agree upon. +For aircraft arriving into AMB TCU there is no standard assignable level and simply is what ever the controllers agree upon. !!! example - **BN TCU** -> **AM TCU**: "via WACKO, STAL13, what level can I assign?" - **AM TCU** -> **BN TCU**: "STAL13, `A090`" - **BN TCU** -> **AM TCU**: "`A090`, STAL13" + **BN TCU** -> **AMB TCU**: "via WACKO, STAL13, what level can I assign?" + **AMB TCU** -> **BN TCU**: "STAL13, `A090`" + **BN TCU** -> **AMB TCU**: "`A090`, 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. diff --git a/docs/terminal/curtin.md b/docs/terminal/curtin.md new file mode 100644 index 000000000..a3e927802 --- /dev/null +++ b/docs/terminal/curtin.md @@ -0,0 +1,52 @@ +--- + title: Curtin TCU +--- + +--8<-- "includes/abbreviations.md" + +## Positions + +| Name | Callsign | Frequency | Login Identifier | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| Curtin TCU | Curtin Approach | 121.000 | CIN_APP | + +## Airspace +The limits of the CIN TCU are `SFC` to `F200` within 25 DME CIN. This may be amended by NOTAM. + +By default, CIN APP owns the following Restricted Areas, as detailed below: + +- R801A (Partial) (`SFC`-`A035`) +- R802A (`A035`-`F200`) + +The above Restricted Areas are classified as Class C when CIN APP is active. + +!!! note + See [VATPAC NOTAMs](https://vatpac.org/publications/notam){target=new} for active NOTAMs which may affect military operations. + +## Coordination +### CIN ADC +'Next' coordination is required from CIN ADC to CIN TCU for all aircraft. + +!!! example + **CIN ADC** -> **CIN TCU**: "Next, ASY404, runway 29" + **CIN TCU** -> **CIN ADC**: "ASY404, unrestricted" + **CIN ADC** -> **CIN TCU**: "ASY404" + +### TRT(KIY) +#### Departures +Voiceless coordination is in place from CIN TCU to KIY for aircraft: +Planned at or above `F190`: `Assigned F190` +Planned below `F190`: `Assigned the RFL` + +Any aircraft not meeting the above criteria must be prior coordinated to ENR. + +!!! example + **CIN TCU** -> **KIY**: "ASY404, with your concurrence, will be assigned F180, for my separation with JTE654" + **KIY** -> **CIN TCU**: "ASY404, concur F160" + +#### Arrivals +The Standard assignable level from KIY to CIN TCU is `F130`, and tracking via CIN VOR. All other aircraft must be prior coordinated. + +!!! 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} + diff --git a/docs/terminal/learmonth.md b/docs/terminal/learmonth.md new file mode 100644 index 000000000..ddb6be1c2 --- /dev/null +++ b/docs/terminal/learmonth.md @@ -0,0 +1,53 @@ +--- + title: Learmonth TCU +--- + +--8<-- "includes/abbreviations.md" + +## Positions + +| Name | Callsign | Frequency | Login Identifier | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| Learmonth TCU | Learmonth Approach | 120.500 | LM_APP | + +## Airspace +The limits of the LM TCU are `SFC` to `F280` within 40 DME LM. This may be amended by NOTAM. + +By default, LM APP owns the following Restricted Areas, as detailed below: + +- R859A (`A045`-`A100`) +- R859B (`A100`-`F280`) +- R860A (`A015`-`A025`) +- R860B (`A025`-`F280`) + +The above Restricted Areas are classified as Class C when LM APP is active. + +!!! note + See [VATPAC NOTAMs](https://vatpac.org/publications/notam){target=new} for active NOTAMs which may affect military operations. + +## Coordination +### LM ADC +'Next' coordination is required from LM ADC to LM TCU for all aircraft. + +!!! example + **LM ADC** -> **LM TCU**: "Next, QFA1601, runway 36" + **LM TCU** -> **LM ADC**: "QFA1601, Right heading 060 Visual, unrestricted" + +### OLW +#### Departures +Voiceless coordination is in place from LM TCU to OLW for aircraft: +Planned at or above `F270`: `Assigned F270` +Planned below `F270`: `Assigned the RFL` + +Any aircraft not meeting the above criteria must be prior coordinated to ENR. + +!!! example + **LM TCU** -> **OLW**: "QFA1601, with your concurrence, will be assigned F160, for my separation with JTE654" + **OLW** -> **LM TCU**: "QFA1601, concur F160" + +#### Arrivals +The Standard assignable level from OLW to LM TCU is `F130`, and tracking via LM VOR. All other aircraft must be prior coordinated. + +!!! 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} + diff --git a/docs/terminal/scherger.md b/docs/terminal/scherger.md new file mode 100644 index 000000000..fb79e410e --- /dev/null +++ b/docs/terminal/scherger.md @@ -0,0 +1,53 @@ +--- + title: Scherger TCU +--- + +--8<-- "includes/abbreviations.md" + +## Positions + +| Name | Callsign | Frequency | Login Identifier | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| Scherger TCU | Scherger Approach | 124.200 | SG_APP | + +## Airspace +The limits of the SG TCU are `SFC` to `F245` within 40 NM of the YBSG ARP. This may be amended by NOTAM. + +By default, SG APP owns the following Restricted Areas, as detailed below: + +- R604A (`A040`-`F125`) +- R604B (`F125`-`F245`) +- R605A (`A040`-`F125`) +- R604B (`F125`-`F245`) + +The above Restricted Areas are classified as Class C when SG APP is active. + +!!! note + See [VATPAC NOTAMs](https://vatpac.org/publications/notam){target=new} for active NOTAMs which may affect military operations. + +## Coordination +### SG ADC +'Next' coordination is required from SG ADC to SG TCU for all aircraft. + +!!! example + **SG ADC** -> **SG TCU**: "Next, ASY219, runway 30" + **SG TCU** -> **SG ADC**: "ASY219, unrestricted" + +### ISA(ARA) +#### Departures +Voiceless coordination is in place from SG TCU to ARA for aircraft: +Planned at or above `F245`: `Assigned F240` +Planned below `F245`: `Assigned the RFL` + +Any aircraft not meeting the above criteria must be prior coordinated to ENR. + +!!! example + **SG TCU** -> **ARA**: "ASY219, with your concurrence, will be assigned F200, for my separation with ASY404" + **ARA** -> **SG TCU**: "ASY219, concur F200" + +#### Arrivals +The Standard assignable level from ARA to SG TCU is `F130`, and tracking via WP VOR. All other aircraft must be prior coordinated. + +!!! 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} + diff --git a/docs/terminal/williamtown.md b/docs/terminal/williamtown.md index 308da01ed..98bbb1532 100644 --- a/docs/terminal/williamtown.md +++ b/docs/terminal/williamtown.md @@ -8,12 +8,17 @@ | Name | Callsign | Frequency | Login Identifier | | ------------------ | -------------- | ---------------- | --------------------------------------| -| Williamtown Approach | Willy Approach | 135.700 | WLM_APP | +| **Williamtown Approach (High)** | **Willy Approach** | **133.300** | **WLM_APP** | +| Williamtown Approach (Low)† | Willy Approach | 135.700 | WLM-L_APP | + +† *Non-standard positions* may only be used in accordance with [VATPAC Ratings and Controller Positions Policy](https://vatpac.org/publications/policies). ## Airspace ### Default By default, WLM TCU owns the airspace within the WLM MIL CTR `SFC` to `F125`. This may be amended by NOTAM. +When WLM TCU is active above `F125` by ad-hoc release or NOTAM, WLM-L_APP owns the airspace `SFC` to `F125`, while WLM APP owns the rest of WLM TCU airspace above `F125`. This may be adjusted as required with coordination. + #### Diagram
![WLM TCU Airspace](img/wlmtcu.png){ width="700" } @@ -21,7 +26,7 @@ By default, WLM TCU owns the airspace within the WLM MIL CTR `SFC` to `F125`. Th
!!! note - It is the responsibility of the WLM TCU controller to negotiate any airspace releases with ARL(All). + It is the responsibility of the WLM TCU controller(s) to negotiate any airspace releases with ARL(All). ### ADC When WLM ADC is online, they own the airspace within the WLM MIL CTR A (`SFC`-`A050`). This may be amended/released as required between WLM ADC and WLM TCU.