Fsx 767 Level-d Upload Rte Flight Plan Fmc

Little Navmap supports several flight plan formats, all of which have unlike limitations. All of the formats listed below can exist exported and some can be loaded.

36.1. Little Navmap LNMPLN Format¶

Lilliputian Navmap uses its ain XML based format since but this allows to save all features provided by the programme in a safety style as well as proper file validation. This also eliminates many of the confusing warning dialogs when saving other formats and potential data loss.

While yous can still load, for example, FMS and other formats direct into the plan, saving is limited to the LNMPLN format. Yous have to export the plan as FMS after irresolute it. You can do that either direct from the menu File -> Export Flight Programme equally 10-Plane FMS 11 or using menu File -> Multiexport Flying Plan Options and then File -> Multiexport Flying Plan.

Come across also Flight Plan Multiexport for more information on multiexport.

Note

The LNMPLN format is only understood by Picayune Navmap. Exercise not endeavour to load it into simulators or add-ons.

Consider exported flight plan files as disposable since almost all the export formats take limitations resulting in data loss. Remember that you can always restore them past loading the original LNMPLN file and exporting again.

See Trivial Navmap Flight Plan File Format for a detailed description of the format.

Warning

Always relieve a copy in the default LNMPLN format before exporting to other formats like FMS. This allows Little Navmap to restore all flying plan properties like procedures, alternating airports and remarks.

36.2. Flight Plan Consign Formats¶

The table below shows the capabilities of Piddling Navmap and the supported flight programme formats ( X = supported, 0 = not supported, - = not applicative) equally listed in Flying Programme Multiexport.

Format	Ext.	Open up	Exp	Airw	VFR/IFR	User Wpt. Names	Remarks	Dep. Parking	Cruise Alt.	Ground speed	Proc.
LNMPLN	LNMPLN	X	X	X	X	X	Ten	X	Ten	X	X
Microsoft Flight Simulator 2020	PLN	X	10	X	10	X	0	X	X	0	X 5
FSX and Prepar3D	PLN	X	10	Ten	X	X	0	X	10	0	0
FSX and Prepar3D annotated	PLN	X	10	X	X	10	0	X	X	X	X
FS9 PLN	PLN	10	0	10	Ten	10	0	X	X	0	0
X-Plane FMS 11	FMS	X	Ten	X	0	Ten	0	0	X	0	10
X-Plane FMS 3	FMS	X	X	0	0	X	0	0	X	0	0
FlightGear	FGFP	X	X	0	0	0	0	0	0	0	X ii
FSC	PLN	X	0	X	0	X	0	0	0	0	0
Aerosoft Airbus and others	FLP	X	Ten	Ten	0	0	0	0	0	0	X
Aerosoft CRJ	FLP	10	10	X	0	0	0	0	0	0	X
Garmin	FPL	X	X	0	0	0	0	0	0	0	0
Reality XP GNS 530W/430W V2	FPL	0	Ten	0	0	X	0	0	0	0	0
Reality XP GTN 750/650 Touch	GFP	0	X	10	0	X 1	0	0	0	0	X
Flight1 Garmin GTN 650/750	GFP	0	X	X	0	0	0	0	0	0	0
PMDG Aircraft	RTE	0	X	10	0	0	0	0	0	0	0
Rotate Doc-eighty, JARDesign and others	TXT	0	X	X	0	0	0	0	0	0	0
Majestic Dash MJC8 Q400	FPR	0	X	0	0	0	0	0	0	0	0
IXEG Boeing 737	FPL	0	X	X	0	0	0	0	0	0	0
Flight Factor Airbus	corte.in	0	X	X	0	0	0	0	Ten	0	10 2
iFly	FLTPLAN	0	10	X	0	0	0	0	0	0	0
ProSim	XML 4	0	X	X	0	0	0	0	0	0	0
BlackBox Simulations Airbus	PLN	0	10	Ten	0	0	0	0	0	0	0
Leonardo Maddog Ten	MDX	0	X	X	0	0	0	0	0	0	0
QualityWings	RTE	0	X	10	0	0	0	0	0	0	0
AivlaSoft EFB	EFBR	0	X	X	0	0	0	0	0	0	0
Level-D	RTE	0	10	X	0	0	0	0	0	0	0
FeelThere or Wilco	FPL	0	X	X	0	0	0	0	0	0	0
TFDi Design 717	XML	0	X	10	0	0	0	0	0	0	0
IvAp for IVAO three	FPL	0	X	X	0	0	0	0	0	0	0
X-IVAP for IVAO 3	FPL	0	Ten	Ten	0	0	0	0	0	0	0
VATSIM vPilot or SWIFT 3	VFP	0	X	10	0	0	0	0	0	0	0
UFMC	UFMC	0	X	10	0	0	0	0	0	0	0
X-FMC	FPL	0	X	X	0	0	0	0	0	0	0
Garmin exchange format	GPX	-	X	-	-	-	-	-	-	-	-
HTML flying program web page	HTML	-	Ten	-	-	-	-	-	-	-	-

