Flight Plan Formats

Little Navmap supports several flight plan formats which have all different limitations. Only some of these formats can be loaded and saved.

The program uses different Save as ... file dialogs instead of just one. This allows to remember the directory for each file format separately.

So, there is no need to jump between the FSX flight plan directory, the P3D flight plan directory and the X-Plane FMS output directory.

Note the difference between Save Flight Plan as ... and Export Flight Plan as ...: Export does not change the current file name while Save as ... does.

Feature Table

The table below shows the capabilities of Little Navmap and the supported flight plan formats (X = supported, 0 = not supported):

Format Read Write Airways VFR/ IFR User Wpt. Names Dep. Parking Cruise Alt. Ground speed Proc.
FSX PLN annot. X X X X X X X X X
FSX PLN X X X X X X X 0 0
FS9 PLN clean X 0 X X X X X 0 0
X-Plane FMS 11 X X X 0 X 0 X 0 X
X-Plane FMS 3 X X 0 0 X 0 X 0 0
FLP X X X 0 0 0 0 0 X
Reality XP GNS FPL 0 X 0 0 X 0 0 0 0
Reality XP GTN GFP 0 X X 0 X2 0 0 0 X
Flight1 GTN 0 X X 0 0 0 0 0 0
PMDG RTE 0 X X 0 0 0 0 0 0
TXT 0 X X 0 0 0 0 0 0
Majestic Dash FPR 1 0 X 0 0 0 0 0 0 0
IXEG 737 FPL 0 X X 0 0 0 0 0 0
Flight Factor corte.in 0 X X 0 0 0 X 0 X
GPX 0 X 0 0 0 0 0 0 0

Procedure waypoints are excluded from all file formats except GPX. You have to use the GPS or FMS in the simulator to select procedures.

A dialog is shown if any unsupported features are detected in the current flight plan when trying to save a plan. You can disable this dialog for future saves if you know what you are doing.

You current file name and type will change if you save a plan to a format that is read and writable. This does not happen when exporting.

An example shows how the program deals with the limited formats:

  1. Create a flight plan including procedures.
  2. Save as PLN - current filename changes to new file name NAME.pln.
  3. Save as FMS - a warning is shown and after saving the current filename changes to new NAME.fms.
  4. Restart program - NAME.fms will be reloaded and procedures are lost.
  5. Now export as GFP - Current filename remains NAME.fms.

User Waypoint Names

User waypoint names will be adapted to format limitations when saving. That means that waypoint names can change when reloading a flight plan.

  • PLN: Maximum length for FSX or Prepar3D is 10 charaters and no special characters are allowed. Unsupported characters will be removed and the length will be truncated.
  • FMS: No spaces allowed. These will be replaced with underscores (_).
  • FLP: All user waypoint names will be replaced by coordinates.

FSX PLN FSX PLN

The format FSX PLN is used as a default format because it supports most features and allows to include additional information in form of annotations which will be ignored by flight simulators and most other tools.

FS9 PLN FS9 PLN

File format of the Flight Simulator 2004. Uses the same PLN extension as the FSX PLN format. Little Navmap can only read this format. Therefore a warning dialog is shown before overwriting a file with the newer FSX PLN format.

Clean PLN Clean PLN

This is the same as the FSX PLN but without additional annotations which contain information about selected procedures or ground speed. Use this format if a tool cannot deal with the annotated format.

FMS 11 FMS 11 (X-Plane)

New X-Plane FMS format which can be loaded into the stock GPS, the G1000 and the FMS of X-Plane 11.10. This is the default save format for X-Plane FMS now. Use the export function to save old FMS version 3 files.

This format is supported as of X-Plane 11.10. It can already be used in the beta versions but might crash X-Plane version 11.05 and below.

Little Navmap can read and write this format.

Store these files into the Output/FMS plans directory inside the X-Plane directory.

FMS 3 FMS 3 (X-Plane)

X-Plane FMS format which can be loaded into the stock GPS and FMS of X-Plane 10 and 11.05. The format is very limited and basically stores only a list of waypoints.

Little Navmap can read and write this format.

Store these files into the Output/FMS plans directory inside the X-Plane directory.

FLP

A format that can be read by the X-Plane FMS (not the X-Plane GPS), Aerosoft Airbus and other add-on aircraft. Supports airways and procedures.

You can load these files into the X-Plane FMS including airway information. Procedures are saved in the FLP but cannot loaded yet by the FMS. You have to select these manually after loading the flight plan.

Store these files into the Output/FMS plans directory inside the X-Plane directory if you want to use them in X-Plane.

FPL (Reality XP Garmin GNS)

Flight plan format as FPL file usable by the Reality XP GNS 530W/430W V2.

This file format can only be exported. Reading is not supported.

See below for information on known problems when exporting flight plan data for the GNS.

Little Navmap considers the GNSAPPDATA environment variable if set. See the GNS manual for more information.

The default directory to save the flight plans for the GNS units is C:\ProgramData\Garmin\GNS Trainer Data\GNS\FPL for all simulators. The directory will be created automatically by Little Navmap on first export if it does not exist.

GFP (Reality XP Garmin GTN)

Save flight plan as GFP file usable by the Reality XP GTN 750/650 Touch.

This file format can only be exported. Reading is not supported.

See below for information on known problems when exporting flight plan data for the GTN.

Little Navmap considers the GTNSIMDATA environment variable if set. See the GTN manual for more information.

Garmin GTN Trainer 6.41

