Jeepee you realize you just created more problems than you had, right? now the ILS16 is all messed up with your afcad. Why do you insist on deleting runways?
Honestly, your afcads are great, but please dont touch any runways or navaids. Now I am worried that your afcad for EBBR also messed up the navaids.
Hello Al,
I checked once again my AFCAD this evening, performing a slewing along the full ILS 16 ('IZH', 110.50 MHz) localizer and 3° glide path on runway 16, and compared it with official navigational publication (taking into account the correct QNH setting).
As you can see on my screenshots hereunder, I passed respectively the two ILS DME fixes at D8.2 and D3.0 at respectively 4,000 feet and 2,340 feet; which are the precisely correct values on the chart !
And believe me, even in reality, you can't get more precise than this -due to instrumental error or atmospheric conditions-.
Even the scenery PAPIs do agree with my AFCAD ILSs.
Sooo... I'm once more convinced that my AFCAD file works as it should.
An official approach plate for the ILS runway 16 at LSZH:
Fully established on the ILS runway 16, passing DME fix D3.0 at 2,340':
The only 'problem' I have when deleting the fake runways is a longer queue at holding points for departure. So what...!? Just choose one another suitable runway (I mean in respect of the given wind) for departure, and you're all done !
If you use all these fake runways, just listen the ATIS, and you'll understand my pain... lol It takes you 1 hour to listen for all the runways currently in use; simply ridiculous !
But once again, I never obliged anybody to use my file; you may of course dislike my point of view. Fine, don't use it then.
Concerning EBBR, just point me any error if you find one, and I'll be more than happy to correct it, if any
