Importing RXP’s example gfp, KSLE_KSLE.gfp, to a GTN750, I found that, after activation, the first active leg is strangely located. Expectedly, I thought it would be the first leg between departure airport and the first (of two) subsequent user waypoints. However, what really becomes activated while TERM is annunciated, is the leg to the approach transition JAIME for ILS-runway 31 at the (same) arrival airport KSLE. For clearance, here’s the flight plan:

FPN/RI:F:KSLE:F:N45223W121419:F:N42568W122067:AA:KSLE:AP:I31.JAIME

So overall, it seems that the two user waypoints are simply ignored! Actually, flying that plan, behaves as described, i.e. the user waypoints are skipped. Only if I activate the “expected” first leg manually, the flight’s initial direction goes to USR000 (even after some weird turns, because USR000 is extremely off the runway, oriented to the far left), and some (long) time later TERM switches to ENR.

Accept excuses for a maybe simple error of myself or a false setting, but I’m a beginner. Have my thanks for your help.

Are you activating the approach, or the flightplan?

I'm certain this is documented and expected.

For example is this related (quick google search):

https://bruceair.wordpress.com/2016/02/11/changes-to-flight-plans-with-procedures-in-gtn-system-software-6-x/

Bert, exactly, that's it: I activated the flight plan (directly after import) and not the approach.

Jean-Luc, thanks for the link, but I couldn't find any substantial hint to solve/explain my problem.

IIRC you were surprised how the GNS V2 and the GTN are importing the same flight plan differently.

I was thinking the changes since v6.0 might have been relevant, because the GNS V2 and the GTN do not handle flight planning the same way.

For example:

The GTN 6.62 Pilot's guide says (p 6-13):

v5.13 and Earlier or v6.50 and Later
If you build your flight plan with the destination airport at the end and then load an approach procedure, you will navigate all the way to the destination airport before joining the procedure. Be sure when LOADING and not ACTIVATING an approach procedure that the route to be flown is correct.

v6.00 Through v6.41
If you build your flight plan with the destination airport at the end and then load an approach procedure, the destination airport will be removed from the end of the flight plan. If the leg to the destination airport is the active leg when loading an approach procedure, you will navigate all the way to the destination airport before joining the procedure. Be sure when LOADING and not ACTIVATING an approach procedure that the route to be flown is correct.

Worth mentioning (p6-7):

In software v5.13 and earlier
once VTF is activated all waypoints in the approach prior to the FAF are removed.

In software v6.00 and later
all waypoints along the final approach course, including waypoints before the FAF, are included in the flight plan and the final approach course to the FAF is activated.

 

Yes, that was me. I just opened this other thread here, because I thought import- and leg-troubles are two different pairs of shoes ...

@first remark: that one is related, but I never loaded approaches after importing, just imported flight plans with and without approaches.

@second remark (second paragraph): sounds good, but I'm not really expert enough to follow these words to the last detail. "Activation of the final approach to the FAF". I thought, at a FAF a final approach starts, which would correspond to another wording. e.g. activate the final approach to the runway  ... And finally, FAF and approach transition (JAIME above), are these synonyms?