From 25765f95c6463ad997fca21af9eaa9a825f47dcb Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Mon, 18 Nov 2024 13:18:04 +1100 Subject: [PATCH 1/6] BN SIDs --- docs/aerodromes/classc/Brisbane.md | 47 ++++++++++++------------------ 1 file changed, 19 insertions(+), 28 deletions(-) diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index 904c887e2..913086957 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -80,55 +80,46 @@ When using the SODPROPS mode, pass traffic information to aircraft that are depa Refer to [Parallel Runway Separation Standards](../../../separation-standards/parallelapps) for more information ### Runway Selection -Aircraft shall be assigned the following runways for departure when PROPS are in progress: - -| Aircraft tracking | Runway | -| ----------------| --------- | -| via BIXAD | 01L/19R | -| via GUMKI | 01R/19L | -| via SCOTT | 01R/19L | -| via SANEG | 01R/19L | -| via WACKO | 01L/19R | -| Other aircraft: | -| To the NORTH and WEST | 01L/19R | -| To the SOUTH and EAST | 01R/19L | +During PROPS, aircraft tracking via *any* of the following shall be assigned Runway **01L/19R** for departure: -!!! tip - Runway 01L/19R opened in 2020. Some pilots on VATSIM may have old simulators/scenery, in which case they will only have Runway 01R/19L available. Endeavour to be accommodating of pilots' requests in this instance. +- **BIXAD** +- **AKOBA** +- **BUGNU** +- **ITIDE** + +*All other* aircraft shall be assigned Runway **01R/19L** for departure. -### SID Selection -Jet Aircraft planned via **BIXAD**, **GUMKI**, **SCOTT**, **SANEG**, or **WACKO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus, unless the pilot indicates they are unable to accept a Procedural SID. +## SID Selection +Jet Aircraft planned via **BIXAD**, **GUMKI**, **SCOTT**, **SANEG**, or **WACKO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus^, unless the pilot indicates they are unable to accept a Procedural SID. !!! example Jet Aircraft planned via SCOTT, assigned runway 19L, shall be assigned the SCOTT SID. -Non-Jet aircraft, and aircraft that cannot accept a Procedural SID, shall be assigned the **Radar SID**. - -!!! example - Non-Jet Aircraft planned via WACKO, assigned runway 01L, shall be assigned the BN (RADAR) SID. +!!! exception + ^Jet Aircraft with ADES **YBSU** may plan via **ITIDE**, and be assigned the **Radar SID**. Amended routing is *not required*. -#### SODPROPS -During the SODPROPS runway mode, Jet departures from Runway 01R shall be assigned the **ASISO** Procedural SID in lieu of other Procedural SIDs available that terminate at the appropriate waypoint. +Non-Jet aircraft, and aircraft that cannot accept a Procedural SID, shall be assigned the **Radar SID**. !!! example - Jet Aircraft planned via SCOTT, assigned runway 01R, shall be assigned the ASISO SID, SCOTT Transition. + Non-Jet Aircraft planned via WACKO, assigned runway 01R, shall be assigned the BN (RADAR) SID. ## ATIS #### Operational Info - When parallel runways are used for departures, the ATIS OPR INFO shall include: `INDEPENDENT PARALLEL DEPARTURES IN PROGRESS` When SODPROPS are in operation, the ATIS OPR INFO shall include: `SIMULTANEOUS OPPOSITE DIRECTION PARALLEL RUNWAY OPERATIONS IN PROGRESS` + #### Approach Types The ATIS shall always have `EXP INST APCH` as the approach type. Visual Approaches are permitted on request, as long as a separation standard exists between the aircraft and any aircraft arriving on the parallel runway during PROPS, or departing from the parallel runway during SODPROPS. ## Coordination ### Auto Release -'Next' coordination is **not** required to BN TCU for aircraft that are: - a) Departing from a runway nominated on the ATIS (except during SODPROPS^); and - b) Assigned the standard assignable level; and - c) Assigned a **Procedural** SID +'Next' coordination is **not** required to BN TCU for aircraft that are: + +- Departing from a runway nominated on the ATIS (except during SODPROPS^); and +- Assigned the standard assignable level; and +- Assigned a **Procedural** SID ^Auto Release is not available during SODPROPS runway mode. All aircraft must be coordinated from BN ADC to BN TCU. From fc55be7dbab699b5dba3b29cfb4011c3f50fc351 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Tue, 19 Nov 2024 09:50:20 +1100 Subject: [PATCH 2/6] PH SMC --- docs/aerodromes/classc/Perth.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/aerodromes/classc/Perth.md b/docs/aerodromes/classc/Perth.md index 0d498244e..54dff2982 100644 --- a/docs/aerodromes/classc/Perth.md +++ b/docs/aerodromes/classc/Perth.md @@ -19,12 +19,8 @@ PH ADC is not responsible for any airspace by default. ## Maneuvering Area Responsibility -The division of responsibility between ADC, SMC West, and SMC East is shown below. - -
-![YPPH Maneuvering Area Responsibility](img/ypphsmc.png){ width="700" } -
YPPH Maneuvering Area Responsibility
-
+The area of responsibility between SMC West and East is divided by Runway 03/21. +Everything West of the Runway belongs to SMC West, everything East of the Runway belongs to SMC East. ## Runway Selection ### Southwest Plan From 25ec0d8f72520b424fc0b27c509e78fac3d2c756 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Tue, 19 Nov 2024 11:37:21 +1100 Subject: [PATCH 3/6] events tab --- docs/.pages | 2 +- docs/controller-skills/milkrun.md | 335 ------------------ docs/events/.pages | 4 + docs/{worldflight => events}/img/01PROPS.png | Bin docs/{worldflight => events}/img/0306.png | Bin docs/{worldflight => events}/img/05.png | Bin .../{worldflight => events}/img/05A12DSMC.png | Bin .../{worldflight => events}/img/05A30DSMC.png | Bin docs/{worldflight => events}/img/06queue.png | Bin .../img/16PROPS Arrivals.png | Bin .../img/16PROPS Departures.png | Bin .../img/16sdnrls.png | Bin docs/{worldflight => events}/img/19PROPS.png | Bin docs/{worldflight => events}/img/2124.png | Bin docs/{worldflight => events}/img/23.png | Bin .../{worldflight => events}/img/23A12DSMC.png | Bin .../{worldflight => events}/img/23A30DSMC.png | Bin .../img/34PROPS Arrivals.png | Bin .../img/34PROPS Departures.png | Bin .../img/AYPY TCU 14.png | Bin .../img/AYPY TCU 32.png | Bin docs/{worldflight => events}/img/KAT.png | Bin docs/{worldflight => events}/img/PIY.png | Bin .../img/arrlistexample.png | Bin .../img/arrlistexample2.png | Bin .../img/aypyrtccshade.png | Bin docs/{worldflight => events}/img/aypysmc.png | Bin .../img/clrqbay.png | Bin .../img/coordinatorbars.png | Bin .../img/coordinatorstrips.png | Bin .../img/labeldataentry.png | Bin .../img/odale1.png | Bin .../img/odale2.png | Bin .../img/odale3.png | Bin docs/{worldflight => events}/img/route.png | Bin .../img/slottime.png | Bin docs/{worldflight => events}/img/smcntaxi.png | Bin docs/{worldflight => events}/img/strip1.png | Bin docs/{worldflight => events}/img/strip2.png | Bin .../{worldflight => events}/img/wfcgrerte.png | Bin docs/{worldflight => events}/img/wfteam.png | Bin .../img/ymmlhotspots.png | Bin .../img/ypaddualbrl.png | Bin .../img/ypadgrasstaxi.png | Bin .../img/ypadsmcbase.png | Bin .../img/ypadsmcown.png | Bin .../{worldflight => events}/img/ypdngrass.png | Bin .../img/yssyhotspots.png | Bin docs/events/index.md | 5 + docs/events/milkrun/.pages | 7 + docs/events/milkrun/aerodrome.md | 96 +++++ docs/events/milkrun/enroute.md | 70 ++++ docs/events/milkrun/index.md | 5 + docs/events/milkrun/terminal.md | 52 +++ docs/events/milkrun/workload.md | 92 +++++ docs/{ => events}/worldflight/.pages | 1 + .../worldflight/Aerodromes/.pages | 0 .../worldflight/Aerodromes/adelaide.md | 34 +- .../worldflight/Aerodromes/brisbane.md | 12 +- .../worldflight/Aerodromes/darwin.md | 18 +- .../worldflight/Aerodromes/perth.md | 24 +- .../worldflight/Aerodromes/portmoresby.md | 16 +- .../worldflight/Aerodromes/sydneyarr.md | 8 +- .../worldflight/Aerodromes/sydneydep.md | 30 +- docs/{ => events}/worldflight/Enroute/.pages | 0 .../worldflight/Enroute/aypyybbn.md | 6 +- .../worldflight/Enroute/wammypdn.md | 4 +- .../worldflight/Enroute/ybbnyssy.md | 6 +- .../worldflight/Enroute/ypadypph.md | 8 +- .../worldflight/Enroute/ypdnaypy.md | 0 .../worldflight/Enroute/ypphwiii.md | 6 +- .../worldflight/Enroute/yssyypad.md | 18 +- .../worldflight/Terminal Areas/.pages | 0 .../worldflight/Terminal Areas/adelaide.md | 24 +- .../worldflight/Terminal Areas/brisbane.md | 12 +- .../worldflight/Terminal Areas/darwin.md | 4 +- .../worldflight/Terminal Areas/perth.md | 22 +- .../worldflight/Terminal Areas/portmoresby.md | 6 +- .../worldflight/Terminal Areas/sydneyarr.md | 18 +- .../worldflight/Terminal Areas/sydneydep.md | 6 +- docs/{ => events}/worldflight/index.md | 2 +- docs/terminal/adelaide.md | 4 +- mkdocs.yml | 1 + overrides/home.html | 2 +- 84 files changed, 479 insertions(+), 481 deletions(-) delete mode 100644 docs/controller-skills/milkrun.md create mode 100644 docs/events/.pages rename docs/{worldflight => events}/img/01PROPS.png (100%) rename docs/{worldflight => events}/img/0306.png (100%) rename docs/{worldflight => events}/img/05.png (100%) rename docs/{worldflight => events}/img/05A12DSMC.png (100%) rename docs/{worldflight => events}/img/05A30DSMC.png (100%) rename docs/{worldflight => events}/img/06queue.png (100%) rename docs/{worldflight => events}/img/16PROPS Arrivals.png (100%) rename docs/{worldflight => events}/img/16PROPS Departures.png (100%) rename docs/{controller-skills => events}/img/16sdnrls.png (100%) rename docs/{worldflight => events}/img/19PROPS.png (100%) rename docs/{worldflight => events}/img/2124.png (100%) rename docs/{worldflight => events}/img/23.png (100%) rename docs/{worldflight => events}/img/23A12DSMC.png (100%) rename docs/{worldflight => events}/img/23A30DSMC.png (100%) rename docs/{worldflight => events}/img/34PROPS Arrivals.png (100%) rename docs/{worldflight => events}/img/34PROPS Departures.png (100%) rename docs/{worldflight => events}/img/AYPY TCU 14.png (100%) rename docs/{worldflight => events}/img/AYPY TCU 32.png (100%) rename docs/{worldflight => events}/img/KAT.png (100%) rename docs/{worldflight => events}/img/PIY.png (100%) rename docs/{worldflight => events}/img/arrlistexample.png (100%) rename docs/{worldflight => events}/img/arrlistexample2.png (100%) rename docs/{worldflight => events}/img/aypyrtccshade.png (100%) rename docs/{worldflight => events}/img/aypysmc.png (100%) rename docs/{controller-skills => events}/img/clrqbay.png (100%) rename docs/{worldflight => events}/img/coordinatorbars.png (100%) rename docs/{worldflight => events}/img/coordinatorstrips.png (100%) rename docs/{worldflight => events}/img/labeldataentry.png (100%) rename docs/{controller-skills => events}/img/odale1.png (100%) rename docs/{controller-skills => events}/img/odale2.png (100%) rename docs/{controller-skills => events}/img/odale3.png (100%) rename docs/{worldflight => events}/img/route.png (100%) rename docs/{controller-skills => events}/img/slottime.png (100%) rename docs/{worldflight => events}/img/smcntaxi.png (100%) rename docs/{worldflight => events}/img/strip1.png (100%) rename docs/{worldflight => events}/img/strip2.png (100%) rename docs/{worldflight => events}/img/wfcgrerte.png (100%) rename docs/{worldflight => events}/img/wfteam.png (100%) rename docs/{controller-skills => events}/img/ymmlhotspots.png (100%) rename docs/{worldflight => events}/img/ypaddualbrl.png (100%) rename docs/{worldflight => events}/img/ypadgrasstaxi.png (100%) rename docs/{worldflight => events}/img/ypadsmcbase.png (100%) rename docs/{worldflight => events}/img/ypadsmcown.png (100%) rename docs/{worldflight => events}/img/ypdngrass.png (100%) rename docs/{controller-skills => events}/img/yssyhotspots.png (100%) create mode 100644 docs/events/index.md create mode 100644 docs/events/milkrun/.pages create mode 100644 docs/events/milkrun/aerodrome.md create mode 100644 docs/events/milkrun/enroute.md create mode 100644 docs/events/milkrun/index.md create mode 100644 docs/events/milkrun/terminal.md create mode 100644 docs/events/milkrun/workload.md rename docs/{ => events}/worldflight/.pages (69%) rename docs/{ => events}/worldflight/Aerodromes/.pages (100%) rename docs/{ => events}/worldflight/Aerodromes/adelaide.md (86%) rename docs/{ => events}/worldflight/Aerodromes/brisbane.md (90%) rename docs/{ => events}/worldflight/Aerodromes/darwin.md (88%) rename docs/{ => events}/worldflight/Aerodromes/perth.md (87%) rename docs/{ => events}/worldflight/Aerodromes/portmoresby.md (88%) rename docs/{ => events}/worldflight/Aerodromes/sydneyarr.md (91%) rename docs/{ => events}/worldflight/Aerodromes/sydneydep.md (88%) rename docs/{ => events}/worldflight/Enroute/.pages (100%) rename docs/{ => events}/worldflight/Enroute/aypyybbn.md (96%) rename docs/{ => events}/worldflight/Enroute/wammypdn.md (75%) rename docs/{ => events}/worldflight/Enroute/ybbnyssy.md (93%) rename docs/{ => events}/worldflight/Enroute/ypadypph.md (92%) rename docs/{ => events}/worldflight/Enroute/ypdnaypy.md (100%) rename docs/{ => events}/worldflight/Enroute/ypphwiii.md (73%) rename docs/{ => events}/worldflight/Enroute/yssyypad.md (88%) rename docs/{ => events}/worldflight/Terminal Areas/.pages (100%) rename docs/{ => events}/worldflight/Terminal Areas/adelaide.md (77%) rename docs/{ => events}/worldflight/Terminal Areas/brisbane.md (91%) rename docs/{ => events}/worldflight/Terminal Areas/darwin.md (87%) rename docs/{ => events}/worldflight/Terminal Areas/perth.md (76%) rename docs/{ => events}/worldflight/Terminal Areas/portmoresby.md (91%) rename docs/{ => events}/worldflight/Terminal Areas/sydneyarr.md (77%) rename docs/{ => events}/worldflight/Terminal Areas/sydneydep.md (81%) rename docs/{ => events}/worldflight/index.md (95%) diff --git a/docs/.pages b/docs/.pages index b84d2032a..86e369c38 100644 --- a/docs/.pages +++ b/docs/.pages @@ -5,7 +5,7 @@ nav: - Enroute: enroute - Oceanic: oceanic - Pacific: pacific - - WorldFlight: worldflight + - Events: events - Separation Standards: separation-standards - Client Usage: client - Controller Skills: controller-skills diff --git a/docs/controller-skills/milkrun.md b/docs/controller-skills/milkrun.md deleted file mode 100644 index 3d10cb262..000000000 --- a/docs/controller-skills/milkrun.md +++ /dev/null @@ -1,335 +0,0 @@ ---- -title: Milk Run Monday ---- - ---8<-- "includes/abbreviations.md" - -
-Milk Run - -Milk Run Monday is a very busy event, that tests the limits of controllers at it's busiest. It is important to understand some processes that makes the event run as smooth as possible for all pilot and controllers involved. The information on this page is extracted from various Local Instructions and Controller Skills pages, collated to give all of the most relevant information to controlling the Milk Run event. - -
- -
-ACD - -## ACD -The job of the ACD controller during Milk Run is a fairly straight-forward one, however there are a couple of things to be mindful of. - -Ensure that all flight plans are correct, nothing like `DOSEL DCT RIVET`, `GPS DIRECT`, or anything else unusual like that, just stick to the pre-approved Jet and Non-Jet routes. This helps reduce workload on Enroute controllers down the line. - -### 16 Off Mode Departures at YMML -A Reminder that [Off Mode Departures from Runway 16](../../aerodromes/classc/Melbourne/#off-mode-departures) to the North East and West during the 16A27D Runway Mode must be assigned the **ISPEG** SID, **NOT** the DOSEL SID. The **ISPEG** SID deconflicts concurrent 16 and 27 departures, whereas the DOSEL SID does not. - -### ACD Pushback Requests -Refer to [Pushback Requests on ACD](#pushback-requests-on-acd) - -
- -
-SMC - -## SMC -### Standard Taxi Routes -[YSSY](../../aerodromes/classc/Sydney/#standard-taxi-routes) and [YMML](../../aerodromes/classc/Melbourne/#standard-taxi-routes) both have Published Standard Taxi Routes that can be used to facilitate the orderly flow of traffic on the ground, but this does not preclude the SMC controller from using alternate routing if they deem it neccessary. - -### Queuing -When giving taxi clearance, the SMC controller shall consider holding aircraft short of taxiways when in a long queue for a holding point, so that blockages are not caused on crossing taxiways. The Hotspots to pay the most attention to are circled below - -
-![YMML Taxiway Hotspots](img/ymmlhotspots.png){ width="700" } -
YMML Taxiway Hotspots
-
- -
-![YSSY Taxiway Hotspots](img/yssyhotspots.png){ width="700" } -
YSSY Taxiway Hotspots
-
- -### Protecting Runway Exits -Arriving aircraft *should* hold short of any crossing taxiways upon exiting the runway, but that doesn't mean they always will! Hold short instructions should be used to protect exit taxiways where practical. - -#### YMML -In order to protect common Runway Exit Taxiways, Consider instructing aircraft taxiing: -- Northbound on Taxiway `V`, to Hold Short of Taxiways `F` and `E` -- Southbound on Taxiway `V`, to Hold Short of Taxiways `G` and `J` - -#### YSSY -In order to protect common Runway Exit Taxiways, Consider instructing aircraft taxiing: -- Northbound on Taxiway `B`, to Hold Short of Taxiway `B8` -- Southbound on Taxiway `A`, to Hold Short of Taxiway `A2` *(34 in use)*, or Taxiway `A4` *(16 in use)* - -!!! note - Utilising these hold short instructions also opens up the availability of taxiways `J` and `Y` as alternative taxi routes on the International terminal side - -### ACD Pushback Requests -Refer to [Pushback Requests on ACD](#pushback-requests-on-acd) - -
- -
-ADC - -## ADC -### Runway Modes -Careful selection of the duty runway at an aerodrome is important to ensure safe, expeditious traffic flow. When considering runway configuration, be mindful of the following operational considerations: -
    -
  1. Wind direction and speed
    2. -
  2. SOP-dictated preferred runway modes
    3. -
  3. Traffic flow and efficiency
    4. -
