EDDN ILS 28Z wrong frequenz

[Carlo12 0]

Hi,

 

there seems to be a wrong NAV Data for EDDN.

ILS 28-Z is 109.1, but the CRJ shows 111.75 (LOC 28 Y)

109.1 can not be set, it always reverts back to 111.75

 

AIRAC is 1807

 

 

 

Please login to display this image.

Please login to display this image.

[Hans Hartmann 3694]

That's an issue with the nav database you use. It doesn't contain an ILS on 119.1.

 

This is a Navigraph excerpt for example:

Zitieren

A,EDDN,NUERNBERG,49.498700,11.078008,1046,5000,0,8800,0
R,10,97,8858,148,1,109.550,97,49.500550,11.059169,1022,3.00,47,1,0
R,28,277,8858,148,1,111.750,277,49.496925,11.096025,1046,0.00,50,1,0

 

Unfortunately we can't do anything about it.

 

Edit: of course you manually change it in your airports.txt, but on your own risk!

[JRBarrett 675]

It appears the r/w EDDN airport has a rather unusual situation, where there are two distinct localizers on runway 28. The one on 111.75 is just a localizer only, used for the LOC Y approach, and the other on 109.1 is a full ILS with glideslope used with the ILS Z approach. Maybe this is common at European airports, but I haven’t seen this kind of setup before.

 

If you subscribe to Navigraph FMS data, you might want to pose a question on their support forum. It may be a limitation of their NAV data that a specific runway can’t have more than one localizer frequency associated with it.

 

Edit: Since EDDN has only one runway, 10-28, the localizer-only approach on 111.75 is probably for redundancy in case the main ILS on 109.1 has a failure. The LOC Y and ILS Z approach plates look almost identical. The main ILS on 109.1 is a full CAT III-certified system. For technical reasons, it is unlikely that the two localizers would be active at the same time due to the potential for the two co-located localizer transmitters to interfere with each other. The EDDN tower controller probably has remote control capability to switch on the 111.75 localizer if the main 109.1 fails.

 

If Navigraph can only code one localizer for a specific runway in the nav data, it would probably be better to code for the full ILS on 109.1. For that matter, I’m not sure if FSX/P3D can support two separate localizers on the same runway?

[srcooke 422]

Not quite that uncommon, EDDF for example has dual ILS approaches for 07L/25R

 

Many aircraft addons do not recognize more than the one frequency even when supplied in the database.

 

[Carlo12 0]

On 22.7.2018 at 15:02, Hans Hartmann sagte:

That's an issue with the nav database you use. It doesn't contain an ILS on 119.1.

 

This is a Navigraph excerpt for example:

 

Unfortunately we can't do anything about it.

 

Edit: of course you manually change it in your airports.txt, but on your own risk!

 

I have just updated to AIRAC 1808 and there ist the missing 109.1:

 

A,EDDN,NUERNBERG,49.498700,11.078008,1046,5000,0,8800,0
R,10,97,8858,148,1,109.550,97,49.500550,11.059169,1022,3.00,47,1,0
R,28,277,8858,148,1,111.750,277,49.496925,11.096025,1046,0.00,50,1,0
P,0,49.498611,11.077778,0,0,
.
.
.
P,87,49.495000,11.070000,0,0,
P,9,49.495000,11.078333,0,0,
L,10,INUE,EDDN ILS/CAT I,109.550,49.496453,11.100817,97.00,2.0,49.501711,11.063972,1022,3.00,1
L,28,INUY,EDDN ILS/LLZ NO GS,111.750,49.501172,11.052831,277.00,2.0,0.000000,0.000000,000,0.00,4
L,28,INUW,EDDN ILS/CAT III,109.100,49.501053,11.054047,277.00,2.0,49.498967,11.091378,1062,3.00,3

 

but the FMS only give me the 111.75, so no ILS Landing on RW 28 in EDDN

 

Did a Test with a GTN, correct ILS Settings here:

 

 

 

 

Please login to display this image.

[vali 31]

I had also this issue today on Vatsim, locked to a wrong freq (always nice when it happens on Vatsim with controller online..).

What I do not get, if it is a Navigraph issue, why it happens only with CRJ and not with the PMDG 737 and FSLabs A320, on the same ILS Z 28? I have flown the same approach with all three, only the CRJ is doing this.

A2A with GTN 750 is also OK.

 

My explanation is that on the CRJ it gets locked on, it is in Radio to MAN (not auto), still I can not correct it myself manually as it is locked....