Today I have encountered a navdata problem when flying to Cork.
I was flying inibuilds/Asobo A320neo v2 and the ILS frequency in the FMS for runway 26 was 109.5, whereas it should be 109.9 I believe. In any case it did not work.
Truth be told, I am not sure if this discrepancy is due to Navigraph, as I am not quite sure how ini 320 processes navdata, so if it is not the Navigraph issue, then apologies for bringing it up here (just kindly point me out in the correct direction, as I would like to report this bug so it can be resolved for the benefit of the community ).
As for the tech info:
Win 11
FS2024 SU4
Stock iniA320, stock EICK (handrafted Asobo, no modifications)
AIRAC update 2602, applied yesterday
I cannot tell if the problem had been present in previous cycles, as it was my first time ever flying to Cork, on whatever aircraft.
Hi,
I assume something is wrong with the handcrafted EICK scenery (or a mix of aircraft + scenery). When you disable it, you see the frequencies on the arrival page:
Further, I have tested this with the G1000, and here you can receive the correct signal on 109.90 (ICS) for ILS16 (with or without the handcrafted scenery). So, it looks like an aircraft issue. The G1000 is our reference because we know 100% that this device is using the latest WT navionics framework. I don´t know if the Inibuild A320v2 uses it.
You see, ILS is captured on frequency 109.90 with the ident ICS for runway 16.
Again, I can´t really say if this is now a scenery or an Inibuilds A320v2 issue, but what I can say (and you can test this by yourself with the G1000) is that it´s not navdata related because the frequency is correct in the data.
I would report this to ASOBO/MS for further investigation. The approach page alone is very strange for me (with and without frequencies). By the way, this also happens when you use the stock navdata.
Thank you very much for the comprehensive reply!
I’ll go to the inibuilds support forum for default aircraft then, as I have little hope of getting anything done via Asobo.
).