For Flight1 Garmin GTN 650/750 , Reality XP GNS 530W/430W V2 and Reality XP GTN 750/650 Touch additional export formats be which replace waypoints with user defined waypoints. This helps to avoid the locked waypoint result.

Procedure waypoints are excluded from most file formats by default, except for GPX. You have to apply the GPS, FMS or MCDU in the simulator to select procedures. Exceptions are due east.g. X-Plane FMS and FLP which allow to save and load procedures.

You can enable saving of waypoints by checking the carte items Consign Waypoints for Approaches and/or Export Waypoints for SID and STAR.

The electric current file name and type will change if you lot salve a programme as LNMPLN. This does not occur when exporting.

36.3. User Waypoint Names¶

User waypoint names will be adapted to format limitations when exporting.

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

36.four. Formats¶

36.4.i. Microsoft Flight Simulator 2020¶

File format for MSFS. Little Navmap tin read and export this format.

You can consign this format directly using Export Flight Program as MSFS 2020 PLN.

While the format supports procedures there may appear issues in MSFS loading these. Procedures might be omitted or new ones inserted. Furthermore MSFS does not support the selection of transitions and often inserts these automatically.

You tin can ready a parking spot or fuel pad as starting position but notation that runways and helipads as starting positions will be ignored past MSFS.

36.4.two. FSX and Prepar3D¶

File format for FSX and P3D. Petty Navmap can read and consign this format. Procedures are not saved.

You can consign this format directly using Export Flying Programme as P3D or FSX PLN.

36.four.3. FSX and Prepar3D annotated (obsolete)¶

Annotated PLN format used past Petty Navmap versions up to and including 2.4.5.

This is needed simply if yous like to relieve a flight programme for older Niggling Navmap versions.

Piddling Navmap can read and export this format completely with procedures.

36.4.4. FS9 PLN¶

File format of the Flight Simulator 2004. Uses the same PLN file extension equally the FSX PLN format. Picayune Navmap can only read this format.

36.4.five. 10-Aeroplane FMS xi¶

X-Airplane FMS format which can be loaded into the stock GPS, the G1000 and the FMS of X-Plane xi.10 or subsequently.

You tin export this format directly using Export Flight Programme as 10-Plane FMS 11.

Little Navmap tin can read and export this format.

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

Read the X-Plane manuals for the respective devices on how to load plans inside the cockpit: User Manuals for X-Aeroplane Products.

Note

Little Navmap cannot determine the cruise altitude of a flying plan subsequently loading this format in some cases. You lot might run across errors well-nigh violated distance restrictions after loading. Adjust the cruise distance manually if this is the example.

36.4.6. FMS three (10-Plane)¶

X-Airplane FMS format which tin be loaded into the stock GPS and FMS of X-Plane 10 and xi.05. The format is very express and basically stores but a list of waypoints.

Piddling Navmap tin read and export this format.

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

36.4.7. FlightGear¶

FlightPlan format which can be loaded into the RouteManager of the free flight simulator FlightGear.

You tin export this format directly using Export Flying Plan as FlightGear FGFP.

Footling Navmap can read and export this format.

Y'all tin can save the files into whatever directory and load it within FlightGear.

36.4.eight. FSC¶

File format for FlightSim Commander. Uses the same PLN file extension as the FSX PLN format. Niggling Navmap can but read this format.

36.4.9. Aerosoft Airbus and others¶

