tm24fan8/Airports
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

RJBB 3.0.0 & tools 0.9.0 release candidate

Browse Source
This commit is contained in:
Calvin Ng
2021-05-24 22:49:53 -07:00
parent 218deca326
commit 1cf35f8309
7 changed files with 931 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files
final/AS/JPN/RJBB_readme.md
+81 -18
View File
@@ -1,18 +1,14 @@
# RJBB ACA 2.0.0
# `RJBB` ACA 3.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, and RJOB Okayama Airport. The airspace ceiling is FL180.
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. The controller will need to carefully monitor both departures and arrivals and issue altitude, speed, and vectors to ensure proper separation.
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 2020/12/31. 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.
Based upon AIP Japan 2020/12/31. 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].
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 (even approaches to airports other than the aircraft's intended destination). **\*Use care to ensure you have selected the approach to the correct airport!!!\*** Pressing the APP button again (do not long press) to 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.
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. Given this type of restriction is the only one that can be implemented in Endless ATC, this would have resulted in appraoches providing only lateral guidance. Therefore, restrictions have been implemented to provide a "latest possible descent" to the initial approach fix. 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.
**\*Departures may need to handed off before they reach the boundary of the ACA\***, *as there are cases where the SID exts the ACA before cruise altitude can be reached.*
`RJOY` Yao Airport is currently not implemented in this version.
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`).
@@ -265,7 +261,7 @@ Aircraft depart via:
- `YUBAR` (north)
- `WASYU` (west)
The missed approach hold is OYE/BENES +4000.
The missed approach hold is `OYE`/`BENES` +4000.
There are two simple runway configurations:
@@ -277,17 +273,56 @@ The preferred runway configuration for arrivals from the west. A RNAV AR approac
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*
- No `RJOY` Yao (how to even go about doing this...)
- 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
- Add approaches to both runway ends for all airports.
- Add approaches to many, many fixes as the approach limit has been lifted.
- 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
@@ -304,12 +339,40 @@ The preferred runway configuration for arrivals from the east. The straight-in t
- Added various minor fixes
- Added Akeno ACA area
- Removed training areas as they should be more inactive rather than active...?
* 3.0.0 - 2021/03/xx
* 3.0.0 - 2021/05/xx
- Rewrite of source
- Add `RJBB` ARC series STARs and ILS Y approaches
- 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
- `RJBE` MIDER TRANSITION established
- Added `RJOY` Yao
- Only runway 09-27
- Added many new GA aircraft types