Skipping IAF waypoints on RNAVs

Navigation Data SID/STAR/APPR
1

Noticed this last night after updating to the current build. The RNAV 7 approaches into PAMR all skip the IAF and go straight to the FAF. This was in 2020 on a paid PMS750. I reached out to them and they blamed the navigraph database. On the navigraph approach plate (and my real iFly EFB plate) the IAFs and approach plates are correct, but neither shows up in the approach when loaded from the 750.

To be super specific, 7 Z approach skips the ALSKA IAF and procedure turn and goes direct to TICDU. 7 Y approach skips VEYUK and the procedure turn and goes straight to WOLGI. ATC directs you to the IAF for both.

2

Hi,
That is what I get with the default G1000 with our data installed:

MSFS2020 - no 3rd party scenery used - AIRAC 2605 installed:

image
image1552×1004 244 KB

You see the ALSKA waypoint very clearly, and it is also defined as IAF. You can test this yourself to confirm when using the standard-stock G1000. So far, the data are correct; I can´t see any issue here. The sequence is the same as on the charts.

Sorry, but it looks more a PMS750 issue rather a navdata issue. Try it by yourself, and you will see the correct sequence. By the way, PMS750 uses the same data as the sim, as the default-stock G1000, which I have used here - so, why is this working in the stock G1000 and not in a 3rd party application?

Cheers,
Richard

3

I don’t disagree, they said it wouldn’t be an error on their end. Your explanation is why I reached out to them first, it didn’t make sense that it would be a problem on your end.

4

… but it is an error on their side :slight_smile: … or they can explain why it is working in the stock G1000 but not in the PMS750, both use the same data :slight_smile: … I´m curious about the answer :slight_smile:

Cheers,
Richard

5

Their response was to blame you, then blame the aircraft (Maule M7, T206H, 172 Taildragger, DHC2, and the Toolbar GTN650). So I don’t expect a further explanation or correction from them.

6

Very “professional” answer from the PMS devs … I´m sorry. I would help you when I could, but in this case, it is really a PMS750 issue, and the developer has no interest in looking into it further. It´s a pity, but it is as it is …

The funny part here is that he hasn´t contacted us at least to ask/clarify the issue … that is the common way … :thinking:

Thanks for the update. Let me know when we can do more for you!
Cheers,
Richard