Restructure
This commit is contained in:
AdamJCavanaugh
File diff suppressed because it is too large
Load Diff
@@ -1,373 +1,373 @@
|
||||
Endless ATC Dubai CTA v1.4 by Zac Kaplowitz
|
||||
|
||||
AIRAC 2103
|
||||
|
||||
v1.4 covers the Dubai CTA (OMDB, OMSJ, OMDW) in the 30 configuration. The Minhad restricted airspace is not yet included.
|
||||
|
||||
At OMDB, 30L is for arrivals, 30R is for departures. The platform altitude for 30L is 2000 feet. The platform altitude for 30R is 3000 feet. These altitudes must be used for glideslope intercept.
|
||||
|
||||
Aircraft should never fly the full STAR unless traffic necessitates it. Vectors should be used from the downwind leg to expedite the flow of traffic. A 90 degree base leg and a 30 degree ILS intercept must be used.
|
||||
|
||||
D-APO is implemented at OMDB. With skill set to 12 or above, 30R will open for arrivals as well as departures. 30R arrivals must still maintain separation from 30L arrivals and must establish at 3000 feet.
|
||||
For the purposes of separation, the 30L and 30R localisers are considered to be the same localiser.
|
||||
|
||||
At OMSJ, 30 is used for both arrivals and departures, meaning ICAO separation minima of 7nm must be applied on approach. The platform altitude for 30 is 2000 feet.
|
||||
|
||||
At OMDW, 30 is used for both arrivals and departures, meaning ICAO separation minima of 7nm must be applied on approach. The platform altitude for 30 is 2000 feet.
|
||||
|
||||
The initial climb at OMDB is 4000 feet. It is 3000 feet at OMDW, and 2000 feet at OMSJ.
|
||||
|
||||
Airspace from 1500-FL150.
|
||||
|
||||
On initial contact, arriving aircraft should be cleared for the arrival.
|
||||
|
||||
The minimum separation in the CTA is 3nm. The minimum separation on the localiser at OMDB is 2.5nm. Aircraft on the same SID must be handed off to UAE Radar with at least 8nm in trail.
|
||||
Aircraft entering the Muscat FIR via the same SID (any ANVIX departure, OMDB IVURO departures, OMDW NOLSU departures, OMSJ GETID departures) must be separated by 20nm on CTA exit.
|
||||
|
||||
In general altitudes are used for arrivals and odd altitudes for departures. This is ignored below 4000ft, as 3000ft is used to separate arrivals more efficiently.
|
||||
|
||||
Realistic traffic config:
|
||||
Skill 7, cap 9
|
||||
Flow 30, cap 30
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
General Arrival procedures
|
||||
Speeds
|
||||
|
||||
CTA entry - 230 knots
|
||||
Turning downwind on the DATOB5Z, IMPED3C, NOLSU2M, PUVAL6Z arrivals - 210 knots
|
||||
Passing the threshold on the downwind leg - 190 knots
|
||||
Until 10nm - 190 knots
|
||||
After 10nm - 160 knots
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
IMPED3C
|
||||
|
||||
Passing IMPED, direct ULDOT may be given for a straight-in approach. From the upwind leg, directs may be given to GIRGO, VELAR or RIDEV.
|
||||
6000 feet until DB515, then not below 4000 feet until established on downwind, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
LORID4D
|
||||
|
||||
If there are no ANVIX departures from OMDB, direct DB533 is permitted once past ORGUR. Directs to DB528 or RARPI are permitted once past EMOPO.
|
||||
10000 feet until ORGUR, then 8000 feet until crossing DB533, then 6000 feet, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
PUVAL5C
|
||||
|
||||
If there are no IVURO departures from OMDB and no arrivals or departures at OMSJ, direct GIRGO/VELAR/RIDEV may be given.
|
||||
10000ft until clear of IVURO departures from OMDB and GETID departures from OMSJ, then 9000 feet until clear of GONVI arrivals into OMSJ, then 8000 feet, then 6000 feet, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
VUTEB3D
|
||||
|
||||
No direct routings permitted.
|
||||
8000 feet until PATID, then 6000 feet until clear of departing traffic from OMDB and OMSJ, then 4000 feet until clear of 30L localiser, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
GONVI4M
|
||||
|
||||
No direct routings permitted.
|
||||
8000 feet until UKROL, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
LORID4M
|
||||
|
||||
No direct routings permitted.
|
||||
10000 until clear of OMDB westbound departures, then 8000 feet until UKROL, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
NOLSU2M
|
||||
|
||||
Passing NOLSU, direct NOGSO may be given for a straight-in approach.
|
||||
6000 feet until SJ516, then as required, while ensuring traffic crosses SJ517 below 4000 feet.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
PUVAL6M
|
||||
|
||||
Direct UKTAD is permitted.
|
||||
8000 feet until UKROL, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
DATOB5Z
|
||||
|
||||
If there are no westbound or northbound departures from any airports, direct DEDAX is permitted.
|
||||
10000 feet until DW427, then 8000 feet until DEDAX (or clear of OMDW departures), then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
LORID3Z
|
||||
|
||||
If there are no southbound departures from OMDW, direct DEDAX is permitted.
|
||||
8000 feet until TATMO, then 6000 feet until DEDAX (or clear of OMDW departures), then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
PUVAL6Z
|
||||
|
||||
No directs permitted.
|
||||
12000 feet until IVOXI, then 10000 feet until DW427, then 8000 feet until DEDAX (or clear of OMDW departures), then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
UMAMI4Z
|
||||
|
||||
Passing UMAMI, direct GEXIK may be given for a straight-in approach.
|
||||
6000 feet, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
General Departure Procedures
|
||||
High speed in the CTA
|
||||
|
||||
High speed (above 250kt) for departures is permitted once all turns greater than 30 degrees are completed.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
General Departure Procedures
|
||||
Separation minima
|
||||
|
||||
Aircraft on the same SID must be handed off to UAE Radar 8nm in trail or greater. Aircraft entering the Muscat FIR via the same SID (any ANVIX departure, OMDB IVURO departures, OMDW NOLSU departures, OMSJ GETID departures) must be separated by 20nm on CTA exit.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
ANVIX7F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until DB588, then 9000 feet until clear of OMDW arrivals, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
DAVMO4F
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of VUTEB and PUVAL arrivals into OMDB, then 7000 feet clear of NOLSU and PUVAL arrivals into OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
EMERU2F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until DB587, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
IVURO1F
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of VUTEB and PUVAL arrivals into OMDB, then 7000 feet until clear of NOLSU and PUVAL arrivals into OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
KUTLI4F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until DB587, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
NABIX3F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until clear of LORID arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
RIDAP2F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until clear of LORID arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
SENPA3F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until clear of LORID arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
ANVIX5R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
DAVMO3R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of NOLSU and PUVAL arrivals into OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
EMERU1R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
GETID1R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
KUTLI3R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
NABIX2R
|
||||
|
||||
No direct routings permitted.
|
||||
2000 feet until clear of DAVMO and IVURO departures from OMDB, then 7000 feet until clear of VUTEB arrivals into OMDB, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
RIDAP2R
|
||||
|
||||
No direct routings permitted.
|
||||
2000 feet until clear of DAVMO and IVURO departures from OMDB, then 7000 feet until clear of VUTEB arrivals into OMDB, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
SENPA2R
|
||||
|
||||
No direct routings permitted.
|
||||
2000 feet until clear of DAVMO and IVURO departures from OMDB, then 7000 feet until clear of VUTEB arrivals into OMDB, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
ANVIX4L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then 7000 feet until DW466, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
DAVMO4L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
EMERU1L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then FL150, handoff once leaving 5000 feet. Vectors may need to be used for separation as this SID is very short.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
KUTLI3L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then FL150, handoff once leaving 5000 feet. Vectors may need to be used for separation as this SID is very short.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
NABIX3L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
NOLSU3L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then 7000 feet until DW466, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
RIDAP3L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
SENPA3L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
Changelog
|
||||
|
||||
v1.0 - 11/03/2021 - Initial release
|
||||
|
||||
v1.1 - 11/03/2021 - Added D-APO, fixed callsign pronunciations, reduced frequency of DAVMO and IVURO departures, fixed auto-descent bug
|
||||
|
||||
v1.2 - 17/03/2021 - Added OMSJ and OMDW, adjusted OMDB departure proportions, modified MRVAs to allow for OMSJ and OMDW, modified readme climb instruction to reflect real world procedures for deconfliction of traffic to different airports in the CTA
|
||||
|
||||
v1.3 - 24/03/2021 - Fixed KUTLI3L departure, other minor fixes
|
||||
|
||||
Endless ATC Dubai CTA v1.4 by Zac Kaplowitz
|
||||
|
||||
AIRAC 2103
|
||||
|
||||
v1.4 covers the Dubai CTA (OMDB, OMSJ, OMDW) in the 30 configuration. The Minhad restricted airspace is not yet included.
|
||||
|
||||
At OMDB, 30L is for arrivals, 30R is for departures. The platform altitude for 30L is 2000 feet. The platform altitude for 30R is 3000 feet. These altitudes must be used for glideslope intercept.
|
||||
|
||||
Aircraft should never fly the full STAR unless traffic necessitates it. Vectors should be used from the downwind leg to expedite the flow of traffic. A 90 degree base leg and a 30 degree ILS intercept must be used.
|
||||
|
||||
D-APO is implemented at OMDB. With skill set to 12 or above, 30R will open for arrivals as well as departures. 30R arrivals must still maintain separation from 30L arrivals and must establish at 3000 feet.
|
||||
For the purposes of separation, the 30L and 30R localisers are considered to be the same localiser.
|
||||
|
||||
At OMSJ, 30 is used for both arrivals and departures, meaning ICAO separation minima of 7nm must be applied on approach. The platform altitude for 30 is 2000 feet.
|
||||
|
||||
At OMDW, 30 is used for both arrivals and departures, meaning ICAO separation minima of 7nm must be applied on approach. The platform altitude for 30 is 2000 feet.
|
||||
|
||||
The initial climb at OMDB is 4000 feet. It is 3000 feet at OMDW, and 2000 feet at OMSJ.
|
||||
|
||||
Airspace from 1500-FL150.
|
||||
|
||||
On initial contact, arriving aircraft should be cleared for the arrival.
|
||||
|
||||
The minimum separation in the CTA is 3nm. The minimum separation on the localiser at OMDB is 2.5nm. Aircraft on the same SID must be handed off to UAE Radar with at least 8nm in trail.
|
||||
Aircraft entering the Muscat FIR via the same SID (any ANVIX departure, OMDB IVURO departures, OMDW NOLSU departures, OMSJ GETID departures) must be separated by 20nm on CTA exit.
|
||||
|
||||
In general altitudes are used for arrivals and odd altitudes for departures. This is ignored below 4000ft, as 3000ft is used to separate arrivals more efficiently.
|
||||
|
||||
Realistic traffic config:
|
||||
Skill 7, cap 9
|
||||
Flow 30, cap 30
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
General Arrival procedures
|
||||
Speeds
|
||||
|
||||
CTA entry - 230 knots
|
||||
Turning downwind on the DATOB5Z, IMPED3C, NOLSU2M, PUVAL6Z arrivals - 210 knots
|
||||
Passing the threshold on the downwind leg - 190 knots
|
||||
Until 10nm - 190 knots
|
||||
After 10nm - 160 knots
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
IMPED3C
|
||||
|
||||
Passing IMPED, direct ULDOT may be given for a straight-in approach. From the upwind leg, directs may be given to GIRGO, VELAR or RIDEV.
|
||||
6000 feet until DB515, then not below 4000 feet until established on downwind, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
LORID4D
|
||||
|
||||
If there are no ANVIX departures from OMDB, direct DB533 is permitted once past ORGUR. Directs to DB528 or RARPI are permitted once past EMOPO.
|
||||
10000 feet until ORGUR, then 8000 feet until crossing DB533, then 6000 feet, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
PUVAL5C
|
||||
|
||||
If there are no IVURO departures from OMDB and no arrivals or departures at OMSJ, direct GIRGO/VELAR/RIDEV may be given.
|
||||
10000ft until clear of IVURO departures from OMDB and GETID departures from OMSJ, then 9000 feet until clear of GONVI arrivals into OMSJ, then 8000 feet, then 6000 feet, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Arrival Procedures
|
||||
VUTEB3D
|
||||
|
||||
No direct routings permitted.
|
||||
8000 feet until PATID, then 6000 feet until clear of departing traffic from OMDB and OMSJ, then 4000 feet until clear of 30L localiser, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
GONVI4M
|
||||
|
||||
No direct routings permitted.
|
||||
8000 feet until UKROL, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
LORID4M
|
||||
|
||||
No direct routings permitted.
|
||||
10000 until clear of OMDB westbound departures, then 8000 feet until UKROL, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
NOLSU2M
|
||||
|
||||
Passing NOLSU, direct NOGSO may be given for a straight-in approach.
|
||||
6000 feet until SJ516, then as required, while ensuring traffic crosses SJ517 below 4000 feet.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Arrival Procedures
|
||||
PUVAL6M
|
||||
|
||||
Direct UKTAD is permitted.
|
||||
8000 feet until UKROL, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
DATOB5Z
|
||||
|
||||
If there are no westbound or northbound departures from any airports, direct DEDAX is permitted.
|
||||
10000 feet until DW427, then 8000 feet until DEDAX (or clear of OMDW departures), then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
LORID3Z
|
||||
|
||||
If there are no southbound departures from OMDW, direct DEDAX is permitted.
|
||||
8000 feet until TATMO, then 6000 feet until DEDAX (or clear of OMDW departures), then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
PUVAL6Z
|
||||
|
||||
No directs permitted.
|
||||
12000 feet until IVOXI, then 10000 feet until DW427, then 8000 feet until DEDAX (or clear of OMDW departures), then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Arrival Procedures
|
||||
UMAMI4Z
|
||||
|
||||
Passing UMAMI, direct GEXIK may be given for a straight-in approach.
|
||||
6000 feet, then as required.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
General Departure Procedures
|
||||
High speed in the CTA
|
||||
|
||||
High speed (above 250kt) for departures is permitted once all turns greater than 30 degrees are completed.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
General Departure Procedures
|
||||
Separation minima
|
||||
|
||||
Aircraft on the same SID must be handed off to UAE Radar 8nm in trail or greater. Aircraft entering the Muscat FIR via the same SID (any ANVIX departure, OMDB IVURO departures, OMDW NOLSU departures, OMSJ GETID departures) must be separated by 20nm on CTA exit.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
ANVIX7F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until DB588, then 9000 feet until clear of OMDW arrivals, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
DAVMO4F
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of VUTEB and PUVAL arrivals into OMDB, then 7000 feet clear of NOLSU and PUVAL arrivals into OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
EMERU2F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until DB587, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
IVURO1F
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of VUTEB and PUVAL arrivals into OMDB, then 7000 feet until clear of NOLSU and PUVAL arrivals into OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
KUTLI4F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until DB587, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
NABIX3F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until clear of LORID arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
RIDAP2F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until clear of LORID arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDB Departure Procedures
|
||||
SENPA3F
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until clear of LORID arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
ANVIX5R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
DAVMO3R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of NOLSU and PUVAL arrivals into OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
EMERU1R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
GETID1R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
KUTLI3R
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until clear of GONVI arrivals into OMSJ, then 7000 feet until clear of PUVAL arrivals into OMDB and OMSJ, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
NABIX2R
|
||||
|
||||
No direct routings permitted.
|
||||
2000 feet until clear of DAVMO and IVURO departures from OMDB, then 7000 feet until clear of VUTEB arrivals into OMDB, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
RIDAP2R
|
||||
|
||||
No direct routings permitted.
|
||||
2000 feet until clear of DAVMO and IVURO departures from OMDB, then 7000 feet until clear of VUTEB arrivals into OMDB, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMSJ Departure Procedures
|
||||
SENPA2R
|
||||
|
||||
No direct routings permitted.
|
||||
2000 feet until clear of DAVMO and IVURO departures from OMDB, then 7000 feet until clear of VUTEB arrivals into OMDB, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
ANVIX4L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then 7000 feet until DW466, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
DAVMO4L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
EMERU1L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then FL150, handoff once leaving 5000 feet. Vectors may need to be used for separation as this SID is very short.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
KUTLI3L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then FL150, handoff once leaving 5000 feet. Vectors may need to be used for separation as this SID is very short.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
NABIX3L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
NOLSU3L
|
||||
|
||||
No direct routings permitted.
|
||||
5000 feet until DW465, then 7000 feet until DW466, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
RIDAP3L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
OMDW Departure Procedures
|
||||
SENPA3L
|
||||
|
||||
No direct routings permitted.
|
||||
7000 feet until XARTA, then FL150.
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
---------------------------------------------------------
|
||||
|
||||
Changelog
|
||||
|
||||
v1.0 - 11/03/2021 - Initial release
|
||||
|
||||
v1.1 - 11/03/2021 - Added D-APO, fixed callsign pronunciations, reduced frequency of DAVMO and IVURO departures, fixed auto-descent bug
|
||||
|
||||
v1.2 - 17/03/2021 - Added OMSJ and OMDW, adjusted OMDB departure proportions, modified MRVAs to allow for OMSJ and OMDW, modified readme climb instruction to reflect real world procedures for deconfliction of traffic to different airports in the CTA
|
||||
|
||||
v1.3 - 24/03/2021 - Fixed KUTLI3L departure, other minor fixes
|
||||
|
||||
v1.4 - 01/04/2021 - Updated to Endless ATC v4.4
|
||||
@@ -1,381 +1,381 @@
|
||||
# `RJBB` ACA 3.1.0
|
||||
|
||||
This is an implementation of the Kansai ACA (Approach Control Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `RJBB` Kansai International Airport, `RJOO` Osaka International Airport (often referred to as Itami), `RJBE` Kobe Airport, `RJOS` Tokushima Airport, `RJOT` Takamatsu Airport, `RJOB` Okayama Airport, and `RJOY` Yao Airport. The airspace ceiling is FL180.
|
||||
|
||||
The Kansai ACA is a very complex airspace, with many airports in close vicinity in Osaka Bay and the surroundings. There are many flight paths that cross over each other, and altitude will need to used to separate aircraft very often, especially within Osaka Bay and over Osaka City. The controller will need to carefully monitor both departures and arrivals and issue altitude, speed, and vectors to ensure proper separation.
|
||||
|
||||
Based upon AIP Japan 2021/08/12 (Ministry of Land, Infrastructure, Transport and Tourism) (https://aisjapan.mlit.go.jp/). The choice of SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All aircraft are assumed to be RNAV capable; no conventional NAVAID-based SIDs or STARs were implemented unless there is no RNAV procedure published. Coastline data from [naturalearthdata.com](http://www.naturalearthdata.com).
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Pressing the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
The published STARs for the aerodromes in the Kansai ACA typically do not have "at or below" crossing restrictions. Therefore, there are few restrictions implemented, and descent earlier than the latest possible descent is at controller's discretion, which will be necessary for separation throughout the sector. You can descend aircraft below the implemented restrictions for separation purposes in most cases; any "at or above" crossing restrictions are noted below per airport.
|
||||
|
||||
The Tokushima ACA which exists almost entirely under the Kansai ACA, is treated as part of Kansai ACA for gameplay purposes. Note that only aircraft arriving or departing RJOS Tokushima are allowed into the Tokushima ACA airspace (areas labeled with `OS`).
|
||||
|
||||
The Kansai ACA is extended over the Chubu ACA to the east around `SINGU` and `KODAI` as well as to the north around `ROKKO` and `WAKIT` for gameplay reasons. However, the southwestern part of Kansai ACA around `RJOK` Kochi is omitted for gameplay reasons. Flight routes between `RJOO`/`RJBB` and `RJOK` are also not represented.
|
||||
|
||||
## Airports
|
||||
|
||||
### `RJBB` Kansai International Airport
|
||||
|
||||
The main airport of this airspace, Kansai handles both domestic and international traffic to the Kansai region (Osaka, Kobe, Kyoto, Nara, etc). Arrivals/departures will fly over RJBE Kobe to the north, and care should taken here to maintain separation of aircraft.
|
||||
|
||||
There is custom traffic for `RJBB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Many fixes visible on the map have a defined hold including some key fixes along the STARs.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`SAEKI`) -> `ALISA` (northwest from Korea/northern China and northeast from NE Japan, Europe)
|
||||
- (`RANDY`) -> `BERTH` (west from Fukuoka, western Japan, China)
|
||||
- (`KARIN`) -> `BECKY` (southwest from southwestern Japan, Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- (`EVERT`) -> `CANDY` (southwest from Philippines, south from Indonesia/Oceania, east from Nagoya/PACOTS)
|
||||
- (`KOHWA`) -> `SINGU` -> `DANDE` (east from RJTT Tokyo, RJAA Narita, RJSS Sendai, RJSF Fukushima)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KEC` (east for `RJAA` Narita, PACOTS)
|
||||
- `SHTLE` (east for `RJTT` Tokyo)
|
||||
- `UENOH` (northeast to Tohoku, southeast Hokkaido)
|
||||
- `SIGAK` (northeast to northwest Hokkaido, east NA, Europe)
|
||||
- `YME` (northeast to northeastern China)
|
||||
- `SOUJA` (northwest to Korea, northern China, Europe)
|
||||
- `WASYU` (west to western Japan/Jeju)
|
||||
- `HABAR` (west to China)
|
||||
- `POPPY` (southwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 06R/24L (RWY A)
|
||||
- 06L/24R (RWY B)
|
||||
|
||||
Note that simultaneous parallel independent approaches do not appear to be in use at RJBB. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation.
|
||||
|
||||
The preferred runway is generally RWY A as the main terminal 1 is much closer to RWY A. LCC carriers operating from terminal 2 would have a shorter taxi from RWY B.
|
||||
|
||||
STARs are available from `ALISA`, `BERTH`, `BECKY`, `CANDY`, `DANDE`, and approach modes can be activated from those fixes as well as intermediate fixes on the STARs, as well as fixes on airways joining to the STARs.
|
||||
|
||||
There are two landing configurations:
|
||||
|
||||
- Landing/departing RWY 06L/06R
|
||||
|
||||
This is the preferred configuration for RJBB.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `ALLAN` and `BERRY`, and approaches from GATES are available from `JANET` and `JENNY`.
|
||||
|
||||
Use care not to descend arrivals into Tokushima ACA. Cross TANTA (from ALISA), NALTO (from BERTH), EVIAN, DATIS, JOLLY +6000 (at or above 6000).
|
||||
|
||||
Departures will be climbing over `RJBE` departures from 09, use care to maintain separation. Departures may also join paths after diverging initially especially after `MAIKO`, and may conflict with departures from `RJOO` and `RJBE` northwest of MAIKO.
|
||||
|
||||
The published hold for missed approaches is `LILAC` +3000 for 06L, `AKASI` +4000 (via MAIKO) for 06R.
|
||||
|
||||
- Landing/departing RWY 24L/24R
|
||||
|
||||
This is the south wind configuration for RJBB.
|
||||
|
||||
Vectors onto the localizer should NOT be used. Approaches are available from `MAYAH` (24L), or `AMBER` (24L) and `BEIGE` (24R). Arrivals can be vectored over the sea west of Awaji Island if needed on top of `RJBE` arrivals.
|
||||
|
||||
Use care not to descend arrivals into the `RJBE` PCA. Cross `JOLLY` (from `DANDE`) +8000, `AWAJI` +7000, `MAYAH` 4000 (**at** 4000). Aircraft should descend as per the approach after MAYAH in order to main separation from `RJBE` traffic. Note that due to the lack of circle to land approaches in Endless ATC, `RJBE` 27 arrivals will fly a long downwind at \~1300 and may conflict with `RJBB` 24 arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures to the west will be climbing through arrivals descending to 4000 from `AWAJI` to `LILAC` to `MAYAH` and over `RJBE departures`. Departures over `DAISY` should cross `DAISY` +6000 and JULIA +8000. Departures over HELEN should cross `HELEN` +8000. Due care will need to be taken to maintain separation. Recommend descending to arrivals to 4000 after `AWAJI`, and expediting climb of departures from 24R. Departures to the west may also conflict with `RJBE` departures and `RJOO` departures to the west.
|
||||
|
||||
Departures to the south may conflict with arrivals from DANDE and the south/southwest. Use caution.
|
||||
|
||||
### `RJOO` Osaka International Airport
|
||||
|
||||
An airport near the heart of Osaka, only domestic traffic is handled aside from the odd state aircraft. Mountains surround the airport to the north, west, and east.
|
||||
|
||||
There is custom traffic for `RJOO`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `ROKKO` (northwest from northwestern Japan, northeast from northeastern Japan)
|
||||
- `KODAI` (east from eastern Japan)
|
||||
- `KAZRA` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `JANGO` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `MUGIE` -> `HONMA` -> `KAINA` -> `IZUMI` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `MINAC` (northeast to Tohoku, Hokkaido)
|
||||
- `TOZAN` (northwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `KRE` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 14R/32L
|
||||
- 14L/32R
|
||||
|
||||
Larger aircraft land 14R/32L, as 14L/32R is generally only suitable for aircraft A320/B738 or smaller. It is not possible to model this in the game however.
|
||||
|
||||
Note that simultaneous parallel independent approaches are not used at `RJOO`. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation, however, this would not be used in reality as the runways are too close to each other.
|
||||
|
||||
Airspace to vector arrivals for sequencing is avaiable south of IKOMA/southeast of IZUMI/west of KODAI. Arrivals will fly over `RJOY` Yao, use care not to descend into YAO airspace. Use care to keep separation at `KAINA`, `ROKKO` and near `IKOMA`.
|
||||
|
||||
West departures may conflict with other aircraft on west departures. Use caution.
|
||||
|
||||
The missed approach hold is IZUMI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 32L/32R
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
Due to the mountains surrounding the airport, departures make a climbing left turn towards the south.
|
||||
|
||||
- Landing and departing 14L/14R
|
||||
|
||||
This runway configuration is only used when winds do not allow for use of the 32s. Arrivals circle west of the airport to land the 14s within the mountainous surroundings.
|
||||
|
||||
Due to the lack of circle to land approaches in Endless ATC, aircraft make long downwind to 14. Note that in real life these aircraft would have long flown into terrain, but this is the best we can do here.
|
||||
|
||||
Departures may conflict with arrivals circling to 14. Use caution.
|
||||
|
||||
West departures may conflict with other aircraft on west departures or arrivals to `RJBE`/`RJOT`/`RJOB`. Use caution.
|
||||
|
||||
### `RJBE` Kobe Airport
|
||||
|
||||
A smaller airport in Osaka Bay minutes from central Kobe. Located under to approach to the 24s at `RJBB`, typically in-out operations landing 09 and departing 27 are ideal. Unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJBE`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east from eastern Japan)
|
||||
- `WAKIT` (northeast from northeastern Japan)
|
||||
- `RANDY` -> `BERTH` (west from western Japan)
|
||||
- `KARIN` -> `BECKY` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `CUE` (east to eastern Japan)
|
||||
- `YME` (northeast to Tohoku/Hokkaido)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `POPPY` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
Aircraft arriving/departing `RJBE` in general will be operating under `RJBB` traffic. Ensure that arrivals are low enough before entering the bay, and that departures are clear of traffic above before issuing further climb.
|
||||
|
||||
Arrivals can be vectored over the sea west of Awaji Island.
|
||||
|
||||
Departures may conflict with other aircraft on west departures or arrivals to `RJOT`/`RJOB`. Use caution.
|
||||
|
||||
The missed approach hold is SIOJI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The preferred runway configuration. Departures make a climbing right turn to depart to the west remaining under `RJBB` departures and over `RJBE` arrivals.
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
This runway configuration is used when `RJBB` is landing 24, as Endless ATC requires departures to climb to a minimum of 3000 which would conflict with the `RJBB` 24 approach path. Arrivals circle to land 27, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 27, and may conflict with RJBB arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures will need to climb to 4000 or higher to clear arrivals at 3000.
|
||||
|
||||
### `RJOS` Tokushima Airport
|
||||
|
||||
A joint-use civilian airport and JSDF-M base. Training operations with Beech King Airs are conducted by the JSDF-M from this base. Typically in-out operations landing 29 and departing 11 are ideal; unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJOS`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `JOSIN` (southeast to training areas?)
|
||||
- `SINGU` -> ... -> `DATIS` (east from Tokyo)
|
||||
- `KTE` -> `KULUL` -> `TSC` (west from Fukuoka)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KMANO` (east for Tokyo)
|
||||
- `KTE` -> `WASYU` (west to Fukuoka)
|
||||
- `TOSAR` (south to training areas?)
|
||||
|
||||
Departures may conflict with other aircraft on southwest departures and `RJBB` `CANDY` arrivals. Use caution.
|
||||
|
||||
The missed approach hold is TSC/DATIS +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 29
|
||||
|
||||
The preferred runway configuration. Departures make a climbing left turn to depart to the southeast.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 29. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOT` Takamatsu Airport
|
||||
|
||||
An airport nestled up against mountains to the south serving Takamatsu.
|
||||
|
||||
There is custom traffic for `RJOT`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- (`TAKMA`) -> `KTE` (west/southwest)
|
||||
- (`YUBAR`) -> `OYE` -> `KTE` (northwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `WASYU` (west)
|
||||
- `TAROH` (north)
|
||||
|
||||
The missed approach hold is KTE +5000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 26
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 26. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOB` Okayama Airport
|
||||
|
||||
An airport situated in the mountains serving Okayama.
|
||||
|
||||
There is custom traffic for `RJOB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- `WAKIT` (northeast)
|
||||
- (`YUBAR`) -> `OYE`(north)
|
||||
- (`TAKMA`) -> `INOOK` (west/southwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `YME` (northeast)
|
||||
- `YUBAR` (north)
|
||||
- `WASYU` (west)
|
||||
|
||||
The missed approach hold is `OYE`/`BENES` +4000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 07
|
||||
|
||||
The preferred runway configuration for arrivals from the west. A RNAV AR approach utilizing RF legs to circle to 07 from the east is available in reality but the final leg is too short to be reproducible in Endless ATC. Therefore, east arrivals fly the ILS from OYE.
|
||||
|
||||
- Landing and departing 25
|
||||
|
||||
The preferred runway configuration for arrivals from the east. The straight-in to 25 is an RNAV approach as there is no ILS for 25.
|
||||
|
||||
### `RJOY` Yao Airport
|
||||
|
||||
A small airport near Osaka that acts as a general aviation gateway.
|
||||
|
||||
There is custom traffic for `RJOY`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`MIDER`) -> `ITE` (east)
|
||||
- `ROKKO` (north)
|
||||
- (`YUBAR`) -> `OYE`(northwest)
|
||||
- (`KAIFU` -> `IZARI`) -> `MIKAN` (west/southwest)
|
||||
- (`NORAN`) -> `IZUMI` (southeast)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KCC` via `ASUKA` (east)
|
||||
- `KRE` via `IZUMI`, `ITE`, `OLIVE` (southwest)
|
||||
- `YME` via `IZUMI` (north)
|
||||
- `YUBAR` via `IZUMI` (northwest)
|
||||
- `WASYU` via `IZUMI` (west)
|
||||
|
||||
The missed approach hold is `IZUMI` +4200.
|
||||
|
||||
The only instrument approaches available are a VORDME or VOR circling approach from `IZUMI`. The VORDME approach is implemented with circling to all runways. Runway 13/31 is not enabled at this time, but can be easily enabled by editing [configurations] as the other relevant data is all there.
|
||||
|
||||
There is a very high potential for conflicts to the west of the airport. The airport and the VORDME approach sit under the approach path for `RJOO` traffic via `IZUMI`, so you effectively have a ceiling of 5000 to work with when there is traffic overhead. Alternatively, you can vector `RJOO` arrivals to the south to clear the airspace overhead.
|
||||
|
||||
Aircraft inbound to `IZUMI` via V55 from `ITE` will need to stay above `RJOO` departures and `RJBB` arrivals, while staying below `RJBB` `NANKO` departures, `RJOO` arrivals via `IZUMI`, and `RJOY` `ASUKA` departures. Aircraft departing via `IZUMI` (V55) `ITE` will also need to separated from opposite direction inbound traffic. Any aircraft going missed will also need to be separated from other `RJOY` arrivals, and in the case of landing 09, from aircraft inbound the `RJOO` 32s.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
The calm wind configuration. Use care for `ASUKA` departures; keep them separated from arrivals inbound `IZUMI` from `ITE`, and climb them above aircraft on final for `RJOO`.
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The reverse configuration. Use care for `ASUKA` departures to keep them separated from arrivals inbound `IZUMI` from `ITE`.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- Circle to land approaches...............*sigh* They kinda work, but the game is not good at handling close-in base turns so they turn base and final around 4NM out.
|
||||
|
||||
## Changelog
|
||||
|
||||
* 1.0.0 - 2020/10/12 - Initial version.
|
||||
* 2.0.0 - 2020/11/02
|
||||
- Added approaches to both runway ends for all airports.
|
||||
- Added approaches to many, many fixes as the approach limit has been lifted.
|
||||
- Adjusted eastern ACA extension over Chubu ACA
|
||||
- Added previously cut western ACA
|
||||
- Added part of previously cut southwestern ACA
|
||||
- Added `RJOB` Okayama
|
||||
- Arrivals for `RJOO`, `RJBE`, `RJOS`, `RJOT` now fly direct to the a suitable fix inside RJBB ACA on their arrival route instead of a single point for all arrivals.
|
||||
- Adjusted entry points
|
||||
- Removed `Y53 BECKY` entry point for `RJOO`
|
||||
- Removed `YOSAK` departures from `RJBB` (not used in daytime)
|
||||
- Removed `CUE`/`POPPY` departures from `RJOO` (not used in standard flight planned routes)
|
||||
- Removed `MISAKI1` departure from `RJOS` (use HONMA1.KILAP instead for RNAV-capable)
|
||||
- Added `UENOH` departures from `RJBB` (as per standard flight planned route)
|
||||
- Adjusted traffic frequencies
|
||||
- Changed names of airports for voice purposes
|
||||
- Added various minor fixes
|
||||
- Added Akeno ACA area
|
||||
- Removed training areas as they should be more inactive rather than active...?
|
||||
* 3.0.0 - 2021/05/24
|
||||
- Rewrite of source
|
||||
- Removed most of the arbitrary altitude restrictions for approaches
|
||||
- Added FL130 250kt restriction at `KODAI` for `RJOO` to compensate for game spawning arrivals via `OHDAI` at high altitudes and speeds
|
||||
- Complete overhaul of circle to land approaches
|
||||
- `RJOO` 14s
|
||||
- aircraft break left at around `UMEDA`
|
||||
- `RJOT` 08
|
||||
- `RJOS` 11
|
||||
- `RJBE` 27
|
||||
- aircraft break right around 5DME
|
||||
- 27 arrivals now stay above 2500 until established on downwind
|
||||
- they will descent to 1500 and keep clear of RJBB arrivals descending overhead to 2600
|
||||
- 27 arrivals on base no longer conflict with RJBB 24 arrivals descending below 2600
|
||||
- 27 departures can now fly under 27 arrivals to reach `MAIKO`
|
||||
- or climb above 3500 to clear if the arrival is further out
|
||||
- Added `RJBB` ILS Y approaches
|
||||
- Revised `RJOO` `MIRIO`, `JANGO` entry points
|
||||
- Added `RJOO` RNAV 32L approaches
|
||||
- Added another runway configuration
|
||||
- Overhauled `RJOO` departure routes
|
||||
- 32R `ASUKA` departures no longer turn right
|
||||
- Corrected departure fixes based on ITE radials
|
||||
- Added `FOSTA` transition
|
||||
- Overhauled `RJBB` Kansai and Nanko departures
|
||||
- Planes now correctly fly over fly-over waypoints
|
||||
- 24L Kansai departures no longer turn left
|
||||
- Improved the shape of many restricted areas
|
||||
- `CUE` Otsu VORDME decommissioned
|
||||
- `MIDER` established
|
||||
- `RJOO` OTSU FIVE DEPARTURE and KOMATSU TRANSITION abolished
|
||||
- `RJOO` PANAS ONE DEPARTURE and KOMAZ TRANSITION established
|
||||
- `RJBE` OTSU TRANSITION abolished
|
||||
- `RJBE` MIDER TRANSITION established
|
||||
- Added `RJOY` Yao
|
||||
- Only runway 09-27
|
||||
- Added many new GA aircraft types
|
||||
* 3.1.0 - 2021/07/02
|
||||
- Add handoff callsign / frequency support
|
||||
# `RJBB` ACA 3.1.0
|
||||
|
||||
This is an implementation of the Kansai ACA (Approach Control Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `RJBB` Kansai International Airport, `RJOO` Osaka International Airport (often referred to as Itami), `RJBE` Kobe Airport, `RJOS` Tokushima Airport, `RJOT` Takamatsu Airport, `RJOB` Okayama Airport, and `RJOY` Yao Airport. The airspace ceiling is FL180.
|
||||
|
||||
The Kansai ACA is a very complex airspace, with many airports in close vicinity in Osaka Bay and the surroundings. There are many flight paths that cross over each other, and altitude will need to used to separate aircraft very often, especially within Osaka Bay and over Osaka City. The controller will need to carefully monitor both departures and arrivals and issue altitude, speed, and vectors to ensure proper separation.
|
||||
|
||||
Based upon AIP Japan 2021/08/12 (Ministry of Land, Infrastructure, Transport and Tourism) (https://aisjapan.mlit.go.jp/). The choice of SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All aircraft are assumed to be RNAV capable; no conventional NAVAID-based SIDs or STARs were implemented unless there is no RNAV procedure published. Coastline data from [naturalearthdata.com](http://www.naturalearthdata.com).
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Pressing the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
The published STARs for the aerodromes in the Kansai ACA typically do not have "at or below" crossing restrictions. Therefore, there are few restrictions implemented, and descent earlier than the latest possible descent is at controller's discretion, which will be necessary for separation throughout the sector. You can descend aircraft below the implemented restrictions for separation purposes in most cases; any "at or above" crossing restrictions are noted below per airport.
|
||||
|
||||
The Tokushima ACA which exists almost entirely under the Kansai ACA, is treated as part of Kansai ACA for gameplay purposes. Note that only aircraft arriving or departing RJOS Tokushima are allowed into the Tokushima ACA airspace (areas labeled with `OS`).
|
||||
|
||||
The Kansai ACA is extended over the Chubu ACA to the east around `SINGU` and `KODAI` as well as to the north around `ROKKO` and `WAKIT` for gameplay reasons. However, the southwestern part of Kansai ACA around `RJOK` Kochi is omitted for gameplay reasons. Flight routes between `RJOO`/`RJBB` and `RJOK` are also not represented.
|
||||
|
||||
## Airports
|
||||
|
||||
### `RJBB` Kansai International Airport
|
||||
|
||||
The main airport of this airspace, Kansai handles both domestic and international traffic to the Kansai region (Osaka, Kobe, Kyoto, Nara, etc). Arrivals/departures will fly over RJBE Kobe to the north, and care should taken here to maintain separation of aircraft.
|
||||
|
||||
There is custom traffic for `RJBB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Many fixes visible on the map have a defined hold including some key fixes along the STARs.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`SAEKI`) -> `ALISA` (northwest from Korea/northern China and northeast from NE Japan, Europe)
|
||||
- (`RANDY`) -> `BERTH` (west from Fukuoka, western Japan, China)
|
||||
- (`KARIN`) -> `BECKY` (southwest from southwestern Japan, Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- (`EVERT`) -> `CANDY` (southwest from Philippines, south from Indonesia/Oceania, east from Nagoya/PACOTS)
|
||||
- (`KOHWA`) -> `SINGU` -> `DANDE` (east from RJTT Tokyo, RJAA Narita, RJSS Sendai, RJSF Fukushima)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KEC` (east for `RJAA` Narita, PACOTS)
|
||||
- `SHTLE` (east for `RJTT` Tokyo)
|
||||
- `UENOH` (northeast to Tohoku, southeast Hokkaido)
|
||||
- `SIGAK` (northeast to northwest Hokkaido, east NA, Europe)
|
||||
- `YME` (northeast to northeastern China)
|
||||
- `SOUJA` (northwest to Korea, northern China, Europe)
|
||||
- `WASYU` (west to western Japan/Jeju)
|
||||
- `HABAR` (west to China)
|
||||
- `POPPY` (southwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 06R/24L (RWY A)
|
||||
- 06L/24R (RWY B)
|
||||
|
||||
Note that simultaneous parallel independent approaches do not appear to be in use at RJBB. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation.
|
||||
|
||||
The preferred runway is generally RWY A as the main terminal 1 is much closer to RWY A. LCC carriers operating from terminal 2 would have a shorter taxi from RWY B.
|
||||
|
||||
STARs are available from `ALISA`, `BERTH`, `BECKY`, `CANDY`, `DANDE`, and approach modes can be activated from those fixes as well as intermediate fixes on the STARs, as well as fixes on airways joining to the STARs.
|
||||
|
||||
There are two landing configurations:
|
||||
|
||||
- Landing/departing RWY 06L/06R
|
||||
|
||||
This is the preferred configuration for RJBB.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `ALLAN` and `BERRY`, and approaches from GATES are available from `JANET` and `JENNY`.
|
||||
|
||||
Use care not to descend arrivals into Tokushima ACA. Cross TANTA (from ALISA), NALTO (from BERTH), EVIAN, DATIS, JOLLY +6000 (at or above 6000).
|
||||
|
||||
Departures will be climbing over `RJBE` departures from 09, use care to maintain separation. Departures may also join paths after diverging initially especially after `MAIKO`, and may conflict with departures from `RJOO` and `RJBE` northwest of MAIKO.
|
||||
|
||||
The published hold for missed approaches is `LILAC` +3000 for 06L, `AKASI` +4000 (via MAIKO) for 06R.
|
||||
|
||||
- Landing/departing RWY 24L/24R
|
||||
|
||||
This is the south wind configuration for RJBB.
|
||||
|
||||
Vectors onto the localizer should NOT be used. Approaches are available from `MAYAH` (24L), or `AMBER` (24L) and `BEIGE` (24R). Arrivals can be vectored over the sea west of Awaji Island if needed on top of `RJBE` arrivals.
|
||||
|
||||
Use care not to descend arrivals into the `RJBE` PCA. Cross `JOLLY` (from `DANDE`) +8000, `AWAJI` +7000, `MAYAH` 4000 (**at** 4000). Aircraft should descend as per the approach after MAYAH in order to main separation from `RJBE` traffic. Note that due to the lack of circle to land approaches in Endless ATC, `RJBE` 27 arrivals will fly a long downwind at \~1300 and may conflict with `RJBB` 24 arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures to the west will be climbing through arrivals descending to 4000 from `AWAJI` to `LILAC` to `MAYAH` and over `RJBE departures`. Departures over `DAISY` should cross `DAISY` +6000 and JULIA +8000. Departures over HELEN should cross `HELEN` +8000. Due care will need to be taken to maintain separation. Recommend descending to arrivals to 4000 after `AWAJI`, and expediting climb of departures from 24R. Departures to the west may also conflict with `RJBE` departures and `RJOO` departures to the west.
|
||||
|
||||
Departures to the south may conflict with arrivals from DANDE and the south/southwest. Use caution.
|
||||
|
||||
### `RJOO` Osaka International Airport
|
||||
|
||||
An airport near the heart of Osaka, only domestic traffic is handled aside from the odd state aircraft. Mountains surround the airport to the north, west, and east.
|
||||
|
||||
There is custom traffic for `RJOO`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `ROKKO` (northwest from northwestern Japan, northeast from northeastern Japan)
|
||||
- `KODAI` (east from eastern Japan)
|
||||
- `KAZRA` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `JANGO` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `MUGIE` -> `HONMA` -> `KAINA` -> `IZUMI` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `MINAC` (northeast to Tohoku, Hokkaido)
|
||||
- `TOZAN` (northwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `KRE` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 14R/32L
|
||||
- 14L/32R
|
||||
|
||||
Larger aircraft land 14R/32L, as 14L/32R is generally only suitable for aircraft A320/B738 or smaller. It is not possible to model this in the game however.
|
||||
|
||||
Note that simultaneous parallel independent approaches are not used at `RJOO`. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation, however, this would not be used in reality as the runways are too close to each other.
|
||||
|
||||
Airspace to vector arrivals for sequencing is avaiable south of IKOMA/southeast of IZUMI/west of KODAI. Arrivals will fly over `RJOY` Yao, use care not to descend into YAO airspace. Use care to keep separation at `KAINA`, `ROKKO` and near `IKOMA`.
|
||||
|
||||
West departures may conflict with other aircraft on west departures. Use caution.
|
||||
|
||||
The missed approach hold is IZUMI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 32L/32R
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
Due to the mountains surrounding the airport, departures make a climbing left turn towards the south.
|
||||
|
||||
- Landing and departing 14L/14R
|
||||
|
||||
This runway configuration is only used when winds do not allow for use of the 32s. Arrivals circle west of the airport to land the 14s within the mountainous surroundings.
|
||||
|
||||
Due to the lack of circle to land approaches in Endless ATC, aircraft make long downwind to 14. Note that in real life these aircraft would have long flown into terrain, but this is the best we can do here.
|
||||
|
||||
Departures may conflict with arrivals circling to 14. Use caution.
|
||||
|
||||
West departures may conflict with other aircraft on west departures or arrivals to `RJBE`/`RJOT`/`RJOB`. Use caution.
|
||||
|
||||
### `RJBE` Kobe Airport
|
||||
|
||||
A smaller airport in Osaka Bay minutes from central Kobe. Located under to approach to the 24s at `RJBB`, typically in-out operations landing 09 and departing 27 are ideal. Unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJBE`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east from eastern Japan)
|
||||
- `WAKIT` (northeast from northeastern Japan)
|
||||
- `RANDY` -> `BERTH` (west from western Japan)
|
||||
- `KARIN` -> `BECKY` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `CUE` (east to eastern Japan)
|
||||
- `YME` (northeast to Tohoku/Hokkaido)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `POPPY` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
Aircraft arriving/departing `RJBE` in general will be operating under `RJBB` traffic. Ensure that arrivals are low enough before entering the bay, and that departures are clear of traffic above before issuing further climb.
|
||||
|
||||
Arrivals can be vectored over the sea west of Awaji Island.
|
||||
|
||||
Departures may conflict with other aircraft on west departures or arrivals to `RJOT`/`RJOB`. Use caution.
|
||||
|
||||
The missed approach hold is SIOJI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The preferred runway configuration. Departures make a climbing right turn to depart to the west remaining under `RJBB` departures and over `RJBE` arrivals.
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
This runway configuration is used when `RJBB` is landing 24, as Endless ATC requires departures to climb to a minimum of 3000 which would conflict with the `RJBB` 24 approach path. Arrivals circle to land 27, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 27, and may conflict with RJBB arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures will need to climb to 4000 or higher to clear arrivals at 3000.
|
||||
|
||||
### `RJOS` Tokushima Airport
|
||||
|
||||
A joint-use civilian airport and JSDF-M base. Training operations with Beech King Airs are conducted by the JSDF-M from this base. Typically in-out operations landing 29 and departing 11 are ideal; unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJOS`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `JOSIN` (southeast to training areas?)
|
||||
- `SINGU` -> ... -> `DATIS` (east from Tokyo)
|
||||
- `KTE` -> `KULUL` -> `TSC` (west from Fukuoka)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KMANO` (east for Tokyo)
|
||||
- `KTE` -> `WASYU` (west to Fukuoka)
|
||||
- `TOSAR` (south to training areas?)
|
||||
|
||||
Departures may conflict with other aircraft on southwest departures and `RJBB` `CANDY` arrivals. Use caution.
|
||||
|
||||
The missed approach hold is TSC/DATIS +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 29
|
||||
|
||||
The preferred runway configuration. Departures make a climbing left turn to depart to the southeast.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 29. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOT` Takamatsu Airport
|
||||
|
||||
An airport nestled up against mountains to the south serving Takamatsu.
|
||||
|
||||
There is custom traffic for `RJOT`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- (`TAKMA`) -> `KTE` (west/southwest)
|
||||
- (`YUBAR`) -> `OYE` -> `KTE` (northwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `WASYU` (west)
|
||||
- `TAROH` (north)
|
||||
|
||||
The missed approach hold is KTE +5000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 26
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 26. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOB` Okayama Airport
|
||||
|
||||
An airport situated in the mountains serving Okayama.
|
||||
|
||||
There is custom traffic for `RJOB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- `WAKIT` (northeast)
|
||||
- (`YUBAR`) -> `OYE`(north)
|
||||
- (`TAKMA`) -> `INOOK` (west/southwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `YME` (northeast)
|
||||
- `YUBAR` (north)
|
||||
- `WASYU` (west)
|
||||
|
||||
The missed approach hold is `OYE`/`BENES` +4000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 07
|
||||
|
||||
The preferred runway configuration for arrivals from the west. A RNAV AR approach utilizing RF legs to circle to 07 from the east is available in reality but the final leg is too short to be reproducible in Endless ATC. Therefore, east arrivals fly the ILS from OYE.
|
||||
|
||||
- Landing and departing 25
|
||||
|
||||
The preferred runway configuration for arrivals from the east. The straight-in to 25 is an RNAV approach as there is no ILS for 25.
|
||||
|
||||
### `RJOY` Yao Airport
|
||||
|
||||
A small airport near Osaka that acts as a general aviation gateway.
|
||||
|
||||
There is custom traffic for `RJOY`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`MIDER`) -> `ITE` (east)
|
||||
- `ROKKO` (north)
|
||||
- (`YUBAR`) -> `OYE`(northwest)
|
||||
- (`KAIFU` -> `IZARI`) -> `MIKAN` (west/southwest)
|
||||
- (`NORAN`) -> `IZUMI` (southeast)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KCC` via `ASUKA` (east)
|
||||
- `KRE` via `IZUMI`, `ITE`, `OLIVE` (southwest)
|
||||
- `YME` via `IZUMI` (north)
|
||||
- `YUBAR` via `IZUMI` (northwest)
|
||||
- `WASYU` via `IZUMI` (west)
|
||||
|
||||
The missed approach hold is `IZUMI` +4200.
|
||||
|
||||
The only instrument approaches available are a VORDME or VOR circling approach from `IZUMI`. The VORDME approach is implemented with circling to all runways. Runway 13/31 is not enabled at this time, but can be easily enabled by editing [configurations] as the other relevant data is all there.
|
||||
|
||||
There is a very high potential for conflicts to the west of the airport. The airport and the VORDME approach sit under the approach path for `RJOO` traffic via `IZUMI`, so you effectively have a ceiling of 5000 to work with when there is traffic overhead. Alternatively, you can vector `RJOO` arrivals to the south to clear the airspace overhead.
|
||||
|
||||
Aircraft inbound to `IZUMI` via V55 from `ITE` will need to stay above `RJOO` departures and `RJBB` arrivals, while staying below `RJBB` `NANKO` departures, `RJOO` arrivals via `IZUMI`, and `RJOY` `ASUKA` departures. Aircraft departing via `IZUMI` (V55) `ITE` will also need to separated from opposite direction inbound traffic. Any aircraft going missed will also need to be separated from other `RJOY` arrivals, and in the case of landing 09, from aircraft inbound the `RJOO` 32s.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
The calm wind configuration. Use care for `ASUKA` departures; keep them separated from arrivals inbound `IZUMI` from `ITE`, and climb them above aircraft on final for `RJOO`.
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The reverse configuration. Use care for `ASUKA` departures to keep them separated from arrivals inbound `IZUMI` from `ITE`.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- Circle to land approaches...............*sigh* They kinda work, but the game is not good at handling close-in base turns so they turn base and final around 4NM out.
|
||||
|
||||
## Changelog
|
||||
|
||||
* 1.0.0 - 2020/10/12 - Initial version.
|
||||
* 2.0.0 - 2020/11/02
|
||||
- Added approaches to both runway ends for all airports.
|
||||
- Added approaches to many, many fixes as the approach limit has been lifted.
|
||||
- Adjusted eastern ACA extension over Chubu ACA
|
||||
- Added previously cut western ACA
|
||||
- Added part of previously cut southwestern ACA
|
||||
- Added `RJOB` Okayama
|
||||
- Arrivals for `RJOO`, `RJBE`, `RJOS`, `RJOT` now fly direct to the a suitable fix inside RJBB ACA on their arrival route instead of a single point for all arrivals.
|
||||
- Adjusted entry points
|
||||
- Removed `Y53 BECKY` entry point for `RJOO`
|
||||
- Removed `YOSAK` departures from `RJBB` (not used in daytime)
|
||||
- Removed `CUE`/`POPPY` departures from `RJOO` (not used in standard flight planned routes)
|
||||
- Removed `MISAKI1` departure from `RJOS` (use HONMA1.KILAP instead for RNAV-capable)
|
||||
- Added `UENOH` departures from `RJBB` (as per standard flight planned route)
|
||||
- Adjusted traffic frequencies
|
||||
- Changed names of airports for voice purposes
|
||||
- Added various minor fixes
|
||||
- Added Akeno ACA area
|
||||
- Removed training areas as they should be more inactive rather than active...?
|
||||
* 3.0.0 - 2021/05/24
|
||||
- Rewrite of source
|
||||
- Removed most of the arbitrary altitude restrictions for approaches
|
||||
- Added FL130 250kt restriction at `KODAI` for `RJOO` to compensate for game spawning arrivals via `OHDAI` at high altitudes and speeds
|
||||
- Complete overhaul of circle to land approaches
|
||||
- `RJOO` 14s
|
||||
- aircraft break left at around `UMEDA`
|
||||
- `RJOT` 08
|
||||
- `RJOS` 11
|
||||
- `RJBE` 27
|
||||
- aircraft break right around 5DME
|
||||
- 27 arrivals now stay above 2500 until established on downwind
|
||||
- they will descent to 1500 and keep clear of RJBB arrivals descending overhead to 2600
|
||||
- 27 arrivals on base no longer conflict with RJBB 24 arrivals descending below 2600
|
||||
- 27 departures can now fly under 27 arrivals to reach `MAIKO`
|
||||
- or climb above 3500 to clear if the arrival is further out
|
||||
- Added `RJBB` ILS Y approaches
|
||||
- Revised `RJOO` `MIRIO`, `JANGO` entry points
|
||||
- Added `RJOO` RNAV 32L approaches
|
||||
- Added another runway configuration
|
||||
- Overhauled `RJOO` departure routes
|
||||
- 32R `ASUKA` departures no longer turn right
|
||||
- Corrected departure fixes based on ITE radials
|
||||
- Added `FOSTA` transition
|
||||
- Overhauled `RJBB` Kansai and Nanko departures
|
||||
- Planes now correctly fly over fly-over waypoints
|
||||
- 24L Kansai departures no longer turn left
|
||||
- Improved the shape of many restricted areas
|
||||
- `CUE` Otsu VORDME decommissioned
|
||||
- `MIDER` established
|
||||
- `RJOO` OTSU FIVE DEPARTURE and KOMATSU TRANSITION abolished
|
||||
- `RJOO` PANAS ONE DEPARTURE and KOMAZ TRANSITION established
|
||||
- `RJBE` OTSU TRANSITION abolished
|
||||
- `RJBE` MIDER TRANSITION established
|
||||
- Added `RJOY` Yao
|
||||
- Only runway 09-27
|
||||
- Added many new GA aircraft types
|
||||
* 3.1.0 - 2021/07/02
|
||||
- Add handoff callsign / frequency support
|
||||
- Improve reading of Tokushima
|
||||
@@ -1,366 +1,366 @@
|
||||
# `RJBB` 進入管制区 3.1.0
|
||||
|
||||
＊作者は日本人ではありません。以下の文章には間違っている日本語、または間違っている情報が含まれている場合があります。ご了承いただければ幸いです。
|
||||
|
||||
KANSAI ACA(関西進入管制区)を[Endless ATC](https://steamcommunity.com/app/666610)に追加するMODです。`RJBB`関西国際空港、`RJOO`大阪国際空港(伊丹)、`RJBB`神戸空港、`RJOS`徳島空港、`RJOT`高松空港、`RJOB`岡山空港、そして`RJOY`八尾空港が再現されています. 空域の上限はFL180です.
|
||||
|
||||
AIP Japan 2021/08/12 （国土交通省） (https://aisjapan.mlit.go.jp/) をもとに作成しています。 再現されているSID及びSTARは現実の運用と異なる場合があるかもしれませんが、基本的に日中の景気気象状態 (IMC) を再現しているつもりです。すべての航空機がRNAV対応としていて、RNAVの代わりがない場合を除き非RNAVのSID及びSTARは実装されていません。海岸のデータは[naturalearthdata.com](http://www.naturalearthdata.com)のを使っています。
|
||||
|
||||
STARはこのゲームの進入方式で再現されています。進入方式に従って飛行することをを許可できる飛行機は有効なポイントに向かっていなければなりません。友好のポイントにDCTの指示を出した後、ILSの指示の代わりにAPP指示を出せます。一つのポイントから複数の進入方式が始まる場合もあります。指示を確定する前にまたAPPのボタンをクリック/キーを押すと次の進入方式に変わります。選択している飛行機がすでに進入方式に従って飛行しているならば、いったんDCTでポイントに向かう指示を選択しなければ飛行方式の変更はできません。
|
||||
|
||||
KANSAI ACAの南部の直下にあるTOKUSHIMA ACA (徳島進入管制区)はゲームの仕様上、KANSAI ACAの一部として実装しています。`RJOS`発着便のみTOKUSHIMA ACA （`OS`の表示がある空域）に入れます。
|
||||
|
||||
ゲームの仕様上、快適に遊べるように本作ではKANSAI ACAの空域を`OHDAI`の周りに中部へ、または`ROKKO`と`WAKIT`の周りに北へ拡大しています。高知空港はゲームの仕様上実装するのは困難なため、省略されています. 高知県民には申し訳ございません。`RJOO`/`RJBB`発着の`RJOK`便もゲームの仕様上再現できません。
|
||||
|
||||
## 登場する空港
|
||||
|
||||
### `RJBB` 関西国際空港
|
||||
|
||||
＊未翻訳
|
||||
The main airport of this airspace, Kansai handles both domestic and international traffic to the Kansai region (Osaka, Kobe, Kyoto, Nara, etc). Arrivals/departures will fly over RJBE Kobe to the north, and care should taken here to maintain separation of aircraft.
|
||||
|
||||
There is custom traffic for `RJBB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Many fixes visible on the map have a defined hold including some key fixes along the STARs.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`SAEKI`) -> `ALISA` (northwest from Korea/northern China and northeast from NE Japan, Europe)
|
||||
- (`RANDY`) -> `BERTH` (west from Fukuoka, western Japan, China)
|
||||
- (`KARIN`) -> `BECKY` (southwest from southwestern Japan, Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- (`EVERT`) -> `CANDY` (southwest from Philippines, south from Indonesia/Oceania, east from Nagoya/PACOTS)
|
||||
- (`KOHWA`) -> `SINGU` -> `DANDE` (east from RJTT Tokyo, RJAA Narita, RJSS Sendai, RJSF Fukushima)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KEC` (east for `RJAA` Narita, PACOTS)
|
||||
- `SHTLE` (east for `RJTT` Tokyo)
|
||||
- `UENOH` (northeast to Tohoku, southeast Hokkaido)
|
||||
- `SIGAK` (northeast to northwest Hokkaido, east NA, Europe)
|
||||
- `YME` (northeast to northeastern China)
|
||||
- `SOUJA` (northwest to Korea, northern China, Europe)
|
||||
- `WASYU` (west to western Japan/Jeju)
|
||||
- `HABAR` (west to China)
|
||||
- `POPPY` (southwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 06R/24L (RWY A)
|
||||
- 06L/24R (RWY B)
|
||||
|
||||
Note that simultaneous parallel independent approaches do not appear to be in use at RJBB. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation.
|
||||
|
||||
The preferred runway is generally RWY A as the main terminal 1 is much closer to RWY A. LCC carriers operating from terminal 2 would have a shorter taxi from RWY B.
|
||||
|
||||
STARs are available from `ALISA`, `BERTH`, `BECKY`, `CANDY`, `DANDE`, and approach modes can be activated from those fixes as well as intermediate fixes on the STARs, as well as fixes on airways joining to the STARs.
|
||||
|
||||
There are two landing configurations:
|
||||
|
||||
- Landing/departing RWY 06L/06R
|
||||
|
||||
This is the preferred configuration for RJBB.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `ALLAN` and `BERRY`, and approaches from GATES are available from `JANET` and `JENNY`.
|
||||
|
||||
Use care not to descend arrivals into Tokushima ACA. Cross TANTA (from ALISA), NALTO (from BERTH), EVIAN, DATIS, JOLLY +6000 (at or above 6000).
|
||||
|
||||
Departures will be climbing over `RJBE` departures from 09, use care to maintain separation. Departures may also join paths after diverging initially especially after `MAIKO`, and may conflict with departures from `RJOO` and `RJBE` northwest of MAIKO.
|
||||
|
||||
The published hold for missed approaches is `LILAC` +3000 for 06L, `AKASI` +4000 (via MAIKO) for 06R.
|
||||
|
||||
- Landing/departing RWY 24L/24R
|
||||
|
||||
This is the south wind configuration for RJBB.
|
||||
|
||||
Vectors onto the localizer should NOT be used. Approaches are available from `MAYAH` (24L), or `AMBER` (24L) and `BEIGE` (24R). Arrivals can be vectored over the sea west of Awaji Island if needed on top of `RJBE` arrivals.
|
||||
|
||||
Use care not to descend arrivals into the `RJBE` PCA. Cross `JOLLY` (from `DANDE`) +8000, `AWAJI` +7000, `MAYAH` 4000 (**at** 4000). Aircraft should descend as per the approach after MAYAH in order to main separation from `RJBE` traffic. Note that due to the lack of circle to land approaches in Endless ATC, `RJBE` 27 arrivals will fly a long downwind at \~1300 and may conflict with `RJBB` 24 arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures to the west will be climbing through arrivals descending to 4000 from `AWAJI` to `LILAC` to `MAYAH` and over `RJBE departures`. Departures over `DAISY` should cross `DAISY` +6000 and JULIA +8000. Departures over HELEN should cross `HELEN` +8000. Due care will need to be taken to maintain separation. Recommend descending to arrivals to 4000 after `AWAJI`, and expediting climb of departures from 24R. Departures to the west may also conflict with `RJBE` departures and `RJOO` departures to the west.
|
||||
|
||||
Departures to the south may conflict with arrivals from DANDE and the south/southwest. Use caution.
|
||||
|
||||
### `RJOO` 大阪国際空港(伊丹)
|
||||
|
||||
＊未翻訳
|
||||
An airport near the heart of Osaka, only domestic traffic is handled aside from the odd state aircraft. Mountains surround the airport to the north, west, and east.
|
||||
|
||||
There is custom traffic for `RJOO`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `ROKKO` (northwest from northwestern Japan, northeast from northeastern Japan)
|
||||
- `KODAI` (east from eastern Japan)
|
||||
- `KAZRA` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `JANGO` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `MUGIE` -> `HONMA` -> `KAINA` -> `IZUMI` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `MINAC` (northeast to Tohoku, Hokkaido)
|
||||
- `TOZAN` (northwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `KRE` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 14R/32L
|
||||
- 14L/32R
|
||||
|
||||
Larger aircraft land 14R/32L, as 14L/32R is generally only suitable for aircraft A320/B738 or smaller. It is not possible to model this in the game however.
|
||||
|
||||
Note that simultaneous parallel independent approaches are not used at `RJOO`. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation, however, this would not be used in reality as the runways are too close to each other.
|
||||
|
||||
Airspace to vector arrivals for sequencing is avaiable south of IKOMA/southeast of IZUMI/west of KODAI. Arrivals will fly over `RJOY` Yao, use care not to descend into YAO airspace. Use care to keep separation at `KAINA`, `ROKKO` and near `IKOMA`.
|
||||
|
||||
West departures may conflict with other aircraft on west departures. Use caution.
|
||||
|
||||
The missed approach hold is IZUMI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 32L/32R
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
Due to the mountains surrounding the airport, departures make a climbing left turn towards the south.
|
||||
|
||||
- Landing and departing 14L/14R
|
||||
|
||||
This runway configuration is only used when winds do not allow for use of the 32s. Arrivals circle west of the airport to land the 14s within the mountainous surroundings.
|
||||
|
||||
Due to the lack of circle to land approaches in Endless ATC, aircraft make long downwind to 14. Note that in real life these aircraft would have long flown into terrain, but this is the best we can do here.
|
||||
|
||||
Departures may conflict with arrivals circling to 14. Use caution.
|
||||
|
||||
West departures may conflict with other aircraft on west departures or arrivals to `RJBE`/`RJOT`/`RJOB`. Use caution.
|
||||
|
||||
### `RJBE` 神戸空港
|
||||
|
||||
＊未翻訳
|
||||
A smaller airport in Osaka Bay minutes from central Kobe. Located under to approach to the 24s at `RJBB`, typically in-out operations landing 09 and departing 27 are ideal. Unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJBE`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east from eastern Japan)
|
||||
- `WAKIT` (northeast from northeastern Japan)
|
||||
- `RANDY` -> `BERTH` (west from western Japan)
|
||||
- `KARIN` -> `BECKY` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `CUE` (east to eastern Japan)
|
||||
- `YME` (northeast to Tohoku/Hokkaido)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `POPPY` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
Aircraft arriving/departing `RJBE` in general will be operating under `RJBB` traffic. Ensure that arrivals are low enough before entering the bay, and that departures are clear of traffic above before issuing further climb.
|
||||
|
||||
Arrivals can be vectored over the sea west of Awaji Island.
|
||||
|
||||
Departures may conflict with other aircraft on west departures or arrivals to `RJOT`/`RJOB`. Use caution.
|
||||
|
||||
The missed approach hold is SIOJI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The preferred runway configuration. Departures make a climbing right turn to depart to the west remaining under `RJBB` departures and over `RJBE` arrivals.
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
This runway configuration is used when `RJBB` is landing 24, as Endless ATC requires departures to climb to a minimum of 3000 which would conflict with the `RJBB` 24 approach path. Arrivals circle to land 27, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 27, and may conflict with RJBB arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures will need to climb to 4000 or higher to clear arrivals at 3000.
|
||||
|
||||
### `RJOS` 徳島空港
|
||||
|
||||
＊未翻訳
|
||||
A joint-use civilian airport and JSDF-M base. Training operations with Beech King Airs are conducted by the JSDF-M from this base. Typically in-out operations landing 29 and departing 11 are ideal; unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJOS`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `JOSIN` (southeast to training areas?)
|
||||
- `SINGU` -> ... -> `DATIS` (east from Tokyo)
|
||||
- `KTE` -> `KULUL` -> `TSC` (west from Fukuoka)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KMANO` (east for Tokyo)
|
||||
- `KTE` -> `WASYU` (west to Fukuoka)
|
||||
- `TOSAR` (south to training areas?)
|
||||
|
||||
Departures may conflict with other aircraft on southwest departures and `RJBB` `CANDY` arrivals. Use caution.
|
||||
|
||||
The missed approach hold is TSC/DATIS +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 29
|
||||
|
||||
The preferred runway configuration. Departures make a climbing left turn to depart to the southeast.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 29. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOT` 高松空港
|
||||
|
||||
＊未翻訳
|
||||
An airport nestled up against mountains to the south serving Takamatsu.
|
||||
|
||||
There is custom traffic for `RJOT`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- (`TAKMA`) -> `KTE` (west/southwest)
|
||||
- (`YUBAR`) -> `OYE` -> `KTE` (northwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `WASYU` (west)
|
||||
- `TAROH` (north)
|
||||
|
||||
The missed approach hold is KTE +5000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 26
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 26. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOB` 岡山空港
|
||||
|
||||
＊未翻訳
|
||||
An airport situated in the mountains serving Okayama.
|
||||
|
||||
There is custom traffic for `RJOB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- `WAKIT` (northeast)
|
||||
- (`YUBAR`) -> `OYE`(north)
|
||||
- (`TAKMA`) -> `INOOK` (west/southwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `YME` (northeast)
|
||||
- `YUBAR` (north)
|
||||
- `WASYU` (west)
|
||||
|
||||
The missed approach hold is `OYE`/`BENES` +4000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 07
|
||||
|
||||
The preferred runway configuration for arrivals from the west. A RNAV AR approach utilizing RF legs to circle to 07 from the east is available in reality but the final leg is too short to be reproducible in Endless ATC. Therefore, east arrivals fly the ILS from OYE.
|
||||
|
||||
- Landing and departing 25
|
||||
|
||||
The preferred runway configuration for arrivals from the east. The straight-in to 25 is an RNAV approach as there is no ILS for 25.
|
||||
|
||||
### `RJOY` 八尾空港
|
||||
|
||||
＊未翻訳
|
||||
A small airport near Osaka that acts as a general aviation gateway.
|
||||
|
||||
There is custom traffic for `RJOY`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`MIDER`) -> `ITE` (east)
|
||||
- `ROKKO` (north)
|
||||
- (`YUBAR`) -> `OYE`(northwest)
|
||||
- (`KAIFU` -> `IZARI`) -> `MIKAN` (west/southwest)
|
||||
- (`NORAN`) -> `IZUMI` (southeast)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KCC` via `ASUKA` (east)
|
||||
- `KRE` via `IZUMI`, `ITE`, `OLIVE` (southwest)
|
||||
- `YME` via `IZUMI` (north)
|
||||
- `YUBAR` via `IZUMI` (northwest)
|
||||
- `WASYU` via `IZUMI` (west)
|
||||
|
||||
The missed approach hold is `IZUMI` +4200.
|
||||
|
||||
The only instrument approaches available are a VORDME or VOR circling approach from `IZUMI`. The VORDME approach is implemented with circling to all runways. Runway 13/31 is not enabled at this time, but can be easily enabled by editing [configurations] as the other relevant data is all there.
|
||||
|
||||
There is a very high potential for conflicts to the west of the airport. The airport and the VORDME approach sit under the approach path for `RJOO` traffic via `IZUMI`, so you effectively have a ceiling of 5000 to work with when there is traffic overhead. Alternatively, you can vector `RJOO` arrivals to the south to clear the airspace overhead.
|
||||
|
||||
Aircraft inbound to `IZUMI` via V55 from `ITE` will need to stay above `RJOO` departures and `RJBB` arrivals, while staying below `RJBB` `NANKO` departures, `RJOO` arrivals via `IZUMI`, and `RJOY` `ASUKA` departures. Aircraft departing via `IZUMI` (V55) `ITE` will also need to separated from opposite direction inbound traffic. Any aircraft going missed will also need to be separated from other `RJOY` arrivals, and in the case of landing 09, from aircraft inbound the `RJOO` 32s.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
The calm wind configuration. Use care for `ASUKA` departures; keep them separated from arrivals inbound `IZUMI` from `ITE`, and climb them above aircraft on final for `RJOO`.
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The reverse configuration. Use care for `ASUKA` departures to keep them separated from arrivals inbound `IZUMI` from `ITE`.
|
||||
|
||||
## 既知の問題点
|
||||
|
||||
- 旋回進入...............実装できていますが、かなりの余裕のあるベースターンとファイナルアプローチじゃないとミスアプローチのなるので結構広い旋回進入となっています。
|
||||
|
||||
## 変更履歴
|
||||
|
||||
* 3.0.0 - 2021/05/24
|
||||
- ソースをリライト
|
||||
- 現実にはない高度制限を削除
|
||||
- 到着機が高い速度と高度で`OHDAI`に出現するので`KODAI`にFL130/250kt制限を設定
|
||||
- 旋回侵入を一新
|
||||
- `RJOO` 14s
|
||||
- `UMEDA`でleft break
|
||||
- `RJOT` 08
|
||||
- `RJOS` 11
|
||||
- `RJBE` 27
|
||||
- およそ5DMEでright break
|
||||
- 27 到着機はダウンウィンドに合流するまで高度2500以上を維持します
|
||||
- ダウンウィンドで1500に降下して、直上の高度2600に降下する`RJBB`到着機からのセパレーションを維持します
|
||||
- ベースターンで高度2600以下に降下し始める`RJBB`到着機とのセパレーションを失わないようになりました
|
||||
- 27出発機は27到着木の下の高度1500ですれ違って`MAIKO`へ向かえるようになりました
|
||||
- o到着機までの距離に余裕がある場合、まず高度5000に上昇して到着機の上を`MAIKO`に向かうことも可能
|
||||
- `RJBB` ILS Y 進入を実装
|
||||
- `RJOO` 到着機の `MIRIO`, `JANGO` 出現ポイントを修正
|
||||
- `RJOO` RNAV 32L 進入を実装
|
||||
- 使用滑走路の組み合わせを一つ追加
|
||||
- `RJOO`出発経路を大幅に修正
|
||||
- 32Rから`ASUKA`へ向かう出発機は離陸後右に旋回しないように修正
|
||||
- `ITE` ラジアルによる出発経路が磁気偏角を配慮していなかったことを修正
|
||||
- `FOSTA` TRANSITIONを実装
|
||||
- `RJBB`出発経路を大幅に修正
|
||||
- Fly-overポイントを通過してから旋回するように修正
|
||||
- 24Lから`KNE`へ向かう出発機が離陸後左に旋回しないように修正
|
||||
- 制限空域(特別管制区など)の形を改良
|
||||
- `CUE` 大津VORDMEを廃止
|
||||
- 代わりに`MIDER`を設定
|
||||
- `RJOO` OTSU FIVE DEPARTUREとKOMATSU TRANSITIONを廃止
|
||||
- `RJOO` PANAS ONE DEPARTUREとKOMAZ TRANSITIONを設定
|
||||
- `RJBE` OTSU TRANSITIONを廃止
|
||||
- `RJBE` MIDER TRANSITIONを設定
|
||||
- `RJOY` 八尾空港を実装
|
||||
- 09-27滑走路だけ実装
|
||||
- これに伴い小型機を大量実装
|
||||
* 3.1.0 - 2021/07/02
|
||||
- ハンドオフ先のコールサイン及び周波数を実装
|
||||
# `RJBB` 進入管制区 3.1.0
|
||||
|
||||
＊作者は日本人ではありません。以下の文章には間違っている日本語、または間違っている情報が含まれている場合があります。ご了承いただければ幸いです。
|
||||
|
||||
KANSAI ACA(関西進入管制区)を[Endless ATC](https://steamcommunity.com/app/666610)に追加するMODです。`RJBB`関西国際空港、`RJOO`大阪国際空港(伊丹)、`RJBB`神戸空港、`RJOS`徳島空港、`RJOT`高松空港、`RJOB`岡山空港、そして`RJOY`八尾空港が再現されています. 空域の上限はFL180です.
|
||||
|
||||
AIP Japan 2021/08/12 （国土交通省） (https://aisjapan.mlit.go.jp/) をもとに作成しています。 再現されているSID及びSTARは現実の運用と異なる場合があるかもしれませんが、基本的に日中の景気気象状態 (IMC) を再現しているつもりです。すべての航空機がRNAV対応としていて、RNAVの代わりがない場合を除き非RNAVのSID及びSTARは実装されていません。海岸のデータは[naturalearthdata.com](http://www.naturalearthdata.com)のを使っています。
|
||||
|
||||
STARはこのゲームの進入方式で再現されています。進入方式に従って飛行することをを許可できる飛行機は有効なポイントに向かっていなければなりません。友好のポイントにDCTの指示を出した後、ILSの指示の代わりにAPP指示を出せます。一つのポイントから複数の進入方式が始まる場合もあります。指示を確定する前にまたAPPのボタンをクリック/キーを押すと次の進入方式に変わります。選択している飛行機がすでに進入方式に従って飛行しているならば、いったんDCTでポイントに向かう指示を選択しなければ飛行方式の変更はできません。
|
||||
|
||||
KANSAI ACAの南部の直下にあるTOKUSHIMA ACA (徳島進入管制区)はゲームの仕様上、KANSAI ACAの一部として実装しています。`RJOS`発着便のみTOKUSHIMA ACA （`OS`の表示がある空域）に入れます。
|
||||
|
||||
ゲームの仕様上、快適に遊べるように本作ではKANSAI ACAの空域を`OHDAI`の周りに中部へ、または`ROKKO`と`WAKIT`の周りに北へ拡大しています。高知空港はゲームの仕様上実装するのは困難なため、省略されています. 高知県民には申し訳ございません。`RJOO`/`RJBB`発着の`RJOK`便もゲームの仕様上再現できません。
|
||||
|
||||
## 登場する空港
|
||||
|
||||
### `RJBB` 関西国際空港
|
||||
|
||||
＊未翻訳
|
||||
The main airport of this airspace, Kansai handles both domestic and international traffic to the Kansai region (Osaka, Kobe, Kyoto, Nara, etc). Arrivals/departures will fly over RJBE Kobe to the north, and care should taken here to maintain separation of aircraft.
|
||||
|
||||
There is custom traffic for `RJBB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Many fixes visible on the map have a defined hold including some key fixes along the STARs.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`SAEKI`) -> `ALISA` (northwest from Korea/northern China and northeast from NE Japan, Europe)
|
||||
- (`RANDY`) -> `BERTH` (west from Fukuoka, western Japan, China)
|
||||
- (`KARIN`) -> `BECKY` (southwest from southwestern Japan, Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- (`EVERT`) -> `CANDY` (southwest from Philippines, south from Indonesia/Oceania, east from Nagoya/PACOTS)
|
||||
- (`KOHWA`) -> `SINGU` -> `DANDE` (east from RJTT Tokyo, RJAA Narita, RJSS Sendai, RJSF Fukushima)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KEC` (east for `RJAA` Narita, PACOTS)
|
||||
- `SHTLE` (east for `RJTT` Tokyo)
|
||||
- `UENOH` (northeast to Tohoku, southeast Hokkaido)
|
||||
- `SIGAK` (northeast to northwest Hokkaido, east NA, Europe)
|
||||
- `YME` (northeast to northeastern China)
|
||||
- `SOUJA` (northwest to Korea, northern China, Europe)
|
||||
- `WASYU` (west to western Japan/Jeju)
|
||||
- `HABAR` (west to China)
|
||||
- `POPPY` (southwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 06R/24L (RWY A)
|
||||
- 06L/24R (RWY B)
|
||||
|
||||
Note that simultaneous parallel independent approaches do not appear to be in use at RJBB. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation.
|
||||
|
||||
The preferred runway is generally RWY A as the main terminal 1 is much closer to RWY A. LCC carriers operating from terminal 2 would have a shorter taxi from RWY B.
|
||||
|
||||
STARs are available from `ALISA`, `BERTH`, `BECKY`, `CANDY`, `DANDE`, and approach modes can be activated from those fixes as well as intermediate fixes on the STARs, as well as fixes on airways joining to the STARs.
|
||||
|
||||
There are two landing configurations:
|
||||
|
||||
- Landing/departing RWY 06L/06R
|
||||
|
||||
This is the preferred configuration for RJBB.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `ALLAN` and `BERRY`, and approaches from GATES are available from `JANET` and `JENNY`.
|
||||
|
||||
Use care not to descend arrivals into Tokushima ACA. Cross TANTA (from ALISA), NALTO (from BERTH), EVIAN, DATIS, JOLLY +6000 (at or above 6000).
|
||||
|
||||
Departures will be climbing over `RJBE` departures from 09, use care to maintain separation. Departures may also join paths after diverging initially especially after `MAIKO`, and may conflict with departures from `RJOO` and `RJBE` northwest of MAIKO.
|
||||
|
||||
The published hold for missed approaches is `LILAC` +3000 for 06L, `AKASI` +4000 (via MAIKO) for 06R.
|
||||
|
||||
- Landing/departing RWY 24L/24R
|
||||
|
||||
This is the south wind configuration for RJBB.
|
||||
|
||||
Vectors onto the localizer should NOT be used. Approaches are available from `MAYAH` (24L), or `AMBER` (24L) and `BEIGE` (24R). Arrivals can be vectored over the sea west of Awaji Island if needed on top of `RJBE` arrivals.
|
||||
|
||||
Use care not to descend arrivals into the `RJBE` PCA. Cross `JOLLY` (from `DANDE`) +8000, `AWAJI` +7000, `MAYAH` 4000 (**at** 4000). Aircraft should descend as per the approach after MAYAH in order to main separation from `RJBE` traffic. Note that due to the lack of circle to land approaches in Endless ATC, `RJBE` 27 arrivals will fly a long downwind at \~1300 and may conflict with `RJBB` 24 arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures to the west will be climbing through arrivals descending to 4000 from `AWAJI` to `LILAC` to `MAYAH` and over `RJBE departures`. Departures over `DAISY` should cross `DAISY` +6000 and JULIA +8000. Departures over HELEN should cross `HELEN` +8000. Due care will need to be taken to maintain separation. Recommend descending to arrivals to 4000 after `AWAJI`, and expediting climb of departures from 24R. Departures to the west may also conflict with `RJBE` departures and `RJOO` departures to the west.
|
||||
|
||||
Departures to the south may conflict with arrivals from DANDE and the south/southwest. Use caution.
|
||||
|
||||
### `RJOO` 大阪国際空港(伊丹)
|
||||
|
||||
＊未翻訳
|
||||
An airport near the heart of Osaka, only domestic traffic is handled aside from the odd state aircraft. Mountains surround the airport to the north, west, and east.
|
||||
|
||||
There is custom traffic for `RJOO`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `ROKKO` (northwest from northwestern Japan, northeast from northeastern Japan)
|
||||
- `KODAI` (east from eastern Japan)
|
||||
- `KAZRA` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `JANGO` -> `MIRIO` -> `KAINA` -> `IZUMI` (west from western Japan)
|
||||
- `MUGIE` -> `HONMA` -> `KAINA` -> `IZUMI` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `MINAC` (northeast to Tohoku, Hokkaido)
|
||||
- `TOZAN` (northwest to Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `KRE` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 14R/32L
|
||||
- 14L/32R
|
||||
|
||||
Larger aircraft land 14R/32L, as 14L/32R is generally only suitable for aircraft A320/B738 or smaller. It is not possible to model this in the game however.
|
||||
|
||||
Note that simultaneous parallel independent approaches are not used at `RJOO`. It is possible in the game, but the approaches are not built with this in mind. Of course, you can still do simultaneous parallel dependent approaches with staggered sequencing, which can help with dealing with wake turbulence separation, however, this would not be used in reality as the runways are too close to each other.
|
||||
|
||||
Airspace to vector arrivals for sequencing is avaiable south of IKOMA/southeast of IZUMI/west of KODAI. Arrivals will fly over `RJOY` Yao, use care not to descend into YAO airspace. Use care to keep separation at `KAINA`, `ROKKO` and near `IKOMA`.
|
||||
|
||||
West departures may conflict with other aircraft on west departures. Use caution.
|
||||
|
||||
The missed approach hold is IZUMI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 32L/32R
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
Due to the mountains surrounding the airport, departures make a climbing left turn towards the south.
|
||||
|
||||
- Landing and departing 14L/14R
|
||||
|
||||
This runway configuration is only used when winds do not allow for use of the 32s. Arrivals circle west of the airport to land the 14s within the mountainous surroundings.
|
||||
|
||||
Due to the lack of circle to land approaches in Endless ATC, aircraft make long downwind to 14. Note that in real life these aircraft would have long flown into terrain, but this is the best we can do here.
|
||||
|
||||
Departures may conflict with arrivals circling to 14. Use caution.
|
||||
|
||||
West departures may conflict with other aircraft on west departures or arrivals to `RJBE`/`RJOT`/`RJOB`. Use caution.
|
||||
|
||||
### `RJBE` 神戸空港
|
||||
|
||||
＊未翻訳
|
||||
A smaller airport in Osaka Bay minutes from central Kobe. Located under to approach to the 24s at `RJBB`, typically in-out operations landing 09 and departing 27 are ideal. Unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJBE`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east from eastern Japan)
|
||||
- `WAKIT` (northeast from northeastern Japan)
|
||||
- `RANDY` -> `BERTH` (west from western Japan)
|
||||
- `KARIN` -> `BECKY` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `CUE` (east to eastern Japan)
|
||||
- `YME` (northeast to Tohoku/Hokkaido)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
- `POPPY` (southwest to southwestern Japan, south Kyushu)
|
||||
|
||||
Aircraft arriving/departing `RJBE` in general will be operating under `RJBB` traffic. Ensure that arrivals are low enough before entering the bay, and that departures are clear of traffic above before issuing further climb.
|
||||
|
||||
Arrivals can be vectored over the sea west of Awaji Island.
|
||||
|
||||
Departures may conflict with other aircraft on west departures or arrivals to `RJOT`/`RJOB`. Use caution.
|
||||
|
||||
The missed approach hold is SIOJI +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The preferred runway configuration. Departures make a climbing right turn to depart to the west remaining under `RJBB` departures and over `RJBE` arrivals.
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
This runway configuration is used when `RJBB` is landing 24, as Endless ATC requires departures to climb to a minimum of 3000 which would conflict with the `RJBB` 24 approach path. Arrivals circle to land 27, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 27, and may conflict with RJBB arrivals leaving 2600. Having the `RJBE` arrival fly slightly ahead of an overhead `RJBB` arrival should allow for separation to be maintained.
|
||||
|
||||
Departures will need to climb to 4000 or higher to clear arrivals at 3000.
|
||||
|
||||
### `RJOS` 徳島空港
|
||||
|
||||
＊未翻訳
|
||||
A joint-use civilian airport and JSDF-M base. Training operations with Beech King Airs are conducted by the JSDF-M from this base. Typically in-out operations landing 29 and departing 11 are ideal; unfortunately, this is not possible in Endless ATC.
|
||||
|
||||
There is custom traffic for `RJOS`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `JOSIN` (southeast to training areas?)
|
||||
- `SINGU` -> ... -> `DATIS` (east from Tokyo)
|
||||
- `KTE` -> `KULUL` -> `TSC` (west from Fukuoka)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KMANO` (east for Tokyo)
|
||||
- `KTE` -> `WASYU` (west to Fukuoka)
|
||||
- `TOSAR` (south to training areas?)
|
||||
|
||||
Departures may conflict with other aircraft on southwest departures and `RJBB` `CANDY` arrivals. Use caution.
|
||||
|
||||
The missed approach hold is TSC/DATIS +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 29
|
||||
|
||||
The preferred runway configuration. Departures make a climbing left turn to depart to the southeast.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 29. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOT` 高松空港
|
||||
|
||||
＊未翻訳
|
||||
An airport nestled up against mountains to the south serving Takamatsu.
|
||||
|
||||
There is custom traffic for `RJOT`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- (`TAKMA`) -> `KTE` (west/southwest)
|
||||
- (`YUBAR`) -> `OYE` -> `KTE` (northwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `WASYU` (west)
|
||||
- `TAROH` (north)
|
||||
|
||||
The missed approach hold is KTE +5000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 26
|
||||
|
||||
The preferred runway configuration.
|
||||
|
||||
- Landing and departing 11
|
||||
|
||||
This runway configuration is used when winds do not allow straight-in 26. Arrivals circle to land 11, however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 11.
|
||||
|
||||
### `RJOB` 岡山空港
|
||||
|
||||
＊未翻訳
|
||||
An airport situated in the mountains serving Okayama.
|
||||
|
||||
There is custom traffic for `RJOB`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `GINJI` (east)
|
||||
- `WAKIT` (northeast)
|
||||
- (`YUBAR`) -> `OYE`(north)
|
||||
- (`TAKMA`) -> `INOOK` (west/southwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `YME` (northeast)
|
||||
- `YUBAR` (north)
|
||||
- `WASYU` (west)
|
||||
|
||||
The missed approach hold is `OYE`/`BENES` +4000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 07
|
||||
|
||||
The preferred runway configuration for arrivals from the west. A RNAV AR approach utilizing RF legs to circle to 07 from the east is available in reality but the final leg is too short to be reproducible in Endless ATC. Therefore, east arrivals fly the ILS from OYE.
|
||||
|
||||
- Landing and departing 25
|
||||
|
||||
The preferred runway configuration for arrivals from the east. The straight-in to 25 is an RNAV approach as there is no ILS for 25.
|
||||
|
||||
### `RJOY` 八尾空港
|
||||
|
||||
＊未翻訳
|
||||
A small airport near Osaka that acts as a general aviation gateway.
|
||||
|
||||
There is custom traffic for `RJOY`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- (`MIDER`) -> `ITE` (east)
|
||||
- `ROKKO` (north)
|
||||
- (`YUBAR`) -> `OYE`(northwest)
|
||||
- (`KAIFU` -> `IZARI`) -> `MIKAN` (west/southwest)
|
||||
- (`NORAN`) -> `IZUMI` (southeast)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KCC` via `ASUKA` (east)
|
||||
- `KRE` via `IZUMI`, `ITE`, `OLIVE` (southwest)
|
||||
- `YME` via `IZUMI` (north)
|
||||
- `YUBAR` via `IZUMI` (northwest)
|
||||
- `WASYU` via `IZUMI` (west)
|
||||
|
||||
The missed approach hold is `IZUMI` +4200.
|
||||
|
||||
The only instrument approaches available are a VORDME or VOR circling approach from `IZUMI`. The VORDME approach is implemented with circling to all runways. Runway 13/31 is not enabled at this time, but can be easily enabled by editing [configurations] as the other relevant data is all there.
|
||||
|
||||
There is a very high potential for conflicts to the west of the airport. The airport and the VORDME approach sit under the approach path for `RJOO` traffic via `IZUMI`, so you effectively have a ceiling of 5000 to work with when there is traffic overhead. Alternatively, you can vector `RJOO` arrivals to the south to clear the airspace overhead.
|
||||
|
||||
Aircraft inbound to `IZUMI` via V55 from `ITE` will need to stay above `RJOO` departures and `RJBB` arrivals, while staying below `RJBB` `NANKO` departures, `RJOO` arrivals via `IZUMI`, and `RJOY` `ASUKA` departures. Aircraft departing via `IZUMI` (V55) `ITE` will also need to separated from opposite direction inbound traffic. Any aircraft going missed will also need to be separated from other `RJOY` arrivals, and in the case of landing 09, from aircraft inbound the `RJOO` 32s.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 27
|
||||
|
||||
The calm wind configuration. Use care for `ASUKA` departures; keep them separated from arrivals inbound `IZUMI` from `ITE`, and climb them above aircraft on final for `RJOO`.
|
||||
|
||||
- Landing and departing 09
|
||||
|
||||
The reverse configuration. Use care for `ASUKA` departures to keep them separated from arrivals inbound `IZUMI` from `ITE`.
|
||||
|
||||
## 既知の問題点
|
||||
|
||||
- 旋回進入...............実装できていますが、かなりの余裕のあるベースターンとファイナルアプローチじゃないとミスアプローチのなるので結構広い旋回進入となっています。
|
||||
|
||||
## 変更履歴
|
||||
|
||||
* 3.0.0 - 2021/05/24
|
||||
- ソースをリライト
|
||||
- 現実にはない高度制限を削除
|
||||
- 到着機が高い速度と高度で`OHDAI`に出現するので`KODAI`にFL130/250kt制限を設定
|
||||
- 旋回侵入を一新
|
||||
- `RJOO` 14s
|
||||
- `UMEDA`でleft break
|
||||
- `RJOT` 08
|
||||
- `RJOS` 11
|
||||
- `RJBE` 27
|
||||
- およそ5DMEでright break
|
||||
- 27 到着機はダウンウィンドに合流するまで高度2500以上を維持します
|
||||
- ダウンウィンドで1500に降下して、直上の高度2600に降下する`RJBB`到着機からのセパレーションを維持します
|
||||
- ベースターンで高度2600以下に降下し始める`RJBB`到着機とのセパレーションを失わないようになりました
|
||||
- 27出発機は27到着木の下の高度1500ですれ違って`MAIKO`へ向かえるようになりました
|
||||
- o到着機までの距離に余裕がある場合、まず高度5000に上昇して到着機の上を`MAIKO`に向かうことも可能
|
||||
- `RJBB` ILS Y 進入を実装
|
||||
- `RJOO` 到着機の `MIRIO`, `JANGO` 出現ポイントを修正
|
||||
- `RJOO` RNAV 32L 進入を実装
|
||||
- 使用滑走路の組み合わせを一つ追加
|
||||
- `RJOO`出発経路を大幅に修正
|
||||
- 32Rから`ASUKA`へ向かう出発機は離陸後右に旋回しないように修正
|
||||
- `ITE` ラジアルによる出発経路が磁気偏角を配慮していなかったことを修正
|
||||
- `FOSTA` TRANSITIONを実装
|
||||
- `RJBB`出発経路を大幅に修正
|
||||
- Fly-overポイントを通過してから旋回するように修正
|
||||
- 24Lから`KNE`へ向かう出発機が離陸後左に旋回しないように修正
|
||||
- 制限空域(特別管制区など)の形を改良
|
||||
- `CUE` 大津VORDMEを廃止
|
||||
- 代わりに`MIDER`を設定
|
||||
- `RJOO` OTSU FIVE DEPARTUREとKOMATSU TRANSITIONを廃止
|
||||
- `RJOO` PANAS ONE DEPARTUREとKOMAZ TRANSITIONを設定
|
||||
- `RJBE` OTSU TRANSITIONを廃止
|
||||
- `RJBE` MIDER TRANSITIONを設定
|
||||
- `RJOY` 八尾空港を実装
|
||||
- 09-27滑走路だけ実装
|
||||
- これに伴い小型機を大量実装
|
||||
* 3.1.0 - 2021/07/02
|
||||
- ハンドオフ先のコールサイン及び周波数を実装
|
||||
- 徳島の発音を改良
|
||||
@@ -1,23 +1,23 @@
|
||||
[expand.callsigns]
|
||||
|
||||
ckstr = check star
|
||||
rch = reach
|
||||
cnv7 = convoy 7
|
||||
cnv3 = convoy 3
|
||||
madfox = mad fox
|
||||
pswrd = password
|
||||
brgham = brigham
|
||||
vampr = vampire
|
||||
tmboy = tomboy
|
||||
neptn = neptune
|
||||
cygns = cygnus
|
||||
|
||||
ana = all neep pawn
|
||||
#sfj = stah-foo-lai-yaa
|
||||
#jal = juh-pawn eh are
|
||||
#snj = nyuh sky
|
||||
#jta = j oh-shun
|
||||
#ado = eh are do
|
||||
#jjp = orenji lie-nuh
|
||||
#apj = eh are peach
|
||||
[expand.callsigns]
|
||||
|
||||
ckstr = check star
|
||||
rch = reach
|
||||
cnv7 = convoy 7
|
||||
cnv3 = convoy 3
|
||||
madfox = mad fox
|
||||
pswrd = password
|
||||
brgham = brigham
|
||||
vampr = vampire
|
||||
tmboy = tomboy
|
||||
neptn = neptune
|
||||
cygns = cygnus
|
||||
|
||||
ana = all neep pawn
|
||||
#sfj = stah-foo-lai-yaa
|
||||
#jal = juh-pawn eh are
|
||||
#snj = nyuh sky
|
||||
#jta = j oh-shun
|
||||
#ado = eh are do
|
||||
#jjp = orenji lie-nuh
|
||||
#apj = eh are peach
|
||||
#rsd = state aero
|
||||
@@ -0,0 +1,23 @@
|
||||
[expand.callsigns]
|
||||
|
||||
ckstr = check star
|
||||
rch = reach
|
||||
cnv7 = convoy 7
|
||||
cnv3 = convoy 3
|
||||
madfox = mad fox
|
||||
pswrd = password
|
||||
brgham = brigham
|
||||
vampr = vampire
|
||||
tmboy = tomboy
|
||||
neptn = neptune
|
||||
cygns = cygnus
|
||||
|
||||
ana = all neep pawn
|
||||
#sfj = stah-foo-lai-yaa
|
||||
#jal = juh-pawn eh are
|
||||
#snj = nyuh sky
|
||||
#jta = j oh-shun
|
||||
#ado = eh are do
|
||||
#jjp = orenji lie-nuh
|
||||
#apj = eh are peach
|
||||
#rsd = state aero
|
||||
@@ -0,0 +1,23 @@
|
||||
[expand.callsigns]
|
||||
|
||||
ckstr = check star
|
||||
rch = reach
|
||||
cnv7 = convoy 7
|
||||
cnv3 = convoy 3
|
||||
madfox = mad fox
|
||||
pswrd = password
|
||||
brgham = brigham
|
||||
vampr = vampire
|
||||
tmboy = tomboy
|
||||
neptn = neptune
|
||||
cygns = cygnus
|
||||
|
||||
ana = all neep pawn
|
||||
#sfj = stah-foo-lai-yaa
|
||||
#jal = juh-pawn eh are
|
||||
#snj = nyuh sky
|
||||
#jta = j oh-shun
|
||||
#ado = eh are do
|
||||
#jjp = orenji lie-nuh
|
||||
#apj = eh are peach
|
||||
#rsd = state aero
|
||||
@@ -1,124 +1,124 @@
|
||||
# `RKSI` Seoul TMA 1.0.0
|
||||
|
||||
This is an implementation of the Seoul TMA (Terminal Control Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `RKSI` Incheon Airport and `RKSS` Gimpo Airport. The airspace ceiling is FL185.
|
||||
|
||||
The Seoul TMA is a fairly cramped airspace, with restricted areas to the north over the border with the North Korea and close to Gimpo over the city of Seoul. To the south lies Osan Air Base and the Osan TMA that lies underneath the southern portion of the Seoul TMA.
|
||||
|
||||
Based upon AIP Republic of Korea 2021/06/16. All aircraft are assumed to be RNAV capable; no conventional NAVAID-based SIDs or STARs were implemented unless there is no RNAV procedure published. Coastline data from [naturalearthdata.com].
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Pressing the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
Endless ATC does not support altitude restrictions for departures, or floor restrictions for arrivals. However, procedures in the Seoul TMA often have such restrictions to ensure separation. Notable restrictions are noted in each airport's section below; following these restrictions should result in a better gameplay experience.
|
||||
|
||||
The Seoul TMA is extended to the west and to the south, as well as eastwards around airway G597 for gameplay purposes. `RKSM` Seoul Airbase is not implemented.
|
||||
|
||||
## Airports
|
||||
|
||||
### `RKSI` Incheon International Airport
|
||||
|
||||
The main international airport serving Seoul. This airport was built in the ocean west of Seoul by landfilling between two islands. Note an area north of Incheon which is reserved for IFR traffic and is used by certain arrival and departure procedures.
|
||||
|
||||
There is custom traffic for `RKSI`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Certain fixes visible on the map have a defined hold including some key fixes along the STARs.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `OLMEN` (south from Jeju, Taiwan, SE Asia, Shanghai and southern China)
|
||||
- `GUKDO` (southeast from Gimhae, Japan, Oceania, NA)
|
||||
- `REBIT` (west from northern/western China, Europe, Russia, ME etc)
|
||||
- `KARBU` (east from Yangyang, eastern Russia, or northern Japan and NA via CDR)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `BOPTA` (south for Jeju, Taiwan, SE Asia, Shanghai and southern China)
|
||||
- `OSPOT` (southeast for Gimhae, Kyushu, Oceania)
|
||||
- `BINIL` (west for northern/western China, Europe, Russia, ME etc)
|
||||
- `KARBU` (east for Yangyang, eastern Russia, Japan and NA)
|
||||
|
||||
There are four runways:
|
||||
|
||||
- 15L/33R (arrivals only)
|
||||
- 15R/33L (departures only)
|
||||
- 16L/34R (departures only)
|
||||
- 16R/34L (arrivals only)
|
||||
|
||||
STARs and approaches are made with simultaneous approaches in mind, and should maintain at least 1000 ft separation until GS intercept.
|
||||
|
||||
The preferred runway for cargo flights in 15L/33R due to a significantly shorter taxi distance.
|
||||
|
||||
There are two landing configurations:
|
||||
|
||||
- Landing 33R/34L, departing 33L/34R
|
||||
|
||||
This is the preferred configuration for `RKSI`.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `ENPIL` and `PAMBI`.
|
||||
|
||||
Use caution for arrivals via `REBIT`, the point merge to `PAMBI` is only 500ft above Osan TMA, and planes will descend into Osan TMA if cleared to approach 34L.
|
||||
|
||||
The published hold for missed approaches is `GC963` +4000-5000 for the 15s, `DH989` +3000-4000 for the 16s.
|
||||
|
||||
- Landing 15L/16R, departing 15R/16L
|
||||
|
||||
This is the south wind configuration for `RKSI`.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `MUNAN` and `BITIM`.
|
||||
|
||||
Use care to separate arrivals from departures. For arrivals via `SEL`, cross `SEL` +13000, `GC036` +9000, `GC026` +6000. The descent profile to meet -4500 at `GC020` generally requires -210kts by `SEL`. The game will start a descent before SEL that will break these restrictions without speed control, so it is recommended to issue speed 210kts upon leaving the point merge to `SEL`.
|
||||
|
||||
Departures will generally fly under arrivals. For `BINIL` departures, maintain -10000 until `HP100` (until clear of `OLMEN` arrivals). For `BOPTA` arrivals, maintain -13000 until `HD130` (until clear of `OLMEN` arrivals). For `EGOBA` arrivals, 10000 until `CK099` (over `R35`) and -11000 until `EGOBA` may be required depending on traffic from `KARBU`.
|
||||
|
||||
The published hold for missed approaches is `GE978` +4000-5000 for the 33s, `PY980` +3000-4000 for the 34s.
|
||||
|
||||
### `RKSS` Gimpo International Airport
|
||||
|
||||
The main domestic airport for Seoul, located closer to Seoul than Incheon. Limited international flights to key close Asian cities also fly in and out of Gimpo.
|
||||
|
||||
There is custom traffic for `RKSS`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `OLMEN` (south from Jeju etc, Taiwan, Shanghai)
|
||||
- `GUKDO` (southeast from Gimhae, Japan)
|
||||
- `REBIT` (west from Beijing)
|
||||
- `KARBU` (east from Yangyang etc)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `BOPTA` (south for Jeju etc, Taiwan, Shanghai)
|
||||
- `OSPOT` (southeast for Gimhae etc)
|
||||
- `BINIL` (west for northern/western China, Europe, Russia, ME etc)
|
||||
- `KARBU` (east for Yangyang, eastern Russia, Japan and NA)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 14R/32L (arrival only in south wind configuration)
|
||||
- 14L/32R (departure only in south wind configuration)
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 32L/32R
|
||||
|
||||
The preferred runway configuration. In real life, the departures and arrivals alternate between the 32s every 3 hours. In the game, two configurations are provided, one for departing 32L and arriving 32R, one for departing 32R and arriving 32L.
|
||||
|
||||
The missed approach hold is `CAVOI` +4000-6000.
|
||||
|
||||
- Landing and departing 14L/14R
|
||||
|
||||
This is the south wind configuration.
|
||||
|
||||
`REBIT` arrivals starting auto descent without speed control will descend into `RKSI` 15/16 arrivals. -250kts at `REBIT` is recommended to allow for a steeper descent profile to maintain separation.
|
||||
|
||||
Departures should cross `SEL` or `UP050` (the point immediately southwest of `SEL`) -6000. Departures via `NOPIK` should also cross `UP060` (the second fix west of `SEL`) and `UP059` (the third fix west of `SEL` that starts the due west legs) at 6000 if necessary to keep under `RKSI` arrivals. `KARBU` departures should also remain -9000 after passing `SEL` until `EGOBA`, and will climb to cruise under `KARBU` arrivals.
|
||||
|
||||
The missed approach hold is `DOKDO` +4000-5000.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- No mixed configurations...not sure how to implement the alternate SIDs/STARs at `RKSS` that are used during mixed ops...
|
||||
- Holds on intermediate STAR fixes may not work correctly, it seems to be a bug in the game.
|
||||
|
||||
## Changelog
|
||||
|
||||
# `RKSI` Seoul TMA 1.0.0
|
||||
|
||||
This is an implementation of the Seoul TMA (Terminal Control Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `RKSI` Incheon Airport and `RKSS` Gimpo Airport. The airspace ceiling is FL185.
|
||||
|
||||
The Seoul TMA is a fairly cramped airspace, with restricted areas to the north over the border with the North Korea and close to Gimpo over the city of Seoul. To the south lies Osan Air Base and the Osan TMA that lies underneath the southern portion of the Seoul TMA.
|
||||
|
||||
Based upon AIP Republic of Korea 2021/06/16. All aircraft are assumed to be RNAV capable; no conventional NAVAID-based SIDs or STARs were implemented unless there is no RNAV procedure published. Coastline data from [naturalearthdata.com].
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Pressing the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
Endless ATC does not support altitude restrictions for departures, or floor restrictions for arrivals. However, procedures in the Seoul TMA often have such restrictions to ensure separation. Notable restrictions are noted in each airport's section below; following these restrictions should result in a better gameplay experience.
|
||||
|
||||
The Seoul TMA is extended to the west and to the south, as well as eastwards around airway G597 for gameplay purposes. `RKSM` Seoul Airbase is not implemented.
|
||||
|
||||
## Airports
|
||||
|
||||
### `RKSI` Incheon International Airport
|
||||
|
||||
The main international airport serving Seoul. This airport was built in the ocean west of Seoul by landfilling between two islands. Note an area north of Incheon which is reserved for IFR traffic and is used by certain arrival and departure procedures.
|
||||
|
||||
There is custom traffic for `RKSI`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Certain fixes visible on the map have a defined hold including some key fixes along the STARs.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `OLMEN` (south from Jeju, Taiwan, SE Asia, Shanghai and southern China)
|
||||
- `GUKDO` (southeast from Gimhae, Japan, Oceania, NA)
|
||||
- `REBIT` (west from northern/western China, Europe, Russia, ME etc)
|
||||
- `KARBU` (east from Yangyang, eastern Russia, or northern Japan and NA via CDR)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `BOPTA` (south for Jeju, Taiwan, SE Asia, Shanghai and southern China)
|
||||
- `OSPOT` (southeast for Gimhae, Kyushu, Oceania)
|
||||
- `BINIL` (west for northern/western China, Europe, Russia, ME etc)
|
||||
- `KARBU` (east for Yangyang, eastern Russia, Japan and NA)
|
||||
|
||||
There are four runways:
|
||||
|
||||
- 15L/33R (arrivals only)
|
||||
- 15R/33L (departures only)
|
||||
- 16L/34R (departures only)
|
||||
- 16R/34L (arrivals only)
|
||||
|
||||
STARs and approaches are made with simultaneous approaches in mind, and should maintain at least 1000 ft separation until GS intercept.
|
||||
|
||||
The preferred runway for cargo flights in 15L/33R due to a significantly shorter taxi distance.
|
||||
|
||||
There are two landing configurations:
|
||||
|
||||
- Landing 33R/34L, departing 33L/34R
|
||||
|
||||
This is the preferred configuration for `RKSI`.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `ENPIL` and `PAMBI`.
|
||||
|
||||
Use caution for arrivals via `REBIT`, the point merge to `PAMBI` is only 500ft above Osan TMA, and planes will descend into Osan TMA if cleared to approach 34L.
|
||||
|
||||
The published hold for missed approaches is `GC963` +4000-5000 for the 15s, `DH989` +3000-4000 for the 16s.
|
||||
|
||||
- Landing 15L/16R, departing 15R/16L
|
||||
|
||||
This is the south wind configuration for `RKSI`.
|
||||
|
||||
Vectors can be used for sequencing, or direct to fix shortcuts can also be issued (or both). Approaches are available from `MUNAN` and `BITIM`.
|
||||
|
||||
Use care to separate arrivals from departures. For arrivals via `SEL`, cross `SEL` +13000, `GC036` +9000, `GC026` +6000. The descent profile to meet -4500 at `GC020` generally requires -210kts by `SEL`. The game will start a descent before SEL that will break these restrictions without speed control, so it is recommended to issue speed 210kts upon leaving the point merge to `SEL`.
|
||||
|
||||
Departures will generally fly under arrivals. For `BINIL` departures, maintain -10000 until `HP100` (until clear of `OLMEN` arrivals). For `BOPTA` arrivals, maintain -13000 until `HD130` (until clear of `OLMEN` arrivals). For `EGOBA` arrivals, 10000 until `CK099` (over `R35`) and -11000 until `EGOBA` may be required depending on traffic from `KARBU`.
|
||||
|
||||
The published hold for missed approaches is `GE978` +4000-5000 for the 33s, `PY980` +3000-4000 for the 34s.
|
||||
|
||||
### `RKSS` Gimpo International Airport
|
||||
|
||||
The main domestic airport for Seoul, located closer to Seoul than Incheon. Limited international flights to key close Asian cities also fly in and out of Gimpo.
|
||||
|
||||
There is custom traffic for `RKSS`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
|
||||
- `OLMEN` (south from Jeju etc, Taiwan, Shanghai)
|
||||
- `GUKDO` (southeast from Gimhae, Japan)
|
||||
- `REBIT` (west from Beijing)
|
||||
- `KARBU` (east from Yangyang etc)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `BOPTA` (south for Jeju etc, Taiwan, Shanghai)
|
||||
- `OSPOT` (southeast for Gimhae etc)
|
||||
- `BINIL` (west for northern/western China, Europe, Russia, ME etc)
|
||||
- `KARBU` (east for Yangyang, eastern Russia, Japan and NA)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 14R/32L (arrival only in south wind configuration)
|
||||
- 14L/32R (departure only in south wind configuration)
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 32L/32R
|
||||
|
||||
The preferred runway configuration. In real life, the departures and arrivals alternate between the 32s every 3 hours. In the game, two configurations are provided, one for departing 32L and arriving 32R, one for departing 32R and arriving 32L.
|
||||
|
||||
The missed approach hold is `CAVOI` +4000-6000.
|
||||
|
||||
- Landing and departing 14L/14R
|
||||
|
||||
This is the south wind configuration.
|
||||
|
||||
`REBIT` arrivals starting auto descent without speed control will descend into `RKSI` 15/16 arrivals. -250kts at `REBIT` is recommended to allow for a steeper descent profile to maintain separation.
|
||||
|
||||
Departures should cross `SEL` or `UP050` (the point immediately southwest of `SEL`) -6000. Departures via `NOPIK` should also cross `UP060` (the second fix west of `SEL`) and `UP059` (the third fix west of `SEL` that starts the due west legs) at 6000 if necessary to keep under `RKSI` arrivals. `KARBU` departures should also remain -9000 after passing `SEL` until `EGOBA`, and will climb to cruise under `KARBU` arrivals.
|
||||
|
||||
The missed approach hold is `DOKDO` +4000-5000.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- No mixed configurations...not sure how to implement the alternate SIDs/STARs at `RKSS` that are used during mixed ops...
|
||||
- Holds on intermediate STAR fixes may not work correctly, it seems to be a bug in the game.
|
||||
|
||||
## Changelog
|
||||
|
||||
* 1.0.0 - 2021/07/01 - Initial version.
|
||||
File diff suppressed because it is too large
Load Diff
@@ -1,177 +1,177 @@
|
||||
**DUE TO NATURE OF TRAFFIC AT THE `ROAH` AERODROME, THIS AIRPORT FILE HAS QUIRKS RELATED TO MILITARY AIRCRAFT TO/FROM `ROAH`.**
|
||||
|
||||
# `ROAH` ACA 1.0.0
|
||||
|
||||
This is an implementation of the Naha ACA (Approach Control Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `ROAH` Naha Airport in Okinawa, Japan, as well as `RODN` Kadena Air Base and `ROTM` MCAS Futenma. The airspace ceiling is FL200.
|
||||
|
||||
Based on AIP Japan (Ministry of Land, Infrastructure, Transport and Tourism) (https://aisjapan.mlit.go.jp/html/AIP/html/DomesticAIP.do). The choice of SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All aircraft are assumed to be RNAV capable; no conventional NAVAID-based SIDs or STARs are implemented unless there is no RNAV alternative. Coastline data from naturalearthdata.com.
|
||||
|
||||
The Naha ACA is a mostly circular terminal area typical for an island airport. There is a heavy military presence, and military training areas are scattered around the main island as well between the airways that extend out from the Naha `NHC` VORTAC. Approach and departure paths cross over/under each other just north of Naha, and there are many potential conflict points to the west/east of Okinawa as well. The majority of traffic enters the ACA from the northeast from mainland Japan and southwest from the other Ryukyu islands such as Miyakojima and Ishigaki. USAF training area W-178(A) is depicted as inactive for gameplay purposes. Expect heavy use of vectors, especially as traffic increases.
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix, to the same airport or even different airports. Pressing the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
`ROKR` Kerama, `RORA` Aguni, `RORE` Iejima, and `RODE` Ie Shima Auxiliary are not represented due to a lack of traffic to/from outside of the ACA. However, the runways of the former three airports are shown on the map.
|
||||
|
||||
## Airports
|
||||
|
||||
### `ROAH` Naha
|
||||
|
||||
The main airport of this sector. Jointly used by civilian and JSDF traffic, this airport on the southern tip of Okinawa Island has added a new parallel runway in the sea to the west in response to increased traffic including the increases in scrambles of fighter jets. Unlike Chitose in Hokkaido, civilian and military traffic use the same runways, meaning passengers onboard airliners are able to see fighters taking off with afterburners from their window seat.
|
||||
|
||||
As a controller, the mix of aircraft may be more exciting than the normal airport, but will need attention when the `F16` zooming along catches up to the `AT46`... STARs are available, however in real life vectors are used heavily.
|
||||
|
||||
**SOME MILITARY AIRCRAFT (`F16`, `T4`, `P3`, `E2`) ARE DEPICTED AS AIRCRAFT LANDING AT "`JF`" AERODROME FOR TECHNICAL REASONS. THESE AIRCRAFT SHOULD LAND AT `ROAH`.**
|
||||
|
||||
There is custom traffic for `ROAH`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Major fixes on the map have a defined hold including many fixes along the STARs. The published hold for missed approaches is `OLVAL`.
|
||||
|
||||
Aircraft arrive at 3 points:
|
||||
|
||||
- `PRIUS` -`Y525`-> `IHEYA` (north/north east from mainland Japan/Korea)
|
||||
- `GEMNI` -`Y57`-> `VELNO` (southwest from western Ryukyu Islands/Taiwan)
|
||||
- `BUICK` -`V75`-> `NANJO` (east from Daito Islands/Pacific Ocean)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `CHAMP` (north via `Y579` to Korea)
|
||||
- `AMAMI` (north/northeast via `Y574`/`Y53`/`Y25` etc. northeast for mainland Japan)
|
||||
- `BUICK` (east via `V75` for Daito Islands/Pacific Ocean)
|
||||
- `GANJU` or `CANOP` depending on runway (southwest for western Ryukyu Islands/Taiwan)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 18L/36R
|
||||
- 18R/36L (new west parallel runway)
|
||||
|
||||
Two landing configurations are in general use:
|
||||
|
||||
- Landing 36L, departing 36R
|
||||
|
||||
The west runway is used for arrivals while the east runway is used for departures. In real life, traffic may land 36R for a shorter taxi if traffic allows.
|
||||
|
||||
Approaches to 36L are available from `BLISS`.
|
||||
|
||||
STARs are available using APP mode from `IHEYA`, `VELNO`, `BUICK`, and some intermediate points on the STARs. Military aircraft may only engage app mode from certain outer fixes due to technical reasons; recommend vectors to final if not suitable STAR available.
|
||||
|
||||
Use caution for departures towards `KIZNA` conflicting with 05 arrivals to `RODN`. Vectoring may be required to the west at altitude 1200 to clear `RODN` 05 arrivals descending through 2200 at `JIMMY`.
|
||||
|
||||
Simultaneous approaches to 36L and 36R are NOT authorized.
|
||||
|
||||
- Landing 18R, departing 18L
|
||||
|
||||
The west runway is used for arrivals while the east runway is used for departures. In real life, traffic may land 18L for a shorter taxi if traffic allows.
|
||||
|
||||
Approaches to 18R are available from `SALSA`.
|
||||
|
||||
STARs are available using APP mode from `IHEYA`, `VELNO`, `BUICK`, and some intermediate points on the STARs. Military aircraft may only engage app mode from certain outer fixes due to technical reasons, **except for from `VIGER`**. **FOR `JF` AIRCRAFT, TO INITIATE AN APPROACH FROM `VIGER`, USE THE SECOND APPROACH BY SELECTING "APP" TWICE. THE ASSIGNED APPROACH SHOULD BE TO RWY `18LJF` VIA 15 DME ARC CCW. *`JF` aircraft will go around if the runway selected is `18L`.*** Recommend vectors to final if not suitable STAR available.
|
||||
|
||||
Use caution for arrivals conflicting with 05 arrivals to `RODN`. `RODN` arrivals may need to held over `JACKS` for a gap in `ROAH` arrivals.
|
||||
|
||||
Simultaneous approaches to 18L and 18R are NOT authorized.
|
||||
|
||||
### `RODN` Kadena Air Base
|
||||
|
||||
This is the USAF's home in Okinawa. A variety of aircraft, military or chartered civilian, fly in and out of this aerodrome going to training areas or other USAF bases in Japan/Guam/USA.
|
||||
|
||||
There is custom traffic for `RODN`. The proportions and callsigns are very much plain guesses however, no assertions are made regarding accuracy (instead, assertions are made regarding its *inaccuracy*.)
|
||||
|
||||
Major fixes on the map have a defined hold.
|
||||
|
||||
Aircraft depart to ATS routes via `BASHO` `BUICK` `DODGE` or `ONC`, or to the North Range and South Range. There are real life SIDs but they are all just two points in a (mostly) straight line after departure to a waypoint not connected to the ATS routes. Therefore no SIDs are implemented, just a heading after departure. Departures should be vectored until direct to exit point can be issued.
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 05L/23R
|
||||
- 05R/23L
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing 05L, departing 05R
|
||||
|
||||
The north runway is mainly used for arrivals and the south runway is mainly used for departures.
|
||||
|
||||
Approaches to 05L are available from `JACKS` etc.
|
||||
|
||||
No STARs are available, arrivals should be vectored to `JACKS` or other fixes on the approach.
|
||||
|
||||
Use caution for `ROAH` arrivals to 18s or departures from 36s. Arrivals must descend through 2200 at `JIMMY` to remain on GS. Recommend vectors for `ROAH` 36 departures to maintain separation. ~~Recommend holding `RODN` arrivals at `JACKS` until gap can be made in `ROAH` 18 arrivals.~~ **Due to conflicts with `ROAH` 36 departures, 05L has been raised 500ft to displace the glideslope so 05 approaches do not conflict.** However, the `JIMMY` 2200 restriction has been maintained to simulate the original GS.
|
||||
|
||||
The published hold for missed approaches is straight ahead to `IMONO`.
|
||||
|
||||
- Landing 23R, departing 23L
|
||||
|
||||
The north runway is mainly used for arrivals and the south runway is mainly used for departures.
|
||||
|
||||
Approaches to 23R are available from `IMONO` etc.
|
||||
|
||||
No STARs are available, arrivals should be vectored to `IMONO` or other fixes on the approach.
|
||||
|
||||
Use caution for `ROAH` arrivals to 18s or departures from 36s. Departures must climb to at least 2200 to clear. **Due to conflicts between 05 arrivals and `ROAH` 36 departures, 05L/23R has been raised 500ft to displace the glideslope.** However, the altitudes for the fixes along the 23R ILS have been maintained to simulate the original GS.
|
||||
|
||||
The published hold for missed approaches is straight ahead to `JACKS`.
|
||||
|
||||
### `ROTM` MCAS Futenma
|
||||
|
||||
A USN airfield south of Kadena. Most traffic would be helicopters to training areas around Okinawa, but there is some fixed wing traffic to other US military facilities.
|
||||
|
||||
There is custom traffic for `ROTM`. The proportions and callsigns are very much plain guesses however, no assertions are made regarding accuracy (instead, assertions are made regarding its *inaccuracy*.)
|
||||
|
||||
Aircraft depart to ATS routes via `BASHO` `BUICK` `DODGE` or `ONC`. No SIDs are implemented, just a heading after departure. Departures should be vectored until direct to exit point can be issued.
|
||||
|
||||
There is one runway:
|
||||
|
||||
- 06/24
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 06
|
||||
|
||||
No approach fixes are available, and no STARs are available, arrivals should be vectored to final.
|
||||
|
||||
Use caution for `ROAH` traffic under the approach path and parallel `RODN` arrivals to the north.
|
||||
|
||||
- Landing and departing 24
|
||||
|
||||
No approach fixes are available, and no STARs are available, arrivals should be vectored to final.
|
||||
|
||||
Use caution for `ROAH` traffic under the departure path and parallel `RODN` arrivals to the north.
|
||||
|
||||
### `ROKJ` Kumejima
|
||||
|
||||
A runway with a small apron on this island west of Okinawa. The only scheduled service is to `ROAH` Naha, and a seasonal service to `RJTT` Tokyo Haneda.
|
||||
|
||||
There is custom traffic for `ROKJ`. Unfortunately, traffic to `ROAH` cannot be simulated due to the game not supporting this. Only the seasonal traffic to/from the northeast is simulated.
|
||||
|
||||
Aircraft depart and arrive via the `NHC` - `LAVON` - `GURUX` - `DORIS` corridor.
|
||||
|
||||
There is one runway:
|
||||
|
||||
- 03/21
|
||||
|
||||
Only one runway configuration is implemented:
|
||||
|
||||
- Landing and departing 03
|
||||
|
||||
Approaches are available from `DUFFY` and `DORIS`.
|
||||
|
||||
The published hold for missed approaches is a *left* turn to `DORIS`.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- Have different types of traffic use different entry/exit gateways are not possible in this game, therefore aircraft using civil and military routes are separated by duplicating `ROAH`, which means there are two runways each of 18L/36R and 18R/36L. As the game will allow you to select approaches meant for a different airport if they share a starting fix with an approach for the airport the selected aircraft is landing at, this can lead to military aircraft flying the "civilian" approach and going around due to trying to land at the "wrong" airport. To avoid this issue, civil and military aircraft landing `ROAH` do not have approaches that share fixes.
|
||||
- Many areas have their ceiling marked as "0" as they are likely not active for all of their hours of operation and interfere with standard flight paths, or because they are shared with traffic to different airports (which is not supported by the game)
|
||||
- No `ROAH`-`ROKJ` traffic
|
||||
- No `RODN` SIDs - the SIDs are available on the AIP, but the connecting routes to airways are not published as airways or procedures, or even as direct routes or flight planned routes via AIC. Author is only aware of one - `ADDAN` (`DCT`) `BASHO` (`DCT`) `AMAMI`. In fact, `BASHO` does not appear to be used for any other purpose...
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This is a best effort work based on air traffic observations and official aeronautical publications. No guarantee is made that the representation of Naha ACA matches real life procedures in any way. Especially, procedures around `RODN` Kadena and `ROTM` Futenma may be grossly inaccurate, and callsigns for military aircraft are very likely to be either incorrect, out of date, or completely fabricated. Any information (that is not classified or secret in any way) regarding inaccuracies is appreciated.
|
||||
|
||||
## For Developers
|
||||
|
||||
This file is built from `source\ROAH.txt` via `deploy.py`. Make any contributions to `source\ROAH.txt` and NOT to `.\ROAH.txt`.
|
||||
|
||||
## Changelog
|
||||
|
||||
**DUE TO NATURE OF TRAFFIC AT THE `ROAH` AERODROME, THIS AIRPORT FILE HAS QUIRKS RELATED TO MILITARY AIRCRAFT TO/FROM `ROAH`.**
|
||||
|
||||
# `ROAH` ACA 1.0.0
|
||||
|
||||
This is an implementation of the Naha ACA (Approach Control Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `ROAH` Naha Airport in Okinawa, Japan, as well as `RODN` Kadena Air Base and `ROTM` MCAS Futenma. The airspace ceiling is FL200.
|
||||
|
||||
Based on AIP Japan (Ministry of Land, Infrastructure, Transport and Tourism) (https://aisjapan.mlit.go.jp/html/AIP/html/DomesticAIP.do). The choice of SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All aircraft are assumed to be RNAV capable; no conventional NAVAID-based SIDs or STARs are implemented unless there is no RNAV alternative. Coastline data from naturalearthdata.com.
|
||||
|
||||
The Naha ACA is a mostly circular terminal area typical for an island airport. There is a heavy military presence, and military training areas are scattered around the main island as well between the airways that extend out from the Naha `NHC` VORTAC. Approach and departure paths cross over/under each other just north of Naha, and there are many potential conflict points to the west/east of Okinawa as well. The majority of traffic enters the ACA from the northeast from mainland Japan and southwest from the other Ryukyu islands such as Miyakojima and Ishigaki. USAF training area W-178(A) is depicted as inactive for gameplay purposes. Expect heavy use of vectors, especially as traffic increases.
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix, to the same airport or even different airports. Pressing the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
`ROKR` Kerama, `RORA` Aguni, `RORE` Iejima, and `RODE` Ie Shima Auxiliary are not represented due to a lack of traffic to/from outside of the ACA. However, the runways of the former three airports are shown on the map.
|
||||
|
||||
## Airports
|
||||
|
||||
### `ROAH` Naha
|
||||
|
||||
The main airport of this sector. Jointly used by civilian and JSDF traffic, this airport on the southern tip of Okinawa Island has added a new parallel runway in the sea to the west in response to increased traffic including the increases in scrambles of fighter jets. Unlike Chitose in Hokkaido, civilian and military traffic use the same runways, meaning passengers onboard airliners are able to see fighters taking off with afterburners from their window seat.
|
||||
|
||||
As a controller, the mix of aircraft may be more exciting than the normal airport, but will need attention when the `F16` zooming along catches up to the `AT46`... STARs are available, however in real life vectors are used heavily.
|
||||
|
||||
**SOME MILITARY AIRCRAFT (`F16`, `T4`, `P3`, `E2`) ARE DEPICTED AS AIRCRAFT LANDING AT "`JF`" AERODROME FOR TECHNICAL REASONS. THESE AIRCRAFT SHOULD LAND AT `ROAH`.**
|
||||
|
||||
There is custom traffic for `ROAH`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Major fixes on the map have a defined hold including many fixes along the STARs. The published hold for missed approaches is `OLVAL`.
|
||||
|
||||
Aircraft arrive at 3 points:
|
||||
|
||||
- `PRIUS` -`Y525`-> `IHEYA` (north/north east from mainland Japan/Korea)
|
||||
- `GEMNI` -`Y57`-> `VELNO` (southwest from western Ryukyu Islands/Taiwan)
|
||||
- `BUICK` -`V75`-> `NANJO` (east from Daito Islands/Pacific Ocean)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `CHAMP` (north via `Y579` to Korea)
|
||||
- `AMAMI` (north/northeast via `Y574`/`Y53`/`Y25` etc. northeast for mainland Japan)
|
||||
- `BUICK` (east via `V75` for Daito Islands/Pacific Ocean)
|
||||
- `GANJU` or `CANOP` depending on runway (southwest for western Ryukyu Islands/Taiwan)
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 18L/36R
|
||||
- 18R/36L (new west parallel runway)
|
||||
|
||||
Two landing configurations are in general use:
|
||||
|
||||
- Landing 36L, departing 36R
|
||||
|
||||
The west runway is used for arrivals while the east runway is used for departures. In real life, traffic may land 36R for a shorter taxi if traffic allows.
|
||||
|
||||
Approaches to 36L are available from `BLISS`.
|
||||
|
||||
STARs are available using APP mode from `IHEYA`, `VELNO`, `BUICK`, and some intermediate points on the STARs. Military aircraft may only engage app mode from certain outer fixes due to technical reasons; recommend vectors to final if not suitable STAR available.
|
||||
|
||||
Use caution for departures towards `KIZNA` conflicting with 05 arrivals to `RODN`. Vectoring may be required to the west at altitude 1200 to clear `RODN` 05 arrivals descending through 2200 at `JIMMY`.
|
||||
|
||||
Simultaneous approaches to 36L and 36R are NOT authorized.
|
||||
|
||||
- Landing 18R, departing 18L
|
||||
|
||||
The west runway is used for arrivals while the east runway is used for departures. In real life, traffic may land 18L for a shorter taxi if traffic allows.
|
||||
|
||||
Approaches to 18R are available from `SALSA`.
|
||||
|
||||
STARs are available using APP mode from `IHEYA`, `VELNO`, `BUICK`, and some intermediate points on the STARs. Military aircraft may only engage app mode from certain outer fixes due to technical reasons, **except for from `VIGER`**. **FOR `JF` AIRCRAFT, TO INITIATE AN APPROACH FROM `VIGER`, USE THE SECOND APPROACH BY SELECTING "APP" TWICE. THE ASSIGNED APPROACH SHOULD BE TO RWY `18LJF` VIA 15 DME ARC CCW. *`JF` aircraft will go around if the runway selected is `18L`.*** Recommend vectors to final if not suitable STAR available.
|
||||
|
||||
Use caution for arrivals conflicting with 05 arrivals to `RODN`. `RODN` arrivals may need to held over `JACKS` for a gap in `ROAH` arrivals.
|
||||
|
||||
Simultaneous approaches to 18L and 18R are NOT authorized.
|
||||
|
||||
### `RODN` Kadena Air Base
|
||||
|
||||
This is the USAF's home in Okinawa. A variety of aircraft, military or chartered civilian, fly in and out of this aerodrome going to training areas or other USAF bases in Japan/Guam/USA.
|
||||
|
||||
There is custom traffic for `RODN`. The proportions and callsigns are very much plain guesses however, no assertions are made regarding accuracy (instead, assertions are made regarding its *inaccuracy*.)
|
||||
|
||||
Major fixes on the map have a defined hold.
|
||||
|
||||
Aircraft depart to ATS routes via `BASHO` `BUICK` `DODGE` or `ONC`, or to the North Range and South Range. There are real life SIDs but they are all just two points in a (mostly) straight line after departure to a waypoint not connected to the ATS routes. Therefore no SIDs are implemented, just a heading after departure. Departures should be vectored until direct to exit point can be issued.
|
||||
|
||||
There are two runways:
|
||||
|
||||
- 05L/23R
|
||||
- 05R/23L
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing 05L, departing 05R
|
||||
|
||||
The north runway is mainly used for arrivals and the south runway is mainly used for departures.
|
||||
|
||||
Approaches to 05L are available from `JACKS` etc.
|
||||
|
||||
No STARs are available, arrivals should be vectored to `JACKS` or other fixes on the approach.
|
||||
|
||||
Use caution for `ROAH` arrivals to 18s or departures from 36s. Arrivals must descend through 2200 at `JIMMY` to remain on GS. Recommend vectors for `ROAH` 36 departures to maintain separation. ~~Recommend holding `RODN` arrivals at `JACKS` until gap can be made in `ROAH` 18 arrivals.~~ **Due to conflicts with `ROAH` 36 departures, 05L has been raised 500ft to displace the glideslope so 05 approaches do not conflict.** However, the `JIMMY` 2200 restriction has been maintained to simulate the original GS.
|
||||
|
||||
The published hold for missed approaches is straight ahead to `IMONO`.
|
||||
|
||||
- Landing 23R, departing 23L
|
||||
|
||||
The north runway is mainly used for arrivals and the south runway is mainly used for departures.
|
||||
|
||||
Approaches to 23R are available from `IMONO` etc.
|
||||
|
||||
No STARs are available, arrivals should be vectored to `IMONO` or other fixes on the approach.
|
||||
|
||||
Use caution for `ROAH` arrivals to 18s or departures from 36s. Departures must climb to at least 2200 to clear. **Due to conflicts between 05 arrivals and `ROAH` 36 departures, 05L/23R has been raised 500ft to displace the glideslope.** However, the altitudes for the fixes along the 23R ILS have been maintained to simulate the original GS.
|
||||
|
||||
The published hold for missed approaches is straight ahead to `JACKS`.
|
||||
|
||||
### `ROTM` MCAS Futenma
|
||||
|
||||
A USN airfield south of Kadena. Most traffic would be helicopters to training areas around Okinawa, but there is some fixed wing traffic to other US military facilities.
|
||||
|
||||
There is custom traffic for `ROTM`. The proportions and callsigns are very much plain guesses however, no assertions are made regarding accuracy (instead, assertions are made regarding its *inaccuracy*.)
|
||||
|
||||
Aircraft depart to ATS routes via `BASHO` `BUICK` `DODGE` or `ONC`. No SIDs are implemented, just a heading after departure. Departures should be vectored until direct to exit point can be issued.
|
||||
|
||||
There is one runway:
|
||||
|
||||
- 06/24
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
- Landing and departing 06
|
||||
|
||||
No approach fixes are available, and no STARs are available, arrivals should be vectored to final.
|
||||
|
||||
Use caution for `ROAH` traffic under the approach path and parallel `RODN` arrivals to the north.
|
||||
|
||||
- Landing and departing 24
|
||||
|
||||
No approach fixes are available, and no STARs are available, arrivals should be vectored to final.
|
||||
|
||||
Use caution for `ROAH` traffic under the departure path and parallel `RODN` arrivals to the north.
|
||||
|
||||
### `ROKJ` Kumejima
|
||||
|
||||
A runway with a small apron on this island west of Okinawa. The only scheduled service is to `ROAH` Naha, and a seasonal service to `RJTT` Tokyo Haneda.
|
||||
|
||||
There is custom traffic for `ROKJ`. Unfortunately, traffic to `ROAH` cannot be simulated due to the game not supporting this. Only the seasonal traffic to/from the northeast is simulated.
|
||||
|
||||
Aircraft depart and arrive via the `NHC` - `LAVON` - `GURUX` - `DORIS` corridor.
|
||||
|
||||
There is one runway:
|
||||
|
||||
- 03/21
|
||||
|
||||
Only one runway configuration is implemented:
|
||||
|
||||
- Landing and departing 03
|
||||
|
||||
Approaches are available from `DUFFY` and `DORIS`.
|
||||
|
||||
The published hold for missed approaches is a *left* turn to `DORIS`.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- Have different types of traffic use different entry/exit gateways are not possible in this game, therefore aircraft using civil and military routes are separated by duplicating `ROAH`, which means there are two runways each of 18L/36R and 18R/36L. As the game will allow you to select approaches meant for a different airport if they share a starting fix with an approach for the airport the selected aircraft is landing at, this can lead to military aircraft flying the "civilian" approach and going around due to trying to land at the "wrong" airport. To avoid this issue, civil and military aircraft landing `ROAH` do not have approaches that share fixes.
|
||||
- Many areas have their ceiling marked as "0" as they are likely not active for all of their hours of operation and interfere with standard flight paths, or because they are shared with traffic to different airports (which is not supported by the game)
|
||||
- No `ROAH`-`ROKJ` traffic
|
||||
- No `RODN` SIDs - the SIDs are available on the AIP, but the connecting routes to airways are not published as airways or procedures, or even as direct routes or flight planned routes via AIC. Author is only aware of one - `ADDAN` (`DCT`) `BASHO` (`DCT`) `AMAMI`. In fact, `BASHO` does not appear to be used for any other purpose...
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This is a best effort work based on air traffic observations and official aeronautical publications. No guarantee is made that the representation of Naha ACA matches real life procedures in any way. Especially, procedures around `RODN` Kadena and `ROTM` Futenma may be grossly inaccurate, and callsigns for military aircraft are very likely to be either incorrect, out of date, or completely fabricated. Any information (that is not classified or secret in any way) regarding inaccuracies is appreciated.
|
||||
|
||||
## For Developers
|
||||
|
||||
This file is built from `source\ROAH.txt` via `deploy.py`. Make any contributions to `source\ROAH.txt` and NOT to `.\ROAH.txt`.
|
||||
|
||||
## Changelog
|
||||
|
||||
* 1.0 - 2021/02/08 - Initial version.
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,23 @@
|
||||
[expand.callsigns]
|
||||
|
||||
ckstr = check star
|
||||
rch = reach
|
||||
cnv7 = convoy 7
|
||||
cnv3 = convoy 3
|
||||
madfox = mad fox
|
||||
pswrd = password
|
||||
brgham = brigham
|
||||
vampr = vampire
|
||||
tmboy = tomboy
|
||||
neptn = neptune
|
||||
cygns = cygnus
|
||||
|
||||
ana = all neep pawn
|
||||
#sfj = stah-foo-lai-yaa
|
||||
#jal = juh-pawn eh are
|
||||
#snj = nyuh sky
|
||||
#jta = j oh-shun
|
||||
#ado = eh are do
|
||||
#jjp = orenji lie-nuh
|
||||
#apj = eh are peach
|
||||
#rsd = state aero
|
||||
@@ -1,157 +1,157 @@
|
||||
#VHHH TMA 1.0.0
|
||||
|
||||
This is an implementation of the Hong Kong TMA (Terminal Maneuvering Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `VHHH` Hong Kong International Airport (also known as Chek Lap Kok) and `VMMC` Macau International Airport. The airspace ceiling is FL250. `ZGSZ` Shenzhen Baoan, although not part of the VHHH TMA, has traffic that would transit the airspace at altitudes low enough to be considered for inclusion. However it is not currently implemented.
|
||||
|
||||
The maximum controllable area is limited by the spawn point limits in Endless ATC, which is a 100nm circle around the map center. Therefore, the controlled area in this implementation is a heavily reduced portion of the actual VHHH TMA, omitting much of the terminal transition routes. As such, it is recommended to begin a new game at 4x speed until an aircraft reaches an initial approach fix, and play with a high minimum score (be sure to slowly ramp up to the desired value) or a fixed flow of ~30+.
|
||||
|
||||
Based upon AIP HONG KONG EFF 2021/02/25 and AIP MACAO AMDT 39 EFF 2020/11/19. The choice of SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All aircraft are assumed to be RNAV capable. Pure RNAV approaches are not implemented in favour of RNAV+ILS or conventional ILS approaches. Coastline data from naturalearthdata.com.
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Press the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
## Airports
|
||||
|
||||
### `VHHH` Hong Kong International Airport (Chek Lap Kok)
|
||||
|
||||
A modern island airport built on reclaimed land north of Lantau Island after Hong Kong outgrew the old airport at Kai Tak, famous for the IGS RWY 13 "Checkboard" approach. Being located on its own island and built from scratch, the approaches to Chek Lap Kok are much more forgiving than at Kai Tak, but the mountaineous terrain of Hong Kong still restricts flight paths. The proximity of the Hong Kong - Guangzhou FIR boundary just north of the airport, and the other airports closely packed into the river delta region also result in a very restricted airspace.
|
||||
|
||||
In general, `VHHH` operates in a segregated mode with the north runway used for arrivals and the south runway used for departures.
|
||||
|
||||
There is custom traffic for `VHHH`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Some major fixes on the map have a defined hold including many fixes along the STARs. If playing with a high amount of traffic, significant holding may be required with only one landing runway and lack of room for delay vectors close to the airport. For arrivals from the northeast, traffic may be redirected to the southeast arrival route via MEPUT for additional holding at EATON and beyond.
|
||||
|
||||
Note that as the game cannot handle multiple approaches to the same runway from the same fix, `SIERA` 7C/6D STARs from `SIERA` can be activated using direct to `BORDA`.
|
||||
|
||||
Aircraft arrive via 4 points:
|
||||
|
||||
- `FISHA` (`A1/G581 ELATO V522` from Taipei FIR to the east; `A470 DOTMI V512` or `M503 LELIM V591` from the northeast via Guangzhou FIR)
|
||||
- `DAKTO` (`A461/M501 NOMAN V532` from Manila FIR the southeast)
|
||||
- `HOCKY` (`A583 SABNO V542` or `M771/M772 DUMOL Q1 CARSO V551` from the south/southwest)
|
||||
- `GAMBA` (`A1/P901 IDOSI V561` or `A202/R339 SIKOU V571` from Sanya FIR to the west)
|
||||
- `SIERA` (`R473 SIERA` from Guangzhou FIR to the north)
|
||||
|
||||
Aircraft depart via 10 points:
|
||||
|
||||
- `BEKOL` (north via `A461` to China)
|
||||
- `DOTMI` (northeast via `A470` to southeastern China)
|
||||
- `LELIM` (northeast via `M503` to Shanghai Pudong, Qingdao, Dalian, Yantai)
|
||||
- `ENVAR` (east via `M750` to Korea, Japan, Pacific)
|
||||
- `KAPLI` (east via 'G86' to routes south of Taiwan)
|
||||
- `NOMAN` (southeast via `M501` and `A461` to Philippines)
|
||||
- `SABNO` (south via `A583`)
|
||||
- `EPDOS` (southwest via `L642` to Singapore, Malaysia)
|
||||
- `IDOSI` (southwest via `A1` to Cambodia, Vietnam, Thailand)
|
||||
- `SIKOU` (west via `A202` or `R339` to Hainan, Hanoi, India etc.)
|
||||
|
||||
There are two runways:
|
||||
|
||||
-07L/25R (departures)
|
||||
-07R/25L (arrivals)
|
||||
|
||||
Two landing configurations are in general use:
|
||||
|
||||
- Landing 07L, departing 07R
|
||||
|
||||
The usual configuration.
|
||||
|
||||
The ILS approach to 07L is available from the FAF `VH710`, but in practice all approaches are made from `LIMES`. It is not recommended to vector aircraft inside `LIMES`, and should be completely avoided inside `VH710`. due to the proximity of the FIR boundary and the high terrain south and northeast of the airport.
|
||||
|
||||
Upon missed approach, aircraft can climb to 5000 and fly the approach again from `DEDEE`, which will simulate a full missed approach back to the IAF `LIMES`. If the aircraft is not ready by `DEDEE`, the approach is also available from `SAMPU` and `TD` etc.
|
||||
|
||||
Speed management can be effective to sequence aircraft by `LIMES`. Use care to normalize speed between aircraft once they reach `LIMES` so as to maintain separation until the runway.
|
||||
|
||||
Note that independent simultaneous approaches to 07L and 07R are not permitted. Note that the RNP Y contingency procedure is not implemented.
|
||||
|
||||
Departures from 07R should fly the STAR to *fly-over* the first waypoint (`PORPA`) -5000 to clear the high terrain of Lantau Island south of the airport and the restricted area VHR12. Afterwards, altitude management should be sufficient to separate from any other traffic.
|
||||
|
||||
- Landing 25R, departing 25L
|
||||
|
||||
The west wind configuration.
|
||||
|
||||
The ILS approach to 25R is available from the FAF `RIVER`, but in practice all approaches are made from `TD` or `PLOVE`. It is not recommended to vector aircraft inside `TD`, and should be completely avoided inside `RIVER`. due to the proximity of the FIR boundary and the high terrain under the approach path.
|
||||
|
||||
Upon missed approach, aircraft can climb to 5000 and fly the approach again from `MA25R`, which will simulate a full missed approach back to the IAF `TD`. The missed approach path does not actually include point `MA25R`, it is a fictional waypoint placed a distance away from the airport as an aircraft cannot be commanded to proceed direct to a fix close by. The missed approach is also available from `LKC`, but usually the aircraft on missed is too close from `LKC` and the game will not allow direct to `LKC`.
|
||||
|
||||
Speed management can be effective to sequence aircraft by `TD`. Use care to normalize speed between aircraft once they reach `TD` so as to maintain separation until the runway.
|
||||
|
||||
Note that independent simultaneous approaches to 25L and 25R are not permitted. Note that the RNP Y procedure is not implemented.
|
||||
|
||||
Departures from 25R should fly the STAR to *fly-over* the first waypoint (`PRAWN`) -5000 to clear the high terrain of Lantau Island south of the airport. Afterwards, altitude management should be sufficient to separate from any other traffic.
|
||||
|
||||
### `VMMC` Macau International Airport
|
||||
|
||||
This airport serving the city of Macau has an island runway connected to the apron by two long taxiway bridges. Another peculiarity is how it is located between the Hong Kong and Guangzhou FIRs, with aircraft to the north handled by Guangzhou but aircraft to the south handled by Hong Kong. Due to Zhuhai city north of the RWY 34 departure end, aircraft must stay south of the 231 radial from Jiuzhou VOR (`ZAO`) for noise abatement, resulting in an immediate turn to the right departing 34, and a Kai Tak-style approach with an offset localizer to final visual approach for landing 16.
|
||||
|
||||
To faciliate arrivals to 16, a portion of Guangzhou FIR around `ZUH` and south of `NLG` has been included in the airspace, with the low altitudes restricted to `VMMC` traffic.
|
||||
|
||||
There is custom traffic for `VMMC`. The proportions are very much estimates but shouldn't be too far off from reality. Note that only traffic departing and arriving via Hong Kong FIR are included.
|
||||
|
||||
Some major fixes on the map have a defined hold including many fixes along the STARs.
|
||||
|
||||
Aircraft arrive via 4 points:
|
||||
|
||||
- `NEDLE` (`J101` from the east via Taipei FIR or from the northeast via Guangzhou FIR)
|
||||
- `ISBAN` (`J103` from the southeast via Manila FIR or southsouthwest via Sanya FIR)
|
||||
- `DASON` (`J104` from the south/southwest via Sanya FIR)
|
||||
|
||||
Aircraft depart via 9 points:
|
||||
|
||||
- `DOTMI` (northeast via `A470` to southeastern China)
|
||||
- `LELIM` (northeast via `M503` to Shanghai Pudong, Qingdao, Dalian, Yantai)
|
||||
- `ENVAR` (east via `M750` to Korea, Japan, Pacific)
|
||||
- `KAPLI` (east via 'G86' to routes south of Taiwan)
|
||||
- `NOMAN` (southeast via `M501` and `A461` to Philippines)
|
||||
- `SABNO` (south via `A583`)
|
||||
- `EPDOS` (southwest via `L642` to Singapore, Malaysia)
|
||||
- `IDOSI` (southwest via `A1` to Cambodia, Vietnam, Thailand)
|
||||
- `SIKOU` (west via `A202` or `R339` to Hanoi, India etc.)
|
||||
|
||||
There is the one island runway, 16/34. However, to simulate the offset localizer for 16, a fake runway 16C(/34C) is included. Planes will land on 16C instead of 16.
|
||||
|
||||
Two landing configurations are in general use:
|
||||
|
||||
- Landing 34, departing 34
|
||||
|
||||
The usual configuration.
|
||||
|
||||
The ILS approach to 34 is available from the FAF `PAPA`.
|
||||
|
||||
Upon missed approach, aircraft can climb to 6000 (by `MC411`) and fly the approach again from `ZAO`, which will simulate a full missed approach back to the IAF `HAZEL`. If the aircraft is not ready by `ZAO`, the approach is also available from `MC420` and `MC411`. Holding after missed is available at PAPA.
|
||||
|
||||
Speed management can be effective to sequence aircraft. Arrivals via the established STARs are recommended due to the congestion of airspace around `VHHH`.
|
||||
|
||||
Use care to have 34 departures climb to 6000 (+4000 by `MC420`, +5500 by `MC411`) to cross `LKC` 6000 with further climb subject to traffic conditions (arrivals via `SMT` overhead).
|
||||
|
||||
- Landing 16(C), departing 16
|
||||
|
||||
The south wind configuration.
|
||||
|
||||
The LLZ/DME approach to 16(C) is available from the IAF `ZUH`. You should not vector aircraft inside `ZUH` as these aircraft would be under control of Guangzhou after `INDUS`.
|
||||
|
||||
Upon missed approach, aircraft can climb to 4000 and fly direct to MC513 where holding is available at +3000. From `MC513`, aircraft can execute the approach via `INDUS`/`ZUH`/`MC513` at +5900 (+1800m).
|
||||
|
||||
Speed management can be effective to sequence aircraft. Arrivals via the established STARs are recommended due to the congestion of airspace around `VHHH`.
|
||||
|
||||
Use care to separate 16 departures from `VHHH` arrivals between `CANTO` and `MURRY` and `VHHH` departures near `PECAN`.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- No `ZGSZ`
|
||||
- No `ZGSD`
|
||||
- No RNP Y procedures
|
||||
- No 25/34 or 07/16 configurations
|
||||
- The northern boundary is super lazy (I am not going to trace 3nm from the Chinese coastline, sorry)
|
||||
- `SIERA` C/D arrivals only selectable from `BORDA`
|
||||
- `UJ` and `MCU` transitions implemented for `VMMC` 34 but would only be used for arrivals from `ZGZU` FIR, leaving them in for the heck of it
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This is a best effort work based on air traffic observations and official aeronautical publications. No guarantee is made that this representation of VHHH TMA matches real life procedures in any way. Any information regarding inaccuracies is appreciated.
|
||||
|
||||
## For Developers
|
||||
|
||||
This file is built from `source\VHHH.txt` via `deploy.py`. Make any contributions to `source\VHHH.txt` and NOT to `.\VHHH.txt`.
|
||||
|
||||
## Changelog
|
||||
|
||||
* 1.0 - 2020/01/09 - Initial version.
|
||||
#VHHH TMA 1.0.0
|
||||
|
||||
This is an implementation of the Hong Kong TMA (Terminal Maneuvering Area) for [Endless ATC](https://steamcommunity.com/app/666610) featuring `VHHH` Hong Kong International Airport (also known as Chek Lap Kok) and `VMMC` Macau International Airport. The airspace ceiling is FL250. `ZGSZ` Shenzhen Baoan, although not part of the VHHH TMA, has traffic that would transit the airspace at altitudes low enough to be considered for inclusion. However it is not currently implemented.
|
||||
|
||||
The maximum controllable area is limited by the spawn point limits in Endless ATC, which is a 100nm circle around the map center. Therefore, the controlled area in this implementation is a heavily reduced portion of the actual VHHH TMA, omitting much of the terminal transition routes. As such, it is recommended to begin a new game at 4x speed until an aircraft reaches an initial approach fix, and play with a high minimum score (be sure to slowly ramp up to the desired value) or a fixed flow of ~30+.
|
||||
|
||||
Based upon AIP HONG KONG EFF 2021/02/25 and AIP MACAO AMDT 39 EFF 2020/11/19. The choice of SIDs and STARs may not be 100% accurate to real life but should be reasonably accurate reflecting daytime IMC conditions. All aircraft are assumed to be RNAV capable. Pure RNAV approaches are not implemented in favour of RNAV+ILS or conventional ILS approaches. Coastline data from naturalearthdata.com.
|
||||
|
||||
STARs are implemented as approach transitions. To activate an approach, an aircraft must be flying direct to an applicable fix, then the APP button can be activated. Multiple approaches may be available from a fix. Press the APP button again before issuing the approach clearance (do not long press) will select the next approach available from that fix. If the aircraft is already on an approach from that fix, you will need to cancel the approach clearance first before issuing another approach clearance.
|
||||
|
||||
## Airports
|
||||
|
||||
### `VHHH` Hong Kong International Airport (Chek Lap Kok)
|
||||
|
||||
A modern island airport built on reclaimed land north of Lantau Island after Hong Kong outgrew the old airport at Kai Tak, famous for the IGS RWY 13 "Checkboard" approach. Being located on its own island and built from scratch, the approaches to Chek Lap Kok are much more forgiving than at Kai Tak, but the mountaineous terrain of Hong Kong still restricts flight paths. The proximity of the Hong Kong - Guangzhou FIR boundary just north of the airport, and the other airports closely packed into the river delta region also result in a very restricted airspace.
|
||||
|
||||
In general, `VHHH` operates in a segregated mode with the north runway used for arrivals and the south runway used for departures.
|
||||
|
||||
There is custom traffic for `VHHH`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Some major fixes on the map have a defined hold including many fixes along the STARs. If playing with a high amount of traffic, significant holding may be required with only one landing runway and lack of room for delay vectors close to the airport. For arrivals from the northeast, traffic may be redirected to the southeast arrival route via MEPUT for additional holding at EATON and beyond.
|
||||
|
||||
Note that as the game cannot handle multiple approaches to the same runway from the same fix, `SIERA` 7C/6D STARs from `SIERA` can be activated using direct to `BORDA`.
|
||||
|
||||
Aircraft arrive via 4 points:
|
||||
|
||||
- `FISHA` (`A1/G581 ELATO V522` from Taipei FIR to the east; `A470 DOTMI V512` or `M503 LELIM V591` from the northeast via Guangzhou FIR)
|
||||
- `DAKTO` (`A461/M501 NOMAN V532` from Manila FIR the southeast)
|
||||
- `HOCKY` (`A583 SABNO V542` or `M771/M772 DUMOL Q1 CARSO V551` from the south/southwest)
|
||||
- `GAMBA` (`A1/P901 IDOSI V561` or `A202/R339 SIKOU V571` from Sanya FIR to the west)
|
||||
- `SIERA` (`R473 SIERA` from Guangzhou FIR to the north)
|
||||
|
||||
Aircraft depart via 10 points:
|
||||
|
||||
- `BEKOL` (north via `A461` to China)
|
||||
- `DOTMI` (northeast via `A470` to southeastern China)
|
||||
- `LELIM` (northeast via `M503` to Shanghai Pudong, Qingdao, Dalian, Yantai)
|
||||
- `ENVAR` (east via `M750` to Korea, Japan, Pacific)
|
||||
- `KAPLI` (east via 'G86' to routes south of Taiwan)
|
||||
- `NOMAN` (southeast via `M501` and `A461` to Philippines)
|
||||
- `SABNO` (south via `A583`)
|
||||
- `EPDOS` (southwest via `L642` to Singapore, Malaysia)
|
||||
- `IDOSI` (southwest via `A1` to Cambodia, Vietnam, Thailand)
|
||||
- `SIKOU` (west via `A202` or `R339` to Hainan, Hanoi, India etc.)
|
||||
|
||||
There are two runways:
|
||||
|
||||
-07L/25R (departures)
|
||||
-07R/25L (arrivals)
|
||||
|
||||
Two landing configurations are in general use:
|
||||
|
||||
- Landing 07L, departing 07R
|
||||
|
||||
The usual configuration.
|
||||
|
||||
The ILS approach to 07L is available from the FAF `VH710`, but in practice all approaches are made from `LIMES`. It is not recommended to vector aircraft inside `LIMES`, and should be completely avoided inside `VH710`. due to the proximity of the FIR boundary and the high terrain south and northeast of the airport.
|
||||
|
||||
Upon missed approach, aircraft can climb to 5000 and fly the approach again from `DEDEE`, which will simulate a full missed approach back to the IAF `LIMES`. If the aircraft is not ready by `DEDEE`, the approach is also available from `SAMPU` and `TD` etc.
|
||||
|
||||
Speed management can be effective to sequence aircraft by `LIMES`. Use care to normalize speed between aircraft once they reach `LIMES` so as to maintain separation until the runway.
|
||||
|
||||
Note that independent simultaneous approaches to 07L and 07R are not permitted. Note that the RNP Y contingency procedure is not implemented.
|
||||
|
||||
Departures from 07R should fly the STAR to *fly-over* the first waypoint (`PORPA`) -5000 to clear the high terrain of Lantau Island south of the airport and the restricted area VHR12. Afterwards, altitude management should be sufficient to separate from any other traffic.
|
||||
|
||||
- Landing 25R, departing 25L
|
||||
|
||||
The west wind configuration.
|
||||
|
||||
The ILS approach to 25R is available from the FAF `RIVER`, but in practice all approaches are made from `TD` or `PLOVE`. It is not recommended to vector aircraft inside `TD`, and should be completely avoided inside `RIVER`. due to the proximity of the FIR boundary and the high terrain under the approach path.
|
||||
|
||||
Upon missed approach, aircraft can climb to 5000 and fly the approach again from `MA25R`, which will simulate a full missed approach back to the IAF `TD`. The missed approach path does not actually include point `MA25R`, it is a fictional waypoint placed a distance away from the airport as an aircraft cannot be commanded to proceed direct to a fix close by. The missed approach is also available from `LKC`, but usually the aircraft on missed is too close from `LKC` and the game will not allow direct to `LKC`.
|
||||
|
||||
Speed management can be effective to sequence aircraft by `TD`. Use care to normalize speed between aircraft once they reach `TD` so as to maintain separation until the runway.
|
||||
|
||||
Note that independent simultaneous approaches to 25L and 25R are not permitted. Note that the RNP Y procedure is not implemented.
|
||||
|
||||
Departures from 25R should fly the STAR to *fly-over* the first waypoint (`PRAWN`) -5000 to clear the high terrain of Lantau Island south of the airport. Afterwards, altitude management should be sufficient to separate from any other traffic.
|
||||
|
||||
### `VMMC` Macau International Airport
|
||||
|
||||
This airport serving the city of Macau has an island runway connected to the apron by two long taxiway bridges. Another peculiarity is how it is located between the Hong Kong and Guangzhou FIRs, with aircraft to the north handled by Guangzhou but aircraft to the south handled by Hong Kong. Due to Zhuhai city north of the RWY 34 departure end, aircraft must stay south of the 231 radial from Jiuzhou VOR (`ZAO`) for noise abatement, resulting in an immediate turn to the right departing 34, and a Kai Tak-style approach with an offset localizer to final visual approach for landing 16.
|
||||
|
||||
To faciliate arrivals to 16, a portion of Guangzhou FIR around `ZUH` and south of `NLG` has been included in the airspace, with the low altitudes restricted to `VMMC` traffic.
|
||||
|
||||
There is custom traffic for `VMMC`. The proportions are very much estimates but shouldn't be too far off from reality. Note that only traffic departing and arriving via Hong Kong FIR are included.
|
||||
|
||||
Some major fixes on the map have a defined hold including many fixes along the STARs.
|
||||
|
||||
Aircraft arrive via 4 points:
|
||||
|
||||
- `NEDLE` (`J101` from the east via Taipei FIR or from the northeast via Guangzhou FIR)
|
||||
- `ISBAN` (`J103` from the southeast via Manila FIR or southsouthwest via Sanya FIR)
|
||||
- `DASON` (`J104` from the south/southwest via Sanya FIR)
|
||||
|
||||
Aircraft depart via 9 points:
|
||||
|
||||
- `DOTMI` (northeast via `A470` to southeastern China)
|
||||
- `LELIM` (northeast via `M503` to Shanghai Pudong, Qingdao, Dalian, Yantai)
|
||||
- `ENVAR` (east via `M750` to Korea, Japan, Pacific)
|
||||
- `KAPLI` (east via 'G86' to routes south of Taiwan)
|
||||
- `NOMAN` (southeast via `M501` and `A461` to Philippines)
|
||||
- `SABNO` (south via `A583`)
|
||||
- `EPDOS` (southwest via `L642` to Singapore, Malaysia)
|
||||
- `IDOSI` (southwest via `A1` to Cambodia, Vietnam, Thailand)
|
||||
- `SIKOU` (west via `A202` or `R339` to Hanoi, India etc.)
|
||||
|
||||
There is the one island runway, 16/34. However, to simulate the offset localizer for 16, a fake runway 16C(/34C) is included. Planes will land on 16C instead of 16.
|
||||
|
||||
Two landing configurations are in general use:
|
||||
|
||||
- Landing 34, departing 34
|
||||
|
||||
The usual configuration.
|
||||
|
||||
The ILS approach to 34 is available from the FAF `PAPA`.
|
||||
|
||||
Upon missed approach, aircraft can climb to 6000 (by `MC411`) and fly the approach again from `ZAO`, which will simulate a full missed approach back to the IAF `HAZEL`. If the aircraft is not ready by `ZAO`, the approach is also available from `MC420` and `MC411`. Holding after missed is available at PAPA.
|
||||
|
||||
Speed management can be effective to sequence aircraft. Arrivals via the established STARs are recommended due to the congestion of airspace around `VHHH`.
|
||||
|
||||
Use care to have 34 departures climb to 6000 (+4000 by `MC420`, +5500 by `MC411`) to cross `LKC` 6000 with further climb subject to traffic conditions (arrivals via `SMT` overhead).
|
||||
|
||||
- Landing 16(C), departing 16
|
||||
|
||||
The south wind configuration.
|
||||
|
||||
The LLZ/DME approach to 16(C) is available from the IAF `ZUH`. You should not vector aircraft inside `ZUH` as these aircraft would be under control of Guangzhou after `INDUS`.
|
||||
|
||||
Upon missed approach, aircraft can climb to 4000 and fly direct to MC513 where holding is available at +3000. From `MC513`, aircraft can execute the approach via `INDUS`/`ZUH`/`MC513` at +5900 (+1800m).
|
||||
|
||||
Speed management can be effective to sequence aircraft. Arrivals via the established STARs are recommended due to the congestion of airspace around `VHHH`.
|
||||
|
||||
Use care to separate 16 departures from `VHHH` arrivals between `CANTO` and `MURRY` and `VHHH` departures near `PECAN`.
|
||||
|
||||
## Known Issues
|
||||
|
||||
- No `ZGSZ`
|
||||
- No `ZGSD`
|
||||
- No RNP Y procedures
|
||||
- No 25/34 or 07/16 configurations
|
||||
- The northern boundary is super lazy (I am not going to trace 3nm from the Chinese coastline, sorry)
|
||||
- `SIERA` C/D arrivals only selectable from `BORDA`
|
||||
- `UJ` and `MCU` transitions implemented for `VMMC` 34 but would only be used for arrivals from `ZGZU` FIR, leaving them in for the heck of it
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This is a best effort work based on air traffic observations and official aeronautical publications. No guarantee is made that this representation of VHHH TMA matches real life procedures in any way. Any information regarding inaccuracies is appreciated.
|
||||
|
||||
## For Developers
|
||||
|
||||
This file is built from `source\VHHH.txt` via `deploy.py`. Make any contributions to `source\VHHH.txt` and NOT to `.\VHHH.txt`.
|
||||
|
||||
## Changelog
|
||||
|
||||
* 1.0 - 2020/01/09 - Initial version.
|
||||
|
Before Width: | Height: | Size: 93 KiB After Width: | Height: | Size: 93 KiB |
|
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 50 KiB |
@@ -1,21 +1,21 @@
|
||||
Endless ATC [EFRO - Rovaniemi] v2.0 by Zac. Join the Endless ATC discord at https://discord.gg/v4wDGh3
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
The platform altitude for both runways is 2400ft, but descend all aircraft to 3000ft and allow them to descend further automatically.
|
||||
|
||||
The only way to make high traffic levels work at this airport is by utilising the holds.
|
||||
|
||||
Aircraft should generally fly an arrival and not be vectored at all. Where necessary, aircraft should be vectored to intercept at 10 miles at 2400ft.
|
||||
|
||||
The initial climb for all departures is 5000ft. Since some TMA exit points are also entry points, be extremely cautious giving anything above FL90 initially.
|
||||
|
||||
The minimum separation in the TMA is 5nm. Aircraft on the localiser must be separated by 7nm, as per ICAO single runway minima. During periods of high intensity arrivals, reduced minima of 3nm may be used. Departures via the same exit point must be separated by 12nm on TMA exit.
|
||||
|
||||
All arrivals which have a downwind, provided there is no need to hold, should be issued descent to be level at 6000ft abeam the airport. This will allow for continous descent. Passing around 7000ft, if no traffic is conflicting, they should be given descent to 3000ft and allowed to establish on the approach without further input.
|
||||
|
||||
Departures should simply be climbed to ensure separation from arrivals and other departures.
|
||||
|
||||
Changelog
|
||||
|
||||
Endless ATC [EFRO - Rovaniemi] v2.0 by Zac. Join the Endless ATC discord at https://discord.gg/v4wDGh3
|
||||
|
||||
---------------------------------------------------------
|
||||
|
||||
The platform altitude for both runways is 2400ft, but descend all aircraft to 3000ft and allow them to descend further automatically.
|
||||
|
||||
The only way to make high traffic levels work at this airport is by utilising the holds.
|
||||
|
||||
Aircraft should generally fly an arrival and not be vectored at all. Where necessary, aircraft should be vectored to intercept at 10 miles at 2400ft.
|
||||
|
||||
The initial climb for all departures is 5000ft. Since some TMA exit points are also entry points, be extremely cautious giving anything above FL90 initially.
|
||||
|
||||
The minimum separation in the TMA is 5nm. Aircraft on the localiser must be separated by 7nm, as per ICAO single runway minima. During periods of high intensity arrivals, reduced minima of 3nm may be used. Departures via the same exit point must be separated by 12nm on TMA exit.
|
||||
|
||||
All arrivals which have a downwind, provided there is no need to hold, should be issued descent to be level at 6000ft abeam the airport. This will allow for continous descent. Passing around 7000ft, if no traffic is conflicting, they should be given descent to 3000ft and allowed to establish on the approach without further input.
|
||||
|
||||
Departures should simply be climbed to ensure separation from arrivals and other departures.
|
||||
|
||||
Changelog
|
||||
|
||||
v1.0 - 26/04/2021 - Initial release
|
||||
@@ -1,18 +1,18 @@
|
||||
# Manchester Airport including Liverpool John Lennon Airport for Endless ATC
|
||||
|
||||
This implements Manchester Airport (EGCC) and Liverpool John Lennon Airport (EGGP) into [Endless ATC](https://steamcommunity.com/app/666610).
|
||||
|
||||
## Installation
|
||||
To install this airport you will need to copy the [EGCC.txt](./EGCC.txt) file into your steam directory, which by default for Windows 10 is at `C:\Program Files (x86)\Steam\steamapps\common`. From the common folder you need to put the file into the `Endless ATC\locations` folder.
|
||||
|
||||
## Features
|
||||
|
||||
This fully implements all published SIDs and STARs according to the charts published by [VatSIM](https://www.vatsim.uk/) on [ChartFox](https://chartfox.org/EGCC). As is normal for the UK, all STARs end in holding patterns. The published approaches have been used as a base for the approaches implemented in game. There have been some minor modifications to get them to work in game without any problems.
|
||||
|
||||
There are two configurations, one Easterly and one Westerly, which start with one runway open for landing and one for take off at EGCC. This is the way they normally operate. After you reach a score of 7 EGGP will open its single runway.
|
||||
|
||||
Airlines and the aircraft they use have been approximated using data available on [Flightradar24](https://www.flightradar24.com/data/airports/man) and random private traffic has been added in.
|
||||
|
||||
## Changelog
|
||||
|
||||
# Manchester Airport including Liverpool John Lennon Airport for Endless ATC
|
||||
|
||||
This implements Manchester Airport (EGCC) and Liverpool John Lennon Airport (EGGP) into [Endless ATC](https://steamcommunity.com/app/666610).
|
||||
|
||||
## Installation
|
||||
To install this airport you will need to copy the [EGCC.txt](./EGCC.txt) file into your steam directory, which by default for Windows 10 is at `C:\Program Files (x86)\Steam\steamapps\common`. From the common folder you need to put the file into the `Endless ATC\locations` folder.
|
||||
|
||||
## Features
|
||||
|
||||
This fully implements all published SIDs and STARs according to the charts published by [VatSIM](https://www.vatsim.uk/) on [ChartFox](https://chartfox.org/EGCC). As is normal for the UK, all STARs end in holding patterns. The published approaches have been used as a base for the approaches implemented in game. There have been some minor modifications to get them to work in game without any problems.
|
||||
|
||||
There are two configurations, one Easterly and one Westerly, which start with one runway open for landing and one for take off at EGCC. This is the way they normally operate. After you reach a score of 7 EGGP will open its single runway.
|
||||
|
||||
Airlines and the aircraft they use have been approximated using data available on [Flightradar24](https://www.flightradar24.com/data/airports/man) and random private traffic has been added in.
|
||||
|
||||
## Changelog
|
||||
|
||||
* v1.0 - 2021-08-03 - Initial release
|
||||
@@ -1,241 +1,241 @@
|
||||
#LSZH V1.2 - Beaso14
|
||||
#Updated Runway Configurations
|
||||
#Updated Fleet List and Rank using Wikipedia data
|
||||
#Updated Fleet Aircraft using data fro, planespotters.net, although didn't find the Swiss aircraft that are 'not within the swiss fleet anymore' - Codelyokp?
|
||||
#Fleets are now at a reasonably realistic level imho
|
||||
#Changed airport name to "Zurich" as the game seems to use ASCII rather than UNICODE and cannot read the accented "U"
|
||||
#Oh - and the ALT restrictions around LSZH are *crazy hard* to do, (many circles and wavy) polygons - I simplified them massively. If somebody wants to spend hours pinpointing Northings and Eastings, be my guest :)
|
||||
#SID's have been implemented - (just, haha). Currently only "Direct" style departures seem to be allowed, I have contacted Startgrid about this on Itch.io
|
||||
#Expect more complicated and automatic departures in future - fingers crossed.
|
||||
#There are still some pronunciation issues with the airline names (and potentially SID names)
|
||||
#STAR's. Ah. I'm not sure what to do with Zurich's stars, considering most if not all of them start way beyond the 30NM radius of the airport. (Get to a config where rwy 32 or 34 is in use for landings, and find KELIP to the south. It's a long way away! So either we increase the radius, adding more airports, or simplify the STAR's. Awaiting guidance on that tbh.
|
||||
[airspace]
|
||||
elevation = 1416
|
||||
floor = 3000
|
||||
ceiling = 8000
|
||||
above = 17000
|
||||
transitionlevel = 9001
|
||||
center = N47.464699, E8.54917
|
||||
magneticvar = 0.315
|
||||
beacons =
|
||||
KLO, N47.45710, E8.54558, 0, Kloten
|
||||
ZUE, N47.59220, E8.81767, 0, Zurich East
|
||||
TRA, N47.68950, E8.43695, 0, Trasadingen
|
||||
DON, N47.96070, E8.52255, 0, Donaueschingen
|
||||
WIL, N47.17830, E7.90592, 0, Willisau
|
||||
HOC, N47.46660, E7.66544, 0, Hochwald
|
||||
FHD, N47.66640, E9.50886, 0, Friedrichshafen
|
||||
BLM, N47.63280, E7.49950, 0, Bale Mulhouse
|
||||
MEG, N48.05440, E9.36755, 0, Mengen
|
||||
GRE, N47.18320, E7.41818, 0, Grenchen
|
||||
MUR, N46.94610, E7.46687, 0, Muri
|
||||
SHU, N47.02180, E7.39194, 0, Schupberg
|
||||
BER, N46.89910, E7.51048, 0, Bern
|
||||
CLR, N47.92930, E7.39997, 0, Colmar
|
||||
|
||||
line1 =
|
||||
N47.52690, E9.73066
|
||||
N47.51489, E9.71855
|
||||
N47.50640, E9.68545
|
||||
N47.51113, E9.55439
|
||||
N47.51396, E9.45234
|
||||
N47.59795, E9.25029
|
||||
N47.67070, E9.18281
|
||||
N47.77212, E9.11318
|
||||
N47.78218, E9.13203
|
||||
N47.73330, E9.23076
|
||||
N47.67666, E9.37285
|
||||
N47.62476, E9.51396
|
||||
N47.56636, E9.64424
|
||||
N47.52690, E9.73066
|
||||
|
||||
line2 =
|
||||
N47.67068, E9.12754
|
||||
N47.65639, E8.88114
|
||||
N47.67068, E9.18283
|
||||
N47.51116, E9.55438
|
||||
|
||||
line3 =
|
||||
N48.04681, E8.21979
|
||||
N47.93072, E8.49006
|
||||
N47.93630, E8.69583
|
||||
N47.97635, E8.83587
|
||||
N48.05270, E8.97871
|
||||
N48.08642, E9.13188
|
||||
N48.07753, E9.29538
|
||||
N48.11613, E9.42106
|
||||
N48.20233, E9.50880
|
||||
N48.24395, E9.58870
|
||||
N48.24098, E9.66073
|
||||
N48.28909, E9.78403
|
||||
N48.38826, E9.95880
|
||||
N48.45291, E10.12717
|
||||
|
||||
line4 =
|
||||
N46.67632, E8.75082
|
||||
N46.75777, E9.04558
|
||||
N46.83461, E9.41558
|
||||
N46.83461, E9.40876
|
||||
N46.90675, E9.51676
|
||||
N46.96308, E9.53382
|
||||
N47.02765, E9.49589
|
||||
N47.09751, E9.47945
|
||||
N47.17268, E9.48431
|
||||
N47.27076, E9.52751
|
||||
N47.39178, E9.60906
|
||||
N47.46703, E9.62590
|
||||
N47.51116, E9.55438
|
||||
N47.67068, E9.12754
|
||||
N47.67068, E9.18283
|
||||
|
||||
line5 =
|
||||
N47.65639, E8.88114
|
||||
N47.68629, E8.70017
|
||||
N47.66236, E8.61976
|
||||
N47.59467, E8.57966
|
||||
N47.57617, E8.48230
|
||||
N47.60691, E8.32779
|
||||
N47.60691, E8.19829
|
||||
N47.57617, E8.09380
|
||||
N47.56384, E7.92709
|
||||
N47.56989, E7.69806
|
||||
N47.60655, E7.56546
|
||||
N47.67389, E7.52939
|
||||
N47.77362, E7.53859
|
||||
N47.90566, E7.59326
|
||||
N48.00257, E7.60846
|
||||
N48.06430, E7.58417
|
||||
N48.15680, E7.61662
|
||||
N48.28005, E7.70571
|
||||
N48.41002, E7.76514
|
||||
|
||||
[airport1]
|
||||
name = Zurich Airport
|
||||
code = LSZH
|
||||
runways =
|
||||
rwy1, 10, N47.4589, E8.53747, 96.0, 8202, 0, 0, 1391, 3, 94
|
||||
rwy2, 14, N47.4831, E8.53473, 137.2, 10827, 490, 0, 1402, 3, 135
|
||||
rwy3, 16, N47.4756, E8.53595, 155.0, 12139, 0, 1541, 1390, 3, 154
|
||||
## identifier, name, position, true_heading, <length>, <displaced>, <displaced2>, <elevation>, <glideslope>, <localizer>, <glideslope2>, <localizer2>, <beaconname, distance>, <beaconname2, distance2>
|
||||
|
||||
sids =
|
||||
wil
|
||||
zue
|
||||
deges, N47.248, E9.121, deges
|
||||
gersa, N47.024, E8.319, gersa
|
||||
vevit, N47.161, E8.004, vebit
|
||||
|
||||
|
||||
airlines =
|
||||
swr, 10, a320/a321/bcs1/bcs3/a333/a343/b77w/a20n/a21n, swiss
|
||||
edw, 9, a320/a333/a343, edelweiss
|
||||
ezy, 8, a320/a32n/a321, easyjet
|
||||
ewg, 7, a320/a319/a333, eurowings
|
||||
oaw, 5, e190/e195, helvetica
|
||||
tap, 3, a319/a320/a20n/a21n/a321/a332/a339/e190, airportugal
|
||||
vue, 2, a319/a320/a321, vueling
|
||||
aua, 2, a319/a320/a321/b767/dh8d/e190, austrian
|
||||
dlh, 2, a319/a320/a321/a21n/a20n, lufthansa
|
||||
ctn, 1, a319/a320/dh8d, croatian
|
||||
amc, 1, a320, airmalta
|
||||
ual, 1, b752/b753/b763/b772/b773/b78x/b789/b788, united
|
||||
qtr, 1, a332/a333/a35k/b748/b772/b773/b788/b789/a359, qatari
|
||||
klm, 1, b738/b739/b737/b772/b773/a332/a333, klm
|
||||
sxs, 1, b738, sunexpress
|
||||
aee, 1, a320/a321, aegean
|
||||
aza, 1, a319/a320/e175, alitalia
|
||||
ice, 1, b752/b763urkish, icelandic
|
||||
tur, 1, a319/a320/a321/a21n/a332/a333/b738/b739/b773/b789, turkish
|
||||
aer, 1, a320/a321/a333/b738/b773, aeroflot
|
||||
sin, 1, a333/a388/b744/b773/b78x/a359, singapore
|
||||
baw, 1, a319/a320/a21n/b772/b773/b788/b789/b78x/a20n, speedbird
|
||||
|
||||
##############################################################
|
||||
[area1]
|
||||
##############################################################
|
||||
shape = circle ; circle or polygon
|
||||
altitude = 4000 ; minimum allowed altitude in feet
|
||||
radius = 10 ; radius of circle in NM
|
||||
position = 0, 0 ; position of circle center
|
||||
labelpos = 6, 0 ; <position of label>
|
||||
|
||||
##############################################################
|
||||
[area2]
|
||||
##############################################################
|
||||
shape = circle ; circle or polygon
|
||||
altitude = 5000 ; minimum allowed altitude in feet
|
||||
radius = 20 ; radius of circle in NM
|
||||
position = 0, 0 ; position of circle center
|
||||
labelpos = 20, 0 ; <position of label>
|
||||
|
||||
##############################################################
|
||||
[area3]
|
||||
##############################################################
|
||||
shape = circle ; circle or polygon
|
||||
altitude = 6000 ; minimum allowed altitude in feet
|
||||
radius = 30 ; radius of circle in NM
|
||||
position = 0, 0 ; position of circle center
|
||||
labelpos = 30, 0 ; <position of label>
|
||||
|
||||
|
||||
##############################################################
|
||||
[transition1]
|
||||
##############################################################
|
||||
|
||||
runway = rwy3, rev ; runway identifier, <reversed use>
|
||||
beacon = kelip, N46.574, E8.457, 0, kelip ; selectable beacon to enable NAV mode; define a beacon, or choose a name from beacon list above
|
||||
route1 =
|
||||
100
|
||||
N46.574, E8.457, 14000, 210
|
||||
N47.042, E8.446, 10000
|
||||
N47.163, E8.427, 8000, 180
|
||||
N47.199, E8.421, 7000, 180
|
||||
10.5, 7000, 200
|
||||
# first item of the route is the bearing from the plane towards the beacon; if there are multiple routes defined, the closest bearing defines which route is selected.
|
||||
# next lines are optional waypoints: ## location, <maximum altitude>, <maximum speed>
|
||||
# last line is the interception point on the ILS: ## distance (NM) from the threshold, <maximum altitude>, <maximum speed>
|
||||
|
||||
route2 =
|
||||
240
|
||||
1, 18, 4000
|
||||
-3, 18, 0, 180
|
||||
10.5, 3000, 200
|
||||
|
||||
route3 =
|
||||
020
|
||||
1, 10
|
||||
1, 18, 4000
|
||||
-3, 18, 0, 180
|
||||
10.5, 3000, 200
|
||||
|
||||
# multiple [transition] sections can be used for the same runway
|
||||
|
||||
|
||||
##############################################################
|
||||
[planetypes]
|
||||
##############################################################
|
||||
|
||||
##############################################################
|
||||
[configurations]
|
||||
##############################################################
|
||||
config1 =
|
||||
0, rwy2, land
|
||||
8, rwy3, startland
|
||||
9, rwy1, takeoff rev
|
||||
|
||||
config2 =
|
||||
0, rwy3, land rev
|
||||
8, rwy2, land rev
|
||||
9, rwy1, takeoff rev
|
||||
|
||||
config3 =
|
||||
0, rwy1, startland rev
|
||||
0, rwy2, takeoff
|
||||
8, rwy3, takeoff
|
||||
|
||||
|
||||
config4 =
|
||||
0, rwy1, startland rev
|
||||
0, rwy2, takeoff rev
|
||||
8, rwy3, takeoff rev
|
||||
|
||||
#LSZH V1.2 - Beaso14
|
||||
#Updated Runway Configurations
|
||||
#Updated Fleet List and Rank using Wikipedia data
|
||||
#Updated Fleet Aircraft using data fro, planespotters.net, although didn't find the Swiss aircraft that are 'not within the swiss fleet anymore' - Codelyokp?
|
||||
#Fleets are now at a reasonably realistic level imho
|
||||
#Changed airport name to "Zurich" as the game seems to use ASCII rather than UNICODE and cannot read the accented "U"
|
||||
#Oh - and the ALT restrictions around LSZH are *crazy hard* to do, (many circles and wavy) polygons - I simplified them massively. If somebody wants to spend hours pinpointing Northings and Eastings, be my guest :)
|
||||
#SID's have been implemented - (just, haha). Currently only "Direct" style departures seem to be allowed, I have contacted Startgrid about this on Itch.io
|
||||
#Expect more complicated and automatic departures in future - fingers crossed.
|
||||
#There are still some pronunciation issues with the airline names (and potentially SID names)
|
||||
#STAR's. Ah. I'm not sure what to do with Zurich's stars, considering most if not all of them start way beyond the 30NM radius of the airport. (Get to a config where rwy 32 or 34 is in use for landings, and find KELIP to the south. It's a long way away! So either we increase the radius, adding more airports, or simplify the STAR's. Awaiting guidance on that tbh.
|
||||
[airspace]
|
||||
elevation = 1416
|
||||
floor = 3000
|
||||
ceiling = 8000
|
||||
above = 17000
|
||||
transitionlevel = 9001
|
||||
center = N47.464699, E8.54917
|
||||
magneticvar = 0.315
|
||||
beacons =
|
||||
KLO, N47.45710, E8.54558, 0, Kloten
|
||||
ZUE, N47.59220, E8.81767, 0, Zurich East
|
||||
TRA, N47.68950, E8.43695, 0, Trasadingen
|
||||
DON, N47.96070, E8.52255, 0, Donaueschingen
|
||||
WIL, N47.17830, E7.90592, 0, Willisau
|
||||
HOC, N47.46660, E7.66544, 0, Hochwald
|
||||
FHD, N47.66640, E9.50886, 0, Friedrichshafen
|
||||
BLM, N47.63280, E7.49950, 0, Bale Mulhouse
|
||||
MEG, N48.05440, E9.36755, 0, Mengen
|
||||
GRE, N47.18320, E7.41818, 0, Grenchen
|
||||
MUR, N46.94610, E7.46687, 0, Muri
|
||||
SHU, N47.02180, E7.39194, 0, Schupberg
|
||||
BER, N46.89910, E7.51048, 0, Bern
|
||||
CLR, N47.92930, E7.39997, 0, Colmar
|
||||
|
||||
line1 =
|
||||
N47.52690, E9.73066
|
||||
N47.51489, E9.71855
|
||||
N47.50640, E9.68545
|
||||
N47.51113, E9.55439
|
||||
N47.51396, E9.45234
|
||||
N47.59795, E9.25029
|
||||
N47.67070, E9.18281
|
||||
N47.77212, E9.11318
|
||||
N47.78218, E9.13203
|
||||
N47.73330, E9.23076
|
||||
N47.67666, E9.37285
|
||||
N47.62476, E9.51396
|
||||
N47.56636, E9.64424
|
||||
N47.52690, E9.73066
|
||||
|
||||
line2 =
|
||||
N47.67068, E9.12754
|
||||
N47.65639, E8.88114
|
||||
N47.67068, E9.18283
|
||||
N47.51116, E9.55438
|
||||
|
||||
line3 =
|
||||
N48.04681, E8.21979
|
||||
N47.93072, E8.49006
|
||||
N47.93630, E8.69583
|
||||
N47.97635, E8.83587
|
||||
N48.05270, E8.97871
|
||||
N48.08642, E9.13188
|
||||
N48.07753, E9.29538
|
||||
N48.11613, E9.42106
|
||||
N48.20233, E9.50880
|
||||
N48.24395, E9.58870
|
||||
N48.24098, E9.66073
|
||||
N48.28909, E9.78403
|
||||
N48.38826, E9.95880
|
||||
N48.45291, E10.12717
|
||||
|
||||
line4 =
|
||||
N46.67632, E8.75082
|
||||
N46.75777, E9.04558
|
||||
N46.83461, E9.41558
|
||||
N46.83461, E9.40876
|
||||
N46.90675, E9.51676
|
||||
N46.96308, E9.53382
|
||||
N47.02765, E9.49589
|
||||
N47.09751, E9.47945
|
||||
N47.17268, E9.48431
|
||||
N47.27076, E9.52751
|
||||
N47.39178, E9.60906
|
||||
N47.46703, E9.62590
|
||||
N47.51116, E9.55438
|
||||
N47.67068, E9.12754
|
||||
N47.67068, E9.18283
|
||||
|
||||
line5 =
|
||||
N47.65639, E8.88114
|
||||
N47.68629, E8.70017
|
||||
N47.66236, E8.61976
|
||||
N47.59467, E8.57966
|
||||
N47.57617, E8.48230
|
||||
N47.60691, E8.32779
|
||||
N47.60691, E8.19829
|
||||
N47.57617, E8.09380
|
||||
N47.56384, E7.92709
|
||||
N47.56989, E7.69806
|
||||
N47.60655, E7.56546
|
||||
N47.67389, E7.52939
|
||||
N47.77362, E7.53859
|
||||
N47.90566, E7.59326
|
||||
N48.00257, E7.60846
|
||||
N48.06430, E7.58417
|
||||
N48.15680, E7.61662
|
||||
N48.28005, E7.70571
|
||||
N48.41002, E7.76514
|
||||
|
||||
[airport1]
|
||||
name = Zurich Airport
|
||||
code = LSZH
|
||||
runways =
|
||||
rwy1, 10, N47.4589, E8.53747, 96.0, 8202, 0, 0, 1391, 3, 94
|
||||
rwy2, 14, N47.4831, E8.53473, 137.2, 10827, 490, 0, 1402, 3, 135
|
||||
rwy3, 16, N47.4756, E8.53595, 155.0, 12139, 0, 1541, 1390, 3, 154
|
||||
## identifier, name, position, true_heading, <length>, <displaced>, <displaced2>, <elevation>, <glideslope>, <localizer>, <glideslope2>, <localizer2>, <beaconname, distance>, <beaconname2, distance2>
|
||||
|
||||
sids =
|
||||
wil
|
||||
zue
|
||||
deges, N47.248, E9.121, deges
|
||||
gersa, N47.024, E8.319, gersa
|
||||
vevit, N47.161, E8.004, vebit
|
||||
|
||||
|
||||
airlines =
|
||||
swr, 10, a320/a321/bcs1/bcs3/a333/a343/b77w/a20n/a21n, swiss
|
||||
edw, 9, a320/a333/a343, edelweiss
|
||||
ezy, 8, a320/a32n/a321, easyjet
|
||||
ewg, 7, a320/a319/a333, eurowings
|
||||
oaw, 5, e190/e195, helvetica
|
||||
tap, 3, a319/a320/a20n/a21n/a321/a332/a339/e190, airportugal
|
||||
vue, 2, a319/a320/a321, vueling
|
||||
aua, 2, a319/a320/a321/b767/dh8d/e190, austrian
|
||||
dlh, 2, a319/a320/a321/a21n/a20n, lufthansa
|
||||
ctn, 1, a319/a320/dh8d, croatian
|
||||
amc, 1, a320, airmalta
|
||||
ual, 1, b752/b753/b763/b772/b773/b78x/b789/b788, united
|
||||
qtr, 1, a332/a333/a35k/b748/b772/b773/b788/b789/a359, qatari
|
||||
klm, 1, b738/b739/b737/b772/b773/a332/a333, klm
|
||||
sxs, 1, b738, sunexpress
|
||||
aee, 1, a320/a321, aegean
|
||||
aza, 1, a319/a320/e175, alitalia
|
||||
ice, 1, b752/b763urkish, icelandic
|
||||
tur, 1, a319/a320/a321/a21n/a332/a333/b738/b739/b773/b789, turkish
|
||||
aer, 1, a320/a321/a333/b738/b773, aeroflot
|
||||
sin, 1, a333/a388/b744/b773/b78x/a359, singapore
|
||||
baw, 1, a319/a320/a21n/b772/b773/b788/b789/b78x/a20n, speedbird
|
||||
|
||||
##############################################################
|
||||
[area1]
|
||||
##############################################################
|
||||
shape = circle ; circle or polygon
|
||||
altitude = 4000 ; minimum allowed altitude in feet
|
||||
radius = 10 ; radius of circle in NM
|
||||
position = 0, 0 ; position of circle center
|
||||
labelpos = 6, 0 ; <position of label>
|
||||
|
||||
##############################################################
|
||||
[area2]
|
||||
##############################################################
|
||||
shape = circle ; circle or polygon
|
||||
altitude = 5000 ; minimum allowed altitude in feet
|
||||
radius = 20 ; radius of circle in NM
|
||||
position = 0, 0 ; position of circle center
|
||||
labelpos = 20, 0 ; <position of label>
|
||||
|
||||
##############################################################
|
||||
[area3]
|
||||
##############################################################
|
||||
shape = circle ; circle or polygon
|
||||
altitude = 6000 ; minimum allowed altitude in feet
|
||||
radius = 30 ; radius of circle in NM
|
||||
position = 0, 0 ; position of circle center
|
||||
labelpos = 30, 0 ; <position of label>
|
||||
|
||||
|
||||
##############################################################
|
||||
[transition1]
|
||||
##############################################################
|
||||
|
||||
runway = rwy3, rev ; runway identifier, <reversed use>
|
||||
beacon = kelip, N46.574, E8.457, 0, kelip ; selectable beacon to enable NAV mode; define a beacon, or choose a name from beacon list above
|
||||
route1 =
|
||||
100
|
||||
N46.574, E8.457, 14000, 210
|
||||
N47.042, E8.446, 10000
|
||||
N47.163, E8.427, 8000, 180
|
||||
N47.199, E8.421, 7000, 180
|
||||
10.5, 7000, 200
|
||||
# first item of the route is the bearing from the plane towards the beacon; if there are multiple routes defined, the closest bearing defines which route is selected.
|
||||
# next lines are optional waypoints: ## location, <maximum altitude>, <maximum speed>
|
||||
# last line is the interception point on the ILS: ## distance (NM) from the threshold, <maximum altitude>, <maximum speed>
|
||||
|
||||
route2 =
|
||||
240
|
||||
1, 18, 4000
|
||||
-3, 18, 0, 180
|
||||
10.5, 3000, 200
|
||||
|
||||
route3 =
|
||||
020
|
||||
1, 10
|
||||
1, 18, 4000
|
||||
-3, 18, 0, 180
|
||||
10.5, 3000, 200
|
||||
|
||||
# multiple [transition] sections can be used for the same runway
|
||||
|
||||
|
||||
##############################################################
|
||||
[planetypes]
|
||||
##############################################################
|
||||
|
||||
##############################################################
|
||||
[configurations]
|
||||
##############################################################
|
||||
config1 =
|
||||
0, rwy2, land
|
||||
8, rwy3, startland
|
||||
9, rwy1, takeoff rev
|
||||
|
||||
config2 =
|
||||
0, rwy3, land rev
|
||||
8, rwy2, land rev
|
||||
9, rwy1, takeoff rev
|
||||
|
||||
config3 =
|
||||
0, rwy1, startland rev
|
||||
0, rwy2, takeoff
|
||||
8, rwy3, takeoff
|
||||
|
||||
|
||||
config4 =
|
||||
0, rwy1, startland rev
|
||||
0, rwy2, takeoff rev
|
||||
8, rwy3, takeoff rev
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user