diff --git a/docs/aerodromes/classc/canberra.md b/docs/aerodromes/classc/canberra.md index 6d16d691f..20993dab7 100644 --- a/docs/aerodromes/classc/canberra.md +++ b/docs/aerodromes/classc/canberra.md @@ -191,3 +191,13 @@ When a TCU controller is online, aircraft shall be issued with a departure frequ | ------ | ---- | -------------------- | | 35 | AVBEG
DUBUS
HOWLY
NONUP
TANTA
WG VOR
West | 125.9 (CBW) | | 35 | IDROP
CULIN
East | 124.5 (CBE) | + +### MAESTRO + +When a departure is bound for YSSY and MAESTRO is in use, **CB SMC** shall advise **SFL** when the aircraft commences taxi. SFL will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +SFL may waive this requirement during periods of low traffic. + +!!! phraseology + **CB SMC** -> **SFL**: "QFA400, taxiing YSSY" + **SFL** -> **CB SMC**: "QFA400, landing time 45, 8 minutes delay" diff --git a/docs/aerodromes/classc/essendon.md b/docs/aerodromes/classc/essendon.md index 9184936bb..80deeac5c 100644 --- a/docs/aerodromes/classc/essendon.md +++ b/docs/aerodromes/classc/essendon.md @@ -219,3 +219,13 @@ EN ADC is responsible for separation with all YMML traffic, and must coordinate **EN ADC** -> **ML ADC**: "For Ident, OXG, published missed approach from the ILS 26" **ML ADC** -> **EN ADC**: "OXG, my restriction is QFA451 on a 10nm final RWY 34, your separation" **EN ADC** -> **ML ADC**: "My separation with QFA451, OXG" + +### MAESTRO + +When a departure is bound for YMML and MAESTRO is in use, **EN SMC** shall advise **MFL** when the aircraft commences taxi. MFL will activate the flight in MAESTRO and advise a landing time. + +MFL may waive this requirement during periods of low traffic. + +!!! phraseology + **EN SMC** -> **MFL**: "RXA6272, taxiing YMML" + **MFL** -> **EN SMC**: "RXA6272, landing time 22" diff --git a/docs/aerodromes/classc/goldcoast.md b/docs/aerodromes/classc/goldcoast.md index 92ae1ae20..dbfa4f681 100644 --- a/docs/aerodromes/classc/goldcoast.md +++ b/docs/aerodromes/classc/goldcoast.md @@ -243,3 +243,13 @@ When a TCU controller is online, aircraft shall be issued with a departure frequ ### Start Clearance A start clearance is required for aircraft planned to YBBN. Start clearance must be coordinated with BN TCU. + +### MAESTRO + +When a departure is bound for YBBN and MAESTRO is in use, **CG SMC** shall advise **BFL** when the aircraft commences taxi. BFL will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +BFL may waive this requirement during periods of low traffic. + +!!! phraseology + **CG SMC** -> **BFL**: "VOZ789, taxiing YBBN" + **BFL** -> **CG SMC**: "VOZ789, landing time 22, no delay" diff --git a/docs/aerodromes/classc/walton.md b/docs/aerodromes/classc/walton.md index 673e6017b..ba544f15b 100644 --- a/docs/aerodromes/classc/walton.md +++ b/docs/aerodromes/classc/walton.md @@ -205,3 +205,13 @@ The controller assuming responsibility of **WS ACD** shall give [heads-up](../.. - VFR departures - Aircraft with `ADES` YSSY, YSBK, YSCN, YSRI, or YSHW - Aircraft using a runway not on the ATIS + +### MAESTRO + +When a departure is bound for YSSY and MAESTRO is in use, **WS SMC** shall advise **SFL** when the aircraft commences taxi. SFL will activate the flight in MAESTRO and advise a landing time. + +SFL may waive this requirement during periods of low traffic. + +!!! phraseology + **WS SMC** -> **SFL**: "QFA401, taxiing YSSY" + **SFL** -> **WS SMC**: "QFA401, landing time 45" diff --git a/docs/aerodromes/classd/archerfield.md b/docs/aerodromes/classd/archerfield.md index e9be6bf3b..0e511dbe1 100644 --- a/docs/aerodromes/classd/archerfield.md +++ b/docs/aerodromes/classd/archerfield.md @@ -269,3 +269,13 @@ AF ADC must heads-up coordinate **all aircraft** transiting from one ADC control !!! phraseology **AF ADC S** -> **AF ADC N**: "via TAR, TQC for an overhead join" **AF ADC N** -> **AF ADC S**: "TQC, A015" + +### MAESTRO + +When a departure is bound for YBBN and MAESTRO is in use, **AF SMC** shall advise **BFL** when the aircraft commences taxi. BFL will activate the flight in MAESTRO and advise a landing time. + +BFL may waive this requirement during periods of low traffic. + +!!! phraseology + **AF SMC** -> **BFL**: "YPX, taxiing YBBN" + **BFL** -> **AF SMC**: "YPX, landing time 30" diff --git a/docs/aerodromes/classd/avalon.md b/docs/aerodromes/classd/avalon.md index 92d4c06a3..2ebc2fc64 100644 --- a/docs/aerodromes/classd/avalon.md +++ b/docs/aerodromes/classd/avalon.md @@ -53,3 +53,13 @@ When a TCU controller is online, aircraft shall be issued with a departure frequ #### Runway Change Any Runway change must be prior coordinated to the TCU controller responsible for **MAV**. + +### MAESTRO + +When a departure is bound for YMML and MAESTRO is in use, **AV ADC** shall advise **MFL** when the aircraft commences taxi. MFL will activate the flight in MAESTRO and advise a landing time. + +MFL may waive this requirement during periods of low traffic. + +!!! phraseology + **AV ADC** -> **MFL**: "JST405, taxiing YMML" + **MFL** -> **AV ADC**: "JST405, landing time 22" diff --git a/docs/aerodromes/classd/ballina.md b/docs/aerodromes/classd/ballina.md index 5c2ed765b..43b3304ac 100644 --- a/docs/aerodromes/classd/ballina.md +++ b/docs/aerodromes/classd/ballina.md @@ -52,6 +52,16 @@ The standard assignable level from BA ADC to BAA is: | -------- | ----- | | All | The lower of `A050` and `RFL` | +### MAESTRO + +When a departure is bound for YBBN and MAESTRO is in use, **BA ADC** shall advise **BFL** when the aircraft commences taxi. BFL will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +BFL may waive this requirement during periods of low traffic. + +!!! phraseology + **BA ADC** -> **BFL**: "QLK2035, taxiing YBBN" + **BFL** -> **BA ADC**: "QLK2035, landing time 22, 8 minutes delay" + ### Arrivals/Overfliers BAA will heads-up coordinate arrivals/overfliers from Class C to BA ADC prior to **5 mins** from the boundary. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to BA ADC, unless BA ADC nominates a restriction. diff --git a/docs/aerodromes/classd/bankstown.md b/docs/aerodromes/classd/bankstown.md index ba991fc23..04b2a8df2 100644 --- a/docs/aerodromes/classd/bankstown.md +++ b/docs/aerodromes/classd/bankstown.md @@ -302,3 +302,13 @@ BK ADC must coordinate **all helicopter traffic** via CSTH. Coordination must ta !!! phraseology **BK ADC N** -> **BK ADC C**: "Choppers South Inbound/Outbound" **BK ADC C** -> **BK ADC N**: "Roger, Traffic is a Cherokee late downwind" + +### MAESTRO + +When a departure is bound for YSSY and MAESTRO is in use, **BK SMC** shall advise **SFL** when the aircraft commences taxi. SFL will activate the flight in MAESTRO and advise a landing time. + +SFL may waive this requirement during periods of low traffic. + +!!! phraseology + **BK SMC** -> **SFL**: "XKF, taxiing YSSY" + **SFL** -> **BK SMC**: "XKF, landing time 45" diff --git a/docs/aerodromes/classd/camden.md b/docs/aerodromes/classd/camden.md index 62c28a905..c4f9616c0 100644 --- a/docs/aerodromes/classd/camden.md +++ b/docs/aerodromes/classd/camden.md @@ -173,3 +173,13 @@ SY TCU will **NOT** clear the aircraft for the approach. ### IFR overflying YSCN SYC will advise CN ADC of observed IFR aircraft overflying CN CTR below `A025`. + +### MAESTRO + +When a departure is bound for YSSY and MAESTRO is in use, **CN SMC** shall advise **SFL** when the aircraft commences taxi. SFL will activate the flight in MAESTRO and advise a landing time. + +SFL may waive this requirement during periods of low traffic. + +!!! phraseology + **CN SMC** -> **SFL**: "YFX, taxiing YSSY" + **SFL** -> **CN SMC**: "YFX, landing time 45" diff --git a/docs/aerodromes/classd/jandakot.md b/docs/aerodromes/classd/jandakot.md index d10f9a6a4..ca5c51e48 100644 --- a/docs/aerodromes/classd/jandakot.md +++ b/docs/aerodromes/classd/jandakot.md @@ -157,3 +157,13 @@ JT ADC must heads-up coordinate **all aircraft** transiting from one ADC control !!! phraseology **JT ADC C** -> **JT ADC W**: "via FDL, TBN for an overfly" **JT ADC W** -> **JT ADC C**: "TBN, A015" + +### MAESTRO + +When a departure is bound for YPPH and MAESTRO is in use, **JT SMC** shall advise **PFL** when the aircraft commences taxi. PFL will activate the flight in MAESTRO and advise a landing time. + +PFL may waive this requirement during periods of low traffic. + +!!! phraseology + **JT SMC** -> **PFL**: "YDV, taxiing YPPH" + **PFL** -> **JT SMC**: "YDV, landing time 15" diff --git a/docs/aerodromes/classd/launceston.md b/docs/aerodromes/classd/launceston.md index 103dc2710..90874ddbe 100644 --- a/docs/aerodromes/classd/launceston.md +++ b/docs/aerodromes/classd/launceston.md @@ -68,6 +68,16 @@ LT ADC shall give [heads-up](../../controller-skills/coordination.md#airways-cle - VFR departures entering LTA CTA - Aircraft using a runway not on the ATIS +### MAESTRO + +When a departure is bound for YMML and MAESTRO is in use, **LT ADC** shall advise **MFL** when the aircraft commences taxi. MFL will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +MFL may waive this requirement during periods of low traffic. + +!!! phraseology + **LT ADC** -> **MFL**: "QFA601, taxiing YMML" + **MFL** -> **LT ADC**: "QFA601, landing time 30, 12 minutes delay" + ### Arrivals/Overfliers LTA will heads-up coordinate arrivals/overfliers from LTA CTA to LT ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to LT ADC, unless LT ADC nominates a restriction. diff --git a/docs/aerodromes/classd/moorabbin.md b/docs/aerodromes/classd/moorabbin.md index 378d5c16d..161f13cf8 100644 --- a/docs/aerodromes/classd/moorabbin.md +++ b/docs/aerodromes/classd/moorabbin.md @@ -198,3 +198,13 @@ MB ADC must heads-up coordinate **all aircraft** transiting from one ADC control !!! phraseology **MB ADC W** -> **MB ADC E**: "via CARR, EWX for an overfly" **MB ADC E** -> **MB ADC W**: "EWX, A015" + +### MAESTRO + +When a departure is bound for YMML and MAESTRO is in use, **MB SMC** shall advise **MFL** when the aircraft commences taxi. MFL will activate the flight in MAESTRO and advise a landing time. + +MFL may waive this requirement during periods of low traffic. + +!!! phraseology + **MB SMC** -> **MFL**: "YGC, taxiing YMML" + **MFL** -> **MB SMC**: "YGC, landing time 22" diff --git a/docs/aerodromes/procedural/albury.md b/docs/aerodromes/procedural/albury.md index b2ef8531e..3eb5f6012 100644 --- a/docs/aerodromes/procedural/albury.md +++ b/docs/aerodromes/procedural/albury.md @@ -69,3 +69,13 @@ BLA will heads-up coordinate all arrivals/overfliers to AY ADC **AY ADC** -> **BLA**: "RXA6783" The standard assignable level from BLA to AY ADC is `A080`, any other level must be prior coordinated. + +### MAESTRO + +When a departure is bound for YSSY or YMML and MAESTRO is in use, **AY SMC** shall advise the relevant flow controller when the aircraft commences taxi. The flow controller will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +The flow controller may waive this requirement during periods of low traffic. + +!!! phraseology + **AY SMC** -> **SFL**: "QFA414, taxiing YSSY" + **SFL** -> **AY SMC**: "QFA414, landing time 45, 8 minutes delay" diff --git a/docs/aerodromes/procedural/coffs.md b/docs/aerodromes/procedural/coffs.md index 46601a14c..3df98ec80 100644 --- a/docs/aerodromes/procedural/coffs.md +++ b/docs/aerodromes/procedural/coffs.md @@ -60,3 +60,13 @@ INL/MNN will heads-up coordinate all arrivals/overfliers to CFS ADC. **CFS ADC** -> **INL**: "RXA6416" The standard assignable level from INL/MNN to CFS ADC is `A080`, any other level must be prior coordinated. + +### MAESTRO + +When a departure is bound for YBBN and MAESTRO is in use, **CFS ADC** shall advise **BFL** when the aircraft commences taxi. BFL will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +BFL may waive this requirement during periods of low traffic. + +!!! phraseology + **CFS ADC** -> **BFL**: "JST441, taxiing YBBN" + **BFL** -> **CFS ADC**: "JST441, landing time 22, no delay" diff --git a/docs/aerodromes/procedural/sunshinecoast.md b/docs/aerodromes/procedural/sunshinecoast.md index 713ab4ad4..72760d28b 100644 --- a/docs/aerodromes/procedural/sunshinecoast.md +++ b/docs/aerodromes/procedural/sunshinecoast.md @@ -83,3 +83,13 @@ BN TCU Class G shares a tiny border with SU ADC, however there are no SIDs, STAR ![BN TCU / SU ADC Border](../../terminal/img/subntcu.png){ width="700" }
BN TCU / SU ADC Border
+ +### MAESTRO + +When a departure is bound for YBBN and MAESTRO is in use, **SU SMC** shall advise **BFL** when the aircraft commences taxi. BFL will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +BFL may waive this requirement during periods of low traffic. + +!!! phraseology + **SU SMC** -> **BFL**: "QJE1756, taxiing YBBN" + **BFL** -> **SU SMC**: "QJE1756, landing time 30, no delay" diff --git a/docs/aerodromes/procedural/tamworth.md b/docs/aerodromes/procedural/tamworth.md index b9014b802..0844b7a98 100644 --- a/docs/aerodromes/procedural/tamworth.md +++ b/docs/aerodromes/procedural/tamworth.md @@ -219,3 +219,13 @@ TW ADC must heads-up coordinate **all aircraft** transiting from one ADC control !!! phraseology **TW ADC S** -> **TW ADC**: "via GWT, SPP for an overfly" **TW ADC** -> **TW ADC S**: "SPP, `A035`" + +### MAESTRO + +When a departure is bound for YSSY and MAESTRO is in use, **TW SMC** shall advise **SFL** when the aircraft commences taxi. SFL will activate the flight in MAESTRO and advise of any delay that can be absorbed on the ground before departure. + +SFL may waive this requirement during periods of low traffic. + +!!! phraseology + **TW SMC** -> **SFL**: "QFA728, taxiing YSSY" + **SFL** -> **TW SMC**: "QFA728, landing time 45, 12 minutes delay" diff --git a/docs/client/img/maestro-enr1.png b/docs/client/img/maestro-enr1.png new file mode 100644 index 000000000..ad046df92 Binary files /dev/null and b/docs/client/img/maestro-enr1.png differ diff --git a/docs/client/img/maestro-enr2.png b/docs/client/img/maestro-enr2.png new file mode 100644 index 000000000..2c44cae2d Binary files /dev/null and b/docs/client/img/maestro-enr2.png differ diff --git a/docs/client/img/maestro-tma1.png b/docs/client/img/maestro-tma1.png new file mode 100644 index 000000000..34914c38f Binary files /dev/null and b/docs/client/img/maestro-tma1.png differ diff --git a/docs/client/img/maestro-tma2.png b/docs/client/img/maestro-tma2.png new file mode 100644 index 000000000..3f3b15242 Binary files /dev/null and b/docs/client/img/maestro-tma2.png differ diff --git a/docs/client/maestro.md b/docs/client/maestro.md index f128fba68..66bc89271 100644 --- a/docs/client/maestro.md +++ b/docs/client/maestro.md @@ -13,9 +13,10 @@ When the number of arriving aircraft increases, a flow controller is required to MAESTRO is generally not used by TWR controllers, however it allows them to have situational awareness of the flow of inbound aircraft. -The MAESTRO plugin can be accessed from the vatSys menu bar under TFMS. By default, it operates in **offline** mode. Use the `SETUP` button to [connect](#synchronisation) to the server, which allows all connected controllers to share sequence information. +The MAESTRO plugin can be accessed from the vatSys menu bar under TFMS. By default, it operates in **offline** mode. Click the Connection Status button (top-left of the Maestro window) to [connect](#synchronisation) to the server, which allows all connected controllers to share sequence information. ## Installation + The vMaestro plugin should be [downloaded](https://github.com/YuKitsune/vMaestro/releases) and placed in your vatSys Plugins folder. ## Abbreviations @@ -27,62 +28,109 @@ The vMaestro plugin should be [downloaded](https://github.com/YuKitsune/vMaestro | `STA` | **Scheduled** time of arrival at the runway (landing time) calculated by Maestro. | | `ETA_FF` | Estimated time of arrival at the **feeder fix**. | | `STA_FF` | **Scheduled** time of arrival at the feeder fix calculated by Maestro. | +| `TTG` | Time-to-Go from feeder fix to runway threshold. | ## How it works Maestro tracks flights within 2 hours of the feeder fix or when an FDR is activated for flights from departure airports. vatSys provides updated position information every 30 seconds, and Maestro recalculates estimates and sequence position based on the flight's state. -Flights from departure airports are placed in the Pending list and must be manually inserted by the flow controller. These flights can be inserted prior to departure to absorb delay on the ground. +Flights from departure airports are placed in the Pending list and are automatically activated on departure. The flow controller may also insert them prior to departure so that any required delay can be absorbed on the ground. -Maestro calculates landing times (`STA`) based on estimates (`ETA`) and applies delays when the time between consecutive flights is less than the acceptance rate. The `STA_FF` is calculated by subtracting the arrival `ETI` from the `STA`. +Maestro calculates landing times (`STA`) based on estimates (`ETA`) and applies delays when the time between consecutive flights is less than the acceptance rate. The `STA_FF` is derived from the `ETA_FF` plus the enroute portion of the required delay (the delay to be absorbed before the feeder fix). ### The Timeline Each timeline displays flights at their `STA` (runway view) or `STA_FF` (feeder view). +Generally, enroute views will be feeder views, and TMA/flow views will be runway views. + Each tick on the timeline corresponds to one minute. Flight labels are mirrored on either side of the timeline, and contain (from innermost to outermost): -1. `STA` (in feeder view) or `STA_FF` (in runway view) +1. `STA` (for feeder views) or `STA_FF` (for runway views) 2. Assigned runway 3. Callsign 4. Approach Type (if applicable) 5. `#` if zero delay has been assigned 6. `%` if manual delay (other than zero) has been assigned -7. `+` if the flight must cross the feeder-fix at published speed +7. `+` if the flight must cross the feeder fix at profile speed 8. `*` if the FDR is not coupled to a radar track -9. Total delay required (based on the initial `ETA`) +9. Delay required (based on the initial `ETA`) 10. Delay remaining (based on the current `ETA`) -The total delay required remains unchanged as the flight absorbs delay. The remaining delay progressively reduces as delay is absorbed. When the remaining delay reads `00`, all required delay has been absorbed. - -!!! note - After a flight has passed the feeder fix, the `ETA` is calculated based on the `ATO` of the feeder fix, thus, the remaining delay figure will not change once the flight enters the TMA. +Each airport may define additional custom label layouts for specific positions; refer to individual SOPs for details. ![Maestro Window](./img/maestro.png) +#### Delay Figures + +In enroute views, only the enroute portion of the required and remaining delay is displayed. +In runway views, the total delay required and remaining is displayed. + +The total delay required remains unchanged as the flight absorbs delay. The remaining delay progressively reduces as delay is absorbed. When the remaining delay reads `0`, all required delay has been absorbed. + +##### Delay Allocation + +Required delay is split between an **enroute** component and a **TMA** component. The TMA component varies between 0 and 5 minutes depending on the feeder fix and runway. For example, feeder fixes that result in straight-in approaches leave less room for vectoring, so less delay can be absorbed in the TMA. + +Enroute views have been configured to show only the enroute component. +Runway views are configured to show the **total** delay (ENR + TMA delay). + +In the example below, an aircraft has 15 minutes of total required delay: 10 minutes allocated to enroute, and 5 minutes to the TMA. +The enroute label shows **10**, and the TMA label shows **15**. + +
+
+ Enroute view +
Enroute view
+
+
+ TMA view +
TMA view
+
+
+ +By the time the aircraft reaches the feeder fix, 9 of the 10 enroute minutes have been absorbed. +The enroute remaining delay drops to **1**, while the TMA remaining delay is now **6** (the 1 minute not absorbed enroute, plus the original 5 minutes of TMA delay). + +
+
+ Enroute view after feeder fix +
Enroute view
+
+
+ TMA view after feeder fix +
TMA view
+
+
+ +!!! note + Once an aircraft passes the feeder fix, its `ETA` stops updating, so delay figures on the label will not change until the next processing cycle after feeder fix passage. + ### Flight States Maestro uses various states that affect how flights are processed. Each state is indicated by a specific color on the flight label: -**Unstable**: All new flights start in this state and remain unstable for at least 5 minutes. After each update, unstable flights are re-positioned in the sequence based on their calculated `ETA`, and their `STA_FF` and `STA` times are re-calculated. +**Unstable**: All new flights start in this state and remain unstable for at least 5 minutes. On each update, the full processing cycle runs: estimates are recalculated, the flight is repositioned in the sequence, and scheduling assigns a runway and `STA`. The runway and approach type may change if an earlier `STA` is available on an alternative runway. -**Stable**: Flights become stable 25 minutes prior to the `ETA_FF`. Stable flights keep their position in the sequence unless a flight appears, disappears, or moves before it. Stable flights can be displaced by a preceding flight being moved by controller action or a new flight entering the sequence with an earlier `ETA_FF`. +**Stable**: Flights become Stable 25 minutes prior to the `ETA_FF`. Stable flights keep their position in the sequence unless displaced by controller action on a preceding flight, or a new flight entering with an earlier `ETA`. There is no alert when required delays change; controllers should regularly review delay figures. -**Super Stable**: Flights become super stable at the original `ETA_FF`. Super stable flights are fixed in position. All new flights are positioned after super stable flights. Super stable flights can only be moved manually by controller interaction. +**Super Stable**: Flights become SuperStable at the original `ETA_FF` (the `ETA_FF` at the time they became Stable). SuperStable flights are fixed in position. All new flights are positioned after them. Displacement only occurs through controller action on this flight or a preceding flight. -**Frozen**: Flights become frozen within 15 minutes of the `STA`. No changes can be made to frozen flights. They remain locked in their scheduled position and time. +**Frozen**: Flights become Frozen within 15 minutes of the `STA`. Frozen flights cannot be displaced at all, even by controller actions. -**Landed**: Flights become landed at the `STA`. No changes can be made to landed flights. The last 5 landed flights remain in the system in case of an overshoot, after which they are automatically removed. +**Landed**: Flights become Landed at the `STA`. The last 5 landed flights remain visible in case of an overshoot, after which they are automatically removed. ### Delaying Action The delay figure on the flight label is color coded to indicate the suggested delaying action: -- **Expedite**: The aircraft needs to make up the time shown (a minus sign will be in front of the delay number) -- **No delay**: No delaying action required. The aircraft can maintain their profile speed. -- **Speed reduction**: A short delay is required for the flight to meet their `STA`. -- **Holding recommended**: Extended delay is required. +- **Expedite**: The aircraft needs to speed up, and make up the time shown (a minus sign will be in front of the delay number) +- **No delay**: No delaying action required. +- **Resume**: Very small delay remaining; aircraft will absorb it by resuming track (e.g., completing a turn out of holding). +- **Speed reduction**: Delay can be absorbed linearly using speed control or vectoring. +- **Path Stretching**: Delay needs to be absorbed in the TMA. +- **Holding**: Extended delay is required. ## Interactions @@ -159,6 +207,14 @@ Ensure the `ETA_FF` is accurate at least 10 minutes prior to the feeder fix. If Remove any PETOs (Pilot Estimated Time Over) that may affect the accuracy of the system estimates. +!!! note + The Hold Plugin will set a PETO on the holding point, and the waypoint immediately after it. Do not clear these PETOs. + When MAESTRO is used in conjunction with the Hold Plugin, the `ETA_FF` will be calculated based on the hold exit time. + Verify the ETA_FF is accurate upon cancelling a hold, and re-routing the aircraft past the holding point. + +!!! tip + If the ETA_FF is inaccurate, check the TAS in the flight plan is accurate. + ### Re-routing When re-routing a flight via a new feeder fix, use the Recompute function (right-click the flight, select Recompute) after the re-route has been processed. This will recalculate the flight's feeder fix, estimates, and position in the sequence. @@ -238,7 +294,7 @@ Monitor the sequence for any anomalies, including: ### Sequence Adjustments -Adjust the sequence as required using the available functions (Move Flight, Change Runway, Manual Delay, etc.). +Adjust the sequence as required using the available functions (Move Flight, Change Runway, Manual Delay, etc.) to minimise delay. Before making large adjustments to the sequence: @@ -250,13 +306,24 @@ This alerts controllers that delay figures may be temporarily inaccurate and pre ### Pending Flights -Regularly review the Pending list (click `DEPS`) and insert flights from departure airports at appropriate times. +Flights from designated departure airports (i.e. those within approximately 30 to 45 minutes flight time that will track via a feeder fix) appear in the Pending list and are inserted using the `DEPS` button. +Maestro will automatically calculate a sequence position and any required delay based on the selected Take-Off time. -Coordinate with relevant units regarding pending flights, and advise them of the expected delay. +Periodically review the Pending list and insert flights when notified of their intention to depart. +Coordinate with relevant units and advise them of the expected delay and landing time. !!! tip - Maestro will calculate delays for pending flights on the ground. - Advise pilots of the expected delay prior to departure to allow them to absorb the delay on the ground rather than in the air. + By activating flights early, Maestro can calculate delays for flights still on the ground. + Advise pilots of the expected delay and landing time prior to departure to allow them to absorb the delay on the ground rather than in the air. + The remaining delay does not update until they depart and are correlated to a radar track. + +### Arrivals from within the TMA + +Aircraft departing from aerodromes within the TMA that will **not** track via a feeder fix cannot be automatically sequenced by Maestro. +These flights must be inserted directly onto the ladder using the `Insert Flight` function (right-click a flight or the ladder, select `Insert Flight`). + +!!! warning "Important" + When inserting a TMA departure using `Insert Flight`, the flight is placed at the time you select. Maestro will not calculate a sequence position or delay. ### Slots @@ -284,11 +351,13 @@ Before making changes to the TMA configuration: When scheduling a future configuration change, ensure the transition time allows sufficient buffer for aircraft in the sequence to land under the current configuration. +If only the acceptance rate needs to change, use the Change Landing Rates function rather than a full configuration change. Configuration changes recompute the entire sequence from the transition point, which may cause unnecessary disruption. + ## Synchronisation When connected to the Maestro server, the sequence is synchronised between all connected controllers. This allows multiple controllers to view and interact with the same sequence in real-time. -Connection to the Maestro server is established using the `SETUP` button in the Configuration Zone. +Connection to the Maestro server is established by clicking the Connection Status button (top-left of the Maestro window) to open the connection settings. ### Permissions @@ -323,8 +392,8 @@ The Online Status Indicator in the Configuration Zone displays the current conne | ------ | ------- | | `OFFLINE` | Not connected to the Maestro server. All processing is local, and all functions are available. | | `READY` | Connected to the Maestro server but not yet connected to VATSIM. No data is synchronised. | -| `FMP` | Connected as Flow. Your instance processes the sequence and distributes it to other controllers. | -| `APP` | Connected as Approach. Some functions are restricted (see [Permissions](#permissions)). | -| `ENR` | Connected as Enroute. Some functions are restricted (see [Permissions](#permissions)). | -| `ENR/FMP` or `APP/FMP` | Connected as Enroute or Approach with Flow authority. No dedicated Flow controller is online. All functions are available. | +| `FLOW` | Connected as Flow. Your instance processes the sequence and distributes it to other controllers. | +| `APP` | Connected as Approach. A Flow controller is online. Some functions are restricted (see [Permissions](#permissions)). | +| `ENR` | Connected as Enroute. A Flow controller is online. Some functions are restricted (see [Permissions](#permissions)). | +| `ENR/FLOW` or `APP/FLOW` | Connected as Enroute or Approach with Flow authority. No dedicated Flow controller is online. All functions are available. | | `OBS` | Connected as Observer. The sequence is read-only. | diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md index 95cbc8a84..226763dc2 100644 --- a/docs/terminal/brisbane.md +++ b/docs/terminal/brisbane.md @@ -393,6 +393,39 @@ The following calculator will generate a landing time from a feeder fix ETA, or === "Feeder Fix Time"
+### MAESTRO + +#### Feeder Fix selection + +Arrivals via `BLAKA`, `GOMOL`, `TEBOT`, and `UGTUG` are configured to allocate arrivals to 19L or 01R. +Arrivals via `ENLIP`, `WOODY`, `MORBI`, and `SMOKA` are allocated to 19R or 01L. + +Coordinate with BFL when an arrival is unable to accept their allocated runway. + +#### Delay Strategy + +Enroute delay is prioritised over TMA delay. Arrivals should absorb as much of the required delay as possible before the feeder fix. +MAESTRO may allocate 1 - 2 minutes of delay to the TMA in order to avoid holding. + +#### TMA Configuration + +| Mode | Runways | Rate | Dependency Rate | +|------|---------|:----:|:---------------:| +| 19 | 19L, 19R | 25/hr (144s) | - | +| 01 | 01L, 01R | 25/hr (144s) | - | +| SODPROPS | 19R | 12/hr (300s) | - | + +#### Views + +| View | Window | Reference | Ladders | +|------|:------:|:---------:|---------| +| INL | 30 min | `STA_FF` | BLAKA, GOMOL | +| DOS | 30 min | `STA_FF` | ENLIP, WOODY | +| BUR | 30 min | `STA_FF` | MORBI, SMOKA | +| SDY | 30 min | `STA_FF` | TEBOT, UGTUG | +| ALL | 30 min | `STA_FF` | BLAKA/ENLIP/GOMOL/MORBI, SMOKA/TEBOT/UGTUG/WOODY | +| RWY | 45 min | `STA` | 01L/19R, 01R/19L | + ## Coordination ### Enroute #### Departures diff --git a/docs/terminal/melbourne.md b/docs/terminal/melbourne.md index d2fb95a46..44c152108 100644 --- a/docs/terminal/melbourne.md +++ b/docs/terminal/melbourne.md @@ -311,6 +311,37 @@ The following calculator will generate a landing time from a feeder fix ETA, or === "Feeder Fix Time"
+### MAESTRO + +#### Delay Strategy + +Enroute delay is prioritised over TMA delay. Arrivals should absorb as much of the required delay as possible before the feeder fix. +MAESTRO may allocate 1 - 2 minutes of delay to the TMA in order to avoid holding. + +#### TMA Configuration + +| Mode | Runways | Rate | Dependency Rate | +|------|---------|:----:|:---------------:| +| 34 | 34 | 25/hr (144s) | - | +| 27 | 27 | 25/hr (144s) | - | +| 16 | 16 | 25/hr (144s) | - | +| 09 | 09 | 25/hr (144s) | - | +| 34/27 | 34, 27 | 25/hr (144s) | 60s | +| 34/09 | 34, 09 | 25/hr (144s) | 60s | +| 16/27 | 16, 27 | 25/hr (144s) | 90s | +| 16/09 | 16, 09 | 25/hr (144s) | 90s | + +Melbourne has no feeder fix preferences configured; Maestro assigns each flight to the runway producing the earliest landing time. + +#### Views + +| View | Window | Reference | Ladders | +|------|:------:|:---------:|---------| +| BLA/ELW | 30 min | `STA_FF` | BOOIN, BOYSE | +| MUN/YWE | 30 min | `STA_FF` | ARBEY, ALAXO | +| HUO/WON | 30 min | `STA_FF` | RAZZI, LATTA/EKKAS/MENOG | +| ALL | 30 min | `STA_FF` | ARBEY/ALAXO/LATTA/MENOG, BOOIN/BOYSE/RAZZI/EKKAS | +| RWY | 45 min | `STA` | 16/34, 09/27 | ## Coordination ### Enroute diff --git a/docs/terminal/perth.md b/docs/terminal/perth.md index 117f70381..85c6cba85 100644 --- a/docs/terminal/perth.md +++ b/docs/terminal/perth.md @@ -211,6 +211,35 @@ The following calculator will generate a landing time from a feeder fix ETA, or === "Feeder Fix Time"
+### MAESTRO + +#### Delay Strategy + +Enroute delay is prioritised over TMA delay. Arrivals should absorb as much of the required delay as possible before the feeder fix. +MAESTRO may allocate 1 - 2 minutes of delay to the TMA in order to avoid holding. + +#### TMA Configuration + +| Mode | Runways | Rate | Dependency Rate | +|------|---------|:----:|:---------------:| +| 21/24 | 21, 24 | 24/hr (150s) | 30s | +| 21 | 21 | 25/hr (144s) | - | +| 24 | 24 | 25/hr (144s) | - | +| 03 | 03 | 25/hr (144s) | - | +| 06 | 06 | 25/hr (144s) | - | + +Perth has no feeder fix preferences configured; Maestro assigns each flight to the runway producing the earliest landing time. + +#### Views + +| View | Window | Reference | Ladders | +|------|:------:|:---------:|---------| +| PIY | 30 min | `STA_FF` | JULIM/SAPKO, KABLI/DAYLR/LAVEX | +| LEA | 30 min | `STA_FF` | KAGMI | +| JAR | 30 min | `STA_FF` | OLMAM, SOLUS | +| ALL/HYD | 30 min | `STA_FF` | JULIM/SAPKO/KAGMI/SOLUS, KABLI/DAYLR/LAVEX/OLMAM | +| RWY | 45 min | `STA` | 03/21, 06/24 | + ## Coordination ### Enroute #### Departures diff --git a/docs/terminal/sydney.md b/docs/terminal/sydney.md index f95954a25..a9cfabb6f 100644 --- a/docs/terminal/sydney.md +++ b/docs/terminal/sydney.md @@ -684,6 +684,52 @@ The following calculator will generate a landing time from a feeder fix ETA, or === "Feeder Fix Time"
+### MAESTRO + +#### Feeder Fix selection + +`BOREE`, `YAKKA`, and `MARLN` feeder fixes have been configured to allocate arrivals to `16L` or `34R` during parallel operations. + +If an aircraft cannot accept this allocation, ENR may move them to `16R` or `34L` without coordinating with SFL. +This should be done at least 30 mins prior to `ETA_FF` to avoid changing the stable sequence. + +#### Delay Strategy + +Enroute delay is prioritised over TMA delay. +Arrivals should absorb as much of the required delay as possible before the feeder fix. +MAESTRO may allocate 1 - 2 minutes of delay to the TMA in order to avoid holding. + +Delay can be absorbed within the TMA by extending the downwind legs of the approach. + +#### TMA Configuration + +| Mode | Runways | Rate | Dependency Rate | +|------|---------|:----:|:---------------:| +| 34IVA | 34L, 34R | 24/hr (150s) | - | +| 34I | 34L, 34R | 20/hr (180s) | 60s | +| 16IVA | 16R, 16L | 24/hr (150s) | - | +| 16I | 16R, 16L | 20/hr (180s) | 60s | +| 07I | 07 | 25/hr (144s) | - | +| 25I | 25 | 25/hr (144s) | - | +| SODPROPS | 34L | 24/hr (150s) | - | + +#### Views + +| View | Window | Reference | Ladders | +|------|:------:|:---------:|---------| +| GUN/BIK | 30 min | `STA_FF` | ENLAD, AKMIR | +| ARL | 30 min | `STA_FF` | BOREE, YAKKA | +| OCN | 30 min | `STA_FF` | MARLN | +| ARL/OCN | 30 min | `STA_FF` | BOREE/YAKKA, MARLN | +| ALL | 30 min | `STA_FF` | ENLAD/AKMIR, BOREE/YAKKA/MARLN | +| RWY | 45 min | `STA` | 34L/16R/07, 34R/16L/25 | +| FLO_RWY | 45 min | `STA` | 16R/34L, 16L/34R, 07, 25 | + +**FLO_RWY** uses a custom label layout displaying: +- callsign and wake category coloured by feeder fix (**ENLAD / AKMIR**, **BOREE / YAKKA**, **MARLN**) +- total required delay coloured by state +- total remaining delay, coloured by state + ## Coordination ### Enroute #### Departures