From 5450a8d6f6057b9918ca9f02a352609dfa503f58 Mon Sep 17 00:00:00 2001 From: Charlie Date: Tue, 10 Dec 2024 18:27:04 +1000 Subject: [PATCH 1/8] inital addition of helicopter ops to the sops private fork --- docs/aerodromes/classc/Brisbane.md | 68 ++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index 5b308dc3b..a70590a99 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -29,6 +29,74 @@ There are three SMC positions at Brisbane which are responsible for various part
YBBN Maneuvering Area Responsibility
+## Helicopter Operations +Brisbane has one helipad located within the general aviation apron, most rescue helicopters are based within the airline maintenance hangars and will depart from the **H2 taxiway** to save time when operating. + +#### Waypoints +VFR and IFR helicopters are normally processed via two visual waypoints north and south of the field, when in VMC conditions. IFR helicopters in IMC conditions may conform to fixed wing ops and be processed via the BN (RADAR) SID from an appropriate runway, unless a visual departure is acceptable. These waypoints are used for **departures** and **arrivals**, depending on weather and traffic conditions. + + +| Direction | Waypoint | Name | +| ------------------ | -------------- | ---------------- | +| North | BLHS | Bald Hills | +| South | MBHM | Manly Boat Harbour | +| East | MBHM | Manly Boat Harbour | +| West | BLHS | Bald Hills | + +#### Departures + +Refer to [Maneuvering Area Responsibility](#maneuvering-area-responsibility) to determine which SMC or ADC position (when non-standard positions are online) is responsible for managing helicopter arrivals and departures. + +!!! example + **RSCU533:** "Brisbane Delivery, helicopter RSCU533, medivac for YXHE, request clearance" + **BN ACD:** "RSCU533, Brisbane Delivery, cleared to YXHE via BLHS, climb 2500, squawk 1256, departure frequency 124.7" + **RSCU533:** "Cleared to YXHE via BLHS, climb 2500, squawk 1256, departures 124.7, RSCU533" + +Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance BN ADC. Helicopters landing on other surfaces outside the maneuvering areas should be instructed to *"report on the ground"* so the controllers knows when they are no longer active in their airspace. + +!!! example + **RSCU533:** "Brisbane Tower, helicopter RSCU533, H2 ready" + **BN ADC:** "RSCU533, Brisbane Tower, H2 cleared for takeoff" + **RSCU533:** "H2 cleared for takeoff, RSCU533" + + **BN ADC:** "RSCU533, contact departures" + **RSCU533:** "Departures, RSCU533" + +#### Arrivals + +IFR helicopters operating within in IMC conditions may conform to fixed wing ops and be processed via an instrument approach for a appropriate duty runway. Standard fixed wing phraseology shall be used during these conditions. + +!!! example + **RSCU533:** "Brisbane Tower, helicopter RSCU533" + **BN ADC:** "RSCU533, Brisbane Tower, cleared visual approach H2" + **RSCU533:** "Cleared visual approach H2, RSCU533" + +During times of peak fixed wing traffic, instruct helicopters to orbit in present position or overhead the VFR waypoint until advised, and maintain own separation on approach to the helipad. + +!!! example + **BN ADC:** "RSCU533, orbit overhead Bald Hills until advised, traffic is a Fokker 70 on 4nm final 01L, report in sight" + **RSCU533:** "Orbit overhead Bald Hills, traffic in sight, RSCU533" + + **BN ADC:** "RSCU533, pass behind that aircraft, maintain own separation, caution wake turbulence, cleared visual approach H2" + **RSCU533:** "Pass behind the Fokker 70, maintain own separation, cleared visual approach H2, RSCU553" + +Traffic information must be issued to both aircraft. + +!!! example + **BN ADC:** "UTY7241 traffic is a rescue helicopter north of the field overhead Bald Hills, they will maintain own separation and pass behind you on approach, runway 01L, cleared to land" + **UTY7241:** "Copied rescue helicopter, runway 01L cleared to land, UTY7241" + +!!! example + **BN ADC:** "RSCU533, H2 cleared to land" + **RSCU533:** "Cleared to land H2, RSCU533" + +Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance BN ADC. Helicopters landing on other surfaces outside the maneuvering areas should be instructed to *"report on the ground"* so the controllers knows when they are no longer active in their airspace. + +!!! example + **RSCU533:** "RSCU533, on the ground H2" + **BN ADC:** "RSCU533, contact Ground 124.05" + **RSCU533:** "contact Ground 124.05, RSCU533" + ## Standard Taxi Routes Taxiway A is to be used in the same direction as the duty runway. Taxiway B is to be used in the opposite direction to the duty runway. From 29b19bf2cdb44ae1a0d5a61bee2644377a3a1574 Mon Sep 17 00:00:00 2001 From: llamavert Date: Tue, 10 Dec 2024 18:36:42 +1000 Subject: [PATCH 2/8] fix typo --- docs/aerodromes/classc/Brisbane.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index a70590a99..ddefae30a 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -64,7 +64,7 @@ Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, t #### Arrivals -IFR helicopters operating within in IMC conditions may conform to fixed wing ops and be processed via an instrument approach for a appropriate duty runway. Standard fixed wing phraseology shall be used during these conditions. +IFR helicopters operating within IMC conditions may conform to fixed wing ops and be processed via an instrument approach for a appropriate duty runway. Standard fixed wing phraseology shall be used during these conditions. !!! example **RSCU533:** "Brisbane Tower, helicopter RSCU533" From 5473ab39b269ba97a8d936b0d8ae990078ab5450 Mon Sep 17 00:00:00 2001 From: llamavert Date: Tue, 10 Dec 2024 20:11:40 +1000 Subject: [PATCH 3/8] updated to report airborne --- docs/aerodromes/classc/Brisbane.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index ddefae30a..bf619bae2 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -52,7 +52,7 @@ Refer to [Maneuvering Area Responsibility](#maneuvering-area-responsibility) to **BN ACD:** "RSCU533, Brisbane Delivery, cleared to YXHE via BLHS, climb 2500, squawk 1256, departure frequency 124.7" **RSCU533:** "Cleared to YXHE via BLHS, climb 2500, squawk 1256, departures 124.7, RSCU533" -Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance BN ADC. Helicopters landing on other surfaces outside the maneuvering areas should be instructed to *"report on the ground"* so the controllers knows when they are no longer active in their airspace. +Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance by BN ADC. Helicopters departing on other surfaces outside the maneuvering areas should be instructed to *"report airborne"* so the controllers knows when they are active in their airspace. !!! example **RSCU533:** "Brisbane Tower, helicopter RSCU533, H2 ready" @@ -90,7 +90,7 @@ Traffic information must be issued to both aircraft. **BN ADC:** "RSCU533, H2 cleared to land" **RSCU533:** "Cleared to land H2, RSCU533" -Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance BN ADC. Helicopters landing on other surfaces outside the maneuvering areas should be instructed to *"report on the ground"* so the controllers knows when they are no longer active in their airspace. +Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance by BN ADC. Helicopters landing on other surfaces outside the maneuvering areas should be instructed to *"report on the ground"* so the controllers knows when they are no longer active in their airspace. !!! example **RSCU533:** "RSCU533, on the ground H2" From 9b28c29a144b207573d53ae202a0b5174736b817 Mon Sep 17 00:00:00 2001 From: llamavert Date: Tue, 10 Dec 2024 22:02:13 +1000 Subject: [PATCH 4/8] updated rescue helicopter parking --- docs/aerodromes/classc/Brisbane.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index bf619bae2..a6afa6579 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -30,7 +30,7 @@ There are three SMC positions at Brisbane which are responsible for various part ## Helicopter Operations -Brisbane has one helipad located within the general aviation apron, most rescue helicopters are based within the airline maintenance hangars and will depart from the **H2 taxiway** to save time when operating. +Brisbane has one helipad located within the general aviation apron, most rescue helicopters are based within the general aviation maintenance area and will depart from the **H2 taxiway** to save time when operating. #### Waypoints VFR and IFR helicopters are normally processed via two visual waypoints north and south of the field, when in VMC conditions. IFR helicopters in IMC conditions may conform to fixed wing ops and be processed via the BN (RADAR) SID from an appropriate runway, unless a visual departure is acceptable. These waypoints are used for **departures** and **arrivals**, depending on weather and traffic conditions. From ef4300246fae8baca6e16e00c38f22d88ef86356 Mon Sep 17 00:00:00 2001 From: llamavert Date: Wed, 11 Dec 2024 10:17:27 +1000 Subject: [PATCH 5/8] init commit YSRI private branch --- docs/aerodromes/classc/Richmond.md | 74 +++++++++++++++++++++++++++++- 1 file changed, 72 insertions(+), 2 deletions(-) diff --git a/docs/aerodromes/classc/Richmond.md b/docs/aerodromes/classc/Richmond.md index b7972dfcc..5e9978faf 100644 --- a/docs/aerodromes/classc/Richmond.md +++ b/docs/aerodromes/classc/Richmond.md @@ -4,7 +4,77 @@ --8<-- "includes/abbreviations.md" -Reserved. +## Positions +| Name | Callsign | Frequency | Login ID | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| **Richmond ADC** | **Richmond Tower** | **135.500** | **RI_TWR** | +| **Richmond SMC** | **Richmond Ground** | **128.250** | **RI_GND** | +| Richmond ATIS | | 123.300 | YSRI_ATIS | + + + +## Airspace + +RIC ADC owns the Class C airspace **in the RIC CTR** within 10nm of the YSRI ARP from `SFC` to `A045`. This airspace is primarily used for military circuits and initial and pitch approaches, and airdrops. + +## Charts !!! note - Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new} \ No newline at end of file + Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP Page](https://ais-af.airforce.gov.au/australian-aip){target=new} + + +## YSRI Aerodrome + +### SID Selection +Aircraft planned via **ANKUB**, **KADOM** or **MUDGI** shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. + +### Runway Operations +Runways 10/28 is the primary runway at YSRI. + +## VFR Procedures +All aircraft outbound and inbound, or transiting the field maintain `A015`. +Aircraft transiting the RIC CTR track via the northbound or southbound VFR route. +Aircraft tracking northbound contact RIC ADC at Nepean Bridge (NPBR) for clearance. +Aircraft tracking southbound contact RIC ADC at Kurmond (KRMD) for clearance. + +!!! tip + You can find details of the transit route (including reporting points and altitudes) in the [`ERSA FAC YSRI`](https://www.airservicesaustralia.com/aip/current/ersa/FAC_YSRI_28NOV2024.pdf){target=new}. + +### Training Areas +Richmond has 3 training areas surrounding the field used for civil and military operations. + +| **Name** | **Identifier** | **Vertical Limits** | **Notes** | +|-------------------------|---------------|---------------------|-----------------------------------| +| Londonderry Training Area| LDD TA | `SFC - A015` | Contained within R470 | +| Northern Training Area| NTA TA | `SFC - A060` | Contained within R470 | +| Southern Training Area| STA TA | `SFC - A040` | Contained within R470 | + +## Miscellaneous +### Circuit Operations +YSRI circuit area is defined as within 6nm of the YSRI ARP. An aircraft operating in the circuit will be issued a clearance to the operate within the circuit area not above `A015`. + +### Circuit Direction +| Runway | Direction | +| ------ | ----------| +| 10 | Left | +| 28 | Left | + +### Start Approval +A start approval is required whenever parachute drops are conducted onto the Richmond Drop Zone. Additionally, ‘propellers/engines stopped’ reports are required. ATC shall notify these requirements by ATIS broadcast. + +### Inital and Pitch +The standard inital points are 5nm downwind of the active runway, dead side, left pitch/circuit. + +## Coordination +### RIC TCU + +'Next' coordination is required from RIC ADC to SY TCU for all aircraft. + +!!! example + **RIC ADC** -> **SY TCU**: "Next, TROJ57, runway 28" + **SY TCU** -> **RIC ADC**: "TROJ57, unrestricted" + **RIC ADC** -> **SY TCU**: "TROJ57" + +### Level Assignment +The Standard Assignable Level from **RIC ADC** to **SY TCU** is: +a) The Lower of `A050` or `RFL` for Aircraft assigned via Procedural or RNAV SID. \ No newline at end of file From 7455e07d2a62f47e63f0b65aabe38e421a83c25d Mon Sep 17 00:00:00 2001 From: llamavert Date: Wed, 11 Dec 2024 10:22:31 +1000 Subject: [PATCH 6/8] fix typo --- docs/aerodromes/classc/Richmond.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/aerodromes/classc/Richmond.md b/docs/aerodromes/classc/Richmond.md index 5e9978faf..cb8387592 100644 --- a/docs/aerodromes/classc/Richmond.md +++ b/docs/aerodromes/classc/Richmond.md @@ -16,7 +16,7 @@ ## Airspace -RIC ADC owns the Class C airspace **in the RIC CTR** within 10nm of the YSRI ARP from `SFC` to `A045`. This airspace is primarily used for military circuits and initial and pitch approaches, and airdrops. +RIC ADC owns the Class C airspace **in the RIC CTR** within 10nm of the YSRI ARP from `SFC` to `A045`. This airspace is primarily used for military circuits, initial and pitch approaches and airdrops. ## Charts !!! note From b79a8154a9bcabb99fd12ae7f9c5e7ccae1cd5d8 Mon Sep 17 00:00:00 2001 From: llamavert Date: Mon, 16 Dec 2024 12:10:22 +1000 Subject: [PATCH 7/8] remove Brisbane.md from YSRI --- docs/aerodromes/classc/Brisbane.md | 68 ------------------------------ docs/aerodromes/classc/Richmond.md | 6 +-- 2 files changed, 3 insertions(+), 71 deletions(-) diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index a6afa6579..5b308dc3b 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -29,74 +29,6 @@ There are three SMC positions at Brisbane which are responsible for various part
YBBN Maneuvering Area Responsibility
-## Helicopter Operations -Brisbane has one helipad located within the general aviation apron, most rescue helicopters are based within the general aviation maintenance area and will depart from the **H2 taxiway** to save time when operating. - -#### Waypoints -VFR and IFR helicopters are normally processed via two visual waypoints north and south of the field, when in VMC conditions. IFR helicopters in IMC conditions may conform to fixed wing ops and be processed via the BN (RADAR) SID from an appropriate runway, unless a visual departure is acceptable. These waypoints are used for **departures** and **arrivals**, depending on weather and traffic conditions. - - -| Direction | Waypoint | Name | -| ------------------ | -------------- | ---------------- | -| North | BLHS | Bald Hills | -| South | MBHM | Manly Boat Harbour | -| East | MBHM | Manly Boat Harbour | -| West | BLHS | Bald Hills | - -#### Departures - -Refer to [Maneuvering Area Responsibility](#maneuvering-area-responsibility) to determine which SMC or ADC position (when non-standard positions are online) is responsible for managing helicopter arrivals and departures. - -!!! example - **RSCU533:** "Brisbane Delivery, helicopter RSCU533, medivac for YXHE, request clearance" - **BN ACD:** "RSCU533, Brisbane Delivery, cleared to YXHE via BLHS, climb 2500, squawk 1256, departure frequency 124.7" - **RSCU533:** "Cleared to YXHE via BLHS, climb 2500, squawk 1256, departures 124.7, RSCU533" - -Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance by BN ADC. Helicopters departing on other surfaces outside the maneuvering areas should be instructed to *"report airborne"* so the controllers knows when they are active in their airspace. - -!!! example - **RSCU533:** "Brisbane Tower, helicopter RSCU533, H2 ready" - **BN ADC:** "RSCU533, Brisbane Tower, H2 cleared for takeoff" - **RSCU533:** "H2 cleared for takeoff, RSCU533" - - **BN ADC:** "RSCU533, contact departures" - **RSCU533:** "Departures, RSCU533" - -#### Arrivals - -IFR helicopters operating within IMC conditions may conform to fixed wing ops and be processed via an instrument approach for a appropriate duty runway. Standard fixed wing phraseology shall be used during these conditions. - -!!! example - **RSCU533:** "Brisbane Tower, helicopter RSCU533" - **BN ADC:** "RSCU533, Brisbane Tower, cleared visual approach H2" - **RSCU533:** "Cleared visual approach H2, RSCU533" - -During times of peak fixed wing traffic, instruct helicopters to orbit in present position or overhead the VFR waypoint until advised, and maintain own separation on approach to the helipad. - -!!! example - **BN ADC:** "RSCU533, orbit overhead Bald Hills until advised, traffic is a Fokker 70 on 4nm final 01L, report in sight" - **RSCU533:** "Orbit overhead Bald Hills, traffic in sight, RSCU533" - - **BN ADC:** "RSCU533, pass behind that aircraft, maintain own separation, caution wake turbulence, cleared visual approach H2" - **RSCU533:** "Pass behind the Fokker 70, maintain own separation, cleared visual approach H2, RSCU553" - -Traffic information must be issued to both aircraft. - -!!! example - **BN ADC:** "UTY7241 traffic is a rescue helicopter north of the field overhead Bald Hills, they will maintain own separation and pass behind you on approach, runway 01L, cleared to land" - **UTY7241:** "Copied rescue helicopter, runway 01L cleared to land, UTY7241" - -!!! example - **BN ADC:** "RSCU533, H2 cleared to land" - **RSCU533:** "Cleared to land H2, RSCU533" - -Taxiway H2 is inside the maneuvering area and therefore owned by **BN SMC-N**, treated like a runway requiring a takeoff and landing clearance by BN ADC. Helicopters landing on other surfaces outside the maneuvering areas should be instructed to *"report on the ground"* so the controllers knows when they are no longer active in their airspace. - -!!! example - **RSCU533:** "RSCU533, on the ground H2" - **BN ADC:** "RSCU533, contact Ground 124.05" - **RSCU533:** "contact Ground 124.05, RSCU533" - ## Standard Taxi Routes Taxiway A is to be used in the same direction as the duty runway. Taxiway B is to be used in the opposite direction to the duty runway. diff --git a/docs/aerodromes/classc/Richmond.md b/docs/aerodromes/classc/Richmond.md index cb8387592..7c7d1a58f 100644 --- a/docs/aerodromes/classc/Richmond.md +++ b/docs/aerodromes/classc/Richmond.md @@ -32,10 +32,10 @@ Aircraft planned via **ANKUB**, **KADOM** or **MUDGI** shall be assigned the **P Runways 10/28 is the primary runway at YSRI. ## VFR Procedures -All aircraft outbound and inbound, or transiting the field maintain `A015`. +All VFR aircraft outbound and inbound, or transiting the field maintain `A015`. Aircraft transiting the RIC CTR track via the northbound or southbound VFR route. -Aircraft tracking northbound contact RIC ADC at Nepean Bridge (NPBR) for clearance. -Aircraft tracking southbound contact RIC ADC at Kurmond (KRMD) for clearance. +Aircraft transiting northbound contact RIC ADC at Nepean Bridge (NPBR) for clearance. +Aircraft transiting southbound contact RIC ADC at Kurmond (KRMD) for clearance. !!! tip You can find details of the transit route (including reporting points and altitudes) in the [`ERSA FAC YSRI`](https://www.airservicesaustralia.com/aip/current/ersa/FAC_YSRI_28NOV2024.pdf){target=new}. From 7460d946b2c5092077d9e63a1338ea5d0e6b912f Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Tue, 17 Dec 2024 14:36:00 +1100 Subject: [PATCH 8/8] tweaks --- docs/aerodromes/classc/Richmond.md | 48 ++++++++++++++---------------- docs/terminal/sydney.md | 22 +++++++++++--- includes/abbreviations.md | 2 ++ 3 files changed, 43 insertions(+), 29 deletions(-) diff --git a/docs/aerodromes/classc/Richmond.md b/docs/aerodromes/classc/Richmond.md index 7c7d1a58f..f332e46a2 100644 --- a/docs/aerodromes/classc/Richmond.md +++ b/docs/aerodromes/classc/Richmond.md @@ -12,42 +12,43 @@ | **Richmond SMC** | **Richmond Ground** | **128.250** | **RI_GND** | | Richmond ATIS | | 123.300 | YSRI_ATIS | - - ## Airspace +RI ADC being online will activate the **R470** Restricted Area, which is reclassified as **Class C** when active. -RIC ADC owns the Class C airspace **in the RIC CTR** within 10nm of the YSRI ARP from `SFC` to `A045`. This airspace is primarily used for military circuits, initial and pitch approaches and airdrops. +Control authority of the **R470** Restricted Area when active is as follows: + +- RI ADC `SFC`-`A015` +- SY TCU (SDN) `A015`-`A045` ## Charts !!! note Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP Page](https://ais-af.airforce.gov.au/australian-aip){target=new} - -## YSRI Aerodrome - +## Aerodrome ### SID Selection -Aircraft planned via **ANKUB**, **KADOM** or **MUDGI** shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. +vatSys does not have SIDs built-in for YSRI. Aircraft planned via **ANKUB**, **KADOM** or **MUDGI** may be assigned the SID that terminates at the appropriate waypoint, as long as ATC is familiar with the chart, and the pilot is able. -### Runway Operations -Runways 10/28 is the primary runway at YSRI. +Aircraft who are not planned via these points, or who are negative RNAV, may be assigned a visual departure. ## VFR Procedures All VFR aircraft outbound and inbound, or transiting the field maintain `A015`. Aircraft transiting the RIC CTR track via the northbound or southbound VFR route. -Aircraft transiting northbound contact RIC ADC at Nepean Bridge (NPBR) for clearance. -Aircraft transiting southbound contact RIC ADC at Kurmond (KRMD) for clearance. +Aircraft transiting northbound contact RI ADC at NPBR for clearance. +Aircraft transiting southbound contact RI ADC at KRMD for clearance. !!! tip - You can find details of the transit route (including reporting points and altitudes) in the [`ERSA FAC YSRI`](https://www.airservicesaustralia.com/aip/current/ersa/FAC_YSRI_28NOV2024.pdf){target=new}. + You can find details of the transit route (including reporting points and altitudes) in the [ERSA FAC YSRI and VTC](https://www.airservicesaustralia.com/aip/aip.asp){target=new}. ### Training Areas -Richmond has 3 training areas surrounding the field used for civil and military operations. +There are three training areas located within **R470**, used for civil and military operations. | **Name** | **Identifier** | **Vertical Limits** | **Notes** | |-------------------------|---------------|---------------------|-----------------------------------| -| Londonderry Training Area| LDD TA | `SFC - A015` | Contained within R470 | -| Northern Training Area| NTA TA | `SFC - A060` | Contained within R470 | -| Southern Training Area| STA TA | `SFC - A040` | Contained within R470 | +| Londonderry Training Area | LDD TA | `SFC - A015` | Contained within R470 | +| Northern Training Area | NTA TA | `SFC - A060` | Contained within R470 | +| Southern Training Area | STA TA | `SFC - A040` | Contained within R470 | + +Refer to [YSRI FIHA AD2 SUPP](https://ais-af.airforce.gov.au/australian-aip){target=new} for charts and more info. ## Miscellaneous ### Circuit Operations @@ -66,15 +67,12 @@ A start approval is required whenever parachute drops are conducted onto the Ric The standard inital points are 5nm downwind of the active runway, dead side, left pitch/circuit. ## Coordination -### RIC TCU - -'Next' coordination is required from RIC ADC to SY TCU for all aircraft. +### SY TCU +'Next' coordination is required from RI ADC to SY TCU for all aircraft. !!! example - **RIC ADC** -> **SY TCU**: "Next, TROJ57, runway 28" - **SY TCU** -> **RIC ADC**: "TROJ57, unrestricted" - **RIC ADC** -> **SY TCU**: "TROJ57" + **RI ADC** -> **SDN**: "Next, TROJ57, runway 28" + **SDN** -> **RI ADC**: "TROJ57, unrestricted" + **RI ADC** -> **SDN**: "TROJ57" -### Level Assignment -The Standard Assignable Level from **RIC ADC** to **SY TCU** is: -a) The Lower of `A050` or `RFL` for Aircraft assigned via Procedural or RNAV SID. \ No newline at end of file +The Standard Assignable Level from **RI ADC** to **SY TCU** is the lower of `A050` or the `RFL`. \ No newline at end of file diff --git a/docs/terminal/sydney.md b/docs/terminal/sydney.md index 1d8330eb2..04a93309a 100644 --- a/docs/terminal/sydney.md +++ b/docs/terminal/sydney.md @@ -36,7 +36,6 @@ SY TCU is responsible for the Sydney TMA, except: - R470 Restricted Area, when RIC ADC is online (or as negotiated) ### Reclassifications - #### BK CTR BK CTR reverts to Class G when **BK ADC** is offline, and is administered by the relevant SY TCU controller. @@ -45,6 +44,14 @@ See also: [BK ADC Offline](#bk-adc-offline). #### CN CTR CN CTR reverts to Class G when **CN ADC** is offline, and is administered by the relevant SY TCU controller. +#### RI CTR +RI ADC being online will activate the **R470** Restricted Area, which is reclassified as **Class C** when active. + +Control authority of the **R470** Restricted Area when active is as follows: + +- RI ADC `SFC`-`A015` +- SY TCU (SDN) `A015`-`A045` + ### Airspace Structural Arrangements Pursuant to Section 2 of the [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}, the following rules apply, in the order presented, to these controller positions, except **SFL**: @@ -661,7 +668,14 @@ SY TCU will **NOT** clear the aircraft for the approach. **CN ADC** must issue an airways clearance to these aircraft on first contact. -### RIC ADC -Reserved. +### RI ADC +'Next' coordination is required from RI ADC to SY TCU for all aircraft. - +!!! example + **RI ADC** -> **SDN**: "Next, TROJ57, runway 28" + **SDN** -> **RI ADC**: "TROJ57, unrestricted" + **RI ADC** -> **SDN**: "TROJ57" + +The Standard Assignable Level from **RI ADC** to **SY TCU** is the lower of `A050` or `RFL`. + + \ No newline at end of file diff --git a/includes/abbreviations.md b/includes/abbreviations.md index 9aa72dd77..76464d781 100644 --- a/includes/abbreviations.md +++ b/includes/abbreviations.md @@ -258,6 +258,8 @@ *[PWLC]: Powerline Crossing *[LUY]: Latrobe University *[WMS]: Williamstown +*[NPBR]: Nepean Bridge +*[KRMD]: Kurmond *[YBBB]: Brisbane FIR *[YMMM]: Melbourne FIR *[NFFF]: Nadi FIR