January 6, 20224 yr Hello, question regarding the WT G1000NXi VNAV profile. Hope someone can help out. Take a look at this screenshot of a route I have plugged in with an RNAV approach. For some reason the g1000 has some waypoint “ETNOR” as it’s vnav waypoint however the first RNAV approach point is NEPAM. 2 questions: why does it say ETNOR. where did that come from? how can I change the vnav waypoint to something else like the first waypoint in the RNAV approach? Thanks! 1-vnav966×734 84.8 KB
January 6, 20224 yr As shown below, ETNOR is a waypoint between OBA and ARPIX. I don't see ETNOR listed as a waypoint in your FP. It looks like you would go from OBA to ARPIX. I would think you could enable VNV after ARPIX and it would get you down to 3000 at BABLU. I would activate the approach a few miles before reaching NEPAM. Al Edited January 6, 20224 yr by ark
January 6, 20224 yr Author 21 minutes ago, ark said: As shown below, ETNOR is a waypoint between OBA and ARPIX. I don't see ETNOR listed as a waypoint in your FP. It looks like you would go from OBA to ARPIX. I would think you could enable VNV after ARPIX and it would get you down to 3000 at BABLU. I would activate the approach a few miles before reaching NEPAM. Al It's strange as ETNOR is nowhere on my flight plan. It's part of a different arrival or something but has nothing to do with it currently. Feel like this may be a bug. However the bigger issue is I want NEPAM to be the vnav reference altitude so I can get the VNAV autopilot to work. Do you know how to force the G1000 to have a particular VNAV waypoint reference? Edited January 6, 20224 yr by dresoccer4
January 6, 20224 yr Author 27 minutes ago, ark said: As shown below, ETNOR is a waypoint between OBA and ARPIX. I don't see ETNOR listed as a waypoint in your FP. It looks like you would go from OBA to ARPIX. I would think you could enable VNV after ARPIX and it would get you down to 3000 at BABLU. I would activate the approach a few miles before reaching NEPAM. Al update: discovered something strange. so the VNAV waypoint still won’t change to NEPAM while enroute. However manually modifying NEPAM’s altitude restriction also changes ETNOR’s altitude! It’s like the G1000 is actually using NEPAM but showing ETNOR for some reason.
January 6, 20224 yr Does seem to be a bug of some type. ETNOR is a waypoint on a STAR for Rwy 17, but that STAR is for a flight going up to ENBR from the South, not coming in from the West. Should be interesting to see what happens when you fly this flight plan. Al
Archived
This topic is now archived and is closed to further replies.