Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aerodrome categories, Airspace descriptions, and more #218

Merged
merged 6 commits into from
Jan 31, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/aerodromes/classc/.pages
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Edit this page to get:
# - Title for the whole directory
# - Titles for specific pages or subdirectories
# - Order of pages (otherwise alphabetical order)

title: Class C
nav:
- ...
File renamed without changes.
File renamed without changes.
15 changes: 10 additions & 5 deletions docs/aerodromes/Brisbane.md → docs/aerodromes/classc/Brisbane.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ When using the SODPROPS mode, pass traffic information to aircraft that are depa
**DEF:** "Cleared to Land Runway 19R, DEF"

## Parallel Runway Operations
Refer to [Parallel Runway Separation Standards](../../separation-standards/parallelapps) for more information
Refer to [Parallel Runway Separation Standards](../../../separation-standards/parallelapps) for more information

### Runway Selection
Aircraft shall be assigned the following runways for departure when PROPS are in progress:
Expand All @@ -85,16 +85,21 @@ Aircraft shall be assigned the following runways for departure when PROPS are in
Runway 01L/19R opened in 2020. Some pilots on VATSIM may have old simulators/scenery, in which case they will only have Runway 01R/19L available. Endeavour to be accommodating of pilots' requests in this instance.

### SID Selection

Jet Aircraft planned via **BIXAD**, **GUMKI**, **SCOTT**, **SANEG**, or **WACKO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus, unless the pilot indicates they are unable to accept a Procedural SID.

!!! example
Jet Aircraft planned via SCOTT, assigned runway 19L, shall be given the SCOTT SID.
Jet Aircraft planned via SCOTT, assigned runway 19L, shall be assigned the SCOTT SID.

Non-Jet aircraft, and aircraft that cannot accept a Procedural SID, shall be assigned the **Radar SID**.

!!! example
Non-Jet Aircraft planned via WACKO, assigned runway 01L, shall be given the BN (RADAR) SID.
Non-Jet Aircraft planned via WACKO, assigned runway 01L, shall be assigned the BN (RADAR) SID.

#### SODPROPS
During the SODPROPS runway mode, Jet departures from Runway 01R shall be assigned the **ASISO** Procedural SID in lieu of other Procedural SIDs available that terminate at the appropriate waypoint.

!!! example
Jet Aircraft planned via SCOTT, assigned runway 01R, shall be assigned the ASISO SID, SCOTT Transition.

## ATIS
#### Operational Info
Expand Down Expand Up @@ -132,4 +137,4 @@ For Jets: `A060`
For Non-Jets: The lower of `A040` or the `RFL`

