RJBB ACA 4.0.0 + tools 0.12.0
This commit is contained in:
Calvin Ng
+8464
-2575
File diff suppressed because it is too large
Load Diff
+132
-72
@@ -1,4 +1,4 @@
|
||||
# `RJBB` ACA 3.1.0
|
||||
# `RJBB` ACA 4.0.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.
|
||||
|
||||
@@ -12,7 +12,7 @@ The published STARs for the aerodromes in the Kansai ACA typically do not have "
|
||||
|
||||
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.
|
||||
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
|
||||
|
||||
@@ -24,13 +24,21 @@ There is custom traffic for `RJBB`. The proportions are very much estimates but
|
||||
|
||||
Many fixes visible on the map have a defined hold including some key fixes along the STARs.
|
||||
|
||||
Aircraft arrive at:
|
||||
Aircraft will enter the ACA and fly along their flight planned routes and hold at the last point on their route provided no further instruction is issued. Aircraft can be further cleared for the STAR & approach via any points up to and including the route endpoint. STARs can also be resumed at most points along the STAR, and aircraft can be cleared for the approach directly from the IF or FAF. The route endpoints and corresponding arrival routes are:
|
||||
|
||||
- (`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)
|
||||
- `ALISA`
|
||||
- `Y36 ALISA`: `TONBI SAEKI ALISA` (northwest from Korea/northern China)
|
||||
- `Y361 SAEKI Y36 ALISA`: `SPICE SAEKI ALISA` (northeast from NE Japan, Europe)
|
||||
- `BERTH`
|
||||
- `Y35 BERTH`: `(Y35) RANDY BERTH` (west from Fukuoka, western Japan, China)
|
||||
- `BECKY`
|
||||
- `Y53 BECKY`: `KARIN BECKY` (southwest from southwestern Japan, Taiwan, HK, Singapore, Malaysia, etc.)
|
||||
- `CANDY`
|
||||
- `Y46 CANDY`: `EVERT CANDY` (southwest from Philippines, south from Indonesia/Oceania, east from Nagoya/PACOTS)
|
||||
- `DANDE`
|
||||
- `Y544 DANDE`: `(Y544) SINGU RIDGE DANDE` (east from `RJTT` Tokyo, `RJAA` Narita, `RJSS` Sendai, `RJSF` Fukushima)
|
||||
|
||||
It is recommended that arrivals via `Y544` cross `DANDE` (or `DINAH`) at 10000 for separation from arrivals to `RJOO` at 11000 over `KAINA`. An alternate route for `Y544` arrivals with a longer track is also available via `SOMEI DINAH GOBOH UBUYU DATIS`.
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
@@ -49,37 +57,35 @@ 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.
|
||||
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.
|
||||
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, but RWY A is often the sole runway in use.
|
||||
|
||||
There are two landing configurations:
|
||||
|
||||
- Landing/departing RWY 06L/06R
|
||||
|
||||
This is the preferred configuration for RJBB.
|
||||
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.
|
||||
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.
|
||||
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.
|
||||
Vectors onto the localizer should NOT be used. Approaches are available from IAF `MAYAH` (24L/24R), or IFs `AMBER` (24L) and `BEIGE` (24R). Arrivals can be vectored over the sea west of Awaji Island if needed on top of `RJBE` arrivals (watch for `RJOT` 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.
|
||||
Use care not to descend arrivals into the `RJBE` PCA. Cross `JOLLY` (from `DANDE`) +8000, `AWAJI` +7000, `MAYAH` 4000 (**at** 4000). Strongly recommend aircraft cross `LILAC` at 4000 (descend after passing `AWAJI`). Aircraft should descend as per the approach after `MAYAH` in order to main separation from `RJBE` traffic landing 27 below descending 1600 on downwind to 800 on final.
|
||||
|
||||
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 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, such as restricting 24R departures to `HELEN` and `DAISY` to 210kts, expediting climb, etc. 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.
|
||||
Departures to the south may conflict with arrivals from `DANDE` and the south/southwest. Use caution.
|
||||
|
||||
### `RJOO` Osaka International Airport
|
||||
|
||||
@@ -87,13 +93,21 @@ An airport near the heart of Osaka, only domestic traffic is handled aside from
|
||||
|
||||
There is custom traffic for `RJOO`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
Aircraft will enter the ACA and fly along their flight planned routes and hold at the last point on their route provided no further instruction is issued. Aircraft can be further cleared for the STAR & approach via any points up to and including the route endpoint. STARs can also be resumed at most points along the STAR, and aircraft can be cleared for the approach directly from the IF or FAF. The route endpoints and corresponding arrival routes are:
|
||||
|
||||
- `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)
|
||||
- `IKOMA`
|
||||
- via `ROKKO`
|
||||
- `Y384 ROKKO`: `(Y384) ROKKO` (northeast from northeastern Japan)
|
||||
- `Y38 ROKKO`: `TOZAN ROKKO` (northwest from northwestern Japan)
|
||||
- `RJBT.../RJOR YME V55.../RJOH YME V55...ROKKO`: `(GUNZE) ROKKO` (northwest from `RJBT`, `RJOR`, `RJOH`)
|
||||
- The STAR from `ROKKO` is flight planned; aircraft continue to `IKOMA` via `ROKKO KAMEO OTABE ABENO IKOMA`
|
||||
- via `KODAI`
|
||||
- `Y546 KODAI`: `OHDAI KODAI` (east from eastern Japan)
|
||||
- The STAR from `KODAI` is flight planned; aircraft continue to `IKOMA` via `KODAI MIRAI ABENO IKOMA`
|
||||
- `IZUMI`
|
||||
- `Y401 KAINA Y753 IZUMI`: `RIVER ZOROH KAZRA MIRIO KAINA IZUMI` (west from western Japan for `DH8D` aircraft)
|
||||
- `Y231 MIRIO Y401 KAINA Y753 IZUMI`: `(Y231) JANGO BECKY MIRIO KAINA IZUMI` (west from western Japan)
|
||||
- `Y753 IZUMI`: `MUGIE HONMA KAINA IZUMI` -> `HONMA` -> `KAINA` -> `IZUMI` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
@@ -109,15 +123,15 @@ 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.
|
||||
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`.
|
||||
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 `RJOY` 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.
|
||||
The missed approach hold is `IZUMI` +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
@@ -143,17 +157,20 @@ A smaller airport in Osaka Bay minutes from central Kobe. Located under to appro
|
||||
|
||||
There is custom traffic for `RJBE`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
Aircraft will enter the ACA and fly along their flight planned routes and hold at the last point on their route provided no further instruction is issued. Aircraft can be further cleared for the STAR & approach via any points up to and including the route endpoint. STARs can also be resumed at most points along the STAR, and aircraft can be cleared for the approach directly from the IF or FAF. The route endpoints and corresponding arrival routes are:
|
||||
|
||||
- `GINJI` (east from eastern Japan)
|
||||
- `WAKIT` (northeast from northeastern Japan)
|
||||
- `RANDY` -> `BERTH` (west from western Japan)
|
||||
- `KARIN` -> `BECKY` (southwest from southwestern Japan)
|
||||
- `TRACY`
|
||||
- `Y20 WAKIT Y201 TRACY`: `ARASI GINJI WAKIT TRACY` (east from eastern Japan)
|
||||
- `Y382 WAKIT Y201 TRACY`: `(Y382) WAKIT TRACY` (northeast from northeastern Japan)
|
||||
- `BERTH`
|
||||
- `Y35 BERTH`: `(Y35) RANDY BERTH` (west from western Japan)
|
||||
- `BECKY`
|
||||
- `Y53 BECKY`: `(Y53) KARIN BECKY` (southwest from southwestern Japan)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east for Tokyo)
|
||||
- `CUE` (east to eastern Japan)
|
||||
- `MIDER` (east to eastern Japan)
|
||||
- `YME` (northeast to Tohoku/Hokkaido)
|
||||
- `SOUJA` (west to north Kyushu)
|
||||
- `WASYU` (west to western Japan, central Kyushu)
|
||||
@@ -161,45 +178,53 @@ Aircraft depart via:
|
||||
|
||||
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.
|
||||
Arrivals can be vectored over the sea west of Awaji Island (the island under `AWAJI` waypoint). If vectoring far and high, use caution for `RJOT` arrivals descending from `WAKIT` southwest towards `POPAI`.
|
||||
|
||||
Departures may conflict with other aircraft on west departures or arrivals to `RJOT`/`RJOB`. Use caution.
|
||||
|
||||
The missed approach hold is SIOJI +3000.
|
||||
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.
|
||||
The preferred runway configuration.
|
||||
|
||||
Departures make a climbing right turn to **1500** to depart to the west remaining under `RJBB` departures and over `RJBE` arrivals. The controller will need to issue to climb past 4000 to stay above arrivals to 09 before joining the outbound course to `MAIKO`. If `RJBB` is landing 24s, departures need to keep below `RJBB` arrivals passing `MAYAH` at 4000 descending to 2600.
|
||||
|
||||
- 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.
|
||||
The west wind configuration.
|
||||
|
||||
Departures will need to climb to 4000 or higher to clear arrivals at 3000.
|
||||
Arrivals circle to land 27; however as Endless ATC does not have circle to land approaches, arrivals make a long downwind to 27. They should be able to maintain separation even while turning to base with RJBB arrivals leaving 2600.
|
||||
|
||||
Departures will climb straight out to **3000** bound for `MAIKO`. Use caution not to issue further climb before clear of `RJBB` arrivals.
|
||||
|
||||
### `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.
|
||||
A joint-use civilian airport and JSDF-M base. Training operations with Beech King Airs are conducted by the JSDF-M from this base, and there are occasionally transiting JSDF aircraft. 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:
|
||||
Aircraft will enter the ACA and fly along their flight planned routes and hold at the last point on their route provided no further instruction is issued. Aircraft can be further cleared for the approach via any points up to and including the route endpoint. Aircraft can also be cleared for the approach directly from the IF or FAF. The route endpoints and corresponding arrival routes are:
|
||||
|
||||
- `JOSIN` (southeast to training areas?)
|
||||
- `SINGU` -> ... -> `DATIS` (east from Tokyo)
|
||||
- `KTE` -> `KULUL` -> `TSC` (west from Fukuoka)
|
||||
- `DATIS`
|
||||
- `Y544 SINGU Y542 DATIS`: `SINGU SOMEI DINAH GOBOH UBUYU DATIS` (east from Tokyo)
|
||||
- `TSC`
|
||||
- `KEC JOSIN TSC`: `(KEC30) JOSIN TSC` (southeast from training areas?)
|
||||
- `Y33 KTE KULUL TSC`: `SAKAI KOMPI KTE KULUL TSC` (west from Fukuoka)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KMANO` (east for Tokyo)
|
||||
- `KMANO` -> `KILAP` (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.
|
||||
Departures may conflict with other aircraft on southwest departures and `RJBB` `BECKY`/`CANDY` arrivals. Use caution.
|
||||
|
||||
The missed approach hold is TSC/DATIS +3000.
|
||||
Radar vectors to `DATIS` or to final for ILS 29 are possible options for arrivals from `JOSIN` instead of the ILS from `TSC`.
|
||||
|
||||
The missed approach hold is `TSC`/`DATIS` +3000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
@@ -217,19 +242,21 @@ 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:
|
||||
Aircraft will enter the ACA and fly along their flight planned routes and hold at the last point on their route provided no further instruction is issued. Aircraft can be further cleared for the STAR & approach via any points up to and including the route endpoint. STARs can also be resumed at most points along the STAR, and aircraft can be cleared for the approach directly from the IF or FAF. The route endpoints and corresponding arrival routes are:
|
||||
|
||||
- `GINJI` (east)
|
||||
- (`TAKMA`) -> `KTE` (west/southwest)
|
||||
- (`YUBAR`) -> `OYE` -> `KTE` (northwest)
|
||||
- `WIMPY`
|
||||
- `Y20 WAKIT Y203 WIMPY` (east)
|
||||
- `KTE`
|
||||
- `Y288 TAKMA KTE`: `TAKMA KTE` (west/southwest)
|
||||
- `Y39 OYE KTE`: `YUBAR OYE KTE` (northwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `SHTLE` (east)
|
||||
- `WASYU` (west)
|
||||
- `TAROH` (north)
|
||||
- `MIHOU` (north)
|
||||
|
||||
The missed approach hold is KTE +5000.
|
||||
The missed approach hold is `KTE` +5000.
|
||||
|
||||
There are two simple runway configurations:
|
||||
|
||||
@@ -247,12 +274,13 @@ 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:
|
||||
Aircraft will enter the ACA and fly along their flight planned routes and hold at the last point on their route provided no further instruction is issued. Aircraft can be further cleared for the approach via any points up to and including the route endpoint. Aircraft can also be cleared for the approach directly from the IF or FAF. The route endpoints and corresponding arrival routes are:
|
||||
|
||||
- `GINJI` (east)
|
||||
- `WAKIT` (northeast)
|
||||
- (`YUBAR`) -> `OYE`(north)
|
||||
- (`TAKMA`) -> `INOOK` (west/southwest)
|
||||
- `OYE`
|
||||
- `Y20 WAKIT Y205 OYE`: `ARASI GINJI WAKIT TRIPY MIMMY SIMAG BENES OYE` (east)
|
||||
- `Y382 WAKIT Y205 OYE`: `(Y382) WAKIT TRIPY MIMMY SIMAG BENES OYE` (northeast)
|
||||
- `Y39 OYE`: `YUBAR OYE` (northwest)
|
||||
- `Y288 INOOK OYE`: `TAKMA INOOK OYE` (west/southwest)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
@@ -267,33 +295,38 @@ 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.
|
||||
The preferred runway configuration for arrivals from the west. A straight-in ILS approach for arrivals from `TAKMA` is available via `INOOK`. A RNAV RNP 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 approach 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.
|
||||
The preferred runway configuration for arrivals from the east. The straight-in to 25 is an RNAV RNP approach as there is no ILS for 25. A transition to final is available from `BENES`.
|
||||
|
||||
### `RJOY` Yao Airport
|
||||
|
||||
A small airport near Osaka that acts as a general aviation gateway.
|
||||
A small airport near Osaka that acts as a general aviation hub.
|
||||
|
||||
There is custom traffic for `RJOY`. The proportions are very much estimates but shouldn't be too far off from reality.
|
||||
|
||||
Aircraft arrive at:
|
||||
Aircraft will enter the ACA and fly along their flight planned routes and hold at the last point on their route provided no further instruction is issued. Aircraft can be further cleared for the approach via any points up to and including the route endpoint. Aircraft can also be cleared for the approach directly from the IF or FAF. The route endpoints and corresponding arrival routes are:
|
||||
|
||||
- (`MIDER`) -> `ITE` (east)
|
||||
- `ROKKO` (north)
|
||||
- (`YUBAR`) -> `OYE`(northwest)
|
||||
- (`KAIFU` -> `IZARI`) -> `MIKAN` (west/southwest)
|
||||
- (`NORAN`) -> `IZUMI` (southeast)
|
||||
- `IZUMI`
|
||||
- `V28 ITE V55 IZUMI`: `MIDER ITE IZUMI` (east)
|
||||
- `(YME) V55 IZUMI`: `GUNZE ROKKO SANDA ITE IZUMI` (north)
|
||||
- `Y384 ROKKO V55 IZUMI`: `(Y384) ROKKO SANDA ITE IZUMI` (northeast)
|
||||
- `Y38 ROKKO V55 IZUMI`: `TOZAN ROKKO SANDA ITE IZUMI` (northwest)
|
||||
- `(KRE) KAIFU IZARI MIKAN IZUMI`: `KAIFU IZARI MIKAN IZUMI` (southwest)
|
||||
- `V28 ITE V55 IZUMI`: `WASYU OYE OLIVE AYAYA BUMER ARIMA ITE IZUMI` (west)
|
||||
- `Y33 KTE KULUL TSC MIKAN IZUMI`: `SAKAI KOMPI KTE KULUL TSC MIKAN IZUMI` (west)
|
||||
- `V55 IZUMI`: `NORAN OSAMU IYOKA IZUMI` (southeast)
|
||||
|
||||
Aircraft depart via:
|
||||
|
||||
- `KCC` via `ASUKA` (east)
|
||||
- `KRE` via `IZUMI`, `ITE`, `OLIVE` (southwest)
|
||||
- `KRE` via `IZUMI`, `KAIFU` (southwest)
|
||||
- `YME` via `IZUMI` (north)
|
||||
- `YUBAR` via `IZUMI` (northwest)
|
||||
- `WASYU` via `IZUMI` (west)
|
||||
- `YUBAR` via `IZUMI`, `ITE`, `OYE` (northwest)
|
||||
- `WASYU` via `IZUMI`, `ITE`, `OYE` (west)
|
||||
- `NORAN` via `IZUMI` (southeast)
|
||||
|
||||
The missed approach hold is `IZUMI` +4200.
|
||||
|
||||
@@ -315,7 +348,9 @@ The reverse configuration. Use care for `ASUKA` departures to keep them separate
|
||||
|
||||
## 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.
|
||||
- Circle to land approaches make a long downwind (a short final is not possible in game)
|
||||
- `Y401` arrivals to `RJOO` aren't restricted to `DH8D` (not possible in game)
|
||||
- `KAIFU` arrivals to `RJOO` aren't restricted to other props (not possible in game)
|
||||
|
||||
## Changelog
|
||||
|
||||
@@ -378,4 +413,29 @@ The reverse configuration. Use care for `ASUKA` departures to keep them separate
|
||||
- Added many new GA aircraft types
|
||||
* 3.1.0 - 2021/07/02
|
||||
- Add handoff callsign / frequency support
|
||||
- Improve reading of Tokushima
|
||||
- Improve reading of Tokushima
|
||||
* 4.0.0 - 2021/08/30
|
||||
- Complete overhaul of arrivals
|
||||
- All arrivals enter the ACA cleared to the last waypoint on flight plan
|
||||
- All arrivals now enter the ACA at more accurate locations
|
||||
- All arrivals now enter the ACA at appropriate altitudes for each entrypoint
|
||||
- `RJBB`
|
||||
- `ALISA` arrivals split to arrivals via `Y36` and `Y361`
|
||||
- `RJOO`
|
||||
- Adjusted proportions between entrypoints
|
||||
- Added entrypoint for arrivals from Sanin region airports
|
||||
- `RJOY`
|
||||
- Entrypoints revised
|
||||
- Traffic overhauled
|
||||
- Proportions adjusted
|
||||
- Less GA traffic to `RJBB`, `RJBE`, `RJOT`, `RJOB`
|
||||
- Small GA traffic added to `RJBE`, `RJOT`, `RJOB`
|
||||
- Updated `CYGNS`, added `JF1` and `AF1` to `RJOO`
|
||||
- Added a few transients to `RJOS`
|
||||
- Added navaid check traffic
|
||||
- Adjusted `RJBB` ILS Z/Y 24R approaches to allow for more room for `RJBE` arrivals circling to 27
|
||||
- Adjusted `RJBE` circle to 27 so that `B763` can intercept the final without going missed
|
||||
- Added initial climb altitudes per airport
|
||||
- Notably, `RJBE` 09 departures climb to 1500 while 27 departures climb to 3000
|
||||
- This will reduce workload during west wind at `RJBE`
|
||||
- Adjust names of departures to take advantage of new 7 character limit in tags
|
||||
+94
-281
@@ -1,6 +1,6 @@
|
||||
# `RJBB` 進入管制区 3.1.0
|
||||
# `RJBB` 進入管制区 4.0.0
|
||||
|
||||
＊作者は日本人ではありません。以下の文章には間違っている日本語、または間違っている情報が含まれている場合があります。ご了承いただければ幸いです。
|
||||
> 作者は日本人ではありません。以下の文章には間違っている日本語、または間違っている情報が含まれている場合があります。ご了承いただければ幸いです。
|
||||
|
||||
KANSAI ACA(関西進入管制区)を[Endless ATC](https://steamcommunity.com/app/666610)に追加するMODです。`RJBB`関西国際空港、`RJOO`大阪国際空港(伊丹)、`RJBB`神戸空港、`RJOS`徳島空港、`RJOT`高松空港、`RJOB`岡山空港、そして`RJOY`八尾空港が再現されています. 空域の上限はFL180です.
|
||||
|
||||
@@ -10,317 +10,105 @@ STARはこのゲームの進入方式で再現されています。進入方式
|
||||
|
||||
KANSAI ACAの南部の直下にあるTOKUSHIMA ACA (徳島進入管制区)はゲームの仕様上、KANSAI ACAの一部として実装しています。`RJOS`発着便のみTOKUSHIMA ACA （`OS`の表示がある空域）に入れます。
|
||||
|
||||
ゲームの仕様上、快適に遊べるように本作ではKANSAI ACAの空域を`OHDAI`の周りに中部へ、または`ROKKO`と`WAKIT`の周りに北へ拡大しています。高知空港はゲームの仕様上実装するのは困難なため、省略されています. 高知県民には申し訳ございません。`RJOO`/`RJBB`発着の`RJOK`便もゲームの仕様上再現できません。
|
||||
高知空港とその周辺の空域はゲームの仕様上実装するのは困難なため、省略されています. `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.
|
||||
到着機は管制区に入った後、フライトプランルートに沿って進んで、終点ポイントにたどり着いたら新たな指示がない場合ホールドに入る。STARと進入許可はルートの各ポイントから出せる。STARも途中のポイントから再開の指示を出せて、進入許可もIAF/IFあるいはFAFから出せる。ルート終点ポイントとその到着ルートは以下の通り:
|
||||
|
||||
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.
|
||||
- `ALISA`
|
||||
- `Y36 ALISA`: `TONBI SAEKI ALISA` (北西)
|
||||
- `Y361 SAEKI Y36 ALISA`: `SPICE SAEKI ALISA` (北東)
|
||||
- `BERTH`
|
||||
- `Y35 BERTH`: `(Y35) RANDY BERTH` (西)
|
||||
- `BECKY`
|
||||
- `Y53 BECKY`: `KARIN BECKY` (南西)
|
||||
- `CANDY`
|
||||
- `Y46 CANDY`: `EVERT CANDY` (南南西、南、東)
|
||||
- `DANDE`
|
||||
- `Y544 DANDE`: `(Y544) SINGU RIDGE DANDE` (`RJTT`/`RJAA`/`RJSS`/`RJSF`)
|
||||
|
||||
### `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.
|
||||
到着機は管制区に入った後、フライトプランルートに沿って進んで、終点ポイントにたどり着いたら新たな指示がない場合ホールドに入る。STARと進入許可はルートの各ポイントから出せる。STARも途中のポイントから再開の指示を出せて、進入許可もIAF/IFあるいはFAFから出せる。ルート終点ポイントとその到着ルートは以下の通り:
|
||||
|
||||
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.
|
||||
- `IKOMA`
|
||||
- via `ROKKO`
|
||||
- `Y384 ROKKO`: `(Y384) ROKKO` (北東)
|
||||
- `Y38 ROKKO`: `TOZAN ROKKO` (北西)
|
||||
- `RJBT.../RJOR YME V55.../RJOH YME V55...ROKKO`: `(GUNZE) ROKKO` (`RJBT`/`RJOR`/`RJOH`)
|
||||
- `ROKKO`からのSTARはフライトプランルートに含まれるので`ROKKO`から`ROKKO KAMEO OTABE ABENO IKOMA`を沿って`IKOMA`まで進む
|
||||
- via `KODAI`
|
||||
- `Y546 KODAI`: `OHDAI KODAI` (東)
|
||||
- `KODAI`からのSTARはフライトプランルートに含まれるので`KODAI`から`KODAI MIRAI ABENO IKOMA`を沿って`IKOMA`まで進む
|
||||
- `IZUMI`
|
||||
- `Y401 KAINA Y753 IZUMI`: `RIVER ZOROH KAZRA MIRIO KAINA IZUMI` (西)
|
||||
- `Y231 MIRIO Y401 KAINA Y753 IZUMI`: `(Y231) JANGO BECKY MIRIO KAINA IZUMI` (西)
|
||||
- `Y753 IZUMI`: `MUGIE HONMA KAINA IZUMI` -> `HONMA` -> `KAINA` -> `IZUMI` (南西)
|
||||
|
||||
### `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.
|
||||
到着機は管制区に入った後、フライトプランルートに沿って進んで、終点ポイントにたどり着いたら新たな指示がない場合ホールドに入る。STARと進入許可はルートの各ポイントから出せる。STARも途中のポイントから再開の指示を出せて、進入許可もIAF/IFあるいはFAFから出せる。ルート終点ポイントとその到着ルートは以下の通り:
|
||||
|
||||
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.
|
||||
- `TRACY`
|
||||
- `Y20 WAKIT Y201 TRACY`: `ARASI GINJI WAKIT TRACY` (東)
|
||||
- `Y382 WAKIT Y201 TRACY`: `(Y382) WAKIT TRACY` (北東)
|
||||
- `BERTH`
|
||||
- `Y35 BERTH`: `(Y35) RANDY BERTH` (西)
|
||||
- `BECKY`
|
||||
- `Y53 BECKY`: `(Y53) KARIN BECKY` (南西)
|
||||
|
||||
### `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.
|
||||
到着機は管制区に入った後、フライトプランルートに沿って進んで、終点ポイントにたどり着いたら新たな指示がない場合ホールドに入る。進入許可はルートの各ポイント、IAF、IFあるいはFAFから出せる。ルート終点ポイントとその到着ルートは以下の通り:
|
||||
|
||||
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.
|
||||
- `DATIS`
|
||||
- `Y544 SINGU Y542 DATIS`: `SINGU SOMEI DINAH GOBOH UBUYU DATIS` (東)
|
||||
- `TSC`
|
||||
- `KEC JOSIN TSC`: `(KEC30) JOSIN TSC` (南東)
|
||||
- `Y33 KTE KULUL TSC`: `SAKAI KOMPI KTE KULUL TSC` (西)
|
||||
|
||||
### `RJOT` 高松空港
|
||||
|
||||
＊未翻訳
|
||||
An airport nestled up against mountains to the south serving Takamatsu.
|
||||
到着機は管制区に入った後、フライトプランルートに沿って進んで、終点ポイントにたどり着いたら新たな指示がない場合ホールドに入る。STARと進入許可はルートの各ポイントから出せる。STARも途中のポイントから再開の指示を出せて、進入許可もIAF/IFあるいはFAFから出せる。ルート終点ポイントとその到着ルートは以下の通り:
|
||||
|
||||
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.
|
||||
- `WIMPY`
|
||||
- `Y20 WAKIT Y203 WIMPY` (東)
|
||||
- `KTE`
|
||||
- `Y288 TAKMA KTE`: `TAKMA KTE` (西)
|
||||
- `Y39 OYE KTE`: `YUBAR OYE KTE` (北西)
|
||||
|
||||
### `RJOB` 岡山空港
|
||||
|
||||
＊未翻訳
|
||||
An airport situated in the mountains serving Okayama.
|
||||
到着機は管制区に入った後、フライトプランルートに沿って進んで、終点ポイントにたどり着いたら新たな指示がない場合ホールドに入る。進入許可はルートの各ポイント、IAF、IFあるいはFAFから出せる。ルート終点ポイントとその到着ルートは以下の通り:
|
||||
|
||||
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.
|
||||
- `OYE`
|
||||
- `Y20 WAKIT Y205 OYE`: `ARASI GINJI WAKIT TRIPY MIMMY SIMAG BENES OYE` (東)
|
||||
- `Y382 WAKIT Y205 OYE`: `(Y382) WAKIT TRIPY MIMMY SIMAG BENES OYE` (北東)
|
||||
- `Y39 OYE`: `YUBAR OYE` (北西)
|
||||
- `Y288 INOOK OYE`: `TAKMA INOOK OYE` (西)
|
||||
|
||||
### `RJOY` 八尾空港
|
||||
|
||||
＊未翻訳
|
||||
A small airport near Osaka that acts as a general aviation gateway.
|
||||
到着機は管制区に入った後、フライトプランルートに沿って進んで、終点ポイントにたどり着いたら新たな指示がない場合ホールドに入る。進入許可はルートの各ポイント、IAF、IFあるいはFAFから出せる。ルート終点ポイントとその到着ルートは以下の通り:
|
||||
|
||||
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`.
|
||||
- `IZUMI`
|
||||
- `V28 ITE V55 IZUMI`: `MIDER ITE IZUMI` (東)
|
||||
- `(YME) V55 IZUMI`: `GUNZE ROKKO SANDA ITE IZUMI` (北)
|
||||
- `Y384 ROKKO V55 IZUMI`: `(Y384) ROKKO SANDA ITE IZUMI` (北東)
|
||||
- `Y38 ROKKO V55 IZUMI`: `TOZAN ROKKO SANDA ITE IZUMI` (北西)
|
||||
- `(KRE) KAIFU IZARI MIKAN IZUMI`: `KAIFU IZARI MIKAN IZUMI` (南西)
|
||||
- `V28 ITE V55 IZUMI`: `WASYU OYE OLIVE AYAYA BUMER ARIMA ITE IZUMI` (西)
|
||||
- `Y33 KTE KULUL TSC MIKAN IZUMI`: `SAKAI KOMPI KTE KULUL TSC MIKAN IZUMI` (西)
|
||||
- `V55 IZUMI`: `NORAN OSAMU IYOKA IZUMI` (南東)
|
||||
|
||||
## 既知の問題点
|
||||
|
||||
- 旋回進入...............実装できていますが、かなりの余裕のあるベースターンとファイナルアプローチじゃないとミスアプローチのなるので結構広い旋回進入となっています。
|
||||
- 旋回進入はエクステンドダウンウィンドをする（ゲームの仕様で短いファイナルはできないため）
|
||||
- `Y401`から`RJOO`の到着機は`DH8D`に限定されていない (ゲームの仕様ではできない)
|
||||
- `KAIFU` から`RJOO` の到着機はその他プロップ機に限定されていない (ゲームの仕様ではできない)
|
||||
|
||||
## 変更履歴
|
||||
|
||||
@@ -363,4 +151,29 @@ The reverse configuration. Use care for `ASUKA` departures to keep them separate
|
||||
- これに伴い小型機を大量実装
|
||||
* 3.1.0 - 2021/07/02
|
||||
- ハンドオフ先のコールサイン及び周波数を実装
|
||||
- 徳島の発音を改良
|
||||
- 徳島の発音を改良
|
||||
* 4.0.0 - 2021/08/30
|
||||
- 到着経路をリニューアル
|
||||
- 到着機はフライトプランルートの終点まで進む
|
||||
- 到着機が管制区に入る位置を修正
|
||||
- 到着機が管制区に入る時の高度を各ルートで設定
|
||||
- `RJBB`
|
||||
- `ALISA`からの到着機は`Y36`と`Y361`を別々にエントリーポイントを設定
|
||||
- `RJOO`
|
||||
- 各スポーンポイントの交通量比率を調整
|
||||
- 山陰地区空港からのエントリーポイントを設定
|
||||
- `RJOY`
|
||||
- エントリーポイントを変更
|
||||
- 登場機をアップデート
|
||||
- 比率を調整
|
||||
- `RJBB`, `RJBE`, `RJOT`, `RJOB`の小型機の比率を下げる
|
||||
- `RJBE`, `RJOT`, `RJOB`に小型機を実装
|
||||
- `CYGNS`をアップデート、`RJOO`に`JF1`と`AF1`を実装
|
||||
- `RJOS`に所在しない自衛隊機を追加
|
||||
- チェックスターを追加
|
||||
- `RJBE`27に旋回する到着機とセパレーションのため`RJBB` ILS Z/Y 24R アプローチを調整
|
||||
- `B763`がミスドアプローチしないように`RJBE`27への旋回経路を調整
|
||||
- 出発機の一次上昇高度を各出発経路に設定
|
||||
- 特に`RJBE`09出発機は1500までの上昇に対して27出発機は3000まで上昇する
|
||||
- `RJBE`西風の時の西行量が大福に減る
|
||||
- 出発経路の名前を変更
|
||||
@@ -252,7 +252,7 @@ Approaches are available using APP mode from `TOHNE` and `ASEKI`. Arrival routes
|
||||
* 3.2.0 - 2021/07/06
|
||||
- 出発機のハンドオフ先のコールサイン及び周波数を実装
|
||||
- レア発着機の追加や修正
|
||||
* 3.3.0 - 2021/07/06
|
||||
* 3.3.0 - 2021/07/18
|
||||
- 進入管制区の各入口の維持高度を個別に設定
|
||||
- 各SIDの初期維持高度を個別に設定
|
||||
- 進入管制区の入口ポイントを進入管制区境界にあるポイントに変更
|
||||
|
||||
+1357
-773
File diff suppressed because it is too large
Load Diff
@@ -3305,7 +3305,7 @@ route = @Y10
|
||||
#===RJTT SIDs
|
||||
|
||||
[commondeparture]
|
||||
common = RJTT
|
||||
airport = RJTT
|
||||
|
||||
route = @!ROVER2A
|
||||
!TORAM
|
||||
@@ -4524,7 +4524,7 @@ route = @Y30
|
||||
#===RJAA SIDs
|
||||
|
||||
[commondeparture]
|
||||
common = RJAA
|
||||
airport = RJAA
|
||||
|
||||
route = @!AGRIS
|
||||
!RADIX
|
||||
|
||||
+27
-3
@@ -430,7 +430,7 @@ route = @HABIK
|
||||
|
||||
A departure route can start with `@<name>` which makes the route a "segment". A segment will not be output in the product. This segment will be available for reference in the current `[departure]`. This is useful for defining initial departure segments unique to specific runways.
|
||||
|
||||
Alternatively, a departure route can start with `@!<name>` which also makes the route a "segment", but available to all subsequent `[departure]`s including the current one. This is useful for defining transition segments common to all runways.
|
||||
Alternatively, a departure route can start with `@!<name>` which also makes the route a "segment", but available to all subsequent `[departure]`s for the same airport including the current one. This is useful for defining transition segments common to all runways.
|
||||
|
||||
To use these segments, a departure route can include after the route name line an unlimited number of `@<name>` lines , which will be substituted with the respective segment.
|
||||
|
||||
@@ -448,7 +448,7 @@ route = @TAROH3
|
||||
!OT26D
|
||||
!TAROH
|
||||
|
||||
# MIHO TRANSITION available in all [departure]s
|
||||
# MIHO TRANSITION available in all [departure]s for the airport this runway belongs to
|
||||
route = @!MIHO
|
||||
!MIHOU
|
||||
|
||||
@@ -500,6 +500,25 @@ route = *4
|
||||
@!SHTLE
|
||||
```
|
||||
|
||||
For organizational purposes, you can define shared segments in a `[commondeparture]` section:
|
||||
|
||||
```INI
|
||||
#this section will not be in the outputted product
|
||||
[commondeparture]
|
||||
airport = OS
|
||||
|
||||
#you still need to define with @! to make them shared by airport
|
||||
route = @!KILAP
|
||||
!KMANO
|
||||
!KILAP
|
||||
|
||||
route = @!WASYU
|
||||
!KULUL
|
||||
!KTE
|
||||
!UTAZU
|
||||
!WASYU
|
||||
```
|
||||
|
||||
## Changelog
|
||||
* 0.8.0 - 2021/02/20
|
||||
- Added generated approaches feature
|
||||
@@ -543,4 +562,9 @@ route = *4
|
||||
- To be used to connect to multiple runways
|
||||
- The approach route is not extended with the linked approach
|
||||
- Airlines can be defined with two dashes to define unique traffic
|
||||
- Pronunciation generation added to support this
|
||||
- Pronunciation generation added to support this
|
||||
* 0.12.0 - 2021/08/30
|
||||
- Add simple error checking for entrypoints
|
||||
- Bug fix for approaches terminating in holds that connect to another approach
|
||||
- `[commondeparture]` feature for defining departures per airport
|
||||
- Allow second argument in `[airport] code=` to define full ICAO code for secondary airports
|
||||
+1
-1
@@ -82,7 +82,7 @@ jna = jin air
|
||||
jsa = jetstar asia
|
||||
jst = jet star
|
||||
jta = j-ocean
|
||||
jyh = trans ajde
|
||||
jyh = trans jade
|
||||
kac = kuwaiti
|
||||
kal = korean air
|
||||
klm = k-l-m
|
||||
|
||||
+65
-29
@@ -34,7 +34,7 @@ class Fix:
|
||||
|
||||
fixes: ClassVar = None
|
||||
_var: ClassVar[float] = 0
|
||||
_registry: ClassVar = {}
|
||||
_subclass_registry: ClassVar = {}
|
||||
|
||||
@staticmethod
|
||||
def initialize(magvar):
|
||||
@@ -44,19 +44,21 @@ class Fix:
|
||||
@classmethod
|
||||
@property
|
||||
def special_prefixes(cls):
|
||||
return cls._registry.keys()
|
||||
return cls._subclass_registry.keys()
|
||||
|
||||
@classmethod
|
||||
def __init_subclass__(cls, /, name_prefix=None, **kwargs):
|
||||
super().__init_subclass__(**kwargs)
|
||||
if name_prefix is not None:
|
||||
for prefix in name_prefix:
|
||||
cls._registry[prefix] = cls
|
||||
cls._subclass_registry[prefix] = cls
|
||||
|
||||
def __new__(cls, name, *args, **kwargs):
|
||||
if name in cls.fixes:
|
||||
return cls.fixes[name]
|
||||
name_prefix = name[:1]
|
||||
if name_prefix in cls._registry:
|
||||
return object.__new__(cls._registry[name_prefix])
|
||||
if name_prefix in cls._subclass_registry:
|
||||
return object.__new__(cls._subclass_registry[name_prefix])
|
||||
else:
|
||||
return object.__new__(cls)
|
||||
|
||||
@@ -542,7 +544,7 @@ def _process_simple_approach_fix_list(fix_list, runway, fixes,
|
||||
|
||||
|
||||
def _process_approach_fix_list(fix_list, runway, fixes, tagged_routes,
|
||||
generated_approaches, current_tag=None, top_level=True, debug=False):
|
||||
generated_approaches, current_tag=None, top_level=True, terminate=False, debug=False):
|
||||
"""Inner worker function for `process_approach_fix_list`.
|
||||
|
||||
Args:
|
||||
@@ -555,7 +557,8 @@ def _process_approach_fix_list(fix_list, runway, fixes, tagged_routes,
|
||||
that were tagged for lookup.
|
||||
`generated_approaches`: A dict keyed by runway of dicts of parameters
|
||||
to be used to generate derived approaches in post-processing.
|
||||
`top_level`: Whether or not to process any approach generator commands.
|
||||
`top_level` (bool): Whether or not to process any approach generator commands.
|
||||
`terminate` (bool): Whether or not the route has already terminated.
|
||||
`debug` (bool): Whether to print debug information."""
|
||||
|
||||
if debug:
|
||||
@@ -563,13 +566,15 @@ def _process_approach_fix_list(fix_list, runway, fixes, tagged_routes,
|
||||
if fix_list[-1].startswith('@'):
|
||||
following_tags = (tag.strip().lstrip('@') for tag in fix_list[-1].split(','))
|
||||
|
||||
_process_simple_approach_fix_list(fix_list[:-1], runway, fixes,
|
||||
tagged_routes[runway], generated_approaches, current_tag, top_level)
|
||||
if not terminate:
|
||||
_process_simple_approach_fix_list(fix_list[:-1], runway, fixes,
|
||||
tagged_routes[runway], generated_approaches, current_tag, top_level)
|
||||
|
||||
terminate = False
|
||||
if len(fix_list) > 1:
|
||||
last_fix = fix_list[-2].strip()
|
||||
terminate = last_fix.startswith('end') and last_fix.endswith('hold')
|
||||
if len(fix_list) > 1:
|
||||
last_fix = fix_list[-2].strip()
|
||||
terminate = last_fix.startswith('end') and last_fix.endswith('hold')
|
||||
if debug and terminate:
|
||||
print(f"Terminating approach {fix_list}")
|
||||
|
||||
for generated_approach in generated_approaches[runway or current_tag]:
|
||||
if 'tag' in generated_approach:
|
||||
@@ -610,13 +615,19 @@ The requesting approach route was {fix_list}''')
|
||||
following_route = tagged_routes[following_tag_runway][following_tag]
|
||||
if remove_first_fix:
|
||||
following_route = following_route[1:]
|
||||
if not terminate:
|
||||
_process_approach_fix_list(following_route,
|
||||
following_tag_runway, fixes, tagged_routes, generated_approaches, following_tag,
|
||||
False, debug=debug)
|
||||
|
||||
if debug and terminate:
|
||||
print(f"Connecting terminated approach {fix_list} to {following_route}")
|
||||
_process_approach_fix_list(following_route,
|
||||
following_tag_runway, fixes, tagged_routes, generated_approaches, following_tag,
|
||||
False, terminate=terminate, debug=debug)
|
||||
else:
|
||||
_process_simple_approach_fix_list(fix_list, runway, fixes,
|
||||
tagged_routes[runway], generated_approaches, current_tag, top_level)
|
||||
if terminate:
|
||||
if debug:
|
||||
print(f"Finalizing terminated approach with {fix_list}")
|
||||
else:
|
||||
_process_simple_approach_fix_list(fix_list, runway, fixes,
|
||||
tagged_routes[runway], generated_approaches, current_tag, top_level)
|
||||
|
||||
return generated_approaches
|
||||
|
||||
@@ -705,11 +716,10 @@ def process_departure_fix_list(fix_list, runway, airport, fixes, tagged_routes,
|
||||
tagged_routes[airport] = {}
|
||||
if fix_list[0].startswith('@'):
|
||||
tag = fix_list[0].lstrip('@')
|
||||
tag_namespace = airport
|
||||
if tag.startswith('!!'):
|
||||
tag_namespace = None
|
||||
elif tag.startswith('!'):
|
||||
tag_namespace = runway
|
||||
tag_namespace = airport
|
||||
elif runway:
|
||||
tag_namespace = runway
|
||||
else:
|
||||
@@ -752,7 +762,9 @@ def _process_departure_fix_list(fix_list, runway, airport, fixes, tagged_routes,
|
||||
elif tag in tagged_routes[airport]:
|
||||
tagged_route = tagged_routes[airport][tag]
|
||||
else:
|
||||
raise KeyError(f"Unable to find route tagged @{tag}")
|
||||
raise KeyError(f'''Unable to find route tagged @{tag}.
|
||||
tags for runway {runway}: {tagged_routes[runway]}
|
||||
tags for airport {airport}: {tagged_routes[airport]}''')
|
||||
yield from _process_departure_fix_list(tagged_route,
|
||||
runway, airport, fixes, tagged_routes, top_level=False, altitude=altitude)
|
||||
yield from _process_departure_fix_list(fix_list[1:],
|
||||
@@ -767,7 +779,9 @@ def _process_departure_fix_list(fix_list, runway, airport, fixes, tagged_routes,
|
||||
elif tag in tagged_routes[airport]:
|
||||
tagged_route = tagged_routes[airport][tag]
|
||||
else:
|
||||
raise KeyError(f"Unable to find route tagged @{tag}")
|
||||
raise KeyError(f'''Unable to find route tagged @{tag}.
|
||||
tags for runway {runway}: {tagged_routes[runway]}
|
||||
tags for airport {airport}: {tagged_routes[airport]}''')
|
||||
yield from _process_departure_fix_list(fix_list[:-1],
|
||||
runway, airport, fixes, tagged_routes, top_level=False, altitude=altitude)
|
||||
yield from _process_departure_fix_list(tagged_route,
|
||||
@@ -802,16 +816,30 @@ def process_sids_fix_list(fix_list, fixes):
|
||||
yield line
|
||||
|
||||
|
||||
def process_entrypoints_list(entrypoints_list):
|
||||
def process_entrypoints_list(entrypoints_list, fixes=None):
|
||||
"""Processes special commands in a list of fixes in minor format
|
||||
and produces an iterable of definitions as the result.
|
||||
|
||||
Substitute any "!<name>[, <extra_data>]" in `fix_list` with
|
||||
"lat, lon[, <extra_data>]" based on `fixes`.
|
||||
|
||||
If `fixes` is provided, error checking will be done. Any problems
|
||||
will be printed to console.
|
||||
|
||||
Args:
|
||||
`entrypoints_list` (list): A list of entrypoints definitions."""
|
||||
`entrypoints_list` (list): A list of entrypoints definitions.
|
||||
`fixes` (dict): A lookup of `Fix`es."""
|
||||
for line in entrypoints_list:
|
||||
if not line.strip():
|
||||
yield line
|
||||
continue
|
||||
entrypoint_heading, _, entrypoint_definition = line.partition(',')
|
||||
entrypoint_fix, _, entrypoint_definition = entrypoint_definition.partition(',')
|
||||
entrypoint_fix = entrypoint_fix.strip()
|
||||
if entrypoint_fix not in fixes:
|
||||
print(f"Warning: entrypoint fix {entrypoint_fix} is not defined")
|
||||
elif fixes[entrypoint_fix].is_hidden():
|
||||
print(f"Warning: entrypoint fix {entrypoint_fix} is defined as a hidden fix")
|
||||
entrypoint_definition, _, entrypoint_last_parameter = line.rpartition(',')
|
||||
entrypoint_last_parameter = entrypoint_last_parameter.strip()
|
||||
if entrypoint_last_parameter.startswith('*'):
|
||||
@@ -1001,7 +1029,7 @@ def process(args, input_file=None, preprocessed_input=None):
|
||||
runways = airport_data['runways'].strip().splitlines()
|
||||
for runway_definition in runways:
|
||||
runway_id, _, _ = runway_definition.partition(',')
|
||||
runway_to_airport[runway_id] = airport_code
|
||||
runway_to_airport[runway_id] = airport_code.strip()
|
||||
|
||||
gateways = dict((tuple(map(str.strip, gateway.split(","))) for gateway in airport_data['gateways'].strip().splitlines()),
|
||||
**default_gateways) if 'gateways' in airport_data else None
|
||||
@@ -1017,7 +1045,7 @@ def process(args, input_file=None, preprocessed_input=None):
|
||||
|
||||
if 'entrypoints' in airport_data:
|
||||
airport_data['entrypoints'] = "\n".join(
|
||||
process_entrypoints_list(airport_data['entrypoints'].splitlines()))
|
||||
process_entrypoints_list(airport_data['entrypoints'].splitlines(), Fix.fixes))
|
||||
|
||||
# process approach/transition sections
|
||||
approaches = {section: source[section] for section in source
|
||||
@@ -1093,11 +1121,19 @@ Defined beacon was {generated_approach.beacon}, actual beacon was {approach_beac
|
||||
departures = [source[section] for section in sorted(source) if section.startswith('departure')]
|
||||
tagged_departures = {None: {}}
|
||||
|
||||
for departure_data in common_departures:
|
||||
if 'airport' not in departure_data:
|
||||
raise RuntimeError(f'''A [commondeparture] exists with no airport specified.''')
|
||||
|
||||
for departure_data in chain(common_departures, departures):
|
||||
if 'common' in departure_data:
|
||||
departure_airport = departure_data['common']
|
||||
if 'airport' in departure_data:
|
||||
departure_airport = departure_data['airport']
|
||||
departure_runway = None
|
||||
departure_base_runway = None
|
||||
elif 'runway' not in departure_data:
|
||||
raise RuntimeError(f'''A departure exists with no runway. Aborting.
|
||||
The contents of the departure section are as follows:
|
||||
{"".join(departure_data.values())}''')
|
||||
else:
|
||||
departure_runway = departure_data['runway']
|
||||
departure_runway = departure_runway.partition(',')
|
||||
|
||||
Reference in New Issue
Block a user