You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/aerodromes/classc/Richmond.md
+44-14Lines changed: 44 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,27 +25,57 @@ Control authority of the **R470** Restricted Area when active is as follows:
25
25
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}
26
26
27
27
## SID Selection
28
-
Aircraft planned via **ANKUB**, **KADOM** or **MUDGI** may be assigned the SID that terminates at the appropriate waypoint. Aircraft who are not planned via these points, or who are negative RNAV, may be assigned a visual departure.
28
+
Military aircraft planned via **ANKUB**, **KADOM** or **MUDGI** may be assigned the SID that terminates at the appropriate waypoint. Aircraft who are not planned via these points, or who are negative RNAV, may be assigned a visual departure.
29
+
30
+
!!! tip
31
+
Military SID charts are contained in the [RAAF TERMA](https://ais-af.airforce.gov.au/){target=new} document.
29
32
30
33
## VFR Procedures
31
-
All VFR aircraft outbound and inbound, or transiting the field maintain `A015`.
32
-
Aircraft transiting the RIC CTR track via the northbound or southbound VFR route.
33
-
Aircraft transiting northbound contact RI ADC at NPBR for clearance.
34
-
Aircraft transiting southbound contact RI ADC at KRMD for clearance.
34
+
VFR aircraft transiting to/from YSRI should do so at `A015`.
35
35
36
-
!!! tip
37
-
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}.
36
+
Aircraft intending to transit the RIC CTR should plan via the [Richmond Lane of Entry](#richmond-lane-of-entry).
37
+
38
+
### Richmond Lane of Entry
39
+
A lane of entry is available in the western portion of the RIC CTR, allowing aircraft to transit the zone from north to south (or vice versa). A clearance is required from **RI ADC** prior to entering the CTR.
40
+
41
+
| Direction | Routing | Altitude | Reporting Point |
42
+
| --- | --- | --- | --- |
43
+
| Northbound | NPBR, then via the powerlines to KRMD, then WSFR |`A015`| KRMD |
44
+
| Southbound | WSFR to KRMD, then via the powerlines to NPBR |`A015`| KRMD |
45
+
46
+
!!! phraseology
47
+
**FWC**: "Richmond Tower, FWC, Cessna 172, 4nm south of NPBR, `A015`, received Bravo, for the lane of entry, request clearance"
**RI ADC**: "FWC, identified, cleared to track via the lane northbound, maintain `A015`"
52
+
**FWC**: "Cleared to track via the lane northbound, maintain `A015`, FWC"
53
+
54
+
Pilots must report their position and estimate for their next waypoint at KRMD.
55
+
56
+
!!! phraselogy
57
+
**FWC**: "FWC, KRMD, estimating WSFR at time 33"
58
+
**RI ADC**: "FWC"
59
+
60
+
Details of the lane are available in the `YSRI ERSA FAC` and on the Sydney VTC.
61
+
62
+
!!! note
63
+
Delays may be required during times of peak traffic into/out of YSRI.
38
64
39
65
### Training Areas
40
-
There are three training areas located within **R470**, used for civil and military operations.
66
+
There are three training areas located within R470, used for both civil and military operations.
67
+
68
+
!!! warning "Important"
69
+
Operations above `A015` may require an airspace release from **SY TCU**. Due to published departure procedures from YSSY, levels above `A040` may not be available.
| Londonderry Training Area |LDD TA |`SFC - A015`| Contained within R470 |
45
-
| Northern Training Area |NTA TA |`SFC - A060`| Contained within R470 |
46
-
| Southern Training Area |STA TA |`SFC - A040`| Contained within R470 |
71
+
| Name|Vertical Limits |Lateral Boundary|
72
+
|----|---------------|---|
73
+
| Londonderry Training Area |`SFC - A015`| Yarramundi Bridge<br>East to Springwood Road<br>Bonner Road to intersection of Vincent Road<br>West along Vincent Road to the intersection of the Nepean River<br>North via the eastern bank of the Nepean River to Yarramundi Bridge|
74
+
| Northern Training Area |`SFC - A060`| Intersection of North-South powerlines & Bells Line of Road<br>North along power lines to the R470 boundary<br>East along the R470 boundary to the Hawkesbury River<br>South tot Kurmond Road<br>West along Kurmond Road to Kurmond<br>Via Bells Line of Road to the intersection of the power lines|
75
+
| Southern Training Area |`SFC - A040`| Richmond Train Station<br>West to the water tank<br>Straight line to the R470 boundary<br>Along the R470 boundary to the Northern Road<br>Along Northern Road to the intersection of Richmond/Blacktown Road<br>Richmond Road to George & Macquarie Street to the railway overpass|
47
76
48
-
Refer to [YSRI FIHA AD2 SUPP](https://ais-af.airforce.gov.au/australian-aip){target=new} for charts and more info.
77
+
!!! tip
78
+
Diagrams of the training areas are available in the [Richmond FIHA AD2](https://ais-af.airforce.gov.au/){target=new} document.
49
79
50
80
## Circuit Operations
51
81
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`.
@@ -183,6 +190,39 @@ Except when the traffic situation warrants, taxi clearances shall conform to the
183
190
!!! tip
184
191
For aircraft taxiing northbound on B, consider instructing them to hold short of taxiway B8 when 34L or 16R are in use for arrivals, in order to separate from aircraft using the B7 & B9 rapid exits.
185
192
193
+
Additional standard taxi routes exist into and out of some domestic aprons.
`ERSA FAC YSSY` noise abatement procedures require jet aircraft to depart runway 34L from full length only. This should be simulated where practical but intersection departures should be offered to jet aircraft on request where available.
187
227
188
228
### Runway 16L/34R
@@ -205,6 +245,13 @@ Aircraft landing on runway 16L/34R are expected to vacate the runway and taxi vi
205
245
!!! phraseology
206
246
**SY ADC**: "JAL52, taxi via Tango, Lima, on Lima contact Ground 121.7"
207
247
248
+
The standard arrival taxi routes are:
249
+
250
+
| Landing Runway | Route |
251
+
| --- | --- |
252
+
| RWY 16L | T, L |
253
+
| RWY 34R | T2, U, U1, L, or<br>U1, L |
254
+
208
255
### Transferring Between SMCs
209
256
When both SMC positions are online and an aircraft is to be passed from one to the other (e.g. an aircraft taxis from the domestic terminal for runway 34L), they should be instructed to hold short of runway 16R/34L and to contact the next SMC frequency.
The Traffic Info plugin replicates the Eurocat window of the same name, which helps real world controllers manage the issuance of traffic information to pilots. Traffic pairings can be created between two or more aircraft, providing a place for controllers to record when traffic information is provided to each pilot.
9
+
10
+
The plugin is targeted towards Terminal and Enroute controllers.
11
+
12
+
<figuremarkdown>
13
+
{ width="700" }
14
+
</figure>
15
+
16
+
## Installation
17
+
The Traffic Info plugin can be installed through the [vatSys Plugin Manager](https://github.com/badvectors/PluginManager){target=new}.
18
+
19
+
## Usage
20
+
Controllers should create a pairing between two aircraft requiring traffic information as early as possible. This can act as a visual cue to ensure that they don't forget to issue the traffic information to each pilot.
21
+
22
+
### Create a Pairing
23
+
With an aircraft selected, hold the `F7` key and select a second aircraft.
24
+
25
+
The Traffic Info window will open (if it isn't already) and the traffic pairing will be created. Each individual aircraft is listed, with each relevant aircraft nested below. The callsign of each primary aircraft is coloured depending on their FDR state and owner.
26
+
27
+
<figuremarkdown>
28
+
{ width="700" }
29
+
</figure>
30
+
31
+
### Record Traffic Info
32
+
Once traffic information has been passed to a pilot, `left click` the nested callsign to change it from white to blue.
33
+
34
+
To mark traffic information as outstanding (not yet completed), `right click` the nested callsign to change it from blue to white.
35
+
36
+
<figuremarkdown>
37
+
{ width="700" }
38
+
<figcaption>Traffic information on RXA4356 has been provided to QLK270 but the reciprocal information to RXA4356 is still outstanding.</figcaption>
39
+
</figure>
40
+
41
+
### Delete Aircraft
42
+
When traffic information is no longer required or relevant, remove the traffic pairing.
43
+
44
+
`Middle click` the indented aircraft to remove them from the window. Deleting an aircraft will **not** delete the reciprocal pairing (i.e. deleting DEF from ABC **will not** delete ABC from DEF).
45
+
46
+
<figuremarkdown>
47
+
{ width="600" }
0 commit comments