The default directory to save the flight plans for the GTN units is C:\ProgramData\Garmin\Trainers\GTN\FPLN for all simulators. The directory will be created automatically by Little Navmap on first export if it does not exist.

Garmin GTN Trainer 6.21

If you're using the trainer version 6.21 then the default path is C:\ProgramData\Garmin\GTN Trainer Data\GTN\FPLN. You have to create this directory manually and then navigate to it in the file dialog when saving. Little Navmap will remember the selected directory.

GFP (Flight1 Garmin GTN)

This is the flight plan format used by the Flight1 GTN 650/750.

This file format can only be exported. Reading is not supported.

See below for information on problems when exporting flight plan data for the GTN.

The default directories to save the flight plans for the GTN units are:

  • Prepar3D v3: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\F1TGTN\FPL.
  • Prepar3D v3: C:\Program Files\Lockheed Martin\Prepar3D v4\F1TGTN\FPL.
  • Flight Simulator X: C:\ProgramFiles(x86)\Microsoft Games\Flight Simulator X\F1GTN\FPL

You might need to change the user privileges on this directory if your saved flight plans do not show up in the GTN. Give yourself full control and/or ownership of this directory to avoid this.

A typical symptom is that you can save the flight plan in Little Navmap and you can also see the saved plan in Little Navmap's open dialogs but it does not show up in the GTN unit. Change the privileges of the export directory as mentioned above if that is the case.

The file is a simple text format containing only one line of text. Example for the content of a flight plan file named KEAT-CYPU.gfp:

FPN/RI:F:KEAT:F:EAT.V120.SEA.V495.CONDI.V338.YVR.V330.TRENA:F:N50805W124202:F:N51085W124178:F:CAG3:F:N51846W124150:F:CYPU

RTE (PMDG)

A PMDG RTE file. File location depends on the used aircraft but is usually PMDG\FLIGHTPLANS in the simulator base directory.

TXT (JARDesign and Rotate Simulations)

A simple file format usable by JARDesign or Rotate Simulations aircraft. Location depends on the used aircraft which is usually in the X-Plane directory aircraft.

The file is a simple text format containing only one line of text. Example for the content of a TXT file named CBZ9CYDC.txt:

CBZ9 SID AIRIE V324 YKA B8 DURAK STAR CYDC

FPR (Majestic Dash)

Flight plan format for the Majestic Software MJC8 Q400. Note that the export is currently limited to a list of waypoints.

The flight plan has to be saved to YOURSIMULATOR\SimObjects\Airplanes\mjc8q400\nav\routes.

Note that the FMC in the Dash will show invalid coordinates when you press INFO on a waypoint or airport. The flight plan, navigation and autopilot are not affected otherwise.

FPL (IXEG Boeing)

Exports the current flight plan as a FPL file usable by the IXEG Boeing 737. The format is the same as TXT but with a different file extension.

The file should be saved to XPLANE\Aircraft\X-Aviation\IXEG 737 Classic\coroutes. You have to create the directory manually if it does not exist.

corte.in (Flight Factor Airbus)

A format for the Flight Factor Airbus. The file is not truncated and flight plans are appended when saving.

Flight plans are saved in a slightly extended ATS route notation which also allows to save the cruise altitude and approach procedures. Edit the file with a simple text editor if you want to remove flight plans.

Example:

RTE ETOPS002 EINN 06 UNBE2A UNBEG DCT 5420N DCT NICSO N236A ALLEX Q822 ENE DCT CORVT KJFK I22R JFKBOS01 CI30 FL360
RTE EDDFEGLL EDDF 25C BIBT4G BIBTI UZ29 NIK UL610 LAM EGLL I27R LAM CI25 FL330

GPX

GPX not a flight plan format.

The GPS Exchange Format can be read by Google Earth and most other GIS applications.

The flight plan is embedded as a route and the flown aircraft trail as a track including simulator time and altitude.

The route has departure and destination elevation and cruise altitude set for all waypoints. Waypoints of all procedures are included in the exported file. Note that the waypoints will not allow to reproduce all parts of a procedure like holds or procedure turns.

Notes about the Garmin Formats GFP and FPL

Various problems can appear when reading exported flight plans into the Garmin units. Most of these are a result of the Garmin navigation database which uses data of an older AIRAC cycle (mostly 1611 at the time of writing). Updated simulator or add-on databases (like the one in Little Navmap) can use the latest navdata or an old one from FSX or P3D stock data. X-Plane 11.10 stock navdata is currently based on 1611.

Any waypoints, airways or procedures that are removed, added or renamed over time can cause locked waypoints or other messages when reading a flight plan into the GNS or GTN.

It is easy to remove locked waypoints within the GNS or GTN to enable the flight plan to be activated. Refer to the documentation of the Garmin unit.

Little Navmap allows to change the Garmin export to replace all waypoints with user defined waypoints to avoid locking. While this is a sufficient approach to avoid the locked waypoints it comes with a few limitations:

  • Departure and destination airport are not saved as user defined waypoints. These have to exist in the Garmin navigation database.
  • Navaid information like frequencies cannot be displayed since the waypoint cannot be related to the radio navaid.
  • Procedures like SID and STAR cannot be saved with the flight plan and have to be selected manually.
  • The GTN (not the GNS) changes all names to a generic USERWPT... scheme.

The export of user defined waypoints can be enabled in the options dialog on tab Flight Plan.

1. The FPR format does allow saving of airways and procedures but this will be implemented in a future release of Little Navmap.
2. User defined waypoints will be renamed when loading into the GTN.

results matching ""

    No results matching ""