Hello all,Just to prevent frustrating situations during approaches, especially when flying on-line, I thought I'd share this: The ILS frequency for runway 05R, which comes with the fantastic Manchester Xtreme scenery (108.90), is not correct. Up to date maps and AIRAC cycles show 111.55 as the right frequency. Thanks to good old AFCAD (or ADE) this can be solved within seconds...Regards,Ren

Hello all,Just to prevent frustrating situations during approaches, especially when flying on-line, I thought I'd share this: The ILS frequency for runway 05R, which comes with the fantastic Manchester Xtreme scenery (108.90), is not correct. Up to date maps and AIRAC cycles show 111.55 as the right frequency. Thanks to good old AFCAD (or ADE) this can be solved within seconds...Regards,Ren

Rene,Have you advised Gary of this so he can include it in the update?

Hi Ray,Not yet. I first tried to bring it up in the UK2000 forum, but I need to register, which apparently may take up to 48 hrs.Regards,Ren

Hi Ray,Not yet. I first tried to bring it up in the UK2000 forum, but I need to register, which apparently may take up to 48 hrs.Regards,Ren

With new airport design editors out I would be cautious in using AFCAD for other than AFCAD created files. AFCAD can corrupt files created by ADE9X (Airport Design Editor usually having AFD_ in the file name) or AFX (usually having AFX in the file name). AFCAD files by convention have AF2_ in the file name.Some navaid information is in a separate layer that will show up in the AFCAD search as displaying no airport scenery objects. Check that "blank" layer for navaid lists. They are there to work around FS limitations.The best route is to ask on the UK2000 forum what is safe to use.If using Radar Contact be sure you have the latest version of makerwus.exe and rebuild the scenery database after any change.It also would be safest to backup the airport scenery folder to preserve the .bgls in case you need to restore them and if you have the room the texture folder as well. Navaid information might be in a .bgl name not easily recognized so best to backup all the .bgls.

With new airport design editors out I would be cautious in using AFCAD for other than AFCAD created files. AFCAD can corrupt files created by ADE9X (Airport Design Editor usually having AFD_ in the file name) or AFX (usually having AFX in the file name). AFCAD files by convention have AF2_ in the file name.Some navaid information is in a separate layer that will show up in the AFCAD search as displaying no airport scenery objects. Check that "blank" layer for navaid lists. They are there to work around FS limitations.The best route is to ask on the UK2000 forum what is safe to use.If using Radar Contact be sure you have the latest version of makerwus.exe and rebuild the scenery database after any change.It also would be safest to backup the airport scenery folder to preserve the .bgls in case you need to restore them and if you have the room the texture folder as well. Navaid information might be in a .bgl name not easily recognized so best to backup all the .bgls.

Norman over at UK2000 has stated that you should ONLY use ADE to modify the EGCC files...Just a heads up,-Paul

The ILS frequency for runway 05R, which comes with the fantastic Manchester Xtreme scenery IS 108.90 which IS correct. :(

The ILS frequency for runway 05R, which comes with the fantastic Manchester Xtreme scenery IS 108.90 which IS correct. :(

I based my initial post on Navigraph data (current airport charts as well as AIRAC), which I assumed to be correct. Meanwhile I discovered that the UK aeronautical information service (NATS UK) indeed mentiones 108.90. So it seems that the problem lies in the Navigraph data rather than in the UK2000 scenery, although it is at least surprising that Navigraph would make such a mistake. Fact remains that the non-compliance between the widely used Navigraph data and the scenery may create (already has created) confusion.As far as changing an airport file with AFCAD is concerned: I was not aware of the wisdom brought forward by ronzie and psolk and I'm grateful for their posts. I did not have difficulties though in opening the particular EGCC file with AFCAD (filename starts with AF2) and making changes, such as removing double nodes and correcting missing links. But I should also add that after changing the file ATC behaves strangely in assigning approaches, e.g. giving instructions for a visual approach for rwy 23R . Can't imagine what the relation is with the changes I've made. :( Regards,Ren

I based my initial post on Navigraph data (current airport charts as well as AIRAC), which I assumed to be correct. Meanwhile I discovered that the UK aeronautical information service (NATS UK) indeed mentiones 108.90. So it seems that the problem lies in the Navigraph data rather than in the UK2000 scenery, although it is at least surprising that Navigraph would make such a mistake. Fact remains that the non-compliance between the widely used Navigraph data and the scenery may create (already has created) confusion.As far as changing an airport file with AFCAD is concerned: I was not aware of the wisdom brought forward by ronzie and psolk and I'm grateful for their posts. I did not have difficulties though in opening the particular EGCC file with AFCAD (filename starts with AF2) and making changes, such as removing double nodes and correcting missing links. But I should also add that after changing the file ATC behaves strangely in assigning approaches, e.g. giving instructions for a visual approach for rwy 23R . Can't imagine what the relation is with the changes I've made. :( Regards,Ren

I based my initial post on Navigraph data (current airport charts as well as AIRAC), which I assumed to be correct

Indeed. I have noticed recently more and more charts and AIRAC data from Navigraph have wrong, missing or outdated elements. I will have to report it in their forums. Also departing from Paris to Manchester I had no ATREX point in my EMB-170 FMC, which is a SID point for LFPG (present in their charts for a change). Here is the EGCC 05R excerpt from Navigraph charts (the latest set): I'll have to double check everything before the weekend VATSIM Manchester flyinn.

As far as changing an airport file with AFCAD is concerned: I was not aware of the wisdom brought forward by ronzie and psolk and I'm grateful for their posts. I did not have difficulties though in opening the particular EGCC file with AFCAD (filename starts with AF2) and making changes, such as removing double nodes and correcting missing links. But I should also add that after changing the file ATC behaves strangely in assigning approaches, e.g. giving instructions for a visual approach for rwy 23R . Can't imagine what the relation is with the changes I've made. :( Regards,Ren

@Paul: I thought it would be wise to follow your advice and brought everything back into the original state. I don't intend to touch it any more. Again, your help is very much appreciated.@jvile01: Thanks for the additional explanation. This issue makes me think of changing light bulbs in my car. A decade or so ago I would stop at a petrol station to buy a new bulb, changed it and continued my journey. Nowadays I make an appointment with the dealer. :( Kind regards,Ren

So it seems that the problem lies in the Navigraph data rather than in the UK2000 scenery, although it is at least surprising that Navigraph would make such a mistake. Fact remains that the non-compliance between the widely used Navigraph data and the scenery may create (already has created) confusion.

Surely the fact is that the Navigraph data is simply wrong - full stop?

Surely the fact is that the Navigraph data is simply wrong - full stop?

Rafal wrote that he will bring the subject up in the Navigraph forum. Apart from that I have made two attempts to send them a message, but both attemps failed. Any suggestions?

Is it the chart service being referred to or the terminal procedure code for the FMCs with these errors.

Rafal wrote that he will bring the subject up in the Navigraph forum. Apart from that I have made two attempts to send them a message, but both attemps failed. Any suggestions?