diff --git a/docs/.pages b/docs/.pages index ce6d1a2e1..b84d2032a 100644 --- a/docs/.pages +++ b/docs/.pages @@ -5,6 +5,7 @@ nav: - Enroute: enroute - Oceanic: oceanic - Pacific: pacific + - WorldFlight: worldflight - Separation Standards: separation-standards - Client Usage: client - Controller Skills: controller-skills diff --git a/docs/aerodromes/classc/Darwin.md b/docs/aerodromes/classc/Darwin.md index 2d87eca87..b66f951f2 100644 --- a/docs/aerodromes/classc/Darwin.md +++ b/docs/aerodromes/classc/Darwin.md @@ -68,9 +68,9 @@ d) Helo: `A010` !!! example - **DN ADC** -> **DN TCU**: "Next, ABC, runway 18" - **DN TCU** -> **DN ADC**: "ABC, Track Extended Centreline, unrestricted" - **DN ADC** -> **DN TCU**: "Track Extended Centreline, unrestricted, ABC" + **DN ADC** -> **DN TCU**: "Next, EOC, runway 18" + **DN TCU** -> **DN ADC**: "EOC, Track Extended Centreline, unrestricted" + **DN ADC** -> **DN TCU**: "Track Extended Centreline, EOC" All departures from 18/36 require departure coordination with **DN TCU** diff --git a/docs/worldflight/.pages b/docs/worldflight/.pages new file mode 100644 index 000000000..7d1167854 --- /dev/null +++ b/docs/worldflight/.pages @@ -0,0 +1,5 @@ +nav: + - Overview: index.md + - Aerodromes + - Terminal Areas + - Enroute \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/.pages b/docs/worldflight/Aerodromes/.pages new file mode 100644 index 000000000..8646360d9 --- /dev/null +++ b/docs/worldflight/Aerodromes/.pages @@ -0,0 +1,9 @@ +title: Aerodromes +nav: + - sydneydep.md + - adelaide.md + - perth.md + - darwin.md + - portmoresby.md + - brisbane.md + - sydneyarr.md \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/adelaide.md b/docs/worldflight/Aerodromes/adelaide.md new file mode 100644 index 000000000..a2480c010 --- /dev/null +++ b/docs/worldflight/Aerodromes/adelaide.md @@ -0,0 +1,231 @@ +--- + title: 2. Adelaide (YPAD) +--- + +--8<-- "includes/abbreviations.md" + +## Positions +An additional Non-Standard position for AD SMC will be used + +| Name | Callsign | Frequency | Login ID | +| ------------------ | -------------- | ---------------- | ---------------------------------------- | +| Adelaide SMC (West) | Adelaide Ground | 126.550 | **AD-W_GND** | + +## Runway Modes + +| Priority | Mode | +| ---------- | --- | +| 1 | 23A30AD | +| 2 | 05A30AD | +| 3 | 05A12D | +| 4 | 23A12D | + +*Single Runway* Operations shall be **avoided** at all costs. + +## 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` + +### 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. + +### 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. + +
+![Strips Menu](../img/strip1.png){ width="500" } +
Strips Menu
+
+ +
+![Change to Time](../img/strip2.png){ width="500" } +
Change to Time
+
+ +### 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). + +### SID Selection +Runway 05/23 Departures will be assigned the standard **GILES5** SID. + +Runway 12/30 Departures will be assigned the **AD4** RADAR SID. + +### Departure Frequency +Departures from Runway 05, 23, and 30 shall be given the AAW frequency (124.2). +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. + +## Surface Movement Control (SMC) +### Areas of Responsibility +
+![YPAD SMC Areas of Responsibility](../img/ypadsmcown.png){ width="700" } +
YPAD SMC Areas of Responsibility
+
+ +**Do not** give taxi instructions **beyond** your area of responsibility. Instruct aircraft to hold short of taxiways where responsibility changes to the next controller. + +!!! example + **AD SMC:** "QFA7448, Taxi via F2, A, Hold Short of K" + **QFA7448:** "Taxi via F2, A, Hold Short of K, QFA7448" + When QFA7448 is approaching K: + **AD SMC:** "QFA7448, Contact Ground 121.7" + +### Pushback Delays +SMC will be responsible for delaying aircraft's pushback requests, in order to avoid overloading the taxiways. + +If there are more than **5** aircraft in the queue at the Holding Point for *any runway*, do not approve any more pushback requests. + +#### OzStrips +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow) for OzStrips. + +Ensure the Queue function is used to actively to keep track of the order of requests. + +### 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). + +
+![Eastern Terminal Taxi Routes](../img/smcntaxi.png){ width="700" } +
Eastern Terminal Taxi Routes
+
+ +### Grass Taxiing +Due to limitations in the taxiway layout at YPAD, some aircraft will need to be taxied via Grass Routes, as shown below. + +
+![YPAD Grass Taxi Routes](../img/ypadsmcbase.png){ width="700" } +
YPAD Grass Taxi Routes
+
+ +### Taxi Routes + +#### 23A30AD +Aircraft shall taxi around the aerodrome in a **Clockwise** pattern. +Runway 23 Arrivals will vacate **right**, and taxi via **F**, **A**, **B1** to the apron. +Runway 30 Departures will taxi via *Eastern Grass*. +Runway 23 Departures *(Operational Requirement)* will queue to the South West on **T**, then North East on **A**. + +
+![23A30AD SMC Diagram](../img/23A30DSMC.png){ width="700" } +
23A30AD SMC Diagram
+
+ +#### 05A30AD +Aircraft shall taxi around the aerodrome in a **Clockwise** pattern. +Runway 05 Arrivals will vacate **left**, and taxi via **A**, **B1** to the apron. +Runway 30 Departures will taxi via *Eastern Grass*. +Runway 05 Departures *(Operational Requirement)* will taxi via *Eastern Grass* and *Southern Grass*. + +
+![05A30AD SMC Diagram](../img/05A30DSMC.png){ width="700" } +
05A30AD SMC Diagram
+
+ +#### 05A12D +Aircraft shall taxi around the aerodrome in a **Counter-Clockwise** pattern. +Runway 05 Arrivals will vacate **right**, and taxi via *Southern Grass* and *Eastern Grass* to join **T** at **T1**. +Runway 12 Departures will taxi via **A** and **G1**. +Runway 05 Departures *(Operational Requirement)* from the Eastern Terminal will taxi via **A** and **F**. +Runway 05 Departures *(Operational Requirement)* from the Western Terminal will taxi via *Western Grass* and **F**. + +
+![05A12D SMC Diagram](../img/05A12DSMC.png){ width="700" } +
05A12D SMC Diagram
+
+ +#### 23A12D +Aircraft shall taxi around the aerodrome in a **Counter-Clockwise** pattern. +Runway 23 Arrivals will vacate **left**, and taxi via *Southern Grass* and *Eastern Grass* to join **T** at **T1**. +Runway 12 Departures will taxi via **A** and **G1**. +Runway 23 Departures *(Operational Requirement)* will queue to the South West on **T**, then North East on **A**. +Runway 23 Departures *(Operational Requirement)* from the Western Terminal will taxi via *Western Grass* and **F3**, **F4**, Cross 23, *Southern Grass*, *Eastern Grass*, to join queue at **B2**. + +
+![23A12D SMC Diagram](../img/23A12DSMC.png){ width="700" } +
23A12D SMC Diagram
+
+ +## Tower Control (ADC) +### Departure Spacing +Ensure that a minimum of **90 second** spacing is applied between subsequent departures from the same runway. + +### AD4 Assigned Heading +Runway 12/30 Departures will be assigned the **AD4** RADAR SID, with the following Assigned Heading: + +| Runway Mode | Runway 12/30 Assigned Heading | +| ---------- | --- | +| 23A30AD | Runway Heading | +| 05A30AD | H230 | +| 05A12D | H060 | +| 23A12D | H180 | + +### Wake Turbulence Separation +Due to the tight sequence, there are times that [Wake Turbulence Separation](../../../separation-standards/waketurb/#runways) cannot practically be applied. + +When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. + +!!! example + **AD ADC:** "QFA887, A330 has just departed on the crossing runway. Caution Wake Turbulence. Runway 30, Cleared for Takeoff" + **QFA887:** "Cleared for Takeoff Runway 30, QFA887" + +### Managing Runway 30 Arrivals +When Runway 30 and 05/23 is in use for arrivals at YPAD, ADC must manage the speeds of aircraft on final to ensure they will not conflict on landing. + +Use two BRLs anchored on the runway intersection point to monitor distances and speeds. Leave the BRLs there and change them from aircraft to aircraft as the sequence continues. + +Aim for a minimum of **2nm** separation at the instersection. + +
+![Dual BRL at Intersection](../img/ypaddualbrl.png){ width="500" } +
Dual BRL at Intersection
+
+ +### Runway Vacating Instructions +#### 23A30AD +Landing aircraft will be instructed to vacate **right** (any exit). + +!!! note + Instruct aircraft that are observed vacating at **D2** to *remain this frequency*, as ADC owns the taxiway. + +#### 05A30AD +Runway 05 Arrivals will be instructed to vacate **left** (any exit). +Runway 30 Arrivals will be instructed to vacate **right** (any exit). + +!!! note + Instruct aircraft that are observed vacating at **D2** to *remain this frequency*, as ADC owns the taxiway. + +#### 05A12D +Landing aircraft will be instructed to vacate **right** via *Southern Grass* or **D2**. + +#### 23A12D +Landing aircraft will be instructed to vacate **left** via *Southern Grass*. + +## ATIS +When 05 is in use for Arrivals, The ATIS OPR INFO shall include: +`EXP CLR VIA PDC. ADVISE ON FIRST CONTACT WITH DELIVERY IF YOU REQUIRE RUNWAY 05` + +When 23 is in use for Arrivals, The ATIS OPR INFO shall include: +`EXP CLR VIA PDC. ADVISE ON FIRST CONTACT WITH DELIVERY IF YOU REQUIRE RUNWAY 23` + +## Coordination +### AD TCU +#### Auto Release +Standard as per [YPAD Local Instructions](../../../aerodromes/classc/Adelaide/#auto-release), with the exception of auto-release being available for **12/30 Departures** assigned the following *Standard Assignable Departure Headings*: + +| Runway Mode | Runway 12/30 Assigned Heading | +| ---------- | --- | +| 23A30AD | Runway Heading | +| 05A30AD | H230 | +| 05A12D | H060 | +| 23A12D | H180 | + +#### Departures Controller +Departures from Runway 05, 23, and 30 shall be handed off to AAW. +Departures from Runway 12 shall be handed off to AAE. \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/brisbane.md b/docs/worldflight/Aerodromes/brisbane.md new file mode 100644 index 000000000..2316cdf51 --- /dev/null +++ b/docs/worldflight/Aerodromes/brisbane.md @@ -0,0 +1,124 @@ +--- + title: 6. Brisbane (YBBN) +--- + +--8<-- "includes/abbreviations.md" + +## Runway Modes + +| Priority | Mode | +| ---------- | --- | +| 1 | 01 PROPS | +| 2 | 19 PROPS | + +*Single Runway* Operations and *SODPROPS* shall not be used. + +## Airways Clearance Delivery (ACD) +### Flight Plan Compliance +Ensure **all flight plans** are checked for compliance with the approved WF Route: + +`DCT BN H91 IGDAM H652 TESAT DCT` + +### 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. + +### 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. + +
+![Strips Menu](../img/strip1.png){ width="500" } +
Strips Menu
+
+ +
+![Change to Time](../img/strip2.png){ width="500" } +
Change to Time
+
+ +### Runway Selection +Runway **01R/19R** will be the primary runway for departures. + +**Heavy** and **Super** aircraft **must** be assigned Runway **01R/19R**. + +**Medium** and **Light** aircraft *may* be assigned Runway **01L/19L** at the discretion of the ACD controller to balance departing traffic. + +!!! note + Be mindful that 01L/19L Departures will incur additional delays, due to it being the primary arrival runway. + +### SID Selection + +| Runway | SID | +| ---------- | --- | +| 01L | BN4 | +| 01R | SANEG1 | +| 19L | BN4 | +| 19R | BN4 | + +### Departure Frequency +Departures from Runway 01L and 19L shall be given the BDN frequency (133.45). +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. + +## 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. + +If there are more than **5** aircraft in the queue at the Holding Point for *any runway*, do not approve any more pushback requests. + +#### OzStrips +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow) for OzStrips. + +Ensure the Queue function is used to actively to keep track of the order of requests. + +## Tower Control (ADC) +### Departure Spacing +Ensure that a minimum of **90 second** spacing is applied between subsequent departures from the same runway. + +### BN4 Assigned Heading +Runway 01L, 19L and 19R Departures will be assigned the **BN4** RADAR SID, with the following Assigned Heading: + +| Runway | Assigned Heading | +| ---------- | --- | +| 01L | H340 | +| 19L | H160 | +| 19R | H210 | + +## ATIS +### Approach Expectation +#### 01 PROPS + +| Cloud Base | Visibility | Approach | +| -----------------------| -------------- | -------------------------------------| +| >3000FT | >5000M | `EXP INDEP VISUAL APCH. DO NOT PASS THRU ASSIGNED RWY CL` | +| Between 2000FT & 3000FT| >5000M | `EXP INSTR APCH THEN INDEP VISUAL APCH WHEN VISUAL`| +| Below 2000FT **or** | <5000M | `EXP INSTR APCH` | + +#### 19 PROPS + +| Cloud Base / Visibility | Approach | +| -----------------------| -------------------------------------| +| >1700FT **and** >5000m | `EXP INDEP VISUAL APCH. DO NOT PASS THRU ASSIGNED RWY CL` | +| <1700FT **or** <5000m | `EXP INSTR APCH` | + +### OPR INFO +The ATIS OPR INFO shall include: +`EXP CLR VIA PDC. INDEPENDENT PARL APPROACHES AND DEPS IN PROGRESS` + +## Coordination +### BDN/BDS +#### Auto Release +Available for aircraft assigned `A060`, and: + +| Runway | SID | Assigned Heading | +| ---------- | --- | --- | +| 01L | BN4 | H340 | +| 01R | SANEG1 | - | +| 19L | BN4 | H160 | +| 19R | BN4 | H210 | + +#### Departures Controller +Departures from Runway 01L and 19L shall be handed off to BDN. +Departures from Runway 01R and 19R shall be handed off to BDS. \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/darwin.md b/docs/worldflight/Aerodromes/darwin.md new file mode 100644 index 000000000..4c20fde14 --- /dev/null +++ b/docs/worldflight/Aerodromes/darwin.md @@ -0,0 +1,120 @@ +--- + title: 4. Darwin (YPDN) +--- + +--8<-- "includes/abbreviations.md" + +## Runway Modes +Single runway operations on either **runway 11 or 29** will be in use for all aircraft. Runway 18/36 will not be available for arrivals and departures, due to it's use as a taxiway for some aircraft. + +## Airways Clearance Delivery (ACD) +### Flight Plan Compliance +Ensure **all flight plans** are checked for compliance with the approved WF Route: + +`DCT DN Y25 RUPEG DCT IGOPO B598 ESKIM DCT GUMBU DCT PY DCT` + +### 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. + +### 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. + +
+![Strips Menu](../img/strip1.png){ width="500" } +
Strips Menu
+
+ +
+![Change to Time](../img/strip2.png){ width="500" } +
Change to Time
+
+ +### SID Selection +Runway 11 Departures shall be issued the **RUPEG2** SID. +Runway 29 Departures shall be issued the **DN7** RADAR SID. + +### Departure Frequency +Regardless of Runway in use, Departure frequency shall be DAE (**125.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. + +## Surface Movement Control (SMC) +### Pushback Delays +SMC will be responsible for delaying aircraft's pushback requests, in order to avoid overloading the taxiways. + +If there are more than **5** aircraft in the queue at any Holding Point, do not approve any more pushback requests. Instead, use the queue function to keep track of who is awaiting push. + +#### OzStrips +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow) for OzStrips. + +Ensure the Queue function is used to actively to keep track of the order of requests. + +### Taxi Routes +#### Grass Taxiing +Due to the taxiway layout at YPDN, some aircraft may need to taxi via temporary grass taxiways, as shown below: + +
+![YPDN Grass Taxi Routes](../img/ypdngrass.png){ width="700" } +
YPDN Grass Taxi Routes
+
+ +#### Runway 11 +Aircraft from the RPT apron should taxi outbound via **B2** and **Z** to holding point **C4**. Aircraft from the southwestern apron should taxi outbound via **C2** to holding point **A1**. **C3** *should not* be used as a holding point. + +Aircraft vacating runway 11 to the left (north) should be instructed to taxi via the **northern grass** and **E2** to the bay. Aircraft vacating to the right (south) should be instructed to taxi via **A**, **runway 18**, and **C1** to the southwestern apron. Alternatively, they may park at the *BRA* or *FRA* aprons. + +#### Runway 29 +Aircraft from the RPT apron should taxi outbound via **E2** and the **northern grass**. Aircraft from the southwestern apron should taxi outbound via **C1**, **runway 36**, and **A** to holding point **A6**. + +Aircraft vacating runway 29 to the right (north) should be instructed to taxi via **Z** (if required) and **B2** to the bay. Aircraft vacating to the left (south) will be instructed by ADC to vacate at **C3** or **A1**. They should be instructed to taxi via **A1** (if required) and **C2** to the southwestern apron. + +## Tower Control (ADC) +### Departure Spacing +Ensure that a minimum of **90 second** spacing is applied between subsequent departures from the same runway. + +### DN7 Assigned Heading +Departures from Runway 29 will be assigned the **DN7** SID with an assigned heading of **H130**. + +### Wake Turbulence Separation +Due to the tight sequence, there are times that [Wake Turbulence Separation](../../../separation-standards/waketurb/#runways) cannot practically be applied. + +When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. + +!!! example + **DN ADC:** "QFA887, A330 has just departed on the crossing runway. Caution Wake Turbulence. Runway 29, Cleared for Takeoff" + **QFA887:** "Cleared for Takeoff Runway 29, QFA887" + +### Runway Vacating Instructions +ADC should assess traffic congestion on both the north and south sides of the aerodrome, and direct pilots to vacate towards the least congested side. + +#### Runway 11 +Aircraft intended for the northern aprons should be instructed to vacate at either **E2** or via the **northern grass** if they miss it. Aircraft intended for the southwestern apron should be instructed to vacate on any taxiway to the right. + +!!! example + **DN ADC**: "QFA25, vacate to the right, runway 11, cleared to land" + +#### Runway 29 +Aircraft intended for the northern aprons should be instructed to vacate at either **B2** or **runway 36**. This way, any pilots who miss the crossing runway can still vacate via **C4**. Aircraft intended for the southwestern apron should be instructed to vacate at either **C3** or **A1**. + +!!! important + It is **vital** that aircraft do not vacate left (south) prior to runway 36, as this will cause significant conflict with the outbound taxi route and likely to lead to the aircraft being required to disconnect. If an aircraft slows down rapidly, consider instructing them to vacate to the right via **B2** or reminding them to keep their speed up and roll through to vacate at **C3**. + +## ATIS +The ATIS OPR INFO shall include: +`EXP CLR VIA PDC` + +## Coordination +### DN TCU +#### Auto Release +Available for aircraft assigned `F180`, and: + +| Runway | SID | Assigned Heading | +| ---------- | --- | --- | +| 11 | RUPEG2 | - | +| 29 | DN7 | H130 | + +#### Departures Controller +All departures shall be handed off to DAE. +DAW has *No Restrictions or Requirements* on Runway 29 Departures. \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/perth.md b/docs/worldflight/Aerodromes/perth.md new file mode 100644 index 000000000..28e9925d4 --- /dev/null +++ b/docs/worldflight/Aerodromes/perth.md @@ -0,0 +1,148 @@ +--- + title: 3. Perth (YPPH) +--- + +--8<-- "includes/abbreviations.md" + +## Runway Modes + +| Priority | Mode | Operation | +| ---------- | --- | --- | +| 1 | 24A21D | [Simultaneous Independent Crossing Runway Operations](#24a21d) | +| 2 | 03A06D | [Land and Hold Short Operations](#03a06d) | + +*Single Runway* Operations shall be **avoided** at all costs. + +### 24A21D +Simultaneous Independent Crossing Runway Operations will be in use, allowing aircraft to depart from Runway 21 without conflicting with Runway 24 arrivals. + +Runway 21 TORA from Intersection **P** is **2000m**. + +Expect some arrivals to be landing on Runway 21 due to operational requirements. + +### 03A06D +Land and Hold Short Operations (LAHSO) will be in use, allowing aircraft to land on Runway 03 without conflicting with Runway 06 departures. + +Runway 03 LDA to Runway **06/24** Intersection is **2355m**. + +!!! example + **PH ADC:** "GTI1471, 737 departing on Crossing Runway. Hold Short Runway 06. Cleared to land Runway 03" + **GTI1471:** "Cleared to land Runway 03, GTI1471" + **PH ADC:** "QFA365, 747 landing on Crossing Runway will Hold Short. Runway 06, Cleared for takeoff" + **QFA365:** "Cleared for takeoff Runway 06, QFA365" + +Aircraft that are unable to Land and Hold Short of Runway 06 will have `XX` entered in their scratchpad by preceding controllers. + +## Airways Clearance Delivery (ACD) +### Flight Plan Compliance +Ensure **all flight plans** are checked for compliance with the approved WF Route: + +`DCT PH Y15 ESDEG Q587 IGLUT T58 SAPDA A585 IPKON IPKO2G` + +### 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. + +### 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. + +
+![Strips Menu](../img/strip1.png){ width="500" } +
Strips Menu
+
+ +
+![Change to Time](../img/strip2.png){ width="500" } +
Change to Time
+
+ +### 03A06D +All Medium and Light aircraft are *assumed* to be able to accept Runway 06 for Departure. + +Heavy and Super aircraft must be **queried** if they are able to accept Runway 06 for Departure. + +!!! note + *Requests* for Runway 03 cannot be facilitated. The aircraft must **operationally require** longer than *2163m TORA* to receive it. + +Aircraft that *operationally require* Runway 03 shall be assigned it. + +### SID Selection +Departures from Runway 06 will be assigned the **PH7** SID. +Departures from Runway 03 and 21 will be assigned the standard **AVNEX5** SID. + +### 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. + +## Surface Movement Control (SMC) +### Pushback Delays +SMC East and West will be responsible for delaying aircraft's pushback requests, in order to avoid overloading the taxiways. + +If there are more than **5** aircraft in the queue at the Holding Point for *any runway*, do not approve any more pushback requests. + +#### OzStrips +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow) for OzStrips. + +Ensure the Queue function is used to actively to keep track of the order of requests. + +### Runway 21 Departures +By default, all aircraft will be assigned Intersection **P** for departure. Verify with **Heavy** and **Super** aircraft when they request taxi if they can accept Intersection **P**. + +!!! note + *Requests* for the full length runway cannot be facilitated. The aircraft must **operationally require** longer than *2000m TORA* to receive it. + +Aircraft from the Western Apron shall be taxied via **D** and **N**. + +Aircraft that cannot accept Intersection **P** for departure will be assigned a **full length** departure. + +### Runway 06 Departures +Ensure that all aircraft queue for Runway 06 to the South East, via **A** and **V**. + +
+![Runway 06 Queue Paths](../img/06queue.png){ width="500" } +
Runway 06 Queue Paths
+
+ +This will avoid blocking up the Western Apron, and ensure aircraft have room to pushback. + +### Runway 03 Arrivals +Aircraft for the Western Apron will be instructed to vacate **right**. These aircraft shall be taxied via **C**, **W** and **B** to remain clear of aircraft taxiing for departure. + +## Tower Control (ADC) +### Runway 21 Full Length Departures +Full Length Departures have **equal priority** to aircraft that are compliant with Simultaneous Independent Crossing Runway Operations. However, Full Length departures may incur additional delays while being separated from Runway 24 Arrivals. + +!!! tip + Ensure the OzStrips queue bay is used actively to keep track of the queue. + +### Runway 06 Departures +Departures from Runway 06 will be assigned the **PH7** SID, with an Assigned Heading of **Runway Heading**. + +### Runway 03 Arrivals +Instruct **all** Runway 03 Arrivals to vacate **right**, even if they are for the Western Apron. + +### Departure Spacing +Ensure that a minimum of **90 second** spacing is applied between subsequent departures from the same runway. + +### Wake Turbulence Separation +Due to the tight sequence, there are times that [Wake Turbulence Separation](../../../separation-standards/waketurb/#runways) cannot practically be applied. + +When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. + +!!! example + **PH ADC:** "EVY30, 777 has just departed from the crossing runway. Caution Wake Turbulence. Runway 24, Cleared to Land" + **EVY30:** "Cleared to Land Runway 24, EVY30" + +## ATIS +The ATIS OPR INFO shall include: +`EXP CLR VIA PDC` + +During 24A21D, the ATIS OPR INFO shall include: +`SIMUL INDEP CROSSING RWY OPS IN PROG` + +During 03A06D, the ATIS OPR INFO shall include: +`LAHSO IN PROG. RWY 03 LANDING DISTANCE AVBL 2355 METRES` + +## Coordination +### PH TCU +#### Auto Release +Standard as per [PH TCU Local Instructions](../../../terminal/perth/#ph-adc), with the exception of auto-release being available for **06 Departures** assigned **Runway Heading** during the the [03A06D Runway Mode](#03a06d) \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/portmoresby.md b/docs/worldflight/Aerodromes/portmoresby.md new file mode 100644 index 000000000..dfaa7f853 --- /dev/null +++ b/docs/worldflight/Aerodromes/portmoresby.md @@ -0,0 +1,102 @@ +--- + title: 5. Port Moresby (AYPY) +--- + +--8<-- "includes/abbreviations.md" + +## Positions +An additional Non-Standard position for AYPY ACD will be used + +| Name | ID | Callsign | Frequency | Login ID | +| ------------------ | --------------| -------------- | ---------------- | --------------------------------------| +| Port Moresby Delivery | AYPY ACD | Jacksons Delivery | 124.400 | AYPY_DEL | + +## Airways Clearance Delivery (ACD) +### Flight Plan Compliance +Ensure **all flight plans** are checked for compliance with the approved WF Route: + +`DCT PY DCT LOTGU DCT VIPAM B220 KELPI Y89 BESBO Y177 BN DCT` + +### 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. + +### 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. + +
+![Strips Menu](../img/strip1.png){ width="500" } +
Strips Menu
+
+ +
+![Change to Time](../img/strip2.png){ width="500" } +
Change to Time
+
+ +### SID Selection +All aircraft shall be issued the **LOTGU1** SID. + +### 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. + +## Surface Movement Control (SMC) +### Runway 14R/32L +Runway 14R/32L will be used for taxiing. The Runway is released to SMC by default. + +*Southern Grass* Taxiway shall be used for Runway 32R departures queuing. It may also be used for Runway 14L Arrivals vacating. + +Standard taxi directions are shown below. + +
+![AYPY Standard Taxi Routes](../img/aypysmc.png){ width="700" } +
AYPY Standard Taxi Routes
+
+ +### Pushback Delays +SMC will be responsible for delaying aircraft's pushback requests, in order to avoid overloading the taxiways. + +If there are more than **5** aircraft in the queue at the Holding Point for the departure runway, do not approve any more pushback requests. + +#### OzStrips +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow) for OzStrips. + +Ensure the Queue function is used to actively to keep track of the order of requests. + +## Tower Control (ADC) +### Runway 14R/32L Release +Runway 14R/32L will be used for taxiing. The Runway is released to SMC by default. + +### Departure Spacing +Ensure that a minimum of **90 second** spacing is applied between subsequent departures from the same runway. + +### Wake Turbulence Separation +Due to the tight sequence, there are times that [Wake Turbulence Separation](../../../separation-standards/waketurb/#runways) cannot practically be applied. + +When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. + +!!! example + **AYPY ADC:** "ANG3, 747 has just departed. Caution Wake Turbulence. Runway 32L, Cleared for Takeoff" + **ANG3:** "Cleared for Takeoff Runway 32L, ANG3" + +### Runway Vacating Instructions +To minimise runway occupancy, it is essential that aircraft vacate the runway without delay. ADC shall instruct all arriving aircraft to vacate via the following exits when issued a landing clearance: + +| Landing Runway | Exit | +| -------------- | ---- | +| 14L | M | +| 32R | F | + +If aircraft miss these exits, they should be instructed to vacate via **A** (landing 32R) or via **the grass** (landing 14L) without delay. + +## ATIS +The ATIS OPR INFO shall include: +`EXP CLR VIA PDC` + +## Coordination +#### Auto Release +Available for aircraft assigned: + +- A Runway nominated on the ATIS; and +- The **LOTGU1** SID; and +- `A080` \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/sydneyarr.md b/docs/worldflight/Aerodromes/sydneyarr.md new file mode 100644 index 000000000..975eaa039 --- /dev/null +++ b/docs/worldflight/Aerodromes/sydneyarr.md @@ -0,0 +1,66 @@ +--- + title: 7. Sydney (YSSY) Arrivals +--- + +--8<-- "includes/abbreviations.md" + +## Runway Modes +**16 PROPS** and **34 PROPS** are the *preferred* Runway Modes, with equal preference. + +Due to the nature of the event, a non-standard maximum crosswind limitation has been approved up to **30 knots**. A single runway mode should only be considered if the crosswind exceeds this figure. + +Runway mode changes will be extremely difficult, so ensure an appropriate mode is chosen with consideration to the forecast wind values over the course of the event. + +## Airways Clearance Delivery (ACD) +The ACD role will perform as normal. Expect a handful of departures who want to maximise the ATC coverage. Normal departure procedures apply for all aircraft. + +## Surface Movement Control (SMC) +### OzStrips +With two SMC controllers online, utilise [strip bay bars](../../client/towerstrips.md#multiple-adcsmc-positions) to keep the **Taxi** and **Holding Point** strip bays organised. + +### Departures +It is unlikely that Coordinator will be open, so normal outbound taxi procedures apply. If Coordinator is online, refer to the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow). + +### Separation Assurance +Both SMC positions must be careful to ensure separation is assured at all times, particularly through the complex taxiway intersections at Sydney. + +With runways 34L/R in use for arrivals/departures, SMC East should consider instructing aircraft taxiing southbound on Charlie to initially hold short of Golf (to avoid conflict with aircraft taxiing from DOM2 and eastward). After crossing the runway, consider instructing aircraft to hold short of Bravo 10 (to avoid conflict with inbound aircraft from 34R). Inbound aircraft should be instructed to hold short of Bravo 8 (to give way to aircraft vacating 34L at the rapid exit). + +During PROPS, maximum use of runway 07/25 should be utilised to enable an east/westbound split between taxiway Golf and the runway. + +SMC West should protect the Alpha 2 rapid exit and utilise taxiways Yankee and Juilet as a second path for aircraft when Golf and Alpha are already occupied. Be careful taxiing outbound aircraft south of Juliet while an aircraft is landing on runway 34L, as they will plan to vacate via Alpha 2. + +### Runway Crossings +Due to the full arrival sequence, runway crossings (across 16R/34L) should be avoided where possible. Landing aircraft are expected to vacate to the left or right, depending on their intended parking position. If an aircraft wishes to taxi to an apron on the other side of the runway, encourage them to find a new parking position on the same side to where they currently are. + +If a crossing is required, coordinate *early* with ADC, who may obtain assurance from a landing aircraft that they will vacate via a specified runway exit. ADC will then issue crossing instructions to SMC while the landing aircraft is still on the runway. + +## Tower Control (ADC) +### OzStrips +With two SMC controllers online, utilise [strip bay bars](../../client/towerstrips.md#multiple-adcsmc-positions) to keep the **Holding Point** and **Runway** strip bays organised. + +### Runway Vacating Instructions +To avoid creating conflict for SMC, ADC shall instruct all arriving aircraft to vacate via the following exits when issued a landing clearance: + +| Landing Runway | Exit | +| -------------- | ---- | +| 16R | B7 (left) or A4 (right) | +| 16L | T3 or T4 | +| 34L | A2 (left) or B9 (right) | +| 34R | T2 or U1 | + +!!! example + **SY ADC**: "JST554, vacate via B9 to the right, runway 34L, cleared to land" + +### Runway Efficiency +The success of the event will be decided by ADC's ability to minimise runway occupancy and maximise runway efficiency. Where necessary, instruct landing aircraft to 'vacate without delay'. + +While runway crossings will be minimised, should a crossing be required, instruct a landing aircraft to report when they are assured of taking the assigned rapid exit. Once that assurance has been received, instruct SMC to cross the applicable aircraft (provided they are further upwind than the assured runway exit). + +!!! example + **SY ADC**: "QFA451, report when assured of vacating via B9 to the right, runway 34L, cleared to land" + +If any aircraft need to depart during the arrival window, ensure that maximum efficiency is achieved by instructing them to line up as soon as the landing aircraft has cleared the threshold. Avoid go arounds at all costs, and if necessary, delay the departing aircraft where a gap between two arrivals is too tight. + +## Coordination +Standard as per [YSSY Local Instructions](../../../aerodromes/classc/Sydney/#auto-release). \ No newline at end of file diff --git a/docs/worldflight/Aerodromes/sydneydep.md b/docs/worldflight/Aerodromes/sydneydep.md new file mode 100644 index 000000000..18050c882 --- /dev/null +++ b/docs/worldflight/Aerodromes/sydneydep.md @@ -0,0 +1,178 @@ +--- + title: 1. Sydney (YSSY) Departures +--- + +--8<-- "includes/abbreviations.md" + +## Positions +An additional Non-Standard position for Sydney ACD will be used + +| Name | ID | Callsign | Frequency | Login ID | +| ------------------ | --------------| -------------- | ---------------- | --------------------------------------| +| [Sydney (Assistant) Delivery](#dual-acd-controller-operations) | SY-C_DEL | N/A | N/A | SY-C_DEL | + +## Runway Modes +**16 PROPS** and **34 PROPS** are the available Runway Modes, with equal preference. 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 TESAT A576 KADOM H44 BORLI W451 MIA H309 AD DCT` + +### 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. + +### 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. + +
+![Strips Menu](../img/strip1.png){ width="500" } +
Strips Menu
+
+ +
+![Change to Time](../img/strip2.png){ width="500" } +
Change to Time
+
+ +### Dual ACD Controller Operations +YSSY will have a non-standard second ACD Controller. + +#### SY-C_DEL +**SY-C_DEL** will be responsible for: + +- Checking [Flight Plan compliance](#flight-plan-compliance) +- Entering Flight Data (Setting [Runway](#runway-selection), [SID](#sid-selection) and [CFL](../../../aerodromes/classc/Sydney/#auto-release)) +- Sending [PDCs](#pdcs) + +SY-C_DEL has *no frequency*, and will not talk to aircraft by voice. + +#### SY_DEL +**SY_DEL** will be responsible for: + +- Handling [PDC](#pdcs) Readbacks +- All the tasks of [SY-C_DEL](#sy-c_del) for aircraft that call for clearance + +### Runway Selection +By default, assign aircraft the departure runway that corresponds to their departure apron (ie, **16L/34R** on *East* Apron, **16R/34L** on *West* Apron). + +### SID Selection +Non-Standard SIDs are in use for Runway 16L and 34R. + +| Runway | SID | +| ---------- | --- | +| 16R | GROOK1KADOM | +| 34L | KADOM1 | +| 16L/34R | SY3 | + +### Departure Frequency +Departures from Runway 16R and 34L shall be given the SDN frequency (123.0). +Departures from Runway 16L and 34R shall be given the SDS frequency (129.7). + +### 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 Coordinator when ready for pushback or taxi. + +## Coordinator +Coordinator operations shall be conducted in accordance with the Sydney Aerodrome [Coordinator](../../aerodromes/classc/Sydney.md#sydney-coordinator) procedures, using the OzStrips plugin. + +!!! important + Official WorldFlight teams should be afforded priority when requesting pushback or taxi (if no pushback required), and placed ahead of other non-official aircraft. + +### OzStrips +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow) for OzStrips. + +Coordinator must place a `MONITOR GROUND EAST` & `MONITOR GROUND WEST` bar in the **Cleared Bay Queue** and queue any aircraft who request pushback or taxi (if no pushback required) in the Cleared Bay. + +
+![Coordinator Bars](../img/coordinatorbars.png){ width="500" } +
+ +When less than **three** strips are present below a particular `MONITOR GROUND` bar, Coordinator may instruct the bottom most aircraft in the queue to monitor that SMC frequency. + +
+![Coordinator Strips](../img/coordinatorstrips.png){ width="500" } +
An example of the Coordinator layout
+
+ +If three strips are already present below a respective bar, any subsequent aircraft who request pushback must be instructed to remain on the Coordinator frequency, and an estimated delay given if known. Place these strips in the **Cleared Bay Queue**, but above the respective `MONITOR GROUND` bars. The bottom-most strip is always at the front of any queue. + +!!! example + **QFA452**: "Sydney Coordinator, Qantas 452, bay 5, request pushback" + **SY COORD**: "Qantas 452, Sydney Coordinator, monitor ground 121.7" + ... + **VOZ318**: "Sydney Coordinator, Velocity 318, bay 39, request pushback" + **SY COORD**: "Velocity 318, Coordinator, remain this frequency, approximate 5 minute delay due traffic congestion" + +!!! important + Ensure aircraft are [squawking mode C and the correct code](../../client/towerstrips.md#strips) before instructing them to monitor ground. + +### Delay Expectation +Aircraft can expect **extensive** delays for Pushback during the event, possibly *multiple hours*. Try to keep pilots informed of their delay expectation, either by providing a figure in minutes, or a position in the queue. + +!!! example + **JST764**: "Sydney Coordinator, JST764, bay 55, request pushback" + **SY COORD**: "JST764, Coordinator, remain this frequency, number 62 in the queue" + +## Surface Movement Control (SMC) +### OzStrips +With two SMC controllers online, utilise [strip bay bars](../../client/towerstrips.md#multiple-adcsmc-positions) to keep the **Taxi** and **Holding Point** strip bays organised. + +### Departures +With Coordinator online, aircraft will request pushback on the Coordinator frequency and be told to monitor the applicable SMC frequency when appropriate. These pilots will be waiting for you to initiate contact with them. + +When workload (and holding point congestion) allows, issue pushback to the **bottom most** aircraft below the `MONITOR GROUND EAST` or `MONITOR GROUND WEST` bar (as appropriate) and move the strip to the **Pushback Bay**. + +!!! important + It is preferable to hold aircraft on the bay (where they aren't blocking taxiways or burning their holding fuel) when congestion leads to blocked holding points. Issue pushback with enough lead time to prevent large gaps in the departure sequence. + +### Separation Assurance +Both SMC positions must be careful to ensure separation is assured at all times, particularly through the complex taxiway intersections at Sydney. + +With runways 34L/R in use for departures, SMC East should consider instructing aircraft taxiing southbound on Charlie to initially hold short of Golf (to avoid conflict with aircraft taxiing from DOM2 and eastward). After crossing the runway, consider instructing aircraft to hold short of Bravo 10 (to avoid conflict with inbound aircraft from 34R). Inbound aircraft should be instructed to hold short of Bravo 8 (to give way to aircraft vacating 34L at the rapid exit). + +During PROPS, maximum use of runway 07/25 should be utilised to enable an east/westbound split between taxiway Golf and the runway. + +SMC West should protect the Alpha 2 rapid exit and utilise taxiways Yankee and Juilet as a second path for aircraft when Golf and Alpha are already occupied. Be careful taxiing outbound aircraft south of Juliet while an aircraft is landing on runway 34L, as they will plan to vacate via Alpha 2. + +## Tower Control (ADC) +### OzStrips +With two SMC controllers online, utilise [strip bay bars](../../client/towerstrips.md#multiple-adcsmc-positions) to keep the **Holding Point** and **Runway** strip bays organised. + +### Departure Spacing +While PROPS are in use, subsequent departures from the same runway **must** be spaced by **3 minutes**, to assist with arrival flow in to YPAD. + +If a single runway is in use for departures, subsequent departures **must** be spaced by **90 seconds**. + +### SY3 Assigned Heading +Runway 16L/34R Departures will be assigned the **SY3** RADAR SID, with an Assigned Heading of **H120**. + +### Runway Vacating Instructions +To avoid creating conflict for SMC, ADC shall instruct all arriving aircraft to vacate via the following exits when issued a landing clearance: + +| Landing Runway | Exit | +| -------------- | ---- | +| 16R | B7 (left) or A4 (right) | +| 16L | T3 or T4 | +| 34L | A2 (left) or B9 (right) | +| 34R | T2 or U1 | + +!!! example + **SY ADC**: "JST554, vacate via B9 to the right, runway 34L, cleared to land" + +## ATIS +The ATIS OPR INFO shall include: +`EXP CLR VIA PDC, ALL ACFT EXP INTERSECTION DEPARTURE` + +## Coordination +### SY TCU +#### Auto Release +Standard as per [YSSY Local Instructions](../../../aerodromes/classc/Sydney/#auto-release), with the exception of auto-release being available for the following: + +- 16L/34R Departure SID: **SY3** RADAR +- 16L/34R Standard Assignable Departure Heading: **H120** + +#### Departures Controller +Departures from Runway 16R and 34L shall be handed off to SDN. +Departures from Runway 16L and 34R shall be handed off to SDS. \ No newline at end of file diff --git a/docs/worldflight/Enroute/.pages b/docs/worldflight/Enroute/.pages new file mode 100644 index 000000000..955590aae --- /dev/null +++ b/docs/worldflight/Enroute/.pages @@ -0,0 +1,9 @@ +title: Enroute +nav: + - yssyypad.md + - ypadypph.md + - ypphwiii.md + - wammypdn.md + - ypdnaypy.md + - aypyybbn.md + - ybbnyssy.md \ No newline at end of file diff --git a/docs/worldflight/Enroute/aypyybbn.md b/docs/worldflight/Enroute/aypyybbn.md new file mode 100644 index 000000000..3580aa3b1 --- /dev/null +++ b/docs/worldflight/Enroute/aypyybbn.md @@ -0,0 +1,126 @@ +--- + title: 6. AYPY to YBBN +--- + +--8<-- "includes/abbreviations.md" + +## Positions +An additional Non-Standard position for AYPM CTR will be used + +| Name | ID | Callsign | Frequency | Login ID | +| ------------------ | --------------| -------------- | ---------------- | --------------------------------------| +| Port Moresby Centre | AYPM CTR | Moresby Centre | 123.400 | AYPM_CTR | +| Port Moresby (East) Centre | AYPE CTR | Moresby Centre | 125.600 | AYPE_CTR | + +## Sector Responsibilities +### Port Moresby (AYPE) CTR +AYPE CTR will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. + +Aircraft shall be handed off directly to TBP. ARE is skipped. + +!!! note + AYPE CTR will have better VHF coverage than TBP on aircraft until approximately **100nm South** of **VIPAM**. It is *advisable* to delay handing off aircraft to TBP until approximately that point. + +### Arafura East (ARE) +ARE has *no Restrictions or Requirements* on AYPY-YBBN aircraft. + +### Tabletop (TBP) +TBP will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. + +TBP may prime the KEN frequency (120.15) in order to get better VHF range on aircraft coming from AYPM CTR. Advise the AYPM CTR controller if you want handoffs on the KEN frequency instead of TBP. + +### Swampy (SWY) +SWY will be responsible for starting to form the sequence in to YBBN, by applying *speed control* in the cruise. + +### Keppel (KPL) +KPL will be responsible for issuing STAR clearances in to YBBN, and finalising the sequence using *speed control* and *vectors* in to YBBN. + +#### STARs +See [STAR Clearances](#star-clearances) + +### Burnett (BUR) +BUR will be responsible for finessing the sequence in to YBBN if required. + +BUR will take responsibility for the DOS subsector, to facilitate **ENLIP** arrivals. No additional frequencies will need to be primed to BUR. + +#### Sequencing +**All aircraft** must be instructed to cross **SMOKA** or **ENLIP** at **250 knots**, then *published STAR speeds*. + +!!! note + This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm). + +Minimum distance between arrivals at handoff to BAN/BAS is **10nm** (with no significant closing speed). + +## STAR Clearances +All aircraft shall be issued the **SMOKA1A** STAR for Runway **01L/19L** by default. + +### ENLIP Reclearance +To aid with distributing the arrival sequence, KPL may reclear aircraft DCT to **ENLIP** for the following ENLIP STAR: + +| Runway | STAR | +| ---------- | --- | +| 01R | ENLIP2A | +| 19R | ENLIP2X† | + +†Aircraft on the **Xray** STAR will still expect an *Independent Visual Approach* from that STAR, unless the ATIS indicates otherwise. + +Arrivals may, when suitable for the *sequence*, and clear of *01L/19R traffic*, be cleared DCT to the following points on the STAR: + +| Runway | DCT | +| ---------- | --- | +| 01R | MULNI | +| 19R | DRAIN | + +## Coordination +### AYPY DEP to AYPM CTR +Voiceless for all aircraft: + +- Assigned the lower of `F240` or the `RFL`; and +- Tracking via **NUPTA** + +All other aircraft going to AYPM CTR CTA will be **Heads-up** Coordinated. + +### KPL to BUR +Changes to Route and CFL are **permitted** within **50nm** of the boundary, without coordination, for sequencing purposes. +Aircraft must be tracking via **ENLIP** or **SMOKA** + +### BUR to BAS/BAN +#### Airspace +Non-Standard Airspace Division will be in use for BN TCU. Refer to [these diagrams](../../Terminal Areas/brisbane/#airspace-division). + +Runway **01L** and **19L** Arrivals will be handed off to BAN. +Runway **01R** and **19R** Arrivals will be handed off to BAS. + +#### Arrivals +Voiceless for all aircraft: + +- With ADES **YBBN**; and +- Assigned `A090`; and +- Assigned any of the following: + +| STAR | Runway | DCT Tracking available | +| ---------- | --- | --- | +| SMOKA1A | 01L | None | +| SMOKA1A | 19L | None | +| ENLIP2A | 01R | DCT **MULNI** | +| ENLIP2X | 19R | DCT **DRAIN** | + +All other aircraft coming from BUR/DOS CTA must be **Heads-up** Coordinated to BN TCU prior to **20nm** from the boundary. + +#### Between KPL/BUR and BFL +BFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +BFL must **voice coordinate** any changes to instructions after KPL/BUR has put a `<` on it. + +BFL will **voice coordinate** to KPL/BUR any aircraft that must be rerouted via **ENLIP** for **01R/19R**. + +!!! example + **BFL** -> **KPL**: "PAA001 via ENLIP for 01R please" + **KPL** -> **BFL**: "PAA001 via ENLIP for 01R, will be" + +KPL/BUR must **voice coordinate** any requests for *Track Shortening* or *CSR* to BFL. + +!!! tip + If in your judgement, the request won't be available due to the sequence, there is no need to voice coordinate the requests. Just deny them. \ No newline at end of file diff --git a/docs/worldflight/Enroute/wammypdn.md b/docs/worldflight/Enroute/wammypdn.md new file mode 100644 index 000000000..266ac3b60 --- /dev/null +++ b/docs/worldflight/Enroute/wammypdn.md @@ -0,0 +1,32 @@ +--- + title: 4. WAMM to YPDN +--- + +--8<-- "includes/abbreviations.md" + +## Sector Responsibilities +### Territory (TRT) +TRT is responsible for issuing STAR Clearances and all sequencing actions in to YPDN. + +TRT will be responsible for the TRT subsector **only**. + +#### STARs +All aircraft shall be issued the **ANUPA1A** STAR. + +#### Sequencing +**All aircraft** must be instructed to cross **ANUPA** at **250 knots**, then *published STAR speeds*. + +!!! note + This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm). + +Minimum distance between arrivals at handoff to DAW is **10nm** (with no significant closing speed). It is important to try not to exceed **15nm**, due to the large number of arrivals. + +## Coordination +### WAAF CTR to TRT +As per [Standard TRT coordination procedures](../../../enroute/Brisbane Centre/TRT/#international-waaf), All aircraft should be Heads-up Coordinated by WAAF CTR prior to **30 mins** from boundary. + +!!! tip + It may be prudent (especially if they are using vatSys) to set up a Voiceless Coordination Agreement with WAAF CTR, in order to reduce workload for both controllers. + +### TRT to DAW +Standard as per [TRT Local Instructions](../../../nroute/Brisbane Centre/TRT/#arrivalsoverfliers) \ No newline at end of file diff --git a/docs/worldflight/Enroute/ybbnyssy.md b/docs/worldflight/Enroute/ybbnyssy.md new file mode 100644 index 000000000..b70e665be --- /dev/null +++ b/docs/worldflight/Enroute/ybbnyssy.md @@ -0,0 +1,85 @@ +--- + title: 7. YBBN to YSSY +--- + +--8<-- "includes/abbreviations.md" + +## Sector Responsibilities +### Gold Coast (GOL) +GOL is responsible for reclearing certain aircraft via **OLTIN YAKKA MEPIL**. + +**All** aircraft that GOL receives from BDS/BDN on a heading *east* of **SANEG** shall be recleared via this amended tracking. + +Additionally, GOL may reclear more aircraft from the standard route to the amended **OLTIN YAKKA MEPIL** tracking, in order to keep a 50/50 balance between **BOREE** and **MEPIL** arrivals in to **YSSY**. +**Do not** reclear **Heavy** or **Super** aircraft via **MEPIL**. Leave them on planned route. + +### Inverell (INL) +INL will be responsible for starting to form the sequence in to YSSY, by applying *speed control* in the cruise. + +INL will be responsible for the INL subsector **only**. + +### Armidale (ARL) +ARL will be responsible for issuing STAR clearances in to YSSY, and finalising the sequence using *speed control* and *vectors* in to YSSY. + +ARL will be responsible for the ARL and MNN subsectors **only**. + +!!! tip + Early Handoffs to CNK (~30-50nm from boundary) are a great way to balance workload + +#### STARs + +| Fix | Runway | STAR | +| ---------- | --- | --- | +| BOREE | 16R | BOREE3P | +| BOREE | 34L | BOREE3A | +| MEPIL | 16L | MEPIL3 | +| MEPIL | 34R | MEPIL3 | + +### Cessnock (CNK) +CNK will be responsible for finessing the sequence in to YSSY if required. + +#### Sequencing +**All aircraft** must be instructed to cross **BOREE** or **MEPIL** at **250 knots**, then *published STAR speeds*. + +!!! note + This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm). + +Minimum distance between arrivals at handoff to SAN/SAS is **10nm** (with no significant closing speed). It is important to try not to exceed **15nm**, due to the large number of arrivals. + +## Coordination +### BDN/BDS to GOL +Voiceless for all aircraft: + +- Assigned the lower of `F180` or the `RFL`; and +- Tracking via **SANEG**; or +- East of **SANEG**, Assigned a Heading between **H180**-**H160**. + +All other aircraft going to GOL CTA will be **Heads-up** Coordinated. + +### ARL to CNK +Changes to Route and CFL are **permitted** within **50nm** of the boundary, without coordination, for sequencing purposes. +Aircraft must be tracking via **BOREE** or **MEPIL**. + +### CNK to SAS/SAN +Standard as per [ARL Local Instructions](../../../enroute/Brisbane Centre/ARL/#arrivalsoverfliers). + +**BOREE** Arrivals will be handed off to SAS. +**MEPIL** Arrivals will be handed off to SAN. + +#### Between ARL/CNK and SFL +SFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +SFL must **voice coordinate** any changes to instructions after ARL/CNK has put a `<` on it. + +SFL will **voice coordinate** to ARL/CNK any aircraft that must be rerouted via **OLTIN YAKKA MEPIL** for **16L/34R**. + +!!! example + **SFL** -> **ARL**: "ANZ361 via OLTIN for 34R please" + **ARL** -> **SFL**: "ANZ361 via OLTIN for 34R, will be" + +ARL/CNK must **voice coordinate** any requests for *Track Shortening* or *CSR* to SFL. + +!!! tip + If in your judgement, the request won't be available due to the sequence, there is no need to voice coordinate the requests. Just deny them. \ No newline at end of file diff --git a/docs/worldflight/Enroute/ypadypph.md b/docs/worldflight/Enroute/ypadypph.md new file mode 100644 index 000000000..3b69b5da3 --- /dev/null +++ b/docs/worldflight/Enroute/ypadypph.md @@ -0,0 +1,102 @@ +--- + title: 2. YPAD to YPPH +--- + +--8<-- "includes/abbreviations.md" + +## Positions +FOW is an additional non-standard sector for the event (Split from FOR). + +| Name | Callsign | Frequency | Login ID | +| ---- | -------- | --------- | -------- | +| Forrest West | Melbourne Centre | 131.700 | ML-FOW_CTR | + +## Sector Responsibilities +### Tailem Bend (TBD) +TBD has *no Restrictions or Requirements* on YPAD departures tracking DCT **LONLY**. + +### Augusta (AUG), Forrest (FOR), Forrest West (FOW) +AUG, FOR, and FOW will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. + +!!! caution + AUG and FOR should look out for aircraft converging at **LONLY** and **LESON** respectively, at the same time and level. Use vertical separation wherever possible. + +### Esperance (ESP) +ESP will be responsible for starting to form the sequence in to YPPH, by applying *speed control* in the cruise. + +ESP must also check for LAHSO compliance during the [03A06D Runway Mode](#03a06d-lahso). + +### Hyden (HYD) +HYD will be responsible for issuing STAR clearances in to YPPH, and finalising the sequence using *speed control* and *vectors* in to YPPH. + +HYD may vector in to CRS or JAR airspace if required for sequencing. + +#### STARs +All aircraft shall be issued the **KABLI1A** STAR. + +### Pingelly (PIY) +PIY will be responsible for finessing the sequence in to YPPH if required. + +PIY will be responsible for the PIY **subsector only**. + +#### Sequencing +**All aircraft** must be instructed to cross **KABLI** at **250 knots**, then *published STAR speeds*. + +!!! note + This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm). + +Minimum distance between arrivals at handoff to PHA is **10nm** (with no significant closing speed). It is important to try not to exceed **15nm**, due to the large number of arrivals. + +## YPPH Arrivals +### Runway Modes +Depending on wind limitations, there are two possible Runway Modes in use at YPAD. + +#### 24A21D +During 24A21D, **Heavy** and **Super** aircraft must be asked if they *operationally require* Runway 21 for arrival. + +Aircraft that operationally require Runway 21 may be cleared for the KABLI1A/21 without coordination. + +#### 03A06D (LAHSO) +During 03A06D, ESP must ask **Heavy** and **Super** aircraft if they are able to Land and Hold Short of Runway 06. + +Landing Distance Available (LDA) for Runway 03 LAHSO is **2355m**. + +Aircraft that are *unable* to Land and Hold Short of Runway 06 must have `XX` entered in their scratchpad. + +## Coordination +### AAW to AUG +Voiceless for all aircraft: + +- Assigned the lower of `F240` or the `RFL`; and +- Tracking via **GILES**; or +- North of **GILES**, DCT **LESON**; or +- South of **GILES**, DCT **LONLY** + +All other aircraft going to AUG CTA will be **Heads-up** Coordinated. + +### HYD to PIY +Changes to Route and CFL are **permitted** within **50nm** of the boundary, without coordination, for sequencing purposes. +Aircraft must be tracking via **MALUP** or **KABLI**, with the exception of: +**Runway 21** Arrivals may be assigned a Heading **North** of the **MALUP-KABLI** track, without coordination. + +### PIY to PHA +Standard as per [PIY Local Instructions](../../../enroute/Melbourne Centre/PIY/#arrivalsoverfliers), with the exception of: + +- During the [24A21D Runway Mode](#24a21d), arrivals assigned **Runway 21** may be handed off to PHA on a **Heading** *north* of the Runway 24 arrivals, without coordination. + +
+![PIY to PHA 24A21D](../img/PIY.png){ width="700" } +
PIY to PHA 24A21D
+
+ +#### Between PIY/HYD and PFL +PFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +PFL must **voice coordinate** any changes to instructions after PIY/HYD has put a `<` on it. + +PIY/HYD must **voice coordinate** any requests for *Track Shortening*, *CSR*, or *Victor/Xray STARs*, to PFL. + +!!! tip + If in your judgement, the request won't be available due to the sequence, there is no need to voice coordinate the requests. Just deny them. \ No newline at end of file diff --git a/docs/worldflight/Enroute/ypdnaypy.md b/docs/worldflight/Enroute/ypdnaypy.md new file mode 100644 index 000000000..31f4676f3 --- /dev/null +++ b/docs/worldflight/Enroute/ypdnaypy.md @@ -0,0 +1,57 @@ +--- + title: 5. YPDN to AYPY +--- + +--8<-- "includes/abbreviations.md" + +## Positions +ARW is an additional non-standard sector for the event (Split from ARA). + +| Name | Callsign | Frequency | Login ID | +| ---- | -------- | --------- | -------- | +| Arafura East | Brisbane Centre | 127.600 | BN-ARE_CTR | + +AYPE CTR will also be a non-standard split-off from AYPM CTR. They will manage AYPY departures (Not involved in this leg). + +## Sector Responsibilities +### Territory South (TRS) and Arafura (ARA) +TRS and ARW will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. + +### Arafura East (ARE) +ARA will be responsible for starting to form the sequence in to AYPY, by applying *speed control* in the cruise. + +### Port Moresby (AYPM) CTR +AYPM CTR will be responsible for issuing STAR Clearances and the final sequencing in to AYPY + +#### STARs +All aircraft shall be issued the **GUMBU1** STAR. + +#### Sequencing +**All aircraft** must be instructed to cross **GUMBU** at **250 knots**, then *published STAR speeds*. + +!!! note + This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm). + +Minimum distance between arrivals at handoff to AYPY APP is **10nm** (with no significant closing speed). It is important to try not to exceed **15nm**, due to the large number of arrivals. + +## Coordination +### DAE to TRS +Voiceless for all aircraft: + +- Assigned the lower of `F180` or the `RFL`; and +- Tracking via **RUPEG** + +All other aircraft going to TRS CTA will be **Heads-up** Coordinated. + +### AYPM CTR to AYPY APP +#### Airspace +The Vertical limits of the AYPY TCU are `SFC` to `F245`. + +#### Arrivals +Voiceless for all aircraft: + +- With ADES **AYPY**; and +- Assigned the **GUMBU1** STAR; and +- Assigned `A100` + +All other aircraft coming from AYPM CTR CTA must be **Heads-up** Coordinated to AYPY TCU prior to **20nm** from the boundary. \ No newline at end of file diff --git a/docs/worldflight/Enroute/ypphwiii.md b/docs/worldflight/Enroute/ypphwiii.md new file mode 100644 index 000000000..d7a232f1d --- /dev/null +++ b/docs/worldflight/Enroute/ypphwiii.md @@ -0,0 +1,44 @@ +--- + title: 3. YPPH to WIII +--- + +--8<-- "includes/abbreviations.md" + +## Sector Responsibilities +### Pingelly (PIY) +PIY has *no Restrictions or Requirements* on YPPH departures tracking DCT **ESDEG**. + +### Leeman (LEA) +LEA will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. + +!!! caution + During the 03A06D Runway Mode at YPPH, LEA should look out for aircraft converging at **ESDEG** at the same time and level. Use vertical separation wherever possible. + +### Geraldton (GEL), Meekatharra (MEK), Paraburdoo (PAR), Onslow (OLW) +GEL, MEK, PAR and OLW will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. + +Aircraft shall have their **identification terminated** on handoff to INE, and instructed to give a **PAVNU** Position Report on first contact. + +!!! example + **OLW:** "BTK6081, at PAVNU, Identification terminates. Contact Brisbane Radio 123.65 with PAVNU Position Report" + +### Indian East (INE) +INE will be responsible for ensuring [Procedural Separation](../../../separation-standards/procedural/) is in place between aircraft in the Enroute phase of flight. + +!!! tip + Since you will be busy, keep the separation as *simple* as possible. [10 minutes Longitudinal](../../../separation-standards/procedural/#same-track), or [Vertical](../../../separation-standards/procedural/#vertical). Using a mix of *Standard* and *Non-Standard* levels is **highly recommended** to assist with this + +## Coordination +### PHD to LEA +Voiceless for all aircraft: + +- Assigned the lower of `F180` or the `RFL`; and +- Tracking via **AVNEX** or **ESDEG** + +All other aircraft going to LEA CTA will be **Heads-up** Coordinated. + +### INE to WIIF CTR +As per [Standard IND coordination procedures](../../../oceanic/Positions/IND/#international-non-pacific), Heads-up Coordination required for all aircraft prior to **30 mins** from boundary. + +!!! tip + It may be prudent (especially if they are using vatSys) to set up a Voiceless Coordination Agreement with WIIF CTR, in order to reduce workload for both controllers. \ No newline at end of file diff --git a/docs/worldflight/Enroute/yssyypad.md b/docs/worldflight/Enroute/yssyypad.md new file mode 100644 index 000000000..24562a185 --- /dev/null +++ b/docs/worldflight/Enroute/yssyypad.md @@ -0,0 +1,95 @@ +--- + title: 1. YSSY to YPAD +--- + +--8<-- "includes/abbreviations.md" + +## Sector Responsibilities +### Katoomba (KAT) +KAT will take responsibility for the BIK and GUN subsectors. No additional frequencies will need to be primed to KAT. + +
+![KAT Area of Responsibility](../img/KAT.png){ width="700" } +
KAT Area of Responsibility
+
+ +Some aircraft will be handed off to KAT south of route on **H260**. When it's suitable, KAT must clear these aircraft DCT **BORLI**. + +#### Runway 30 at YPAD +If Runway 30 is in use for arrivals at YPAD, aircraft can be sent DCT **DRINA**, thence **AD**, to expect Runway 30. This will help ease the load on the sequence in to 05/23. + +This will only be available for the *first few hours* of the event, while YPAD has low or no departures (Until approximately **0030Z**). + +This tracking should only be issued to aircraft *south* of the flight planned route. + +This tracking must **only** be issued to **Light** and **Medium** Wake Turbulence Category aircraft. + +!!! tip + Balance **DRINA** tracking at your discretion. For every aircraft KAT receives on a heading from SY DEP, send one to **BORLI**, then one to **DRINA**, and continue cycling like that. + +### Griffith (GTH), Oxley (OXL) +GTH and OXL will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. + +!!! caution + GTH should look out for aircraft converging at **BORLI** at the same time and level. Use vertical separation wherever possible. + +If [Runway 30 is in use at YPAD](#runway-30-at-ypad), monitor the distribution of aircraft tracking on *Flight Planned Route* VS DCT **DRINA**. +Aim to maintain around *2/3rds* on *Flight Planned Route*, *1/3rd* DCT **DRINA**. Reroute aircraft as required to maintain this distribution. + +### Mungo (MUN) +MUN will be responsible for starting to form the sequence in to YPAD, by applying *speed control* in the cruise. + +### Tailem Bend (TBD) +TBD will be responsible for issuing STAR clearances in to YPAD, and providing the final sequence to handoff to AAE. + +TBD will be responsible for the TBD subsector **only**. + +#### STARs +Runway 23 Arrivals shall be issued the **BLACK3A** STAR. +Runway 05 Arrivals shall be issued the **BLACK3Z** STAR. +Runway 30 Arrivals shall be cleared from **DRINA** DCT **PADEL** for the RNP Approach. + +#### Sequencing +**All aircraft** must be instructed to cross **BLACK**/**DRINA** at **250 knots**, then *published STAR speeds*. + +!!! note + This instruction is not required for aircraft that have a clear gap in front of them in the sequence (>30nm). + +Minimum distance between arrivals at handoff to AAE is **10nm** (with no significant closing speed). It is important to try not to exceed **15nm**, due to the large number of arrivals. + +##### Runway 30 Arrivals +If Runway 30 is in use for arrivals, it is important to note that AFL will be issuing Feeder Fix times at **DRINA**. It is important that aircraft are sequenced to cross at these times, rather than just bunching up all Runway 30 arrivals as tight as you can. This is to avoid conflicts at the Runway intersection. + +!!! tip + A Feeder Fix time will be denoted by an `F` followed by two digits, in the aircraft's Global Ops Field. This will also show in the Arrivals List Window. For example, `F46` means *"Cross DRINA at time 46, at 250 knots"*. Visit the [Sequencing Annotations SOPs](../../../client/annotations/#sequencingflow) for more info + +## Coordination +### SY TCU to KAT +Voiceless for all aircraft: + +- Assigned the lower of `F280` or the `RFL`; and +- Tracking via **KADOM**; or +- South of **KADOM**, Assigned **H260** + +All other aircraft going to KAT CTA will be **Heads-up** Coordinated. + +### TBD to AAE +Voiceless for all aircraft: + +- With ADES **YPAD**; and +- Assigned `A090`; and +- Assigned the **BLACK3A/23** STAR; or +- Assigned the **BLACK3Z/05** STAR; or +- Tracking DCT **PADEL** + +#### Between TBD and AFL +AFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +AFL must **voice coordinate** any changes to instructions after TBD has put a `<` on it. + +TBD must **voice coordinate** any requests for *Track Shortening*, *CSR*, or *Victor/Xray STARs*, to AFL. + +!!! tip + If in your judgement, the request won't be available due to the sequence, there is no need to voice coordinate the requests. Just deny them. \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/.pages b/docs/worldflight/Terminal Areas/.pages new file mode 100644 index 000000000..f5daefead --- /dev/null +++ b/docs/worldflight/Terminal Areas/.pages @@ -0,0 +1,9 @@ +title: Terminal Areas +nav: + - sydneydep.md + - adelaide.md + - perth.md + - darwin.md + - portmoresby.md + - brisbane.md + - sydneyarr.md \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/adelaide.md b/docs/worldflight/Terminal Areas/adelaide.md new file mode 100644 index 000000000..6b695c2f3 --- /dev/null +++ b/docs/worldflight/Terminal Areas/adelaide.md @@ -0,0 +1,127 @@ +--- + title: 2. Adelaide (YPAD) +--- + +--8<-- "includes/abbreviations.md" + +## Airspace Division +Standard airspace division will be in use as per [AD TCU Local Instructions](../../../terminal/adelaide/#airspace-division). + +## Runway Modes +Depending on wind limitations, there are four possible Runway Modes in use at YPAD: + +- 23A30AD +- 23A12AD +- 05A30D +- 05A12D + +The **red** line represents the STAR to the arrival runway. +The **solid green** line represents the SID to **GILES**. +The **dashed green** line represents the *suggested vectors* for [12/30 departures](#1230-departures). + +### 05 + +
+![05 Arrival/Departure Routes](../img/05.png){ width="700" } +
05 Arrival/Departure Routes
+
+ +All arrivals on Runway 05 will be cleared for the **RNP Z** Approach. + +### 23 + +
+![23 Arrival/Departure Routes](../img/23.png){ width="700" } +
23 Arrival/Departure Routes
+
+ +All arrivals on Runway 23 will be cleared for the **ILS** Approach. + +### 12/30 Departures +Not all aircraft will be able to accept 12/30 for Departure. AAW/AAE must vector 12/30 Departures clear of the 05/23 Arrivals and Departures. + +Aircraft **north** of the GILES SID will be cleared DCT **LESON**. +Aircraft **south** of the GILES SID will be cleared DCT **LONLY**. + +## Flow +AFL will formulate the sequence in accordance with the [AD TCU Flow Table](../../../terminal/adelaide/#flow). Ensure that event traffic gets priority over non-event traffic. + +AFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +### Runway 30 Spacing +When Runway 30 is in use for arrivals, arrivals shall be spaced out in a **+2/+2/+1** pattern. + +| Number | Runway | Gap (mins) | Example Landing Time | +| ---------- | --- | --- | --- | +| 1 | 30 | | L00 | +| 2 | 05/23 | +2 | L02 | +| 3 | 05/23 | +2 | L04 | +| 4 | 30 | +1 | L05 | +| 5 | 05/23 | +2 | L07 | +| 6 | 05/23 | +2 | L09 | +| 7 | 30 | +1 | L10 | + +That is, two arrivals in to Runway 05/23 spaced out by 2 minutes each, followed by 1 arrival in to Runway 30 spaced out by 1 minute, and repeated. + +#### Times +**DRINA** to Runway 30 Threshold via **PADEL** is **12 minutes**. Subtract **1 minute** if assigned MX or CSR. + +### Wake Turbulence Separation +Due to the tight sequence, there are times that [Wake Turbulence Separation](../../../separation-standards/waketurb/#airspace) cannot practically be applied. + +When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. + +!!! example + **AAE:** "JST762, Traffic is BAW47C, a 747 4nm ahead. Caution Wake Turbulence" + **JST762:** "JST762" + +### Speeds +TBD will instruct all arrivals to cross **BLACK**/**DRINA** at **250 knots**, then *published STAR speeds*. + +## Coordination +### AD ADC +#### Auto Release +Standard as per [AD TCU Local Instructions](../../../terminal/adelaide/#ad-adc), with the exception of auto-release being available for **12/30 Departures** assigned the following *Standard Assignable Departure Headings*: + +| Runway Mode | Runway 12/30 Assigned Heading | +| ---------- | --- | +| 23A30AD | Runway Heading | +| 23A12AD | H180 | +| 05A30D | H230 | +| 05A12D | H060 | + +### AD TCU Internal +Departures from **Runway 12** will transit both AAE and AAW airspace. + +Voiceless coordination is in use from AAE to AAW for aircraft: + +- Assigned the lower of `F240` or the `RFL`; and +- Assigned a *Heading* clear of 05/23 Arrivals/Departures + +### AAW to AUG +Voiceless for all aircraft: + +- Assigned the lower of `F240` or the `RFL`; and +- Tracking via **GILES**; or +- North of **GILES**, DCT **LESON**; or +- South of **GILES**, DCT **LONLY** + +All other aircraft going to AUG CTA will be **Heads-up** Coordinated. + +### TBD to AAE +Voiceless for all aircraft: + +- With ADES **YPAD**; and +- Assigned `A090`; and +- Assigned the **BLACK3A/23** STAR; or +- Assigned the **BLACK3Z/05** STAR; or +- Tracking DCT **PADEL** + +TBD has *no Restrictions or Requirements* on YPAD departures tracking DCT **LONLY** + +#### Between TBD and AFL +AFL must **voice coordinate** any changes to instructions after TBD has put a `<` on it. + +TBD must **voice coordinate** any requests for *Track Shortening*, *CSR*, or *Victor/Xray STARs*, to AFL. \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/brisbane.md b/docs/worldflight/Terminal Areas/brisbane.md new file mode 100644 index 000000000..8e16da5a4 --- /dev/null +++ b/docs/worldflight/Terminal Areas/brisbane.md @@ -0,0 +1,166 @@ +--- + title: 6. Brisbane (YBBN) +--- + +--8<-- "includes/abbreviations.md" + +## Runway Modes +### 01 PROPS +#### Airspace Division +Non-Standard airspace division will be in use. + +The **red** line represents the STARs to the arrival runways. +The **solid green** line represents the SID to **SANEG**. +The **dashed green** line represents the *suggested vectors* for **01L** Departures. + +
+![01 PROPS Airspace Division](../img/01PROPS.png){ width="700" } +
01 PROPS Airspace Division
+
+ +01L will be the primary runway for arrivals. +01R will be the primary runway for departures. + +#### 01L Departures +Departures from Runway 01L will be assigned the **BN4** SID with an assigned heading of **H340**. +Aircraft must then be vectored to the east, then assigned a heading of **H180** when clear of 01R Departures. +Aircraft may be handed off to GOL on this heading. + +### 19 PROPS +#### Airspace Division +Non-Standard airspace division will be in use. + +The **red** line represents the STARs to the arrival runways. +The **dashed green** lines represents the *suggested vectors* for Departures. + +
+![19 PROPS Airspace Division](../img/19PROPS.png){ width="700" } +
19 PROPS Airspace Division
+
+ +19L will be the primary runway for arrivals. +19R will be the primary runway for departures. + +#### 19L Departures +Departures from Runway 19L will be assigned the **BN4** SID with an assigned heading of **H160**. +Aircraft may be handed off to GOL on this heading. + +#### 19R Departures +Departures from Runway 19R will be assigned the **BN4** SID with an assigned heading of **H210**. +Aircraft may be cleared DCT **SANEG** when clear of 19L Departures. + +### Approach Expectation +All arrivals will be cleared for the Approach type indicated on the ATIS. + +#### Independent Visual Approaches +Although not used at YBBN normally, IVAs can be expected to be in use for WorldFlight, to facilitate the high volume of traffic for both runways. + +Aircraft must report both **visual**, *and* **runway in sight** in order to be cleared for an IVA. + +!!! tip + The [Label Data Annotations](../../../client/annotations/#miscellaneous) for these are `V` and `R`, respectively + +Ensure you familiarise yourself with the applicable [Separation Standards](../../../separation-standards/parallelapps/#independent-visual-approaches) + +Pass *Traffic Information* on aircraft that will come within **1.5nm** of each other on parallel approaches. + +!!! example + **BAN:** "UAL8317, Traffic is an A320 at your 2 o'clock for the parallel runway" + +#### 19R Arrivals +Runway 19R Arrivals will be assigned the **Xray** STAR. The preferred approach type will be the **Independent Visual Approach**, however if weather does not permit this: + +- Aircraft that can accept the **RNP X** Approach will be cleared for it; or +- Aircraft that **cannot** accept the RNP X Approach, will be cleared **LUVNA** DCT **SABKO** for the **ILS** Approach. + +## Sector Distribution +In order to balance workload effectively, it is recommended to distribute responsibility for the Brisbane TCU sectors accordingly (BAC not included): + +### Two Controllers Online + +- BAS and BAN combined +- BDS and BDN combined +- No BFL + +### Three Controllers Online + +- BAS and BAN combined +- BDS and BDN combined +- BFL on its own + +### Four Controllers Online + +- BAS on its own +- BAN on its own +- BDS and BDN combined +- BFL on its own + +## Flow +BFL will formulate the sequence in accordance with the [Flow Times](#times) below. Ensure that event traffic gets priority over non-event traffic. + +BFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +### Times +The times below indicate the number of minutes from the Feeder Fix to the Runway Threshold on the appropriate STAR. + +| FF | Runway | Time | +| ---------- | --- | --- | +| SMOKA | 01L | 16 | +| SMOKA | 19L | 14 | +| ENLIP | 01R | 11 | +| ENLIP | 19R | 16 | + +Subtract **1 minute** if assigned MX or CSR. + +### Speeds +BUR will instruct all arrivals to cross **SMOKA** and **ENLIP** at **250 knots**, then *published STAR speeds*. + +## Coordination +### BN ADC +#### Auto Release +Available for aircraft assigned `A060`, and: + +| Runway | SID | Assigned Heading | +| ---------- | --- | --- | +| 01L | BN4 | H340 | +| 01R | SANEG1 | - | +| 19L | BN4 | H160 | +| 19R | BN4 | H210 | + +### BDN/BDS to GOL +Voiceless for all aircraft: + +- Assigned the lower of `F180` or the `RFL`; and +- Tracking via **SANEG**; or +- East of **SANEG**, Assigned a Heading between **H180**-**H160**. + +All other aircraft going to GOL CTA will be **Heads-up** Coordinated. + +### BUR to BAN/BAS +Voiceless for all aircraft: + +- With ADES **YBBN**; and +- Assigned `A090`; and +- Assigned any of the following: + +| STAR | Runway | DCT Tracking available | +| ---------- | --- | --- | +| SMOKA1A | 01L | None | +| SMOKA1A | 19L | None | +| ENLIP2A | 01R | DCT **MULNI** | +| ENLIP2X | 19R | DCT **DRAIN** | + +All other aircraft coming from BUR/DOS CTA will be **Heads-up** Coordinated to BN TCU prior to **20nm** from the boundary. + +#### Between BUR/KPL and BFL +BFL must **voice coordinate** any changes to instructions after BUR/KPL has put a `<` on it. + +BFL must **voice coordinate** to KPL/BUR any aircraft that must be rerouted via **ENLIP** for **01R/19R**. + +!!! example + **BFL** -> **KPL**: "PAA001 via ENLIP for 01R please" + **KPL** -> **BFL**: "PAA001 via ENLIP for 01R, will be" + +BUR/KPL must **voice coordinate** any requests for *Track Shortening*, *CSR*, or *Different STARs*, to BFL. \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/darwin.md b/docs/worldflight/Terminal Areas/darwin.md new file mode 100644 index 000000000..63380910e --- /dev/null +++ b/docs/worldflight/Terminal Areas/darwin.md @@ -0,0 +1,46 @@ +--- + title: 4. Darwin (YPDN) +--- + +--8<-- "includes/abbreviations.md" + +## Airspace Division +Standard airspace division will be in use as per [DN TCU Local Instructions](../../../terminal/darwin/#airspace-division). + +## Runway 29 Departures +Departures from Runway 29 will call DAE on an assigned heading of **H130**. These aircraft can be cleared DCT **RUPEG** when suitable. + +## Flow +### Speeds +TRT will instruct all arrivals to cross **ANUPA** at **250 knots**, then *published STAR speeds*. + +## Coordination +### DN ADC +#### Auto Release +Available for aircraft assigned `F180`, and: + +| Runway | SID | Assigned Heading | +| ---------- | --- | --- | +| 11 | RUPEG2 | - | +| 29 | DN7 | H130 | + +### DN TCU Internal +Arrivals/Departures on **Runway 29** will transit both DAW and DAE airspace. + +Voiceless coordination is in use from DAW to DAE for arrivals: + + - Assigned `A100`; and + - Assigned the **ANUPA1A** STAR + +DAW has *No Restrictions or Requirements* on Runway 29 Departures. + +### DAE to TRS +Voiceless for all aircraft: + +- Assigned the lower of `F180` or the `RFL`; and +- Tracking via **RUPEG** + +All other aircraft going to TRS CTA will be **Heads-up** Coordinated. + +### TRT to DAW +Standard as per [DN TCU Local Instructions](../../../terminal/darwin/#arrivals) \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/perth.md b/docs/worldflight/Terminal Areas/perth.md new file mode 100644 index 000000000..87eb55c68 --- /dev/null +++ b/docs/worldflight/Terminal Areas/perth.md @@ -0,0 +1,108 @@ +--- + title: 3. Perth (YPPH) +--- + +--8<-- "includes/abbreviations.md" + +## Runway Modes +Depending on wind limitations, there are two possible Runway Modes in use at YPPH: + +### 24A21D +Enroute will assign **Runway 21** to arrivals that *operationally require* it + +All arrivals on Runway 21/24 will be cleared for the **ILS** Approach. + +#### Airspace Division +Non-Standard airspace division will be in use. + +The **red** line represents the STAR to the arrival runway. +The **solid green** line represents the SID to **AVNEX**. + +
+![24A21D Airspace Division](../img/2124.png){ width="700" } +
24A21D Airspace Division
+
+ +### 03A06D +Enroute will enter `XX` in the scratchpad for arrivals that are *unable* to Land and Hold Short of **Runway 06**. + +Departures that *operationally require* **Runway 03** will be assigned the **PH7** SID with *Runway Heading*. PHD shall clear these aircraft DCT **ESDEG** when practical. + +All arrivals on Runway 03 will be cleared for the **ILS** Approach. + +#### Airspace Division +Non-Standard airspace division will be in use. + +The **red** line represents the STAR to the arrival runway. +The **solid green** line represents the SID to **AVNEX**. +The **dashed green** line represents the *suggested vectors* for [06 departures](#06-departures). + +
+![03A06D Airspace Division](../img/0306.png){ width="700" } +
03A06D Airspace Division
+
+ +## Flow +PFL will formulate the sequence in accordance with the [Flow Times](#times) below. Ensure that event traffic gets priority over non-event traffic. + +PFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +### Times +The times below indicate the number of minutes from **KABLI** to the Runway Threshold on the Alpha STAR. + +| Runway | Time | +| ---------- | --- | +| 03 | 16| +| 21 | 16 | +| 24 | 14 | + +Subtract **1 minute** if assigned MX or CSR. + +### Wake Turbulence Separation +Due to the tight sequence, there are times that [Wake Turbulence Separation](../../../separation-standards/waketurb/#airspace) cannot practically be applied. + +When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. + +!!! example + **PHA:** "VOZ721, Traffic is QFA25, a 747 4nm ahead. Caution Wake Turbulence" + **VOZ721:** "VOZ721" + +### Speeds +PIY will instruct all arrivals to cross **KABLI** at **250 knots**, then *published STAR speeds*. + +### Runway 21 vs Runway 24 Arrivals +The **KABLI1A** STAR is approximately **2 minutes** *longer* on Runway 21 vs Runway 24. Take this in to account when building the sequence. + +## Coordination +### PH ADC +#### Auto Release +Standard as per [PH TCU Local Instructions](../../../terminal/perth/#ph-adc), with the exception of auto-release being available for **06 Departures** assigned **Runway Heading** during the the [03A06D Runway Mode](#03a06d) + +### PHD to LEA +Voiceless for all aircraft: + +- Assigned the lower of `F180` or the `RFL`; and +- Tracking via **AVNEX** or **ESDEG** + +All other aircraft going to LEA CTA will be **Heads-up** Coordinated. + +### PIY to PHA +Standard as per [PH TCU Local Instructions](../../../terminal/perth/#arrivals), with the exception of: + +- During the [24A21D Runway Mode](#24a21d), arrivals assigned **Runway 21** may be handed off to PHA on a **Heading** *north* of the Runway 24 arrivals, without coordination. + +
+![PIY to PHA 24A21D](../img/PIY.png){ width="700" } +
PIY to PHA 24A21D
+
+ +#### Between PIY/HYD and PFL +PFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +PFL must **voice coordinate** any changes to instructions after PIY/HYD has put a `<` on it. + +PIY/HYD must **voice coordinate** any requests for *Track Shortening*, *CSR*, or *Victor/Xray STARs*, to PFL. \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/portmoresby.md b/docs/worldflight/Terminal Areas/portmoresby.md new file mode 100644 index 000000000..d64283ea0 --- /dev/null +++ b/docs/worldflight/Terminal Areas/portmoresby.md @@ -0,0 +1,69 @@ +--- + title: 5. Port Moresby (AYPY) +--- + +--8<-- "includes/abbreviations.md" + +## Positions +An additional Non-Standard position for AYPY DEP will be used + +| Name | ID | Callsign | Frequency | Login ID | +| ------------------ | --------------| -------------- | ---------------- | --------------------------------------| +| Port Moresby Approach | AYPY APP | Jacksons Radar | 125.800 | AYPY_APP | +| Port Moresby Departures | AYPY DEP | Jacksons Radar | 124.100 | AYPY_DEP | + +## Airspace Division +Non-Standard airspace division will be in use. + +The **red** line represents the STAR to the arrival runway. +The **green** line represents the SID to **NUPTA**. + +### 14 + +
+![Runway 14 Airspace Division](../img/AYPY TCU 14.png){ width="700" } +
Runway 14 Airspace Division
+
+ +All arrivals on Runway 14 will be cleared for the **ILS** Approach. + +### 32 + +
+![Runway 32 Airspace Division](../img/AYPY TCU 32.png){ width="700" } +
Runway 32 Airspace Division
+
+ +All arrivals on Runway 32 will be cleared for the **ILS** Approach. + +## Terrain +**Very high terrain** exists to the North-East of the field, with the MVA up to `F155`. Use *caution* when vectoring, and ensure that terrain separation is maintained at **all times**. + +!!! tip + The *biggest risk* to terrain separation is vectoring **Runway 14 Arrivals** (Potential conflict areas are shaded in **Red** below). Avoid vectoring to the *East* of the Extended Centreline, and do not assign below `A060` until aircraft are within **30nm** of the field. + +
+![AYPY RTCC](../img/aypyrtccshade.png){ width="700" } +
AYPY RTCC
+
+ +## Flow +### Speeds +AYPM CTR will instruct all arrivals to cross **GUMBU** at **250 knots**, then *published STAR speeds*. + +## Coordination +### AYPY ADC +#### Auto Release +Available for aircraft assigned: + +- A Runway nominated on the ATIS; and +- The **NUPTA1** SID; and +- `A080` + +### AYPY DEP to AYPM CTR +Voiceless for all aircraft: + +- Assigned the lower of `F240` or the `RFL`; and +- Tracking via **NUPTAU** + +All other aircraft going to AYPM CTR CTA will be **Heads-up** Coordinated. \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/sydneyarr.md b/docs/worldflight/Terminal Areas/sydneyarr.md new file mode 100644 index 000000000..23a709e70 --- /dev/null +++ b/docs/worldflight/Terminal Areas/sydneyarr.md @@ -0,0 +1,99 @@ +--- + title: 7. Sydney (YSSY) Arrivals +--- + +--8<-- "includes/abbreviations.md" + +## Runway Modes +### 16 PROPS +#### Airspace Division +Non-Standard airspace division will be in use. + +The **red** line represents the STARs to the arrival runways. + +
+![16 PROPS Airspace Division](../img/16PROPS Arrivals.png){ width="700" } +
16 PROPS Airspace Division
+
+ +### 34 PROPS +#### Airspace Division +Non-Standard airspace division will be in use. + +The **red** line represents the STARs to the arrival runways. + +
+![34 PROPS Airspace Division](../img/34PROPS Arrivals.png){ width="700" } +
34 PROPS Airspace Division
+
+ +#### 34R Arrivals +Ensure that 34R Arrivals are assigned **H150** at or prior to **LANOL**, to ensure separation with 34L Arrivals. + +### Approach Expectation +All arrivals will be cleared for the Approach type indicated on the ATIS. + +#### Independent Visual Approaches +IVAs can be expected to be in use for WorldFlight, to facilitate the high volume of traffic for both runways. + +Aircraft must report both **visual**, *and* **runway in sight** in order to be cleared for an IVA. + +!!! tip + The [Label Data Annotations](../../../client/annotations/#miscellaneous) for these are `V` and `R`, respectively + +Ensure you familiarise yourself with the applicable [Separation Standards](../../../separation-standards/parallelapps/#independent-visual-approaches) + +Pass *Traffic Information* on aircraft that will come within **1nm** of each other on parallel approaches. + +!!! example + **SFW:** "NPT11W, Traffic is a 767 at your 10 o'clock for the parallel runway" + +## Sector Distribution +In order to balance workload effectively, it is recommended to distribute responsibility for the Sydney TCU sectors accordingly: + +### Two Controllers Online + +- SAS and SFW combined +- SAN and SFE combined +- No SFL + +### Three Controllers Online + +- SAS and SFW combined +- SAN and SFE combined +- SFL on its own + +### Four Controllers Online + +- SAS and SAN combined +- SFW on its own +- SFE on its own +- SFL on its own + +## Flow +SFL will formulate the sequence in accordance with the [SY TCU Flow Table](../../../terminal/sydney/#flow). Ensure that event traffic gets priority over non-event traffic. + +SFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). + +Appropriate annotations for the Arrivals List Window can be found [here](../../../client/annotations/#sequencingflow). + +### Speeds +CNK will instruct all arrivals to cross **BOREE** and **MEPIL** at **250 knots**, then *published STAR speeds*. + +## Coordination +### APP to DIR +Standard as per [SY TCU Local Instructions](../../../terminal/sydney/#app-dir). + +### CNK to SAS/SAN +Standard as per [SY TCU Local Instructions](../../../terminal/sydney/#arrivals). + +#### Between ARL/CNK and SFL +SFL must **voice coordinate** any changes to instructions after ARL/CNK has put a `<` on it. + +SFL must **voice coordinate** to ARL/CNK any aircraft that must be rerouted via **OLTIN YAKKA MEPIL** for **16L/34R**. + +!!! example + **SFL** -> **ARL**: "ANZ361 via OLTIN for 34R please" + **ARL** -> **SFL**: "ANZ361 via OLTIN for 34, will be" + +ARL/CNK must **voice coordinate** any requests for *Track Shortening* or *CSR* to SFL. \ No newline at end of file diff --git a/docs/worldflight/Terminal Areas/sydneydep.md b/docs/worldflight/Terminal Areas/sydneydep.md new file mode 100644 index 000000000..fd7ebf1f2 --- /dev/null +++ b/docs/worldflight/Terminal Areas/sydneydep.md @@ -0,0 +1,47 @@ +--- + title: 1. Sydney (YSSY) Departures +--- + +--8<-- "includes/abbreviations.md" + +## Airspace Division +Non-Standard airspace division will be in use. + +The **solid** green line represents the SID to **KADOM**. +The **dashed** green line represents the *suggested vectors* for [16L/34R departures](#16l34r-departures). + +### 16 PROPS + +
+![16 PROPS Airspace Division](../img/16PROPS Departures.png){ width="700" } +
16 PROPS Airspace Division
+
+ +### 34 PROPS + +
+![34 PROPS Airspace Division](../img/34PROPS Departures.png){ width="700" } +
34 PROPS Airspace Division
+
+ +## 16L/34R Departures +Departures from 16L/34R will be assigned the **SY3** SID with a heading of **H120**. SDS must then vector the aircraft south of the 16R/34L Departures. Aircraft will be handed off to KAT on a Heading of **H260**. + +## Coordination +### SY ADC +#### Auto Release +Standard as per [SY TCU Local Instructions](../../../terminal/sydney/#sy-adc), with the exception of: + +- 16L/34R Departure SID: **SY3** RADAR +- 16L/34R Standard Assignable Departure Heading: **H120** + +### KAT +KAT will be extending to the BIK subsector. + +Voiceless for all aircraft: + +- Assigned the lower of `F280` or the `RFL`; and +- Tracking via **KADOM**; or +- South of **KADOM**, Assigned **H260** + +All other aircraft going to KAT CTA will be **Heads-up** Coordinated. \ No newline at end of file diff --git a/docs/worldflight/img/01PROPS.png b/docs/worldflight/img/01PROPS.png new file mode 100644 index 000000000..b82325387 Binary files /dev/null and b/docs/worldflight/img/01PROPS.png differ diff --git a/docs/worldflight/img/0306.png b/docs/worldflight/img/0306.png new file mode 100644 index 000000000..39ed086ae Binary files /dev/null and b/docs/worldflight/img/0306.png differ diff --git a/docs/worldflight/img/05.png b/docs/worldflight/img/05.png new file mode 100644 index 000000000..bd33ca95b Binary files /dev/null and b/docs/worldflight/img/05.png differ diff --git a/docs/worldflight/img/05A12DSMC.png b/docs/worldflight/img/05A12DSMC.png new file mode 100644 index 000000000..ed6fb83dd Binary files /dev/null and b/docs/worldflight/img/05A12DSMC.png differ diff --git a/docs/worldflight/img/05A30DSMC.png b/docs/worldflight/img/05A30DSMC.png new file mode 100644 index 000000000..f14a30611 Binary files /dev/null and b/docs/worldflight/img/05A30DSMC.png differ diff --git a/docs/worldflight/img/06queue.png b/docs/worldflight/img/06queue.png new file mode 100644 index 000000000..97a6ca41a Binary files /dev/null and b/docs/worldflight/img/06queue.png differ diff --git a/docs/worldflight/img/16PROPS Arrivals.png b/docs/worldflight/img/16PROPS Arrivals.png new file mode 100644 index 000000000..bad8ff66f Binary files /dev/null and b/docs/worldflight/img/16PROPS Arrivals.png differ diff --git a/docs/worldflight/img/16PROPS Departures.png b/docs/worldflight/img/16PROPS Departures.png new file mode 100644 index 000000000..ab4c7d598 Binary files /dev/null and b/docs/worldflight/img/16PROPS Departures.png differ diff --git a/docs/worldflight/img/19PROPS.png b/docs/worldflight/img/19PROPS.png new file mode 100644 index 000000000..51ec3f984 Binary files /dev/null and b/docs/worldflight/img/19PROPS.png differ diff --git a/docs/worldflight/img/2124.png b/docs/worldflight/img/2124.png new file mode 100644 index 000000000..c1fb8f267 Binary files /dev/null and b/docs/worldflight/img/2124.png differ diff --git a/docs/worldflight/img/23.png b/docs/worldflight/img/23.png new file mode 100644 index 000000000..9eebc1ce9 Binary files /dev/null and b/docs/worldflight/img/23.png differ diff --git a/docs/worldflight/img/23A12DSMC.png b/docs/worldflight/img/23A12DSMC.png new file mode 100644 index 000000000..ca595ae1a Binary files /dev/null and b/docs/worldflight/img/23A12DSMC.png differ diff --git a/docs/worldflight/img/23A30DSMC.png b/docs/worldflight/img/23A30DSMC.png new file mode 100644 index 000000000..fbe7c726a Binary files /dev/null and b/docs/worldflight/img/23A30DSMC.png differ diff --git a/docs/worldflight/img/34PROPS Arrivals.png b/docs/worldflight/img/34PROPS Arrivals.png new file mode 100644 index 000000000..71c033efb Binary files /dev/null and b/docs/worldflight/img/34PROPS Arrivals.png differ diff --git a/docs/worldflight/img/34PROPS Departures.png b/docs/worldflight/img/34PROPS Departures.png new file mode 100644 index 000000000..c43ece3cd Binary files /dev/null and b/docs/worldflight/img/34PROPS Departures.png differ diff --git a/docs/worldflight/img/AYPY TCU 14.png b/docs/worldflight/img/AYPY TCU 14.png new file mode 100644 index 000000000..bc9054ae3 Binary files /dev/null and b/docs/worldflight/img/AYPY TCU 14.png differ diff --git a/docs/worldflight/img/AYPY TCU 32.png b/docs/worldflight/img/AYPY TCU 32.png new file mode 100644 index 000000000..09fd59f4d Binary files /dev/null and b/docs/worldflight/img/AYPY TCU 32.png differ diff --git a/docs/worldflight/img/KAT.png b/docs/worldflight/img/KAT.png new file mode 100644 index 000000000..3233dd142 Binary files /dev/null and b/docs/worldflight/img/KAT.png differ diff --git a/docs/worldflight/img/PIY.png b/docs/worldflight/img/PIY.png new file mode 100644 index 000000000..fe24a92a7 Binary files /dev/null and b/docs/worldflight/img/PIY.png differ diff --git a/docs/worldflight/img/arrlistexample.png b/docs/worldflight/img/arrlistexample.png new file mode 100644 index 000000000..8e65773f3 Binary files /dev/null and b/docs/worldflight/img/arrlistexample.png differ diff --git a/docs/worldflight/img/arrlistexample2.png b/docs/worldflight/img/arrlistexample2.png new file mode 100644 index 000000000..6d16cfd89 Binary files /dev/null and b/docs/worldflight/img/arrlistexample2.png differ diff --git a/docs/worldflight/img/aypyrtccshade.png b/docs/worldflight/img/aypyrtccshade.png new file mode 100644 index 000000000..bd60afa56 Binary files /dev/null and b/docs/worldflight/img/aypyrtccshade.png differ diff --git a/docs/worldflight/img/aypysmc.png b/docs/worldflight/img/aypysmc.png new file mode 100644 index 000000000..d612d167a Binary files /dev/null and b/docs/worldflight/img/aypysmc.png differ diff --git a/docs/worldflight/img/coordinatorbars.png b/docs/worldflight/img/coordinatorbars.png new file mode 100644 index 000000000..07983a624 Binary files /dev/null and b/docs/worldflight/img/coordinatorbars.png differ diff --git a/docs/worldflight/img/coordinatorstrips.png b/docs/worldflight/img/coordinatorstrips.png new file mode 100644 index 000000000..2a74ada5d Binary files /dev/null and b/docs/worldflight/img/coordinatorstrips.png differ diff --git a/docs/worldflight/img/labeldataentry.png b/docs/worldflight/img/labeldataentry.png new file mode 100644 index 000000000..4399431b9 Binary files /dev/null and b/docs/worldflight/img/labeldataentry.png differ diff --git a/docs/worldflight/img/route.png b/docs/worldflight/img/route.png new file mode 100644 index 000000000..45e7c76aa Binary files /dev/null and b/docs/worldflight/img/route.png differ diff --git a/docs/worldflight/img/smcntaxi.png b/docs/worldflight/img/smcntaxi.png new file mode 100644 index 000000000..8913162f7 Binary files /dev/null and b/docs/worldflight/img/smcntaxi.png differ diff --git a/docs/worldflight/img/strip1.png b/docs/worldflight/img/strip1.png new file mode 100644 index 000000000..5c80836a6 Binary files /dev/null and b/docs/worldflight/img/strip1.png differ diff --git a/docs/worldflight/img/strip2.png b/docs/worldflight/img/strip2.png new file mode 100644 index 000000000..2fe7299fb Binary files /dev/null and b/docs/worldflight/img/strip2.png differ diff --git a/docs/worldflight/img/wfcgrerte.png b/docs/worldflight/img/wfcgrerte.png new file mode 100644 index 000000000..adf821b4a Binary files /dev/null and b/docs/worldflight/img/wfcgrerte.png differ diff --git a/docs/worldflight/img/ypaddualbrl.png b/docs/worldflight/img/ypaddualbrl.png new file mode 100644 index 000000000..fff115415 Binary files /dev/null and b/docs/worldflight/img/ypaddualbrl.png differ diff --git a/docs/worldflight/img/ypadgrasstaxi.png b/docs/worldflight/img/ypadgrasstaxi.png new file mode 100644 index 000000000..dfdb150a2 Binary files /dev/null and b/docs/worldflight/img/ypadgrasstaxi.png differ diff --git a/docs/worldflight/img/ypadsmcbase.png b/docs/worldflight/img/ypadsmcbase.png new file mode 100644 index 000000000..494fa8eeb Binary files /dev/null and b/docs/worldflight/img/ypadsmcbase.png differ diff --git a/docs/worldflight/img/ypadsmcown.png b/docs/worldflight/img/ypadsmcown.png new file mode 100644 index 000000000..10b8c24bd Binary files /dev/null and b/docs/worldflight/img/ypadsmcown.png differ diff --git a/docs/worldflight/img/ypdngrass.png b/docs/worldflight/img/ypdngrass.png new file mode 100644 index 000000000..00044c6d2 Binary files /dev/null and b/docs/worldflight/img/ypdngrass.png differ diff --git a/docs/worldflight/index.md b/docs/worldflight/index.md new file mode 100644 index 000000000..117085d27 --- /dev/null +++ b/docs/worldflight/index.md @@ -0,0 +1,31 @@ +--- + title: Overview +--- + +Welcome to the controller briefing material for WorldFlight! Event-specific procedures are sorted by position type and should be read in conjunction with the existing SOPs for that position/location. + +## Official Team Callsigns +Official WorldFlight teams should be afforded priority at all stages of flight. **ACD** controllers should add `WF TEAM` to the Global Ops Field and `STS/STATE` to the Remarks flight plan field of any official team aircraft they issue a clearance to. + +The list of callsigns is below: + +| Team Name | Callsign | Aircraft Type | +| --------- | -------- | ------------- | +| WorldFlight AU | QFA25 | B744 | +| Simfest UK | BAW47C | B744 | +| Simflite AU | ASY121 | A332 | +| WorldFlight Perth | GTI1471 | B744 | +| Hamilton | ANZ361 | B738 | +| San Diego | ANZ362 | B738 | +| Velocity UK | NPT11W | B738 | +| Virginia | UAL1120 | B738 | +| Wings4Hope | UAL8317 | B772 | +| Team JeeHell | JHL44 | A320 | +| WorldFlight USA | DAL209 | B738 | +| Ness Aviation | EXS25N | B738 | +| Team SharedFlight | PAA001 | B744 | + +## Route +
+![WorldFlight Route](img/route.png){ width="800" } +
\ No newline at end of file diff --git a/includes/abbreviations.md b/includes/abbreviations.md index a85c026e0..9aa72dd77 100644 --- a/includes/abbreviations.md +++ b/includes/abbreviations.md @@ -68,6 +68,8 @@ *[CSD]: Cairns Departures *[CBW]: Canberra Approach West *[CBE]: Canberra Approach East +*[DAW]: Darwin Approach West +*[DAE]: Darwin Approach East *[HBA]: Hobart Approach *[LTA]: Launceston Approach *[MKA]: Mackay Approach @@ -100,6 +102,7 @@ *[TBD]: Melbourne (Tailem Bend) Centre *[YWE]: Melbourne (Yarrowee) Centre *[ARA]: Brisbane (Arafura) Centre +*[ARE]: Brisbane (Arafura East) Centre *[BAR]: Brisbane (Barra) Centre *[BUR]: Brisbane (Burnett) Centre *[CVN]: Brisbane (Carnarvon) Centre @@ -131,7 +134,8 @@ *[BKE]: Melbourne (Bourke) Centre *[CRS]: Melbourne (Cross) Centre *[ESP]: Melbourne (Esperance) Centre -*[FOR]: Melbourne (Forest) Centre +*[FOR]: Melbourne (Forrest) Centre +*[FOW]: Melbourne (Forrest West) Centre *[GEL]: Melbourne (Geraldton) Centre *[GTH]: Melbourne (Griffith) Centre *[GVE]: Melbourne (Grove) Centre @@ -270,6 +274,7 @@ *[FIMM]: Mauritius FIR *[FAJO]: Johannesburg FIR *[AYPM]: Port Moresby FIR +*[AYPE]: Port Moresby (East) FIR *[NWWW]: Noumea FIR *[NVVV]: Port Vila FIR *[RJTG]: Fukuoka FIR @@ -297,4 +302,6 @@ *[EN]: Essendon *[MB]: Moorabbin *[SUA]: Special Use Airspace -*[CPDLC]: Controller-Pilot Datalink Communications \ No newline at end of file +*[CPDLC]: Controller-Pilot Datalink Communications +*[LDA]: Landing Distance Available +*[TORA]: Takeoff Run Available \ No newline at end of file