Hello,

Firstly, thank you so much to the developer of Little Navmap! It is such a useful and feature rich tool.

I have built the following flight plan in LNM:

1. LIQZ - departure airport
2. PTC - VOR
3. Approach ILS-Y 24, transition (full) via BENTO
4. LIRN - arrival airport

I export to MSFS format and load into the sim... and get something different. The waypoint at the PTC VOR is not retained in the flight plan which just goes straight to BENTO. I thought that it might just be a glitch in the way MSFS shows and draws the plan, but when I am in the aircraft, there is no waypoint at the PTC VOR either. In the MSFS flight plan view I can also see that arrivals SOR1T 24 has been selected automatically.

I only have the MSFS scenery option enabled in LNM.

For other flight plans I see similar issues i.e. that the plan is altered when loaded into the sim. Am I doing something wrong or trying to force a flight plan that is ‘not allowed’?

Thanks in advance, Søren.

(PS. Posting screenshots exceeded my skills - sorry)

 

Hi Søren,

please make sure that you use the latest LNM which 2.6.13. This has a few bugfixes for MSFS PLN export.

Also consider this from the manual and make sure that you're not using the wrong navdata:

Quote

43.1. Microsoft Flight Simulator 2020 Airports and Navdata

• If you use the Navigraph update for MSFS: Update the Little Navmap database with the FMS Data Manager as well to keep the program in sync with the MSFS scenery library. Use the scenery mode Use Navigraph for Navaids and Procedures in the menu Scenery Library to get access to all procedures in Little Navmap.
• If you do not use the Navigraph update for MSFS: Use the scenery mode Do not use Navigraph Database in the menu Scenery Library to avoid issues with missing or changed navaids.

See appendix Microsoft Flight Simulator 2020 for information about MSFS limitations and issues.

Keep in mind that MSFS ignores transitions (actually you cannot store approach transitions in the PLN format) and inserts them automatically (or not).

MSFS is extremely picky and I suspect still buggy when loading flight plans.

Alex

 

Edit: Just checked the flight plan using plain MSFS data (no Navigraph) and the approach seems to be correct in the PLN. Seems like a MSFS issue.

...
<ATCWaypoint id="LIRN">
  <ATCWaypointType>Airport</ATCWaypointType>
  <WorldPosition>N40° 53' 4.00",E14° 17' 27.00",+000254.00</WorldPosition>
  <SuffixFP>Y</SuffixFP>
  <ApproachTypeFP>ILS</ApproachTypeFP>
  <RunwayNumberFP>24</RunwayNumberFP>
  <ICAO>
    <ICAOIdent>LIRN</ICAOIdent>
  </ICAO>
</ATCWaypoint>
...

 

 

 

 

Edited June 16, 20214 yr by albar965
Flight plan ok.

Vielen dank für dein antwort Alex! (that's as far as my German goes)

Can confirm that I am using the latest LNM 2.6.13 and that I have only enabled MSFS scenery, i.e. the option 'Do not use Navigraph Database' is selected.

Don't know if it is useful but I now managed to figure out how to attach files - screenshots below 🙂

Links to the flight plan files:

• LNM format: www.sorenstoy.dk/share/flightplan-lnm.pln
• After loading into MSFS and saving again: www.sorenstoy.dk/share/flightplan-msfs.pln

Something is definitely fishy - extremely picky is probably a good description.

Screenshot of the plan in LNM:

Screenshot of the plan after loading into MSFS - notice the weird first leg towards the VOR in the original file:

Scenery:

BR Søren

 

As Alex wrote the transitions are not exported to MSFS2020, but IMHO at menu LNM->File->Export Options you can still choose/set Export waypoints for Approaches.
Then you should get all procedure's points in flight plan (it should work even for Navigraph db).
In other case procedure's waypoints are not exported, and at such a case it's necessary choose proper procedure in FMC under simulator.

I prefer this last  method (but I use other simulator) as it's more flexible to make quick changes of flight plan in FMC during flight 🙂

Regards,
Piotr

 

 

Edited June 16, 20214 yr by ppgas

I see. The approach is detected correctly, the transition is ignored (it is not even saved in the PLN file) as expected but MSFS adds a STAR on its own.
I'd report this to Asobo.

Alex