- -Runway Modes should be selected for maximum aircraft movements, if the winds permit. That is: -- at YSSY: -      - **16 PROPS**; or -      - **34 PROPS** -- at YMML: -      - **27AD34D**; or -      - **16A27D**; or -      - **09A16D** - -!!! Reminder - For dry runways, the crosswind limitation is 20kt, and the tailwind limitation is 5kt. For wet runways, no tailwind component is permitted. Remember these limitations in selecting the runway mode which is best optimised and works within these limitations - -#### Non-Standard Runway Modes -The usage of non-standard runway modes is **strongly not recommended**, unless approved by a Senior Controller for use in major events. Non-Standard runway modes can cause unintended conflicts in TCU and Enroute airspace that may only slightly reduce an ADC controller's workload, but *dramatically* increase that of the affected TCU or Enroute controller. - -!!! example - At YMML, one of the Preferred Runway Modes is 16A27D. If ADC were to add 16 as a departure runway (16AD27D), this may allow them to get more aircraft to depart. However, Subsequent departures from Runway 16, then via 27, both assigned a DOSEL SID, would be pointed directly at each other in TCU airspace, with no separation assurance. This creates a high workload environment for the TCU controller. - -#### Approach Types -At YMML, the approach type in use has neglible affect on the traffic flow. - -However, at YSSY, the use of Instrument Approaches vs Independent Visual Approaches during Parallel Runway operations has a big effect on the workload of the Sydney TCU controller, and how close they can run aircraft together on parallel runways. Refer to [YSSY Approach Types](../../aerodromes/classc/Sydney/#approach-types) for more information. - -#### Runway Changes -Refer to [Runway Management SOPs](../runwaymanagement/#runway-changes) for advice on limiting Runway Mode changes during busy events. - -### Departure Spacing -ADC should be aiming for **90 second** spacing between subsequent departures in the same direction (Obviously for Milk Run, almost all departures will be going the same way). Ensure that [Wake Turbulence Separation](../../separation-standards/runway/#wake-turbulence) is applied when the lead aircraft is of a **heavier** Wake Turbulence category than the following aircraft. It does not need to be applied between two aircraft of the **same** Wake Turbulence category. - -### Line Up -It is best practice for ADC to line-up aircraft on the runway as soon as possible, ie, as soon as the landing aircraft has passed them, or as soon as the departing aircraft has started to roll. This minimises time spent waiting for aircraft to taxi in to position, and potentially cause gaps in the sequence and/or go-arounds. - -!!! suggestion - Appending the phrase "Be ready immediate" to the end of a line up instruction can ensure the pilot has all checklists completed, and is ready to commence takeoff roll as soon as the clearance is given. This reduces airborne delays, and potential go-around situations - -
- -
-TMA - -## TMA -In theory, aircraft should already be nicely sequenced when they enter your airspace, however, this is not always the case. There can also be additional aircraft that come in from other directions that need to be added to the sequence, which can make things challenging. - -In general, try to keep any sequencing actions in the TMA as subtle as possible. Hard vectors, if not managed well, can be detrimental to the rest of the sequence, and have a knock-on effect that creates additional workload for quite a while. - -Try to use techniques like **30 degree vectors**, and **gentle speed control** to achieve the sequence as required in the TMA. - -### SY TMA Roles -When there are multiple controllers online in the Sydney TMA, the workload can be balanced between them as required based on the traffic scenario. - -The *recommended* division of duties for **2** controllers is: - -- **Controller 1:** - - SAS - - SFW - - SFE -- **Controller 2:** - - SAN - - SDN - - SDS - - SRI - -The *recommended* division of duties for **3** controllers is: -- **Controller 1:** - - SAS - - SAN -- **Controller 2:** - - SFW - - SFE -- **Controller 3:** - - SDN - - SDS - - SRI - -Depending on the Runway Mode, additional portions of airspace may be released between controllers as required to help facilitate the orderly flow of traffic. For example, during the **16 PROPS** Mode, it would be beneficial for SDN to release this portion of airspace to the Approach/Director controller, to facilitate aircraft positioning for a final for Runway 16L/R. - -
-![SDN West Release](img/16sdnrls.png){ width="700" } -
SDN West Release
-
- -### Go-arounds -When there is a go-around in the middle of a bumper-to-bumper sequence, a fair bit of work needs to be done. Obviously there is the additional work of having to vector the aircraft that has gone around back for an approach, but also trying to find a gap for them in the sequence, where none such gap currently exists. This is an important time to use coordination, and get the Enroute controller to create one for you. - -!!! example - **MAE** -> **ELW**: "We've had a Go around. Additional 2 minute delay for all aircraft in this sequence please." - **ELW** -> **MAE**: "Copy, additional 2 minute delay for all aircraft in this sequence." - -
- -
-Enroute - -## Enroute -### Early Handoffs -The most important job of the ELW/BLA controller is the sequencing for YMML. Likewise, the most important job of the GUN/BIK controller is the sequencing for YSSY. In order to make the job of these controllers easier, it is beneficial for them to receive aircraft ***as early as possible***, so they can start to execute all the required actions, like assigning a STAR, amending route if required, enacting speed control, and issuing delay vectors or holding if required. - -This is most important for the BLA transfer to GUN, as GUN does not have a lot of airspace to complete the YSSY sequence. -BLA should aim to handoff aircraft to GUN approximately **50nm** to the boundary, unless there is a restriction (which is quite rare). Note that other aircraft going to GUN airspace (ie: Other aircraft on the YMML-YSSY route) are **not** considered a 'Restriction', as the GUN controller can already see them as Blue (Announced) on their display. - -!!! Reminder - [Handoff Rules](../coordination/#handoffs) permit turns of up to **45 degrees left/right**, and **climb/descent to any level** after handoff. Keep this in mind when considering how early you can handoff aircraft to the next sector - -### Arrival Sequencing -Enroute controllers should be aiming for **2 minute** spacing at the feeder fix between subsequent arrivals. This can be reduced slightly to no less than **10nm**, unless **single runway operations** are in use. - -!!! Reminder - At YMML, aircraft on the LIZZI and BOYSE STARs are considered to be on the same STAR for sequencing purposes. Ie, an aircraft via BOYSE must be sequenced 2 minutes behind an aircraft via LIZZI, and vice versa - -#### Speed Control -The most common descent profile to expect for a B738/A320 like aircraft is close to **Mach .78, transitioning in to 280kts**. Keep this in mind when applying speed control to aircraft. That being said, when taking control of an aircraft's speed, it is **always** best practice to ask the pilot what their current speed is first, rather than blindly launching in to an assigned speed with no idea what effect it will have. - -If applying speed control to multiple aircraft in a sequence, there are some handy rules of thumb to be mindful of: -- If the lead aircraft is doing the **same IAS** as the following aircraft, the distance between them will **close** at about **0.5nm per minute** -- If the lead aircraft is going **20kt IAS faster** than the following aircraft, the distance between them will **hold steady** - -#### Responsibilities -**GUN** and **BIK** are responsible for Sequencing in to **YSSY**. **ELW** and **BLA** are responsible for sequencing in to **YMML**. Although it may seem helpful for other sectors to start to apply speed control to assist with the sequence, sometimes this may hinder natural overtakes from occurring, and create bigger gaps in the sequence, making the job harder for the next controller. It also may not take in to consideration aircraft inbound to the arrival airport from other directions, or that the next controller can create multiple arrival streams. - -Best practice is to just focus on providing separation between aircraft (whether that be vertically, laterally, or longitudinally), and only start to apply sequencing techniques once the aircraft reaches the airspace of the responsible sector. - -#### YSSY Arrivals -##### Runway Assignment -Although the standard runway assignment for arrivals via RIVET is the Western Parallel Runway, eventually, the airspace will get busy enough to warrant distributing arrivals between both the Western and Eastern runways. - -##### Amended routing via ODALE -In order to segregate aircraft inbound to different parallel runways, [Amended routing via ODALE](../../enroute/Melbourne Centre/BIK/#sequencing-into-yssy) should be used for aircraft assigned the Eastern parallel runway (16L/34R). This keeps aircraft segregated in to two distinct arrival streams, and allows a higher volume of arrivals. - -Aircraft can be rerouted on first contact via AKMIR, ODALE, then assigned the ODALE7 arrival for 16L/34R. - -
-![Original Flight Planned Route](img/odale1.png){ width="700" } -
Original Flight Planned Route
-
- -
-![Graphical Reroute via AKMIR, ODALE](img/odale2.png){ width="700" } -
Graphical Reroute via AKMIR, ODALE
-
- -
-![Final routing with Assigned STAR](img/odale3.png){ width="700" } -
Final routing with Assigned STAR
-
- -Although this action may be beneficial to the arrival flow for both Enroute and Approach, it goes against the [Standard runway and STAR assignment](../../enroute/Melbourne Centre/BIK/#sequencing-into-yssy) for YSSY Arrivals from the South-west, so must still be coordinated to SAS or SFL (if online) - -!!! example - **GUN** -> **SFL**: "QFA494 will be via ODALE for 34R" - **SFL** -> **GUN**: "QFA494 via ODALE, 34R, Roger" - -In order to reduce this coordination, GUN/BIK and SFL/SAS may organise blanket coordination to allow this rerouting at the discretion of the GUN/BIK controller. - - -

Demonstration of the ODALE Reroute

- -
- -
-Workload Management - -## Workload Management -### Splitting -Never ever ever ever ever (ever) deny an offer to split up your sector! It could be someone offering to take: -- **BLA** from **ELW** -- **WOL** from **BIK** -- **SY_DEP** from **SY_APP** -- **SY-W_GND** from **SY_GND** -The event gets busy every week, and denying offers to split takes away from the potential pool of controllers to help the event run smoothly. It is better to have a bit of a quieter half an hour, then be ready for the busy rush, than it is to have a decent amount of traffic for half an hour, and get completely snowed under after that. - -#### Prioritisation -Some sectors generally require splitting more than others. For example, the Melbourne TMA can usually operate without the need for a Departures controller for the whole event (although if there's no room for an S3 anywhere else, it's still worth having), whilst a second/third controller in the Sydney TMA is always extremely beneficial. Enroute splits such as WOL and BLA are also extremely beneficial to balancing the workload of the event. - -It can also be beneficial to redistribute the ratings across the event. For example, if Sydney TMA has two or three C1+ controllers on, whilst ELW is covering an offline BIK, it would be prudent for one of the Sydney TMA controllers to move up and cover BIK. - -#### Projecting -Project **ahead of time** when your sector will be busy, by looking at things like: -- ADEP Strip List Length -- Announced Strip List Length -- Number of Blue Announced tracks on screen -- Number of Blue Announced tracks when zoomed out - -Use this information to know that you will be busy soon, and put out a request for a split in the [atc-coordination](https://discord.com/channels/343999482737721354/613736441717194755){target=new} discord channel. If you start to encounter things like: -- Aircraft stepping on each other -- Multiple aircraft having to ask for further climb/descent -- Aircraft not listening to your calls -It may already be too late! And to make matters worse, if you wait too long to ask, there might not be any controllers available to split the sector. - -### Pushback Requests on ACD -During the event, the **SMC** at [YMML](../../aerodromes/classc/melbourne) controller may end up with a much higher workload than the **ACD** controller. Additionally, delays may need to be implemented for aircraft requesting pushback, so as to not overload the taxiways and holding points. - -To mitigate this, pushback requests may be done on **ACD** frequency, to balance the workload. A few steps must be followed to properly execute this procedure. - -1. **SMC** and **ACD** coordinate to implement the procedure, due to high **SMC** workload. -2. **SMC** coordinates with **ADC** in order to have the [ATIS](../../aerodromes/classc/melbourne/#acd-pushback-requests) updated. -3. When **ACD** has finished issuing an airways clearance, they will **remind** pilots to *"Contact me when ready for pushback"*. -4. When a pilot requests pushback, **ACD** will instruct them to **Monitor** *(not contact)* Ground on 121.7, and advise their position in the queue. -5. **ACD** will move the strip in to the **Queue** section of the **Cleared** bay^ in [OzStrips](../../client/towerstrips/), to denote they are awaiting pushback approval†. -6. Eventually, **SMC** will have adequate space on the aprons, taxiways, and holding point, as well as time to make assessments. -7. **SMC** will scan the [Cleared Queue bay](../../client/towerstrips/#stripboard) for the next aircraft in line, and call them to approve their pushback. - -!!! example - **ML SMC** -> **ML ACD**: "It's getting quite busy. Happy to implement Pushback requests on your frequency?" - **ML ACD** -> **ML SMC**: "Understood, affirm" - **ML SMC** -> **ML ACD**: "Thanks, I'll talk to Tower" - - **ML SMC** -> **ML ADC**: "Can we please get `ALL DEPARTURES MUST REQUEST PUSH BACK ON 127.2` on the ATIS?" - **ML ADC** -> **ML SMC**: "Wilco" - - **QFA401:** "Melbourne Delivery, QFA401, Request Clearance" - **ML ACD:** "QFA401, Melbourne Delivery. Cleared to..." - **QFA401:** "Cleared to... we are bay B27, QFA401" - **ML ACD:** "QFA401, Contact me when ready for pushback" - ... - **QFA401:** "Request Pushback" - **ML ACD:** "QFA401, Monitor Ground 121.7, Number 5. They will call you when pushback is available" - **QFA401:** "Monitor 121.7, QFA401" - *ML SMC will move QFA401's strip to the* ***Cleared Queue*** *bay* - *QFA401 will change frequency, but* ***not contact*** *ML SMC* - ... - **ML SMC:** "QFA401, Melbourne Ground, push approved" - -#### Queue Management -Remember that the **bottom** aircraft represents the **front** of the queue. - -^ Additionally, the strips must remain in the strip bay of their **current state**, even if they are in a queue. For example, if they have received an airways clearance and are in the queue for pushback, they must remain in the **Cleared** bay, **not** the Pushback bay. - -
-![Cleared Queue Bay](img/clrqbay.png){ width="500" } -
Cleared Queue Bay
-
- -#### COBT Slot Times -† Aircraft that are compliant with their booked slot time should be moved to the **front** of the queue - -
-![COBT Slot Time](img/slottime.png){ width="200" } -
COBT Slot Time
-
- -### Coordination -Regular Coordination with your peers is critical to the efficient operation of a Milk Run. Not only from a control perspective (eg, asking for an early handoff, requesting an amended route, suggested heading for separation between TMA/ENR, etc), but also from a more long-term event management perspective. If things are getting too busy in your airspace, or are about to get very busy, you may elect to: -- Ask the ADC controller for additional departure spacing -- Temporarily Stop departures -- Ask the adjacent Enroute controller for additional spacing -- (As the TMA Controller) Ask the Enroute controller for an additional **2 minute delay for all aircraft**, due to a **go-around** - -It is also important to not accept aircraft that are in conflict! If the TMA controller is trying to handoff two aircraft pointed at each other at the same level, give them a call on the Hotline, and ask them to fix it before handing off to you. Of course you may offer/suggest a solution, but it should not be your conflict to solve. - -
\ No newline at end of file diff --git a/docs/events/.pages b/docs/events/.pages new file mode 100644 index 000000000..91ff001ea --- /dev/null +++ b/docs/events/.pages @@ -0,0 +1,4 @@ +title: Events +nav: + - "Overview": index.md + - ... \ No newline at end of file diff --git a/docs/worldflight/img/01PROPS.png b/docs/events/img/01PROPS.png similarity index 100% rename from docs/worldflight/img/01PROPS.png rename to docs/events/img/01PROPS.png diff --git a/docs/worldflight/img/0306.png b/docs/events/img/0306.png similarity index 100% rename from docs/worldflight/img/0306.png rename to docs/events/img/0306.png diff --git a/docs/worldflight/img/05.png b/docs/events/img/05.png similarity index 100% rename from docs/worldflight/img/05.png rename to docs/events/img/05.png diff --git a/docs/worldflight/img/05A12DSMC.png b/docs/events/img/05A12DSMC.png similarity index 100% rename from docs/worldflight/img/05A12DSMC.png rename to docs/events/img/05A12DSMC.png diff --git a/docs/worldflight/img/05A30DSMC.png b/docs/events/img/05A30DSMC.png similarity index 100% rename from docs/worldflight/img/05A30DSMC.png rename to docs/events/img/05A30DSMC.png diff --git a/docs/worldflight/img/06queue.png b/docs/events/img/06queue.png similarity index 100% rename from docs/worldflight/img/06queue.png rename to docs/events/img/06queue.png diff --git a/docs/worldflight/img/16PROPS Arrivals.png b/docs/events/img/16PROPS Arrivals.png similarity index 100% rename from docs/worldflight/img/16PROPS Arrivals.png rename to docs/events/img/16PROPS Arrivals.png diff --git a/docs/worldflight/img/16PROPS Departures.png b/docs/events/img/16PROPS Departures.png similarity index 100% rename from docs/worldflight/img/16PROPS Departures.png rename to docs/events/img/16PROPS Departures.png diff --git a/docs/controller-skills/img/16sdnrls.png b/docs/events/img/16sdnrls.png similarity index 100% rename from docs/controller-skills/img/16sdnrls.png rename to docs/events/img/16sdnrls.png diff --git a/docs/worldflight/img/19PROPS.png b/docs/events/img/19PROPS.png similarity index 100% rename from docs/worldflight/img/19PROPS.png rename to docs/events/img/19PROPS.png diff --git a/docs/worldflight/img/2124.png b/docs/events/img/2124.png similarity index 100% rename from docs/worldflight/img/2124.png rename to docs/events/img/2124.png diff --git a/docs/worldflight/img/23.png b/docs/events/img/23.png similarity index 100% rename from docs/worldflight/img/23.png rename to docs/events/img/23.png diff --git a/docs/worldflight/img/23A12DSMC.png b/docs/events/img/23A12DSMC.png similarity index 100% rename from docs/worldflight/img/23A12DSMC.png rename to docs/events/img/23A12DSMC.png diff --git a/docs/worldflight/img/23A30DSMC.png b/docs/events/img/23A30DSMC.png similarity index 100% rename from docs/worldflight/img/23A30DSMC.png rename to docs/events/img/23A30DSMC.png diff --git a/docs/worldflight/img/34PROPS Arrivals.png b/docs/events/img/34PROPS Arrivals.png similarity index 100% rename from docs/worldflight/img/34PROPS Arrivals.png rename to docs/events/img/34PROPS Arrivals.png diff --git a/docs/worldflight/img/34PROPS Departures.png b/docs/events/img/34PROPS Departures.png similarity index 100% rename from docs/worldflight/img/34PROPS Departures.png rename to docs/events/img/34PROPS Departures.png diff --git a/docs/worldflight/img/AYPY TCU 14.png b/docs/events/img/AYPY TCU 14.png similarity index 100% rename from docs/worldflight/img/AYPY TCU 14.png rename to docs/events/img/AYPY TCU 14.png diff --git a/docs/worldflight/img/AYPY TCU 32.png b/docs/events/img/AYPY TCU 32.png similarity index 100% rename from docs/worldflight/img/AYPY TCU 32.png rename to docs/events/img/AYPY TCU 32.png diff --git a/docs/worldflight/img/KAT.png b/docs/events/img/KAT.png similarity index 100% rename from docs/worldflight/img/KAT.png rename to docs/events/img/KAT.png diff --git a/docs/worldflight/img/PIY.png b/docs/events/img/PIY.png similarity index 100% rename from docs/worldflight/img/PIY.png rename to docs/events/img/PIY.png diff --git a/docs/worldflight/img/arrlistexample.png b/docs/events/img/arrlistexample.png similarity index 100% rename from docs/worldflight/img/arrlistexample.png rename to docs/events/img/arrlistexample.png diff --git a/docs/worldflight/img/arrlistexample2.png b/docs/events/img/arrlistexample2.png similarity index 100% rename from docs/worldflight/img/arrlistexample2.png rename to docs/events/img/arrlistexample2.png diff --git a/docs/worldflight/img/aypyrtccshade.png b/docs/events/img/aypyrtccshade.png similarity index 100% rename from docs/worldflight/img/aypyrtccshade.png rename to docs/events/img/aypyrtccshade.png diff --git a/docs/worldflight/img/aypysmc.png b/docs/events/img/aypysmc.png similarity index 100% rename from docs/worldflight/img/aypysmc.png rename to docs/events/img/aypysmc.png diff --git a/docs/controller-skills/img/clrqbay.png b/docs/events/img/clrqbay.png similarity index 100% rename from docs/controller-skills/img/clrqbay.png rename to docs/events/img/clrqbay.png diff --git a/docs/worldflight/img/coordinatorbars.png b/docs/events/img/coordinatorbars.png similarity index 100% rename from docs/worldflight/img/coordinatorbars.png rename to docs/events/img/coordinatorbars.png diff --git a/docs/worldflight/img/coordinatorstrips.png b/docs/events/img/coordinatorstrips.png similarity index 100% rename from docs/worldflight/img/coordinatorstrips.png rename to docs/events/img/coordinatorstrips.png diff --git a/docs/worldflight/img/labeldataentry.png b/docs/events/img/labeldataentry.png similarity index 100% rename from docs/worldflight/img/labeldataentry.png rename to docs/events/img/labeldataentry.png diff --git a/docs/controller-skills/img/odale1.png b/docs/events/img/odale1.png similarity index 100% rename from docs/controller-skills/img/odale1.png rename to docs/events/img/odale1.png diff --git a/docs/controller-skills/img/odale2.png b/docs/events/img/odale2.png similarity index 100% rename from docs/controller-skills/img/odale2.png rename to docs/events/img/odale2.png diff --git a/docs/controller-skills/img/odale3.png b/docs/events/img/odale3.png similarity index 100% rename from docs/controller-skills/img/odale3.png rename to docs/events/img/odale3.png diff --git a/docs/worldflight/img/route.png b/docs/events/img/route.png similarity index 100% rename from docs/worldflight/img/route.png rename to docs/events/img/route.png diff --git a/docs/controller-skills/img/slottime.png b/docs/events/img/slottime.png similarity index 100% rename from docs/controller-skills/img/slottime.png rename to docs/events/img/slottime.png diff --git a/docs/worldflight/img/smcntaxi.png b/docs/events/img/smcntaxi.png similarity index 100% rename from docs/worldflight/img/smcntaxi.png rename to docs/events/img/smcntaxi.png diff --git a/docs/worldflight/img/strip1.png b/docs/events/img/strip1.png similarity index 100% rename from docs/worldflight/img/strip1.png rename to docs/events/img/strip1.png diff --git a/docs/worldflight/img/strip2.png b/docs/events/img/strip2.png similarity index 100% rename from docs/worldflight/img/strip2.png rename to docs/events/img/strip2.png diff --git a/docs/worldflight/img/wfcgrerte.png b/docs/events/img/wfcgrerte.png similarity index 100% rename from docs/worldflight/img/wfcgrerte.png rename to docs/events/img/wfcgrerte.png diff --git a/docs/worldflight/img/wfteam.png b/docs/events/img/wfteam.png similarity index 100% rename from docs/worldflight/img/wfteam.png rename to docs/events/img/wfteam.png diff --git a/docs/controller-skills/img/ymmlhotspots.png b/docs/events/img/ymmlhotspots.png similarity index 100% rename from docs/controller-skills/img/ymmlhotspots.png rename to docs/events/img/ymmlhotspots.png diff --git a/docs/worldflight/img/ypaddualbrl.png b/docs/events/img/ypaddualbrl.png similarity index 100% rename from docs/worldflight/img/ypaddualbrl.png rename to docs/events/img/ypaddualbrl.png diff --git a/docs/worldflight/img/ypadgrasstaxi.png b/docs/events/img/ypadgrasstaxi.png similarity index 100% rename from docs/worldflight/img/ypadgrasstaxi.png rename to docs/events/img/ypadgrasstaxi.png diff --git a/docs/worldflight/img/ypadsmcbase.png b/docs/events/img/ypadsmcbase.png similarity index 100% rename from docs/worldflight/img/ypadsmcbase.png rename to docs/events/img/ypadsmcbase.png diff --git a/docs/worldflight/img/ypadsmcown.png b/docs/events/img/ypadsmcown.png similarity index 100% rename from docs/worldflight/img/ypadsmcown.png rename to docs/events/img/ypadsmcown.png diff --git a/docs/worldflight/img/ypdngrass.png b/docs/events/img/ypdngrass.png similarity index 100% rename from docs/worldflight/img/ypdngrass.png rename to docs/events/img/ypdngrass.png diff --git a/docs/controller-skills/img/yssyhotspots.png b/docs/events/img/yssyhotspots.png similarity index 100% rename from docs/controller-skills/img/yssyhotspots.png rename to docs/events/img/yssyhotspots.png diff --git a/docs/events/index.md b/docs/events/index.md new file mode 100644 index 000000000..34b6677e0 --- /dev/null +++ b/docs/events/index.md @@ -0,0 +1,5 @@ +--- + title: Overview +--- + +Contains Event-specific instructions for various Events on the VATPAC Calendar. \ No newline at end of file diff --git a/docs/events/milkrun/.pages b/docs/events/milkrun/.pages new file mode 100644 index 000000000..44651e82f --- /dev/null +++ b/docs/events/milkrun/.pages @@ -0,0 +1,7 @@ +title: Milk Run Monday +nav: + - Overview: index.md + - Aerodrome Control: aerodrome.md + - Terminal Area Control: terminal.md + - Enroute Control: enroute.md + - Workload Management: workload.md \ No newline at end of file diff --git a/docs/events/milkrun/aerodrome.md b/docs/events/milkrun/aerodrome.md new file mode 100644 index 000000000..302227c12 --- /dev/null +++ b/docs/events/milkrun/aerodrome.md @@ -0,0 +1,96 @@ +--- +title: Aerodrome Control +--- + +--8<-- "includes/abbreviations.md" + +## ACD +The job of the ACD controller during Milk Run is a fairly straight-forward one, however there are a couple of things to be mindful of. + +Ensure that all flight plans are correct, nothing like `DOSEL DCT RIVET`, `GPS DIRECT`, or anything else unusual like that, just stick to the pre-approved Jet and Non-Jet routes. This helps reduce workload on Enroute controllers down the line. + +### 16 Off Mode Departures at YMML +A Reminder that [Off Mode Departures from Runway 16](../../../aerodromes/classc/Melbourne/#off-mode-departures) to the North East and West during the 16A27D Runway Mode must be assigned the **ISPEG** SID, **NOT** the DOSEL SID. The **ISPEG** SID deconflicts concurrent 16 and 27 departures, whereas the DOSEL SID does not. + +### ACD Pushback Requests +Refer to [Pushback Requests on ACD](#pushback-requests-on-acd) + +## SMC +### Standard Taxi Routes +[YSSY](../../../aerodromes/classc/Sydney/#standard-taxi-routes) and [YMML](../../../aerodromes/classc/Melbourne/#standard-taxi-routes) both have Published Standard Taxi Routes that can be used to facilitate the orderly flow of traffic on the ground, but this does not preclude the SMC controller from using alternate routing if they deem it neccessary. + +### Queuing +When giving taxi clearance, the SMC controller shall consider holding aircraft short of taxiways when in a long queue for a holding point, so that blockages are not caused on crossing taxiways. The Hotspots to pay the most attention to are circled below + +
+![YMML Taxiway Hotspots](../img/ymmlhotspots.png){ width="700" } +
YMML Taxiway Hotspots
+
+ +
+![YSSY Taxiway Hotspots](../img/yssyhotspots.png){ width="700" } +
YSSY Taxiway Hotspots
+
+ +### Protecting Runway Exits +Arriving aircraft *should* hold short of any crossing taxiways upon exiting the runway, but that doesn't mean they always will! Hold short instructions should be used to protect exit taxiways where practical. + +#### YMML +In order to protect common Runway Exit Taxiways, Consider instructing aircraft taxiing: +- Northbound on Taxiway `V`, to Hold Short of Taxiways `F` and `E` +- Southbound on Taxiway `V`, to Hold Short of Taxiways `G` and `J` + +#### YSSY +In order to protect common Runway Exit Taxiways, Consider instructing aircraft taxiing: +- Northbound on Taxiway `B`, to Hold Short of Taxiway `B8` +- Southbound on Taxiway `A`, to Hold Short of Taxiway `A2` *(34 in use)*, or Taxiway `A4` *(16 in use)* + +!!! note + Utilising these hold short instructions also opens up the availability of taxiways `J` and `Y` as alternative taxi routes on the International terminal side + +### ACD Pushback Requests +Refer to [Pushback Requests on ACD](#pushback-requests-on-acd) + +## ADC +### Runway Modes +Careful selection of the duty runway at an aerodrome is important to ensure safe, expeditious traffic flow. When considering runway configuration, be mindful of the following operational considerations: +
    +
  1. Wind direction and speed
    2. +
  2. SOP-dictated preferred runway modes
    3. +
  3. Traffic flow and efficiency
    4. +
+ +Runway Modes should be selected for maximum aircraft movements, if the winds permit. That is: +- at YSSY: +      - **16 PROPS**; or +      - **34 PROPS** +- at YMML: +      - **27AD34D**; or +      - **16A27D**; or +      - **09A16D** + +!!! Reminder + For dry runways, the crosswind limitation is 20kt, and the tailwind limitation is 5kt. For wet runways, no tailwind component is permitted. Remember these limitations in selecting the runway mode which is best optimised and works within these limitations + +#### Non-Standard Runway Modes +The usage of non-standard runway modes is **strongly not recommended**, unless approved by a Senior Controller for use in major events. Non-Standard runway modes can cause unintended conflicts in TCU and Enroute airspace that may only slightly reduce an ADC controller's workload, but *dramatically* increase that of the affected TCU or Enroute controller. + +!!! example + At YMML, one of the Preferred Runway Modes is 16A27D. If ADC were to add 16 as a departure runway (16AD27D), this may allow them to get more aircraft to depart. However, Subsequent departures from Runway 16, then via 27, both assigned a DOSEL SID, would be pointed directly at each other in TCU airspace, with no separation assurance. This creates a high workload environment for the TCU controller. + +#### Approach Types +At YMML, the approach type in use has neglible affect on the traffic flow. + +However, at YSSY, the use of Instrument Approaches vs Independent Visual Approaches during Parallel Runway operations has a big effect on the workload of the Sydney TCU controller, and how close they can run aircraft together on parallel runways. Refer to [YSSY Approach Types](../../aerodromes/classc/Sydney/#approach-types) for more information. + +#### Runway Changes +Refer to [Runway Management SOPs](../../../controller-skills/runwaymanagement/#runway-changes) for advice on limiting Runway Mode changes during busy events. + +### Departure Spacing +ADC should be aiming for **90 second** spacing between subsequent departures in the same direction (Obviously for Milk Run, almost all departures will be going the same way). Ensure that [Wake Turbulence Separation](../../../separation-standards/runway/#wake-turbulence) is applied when the lead aircraft is of a **heavier** Wake Turbulence category than the following aircraft. It does not need to be applied between two aircraft of the **same** Wake Turbulence category. + +### Line Up +It is best practice for ADC to line-up aircraft on the runway as soon as possible, ie, as soon as the landing aircraft has passed them, or as soon as the departing aircraft has started to roll. This minimises time spent waiting for aircraft to taxi in to position, and potentially cause gaps in the sequence and/or go-arounds. + +!!! suggestion + Appending the phrase "Be ready immediate" to the end of a line up instruction can ensure the pilot has all checklists completed, and is ready to commence takeoff roll as soon as the clearance is given. This reduces airborne delays, and potential go-around situations \ No newline at end of file diff --git a/docs/events/milkrun/enroute.md b/docs/events/milkrun/enroute.md new file mode 100644 index 000000000..584c78e8d --- /dev/null +++ b/docs/events/milkrun/enroute.md @@ -0,0 +1,70 @@ +--- +title: Enroute Control +--- + +--8<-- "includes/abbreviations.md" + +## Early Handoffs +The most important job of the ELW/BLA controller is the sequencing for YMML. Likewise, the most important job of the GUN/BIK controller is the sequencing for YSSY. In order to make the job of these controllers easier, it is beneficial for them to receive aircraft ***as early as possible***, so they can start to execute all the required actions, like assigning a STAR, amending route if required, enacting speed control, and issuing delay vectors or holding if required. + +This is most important for the BLA transfer to GUN, as GUN does not have a lot of airspace to complete the YSSY sequence. +BLA should aim to handoff aircraft to GUN approximately **50nm** to the boundary, unless there is a restriction (which is quite rare). Note that other aircraft going to GUN airspace (ie: Other aircraft on the YMML-YSSY route) are **not** considered a 'Restriction', as the GUN controller can already see them as Blue (Announced) on their display. + +!!! Reminder + [Handoff Rules](../../../controller-skills/coordination/#handoffs) permit turns of up to **45 degrees left/right**, and **climb/descent to any level** after handoff. Keep this in mind when considering how early you can handoff aircraft to the next sector + +## Arrival Sequencing +Enroute controllers should be aiming for **2 minute** spacing at the feeder fix between subsequent arrivals. This can be reduced slightly to no less than **10nm**, unless **single runway operations** are in use. + +!!! Reminder + At YMML, aircraft on the LIZZI and BOYSE STARs are considered to be on the same STAR for sequencing purposes. Ie, an aircraft via BOYSE must be sequenced 2 minutes behind an aircraft via LIZZI, and vice versa + +### Speed Control +The most common descent profile to expect for a B738/A320 like aircraft is close to **Mach .78, transitioning in to 280kts**. Keep this in mind when applying speed control to aircraft. That being said, when taking control of an aircraft's speed, it is **always** best practice to ask the pilot what their current speed is first, rather than blindly launching in to an assigned speed with no idea what effect it will have. + +If applying speed control to multiple aircraft in a sequence, there are some handy rules of thumb to be mindful of: +- If the lead aircraft is doing the **same IAS** as the following aircraft, the distance between them will **close** at about **0.5nm per minute** +- If the lead aircraft is going **20kt IAS faster** than the following aircraft, the distance between them will **hold steady** + +### Responsibilities +**GUN** and **BIK** are responsible for Sequencing in to **YSSY**. **ELW** and **BLA** are responsible for sequencing in to **YMML**. Although it may seem helpful for other sectors to start to apply speed control to assist with the sequence, sometimes this may hinder natural overtakes from occurring, and create bigger gaps in the sequence, making the job harder for the next controller. It also may not take in to consideration aircraft inbound to the arrival airport from other directions, or that the next controller can create multiple arrival streams. + +Best practice is to just focus on providing separation between aircraft (whether that be vertically, laterally, or longitudinally), and only start to apply sequencing techniques once the aircraft reaches the airspace of the responsible sector. + +### YSSY Arrivals +#### Runway Assignment +Although the standard runway assignment for arrivals via RIVET is the Western Parallel Runway, eventually, the airspace will get busy enough to warrant distributing arrivals between both the Western and Eastern runways. + +#### Amended routing via ODALE +In order to segregate aircraft inbound to different parallel runways, [Amended routing via ODALE](../../enroute/Melbourne Centre/BIK/#sequencing-into-yssy) should be used for aircraft assigned the Eastern parallel runway (16L/34R). This keeps aircraft segregated in to two distinct arrival streams, and allows a higher volume of arrivals. + +Aircraft can be rerouted on first contact via AKMIR, ODALE, then assigned the ODALE7 arrival for 16L/34R. + +
+![Original Flight Planned Route](../img/odale1.png){ width="700" } +
Original Flight Planned Route
+
+ +
+![Graphical Reroute via AKMIR, ODALE](../img/odale2.png){ width="700" } +
Graphical Reroute via AKMIR, ODALE
+
+ +
+![Final routing with Assigned STAR](../img/odale3.png){ width="700" } +
Final routing with Assigned STAR
+
+ +Although this action may be beneficial to the arrival flow for both Enroute and Approach, it goes against the [Standard runway and STAR assignment](../../enroute/Melbourne Centre/BIK/#sequencing-into-yssy) for YSSY Arrivals from the South-west, so must still be coordinated to SAS or SFL (if online) + +!!! example + **GUN** -> **SFL**: "QFA494 will be via ODALE for 34R" + **SFL** -> **GUN**: "QFA494 via ODALE, 34R, Roger" + +In order to reduce this coordination, GUN/BIK and SFL/SAS may organise blanket coordination to allow this rerouting at the discretion of the GUN/BIK controller. + + +

Demonstration of the ODALE Reroute

\ No newline at end of file diff --git a/docs/events/milkrun/index.md b/docs/events/milkrun/index.md new file mode 100644 index 000000000..81498e2bb --- /dev/null +++ b/docs/events/milkrun/index.md @@ -0,0 +1,5 @@ +--- + title: Overview +--- + +Milk Run Monday is a very busy event, that tests the limits of controllers at it's busiest. It is important to understand some processes that makes the event run as smooth as possible for all pilot and controllers involved. The information on this page is extracted from various Local Instructions and Controller Skills pages, collated to give all of the most relevant information to controlling the Milk Run event. \ No newline at end of file diff --git a/docs/events/milkrun/terminal.md b/docs/events/milkrun/terminal.md new file mode 100644 index 000000000..effed33d5 --- /dev/null +++ b/docs/events/milkrun/terminal.md @@ -0,0 +1,52 @@ +--- +title: Terminal Area Control +--- + +--8<-- "includes/abbreviations.md" + +In theory, aircraft should already be nicely sequenced when they enter your airspace, however, this is not always the case. There can also be additional aircraft that come in from other directions that need to be added to the sequence, which can make things challenging. + +In general, try to keep any sequencing actions in the TMA as subtle as possible. Hard vectors, if not managed well, can be detrimental to the rest of the sequence, and have a knock-on effect that creates additional workload for quite a while. + +Try to use techniques like **30 degree vectors**, and **gentle speed control** to achieve the sequence as required in the TMA. + +## SY TMA Roles +When there are multiple controllers online in the Sydney TMA, the workload can be balanced between them as required based on the traffic scenario. + +The *recommended* division of duties for **2** controllers is: + +- **Controller 1:** + - SAS + - SFW + - SFE +- **Controller 2:** + - SAN + - SDN + - SDS + - SRI + +The *recommended* division of duties for **3** controllers is: +- **Controller 1:** + - SAS + - SAN +- **Controller 2:** + - SFW + - SFE +- **Controller 3:** + - SDN + - SDS + - SRI + +Depending on the Runway Mode, additional portions of airspace may be released between controllers as required to help facilitate the orderly flow of traffic. For example, during the **16 PROPS** Mode, it would be beneficial for SDN to release this portion of airspace to the Approach/Director controller, to facilitate aircraft positioning for a final for Runway 16L/R. + +
+![SDN West Release](../img/16sdnrls.png){ width="700" } +
SDN West Release
+
+ +## Go-arounds +When there is a go-around in the middle of a bumper-to-bumper sequence, a fair bit of work needs to be done. Obviously there is the additional work of having to vector the aircraft that has gone around back for an approach, but also trying to find a gap for them in the sequence, where none such gap currently exists. This is an important time to use coordination, and get the Enroute controller to create one for you. + +!!! example + **MAE** -> **ELW**: "We've had a Go around. Additional 2 minute delay for all aircraft in this sequence please." + **ELW** -> **MAE**: "Copy, additional 2 minute delay for all aircraft in this sequence." \ No newline at end of file diff --git a/docs/events/milkrun/workload.md b/docs/events/milkrun/workload.md new file mode 100644 index 000000000..7d6defce2 --- /dev/null +++ b/docs/events/milkrun/workload.md @@ -0,0 +1,92 @@ +--- +title: Workload Management +--- + +--8<-- "includes/abbreviations.md" + +## Splitting +Never ever ever ever ever (ever) deny an offer to split up your sector! It could be someone offering to take: +- **BLA** from **ELW** +- **WOL** from **BIK** +- **SY_DEP** from **SY_APP** +- **SY-W_GND** from **SY_GND** +The event gets busy every week, and denying offers to split takes away from the potential pool of controllers to help the event run smoothly. It is better to have a bit of a quieter half an hour, then be ready for the busy rush, than it is to have a decent amount of traffic for half an hour, and get completely snowed under after that. + +### Prioritisation +Some sectors generally require splitting more than others. For example, the Melbourne TMA can usually operate without the need for a Departures controller for the whole event (although if there's no room for an S3 anywhere else, it's still worth having), whilst a second/third controller in the Sydney TMA is always extremely beneficial. Enroute splits such as WOL and BLA are also extremely beneficial to balancing the workload of the event. + +It can also be beneficial to redistribute the ratings across the event. For example, if Sydney TMA has two or three C1+ controllers on, whilst ELW is covering an offline BIK, it would be prudent for one of the Sydney TMA controllers to move up and cover BIK. + +### Projecting +Project **ahead of time** when your sector will be busy, by looking at things like: +- ADEP Strip List Length +- Announced Strip List Length +- Number of Blue Announced tracks on screen +- Number of Blue Announced tracks when zoomed out + +Use this information to know that you will be busy soon, and put out a request for a split in the [atc-coordination](https://discord.com/channels/343999482737721354/613736441717194755){target=new} discord channel. If you start to encounter things like: +- Aircraft stepping on each other +- Multiple aircraft having to ask for further climb/descent +- Aircraft not listening to your calls +It may already be too late! And to make matters worse, if you wait too long to ask, there might not be any controllers available to split the sector. + +## Pushback Requests on ACD +During the event, the **SMC** at [YMML](../../../aerodromes/classc/melbourne) controller may end up with a much higher workload than the **ACD** controller. Additionally, delays may need to be implemented for aircraft requesting pushback, so as to not overload the taxiways and holding points. + +To mitigate this, pushback requests may be done on **ACD** frequency, to balance the workload. A few steps must be followed to properly execute this procedure. + +1. **SMC** and **ACD** coordinate to implement the procedure, due to high **SMC** workload. +2. **SMC** coordinates with **ADC** in order to have the [ATIS](../../../aerodromes/classc/melbourne/#acd-pushback-requests) updated. +3. When **ACD** has finished issuing an airways clearance, they will **remind** pilots to *"Contact me when ready for pushback"*. +4. When a pilot requests pushback, **ACD** will instruct them to **Monitor** *(not contact)* Ground on 121.7, and advise their position in the queue. +5. **ACD** will move the strip in to the **Queue** section of the **Cleared** bay^ in [OzStrips](../../../client/towerstrips/), to denote they are awaiting pushback approval†. +6. Eventually, **SMC** will have adequate space on the aprons, taxiways, and holding point, as well as time to make assessments. +7. **SMC** will scan the [Cleared Queue bay](../../../client/towerstrips/#stripboard) for the next aircraft in line, and call them to approve their pushback. + +!!! example + **ML SMC** -> **ML ACD**: "It's getting quite busy. Happy to implement Pushback requests on your frequency?" + **ML ACD** -> **ML SMC**: "Understood, affirm" + **ML SMC** -> **ML ACD**: "Thanks, I'll talk to Tower" + + **ML SMC** -> **ML ADC**: "Can we please get `ALL DEPARTURES MUST REQUEST PUSH BACK ON 127.2` on the ATIS?" + **ML ADC** -> **ML SMC**: "Wilco" + + **QFA401:** "Melbourne Delivery, QFA401, Request Clearance" + **ML ACD:** "QFA401, Melbourne Delivery. Cleared to..." + **QFA401:** "Cleared to... we are bay B27, QFA401" + **ML ACD:** "QFA401, Contact me when ready for pushback" + ... + **QFA401:** "Request Pushback" + **ML ACD:** "QFA401, Monitor Ground 121.7, Number 5. They will call you when pushback is available" + **QFA401:** "Monitor 121.7, QFA401" + *ML SMC will move QFA401's strip to the* ***Cleared Queue*** *bay* + *QFA401 will change frequency, but* ***not contact*** *ML SMC* + ... + **ML SMC:** "QFA401, Melbourne Ground, push approved" + +### Queue Management +Remember that the **bottom** aircraft represents the **front** of the queue. + +^ Additionally, the strips must remain in the strip bay of their **current state**, even if they are in a queue. For example, if they have received an airways clearance and are in the queue for pushback, they must remain in the **Cleared** bay, **not** the Pushback bay. + +
+![Cleared Queue Bay](../img/clrqbay.png){ width="500" } +
Cleared Queue Bay
+
+ +### COBT Slot Times +† Aircraft that are compliant with their booked slot time should be moved to the **front** of the queue + +
+![COBT Slot Time](../img/slottime.png){ width="200" } +
COBT Slot Time
+
+ +## Coordination +Regular Coordination with your peers is critical to the efficient operation of a Milk Run. Not only from a control perspective (eg, asking for an early handoff, requesting an amended route, suggested heading for separation between TMA/ENR, etc), but also from a more long-term event management perspective. If things are getting too busy in your airspace, or are about to get very busy, you may elect to: +- Ask the ADC controller for additional departure spacing +- Temporarily Stop departures +- Ask the adjacent Enroute controller for additional spacing +- (As the TMA Controller) Ask the Enroute controller for an additional **2 minute delay for all aircraft**, due to a **go-around** + +It is also important to not accept aircraft that are in conflict! If the TMA controller is trying to handoff two aircraft pointed at each other at the same level, give them a call on the Hotline, and ask them to fix it before handing off to you. Of course you may offer/suggest a solution, but it should not be your conflict to solve. \ No newline at end of file diff --git a/docs/worldflight/.pages b/docs/events/worldflight/.pages similarity index 69% rename from docs/worldflight/.pages rename to docs/events/worldflight/.pages index 7d1167854..d8756687e 100644 --- a/docs/worldflight/.pages +++ b/docs/events/worldflight/.pages @@ -1,3 +1,4 @@ +title: WorldFlight 2024 (Archived) nav: - Overview: index.md - Aerodromes diff --git a/docs/worldflight/Aerodromes/.pages b/docs/events/worldflight/Aerodromes/.pages similarity index 100% rename from docs/worldflight/Aerodromes/.pages rename to docs/events/worldflight/Aerodromes/.pages diff --git a/docs/worldflight/Aerodromes/adelaide.md b/docs/events/worldflight/Aerodromes/adelaide.md similarity index 86% rename from docs/worldflight/Aerodromes/adelaide.md rename to docs/events/worldflight/Aerodromes/adelaide.md index 3a1bcc17c..6e70ece3e 100644 --- a/docs/worldflight/Aerodromes/adelaide.md +++ b/docs/events/worldflight/Aerodromes/adelaide.md @@ -23,7 +23,7 @@ An additional Non-Standard position for AD SMC will be used Any other Runway Mode may **only** be used with approval from the Events Coordinator. ## Workload Management -Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow). +Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow). ## Airways Clearance Delivery (ACD) ### Flight Plan Compliance @@ -42,13 +42,13 @@ If an aircraft has filed an *incorrect* route and you need to give an amended cl 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. +[WorldFlight Teams](../../../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. !!! tip The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}
- ![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" } + ![WF Team Highlight with Events Plugin](../../img/wfteam.png){ width="400" }
WF Team Highlight with Events Plugin
@@ -57,12 +57,12 @@ 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](../../img/strip1.png){ width="500" }
Strips Menu
-![Change to Time](../img/strip2.png){ width="500" } +![Change to Time](../../img/strip2.png){ width="500" }
Change to Time
@@ -91,7 +91,7 @@ Work through the OzStrips Preactive bay from *bottom to top* when sending PDCs. ## Surface Movement Control (SMC) ### Areas of Responsibility
-![YPAD SMC Areas of Responsibility](../img/ypadsmcown.png){ width="700" } +![YPAD SMC Areas of Responsibility](../../img/ypadsmcown.png){ width="700" }
YPAD SMC Areas of Responsibility
@@ -109,7 +109,7 @@ SMC will be responsible for delaying aircraft's pushback requests, in order to a 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. +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow) for OzStrips. Ensure the Queue function is used to actively to keep track of the order of requests. @@ -122,7 +122,7 @@ YPAD does not have any gates suitable for A388 parking. A388s must be instructed 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](../../img/smcntaxi.png){ width="700" }
Eastern Terminal Taxi Routes
@@ -130,7 +130,7 @@ During **all** Runway Modes, aircraft shall be instructed to taxi in the followi 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](../../img/ypadsmcbase.png){ width="700" }
YPAD Grass Taxi Routes
@@ -143,7 +143,7 @@ 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](../../img/23A30DSMC.png){ width="700" }
23A30AD SMC Diagram
@@ -154,7 +154,7 @@ 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](../../img/05A30DSMC.png){ width="700" }
05A30AD SMC Diagram
@@ -166,7 +166,7 @@ Runway 05 Departures *(Operational Requirement)* from the Eastern Terminal will 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](../../img/05A12DSMC.png){ width="700" }
05A12D SMC Diagram
@@ -178,7 +178,7 @@ Runway 23 Departures *(Operational Requirement)* will queue to the South West on 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](../../img/23A12DSMC.png){ width="700" }
23A12D SMC Diagram
@@ -197,9 +197,9 @@ Runway 12/30 Departures will be assigned the **AD4** RADAR SID, with the followi | 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. +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. +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" @@ -213,7 +213,7 @@ Use two BRLs anchored on the runway intersection point to monitor distances and Aim for a minimum of **2nm** separation at the instersection.
-![Dual BRL at Intersection](../img/ypaddualbrl.png){ width="500" } +![Dual BRL at Intersection](../../img/ypaddualbrl.png){ width="500" }
Dual BRL at Intersection
@@ -247,7 +247,7 @@ When 23 is in use for Arrivals, The ATIS OPR INFO shall include: ## 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*: +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 | | ---------- | --- | diff --git a/docs/worldflight/Aerodromes/brisbane.md b/docs/events/worldflight/Aerodromes/brisbane.md similarity index 90% rename from docs/worldflight/Aerodromes/brisbane.md rename to docs/events/worldflight/Aerodromes/brisbane.md index e10e97639..e2c687231 100644 --- a/docs/worldflight/Aerodromes/brisbane.md +++ b/docs/events/worldflight/Aerodromes/brisbane.md @@ -14,7 +14,7 @@ *Single Runway* Operations and *SODPROPS* shall not be used. ## Workload Management -Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow). +Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow). ## Airways Clearance Delivery (ACD) ### Flight Plan Compliance @@ -30,13 +30,13 @@ If an aircraft has filed an *incorrect* route and you need to give an amended cl **BN ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YSSY VIA SANEG H91 IGDAM H652 TESAT DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams -[WorldFlight Teams](../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. +[WorldFlight Teams](../../../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. !!! tip The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}
- ![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" } + ![WF Team Highlight with Events Plugin](../../img/wfteam.png){ width="400" }
WF Team Highlight with Events Plugin
@@ -45,12 +45,12 @@ 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](../../img/strip1.png){ width="500" }
Strips Menu
-![Change to Time](../img/strip2.png){ width="500" } +![Change to Time](../../img/strip2.png){ width="500" }
Change to Time
@@ -92,7 +92,7 @@ SMC Domestic and South will be responsible for delaying aircraft's pushback requ 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. +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow) for OzStrips. Ensure the Queue function is used to actively to keep track of the order of requests. diff --git a/docs/worldflight/Aerodromes/darwin.md b/docs/events/worldflight/Aerodromes/darwin.md similarity index 88% rename from docs/worldflight/Aerodromes/darwin.md rename to docs/events/worldflight/Aerodromes/darwin.md index 37d873d27..6a63da96a 100644 --- a/docs/worldflight/Aerodromes/darwin.md +++ b/docs/events/worldflight/Aerodromes/darwin.md @@ -8,7 +8,7 @@ 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 its use as a taxiway for some aircraft. ## Workload Management -Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow). +Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow). ## Airways Clearance Delivery (ACD) ### Flight Plan Compliance @@ -24,13 +24,13 @@ If an aircraft has filed an *incorrect* route and you need to give an amended cl **DN ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO AYPY VIA RUPEG DCT IGOPO B598 ESKIM DCT GUMBU DCT PY DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams -[WorldFlight Teams](../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. +[WorldFlight Teams](../../../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. !!! tip The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}
- ![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" } + ![WF Team Highlight with Events Plugin](../../img/wfteam.png){ width="400" }
WF Team Highlight with Events Plugin
@@ -39,12 +39,12 @@ 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](../../img/strip1.png){ width="500" }
Strips Menu
-![Change to Time](../img/strip2.png){ width="500" } +![Change to Time](../../img/strip2.png){ width="500" }
Change to Time
@@ -70,7 +70,7 @@ SMC will be responsible for delaying aircraft's pushback requests, in order to a 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. +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow) for OzStrips. Ensure the Queue function is used to actively to keep track of the order of requests. @@ -84,7 +84,7 @@ There is only 1 stand suitable for A388 parking (refer to [YPDN Apron Chart](htt 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](../../img/ypdngrass.png){ width="700" }
YPDN Grass Taxi Routes
@@ -106,9 +106,9 @@ Ensure that a minimum of **90 second** spacing is applied between subsequent dep 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. +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. +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:** "BNZ1193, A380 has just departed ahead. Caution Wake Turbulence. Runway 29, Cleared for Takeoff" diff --git a/docs/worldflight/Aerodromes/perth.md b/docs/events/worldflight/Aerodromes/perth.md similarity index 87% rename from docs/worldflight/Aerodromes/perth.md rename to docs/events/worldflight/Aerodromes/perth.md index 8b00a91fa..b6918066c 100644 --- a/docs/worldflight/Aerodromes/perth.md +++ b/docs/events/worldflight/Aerodromes/perth.md @@ -14,7 +14,7 @@ Any other Runway Mode may **only** be used with approval from the Events Coordinator. ## Workload Management -Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow). +Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow). ### 24A21D Simultaneous Independent Crossing Runway Operations will be in use, allowing aircraft to depart from Runway 21 without conflicting with Runway 24 arrivals. @@ -50,13 +50,13 @@ If an aircraft has filed an *incorrect* route and you need to give an amended cl **PH ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO WIII VIA AVNEX Y15 ESDEG Q587 IGLUT T58 SAPDA A585 IPKON IPKO2G. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams -[WorldFlight Teams](../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. +[WorldFlight Teams](../../../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. !!! tip The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}
- ![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" } + ![WF Team Highlight with Events Plugin](../../img/wfteam.png){ width="400" }
WF Team Highlight with Events Plugin
@@ -65,12 +65,12 @@ 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](../../img/strip1.png){ width="500" }
Strips Menu
-![Change to Time](../img/strip2.png){ width="500" } +![Change to Time](../../img/strip2.png){ width="500" }
Change to Time
@@ -103,7 +103,7 @@ SMC East and West will be responsible for delaying aircraft's pushback requests, 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. +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow) for OzStrips. Ensure the Queue function is used to actively to keep track of the order of requests. @@ -127,7 +127,7 @@ Aircraft that cannot accept Intersection **P** for departure will be assigned a #### Maneuvering Area Responsibility Aircraft from the Western Apron shall be taxied via **D** and **N**. -As per the [YPPH Aerodrome SOPs](../../../aerodromes/classc/Perth/#maneuvering-area-responsibility), ADC is responsible for the taxiways between the thresholds of Runway 21 and 24. +As per the [YPPH Aerodrome SOPs](../../../../../../aerodromes/classc/Perth/#maneuvering-area-responsibility), ADC is responsible for the taxiways between the thresholds of Runway 21 and 24. Instead of SMC coordinating runway crossings with ADC, aircraft taxiing via **N** and **C** shall be instructed to **contact ADC** at Holding Point **D**, where ADC will give them taxi instructions on their frequency. No coordination is required between SMC and ADC for this. @@ -151,7 +151,7 @@ Instead of SMC coordinating runway crossings with ADC, aircraft taxiing via **N* 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](../../img/06queue.png){ width="500" }
Runway 06 Queue Paths
@@ -172,7 +172,7 @@ Full Length Departures have **equal priority** to aircraft that are compliant wi #### Maneuvering Area Responsibility Aircraft from the Western Apron shall be taxied via **D** and **N**. -As per the [YPPH Aerodrome SOPs](../../../aerodromes/classc/Perth/#maneuvering-area-responsibility), ADC is responsible for the taxiways between the thresholds of Runway 21 and 24. +As per the [YPPH Aerodrome SOPs](../../../../../../aerodromes/classc/Perth/#maneuvering-area-responsibility), ADC is responsible for the taxiways between the thresholds of Runway 21 and 24. Instead of SMC coordinating runway crossings with ADC, aircraft taxiing via **N** and **C** shall be instructed to **contact ADC** at Holding Point **D**, where ADC will give them taxi instructions on their frequency. No coordination is required between SMC and ADC for this. @@ -210,9 +210,9 @@ When transferring aircraft westbound on Taxiway **D** to **SMC West**, instruct 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. +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. +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" @@ -231,4 +231,4 @@ During 03A06D, the ATIS OPR INFO shall include: ## 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 +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/events/worldflight/Aerodromes/portmoresby.md similarity index 88% rename from docs/worldflight/Aerodromes/portmoresby.md rename to docs/events/worldflight/Aerodromes/portmoresby.md index 8c53c7668..227643cee 100644 --- a/docs/worldflight/Aerodromes/portmoresby.md +++ b/docs/events/worldflight/Aerodromes/portmoresby.md @@ -12,7 +12,7 @@ An additional Non-Standard position for AYPY ACD will be used | Port Moresby Delivery | AYPY ACD | Jacksons Delivery | 124.400 | AYPY_DEL | ## Workload Management -Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow). +Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow). ## Airways Clearance Delivery (ACD) ### Flight Plan Compliance @@ -34,7 +34,7 @@ If an aircraft has filed an *incorrect* route and you need to give an amended cl The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}
- ![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" } + ![WF Team Highlight with Events Plugin](../../img/wfteam.png){ width="400" }
WF Team Highlight with Events Plugin
@@ -43,12 +43,12 @@ 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](../../img/strip1.png){ width="500" }
Strips Menu
-![Change to Time](../img/strip2.png){ width="500" } +![Change to Time](../../img/strip2.png){ width="500" }
Change to Time
@@ -72,7 +72,7 @@ Runway 14R/32L will be used for taxiing. The Runway is released to SMC by defaul Standard taxi directions are shown below.
-![AYPY Standard Taxi Routes](../img/aypysmc.png){ width="700" } +![AYPY Standard Taxi Routes](../../img/aypysmc.png){ width="700" }
AYPY Standard Taxi Routes
@@ -82,7 +82,7 @@ SMC will be responsible for delaying aircraft's pushback requests, in order to a 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. +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow) for OzStrips. Ensure the Queue function is used to actively to keep track of the order of requests. @@ -99,9 +99,9 @@ Runway 14R/32L will be used for taxiing. The Runway is released to SMC by defaul 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. +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. +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" diff --git a/docs/worldflight/Aerodromes/sydneyarr.md b/docs/events/worldflight/Aerodromes/sydneyarr.md similarity index 91% rename from docs/worldflight/Aerodromes/sydneyarr.md rename to docs/events/worldflight/Aerodromes/sydneyarr.md index 975eaa039..b1d62ad93 100644 --- a/docs/worldflight/Aerodromes/sydneyarr.md +++ b/docs/events/worldflight/Aerodromes/sydneyarr.md @@ -16,10 +16,10 @@ The ACD role will perform as normal. Expect a handful of departures who want to ## 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. +With two SMC controllers online, utilise [strip bay bars](../../../../client/towerstrips/#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). +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/#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. @@ -37,7 +37,7 @@ If a crossing is required, coordinate *early* with ADC, who may obtain assurance ## 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. +With two SMC controllers online, utilise [strip bay bars](../../../../client/towerstrips/#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: @@ -63,4 +63,4 @@ While runway crossings will be minimised, should a crossing be required, instruc 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 +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/events/worldflight/Aerodromes/sydneydep.md similarity index 88% rename from docs/worldflight/Aerodromes/sydneydep.md rename to docs/events/worldflight/Aerodromes/sydneydep.md index 8e0cd1630..ca05cf850 100644 --- a/docs/worldflight/Aerodromes/sydneydep.md +++ b/docs/events/worldflight/Aerodromes/sydneydep.md @@ -15,20 +15,20 @@ An additional Non-Standard position for Sydney ACD will be used **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. ## Workload Management -Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../client/towerstrips.md#recommended-workflow). +Due to the extreme workload expected for all positions, the use of the OzStrips plugin for managing aerodrome positions is **mandatory**. Controllers should familiarise themselves with the plugin and the VATPAC [recommended workflow](../../../../client/towerstrips/#recommended-workflow). ## 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 MAXEM Q60 BLACK H309 AD DCT` +`DCT TESAT A576 KADOM H44 MAXEM Q60 KAKLU H309 AD DCT` **OzStrips** will flag any *non-compliant* WF route. If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC. !!! example - **SY-C_DEL:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YPAD VIA KADOM H44 MAXEM Q60 BLACK H309 AD DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* + **SY-C_DEL:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YPAD VIA KADOM H44 MAXEM Q60 KAKLU H309 AD DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams [WorldFlight Teams](../../#official-team-callsigns) shall have `STS/STATE` added to their remarks, and `WF TEAM` added to their Global Ops Field, to ensure they receive priority. @@ -37,7 +37,7 @@ If an aircraft has filed an *incorrect* route and you need to give an amended cl The [vatSys Events Plugin](https://github.com/badvectors/EventsPlugin){target=new} will also highlight WF Teams, as shown below. Click on the link to install it, or alternatively, use the [Plugin Manager](https://github.com/badvectors/PluginManager){target=new}
- ![WF Team Highlight with Events Plugin](../img/wfteam.png){ width="400" } + ![WF Team Highlight with Events Plugin](../../img/wfteam.png){ width="400" }
WF Team Highlight with Events Plugin
@@ -46,12 +46,12 @@ 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](../../img/strip1.png){ width="500" }
Strips Menu
-![Change to Time](../img/strip2.png){ width="500" } +![Change to Time](../../img/strip2.png){ width="500" }
Change to Time
@@ -64,7 +64,7 @@ YSSY will have a non-standard second ACD Controller. **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)) +- 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. @@ -100,18 +100,18 @@ PDCs will be in use by default, to avoid frequency congestion. ACD shall send a OzStrips displays strips in the Preactive bay ordered by connection time. Aircraft who connected first are shown down the bottom of the bay. ## Coordinator -Coordinator operations shall be conducted in accordance with the Sydney Aerodrome [Coordinator](../../aerodromes/classc/Sydney.md#sydney-coordinator) procedures, using the OzStrips plugin. +Coordinator operations shall be conducted in accordance with the Sydney Aerodrome [Coordinator](../../../../aerodromes/classc/Sydney/#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. +All aerodrome controllers must be familiar with the VATPAC [recommended workflow](../../../../client/towerstrips/#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" } +![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. @@ -119,7 +119,7 @@ When less than **three** strips are present below a particular `MONITOR GROUND` A Custom `PDC SENT` bar should be created in the Preactive window, to keep track of who has and hasn't received a PDC.
-![Coordinator Strips](../img/coordinatorstrips.png){ width="500" } +![Coordinator Strips](../../img/coordinatorstrips.png){ width="500" }
An example of the Coordinator layout
@@ -133,7 +133,7 @@ If three strips are already present below a respective bar, any subsequent aircr **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. + Ensure aircraft are [squawking mode C and the correct code](../../../../client/towerstrips/#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. @@ -144,7 +144,7 @@ Aircraft can expect **extensive** delays for Pushback during the event, possibly ## 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. +With two SMC controllers online, utilise [strip bay bars](../../../../client/towerstrips/#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. @@ -168,7 +168,7 @@ SMC West should protect the Alpha 2 rapid exit and utilise taxiways Yankee and J ## 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. +With two SMC controllers online, utilise [strip bay bars](../../../../client/towerstrips/#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. @@ -198,7 +198,7 @@ The ATIS OPR INFO shall include: ## 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: +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** diff --git a/docs/worldflight/Enroute/.pages b/docs/events/worldflight/Enroute/.pages similarity index 100% rename from docs/worldflight/Enroute/.pages rename to docs/events/worldflight/Enroute/.pages diff --git a/docs/worldflight/Enroute/aypyybbn.md b/docs/events/worldflight/Enroute/aypyybbn.md similarity index 96% rename from docs/worldflight/Enroute/aypyybbn.md rename to docs/events/worldflight/Enroute/aypyybbn.md index d69e8fc16..7a1501f5a 100644 --- a/docs/worldflight/Enroute/aypyybbn.md +++ b/docs/events/worldflight/Enroute/aypyybbn.md @@ -86,7 +86,7 @@ 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). +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. @@ -108,9 +108,9 @@ Voiceless for all aircraft: 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). +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). +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. diff --git a/docs/worldflight/Enroute/wammypdn.md b/docs/events/worldflight/Enroute/wammypdn.md similarity index 75% rename from docs/worldflight/Enroute/wammypdn.md rename to docs/events/worldflight/Enroute/wammypdn.md index 266ac3b60..c54a96ec6 100644 --- a/docs/worldflight/Enroute/wammypdn.md +++ b/docs/events/worldflight/Enroute/wammypdn.md @@ -23,10 +23,10 @@ Minimum distance between arrivals at handoff to DAW is **10nm** (with no signifi ## 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. +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 +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/events/worldflight/Enroute/ybbnyssy.md similarity index 93% rename from docs/worldflight/Enroute/ybbnyssy.md rename to docs/events/worldflight/Enroute/ybbnyssy.md index 7f359b115..8f5963fb8 100644 --- a/docs/worldflight/Enroute/ybbnyssy.md +++ b/docs/events/worldflight/Enroute/ybbnyssy.md @@ -61,15 +61,15 @@ Changes to Route and CFL are **permitted** within **50nm** of the boundary, with Aircraft must be tracking via **BOREE** or **MEPIL**. ### CNK to SAS/SAN -Standard as per [ARL Local Instructions](../../../enroute/Brisbane Centre/ARL/#arrivalsoverfliers). +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). +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). +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. diff --git a/docs/worldflight/Enroute/ypadypph.md b/docs/events/worldflight/Enroute/ypadypph.md similarity index 92% rename from docs/worldflight/Enroute/ypadypph.md rename to docs/events/worldflight/Enroute/ypadypph.md index 3b69b5da3..794544888 100644 --- a/docs/worldflight/Enroute/ypadypph.md +++ b/docs/events/worldflight/Enroute/ypadypph.md @@ -80,19 +80,19 @@ 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: +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](../../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). +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). +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. diff --git a/docs/worldflight/Enroute/ypdnaypy.md b/docs/events/worldflight/Enroute/ypdnaypy.md similarity index 100% rename from docs/worldflight/Enroute/ypdnaypy.md rename to docs/events/worldflight/Enroute/ypdnaypy.md diff --git a/docs/worldflight/Enroute/ypphwiii.md b/docs/events/worldflight/Enroute/ypphwiii.md similarity index 73% rename from docs/worldflight/Enroute/ypphwiii.md rename to docs/events/worldflight/Enroute/ypphwiii.md index b2b6d8a92..9b78caa29 100644 --- a/docs/worldflight/Enroute/ypphwiii.md +++ b/docs/events/worldflight/Enroute/ypphwiii.md @@ -23,10 +23,10 @@ Aircraft shall have their **identification terminated** on handoff to INE, and i **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. +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 + 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 @@ -38,7 +38,7 @@ Voiceless for all aircraft: 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. +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/events/worldflight/Enroute/yssyypad.md similarity index 88% rename from docs/worldflight/Enroute/yssyypad.md rename to docs/events/worldflight/Enroute/yssyypad.md index 30379ecf4..62a148ca2 100644 --- a/docs/worldflight/Enroute/yssyypad.md +++ b/docs/events/worldflight/Enroute/yssyypad.md @@ -9,7 +9,7 @@ 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](../../img/KAT.png){ width="700" }
KAT Area of Responsibility
@@ -45,12 +45,12 @@ TBD will be responsible for issuing STAR clearances in to YPAD, and providing th 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 23 Arrivals shall be issued the **KAKLU1A** STAR. +Runway 05 Arrivals shall be issued the **KAKLU1Z** 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*. +**All aircraft** must be instructed to cross **KAKLU**/**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). @@ -61,7 +61,7 @@ Minimum distance between arrivals at handoff to AAE is **10nm** (with no signifi 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 + 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 @@ -78,14 +78,14 @@ Voiceless for all aircraft: - With ADES **YPAD**; and - Assigned `A090`; and -- Assigned the **BLACK3A/23** STAR; or -- Assigned the **BLACK3Z/05** STAR; or +- Assigned the **KAKLU1A/23** STAR; or +- Assigned the **KAKLU1Z/05** STAR; or - Tracking **DRINA** DCT **PADEL** #### Between TBD and AFL -AFL will construct the sequence via the [Arrivals List Window](../../../controller-skills/sequencing/#arrivals-list). +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). +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. diff --git a/docs/worldflight/Terminal Areas/.pages b/docs/events/worldflight/Terminal Areas/.pages similarity index 100% rename from docs/worldflight/Terminal Areas/.pages rename to docs/events/worldflight/Terminal Areas/.pages diff --git a/docs/worldflight/Terminal Areas/adelaide.md b/docs/events/worldflight/Terminal Areas/adelaide.md similarity index 77% rename from docs/worldflight/Terminal Areas/adelaide.md rename to docs/events/worldflight/Terminal Areas/adelaide.md index 7ca0fd3bf..2c8459f12 100644 --- a/docs/worldflight/Terminal Areas/adelaide.md +++ b/docs/events/worldflight/Terminal Areas/adelaide.md @@ -5,7 +5,7 @@ --8<-- "includes/abbreviations.md" ## Airspace Division -Standard airspace division will be in use as per [AD TCU Local Instructions](../../../terminal/adelaide/#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: @@ -22,7 +22,7 @@ The **dashed green** line represents the *suggested vectors* for [12/30 departur ### 05
-![05 Arrival/Departure Routes](../img/05.png){ width="700" } +![05 Arrival/Departure Routes](../../img/05.png){ width="700" }
05 Arrival/Departure Routes
@@ -32,7 +32,7 @@ All arrivals on Runway 30 will be cleared for the **RNP** Approach. Visual appro ### 23
-![23 Arrival/Departure Routes](../img/23.png){ width="700" } +![23 Arrival/Departure Routes](../../img/23.png){ width="700" }
23 Arrival/Departure Routes
@@ -46,11 +46,11 @@ 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 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). +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). +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. @@ -71,21 +71,21 @@ That is, two arrivals in to Runway 05/23 spaced out by 2 minutes each, followed **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. +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. +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*. +TBD will instruct all arrivals to cross **KAKLU**/**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*: +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 | | ---------- | --- | @@ -117,8 +117,8 @@ Voiceless for all aircraft: - With ADES **YPAD**; and - Assigned `A090`; and -- Assigned the **BLACK3A/23** STAR; or -- Assigned the **BLACK3Z/05** STAR; or +- Assigned the **KAKLU1A/23** STAR; or +- Assigned the **KAKLU1Z/05** STAR; or - Tracking **DRINA** DCT **PADEL** TBD has *no Restrictions or Requirements* on YPAD departures tracking DCT **LONLY** diff --git a/docs/worldflight/Terminal Areas/brisbane.md b/docs/events/worldflight/Terminal Areas/brisbane.md similarity index 91% rename from docs/worldflight/Terminal Areas/brisbane.md rename to docs/events/worldflight/Terminal Areas/brisbane.md index e051da513..0cd6ae327 100644 --- a/docs/worldflight/Terminal Areas/brisbane.md +++ b/docs/events/worldflight/Terminal Areas/brisbane.md @@ -14,7 +14,7 @@ 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](../../img/01PROPS.png){ width="700" }
01 PROPS Airspace Division
@@ -34,7 +34,7 @@ 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](../../img/19PROPS.png){ width="700" }
19 PROPS Airspace Division
@@ -58,9 +58,9 @@ Although not used at YBBN normally, IVAs can be expected to be in use for WorldF Aircraft must report both **visual**, *and* **runway in sight** in order to be cleared for an IVA (Runway in Sight implies Visual). !!! tip - The [Label Data Annotations](../../../client/annotations/#miscellaneous) for these are `V` and `R`, respectively + 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) +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. @@ -98,9 +98,9 @@ In order to balance workload effectively, it is recommended to distribute respon ## 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). +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). +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. diff --git a/docs/worldflight/Terminal Areas/darwin.md b/docs/events/worldflight/Terminal Areas/darwin.md similarity index 87% rename from docs/worldflight/Terminal Areas/darwin.md rename to docs/events/worldflight/Terminal Areas/darwin.md index 63380910e..18e71cf25 100644 --- a/docs/worldflight/Terminal Areas/darwin.md +++ b/docs/events/worldflight/Terminal Areas/darwin.md @@ -5,7 +5,7 @@ --8<-- "includes/abbreviations.md" ## Airspace Division -Standard airspace division will be in use as per [DN TCU Local Instructions](../../../terminal/darwin/#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. @@ -43,4 +43,4 @@ Voiceless for all aircraft: 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 +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/events/worldflight/Terminal Areas/perth.md similarity index 76% rename from docs/worldflight/Terminal Areas/perth.md rename to docs/events/worldflight/Terminal Areas/perth.md index 447054dd7..f110c7b0d 100644 --- a/docs/worldflight/Terminal Areas/perth.md +++ b/docs/events/worldflight/Terminal Areas/perth.md @@ -19,7 +19,7 @@ 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](../../img/2124.png){ width="700" }
24A21D Airspace Division
@@ -40,16 +40,16 @@ 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](../../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). +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). +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. @@ -63,9 +63,9 @@ The times below indicate the number of minutes from **KABLI** to the Runway Thre 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. +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. +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" @@ -80,7 +80,7 @@ The **KABLI1A** STAR is approximately **2 minutes** *longer* on Runway 21 vs Run ## 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) +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: @@ -91,19 +91,19 @@ Voiceless for all aircraft: 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: +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](../../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). +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). +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. diff --git a/docs/worldflight/Terminal Areas/portmoresby.md b/docs/events/worldflight/Terminal Areas/portmoresby.md similarity index 91% rename from docs/worldflight/Terminal Areas/portmoresby.md rename to docs/events/worldflight/Terminal Areas/portmoresby.md index 205fb01dc..50f5293b0 100644 --- a/docs/worldflight/Terminal Areas/portmoresby.md +++ b/docs/events/worldflight/Terminal Areas/portmoresby.md @@ -21,7 +21,7 @@ The **green** line represents the SID to **NUPTA**. ### 14
-![Runway 14 Airspace Division](../img/AYPY TCU 14.png){ width="700" } +![Runway 14 Airspace Division](../../img/AYPY TCU 14.png){ width="700" }
Runway 14 Airspace Division
@@ -30,7 +30,7 @@ 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](../../img/AYPY TCU 32.png){ width="700" }
Runway 32 Airspace Division
@@ -43,7 +43,7 @@ All arrivals on Runway 32 will be cleared for the **ILS** Approach. 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](../../img/aypyrtccshade.png){ width="700" }
AYPY RTCC
diff --git a/docs/worldflight/Terminal Areas/sydneyarr.md b/docs/events/worldflight/Terminal Areas/sydneyarr.md similarity index 77% rename from docs/worldflight/Terminal Areas/sydneyarr.md rename to docs/events/worldflight/Terminal Areas/sydneyarr.md index 9e881dab8..b76ea240c 100644 --- a/docs/worldflight/Terminal Areas/sydneyarr.md +++ b/docs/events/worldflight/Terminal Areas/sydneyarr.md @@ -12,7 +12,7 @@ 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](../../img/16PROPS Arrivals.png){ width="700" }
16 PROPS Airspace Division
@@ -23,7 +23,7 @@ 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](../../img/34PROPS Arrivals.png){ width="700" }
34 PROPS Airspace Division
@@ -39,9 +39,9 @@ IVAs can be expected to be in use for WorldFlight, to facilitate the high volume Aircraft must report both **visual**, *and* **runway in sight** in order to be cleared for an IVA (Runway in Sight implies Visual). !!! tip - The [Label Data Annotations](../../../client/annotations/#miscellaneous) for these are `V` and `R`, respectively + 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) +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. @@ -71,21 +71,21 @@ In order to balance workload effectively, it is recommended to distribute respon - 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 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). +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). +Appropriate annotations for the Arrivals List Window can be found [here](../../../../../../client/annotations/#sequencingflow). ### Speeds CNK will instruct all arrivals to cross **BOREE** and **YAKKA** at **250 knots**, then *published STAR speeds*. ## Coordination ### APP to DIR -Standard as per [SY TCU Local Instructions](../../../terminal/sydney/#app-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). +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. diff --git a/docs/worldflight/Terminal Areas/sydneydep.md b/docs/events/worldflight/Terminal Areas/sydneydep.md similarity index 81% rename from docs/worldflight/Terminal Areas/sydneydep.md rename to docs/events/worldflight/Terminal Areas/sydneydep.md index fd7ebf1f2..79a3efd7c 100644 --- a/docs/worldflight/Terminal Areas/sydneydep.md +++ b/docs/events/worldflight/Terminal Areas/sydneydep.md @@ -13,14 +13,14 @@ The **dashed** green line represents the *suggested vectors* for [16L/34R depart ### 16 PROPS
-![16 PROPS Airspace Division](../img/16PROPS Departures.png){ width="700" } +![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](../../img/34PROPS Departures.png){ width="700" }
34 PROPS Airspace Division
@@ -30,7 +30,7 @@ Departures from 16L/34R will be assigned the **SY3** SID with a heading of **H12 ## Coordination ### SY ADC #### Auto Release -Standard as per [SY TCU Local Instructions](../../../terminal/sydney/#sy-adc), with the exception of: +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** diff --git a/docs/worldflight/index.md b/docs/events/worldflight/index.md similarity index 95% rename from docs/worldflight/index.md rename to docs/events/worldflight/index.md index 117085d27..edbf6b06b 100644 --- a/docs/worldflight/index.md +++ b/docs/events/worldflight/index.md @@ -27,5 +27,5 @@ The list of callsigns is below: ## Route
-![WorldFlight Route](img/route.png){ width="800" } +![WorldFlight Route](../img/route.png){ width="800" }
\ No newline at end of file diff --git a/docs/terminal/adelaide.md b/docs/terminal/adelaide.md index 01d5d4e1f..9573bf267 100644 --- a/docs/terminal/adelaide.md +++ b/docs/terminal/adelaide.md @@ -92,7 +92,7 @@ The times assume there is *Nil wind*. | ---------- | --- | ------- | ----- | --- | | ALEXI | 14 | 13 | - | - | | DRINA | - | - | 14 | 13 | -| BLACK | 16 | 15 | 12^ | - | +| KAKLU | 16 | 15 | 12^ | - | | KLAVA | 16 | 15 | 13 | 12 | | ERITH | - | - | 13 | 12 | | MARGO | 14 | 13 | 15 | 13 | @@ -124,7 +124,7 @@ For Non-Jets tracking via the *full Jet STARs*, see [table above](#jets) | ---------- | --- | --- | --- | --- | | ALEXI | 12 | 14 | 12 | 11 | | DRINA | 14 | 17 | 14 | 13 | -| BLACK | 16 | 15 | 13 | 13 | +| KAKLU | 16 | 15 | 13 | 13 | | RUSSL | 17 | 15 | 14 | 13 | | KLAVA | 15 | 13 | 13 | 16 | | ERITH | - | - | - | - | diff --git a/mkdocs.yml b/mkdocs.yml index 780f80852..4701fcc74 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -91,6 +91,7 @@ plugins: 'controller-skills/cpdlc.md': 'client/cpdlc.md' 'controller-skills/maestro.md': 'client/maestro.md' 'controller-skills/vatsys.md': 'client/vatsys.md' + 'controller-skills/milkrun.md': 'events/milkrun.md/' # Styling Front-end extra_css: diff --git a/overrides/home.html b/overrides/home.html index a26843758..8595d7cee 100644 --- a/overrides/home.html +++ b/overrides/home.html @@ -30,7 +30,7 @@

Featured Changes

- +

Milk Run Monday

From 754f94e96ad43b3c23d6f5556c84c03451dfd72d Mon Sep 17 00:00:00 2001 From: Matt Kelly <41880668+mattkelly4@users.noreply.github.com> Date: Wed, 20 Nov 2024 11:32:51 +1100 Subject: [PATCH 4/6] Fix broken links --- docs/events/milkrun/aerodrome.md | 10 +++++----- docs/events/worldflight/Terminal Areas/perth.md | 2 +- mkdocs.yml | 1 - 3 files changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/events/milkrun/aerodrome.md b/docs/events/milkrun/aerodrome.md index 302227c12..67e6c9ab9 100644 --- a/docs/events/milkrun/aerodrome.md +++ b/docs/events/milkrun/aerodrome.md @@ -12,8 +12,8 @@ Ensure that all flight plans are correct, nothing like `DOSEL DCT RIVET`, `GPS D ### 16 Off Mode Departures at YMML A Reminder that [Off Mode Departures from Runway 16](../../../aerodromes/classc/Melbourne/#off-mode-departures) to the North East and West during the 16A27D Runway Mode must be assigned the **ISPEG** SID, **NOT** the DOSEL SID. The **ISPEG** SID deconflicts concurrent 16 and 27 departures, whereas the DOSEL SID does not. -### ACD Pushback Requests -Refer to [Pushback Requests on ACD](#pushback-requests-on-acd) +### ACD/Coordinator Pushback Requests +Specific procedures apply to the use of [Pushback Requests on ACD](../../aerodromes/classc/Melbourne.md#pushback-requests-on-acd) at YMML and [Coordinator](../../aerodromes/classc/Sydney.md#sydney-coordinator) at YSSY. Ensure that all relevant controllers are following these procedures accurately. ## SMC ### Standard Taxi Routes @@ -43,13 +43,13 @@ In order to protect common Runway Exit Taxiways, Consider instructing aircraft t #### YSSY In order to protect common Runway Exit Taxiways, Consider instructing aircraft taxiing: - Northbound on Taxiway `B`, to Hold Short of Taxiway `B8` -- Southbound on Taxiway `A`, to Hold Short of Taxiway `A2` *(34 in use)*, or Taxiway `A4` *(16 in use)* +- Southbound on Taxiway `A`, to Hold Short of `Runway 25` *(34 in use)*, or avoid Taxiway `A` if an aircraft is landing on Runway 16R and will be vacating to the right *(16 in use)* !!! note Utilising these hold short instructions also opens up the availability of taxiways `J` and `Y` as alternative taxi routes on the International terminal side -### ACD Pushback Requests -Refer to [Pushback Requests on ACD](#pushback-requests-on-acd) +### ACD/Coordinator Pushback Requests +Specific procedures apply to the use of [Pushback Requests on ACD](../../aerodromes/classc/Melbourne.md#pushback-requests-on-acd) at YMML and [Coordinator](../../aerodromes/classc/Sydney.md#sydney-coordinator) at YSSY. Ensure that all relevant controllers are following these procedures accurately. ## ADC ### Runway Modes diff --git a/docs/events/worldflight/Terminal Areas/perth.md b/docs/events/worldflight/Terminal Areas/perth.md index f110c7b0d..1dbb01507 100644 --- a/docs/events/worldflight/Terminal Areas/perth.md +++ b/docs/events/worldflight/Terminal Areas/perth.md @@ -37,7 +37,7 @@ 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). +The **dashed green** line represents the *suggested vectors* for 06 departures.

![03A06D Airspace Division](../../img/0306.png){ width="700" } diff --git a/mkdocs.yml b/mkdocs.yml index 4701fcc74..780f80852 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -91,7 +91,6 @@ plugins: 'controller-skills/cpdlc.md': 'client/cpdlc.md' 'controller-skills/maestro.md': 'client/maestro.md' 'controller-skills/vatsys.md': 'client/vatsys.md' - 'controller-skills/milkrun.md': 'events/milkrun.md/' # Styling Front-end extra_css: From 1ab7422dd4fd6c1ee7878e70bf960bce378c52d0 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Wed, 20 Nov 2024 19:50:25 +1100 Subject: [PATCH 5/6] BN rwys and std hdg --- docs/aerodromes/classc/Brisbane.md | 40 +++++++++++++++++++++++------- docs/aerodromes/classc/Sydney.md | 2 +- docs/terminal/brisbane.md | 21 +++++++++++++--- 3 files changed, 50 insertions(+), 13 deletions(-) diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index 913086957..5b308dc3b 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -80,14 +80,22 @@ When using the SODPROPS mode, pass traffic information to aircraft that are depa Refer to [Parallel Runway Separation Standards](../../../separation-standards/parallelapps) for more information ### Runway Selection -During PROPS, aircraft tracking via *any* of the following shall be assigned Runway **01L/19R** for departure: -- **BIXAD** -- **AKOBA** -- **BUGNU** -- **ITIDE** - -*All other* aircraft shall be assigned Runway **01R/19L** for departure. +| Aircraft tracking | Runway | +| ----------------| --------- | +| via ITIDE | 01L/19R | +| via BIXAD | 01L/19R | +| via BUGNU | 01L/19R | +| via AKOBA | 01L/19R | +| via WACKO | **01R**/19R | +| via SAMVI | 01L/19R | +| via SANEG | 01R/19L | +| via LAGOB | 01R/19L | +| via SCOTT | 01R/19L | +| via GUMKI | 01R/19L | +| Other aircraft: | +| To the NORTH WEST | 01L/19R | +| All other directions | 01R/19L | ## SID Selection Jet Aircraft planned via **BIXAD**, **GUMKI**, **SCOTT**, **SANEG**, or **WACKO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus^, unless the pilot indicates they are unable to accept a Procedural SID. @@ -119,7 +127,8 @@ The ATIS shall always have `EXP INST APCH` as the approach type. Visual Approach - Departing from a runway nominated on the ATIS (except during SODPROPS^); and - Assigned the standard assignable level; and -- Assigned a **Procedural** SID +- Assigned a **Procedural** SID; or +- Assigned the **Radar** SID with a [Standard Assignable Heading](#standard-assignable-departure-headings) ^Auto Release is not available during SODPROPS runway mode. All aircraft must be coordinated from BN ADC to BN TCU. @@ -140,4 +149,17 @@ For Jets: `A060` For Non-Jets: The lower of `A040` or the `RFL` ### Departures Controller -Refer to [Brisbane TCU Airspace Division](../../../terminal/brisbane/#airspace-division) for information on airspace divisions when **BDN** and/or **BDS** are online. \ No newline at end of file +Refer to [Brisbane TCU Airspace Division](../../../terminal/brisbane/#airspace-division) for information on airspace divisions when **BDN** and/or **BDS** are online. + +### Standard Assignable Departure Headings +Aircraft that have been cleared the **BN (RADAR) SID** must receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required (excluding during SODPROPS) to the BN TCU controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below: + +| Runway | Assigned Heading +| ----------------- | -------------- | +| 01L | H340 | +| 01R | H120 | +| 19L | H110 | +| 19R | H270 | + +!!! tip + If strong winds are present at altitude, ADC/DEP should discuss slight changes to these headings (+/- 5 degrees) to compensate for large crosswind components. \ No newline at end of file diff --git a/docs/aerodromes/classc/Sydney.md b/docs/aerodromes/classc/Sydney.md index 42a023581..3e1384d32 100644 --- a/docs/aerodromes/classc/Sydney.md +++ b/docs/aerodromes/classc/Sydney.md @@ -436,7 +436,7 @@ Aircraft that have been cleared the **SY (RADAR) SID** must receive an assigned | 34R | 030, 070 | 350 | !!! tip - If strong winds are present at altitude, TWR/DEP should discuss slight changes to these headings (+/- 5 degrees) to compensate for large crosswind components. + If strong winds are present at altitude, ADC/DEP should discuss slight changes to these headings (+/- 5 degrees) to compensate for large crosswind components. ### Between ADC and SMC #### Inactive Runway Releases diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md index 155221c53..bbf55f925 100644 --- a/docs/terminal/brisbane.md +++ b/docs/terminal/brisbane.md @@ -155,9 +155,11 @@ All other aircraft coming from INL CTA will be **Heads-up** Coordinated to BN TC ### BN ADC #### Auto Release 'Next' coordination is **not** required from BN ADC for aircraft that are: - a) Departing from a runway nominated on the ATIS (except during SODPROPS^); and - b) Assigned the standard assignable level; and - c) Assigned a **Procedural** SID + +- Departing from a runway nominated on the ATIS (except during SODPROPS^); and +- Assigned the standard assignable level; and +- Assigned a **Procedural** SID; or +- Assigned the **Radar** SID with a [Standard Assignable Heading](#standard-assignable-departure-headings) ^Auto Release is not available during SODPROPS runway mode. All aircraft will be coordinated from BN ADC to BN TCU. @@ -170,6 +172,19 @@ The Standard Assignable level from BN ADC to BN TCU is: For Jets: `A060` For Non-Jets: The lower of `A040` or the `RFL` +#### Standard Assignable Departure Headings +Aircraft that have been cleared the **BN (RADAR) SID** will receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required (excluding during SODPROPS) from the BN ADC controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below: + +| Runway | Assigned Heading +| ----------------- | -------------- | +| 01L | H340 | +| 01R | H120 | +| 19L | H110 | +| 19R | H270 | + +!!! tip + If strong winds are present at altitude, ADC/DEP should discuss slight changes to these headings (+/- 5 degrees) to compensate for large crosswind components. + ### CG ADC #### Airspace CG ADC is responsible for the Class C Airspace within the CG CTR `SFC` to `A015`. From 593550e811d35b9431b558df4e6f8dfe52b15a4e Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Wed, 20 Nov 2024 19:53:20 +1100 Subject: [PATCH 6/6] 2412 --- docs/enroute/Brisbane Centre/ARL.md | 4 ++-- docs/enroute/Melbourne Centre/TBD.md | 2 +- docs/events/worldflight/Enroute/ybbnyssy.md | 4 ++-- docs/terminal/adelaide.md | 16 ++++++++-------- docs/terminal/sydney.md | 2 +- 5 files changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/enroute/Brisbane Centre/ARL.md b/docs/enroute/Brisbane Centre/ARL.md index f770fff3f..ab742bac7 100644 --- a/docs/enroute/Brisbane Centre/ARL.md +++ b/docs/enroute/Brisbane Centre/ARL.md @@ -106,8 +106,8 @@ Non-jet aircraft for YSSY shall be assigned the **MEPIL** STAR. !!! example **BIK:** "RXA6417, amended tracking and STAR available" **RXA6417:** "RXA6417, go ahead" - **BIK:** "RXA6417, recleared direct BOREE for the BOREE3A arrival, runway 34L, maintain FL180" - **RXA6417:** "Recleared direct BOREE for the BOREE3A arrival, runway 34L, maintain FL180, RXA6417" + **BIK:** "RXA6417, recleared direct BOREE for the BOREE4A arrival, runway 34L, maintain FL180" + **RXA6417:** "Recleared direct BOREE for the BOREE4A arrival, runway 34L, maintain FL180, RXA6417" #### Adjacent Feeder Fixes Aircraft assigned the **same runway** inbound via **BOREE** and **MEPIL**, must be considered to be on the **same STAR** for sequencing purposes. That is, they must be at least **2 minutes** apart at their respective Feeder fixes. diff --git a/docs/enroute/Melbourne Centre/TBD.md b/docs/enroute/Melbourne Centre/TBD.md index d39ca3fb9..d26aef822 100644 --- a/docs/enroute/Melbourne Centre/TBD.md +++ b/docs/enroute/Melbourne Centre/TBD.md @@ -45,7 +45,7 @@ Must be considered to be on the **same STAR** for sequencing purposes. That is, Aircraft tracking via OJJAY and MARGO (ie *J251 WHA H84 MARGO*) from the North for Runway 23 shall be assigned: **RAYNA** STAR with the **OJJAY** transition **not** -**SALTY** STAR with the **MARGO** transition +**BUGSU** STAR with the **MARGO** transition vatSys will not necessarily select the correct STAR by default when entering the runway, so ensure the correct STAR is selected. diff --git a/docs/events/worldflight/Enroute/ybbnyssy.md b/docs/events/worldflight/Enroute/ybbnyssy.md index 8f5963fb8..f7c6238b2 100644 --- a/docs/events/worldflight/Enroute/ybbnyssy.md +++ b/docs/events/worldflight/Enroute/ybbnyssy.md @@ -30,8 +30,8 @@ ARL will be responsible for the ARL and MNN subsectors **only**. | Fix | Runway | STAR | | ---------- | --- | --- | -| BOREE | 16R | BOREE3P | -| BOREE | 34L | BOREE3A | +| BOREE | 16R | BOREE4P | +| BOREE | 34L | BOREE4A | | MEPIL | 16L | MEPIL3 | | MEPIL | 34R | MEPIL3 | diff --git a/docs/terminal/adelaide.md b/docs/terminal/adelaide.md index 9573bf267..d2e774adc 100644 --- a/docs/terminal/adelaide.md +++ b/docs/terminal/adelaide.md @@ -90,15 +90,15 @@ The times assume there is *Nil wind*. | Feeder Fix | 05Z | 05V/W/X | 23A/Z | 23V | | ---------- | --- | ------- | ----- | --- | -| ALEXI | 14 | 13 | - | - | +| INTOG | 14 | 13 | - | - | | DRINA | - | - | 14 | 13 | | KAKLU | 16 | 15 | 12^ | - | | KLAVA | 16 | 15 | 13 | 12 | | ERITH | - | - | 13 | 12 | | MARGO | 14 | 13 | 15 | 13 | -| RIKAB | 13 | 12^ | 17 | 15 | +| ATNAR | 13 | 12^ | 17 | 15 | -- **GULLY** - Threshold is **5 minutes** +- **VIRAT** - Threshold is **5 minutes** - **PADSI** - Threshold is **3.5 minutes** - Add **1 minute** for aircraft assigned a reduced speed, Except ^ - Subtract **1 minute** for MX or CSR @@ -113,7 +113,7 @@ The times assume there is *Nil wind*. This table assumes that aircraft will be assigned: -- The appropriate *Non-Jet STAR* (**ATPIP**, **ELROX**, **GULFS**, **PAMMY**, **RUSSL**, **SURGN**), or if none is available: +- The appropriate *Non-Jet STAR* (**ATPIP**, **ELROX**, **GULFS**, **PAMMY**, **BEVSO**, **SURGN**), or if none is available: - *No STAR* Thence track via a **5nm final** for the assigned runway. @@ -122,14 +122,14 @@ For Non-Jets tracking via the *full Jet STARs*, see [table above](#jets) | Feeder Fix | 05 | 12 | 23 | 30 | | ---------- | --- | --- | --- | --- | -| ALEXI | 12 | 14 | 12 | 11 | +| INTOG | 12 | 14 | 12 | 11 | | DRINA | 14 | 17 | 14 | 13 | | KAKLU | 16 | 15 | 13 | 13 | -| RUSSL | 17 | 15 | 14 | 13 | +| BEVSO | 17 | 15 | 14 | 13 | | KLAVA | 15 | 13 | 13 | 16 | | ERITH | - | - | - | - | | MARGO | 13 | 12 | 13 | 15 | -| RIKAB | 13 | 13 | 15 | 16 | +| ATNAR | 13 | 13 | 15 | 16 | | ELROX | 11 | 11 | 14 | 13 | - **5nm final** - Threshold is **2 minutes** @@ -220,7 +220,7 @@ VFR aircraft require a level readback. Aircraft departing YPED in to AD TCU Class C will be coordinated from **EDN ADC** at Taxi. !!! example - **EDN ADC** -> **AD TCU**: "Taxi, BLKT11 for YMES, via GULLY" + **EDN ADC** -> **AD TCU**: "Taxi, BLKT11 for YMES, via VIRAT" **AD TCU** -> **EDN ADC**: "BLKT11" When the aircraft is ready for takeoff, **EDN ADC** will give a "Next" call, where AD TCU will provide the cleared level. diff --git a/docs/terminal/sydney.md b/docs/terminal/sydney.md index c2255547b..3746d1c72 100644 --- a/docs/terminal/sydney.md +++ b/docs/terminal/sydney.md @@ -157,7 +157,7 @@ All aircraft should be assigned no lower than `A060` until clear of the active r Remember that you will not receive "Next" Coordination on aircraft assigned Standard Assignable Levels (ie `A050` for Jets, `A030` for Non-Jets), meaning an aircraft could depart at any time without prior warning and climb to `A050`. !!! example - For an aircraft inbound from the north on the BOREE3A arrival to runway 34R, assign no lower than `A080` until any adjacent aircraft are maintaing `A060`, then `A070` until the aircraft are laterally clear. The arrival should then be assigned `A060` until south of the field. + For an aircraft inbound from the north on the BOREE4A arrival to runway 34R, assign no lower than `A080` until any adjacent aircraft are maintaing `A060`, then `A070` until the aircraft are laterally clear. The arrival should then be assigned `A060` until south of the field. Be mindful of departures from YSBK which may also impact aircraft on downwind for RWY 16R at YSSY. Do not assign lower than `A040` until the aircraft is north/east of the BK CTR and clear of any departing traffic (who are assigned `A030` by default).