Not sure if it is the aircraft, the sim, me, or some combination.

I have Navigraph data installed.  When I get to the final approach fix, the G3000 does not recognize it.  For example, at KNQX, once I get to WEBUN, the GPS still shows that I am on the DEMTE to WEBUN segment, and never changes even after touchdown.  The GS indicator shows that I am above the glideslope even after touching down on the runway.

I am having this behavior consistently with all RNAV approaches.  Anyone else having similar issues?

There have been hundreds of postings about the RNAV issue.  I have written at least a dozen.  I have spent many frustrating hours trying to make RNAV work in the Textron 172, G36, in the DA62, and the TBM.  They all have the same problem - RNAV is totally unreliable and the performance is unpredictable.

Yesterday I was flying the RNAV (GPS) Rwy 7 approach at KSBA in the Bonanza.  My flight plan showed the correct waypoints and was activated as I approached the final fix (WURLL) prior to the IAF at AFOXY.  The autopilot tracked correctly and the flight plan window showed the correct leg and follow on fixes to the final fix at NAPPS.  As the plane approached ECEVA (IF) it did a 180° turn BACK toward AFOXY (the IAF it had just come from).  

I let the flight continue under AP control and it just kept flying back and forth between AFOXY and ECEVA and never made the turn to the final fix at NAPPS, despite the ECEVA -> NAPPS leg being the next leg in the displayed flight plan after the AFOXY -> ECEVA leg.

This is just one of many strange performance issues I, and many others, have encountered with the G1000 RNAV system.

 

Edited September 28, 20205 yr by TacomaSailor
spelling / grammar

.. and, as you have found, the GS indicator is always low, unless you manually descend to the Intercept Altitude first.  ☹️

Hey Bert.  Thanks both for the info. 

I actually had the opposite problem.  I was at the intercept height (1600 ft) flying along and the diamond never came down.  It staid pegged to the top and I just had to abandon it and fly a visual approach.

I've learned to just stick with the old school ILS approaches for now.  With all the random and intermittent bugs, it is just to frustrating to try and learn.  

I deleted my Navigraph data and was able to fly a reasonable approach into CYYJ this AM.  The GP marker was a bit funky but it did capture the GP at the FAF in a pretty nasty storm.

Unfortunately, one of the reasons I installed Navigraph to begin with was the incomplete NAVBLUE data set.  Most of the smaller airports I fly into in FSE have a few RNAV approaches that are not there by default in the sim.

3 hours ago, ckelly14 said:

Unfortunately, one of the reasons I installed Navigraph to begin with was the incomplete NAVBLUE data set.  Most of the smaller airports I fly into in FSE have a few RNAV approaches that are not there by default in the sim.

Be mindful, navagrph cannot over come the shortcomings or the bugs in Aboso's navigation systems programming. There are many.

Check out the new patch see if that addresses it looks like there was some approach fixes in that

 

On 9/29/2020 at 10:21 AM, Adrian123 said:

Be mindful, navagrph cannot over come the shortcomings or the bugs in Aboso's navigation systems programming. There are many.

Understood.  I know that Navigraph is doing the best they can.

Reinstalled the Navigraph data after the last patch. Flew an IFR into KSFF and I'm still getting the "USER" waypoint bug, but the waypoints were there and I was able to fly a successful ILS approach into Felts.  Pretty much gave up on RNAV approaches.

I was very happy to hear that MSFS is taking responsibility for improving the G1000 and G3000 instead of waiting for a 3rd party.  Hope to see some improvements soon.