-
Outdated Navdata?
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
-
Outdated Navdata?
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)
-
Outdated Navdata?
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.
-
Outdated Navdata?
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.
-
- Airplane Roll
Théo J
Member
-
Joined
-
Last visited