Skip to content

Commit

Permalink
Merge pull request #367 from vatpac-technology/alex-dev
Browse files Browse the repository at this point in the history
  • Loading branch information
@mattkelly4
mattkelly4 authored Oct 30, 2024
2 parents 15305bf + c569886 commit 4107cd2
Show file tree
Hide file tree
Showing 19 changed files with 277 additions and 128 deletions.
53 changes: 17 additions & 36 deletions docs/aerodromes/classc/Darwin.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,7 @@ b) ADC may deny requests for circuits if IFR traffic may be unduly delayed
<figcaption>DN ADC Airspace</figcaption>
</figure>

## Aerodrome
### Standard Taxi Routes
## Standard Taxi Routes
Aircraft transiting to or from the Southern and Northern GA should follow the following standardised taxi routes:
a) Outbound via V1
b) Inbound via Y1
Expand All @@ -36,7 +35,7 @@ Traffic permitting, aircraft above 136,000kg MTOW shall be entered/exited for RW

Taxiway V has a passing bay, located adjacent to the ARFF section. The passing bay is the preferred location for engine run-ups, no longer than 3 minutes

### Runway Modes
## Runway Modes
Runway selection shall be coordinated by DN ADC. In any case, a change of runway mode shall not be broadcast on the ATIS until DAW accepts the change.

The Runway Mode options available are:
Expand All @@ -48,6 +47,10 @@ d) Runway 11 and Runway 36;
e) Runway 11 and Runway 18;
f) Runway 11 only.

## Non-RNAV Departures
For non-RNAV approved IFR aircraft with a wake turbulence category of medium or greater, issue a Radar SID
For non-RNAV approved IFR aircraft with a wake turbulence category of light, issue a visual departure or Radar SID

## 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}
Expand All @@ -62,26 +65,7 @@ b) Jet: `A015`
c) Non-jet: `A010`
d) Helo: `A010`

## Coordination
### Auto Release
"Next" Coordination is a procedure where the **DN ADC** controller gives a heads-up to the DN TCU controller about an impending departure. The DN TCU controller will respond by assigning a heading to the aircraft, for the **DN ADC** controller to pass on with their takeoff clearance.


!!! example
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Next, EOC, runway 18"
<span class="hotline">**DN TCU** -> **DN ADC**</span>: "EOC, Track Extended Centreline, unrestricted"
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Track Extended Centreline, EOC"


All departures from 18/36 require departure coordination with **DN TCU**

### IFR Level Assignment
The Standard Assignable level from **DN ADC** to **DN TCU** is the lower of `F180` or the `RFL`.
If the aircraft is **not** planned via an RNAV SID and has a light wake turbulance cateogry, they are to be assigned the lower of `A030` or the `RFL`.

### VFR Departures
`A020` or the planned level; whichever is lower, to all VFR aircraft.

VFR aircraft are required to track via one of the published VFR Routes.

VFR routes shall be assigned based on the destination radial from Darwin.
Expand All @@ -100,20 +84,17 @@ Assign VFR routes in accordance with the following radial chart:
!!! tip
If a VFR aircraft has not planned via a VFR route as above, use the phraseology: “ABC, cleared amended route VFR route 1, maintain A020, squawk 4512”

### Auto-Release Wedge

The Darwin auto-release wedges extend from the departure end runway threshold, 30 degrees splayed from the centreline, to 7nm

Auto-release at Darwin is only available for VFR aircraft and low-level IFR aircraft.

Tower may depart aircraft that conform with the above conditions within the auto-release wedge using the following headings:
## Coordination
### DN TCU
Auto-Release is **not available** at YPDN. All Departures will be coordinated when ready for departure.

