Hi!

When I try to select EDDL ILS24L I get NAVAID NOT IN DATABASE

In the OIS, I note that the navigraph data is outdated:

2610 rev 1 is outdated; rev 2 was released about 2 weeks ago (https://forum.navigraph.com/t/release-notes-msfs2024-airac-cycle/18116)

How do I get r2 into my plane? Pressing Update data does nothing, it's still r1 even after restarting the sim.

(I get the same error with EDDL ILS23L on "sim default" data btw)

I don't know if it's needed, but I have also installed the navigraph data in my community folder

Edited Monday at 07:02 PM3 days by Gungnir

1 minute ago, Gungnir said:

Hi!

When I try to select EDDL ILS24L I get NAVAID NOT IN DATABASE

In the OIS, I note that the navigraph data is outdated:

2610 rev 1 is outdated; rev 2 was released about 2 weeks ago (https://forum.navigraph.com/t/release-notes-msfs2024-airac-cycle/18116)

How do I get r2 into my plane? Pressing Update data does nothing, it's still r1 even after restarting the sim.

(I get the same error with EDDL ILS23L on "sim default" data btw)

is EDDL 3rd party or default scenery?

From my understanding the R1/R2 navdata updates are only for the base airac, aircraft do not need to be updated!

Thanks 🙂

Hi! It's a 3rd party airport. I also tried with that scenery disabled, and get the same thing. Same for ILS approached at all four runways at that airport btw.

Edited Monday at 07:17 PM3 days by Gungnir

Hi!

I’ve also encountered this issue with Navaids at several airports—both third-party and default—and I’m wondering if it might be related to another problem I’m having with ILS capture… I consistently end up too high or too low during the approach (both with the A350 and the A380). Could this simply be an issue with the AIRAC version?

Thanks.

42 minutes ago, Théo J said:

Hi!

I’ve also encountered this issue with Navaids at several airports—both third-party and default—and I’m wondering if it might be related to another problem I’m having with ILS capture… I consistently end up too high or too low during the approach (both with the A350 and the A380). Could this simply be an issue with the AIRAC version?

Thanks.

Which ones? I can check too

Regarding Navaids, I encountered the issue at EGLL (3rd party). As for ILS, it occurred at LSZH (default) with the A350 and at LEMD (default) with the A380. I hope this is clear; the text has been translated from French.

13 minutes ago, Théo J said:

Regarding Navaids, I encountered the issue at EGLL (3rd party). As for ILS, it occurred at LSZH (default) with the A350 and at LEMD (default) with the A380. I hope this is clear; the text has been translated from French.

I have iniBuilds EGLL, and I get no NAVAID warnings when selecting EGLL ILS approaches:

Okay,

I ran another test using the same flight plan as yesterday (EGLL to LSZH). I was wrong about EGLL—it works perfectly.

When I import via CPNY F-Plan Request and select the ILS in Zurich, I still get the “Navaids not in database” error. Same thing happens with a flight plan to LEMD.

But here’s the strange part: if I select a new destination from the F-Plan and then select the ILS in Zurich again, I no longer get the error message.

Here’s how to reproduce the problem.

CPNY F-Plan Request

Set departure (No problem)

Set Approach (Problem)

Set new destination airport (LEMD, for example)

Set Approach (No problem)

9 minutes ago, Théo J said:

Okay,

I ran another test using the same flight plan as yesterday (EGLL to LSZH). I was wrong about EGLL—it works perfectly.

When I import via CPNY F-Plan Request and select the ILS in Zurich, I still get the “Navaids not in database” error. Same thing happens with a flight plan to LEMD.

But here’s the strange part: if I select a new destination from the F-Plan and then select the ILS in Zurich again, I no longer get the error message.

Here’s how to reproduce the problem.

CPNY F-Plan Request

Set departure (No problem)

Set Approach (Problem)

Set new destination airport (LEMD, for example)

Set Approach (No problem)

I believe this is known sim issue at Zurich, but will verify with the team on my end.

Appreciate your patience 🙂

3 hours ago, iniKyle said:

I believe this is known sim issue at Zurich, but will verify with the team on my end.

Appreciate your patience 🙂

But how can it be a sim issue if two different ways of entering the data into the plane gives an error in one case and not in the other? And this is not only LSZH but LEMD and EDDL and probably many others.

I can confirm that LEMD ILSW32R gives NAVAID NOT IN DATABASE error when it's imported via simbrief...

...and nothing when LEMD was entered manually as destination on the INIT page

Edited Tuesday at 06:01 PM2 days by Gungnir

Thanks for the clarification. I believe I was thinking of something different. I will log this for the team to review as soon as possible!

Adding EPDG to the list (another airport I bought via the inimanager...).

3 minutes ago, Gungnir said:

Adding EPDG to the list (another airport I bought via the inimanager...).

Adding to the list for the team to review, thanks again!

Hello everyone,

I just tried it with the newly arrived AIRAC 2611, and it's still the same problem. So it probably wasn't caused by the previous AIRAC.

And I haven’t really gotten any feedback about the ILS approach being too low, even with third-party airports. I imagine this is related to the NAVAID issue, but if that’s not the case, I’d be happy to start a new thread.

Thanks, Kyle

2 hours ago, Théo J said:

Hello everyone,

I just tried it with the newly arrived AIRAC 2611, and it's still the same problem. So it probably wasn't caused by the previous AIRAC.

And I haven’t really gotten any feedback about the ILS approach being too low, even with third-party airports. I imagine this is related to the NAVAID issue, but if that’s not the case, I’d be happy to start a new thread.

Thanks, Kyle

Hi Theo,

No need to start a new thread. I see the team is working on fixing the NAVAID issue, so I'm hopeful that will also solve the ILS being too low.

Thanks for your patience 🙂