Missing RNP approach at ZULS inibuilds A340&A350 and PMDG

[Boeing7779xN779XW]

Missing RNP(AR) approach at ZULS when flying inibuilds A340&A350 and PMDG 737&777 in MSFS2024, but I can find these procedures in fenix A320/319/321.（AIRAC-2601）

Here are the screenshots:

ini A343

PMDG 737

fenix A320

I open the navdata file and find the RNP(AR) approach in the database of inibuilds and PMDG aircraft, but the procedure just can’t be found in FMC, maybe there’s something wrong with the database?

Thanks

[NAVData]

Hi,
Thank you very much - I can confirm that. It seems to be a bug in our navdata interface, which Inibuilds and PMDG use. RNP approaches are filtered out, so you can´t select them…

Fenix, iFly, Maddog, FSLabs, Justflight, … don´t use this interface; they use the data directly, so you see such approaches. As you mentioned, the data are included but will be filtered out by this interface.

I have reported it internally to fix this, but I can´t say when it will be fixed because there are many steps after our fix (Marketplace release, Xbox, …). Sorry for that, and thank you for the valuable hint!

Cheers,
Richard

[NAVData]

Hi again,
I must revert my previous posting … It seems more a Inibuild and PMDG issue. It looks like the addons filter out such approaches (route-type: H) and not our interface. Sorry for the misunderstanding.

But this is “expected” because these route types (for RNP approaches) are “new,” and the ZULS RNP(AR) approach is the only real RNP approach in our database.

But anyway, I would recommend reporting this to Inibuild and PMDG that all RNP procedures (for approaches, route type H) will be filtered out by their systems. Sorry for the confusion.

Cheers,
Richard

[Boeing7779xN779XW]

Hi Richard,

Thanks for your detailed explanation, I’ll report this to inibuild and PMDG. But I’m not entirely clear on what you mentioned “real RNP approach”. My temporary measure to solve the problem is replace the approach route-type column with ‘R’.

Cheers

[NAVData]

Hi,
There are several different route types according to the ARINC424 specifications. R, for example, stands for “RNAV approach” but without RNP. H stands for “RNAV approach with RNP approach,” and this is the “real” correct route type. That´s what I mean by “real RNP approach”

Anyway, as a temporary workaround, I have also changed the route type to R because this is implemented in the Inibuilds and PMDG. As soon as we (in our SDK documentation), as the 3rd party devs have implemented the updated route-type, I will rewrite it to H

You can expect the data to change with the next AIRAC 2603, latest …

Cheers,
Richard

[Boeing7779xN779XW]

Hi Richard,

Thanks for your and your teams’ effort, but I still have some doubts.

I just read the ARINC424-23 specifications, as it mentioned:

The following old titles will be coded with a Route Type R:
RNAV (GPS) RWY 09
RNAV (GNSS) RWY 09
RNAV (RNP) RWY 09
The following new titles will be coded with Route Type H:
RNP RWY 09
RNP RWY 09 (AR)
The following new titles will be coded with Route Type R:
RNAV RWY 09
RNAV RWY 09 (AR)

I wondering why RNP approaches except ZULS is coded with route_type R but not H. For example, LPMA RNP Y RWY 05 (AR).

Cheers

[NAVData]

The “reason” is that the ZULS RNP approaches are tailored records and not part of the original source (which follows mostly v18 rules & regulations). That means all standard RNP approaches are coded with “R”. The author of the ZULS approaches used the standard v20, and here you have your own route-type for RNP approaches, and that´s H.

In our use cases, it´s really irrelevant whether it is coded as R or H… According to the current ARINC specs, H would be the correct one, but we primarily use v18 as our reference.

Sorry for the confusion, but it´s a little complicated because we also use different versions across record types in the source, so it is not easy to figure out which version is used for which part of the data.

Hope that brings more light in the dark night
Cheers,
Richard

[Boeing7779xN779XW]

Thanks for your patients to explain this, I now fully understand the whole story.

Best wishes