ICAO code SBFN, any approach other than a visual approach causes to malfunction

Hi. For ICAO code SBFN, any approach other than a visual approach causes the flight planner / navitation system to malfunction.

Tested with navigation systems on numerous aircraft; occurs in MSFS 2020/2024 and X-Plane. This issue isn’t limited to the latest version of Navdata; it’s been happening ever since I started using Navigraph.

Can you please explain what you mean by malfunction more specifically?

Regards,

Tim

Hi. Navigation systems behave similarly across all aircraft. The approach is not displayed, or is displayed incorrectly. The flight plan is interrupted and cannot be resumed. Features such as “direct to” a point on the approach do not work. The entire approach fails, meaning navigation stops working. It’s best to try an approach to SBFN yourself. No approach other than a visual approach works.
Regards, Joerg

Hi Joerg,
To be clearer and correct, only the RNP approaches will not be shown on the ND, but all approaches are available. When you look at the sequences, you see all the correct waypoints.

Here from MSFS2024 in the stock G1000:

… and here the same with the VOR approach:

You see in the second screenshot the full, correct path …

I can´t reproduce it in X-Plane 12, because here the path is drawn correctly (beside all the correct waypoints):


Without analyzing it in detail, I have seen that the RNP value in our database is 0 for these legs, which is incorrect and a bug. It could be that MSFS can´t draw the legs correctly due to this bad information, but I must look into it further and will fix the RNP values in the next AIRAC 2607.

Thanks for the example, I will keep you informed here when it´s fixed.

Cheers,
Richard

Hi Rechard,

yes, the VOR approach works too—I forgot to mention that. And the two visual approaches RWY 12/30. All 4 RNP approaches to RWY 12/30 are not working. I can only describe this from the perspective of a user/customer/subscriber, and I’m only reaching out because I’ve consistently encountered this issue in both flight simulators and with all navigation devices across all aircraft models I’ve used.

The more people report such issues, the better, more accurate, and more reliable the Navdata will become. Everyone stands to benefit from this :wink:

Regards,

Joerg

Exactly, Joerg, no problem - I will look into it further in the coming days, but normally you should expect a solution with the next AIRAC 2607 (not with 2606, which is still ready for Thursday).

Thanks, and I’ll keep you informed
Richard

Hi Joerg,
I have looked into it further, and it seems this is more of a sim issue. I have tried testing this without our data (using the stock data), and you see exactly the same behavior. You can select the approaches, but you don´t see the flightpaths.

In this case, please report it to ASOBO/MS, as it appears to be a possible global issue with the stock scenery.

MSFS 1.7.27.0 without our AIRAC installed:

Same situation… You can select it, but you don´t see the flight path below → sim issue, rather a navdata issue on our side.

Cheers,
Richard

Hey there, Richard,

I’ve just reactivated and updated the X-Plane flight simulator—which I rarely use—and updated him and the Navdata as well. Then I checked the approach to SBFN in the navigation module for some aircraft models. The approach legs for RNP approaches are (now) displayed there. I haven’t actually flown them yet. I don’t really like using XP anymore. But the legs weren’t displayed there about a year ago either. So it was similar to MSFS. So, it seems to be working now in XP, but not in MSFS. Thanks a lot for your explanations. I’ll reach out to MS/Asobo with a reference to our thread here.

It’s all very strange. I’ll keep you updated here if I hear anything.

Best regards, Jörg

Joerg, I will check this directly with a WT guy in the next couple of days. Possibly he has an idea …

Will keep you informed here!

Cheers
Richard