NavData seemingly corrupted - CYQB - AIRAC Cycle 2310 Rev.1

[fdelisle]

Hi,

I have an exhausting problem with the navdata. My example is at CYQB where default navdata provide me with the right departures, but is missing the STARs and approaches on runway 11/29. When I add the navigraph navdata (via navigraph hub), I loose all departures except 2, no STARs and it adds 3 blank RNAV approaches and a VOR approach on runway 06. From what I remember, everything was alright a few days ago. The procedures in navigraph charts are all good, but I don’t have the same in MSFS world map/avionics.

I also see that with or without navigraph data msfs shows the second runway as 09/27 instead of 11/29. Don’t know if it’s relevant to the rest of the issue.

I read and tried everything that have been said in the forums about missing data. Uninstalled/rebooted/etc. multiple times. I have no difficulty reverting back to the default MSFS data, but as soon as I install AIRAC Cycle 2310 Rev.1, it gives me this weird template.

So, am I having a problem or is the data really wrong in this cycle?

If it helps:

• AIRAC Cycle 2310 rev.1
• Navigraph Hub 1.2.4

content.xml:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Priorities>
  <Package name="navigraph-navdata-base" priority="1"/>
  <Package name="navigraph-navdata" priority="2"/>
</Priorities>

Thanks in advance for the help!

[NAVDataOld]

Hi,
thanks for all the details - good job and very helpful. Such postings are great - thank you very much at least for your first posting here. Well done - much appreciated.

The problem is not corrupted navdata - all looks perfect and correct, but the main issue here is the outdated scenery in MSFS and you have still mentioned it.

In the MSFS you have four runways 09/27 and 06/24 …

… but in real, the you have 11/29 and 06/24:

So, the MSFS stock scenery is outdated.

And this is exactly the issue - MSFS disable terminal-procedures which are can´t be assigned to a runway. You see on the charts, that all STARs are for all runways but with different “transitions” then to the specific runway. and here as example for 11 and 29, which don´t exist in MSFS and therefore the MSFS disable these procedures.

You see this also on the approach page, with the missing runway-idents on different approaches. That´s because the MSFS “find” the runway 11/29 and therefore MSFS cleared the runway-ident and you only see approach-type.

When you find a freeware scenery, which mirrors the real-world you will see all the correct terminal procedures. I have found one here:

Here the correct runways in MSFS:

the SIDs:

the STARs:

the IAPs:

There is nothing changed in the data, nor have I installed any new one. I have only installed the freeware 3rd party scenery. So, it´s a MSFS issue with outdated runway-idents and no corrupt navdata.

Hope that helps a little bit - thanks again for your detailed report and your question.
Cheers
Richard

[fdelisle]

Such a quick and easy solution, THANK YOU!

Really interesting to understand more how the software reacts to discrepencies. This will give me new tools to troubleshoot in the future. I did think about changing the scenery (great one btw), but probably messed up the order. I made a major cleanup of my community folder recently because I had crashes with radionav and understand that I induced my own problem by using default MSFS data hehe.

Cheers!