DC-3 Airways Annual World Tour

General Category => General Discussion => Topic started by: Glen-WT on Oct 03, 2026, 11:13 AM

Title: MSFS2024: LNMPLN conversion to PLN Hiccup
Post by: Glen-WT on Oct 03, 2026, 11:13 AM
Preparing for flight 01 I downloaded the LNMPLN file & ran it through Little Nav Map to get a PLN version for use in the Garmin GNS530 that my Retro fitted DC-3 uses. I have found that when I fire up the 530 & have a look at the flight, the magenta line misses out LFNC, ie, takes a short cut to the next waypoint. Is there another way I can get a PLN that is identical to the LNMPLN?
GS
Title: Re: MSFS2024: LNMPLN conversion to PLN Hiccup
Post by: 1161 Roy Möhlmann on Oct 03, 2026, 11:32 AM
Yes you can. In LittleNavMap go to the menu File. There you will find some Exports to pln-file for different simulators.
Roy
Title: Re: MSFS2024: LNMPLN conversion to PLN Hiccup
Post by: Glen-WT on Oct 03, 2026, 12:01 PM
Did that Roy, but I'll have a closer look at the various formats available, I may have chosen the wrong one.
Thanks
GS
Title: Re: MSFS2024: LNMPLN conversion to PLN Hiccup
Post by: Glen-WT on Oct 03, 2026, 12:49 PM
You were correct Roy. I reloaded the LNMPLN & then found the export choices, chose MSFS2024 & this time map is ok. I think I inadvertently loaded an MSFS2020 conversion the first time around.
One thing I have learned is that above 10,000', definetly need the Superchargers.
Thanks
GS
Title: Re: MSFS2024: LNMPLN conversion to PLN Hiccup
Post by: Alan-WT on Oct 04, 2026, 04:55 PM
Some of the waypoints in the published flight plan might contain waypoints that no longer exist in your particular simulator's world. I fly twice a week or so with the A2A Misfit Squadron, and this happens frequently. We've got the original flight plan, created either on LNV, or maybe on SkyVector. Either way, all we get on the A2A Forum is a bunch of instructions and other data, along with a link to the flight plan on SkyVector. I get the flight plan off of SkyVector and copy/paste it into the Flight PLan Route Description window in SkyVector. Quite often one or two of the waypoints don't show up, either in my P3D version of LNV, or maybe in my Reality XP GTN 650 or 750.

Here are a couple possible fixes:

If a waypoint is not showing in the flight plan, simply add that point into your flight plan by moving the magenta line to add in a new WPn. Or, if you wanna get fancy, add in a custom user waypoint at the Lat/Long coordinates of the missing waypoint.

I then save my tweaked flight plan using the multiexport button, with one flight plan going to my .PLN folder, and another going to the Garmin GTN750 flight plan folder. Here's what works for my RXP GTNs: [C:\ProgramData\Garmin\Trainers\Databases\FPLN]; you'll have to find what your GPS setup uses for flight plan stashage.

OK - what if the crazy guy who made our fight plan included a private airstrip that doesn't show up on my GTN? I check to see if waypoints are "blocked" before our flight. I create a user waypoint at that Lat/Long location in my Garmin GTN in place of the blocked waypoint, giving it the same ID as the ICAO code for that airport.

This happened to me on Flight 2, which is an easy flight through some nice scenery with navigation provided by a series of NDBs. One of 'em was missing in my particular setup. It showed up in my LNV flight plan window as a little red triangle. Bummer. I clicked on the little red triangle in the map display and moved it a tiny smidge, and it appeared as a valid WP1. Saved into LNV and my Garmin folder no sweat. We flew it last night in my MJ C-47 and didn't fall out of the sky or crash the sim as we flew over WP1.

Hope that helps, man.

Seeya
 ATB


Title: Re: MSFS2024: LNMPLN conversion to PLN Hiccup
Post by: Mike-WT on Oct 05, 2026, 04:41 AM
You can get the latest Navaids updates for your FS9/FSX/P3D sim at Herve Sors site. (https://www.aero.sors.fr/index.html)
Title: Re: MSFS2024: LNMPLN conversion to PLN Hiccup
Post by: 1161 Roy Möhlmann on Oct 05, 2026, 05:26 AM
Alan and Mike, thanks for your advises. We will take that with us for next year.
Roy