36.4.10. Aerosoft CRJ¶

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

Yous can load these files into the X-Aeroplane FMS including airway information. Procedures are saved in the FLP merely cannot loaded notwithstanding by the FMS. You take to select these manually after loading the flight program.

36.four.xi. Garmin¶

Elementary XML based flight program format which stores only a list of waypoints. Little Navmap can read and consign this format.

36.4.12. Reality XP GNS 530W/430W V2¶

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

See Notes about the Garmin Formats GFP and FPL for information on known issues when exporting flight plan data for the GNS.

Little Navmap considers the GNSAPPDATA environs variable if gear up. Come across the GNS manual for more data.

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

36.4.13. Reality XP GTN 750/650 Touch¶

Relieve flying plan as GFP file usable by the Reality XP GTN 750/650 Impact.

Run into Notes about the Garmin Formats GFP and FPL for information on known problems when exporting flight programme information for the GTN.

Footling Navmap considers the GTNSIMDATA environment variable if fix. Run into the GTN manual for more than data.

36.4.xiv. Flight1 Garmin GTN 650/750¶

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

36.iv.14.1. 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. You have to create this directory manually and and then navigate to it in the file dialog when saving. Petty Navmap will call up the selected directory.

36.4.fourteen.ii. Garmin GTN Trainer 6.21¶

If you're using the trainer version vi.21 then the default path is C:\ProgramData\Garmin\GTN Trainer Data\GTN\FPLN . Y'all have to create this directory manually.

36.four.15. Flight1 Garmin GTN 650/750¶

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

See Notes nearly the Garmin Formats GFP and FPL for information on problems when exporting flight program data for the GTN.

The default directories to salvage the flying plans for the GTN units are:

Prepar3D v3: C:\Programme Files (x86)\Lockheed Martin\Prepar3D v3\F1TGTN\FPL .
Prepar3D v4: C:\Program Files\Lockheed Martin\Prepar3D v4\F1TGTN\FPL .
Flying 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 exercise not testify upward in the GTN. Requite yourself full control and/or ownership of this directory to avert this.

A typical symptom is that you can salvage the flying plan in Little Navmap and you lot can likewise see the saved plan in Little Navmap'south open dialogs but information technology does non show upwards in the GTN unit. Change the privileges of the export directory as mentioned above if that is the instance.

The file is a simple text format containing merely one line of text.

Example for the content of a flight programme file named KEAT-CYPU.gfp ¶

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

36.4.16. PMDG Shipping¶

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

This format does not let saving of procedures.

36.4.17. Rotate Physician-fourscore, JARDesign and others¶

A unproblematic file format usable by JARDesign or Rotate Simulations aircraft. The dexport directory depends on the used aircraft which is commonly in the 10-Plane directory Aircraft .

The file is a simple text format containing only ane line of text.

Example for the content of a TXT file named CBZ9CYDC.txt ¶

                CBZ9 SID AIRIE V324 YKA B8 DURAK STAR CYDC

36.4.18. Majestic Dash MJC8 Q400¶

Flight program format for the Majestic Software MJC8 Q400. Note that the export is 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 lot press INFO on a waypoint or airport. The flight plan, navigation and autopilot are not affected otherwise.

36.4.xix. IXEG Boeing 737¶

Exports the electric current flying plan equally a FPL file usable past the IXEG Boeing 737. The format is the same every bit TXT but with a different file extension.

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

36.4.twenty. Flight Cistron Airbus¶

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

Flying plans are saved in a slightly extended ATS road notation which as well allows to salve the prowl altitude and approach procedures. Edit the file with a simple text editor if you desire to remove flight plans.

While this format allows saving of SID and STAR the selection for approaches was removed since information technology is unreliable.

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

36.4.21. iFly¶

Flying programme format for the iFly 737NG for FSX or P3D. The file has to exist saved to YOURSIMULATOR/iFly/737NG/navdata/FLTPLAN .

Procedures cannot be saved.

36.4.22. ProSim¶

A flight plan format for ProSim. The flight plan is appended to the file companyroutes.xml when saving. Remove flight plans manually in a text editor.

