I’ve flown today to Samscene ZULS. According to developer, ZULS has two runways: 27 and 9, but Navigraph provides up to 4 10L-R and 28L-R. I’ve googled a bit and I only could find the 27 and 9 configuration. The problem is that developer and Navigraph definitions collide and I cannot set correctly the approach in my MCDU. Two questions:
Which is the correct configuration?
Even in case the Navigraph configuration is the good one, how could I ignore that data so I can correctly establish a valid procedure in the sim?
If you reference the Navigraph charts you will see the new runway became active in the December 2023 cycle and the existing runway was re-numbered so NG is correct.
Hi,
not sure what sim nor which addon do you use, therefore a more or less general answer to this.
We use real world data and also real world charts, means exactly the same data and charts will be used from real crews in the cockpits. There is no difference to the reality. China is a special case because they don´t have any real public information about their airports/procedures … but I would trust Jeppesen in this case and the reason is simple:
Look on the charts on the bottom CHANGES info plus the published date - here you read: ... new RWY 10L/28R, other RWY reindexed ... (yellow marker)
So, I´m pretty sure that the data and the charts are correct.
Depending on your sim and addon which you are using, you should select the terminal procedures because we offer it and there is no linkage between a scenery in the sim (stock or 3rd party) and the data in your addon - excluding the MSFS.
When you use MSFS you can´t select the terminal procedures because MS/ASOBO disables the terminal procedures (even when they exists in the data) when a terminal procedure can´t be assigned to the runway in the scenery. So, when the scenery in MSFS is outdated and the runway-idents are changed or as in this case a runway is missing due the real-world change than you can´t select the terminal procedures (again, even when you have it in your dataset - which is the case). So in MSFS you have only two options:
wait on MS/ASOBO for an airport-update
or use a 3rd party scenery, which includes the correct runways and which reflects the reality
In both options you will immediately see the terminal procedures without any patch/fix or similar else from our side because you still have the correct procedures in your dataset.
Just for completing all the information, simulator was MSFS and scenery was made by Samscene3D. After your reply I’ve sent them and e-mail reporting the mismatch and requesting and update.