|Departure Type| Runway 11| Runway 29|
|---|---|----|
|VFR |H070V, H106V or H140V| H260V, H286V or H320V|
|IFR (Visual Dep)| H070V, H106V, or H140V |H260V, H286V or H320V|
|IFR (Radar)| H070, H106 or H140 |H260, H286 or H320|
!!! example
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Next, EOC, runway 18"
<span class="hotline">**DN TCU** -> **DN ADC**</span>: "EOC, Track Extended Centreline, unrestricted"
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Track Extended Centreline, EOC"

!!! tip
Tower shall provide visual separation between aircraft in the auto-release wedge and subsequent departures until the preceding departure has been maneuvered by TCU
The Standard Assignable level from **DN ADC** to **DN TCU** is:

- For IFR aircraft assigned a Procedural SID: the lower of `F180` or the `RFL`.
- For IFR aircraft **not** assigned a Procedural SID: the lower of `A030` or the `RFL`.
- For VFR aircraft: the lower of `A020` or the `RFL`.
90 changes: 31 additions & 59 deletions docs/terminal/darwin.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,7 @@ b) ADC may deny requests for circuits if IFR traffic may be unduly delayed
<figcaption>DN ADC Airspace</figcaption>
</figure>

### Surveillance
DN ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the DN ADC airspace.
For simulation purposes, visual separation is assumed to exist below the cloud base, and within 7nm of the aerodrome. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base.

## Aerodrome

### Runway Modes
## Runway Modes
Runway selection shall be coordinated by DN ADC. In any case, a change of runway mode shall not be broadcast on the ATIS until DAW accepts the change.

The Runway Mode options available are:
Expand All @@ -60,10 +54,6 @@ d) Runway 11 and Runway 36;
e) Runway 11 and Runway 18;
f) Runway 11 only.

#### Non-RNAV Departures
For non-RNAV approved IFR aircraft with a wake turbulence category of medium or greater, issue a Radar SID
For non-RNAV approved IFR aircraft with a wake turbulence category of light, issue a visual departure or Radar SID

## 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}
Expand All @@ -80,9 +70,31 @@ Other than in an emergency, the designated fuel jettison area is:
a) Over water in the Beagle Gulf
b) Between the 320 and 020 TACAN radials
c) `A060` or above

### Robertson Barracks
Darwin TCU is not responsible for traffic or separation services within the A005 step to the east of Darwin. This step is designed for low-level VFR MIL helos to transit in/out of Robertson Barracks without the need for communication with Darwin TCU.

### YPDN VFR Departures
`A020` or the planned level; whichever is lower, to all VFR aircraft.

VFR aircraft are required to track via one of the published VFR Routes.

VFR routes shall be assigned based on the destination radial from Darwin.

Assign VFR routes in accordance with the following radial chart:

|Outbound Radial |Assigned VFR Route|
|---|---|
|360 – 040 |VFR Route 1|
|041 – 084 |VFR Route 2|
|085 – 124 |VFR Route 3|
|125 – 180 |VFR Route 4|
|181 – 224 |VFR Route 5|
|225 – 359| Direct|

!!! tip
If a VFR aircraft has not planned via a VFR route as above, use the phraseology: “ABC, cleared amended route VFR route 1, maintain A020, squawk 4512”

## Coordination
### Enroute
#### Departures
Expand Down Expand Up @@ -114,58 +126,18 @@ All other aircraft coming from TRT CTA will be **Heads-up** Coordinated to DN TC
DN ADC owns the airspace within the DN CTR `SFC`–`A010`.

#### Auto Release
"Next" Coordination is a procedure where the **DN ADC** controller gives a heads-up to the DN TCU controller about an impending departure. The DN TCU controller will respond by assigning a heading to the aircraft, for the **DN ADC** controller to pass on with their takeoff clearance.

Auto-Release is **not available** at YPDN. All Departures will be coordinated when ready for departure.

!!! example
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Next, ABC, runway 18"
<span class="hotline">**DN TCU** -> **DN ADC**</span>: "ABC, Track Extended Centreline, unrestricted"
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Track Extended Centreline, unrestricted, ABC"


