Hello Support-Team,
No file type is specified when exporting a flight plan in Navigraph Charts. If, for example, you append .pln to the filename, only the departure and destination airports are exported, not the waypoints.
As a paying customer, I expect a timely solution.
Kind regard s
Rainer Polzer
Hi Rainer,
Welcome.
You don’t need to add the pln extension. It will be added automatically when you specify FS2024 pln format.
I just exported
LDDU DCT NERRA DCT NUPSO DCT BARPI DCT SOTOV P66 KPT L608 SUNEG DCT OLIVI DCT EDFH
and had all the waypoints included in the pln file.
Cheers
Ian
Hi Rainer,
This is due to your settings; you don´t see the file extensions because you have not activated it:
When you enable it, you will see the file extension, but the app automatically adds .pln, even when you have disabled it in Windows Explorer.
So, this is not an app issue or similar; it´s a setting in your OS that suppresses the file extension.
Cheers,
Richard
Hi Richard,
thanks for the explanation.
However, the actual problem is that no waypoints are being exported to the flight plan. Only the departure and destination airports are displayed.
As a supplement, I have also exported this flight plan as a PDF.
Flightplan.pdf (806.1 KB)
Kind regards
Rainer Polzer
Hi Rainer,
Can you upload the raw PLN file instead of the PDF, please, so that we can check the content? It could also be a 3rd party package issue on your system. Please upload the PLN file first, and let me know if you have installed any 3rd-party packages in MSFS2024.
Thank you,
Richard
Hi Richard,
attached you find the PLN file:
LDDUEDFH_M24_11Jun26.pln (5.6 KB)
My installed packages cover basically weather, airplanes and airports. These are:
AccuSeason
ActiveSky
iniBuilds
Aerosoft
JustFlight
PMDG
Best regards
Rainer
Hi Rainer,
Thank you very much for your fast answer …
I have checked the pln file, and now it is clear that you have issues beyond the pln file, since it contains all your waypoints …
This is the content of your uploaded pln-file - you see every waypoint from our app. So the export works as expected:
<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document>
<FlightPlan.FlightPlan>
<DepartureID>LDDU</DepartureID>
<DestinationID>EDFH</DestinationID>
<Title>LDDU - EDFH</Title>
<Descr>LDDU to EDFH created by SimBrief</Descr>
<FPType>IFR</FPType>
<CruisingAlt>14000</CruisingAlt>
<AppVersion>
<AppVersionMajor>12</AppVersionMajor>
</AppVersion>
<DepartureDetails>
<RunwayNumberFP>11</RunwayNumberFP>
<DepartureFP>MADO1W</DepartureFP>
</DepartureDetails>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ICAO>
<ICAORegion>LD</ICAORegion>
<ICAOIdent>MADOS</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ICAO>
<ICAORegion>LD</ICAORegion>
<ICAOIdent>NETKO</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ICAO>
<ICAORegion>LD</ICAORegion>
<ICAOIdent>PALEZ</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ICAO>
<ICAORegion>LI</ICAORegion>
<ICAOIdent>RIFEN</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ICAO>
<ICAORegion>LI</ICAORegion>
<ICAOIdent>RISOM</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ICAO>
<ICAORegion>LI</ICAORegion>
<ICAOIdent>SOTOV</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>P66</ATCAirway>
<ICAO>
<ICAORegion>LO</ICAORegion>
<ICAOIdent>NIGEB</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>P66</ATCAirway>
<ICAO>
<ICAORegion>LO</ICAORegion>
<ICAOIdent>MOGTI</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>P66</ATCAirway>
<ICAO>
<ICAORegion>LO</ICAORegion>
<ICAOIdent>NESES</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>VOR</ATCWaypointType>
<ATCAirway>P66</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>KPT</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>L608</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>KUNOD</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>L608</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>TEDGO</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>L608</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>KOVAN</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>L608</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>SUNEG</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>L608</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>BANIM</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>L608</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>ULNOK</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>L608</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>MISGI</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint>
<ATCWaypointType>Intersection</ATCWaypointType>
<ATCAirway>Z104</ATCAirway>
<ICAO>
<ICAORegion>ED</ICAORegion>
<ICAOIdent>OLGIL</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ArrivalDetails>
<RunwayNumberFP>21</RunwayNumberFP>
<ArrivalFP>OLGI4B</ArrivalFP>
</ArrivalDetails>
<ApproachDetails>
<ApproachTypeFP>ILS</ApproachTypeFP>
<RunwayNumberFP>21</RunwayNumberFP>
</ApproachDetails>
</FlightPlan.FlightPlan>
</SimBase.Document>
What does not work, therefore, is the import in the sim, and I’m pretty sure this is due to one of the 3rd-party sceneries you have installed. One (or more) packages are not 100% SU3+ compatible and therefore mess with the waypoints.
I would highly recommend this FAQ … as a first step, move all scenery-packages somewhere out of your community folder. After that, start the sim again and try the import again - in nearly 99% the cases you will see that it is working.
By the way, I have tried to import your flightplan into my system, and it works:
So, it is not related to our data or our apps. The flightplan will be created correctly, as you see it´s more of an issue with your system. Follow the steps in the FAQ, and I´m pretty sure you can fix this (even when it is time-consuming - but there is no other way to fix it).
Cheers,
Richard
Hi Richard,
many thanks for the truly comprehensive explanations. I deleted the content file as instructed in the FAQ and restarted FS 2024, but that didn’t help. I’ll see how I can implement your other suggestions now. It is, however, a very tedious and time-consuming process …
Kind regards
Rainer
Hi Rainer,
You’re welcome… I would really try to move all your 3rd-party packages (excluding our navdata packages) out of the community folder first. After that, restart the sim and check if the flightplan can be loaded successfully.
That is really the first step and shows you very quickly if you/we are on the right path.
Good luck 
Richard
Hi Richard,
in the course of further research, I stumbled upon the tool Little Navmap. I used it to generate a flight plan with a wide variety of waypoints, and lo and behold: the flight plan — including almost all the waypoints — displays correctly in FS 2024 and is flown successfully 
This also works when I create a flight plan in SimBrief and then import it into Little Navmap. So, I’ve managed to work around the problem for now !
That said, I’m sticking around as a paying subscriber and hope that it will eventually work properly
Thank you once again for your support !
Kind regards
Rainer
Rainer, have you tried the suggestion in my previous posting? If so, please upload your content.xml file here so we can check it.
It is difficult for us when you write several times that you expect a solution because you are a paid subscriber, and then you don´t follow our suggestions/recommendations. And by the way, for us, it is not important, if you are a customer with or without a subscription - we try to help everyone here, so it is not really necessary to mention that every time.
I have shown you in my previous postings that:
So, please follow the steps in the FAQ
Cheers,
Richard
Hi Richard,
I’m sorry if I stepped on your toes… I think it’s really great that you are so committed to this matter!
As previously mentioned, I deleted content.xml and restarted FS 2024 — without success. I have attached the file .
I actually find your company’s work remarkable and the wealth of information — including the newsletter — very interesting. And that holds true regardless of whether I’ve found another tool or no t…
Kind regards
Rainer
Content.xml (103.7 KB)
Hi Rainer,
But in the FAQ, there are a lot more steps, and not only to delete the content.xml file. As I mentioned before, I´m 100% sure you are using a 3rd-party package/scenery that isn’t 100% SU3+ compatible.
So, please look at the FAQ again, especially the “What else can you try?” and here #1, that is the important one. Move ALL packages from your community folder to an external location, excluding the navigraph-* folder. After that, restart the sim and try to import the flightplan as before.
Please upload the content.xml file again (after you have moved all packages) and report back your result - you have a lot of 3rd party packages installed.
Thank you,
Richard
How do you remove and reinstall packages from the community folder if they are encrypted and protected by the Marketplace Store’s security?
Not remove, move it somewhere outside the community folder …
I don´t use Marketplace, so I can´t answer this, but I assume you can disable it, as with every other package.
Cheers,
Richard
Marketplace purchases are not installed in the community folder, but they can be disabled and/or uninstalled using the Content Manager.
If you have many such purchases, it is a bit slower because it’s harder to disable them all at once.
Regards,
Tim
Hi Richard,
I deleted the contents of the Community folder and kept only the Navigraph folders there (current content.xml attached).
I restarted FS2024 — and lo and behold: flight plans created with Navigraph Charts appear in the EFB and can be flown successfully
It is truly amazing what an impact add-ons can have; I honestly hadn’t expected tha t.
So, your recommendation worked!
In the near future — as you suggested — I will gradually move my add-ons back into the Community folder, grouped by manufacturer. That way, I can see how it affects the importing of Navigraph flight plans …
Once again, thank you very much for your help, and all the best to you!
Kind regards
Rainer
Content.xml (93.8 KB)
