Sorry to hear that, but we have no other reports here and I don’t see some in the MSFS forum.
There are a on going discussion about the file formats and how the fkightplans will be created.
When this would really an major/general data issue, then we should see a lot!!! more reports, but nothing.
Cheers
Richard
I receive just now an update (not beta) of the sim and I was also insrall the nes texas city upgrade… after that and with all the packages updated… the north pole issue is happen to me also.
Of course navigraph cycle updated
Hi,
thanks for the report … I haven’t installed the Texas update at the moment, but I will do it for testing.
Can you upload your file please, that we can check it before/after the update.
Have you tried the same as FLT file too instead of PLN?
Thank you
Richard
Exactly the same issue for me, flight plans that were working fine before the recent sim update are now pushing me up to the North Pole.
Ok, we know that now thanks but as I have requested/asked in the previous post:
Does this happen also when you use FLT flightplans instead PLN?
Please can you upload a sample flightplan to reproduce?
… and possible third:
When you remove the Texas update again, loads the flightplan correctly then?
Thanks for the help, but we need anything on base information to see if thats an issue on MSFS or on our side. Only confirm, that this happens to you also is fine but doesn’t really help.
Cheers and thanks for your understanding
Richard
GREAT —I do not feel so alone and “special” anymore – the North Pole issue is now being reported by others. For the longest time, it seemed that I was the only 0ne having this issue …
Welcome to the “North Pole Club” guys !!
Sorry, but I have shown you that you’re special … No other reports before expect your report.
I will test it with and without the Texas update, as soon as I have received a test flightplan and will post the results. I’m currently not sure, about the changes in this update, but when this happens again, they must change anything. I will find out …
Cheers
Richard
PS: 3 of 300.000 MSFS user
I do have same issue since the update of yesterday too…
Hopefully to prove that we’re not “special” and there is something broken here.
My Setup
Windows 11 Insider Release Candidate
Latest Little Nav Map
Latest Navigraph Airac installed to Sim and Little Nav Map
FS2020 updated with recent Avionics update. NO TEXAS update installed
**CREATING THE ISSUE"
**WHEN DID THIS HAPPEN"
On Monday this week i tested the attached flight plan and it was working fine
Since then an incremental avionics update was deployed in FS2020 circa 700MB
Now when i load the same flight plan i get the north pole issue
“FIXING THE ISSUE”
Remove AIRAC cycle data from the NAVIGRAPH HUB, the flight plan is fine again. Indicating that this issue is with the NAVIGRAPH data.
I have attached an example flight plan and screenshots before and after removing Navigraph data.
VFR Camilo Ponce Enriquez (SECA) to Chagual Airport (SPGL).pln (12.3 KB)
Hi,
thank you very much for the details - the first one!!! Good stuff …
No, it´s not a navdata issue it´s some other issue, possible in the cache or similar else - I don´t know because I have tried to load your flightplan now:
You see, I have installed 1.33.8.0 with all updates, AIRAC 2306 rev.2 installed … flightplan loaded without any issue. We are sadly not in the situation to debug deeper but as you see it works …
In most of the environments it works (at least with all WU installed). There are several postings here and also in the MSFS forum which confirms this. I know that doesn´t help you but on the other hand it indicates me, that this has nothing todo with the data itself because also I can´t reproduce this issue (as you see in the video).
What you can try as a test, close the MSFS completly … delete all the “scenery index” files in your %localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes folder, or delete the rolling cache when you use someone. The scenery-indexes will be automatically created when you start the sim again.
But again, I can´t identify any issue on our side, sorry.
Cheers,
Richard
… another test:
Create the same PLN flightplan directly in the MSFS and NOT! in LNM or any other external application … close the MSFS, start it and load the flightplan again. Because all flightplans what I have received looks differ to the MSFS created flightplan PLN file - possible that´s also an issue, I don´t know …
Cheers,
Richard
Are you on the the insider release of Windows 11? There was a update at some point early this week that may have something to do with the issue
TEST.FLT (12.8 KB)
TEST.PLN (2.6 KB)
EDHK-EDDH ILS.SPB (225 Bytes)
.
I’ve also encountered the North Pole tracks issue. I removed all content from the Community Folder with the exception of Navigraph content - the issue occurs. Remove the Navigraph content - the issue is fixed.
The problem occurred after the update for MSFS this morning. I’ve also installed the Navigraph updates for today.
No, I don´t use the Windows Inside version - I´m always on the stable version. Possible that is the reason why it works here and not on other system but I don´t know.
What I have done now is:
I have compared the previous version with the current version and again, ASOBO/MS has removed a lot of airports - also existing one (ie. 08AR, OEPA, NTKK, WAFO, …), plus they added a few (ie. NZAG, NZOB, )…
In the past, this was exactly the issue …
I´m not sure, why they add, change or remove existing airports with nearly every update but they do it on every update now (in the past, I thought, it´s only with the WUs). For us, it means we should rebuild the AIRAC files again to be in sync with the MSFS.
I´m not sure, if this will help because I can´t reproduce this issue as you see - also not with the new TEST.PLN files from @Joburgal
… loaded correctly on my system, sorry.
… exactly that is wired … why does this work with the FLT format but not with the PLN format? Both use the same data … I´m still be sure, that there is somewhere a bug in the MSFS but I can´t say where and why, also why this doesn´t happen on all systems. Most of our users have no issue … also I.
So, main question again:
Do you have installed ALL!! World Updates (possible it´s enough, at least the latest WU13 “Oceania & Antarctica” update) and are all “Up to date”?
Cheers,
Richard
PS: silly question - I miss WU 9 …
… ok, when I remove the latest WU13, I can reproduce it too … so, please check if you have installed at least the latest Word-Update. It is also recommended to install all WU even when you don´t fly in this area. The reason is simple as I have written before:
ASOBO/MS changes and removes airports with nearly every update but you get a world-wide navdata base, where such airports are still included (because existing). I assume, there is some bug in the linkage between the internal MSFS airport list and an external airport list but we don´t know exactly what happened behind the scene but it´s sure, that ASOBO/MS must re-create some files too in the background during the update or later. How knows this …
Here, WU13 de-installed - issue reproduceable with exactly the same flightplan as before:
Cheers,
Richard
Yes all world updates are installed 1-13 and up to date. I’m only missing two City Updates (Texas and France) will see if this does anything.
I guess the million dollar question is what is different for the 4 of us that are currently facing the issue 
Appreciate your support!
Honestly, I assume not … even when I can´t say why I assume this …
EXACTLY - this is really the million dollar question … I´m still looking arround, to reproduce your issues but I can´t (only removing the latest WU13) but you wrote you have installed all WUs so … back to the start 
Cheers & thanks - still debugging …
Richard
Correct on City Updates, both installed and nothing changes. Worth trying
Sorry that not answer you until now, I made some test and here is the result:
Tests:
5) I tried my first file, called file1.pln that has not have those nodes in the xml (the *.pln):
5.1) without navigrapgh cycle it is load OK
5.2) with navigraph cycle, it is loaded with the error
6) a modified file, called file2.pln, with those nodes inside, is loaded OK even with the navigraph cycle
Attached are both files: file1.pln and file2.pln, also screen captures with and without the error.
Regards
Ernesto Aides
file1.pln (2.3 KB)
Thank you very much for the insides and your testing Ernesto - much appreciated …
I´m currently working on a airport-sync with the newest MSFS version and I will release a second revision. As I have written before, this was in all cases the solution due the MSFS airport updates but I can´t guarantee it because I find no way to reproduce your issue. Anyway, it´s worth to try … working on it.
Cheers & thanks again - great to get back a such good feedback/test report
Richard
PS: currently, re-installing WU13 
