Thanks so much. We can help you with testing.

Hello Tim,

firstly, thank you for building such an awesome tool!

Recently, Flight1 have added support for importing flight plans into their supercool GTN units. See below and attached. It would really cool if you could add export support for these Garmin-GFP-Files!

Thanks for considering!

Best regards

Christopher from Hamburg

Statement from the website (http://www.flight1.com/products.asp?product=f1gtn):
"Latest Features with v1.18!

Custom Flight Plan / Waypoint Loading - Users now have the ability to load a custom flight plan and the ablity to import custom waypoints using a very simple procedure (see included document for more info)"

Statement from the tutorial:
"3. Flight Plan File Guidelines
Garmin uses a text based flight plan format that is derived from the IMI/IEI
messages format specified in ARINC 702A-3. But that's just a side note.
Let's take a look at the syntax of a usual Garmin flight plan:
FPN/RI:F:AIRPORT:F:WAYPOINT:F:WAYPOINT.AIRWAY.WAYPOINT:F:AIRPORT
Every flight plan always starts with the "FPN/RI" identifier. The ":F:" spec-
ifies the different flight plan segments. A flight plan segment can be the
departure or arrival airport, a waypoint or a number of waypoints that are
connected via airways. The entry and exit waypoint of an airway are con-
nected to the airway via a dot ".".
The flight plan must be contained in the first line of the file. Anything after
the first line will be discarded and may result in importing failures. Flight
plans can only contain upper case letters, numbers, colons, parenthesis,
commas and periods. Spaces or any other special characters are not al-
lowed. When saved the flight plan name must have a ".gfp" extension."