Having created some flight plans in LittleNavMap, incorporating SID’s and STAR’s/Approaches, I have often been experiencing errors of “Not in Data Base” when entering the flight plan components into the FMS of the Just Flight BAE146 for MSFS 2020.

These error messages all seem to be waypoints on the LNM map, within the SIDS or STARS or Approaches.  Presumably these waypoints came directly from the MSFS database when building the scenery library?

Also presumably, the JF BAE146 must be loading its data from the same MSFS database? Or another database?

An example of this is waypoint I13RZ on the approach to 13L of LFML.

I am posting this at both the LittleNavMap forum and JF146 forum in the hope that someone can advise me how to rectify this situation.

Nigel

Vancouver

Not sure about the BAE. Most likely they use their own navdatabase since reading this BGL stuff is quite unpleasant. Check if the Navigraph FMS Data Manager has an update channel for this add-on if you have a subscription.

LNM 2.8.11 automatically selects the right database mode to use Navigraph or not.

But here are the recommended settings anyway:

Quote

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. This is the default.
  Also check the selection in menu Scenery Library -> Airspace Libraries. Select Navigraph and uncheck Simulator there.

• 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.
  The selection in menu Scenery Library -> Airspace Libraries should have Simulator checked. Uncheck Navigraph there.

See Navigation Databases and FSX, Prepar3D and MSFS Airspaces for more background information on these settings.
See appendix Known Problems and Frequently asked Questions for information about MSFS limitations and issues.
Use the menu item Scenery Library -> Validate Scenery Library Settings to check your settings.

This ensures that your LNM navdata and MSFS navdata are in sync which minimizes issues when loading flight plans.

Alex

19 hours ago, nigelgrant said:

An example of this is waypoint I13RZ on the approach to 13L of LFML.

I'm afraid you've got wrong charts of LFML. I13RZ is FACF point for RNAV-Z 13R approach, but not for RNAV-Z 13L.
For runway 13L and approach RNAV-Z 13L the proper FACF point is I13LZ.
Checked on newest LFML RNAV-Z 13L chart, here: https://www.sia.aviation-civile.gouv.fr/dvd/eAIP_15_JUN_2023/FRANCE/AIRAC-2023-06-15/html/eAIP/Cartes/LFML/AD_2_LFML_IAC_RWY13L_FNA_RNP_Z.pdf  (official SIA/AIP of France)
So, the LNM navigation data and generated flight plans are proper 🙂

Regards,
Piotr

Edited June 28, 20232 yr by ppgas