I'm getting Flight plan import--> Flight plan import failed. This is for flight plans exported out of pilot2atc.

Dave from pilot2atc said that is was because of garmin trainer being out of date. Well..... I updated to cycle 1803 and it didn't help. Still getting import failed.

Any ideas?

Can you post the contents of a couple of .gfp files you are attempting to import?  Just open the .gfp file with notepad or wordpad or another text editor, then copy and paste the contents here.  If they are valid .gfp files the contents will be text.  I am not aware of any difference in .gfp file format from one trainer version to another.

Here is what a .gfp plan looks like:
FPN/RI:F:KIND:D:ROCKY.STL:J8.SGF.J105:AA:KAFW:A:SASIE4.MLC:AP:R16R.FUNGO

That plan is for a flight from Indianapolis, Indiana, to Austin, Texas (Executive)

Cycle 1803 is a nav database reference.  That is separate and distinct from a trainer version.

Edited August 5, 20187 yr by fppilot

P3dv4.3 has a known bug, such that every time a flightplan from any source is loaded, v4.3 recalculates it without waypoints.  Loading the plan a second time corrects the glitch. Don't know, but this perhaps has something to do with your problem.

Here is one.....

FPN/RI:DA:KJNX,:AA:KHSE

This is KJNX to KHSE with approach 07 with vectors

This is exported out of Pilot2ATC

Also.... shouldn't the approach be included the .gfp file?

I can export flight plan as fms, import into little nav, then export to .gpl and it works but some waypoints are converted to user waypoints

Thanks

Edited August 5, 20187 yr by strat919

10 minutes ago, strat919 said:

FPN/RI:DA:KJNX,:AA:KHSE

Cannot say if it is the only issue you are encountering but the plan you provided above has too many punctuation marks.  Get rid of the comma after KJNX and resave the file, taking care to retain the .gfp extension.  Should look like this:

 FPN/RI:DA:KJNX:AA:KHSE

Then try importing it again.

 

15 hours ago, fppilot said:

Cannot say if it is the only issue you are encountering but the plan you provided above has too many punctuation marks.  Get rid of the comma after KJNX and resave the file, taking care to retain the .gfp extension.  Should look like this:

 FPN/RI:DA:KJNX:AA:KHSE

Then try importing it again.

 

Need to make a correction here.  I am providing  a link to below to the Garmin document that contains file specifications for its ..gfp file format.

The DA code for the departure airport is only used when you are departing the airport on a published departure.  Likewise, the AA code for an arrival airport is only used when using a published arrival for that airport.  Your flight plan does not use a departure or arrival.  Neither of your two airports have any published departures.  KJNX has one published arrival, South Boston Five, but you are departing KJNX not arriving.  If not putting a published departure or arrival into your flight plan the code used to separate the elements of the flight plan is instead  ":F:" 

The plan then should then look like this:
FPN/RI:F:KJNX:F:KHSE

If Pilot2ATC is putting the :DA: and :AA" separators into your short flight plan without a departure and/or arrival then it is creating the issue.  It should be using :F: instead!

Here is an example of your flight plan with an interim fix placed between the two airports.
FPN/RI:F:KJNX:F:HOPIM:F:KHSE

Try saving these two as .gfp files and they should import successfully.

The flight plan I illustrated in an earlier post in this topic is much more sophisticated.  That flight plan, from Indianapolis to Ft. Worth (Alliance), uses a published departure, a published arrival, a published approach with fix, and also uses airways:
FPN/RI:DA:KIND:F:TILMN.J24.STL.J8.SGF.J105:AA:KAFW:A:SASIE4.MLC:AP:R16R.FUNGO

Here is the link to the Garmin document of specifications for the .gfp files.  You may wish to pass this on to the developers at Pilot2ATC.
https://forums.jetcareers.com/attachments/gtn-flight-plan-and-user-waypoint-transfer-pdf.34218/

Edited August 5, 20187 yr by fppilot