Hi,

Trying to get VNAV to tell me my TOD etc but it's all greyed out and I get a MSG saying 'Upcoming flight plan leg not supported'. I have an ALT restraint at my FAF which is 1800'. Even if I DTO the VNAV on this waypoint, nothing changes - still no VNAV data. 

The enroute waypoints have their ALT populated with my current altitude, cruise altitude (FL199 or so the Garmin believes, actually FL200). Then there is a waypoint in descent that it has calculated I will be at around FL150. So the descent profile IS there in the plan, it's just not giving me any TOD/VS info. 

Any guesses?

Thanks

EDIT: I wonder if it's anything to do with there being a disconnect between PEPIS and the FAF:

On the map view, PEPIS does not join the FAF, for some reason. 

EDIT 2: Just tried manually inputting CI20 and FI20 before the 'Approach' section. It let me enter FI20 first, then CI20 before it, with alt restraint 1800' at FI20. I then deleted the original CI20 but it would not allow deletion of FI20 post approach section. On adding alt restraint 1800' to the new FI20, the VNAV works. But now I have two FI20s, one '0nm' after the other, after the start of the 'approach' section. But presumably this isn't the official workaround? 

EDIT 3: Incidentally is there a way of having the VNAV required VS on the map view? Just spent most of my descent just now staring at the VNAV screen making sure the VS was correct, not much time to look at the map.

Edited March 15, 20206 yr by JKawai

Hi,

I'd suggest you review the Garmin GTN Pilot's Guide which documents all this (certainly much better than me anyhow!).

Also, please make sure your device AFMS settings are set appropriately. Anytime the manual refers to 'installation settings' it is most likely related to a setting in the AFMS section (like RF legs, or VCALC/VNAV)

12 hours ago, RXP said:

Hi,

I'd suggest you review the Garmin GTN Pilot's Guide which documents all this (certainly much better than me anyhow!).

Also, please make sure your device AFMS settings are set appropriately. Anytime the manual refers to 'installation settings' it is most likely related to a setting in the AFMS section (like RF legs, or VCALC/VNAV)

Thanks, although I can't find anything that specifically solves my issue. It says

"An altitude constraint is invalid if it is added to a waypoint past the FAF" (it isn't - it IS the FAF)

Transition to approach is enabled in AFMS, so that's not an issue. 4.3.3.6 says that when disabled "En route VNAV terminates at the waypoint prior to the FAF on approaches with vertical guidance". 

Can anybody else here shed light on what they do in this situation?