Thijs
6.1 KiB
EHAM v1.0
This is a file to add EHAM (Amsterdam Schiphol Airport) to the Endless ATC game.
Features
Implemented
- Arrivals and departures at EHAM
- (Semi-)Realistic arrival- and departure paths
- Realistic airspace
- Secondary airports: EHRD
- Multiple runway configurations (currently 6)
- Realistic airline schedules. The variety of airlines is quite limited at this time.
- Added ARTIP1X transition to runway 36R
Planned
- Add EHLE secondary when open IRL
- Potentially add night transitions if requested
Basic operations
Departures
EHAM
Each departure will follow a realistic SID from the departure runways. Departures are generally cleared to climb to FL130 after initial contact to approach. When arrivals need to be vectored overhead the airport or away from the standard vectors, departing aircraft are kept at FL60 until clear of the conflict.
EHRD
Departures in real life are coordinated with EHAM APP before being released. Departures towards the south, west and south-east can usually be cleared to FL60 and then to FL130 when clear of EHAM arrivals to RIVER. Departures towards the north should be cleared to climb to FL130 when clear of the potential arriving traffic 36R.
Arrivals
EHAM
Arrivals to EHAM arrive to the TMA through 3 main entry points:
- SUGOL (from the west)
- ARTIP (fron the (north)east)
- RIVER (from the south)
All arrivals are routed to SPL after the entry point in the standard vectors. As such the arrivals from SUGOL and ARTIP are routed to SPL in the sim, arrivals from the south are initially routed to RIVER. In real life these arrivals would be with Amsterdam Radar still as the EHRD TMA it flies over only goes up to FL55. Arrivals via RIVER should be directed to SPL after RIVER for standard vectors. A basic guide for vectoring including a diagram is included at the IVAO Netherlands website.
The following are basic vectoring guidelines
South Configuration (config 1)
Aircraft are routed to SPL and descended to FL40 (Transition level based on Endless ATC parameters). When aircraft are cleared for the initial descend timely, departures should have no problem climbing over. Be specifically mindful of departures to IDRID or BERGI. Then aircraft are vectored on a righthand downwind for ILS18R or lefthand downwind for ILS18C. Aircraft landing 18R are descended to 3000ft on downwind, then 2000 ft on the base turn. Aircraft landing 18C are descended to 3000ft on downwind and remain at 3000ft on base and until intercepted. Ensure that the downwind leaves sufficient room for the base turn.
Alternatively, aircraft from RIVER can be given heading 020 and aircraft from SUGOL and ARTIP are flown direct towards SPY (Spijkerboor). Then the aircraft are descended to 2000ft and 3000ft for RWY 18R and 18C respectively. This is useful at low traffic amounts, but as traffic gets higher, the extra track miles help with separation.
North Configuration (config 2)
Aircraft from SUGOL are vectored for runway 06 and aircraft from ARTIP for runway 36R. Aircraft from RIVER can be vectored to either runway 06 or runway 36R depending on other traffic.
Aircraft from SUGOL are directed to SPL and down to FL40, then turned downwind heading 240. Then descended to 3000ft on the downwind and to 2000ft on the base turn.
Aircraft from ARTIP are directed to PAM descending to FL40 and leave PAM heading 205. Then the aircraft is descended to 3000ft on the heading of 205 and descended to 2000ft on the base turn.
Aircraft from RIVER are either vectored for a straight in ILS06 and controlled by speed to merge with traffic from SUGOL. Aircraft from RIVER to RWY36R are put on a heading of 060 and descended to FL040, be mindful of departures from EHRD. Then the aircraft are merged with traffic from ARTIP based on speed and intercept distance.
Configurations 3/4
Additional configurations based on visibility conditions being below minima for parallel landing. Aircraft from SUGOL are vectored to runway 18R, from ARTIP to runway 22/27 and from RIVER to either runway depending on traffic. Traffic from RIVER to runway 22/27 are flown to SPL at FL70 and then descended once overhead the airport. This could have a conflict with departing traffic from runway 24, as such be mindful when clearing departures higher than FL60.
Configurations 5/6
Alternative North Combinations. In configuration 5 traffic from SUGOL goes to runway 36C, from ARTIP to runway 36R as per config 2 and traffic from RIVER to either depending on traffic. Note that the intercept height for runway 36C is 3000ft and that the downwind from SUGOL is turned just outside of the CTR.
In configuration 6 traffic from ARTIP is going to runway 27, from SUGOL to 06 and traffic from RIVER to either runway depending on traffic. Traffic for runway 27 from RIVER leaves RIVER heading 060 for a left-hand traffic pattern.
EHRD
Arriving traffic from EHRD will arrive from all four cardinal directions. Arrivals from the north and east are routed to PAM, from the west to STD and from the south directly to ROT. Arrivals are then routed to ROT and flown either a right-hand circuit for runway 06 or left-hand circuit for runway 24. Aircraft arriving from PAM towards runway 24 are usually vectored straight in, likewise for west and south arrivals for runway 06. Traffic arriving from the south might require an orbit to lose additional altitude due to EndlessATC limitation on entering altitudes.
Notice bugs or issues? Please open an issue on github.
##Changelog v0.1 Initial release
v0.2
- Corrected initial beacon west arrivals to EHRD
- Added EHAM_readme.md
v0.3
- Added EHAM CTR's 1,2 & 3
- Added EHRD CTR
- Added restricted area's for CTA's prior to SUGOL/RIVER/ARTIP
- Added IRL airlines to the airports
v0.4
- Added additional configurations
v1.0
- Added ARTIP1X transition to runway 36R
- Tweaked EHRD arrival rate
- Tweaked airline mixture
Credits
All coordinates and other information with respect to EHAM/EHRD where directly taken from the eAIP.