All departures from 18/36 require departure coordination with **DN TCU**
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Next, EOC, runway 18"
<span class="hotline">**DN TCU** -> **DN ADC**</span>: "EOC, Track Extended Centreline, unrestricted"
<span class="hotline">**DN ADC** -> **DN TCU**</span>: "Track Extended Centreline, EOC"

#### IFR Departures
The Standard Assignable level from **DN ADC** to **DN TCU** is the lower of `F180` or the `RFL`.
If the aircraft is **not** planned via an RNAV SID and has a light wake turbulance cateogry, they are to be assigned the lower of `A030` or the `RFL`.
The Standard Assignable level from **DN ADC** to **DN TCU** is:

#### VFR Departures
`A020` or the planned level; whichever is lower, to all VFR aircraft.

VFR aircraft are required to track via one of the published VFR Routes.

VFR routes shall be assigned based on the destination radial from Darwin.

Assign VFR routes in accordance with the following radial chart:

|Outbound Radial |Assigned VFR Route|
|---|---|
|360 – 040 |VFR Route 1|
|041 – 084 |VFR Route 2|
|085 – 124 |VFR Route 3|
|125 – 180 |VFR Route 4|
|181 – 224 |VFR Route 5|
|225 – 359| Direct|

!!! tip
If a VFR aircraft has not planned via a VFR route as above, use the phraseology: “ABC, cleared amended route VFR route 1, maintain A020, squawk 4512”

#### Auto-Release Wedge

The Darwin auto-release wedges extend from the departure end runway threshold, 30 degrees splayed from the centreline, to 7nm

Auto-release at Darwin is only available for VFR aircraft and low-level IFR aircraft.

Tower may depart aircraft that conform with the above conditions within the auto-release wedge using the following headings:

|Departure Type| Runway 11| Runway 29|
|---|---|----|
|VFR |H070V, H106V or H140V| H260V, H286V or H320V|
|IFR (Visual Dep)| H070V, H106V, or H140V |H260V, H286V or H320V|
|IFR (Radar)| H070, H106 or H140 |H260, H286 or H320|

!!! tip
Tower shall provide visual separation between aircraft in the auto-release wedge and subsequent departures until the preceding departure has been maneuvered by TCU
- For IFR aircraft assigned a Procedural SID: the lower of `F180` or the `RFL`.
- For IFR aircraft **not** assigned a Procedural SID: the lower of `A030` or the `RFL`.
- For VFR aircraft: the lower of `A020` or the `RFL`.

### DN TCU Internal
Heads-up coordination is not required between DAW and DAE for:
Expand Down
26 changes: 25 additions & 1 deletion docs/worldflight/Aerodromes/adelaide.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,20 +20,35 @@ An additional Non-Standard position for AD SMC will be used
| 3 | 05A12D |
| 4 | 23A12D |

*Single Runway* Operations shall be **avoided** at all costs.
Any other Runway Mode may **only** be used with approval from the Events Coordinator.

## Airways Clearance Delivery (ACD)
### Flight Plan Compliance
Ensure **all flight plans** are checked for compliance with the approved WF Route:

`DCT AD Q33 ESP Q158 PH DCT`

**OzStrips** will flag any *non-compliant* WF route.

If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC.

!!! example
**AD ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YPPH VIA GILES Q33 ESP Q158 PH DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."*

### SMC Frequency
Upon readback of an airways clearance or PDC, instruct aircraft to contact Adelaide Ground on **121.700** when ready for pushback.

### WorldFlight Teams
[WorldFlight Teams](../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority.

!!! tip
The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}

