Hey folks,

there are a lot of posts here regarding pain with flight plan imports into MSFS 2020 but my question is about the opposite way.

I'm planning my flight in MSFS 2020 and writing it into an .pln file. Loading that .pln file into LNM results in a different flight plan there. Different altitudes, different procedures, etc. Is that an expected behaviour of LNM too because of the poor MSFS implementation of writing flight plans into a file? Or is there a trick (setting) to keep that way of export/import right?

P.S.: I updated the Navigraph Database in LNM to 2203.

Thanks and greetings from Germany 🙂

I am able to merely open my MSFS saved .pln files with Navigraph's File, Open Flight Plan.

4 hours ago, h4rp00n33r said:

I'm planning my flight in MSFS 2020 and writing it into an .pln file. Loading that .pln file into LNM results in a different flight plan there. Different altitudes, different procedures, etc. Is that an expected behaviour of LNM too because of the poor MSFS implementation of writing flight plans into a file? Or is there a trick (setting) to keep that way of export/import right?

MSFS automatically selects approach transitions but does not save them. This might explain some differences for procedures. Same for SID and STAR.

Can you post an example where procedures differ?

Altitude is ignored in LNM when loading and LNM calculates this based on the loaded aircraft performance.

LNM tries to be very error tolerant (I've seen files from add-ons, oh my ...) when loading plans and it was a lot of "fun" to make it so.

All the best from somewhere North-West of EDDF 🙂

Alex

Thx @fppilot and @albar965 for your replies. Opening an MSFS-.pln file works but the flight plans look different - especially the waypoints.

I examined the .pln file and found an interesting detail/example.

I planned an IFR flight from Hanover (EDDV) to Dusseldorf (EDDL) via VAXE1S and HALM1X:

In MSFS the interesting approach waypoints look like this:

Opening the .pln file with Notepad++ shows:

So MSFS does not write it's own flight plan correctly into a .pln file: Instead of writing the waypoints

GAPNU
DISIP
DL525
DL555
NATOS
EDDL

it's writing

GAPNU
RONAD
EDDL

So it's no wonder the flight plan looks different in LNM. 🤪

Thanks anyway and greetings from somewhere south of EDDV
Marc

MSFS saves SID and STAR waypoints into the flight plan (needless redundancy usually causing trouble IMO) but *not* approach waypoints. This explains the missing waypoints.

Alex