I hope that you are all enjoying this new masterpiece from Emilios and FlyTampa.
I just wanted to put out some notes on the ADE's included with this airport.
First, though I need to say that designing ADE's for addon scenery is a task that falls under the can't please all the people all the time category. Because our own sims are often very customised, with different styles of flying (online vs offline), dedicated AI setups, the willingness to extensively pre-flight vs Ctrl+E and go etc etc its almost impossible to create something that will satisfy everybody, but what I've tried to do here is simple.
My goal was to make an ADE set that can satisfy as many people as possible while replicating the procedures at Amsterdam as closely as the host simulator will allow. And believe me there are many limitations and restrictions in the host sim that can (and have) thwarted my attempts to get even more realism.
So, that said how to get the most from your EHAM experience ADE wise.................
Because of the operations at EHAM it is necessary to create 4 ADE's for varying wind situations. In order to replicate anything close to actual operations its unfortunately unavoidable.
Thanks to a handy app on the LVNL website I was able to track daily ops at EHAM over a 2 month period and came up with the best and most often used traffic flows.
North ADE:
This ADE should be used when the winds are between 290 and 069 degrees
Departing: 36L
Arriving: 36R 06 36C
This was a very frustrating ADE because this was one where FSX/P3D just would not co-operate. On Northerly ops, 36L is the most commonly used departure runway often with 09. The problem with 36L is that it is so far away from the parking stands that with *any* other runway open for takeoff nothing ever gets sent to 36L. The AI engine uses a points scoring system to assign the departure runway and distance from the gate is one of the variables. So the issue was for a Northerly configuration 36L had to either be the only runway open for take off or it would never be used, in this case I decided to have 36L open and send everything up there.
You will notice too that with 36C open for landings all departing traffic will taxi around either the North or South edge of 36C as per real life, no crossing of the active runway will occur.
South ADE:
This ADE should be used with winds between 120 and 229 degrees
Departing: 18L 24 22
Arriving: 18R 18C
In this case arrivals are split between the 2 18's and achieve a good balance. Departures also split fairly well, although slightly favouring 24. 22 should only be used by GA parked down at the GA aprons.
If you don't care too much about swapping out ADE's and using the other runways, these two ADE's will cover you for most of the Amsterdam operations. Note that on a visit to LVNL in 2012 I was advised that crosswind runway assignments have been agreed with operators into Amsterdam up to a component of 90 degrees at 25 knots (subject obviously to any airframe limitations).
If you desire further realism and options there are the following files also available:
East ADE:
This ADE should be used with winds between 070 and 119 degrees
Departing: 09 36C
Arriving: 06 36R
This one was another frustrating one because 09 gathers most of the departing traffic. I tried various ways to get 36C more traffic but nothing worked. So 09 is sadly heavily favoured. Arrivals are split really well about 50-50 between 06 and 36R but there will be long queues for 09
West ADE:
This ADE should be used with winds between 230 and 289 degrees
Departing: 24 18L
Arriving: 18R 27 22
Good arrival split with almost all traffic split between 18R and 27. 22 was an interesting case because even if its closed completely FS would still land traffic on it. I found by opening it for landings mostly E170s and E190s landed there with the occasional 737. There is not a large amount of landing traffic on 22, maybe 15% or so. FS simply ignored the close command in this case, so the runway may as well be open, and I know it is used in very strong Westerly winds for traffic other than GA.
I hope some of this explains some of the choices and limitations. I would suggest using caution when editing the ADE's to modify the runway assignments because there could be a lot of unintended consequences - like having runways open that the ground flow is not designed to accomodate. Everything in these ADE's was done with a purpose. For example in order for the ATC engine to accept a specific runway open or closed for takeoff/landing command *both* ends of the runway have to be set the same. Which is why on the East ADE 27 will show open for takeoff, and which is why if you use this ADE with the wrong winds you will be assigned 27 for departure and have to backtrack down the whole runway. You may ask why don't I just set 09 open for takeoff only and 27 open for landing only? Because for reasons nobody has been able to figure out the ATC engine will then happily disregard both commands and you will get landing traffic on 09 and departures off 27 in the relevant winds. This is why to "force" the ATC engine to respect the command at one end you must force the other end to be the same.
Parking assignments are designed to avoid as much overflow as is possible with airlines parked at the correct areas. You will see different results based on how your AI traffic files are named as FSX loads them alphabetically, so parking gets filled up on first load on that basis. Another limitation is that FS only recognises the first 5 codes of a gate's parking codes. Any codes you enter after the 5th are a waste of time. This is why at a lot of stands KLM will be the 5th code listed because I find it preferable to have as much traffic as possible on jetways rather than heading straight to overflow. Of course a multitude of things play into gate assignment, radius, code etc being just part of the equation.
An airport this complex is always going to throw up ADE issues, I'll be happy to try and address as much as I can but please be aware there are many limitations placed on what the engine can and can't do and often times much of what is desired just can't be done (ie opening 36L and another runway for takeoff)
I will get out an ADE with all runways open for online fliers and those who don't care about AI or wind dependent runways. Unfortunately I'm a bit under the weather at the moment and it was as much as I could do to get this posted. I'll have the online ADE out very soon and then hopefully everyone will be able to enjoy this wonderful airport as much as possible