<figure markdown>
![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" }
<figcaption>WF Team Highlight with Events Plugin</figcaption>
</figure>

### Strip Setup
By default, vatSys strips will be set to show in *Alphabetical* Order.
This must be changed to be ordered by **Time**, as shown below.
Expand All @@ -48,6 +63,8 @@ This must be changed to be ordered by **Time**, as shown below.
<figcaption>Change to Time</figcaption>
</figure>

By default, the OzStrips Preactive bay will already be ordered by when the aircraft connected to VATSIM, from top to bottom.

### Runway Selection
Aircraft that are unable to accept Runway 12/30 due to operational requirements shall be assigned Runway 05/23 (as appropriate based on Runway Mode).

Expand All @@ -63,6 +80,8 @@ Departures from Runway 12 shall be given the AAE frequency (118.2).
### PDCs
PDCs will be in use by default, to avoid frequency congestion. ACD shall send a PDC to each aircraft as they connect. Upon successful readback of the PDC, ACD shall direct the pilot to contact SMC when ready for pushback or taxi.

Work through the OzStrips Preactive bay from *top to bottom* when sending PDCs.

## Surface Movement Control (SMC)
### Areas of Responsibility
<figure markdown>
Expand All @@ -88,6 +107,11 @@ All aerodrome controllers must be familiar with the VATPAC [recommended workflow

Ensure the Queue function is used to actively to keep track of the order of requests.

A Custom `PDC SENT` bar should be created in the Preactive window, to keep track of who has and hasn't received a PDC.

### A388 Parking
YPAD does not have any gates suitable for A388 parking. A388s must be instructed to park off-apron on the grass, to ensure they do not block any parking spots or taxiways.

### Eastern Terminal Taxi Routes
During **all** Runway Modes, aircraft shall be instructed to taxi in the following area in a **counter-clockwise** pattern. Aircraft shall be instructed to **pushback** facing **South-West** (Tail Right).

Expand Down
22 changes: 22 additions & 0 deletions docs/worldflight/Aerodromes/brisbane.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,24 @@ Ensure **all flight plans** are checked for compliance with the approved WF Rout

`DCT BN H91 IGDAM H652 TESAT DCT`

**OzStrips** will flag any *non-compliant* WF route.

If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC.

!!! example
**BN ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YSSY VIA SANEG H91 IGDAM H652 TESAT DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."*

### WorldFlight Teams
[WorldFlight Teams](../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority.

!!! tip
The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}

<figure markdown>
![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" }
<figcaption>WF Team Highlight with Events Plugin</figcaption>
</figure>

### Strip Setup
By default, vatSys strips will be set to show in *Alphabetical* Order.
This must be changed to be ordered by **Time**, as shown below.
Expand Down Expand Up @@ -62,6 +77,8 @@ Departures from Runway 01R and 19R shall be given the BDS frequency (118.45).
### PDCs
PDCs will be in use by default, to avoid frequency congestion. ACD shall send a PDC to each aircraft as they connect. Upon successful readback of the PDC, ACD shall direct the pilot to contact SMC when ready for pushback or taxi.

Work through the OzStrips Preactive bay from *top to bottom* when sending PDCs.

## Surface Movement Control (SMC)
### Pushback Delays
SMC Domestic and South will be responsible for delaying aircraft's pushback requests, in order to avoid overloading the taxiways.
Expand All @@ -73,6 +90,11 @@ All aerodrome controllers must be familiar with the VATPAC [recommended workflow

Ensure the Queue function is used to actively to keep track of the order of requests.

A Custom `PDC SENT` bar should be created in the Preactive window, to keep track of who has and hasn't received a PDC.

### A388 Parking
There are only 6 stands suitable for A388 parking (refer to [YBBN Apron Chart](https://www.airservicesaustralia.com/aip/current/dap/BBNAP05-162_05SEP2024.pdf){target=new}). If these are all occupied, A388 aircraft must be instructed to park off-apron on grass.

## Tower Control (ADC)
### Departure Spacing
Ensure that a minimum of **90 second** spacing is applied between subsequent departures from the same runway.
Expand Down
Loading

0 comments on commit 4107cd2

Please sign in to comment.