Piddling Navmap creates upward to two backup files when saving the flying program: companyroutes.xml_lnm_backup and companyroutes.xml_lnm_backup.1 .

Procedures cannot exist saved.

Case¶

                                <?xml version="one.0" encoding="UTF-viii"?>                <companyroutes>                <route                name=                "EFMAESGT"                >EFMA RUNGA N872 TEB N623 BEDLA N866 NEGIL ESGT</road>                <route                name=                "LGIRLEDA"                >LGIR SUD UJ65 TRL UM601 RUTOM M601 QUENN Q123 LULIX P167 GINOX UM601 BCN UN975 SELVA LEDA</route>                </companyroutes>

36.four.23. BlackBox Simulations Airbus¶

This format is for the Blackbox Simulations Airbus for FSX or P3D. Save this to YOURSIMULATOR/Blackbox Simulation/Company Routes or YOURSIMULATOR/BlackBox Simulation/Airbus A330 depending on shipping blazon.

This format cannot salve procedures.

36.4.24. Leonardo Maddog X¶

Flying plan for the Leonardo MaddogX shipping. This format cannot save procedures.

36.4.25. QualityWings¶

Flight program for QualityWings shipping. This format cannot relieve procedures. The location depends on the aircraft.

36.4.27. Level-D¶

Flight plan for Level-D aircraft. This format cannot save procedures. Save this to YOURSIMULATOR\Level-D Simulations\navdata\Flightplans .

36.four.28. FeelThere or Wilco¶

The format above cannot save procedures. The location depends on the shipping.

36.four.29. TFDi Pattern 717¶

Flight programme format for the TDFi Design Boeing 717. The format above cannot save procedures.

36.4.30. IvAp for IVAO¶

36.four.31. X-IVAP for IVAO¶

Flight plan format for the IVAO online network clients IvAp or X-IvAp.

The file format for these two clients differs slightly.

Flying Plan Online Network Consign will appear before where yous tin can add all needed information.

36.four.33. UFMC¶

A flight programme format for the UFMC. The format does not allow saving of procedures.

Save the flying plan to XPLANE\Custom Information\UFMC\FlightPlans .

36.4.34. X-FMC¶

Save flight plan as FPL file for the X-FMC. The format does not allow saving of procedures.

The file should exist saved to Path to XPLANE\Resources\plugins\XFMC\FlightPlans .

36.four.35. Garmin exchange format¶

GPX is non a flight programme format.

The GPS Substitution Format can be read by Google Globe and most other GIS applications.

The flying plan is embedded as a road and the flown aircraft trail as a rail including simulator fourth dimension and altitude.

The route has difference and destination meridian and cruise altitude fix 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 process similar holds or procedure turns.

The track contains the shipping trail with flown distance and timestamps.

36.4.36. HTML flight programme web folio¶

This is non a flying plan format. This part saves the current flight plan equally a single HTML spider web folio with all images embedded. Yous can open this page in any spider web browser.

The exported file volition reflect changes of the flying plan table view similar column guild. Columns which are subconscious or shrinked to minimum width are excluded.

36.5. Notes nigh the Garmin Formats GFP and FPL¶

Diverse problems tin announced 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 wheel (mostly 1611 at the time of writing). Updated simulator or add-on databases (like the 1 in Petty Navmap) tin use the latest navdata or an old one from FSX or P3D stock data.

Any waypoints, airways or procedures that are removed, added or renamed over time can crusade 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 program to exist activated. Refer to the documentation of the Garmin unit of measurement.

Fiddling Navmap allows to modify the Garmin consign to supplant all waypoints with user-defined waypoints to avoid locking. While this is a sufficient approach to avoid the locked waypoints information technology comes with a few limitations:

Departure and destination drome are non 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 tin be enabled in the options dialog on tab Flight Plan .

one: Only SID and STAR. Saving or approaches is non supported.
2 (one,two): User-defined waypoints volition be renamed when loading into the GTN.
3 (1,2,3): Boosted information for online flying can be added in a dialog before saving.
four: Full name is companyroutes.xml
5: Procedures might not load in MSFS or might be replaced by other procedures.

templetonealiche.blogspot.com

Source: https://www.littlenavmap.org/manuals/littlenavmap/release/2.2/en/FLIGHTPLANFMT.html