### Departures Controller
Refer to [Brisbane TCU Airspace Division](../../terminal/brisbane/#airspace-division) for information on airspace divisions when **BDN** and/or **BDS** are online.
Refer to [Brisbane TCU Airspace Division](../../../terminal/brisbane/#airspace-division) for information on airspace divisions when **BDN** and/or **BDS** are online.
File renamed without changes.
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,7 @@
| 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
CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`.

## Circuit Direction

Expand Down
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,7 @@
| 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
LM ADC owns the Class C airspace within the LM CTR from `SFC` to `A015`.

## Circuit Direction

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -106,11 +106,20 @@ This permits controllers to assign aircraft either the Alpha or Victor STAR and
| 09A/16D | 09 FOR ARR, RWY 16 FOR DEPARTURES |

### Operational Info
#### Independent Crossing Runway Operations
When using runway mode 09A/16D, the ATIS OPR INFO shall include:
`SIMUL INDEP CROSSING RWY OPS IN PROG`

This allows for both Runway 09 and Runway 16 to operate independently of each other, with aircraft departing Runway 16 from Taxiway Echo.

#### Pushback Request on ACD
The Real-world YMML ATIS will at times include an operational info line:
`ALL DEPARTURES MUST REQUEST PUSH BACK ON 127.2`

Whilst this is used to reduce frequency congestion on SMC in the real world, coordination limitations in the VATSIM environment mean that this procedure serves no benefit to the SMC and ACD controllers (Instead of SMC having to answer a pushback request from an aircraft, SMC still has to answer a coordination line from ACD regarding an aircraft requesting pushback).

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

## Coordination
### Auto Release
!!! important
Expand Down Expand Up @@ -156,4 +165,4 @@ The following Standard Assignable Headings may be used for aircraft assigned the
Any runway change must be prior coordinated to **MAE** and **EN ADC**.

### Departures Controller
Refer to [Melbourne TCU Airspace Division](../../terminal/melbourne/#airspace-division) for information on airspace divisions when **MDN** and/or **MDS** are online.
Refer to [Melbourne TCU Airspace Division](../../../terminal/melbourne/#airspace-division) for information on airspace divisions when **MDN** and/or **MDS** are online.
File renamed without changes.
2 changes: 0 additions & 2 deletions docs/aerodromes/Oakey.md → docs/aerodromes/classc/Oakey.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,6 @@
| Oakey ATIS | | 124.300 | YBOK_ATIS |

## Airspace

OK ADC owns the airspace within 5 DME of the OK VOR from `SFC` to `A025`. This airspace is designed to facilitate circuit traffic.

## Charts
Expand All @@ -39,7 +38,6 @@ The standard circuit direction is to the north of the field.

## Coordination
### OK TCU

'Next' coordination is required from OK ADC to OK TCU for all aircraft not remaining in the circuit.

!!! example
Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ The PH TCU controller can suspend/resume Auto Release at any time, with the conc
The Standard Assignable level from PH ADC to PH TCU is the lower of `A050` or the `RFL`.

### Departures Controller
Refer to [Perth TCU Airspace Division](../../terminal/perth/#airspace-division) for information on airspace divisions when **PHD** is online.
Refer to [Perth TCU Airspace Division](../../../terminal/perth/#airspace-division) for information on airspace divisions when **PHD** is online.

### ACD to PH TCU
The controller assuming responsibility of ACD shall give heads-up coordination to the relevant PH TCU controller prior to the issue of the following clearances:
Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,7 @@
| 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
SG ADC owns the Class C airspace within the SG CTR from `SFC` to `A015`.

## Circuit Direction
| Runway | Direction |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ When using the SODPROPS mode, pass traffic information to aircraft that are depa
When runway 25 is in use, the responsibility for management of the helicopter area falls to **ADC West**. When runway 25 is not in use, **ADC East** (if online) takes responsibility for the heliport.

## Parallel Runway Operations
Refer to [Parallel Runway Separation Standards](../../separation-standards/parallelapps) for more information
Refer to [Parallel Runway Separation Standards](../../../separation-standards/parallelapps) for more information

### Go-arounds / Missed Approaches
When operating under PROPS, go around headings shall diverge from the extended centreline of the parallel runway by at least 30°. Aircraft cleared the ILS or IVA may follow the published missed approach in order to meet this requirement.
Expand Down Expand Up @@ -247,9 +247,6 @@ Unless operationally required, aircraft shall be assigned the following runways
| Jet | All others | **KAMPI** SID, RADAR Transition |
| Non-Jet | All | **RADAR** SID |

!!! note
Some aircraft will be unable to meet Climb Gradient Requirements on the **KAMPI** SID (6.7% to EXUGI), but still able to meet the requirements of the **DEENA** SID (4.7% to 1000ft). As above, the pilot will advise their capabilities. Aircraft that can accept the **DEENA** SID shall be assigned it as preference to the **RADAR** SID

### Runway 25

| Type | Via | SID |
Expand Down Expand Up @@ -376,7 +373,7 @@ For Jets: `A050`
For Non-Jets: The lower of `A030` or the `RFL`

### Departures Controller
Refer to [Sydney TCU Airspace Division](../../terminal/sydney/#airspace-division) for information on airspace divisions when **SDN** and/or **SDS** are online.
Refer to [Sydney TCU Airspace Division](../../../terminal/sydney/#airspace-division) for information on airspace divisions when **SDN** and/or **SDS** are online.

### Standard Assignable Departure Headings
Aircraft that have been cleared the **SY (RADAR) SID** must receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required to the SY TCU controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below:
Expand Down
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
8 changes: 8 additions & 0 deletions docs/aerodromes/classc/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: Overview

---

--8<-- "includes/abbreviations.md"

Local Instructions for all Class C towered aerodromes in Australia. For simulation purposes only.
8 changes: 8 additions & 0 deletions docs/aerodromes/classd/.pages
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Edit this page to get:
# - Title for the whole directory
# - Titles for specific pages or subdirectories
# - Order of pages (otherwise alphabetical order)

title: Class D
nav:
- ...
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ AF ADC is responsible for the Class D airspace in the AF CTR `SFC` to `A015`.
<figcaption>AF ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## VFR Arrival Procedures
VFR aircraft should track via a VFR inbound point at `A015` and be instructed as below:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ YWE(WON) is responsible for the Class G Airspace to the South East of the AV CTR
![AV ADC Airspace](img/avctr.png){ width="500" }
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## SID Selection
Aircraft planned via **ML** shall be assigned the **JUSTY** SID.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ BK ADC is responsible for the Class D airspace in the BK CTR `SFC` to `A015`.
<figcaption>BK ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## Fixed-Wing Operations
### VFR Inbound Procedures
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ CN ADC is responsible for the Class D airspace in the CN CTR `SFC` to `A020`.
<figcaption>CN ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## Departures

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ South of the Runway Centreline: `SFC` to `A025`
<figcaption>HB ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## SID Selection
Jet Aircraft planned via **RIBLI**, **LATUM**, or **LAVOP**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint.
Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ LT ADC is responsible for the Class D airspace in the LT CTR `SFC` to `A015`.
![Launceston Tower Airspace](img/LTTWR.png){ width="700" }
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## SID Selection
Aircraft planned via **MIKIS**, **TASUM**, or **VEKLO** shall be assigned the relevant Procedural SID.
Expand Down
24 changes: 18 additions & 6 deletions docs/aerodromes/Mackay.md → docs/aerodromes/classd/Mackay.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,18 +18,30 @@ MK ADC is responsible for the Class D airspace in the MK CTR `SFC` to `A010`.
![MK ADC Airspace](img/MKTWR.png){ width="700" }
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## 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.
#### Auto Release
'Next' coordination is **not** required to MKA for aircraft that are:
a) Departing from a runway nominated on the ATIS; and
b) Assigned the standard assignable level; and
c) Assigned a **Procedural** SID

!!! example
<span class="hotline">**MK ADC** -> **MKA**</span>: "Next, TFX113"
<span class="hotline">**MKA** -> **MK ADC**</span>: "TFX113, Unrestricted"
<span class="hotline">**MK ADC** -> **MKA**</span>: "TFX113"
<span class="hotline">**MK ADC** -> **MKA**</span>: "Next, ABC, runway 14"
<span class="hotline">**MKA** -> **MK ADC**</span>: "ABC, Heading 150 Visual, unrestricted"
<span class="hotline">**MK ADC** -> **MKA**</span>: "Heading 150 Visual unrestricted, ABC"

The Standard Assignable level from MK ADC to MKA is the lower of `A060` or the `RFL`, any other level must be prior coordinated.
The TCU controller can suspend/resume Auto Release at any time, with the concurrence of **MKA**.

The Standard Assignable level from MKADC to MKA is the lower of `A060` or the `RFL`.

#### SMC
The controller assuming responsibility of **SMC** shall give heads-up coordination to **MKA** prior to the issue of the following clearances:

- VFR Departures
- Aircraft using a runway not on the ATIS

### Arrivals/Overfliers
MKA will heads-up coordinate arrivals/overfliers from Class C to MK ADC.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ MB ADC is responsible for the Class D airspace in the MB CTR `SFC` to `A025`.
<figcaption>MB ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## Runway 04/22
Runway 04/22 is not to be used as an active runway. Used for emergencies only
Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -19,18 +19,30 @@ RK ADC is responsible for the Class D airspace in the RK CTR `SFC` to `A010`.
![RK ADC Airspace](img/RKTWR.png){ width="700" }
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## 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.
#### Auto Release
'Next' coordination is **not** required to **RKA** for aircraft that are:
a) Departing from a runway nominated on the ATIS; and
b) Assigned the standard assignable level; and
c) Assigned a **Procedural** SID

!!! example
<span class="hotline">**RK ADC** -> **RKA**</span>: "Next, VJE"
<span class="hotline">**RKA** -> **RK ADC**</span>: "VJE, Unrestricted"
<span class="hotline">**RK ADC** -> **RKA**</span>: "VJE"
<span class="hotline">**RKA** -> **RK ADC**</span>: "VJE, Track Extended Centreline, Unrestricted"
<span class="hotline">**RK ADC** -> **RKA**</span>: "Track Extended Centreline, VJE"

The Standard Assignable level from RK ADC to RKA is the lower of `A060` or the `RFL`, any other level must be prior coordinated.
The TCU controller can suspend/resume Auto Release at any time, with the concurrence of **RKA**.

The Standard Assignable level from MK/RK ADC to MKA/RKA is the lower of `A060` or the `RFL`.

#### MK/RK SMC
The controller assuming responsibility of **SMC** shall give heads-up coordination to **RKA** controller prior to the issue of the following clearances:

- VFR Departures
- Aircraft using a runway not on the ATIS

### Arrivals/Overfliers
RKA will heads-up coordinate arrivals/overfliers from Class C to RK ADC.
Expand Down
File renamed without changes
File renamed without changes
File renamed without changes
Binary file added docs/aerodromes/classd/img/IMCminlvl.png
File renamed without changes
File renamed without changes
File renamed without changes
Binary file added docs/aerodromes/classd/img/MLTCUairspace.png
File renamed without changes
File renamed without changes
Binary file added docs/aerodromes/classd/img/TRI.jpg
Binary file added docs/aerodromes/classd/img/avctr.png
File renamed without changes
File renamed without changes
Binary file added docs/aerodromes/classd/img/victor_routes.png
8 changes: 8 additions & 0 deletions docs/aerodromes/classd/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: Overview

---

--8<-- "includes/abbreviations.md"

Local Instructions for all Class D towered aerodromes in Australia. For simulation purposes only.
8 changes: 8 additions & 0 deletions docs/aerodromes/procedural/.pages
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Edit this page to get:
# - Title for the whole directory
# - Titles for specific pages or subdirectories
# - Order of pages (otherwise alphabetical order)

title: Procedural
nav:
- ...
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,13 @@
<figcaption>AY ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
AY ADC is responsible for the Class D airspace in the AY CTR `SFC` to `A045`.

Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## Surveillance
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
<span class="hotline">**AY ADC** -> **BLA**</span>: "Can you advise when QLK206D is 5nm clear of DSB?"
<span class="hotline">**BLA** -> **AY ADC**</span>: "Wilco"

<span class="hotline">**BLA** -> **AY ADC**</span>: "QLK206D 5nm clear of DSB"
<span class="hotline">**AY ADC** -> **BLA**</span>: "QLK206D 5nm clear of DSB, thanks"

## Coordination
### Departures
A 'Next' call is made for all aircraft when they are next to depart. AY ADC must inform ELW(BLA) if the aircraft does not depart within **2 minutes** of the next call.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ AS ADC is responsible for the Class D airspace `SFC` to `A045`, as well as the C
<figcaption>AD ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## Surveillance
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
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,9 @@
<figcaption>BRM ADC Airspace</figcaption>
</figure>

Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
BRM ADC is responsible for the Class D airspace `SFC` to `A055`, as well as the Class E airspace `1200ft AGL` to `A055`, within the BRM CTR.

Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.

## Surveillance
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
Expand Down
Loading