18 minutes ago, Adrian123 said:

Just completed 4 RNAV approaches. All worked flawless. Though activation isn't quite the same or realistic compared to the Garmin Trainer, but they all worked well. KCID, KDSM, KOMA and KLNK. I was surprised really.

I gotta try those tomorrow!

Kinda odd also how it skips the initial waypoint in the procedure. May see if you notice that also. Though the altitudes do correspond with the charts.

I'll start taking more RNAV approaches.  

Just to illustrate this... My standard test approach (since the FSX days) is R01L at KTPA.

I typically come in via PIE to FITPA, and fly at 2000 feet AGL.

This does not work here... but I CAN fly the approach at 1000 feet AGL and it works.

(As I found out via trial and error..)

8 hours ago, Bert Pieke said:

Has anyone spent any time with this?

At some airports, the RNAV glidepath is so low that the GS marker on the G1000 is pegged to the bottom the entire time when flying the Approach.

At some others it works OK, and you can fly a coupled LPV landing.

Cannot really see any pattern..  Can anyone shed some light on this? 🙂

i not seen that yet, i dont fly in the US

i fly in sweden and norway use rnp in 95% of my landings, most of the middle and small airports use RNP LPV. the GS works OK for coupled lpv  and Vnav landings on the airports i fly to.

one thing i missing in the deafault flightplanner is option to set the transition fix point you often have 3 fixes and the planner set it auto for you, therfore i often set te approch in the g1000 proc page there you have the trans fixses.

I have Navigraph Charts 

 

Edited August 29, 20205 yr by westman

9 hours ago, Adrian123 said:

Just completed 4 RNAV approaches. All worked flawless. Though activation isn't quite the same or realistic compared to the Garmin Trainer, but they all worked well. KCID, KDSM, KOMA and KLNK. I was surprised really.

Do you mind sharing what you you had to do differently to activate the RNAV approach? For example I can get the King Air to display and follow the lateral guidance but not vertical.

6 hours ago, westman said:

one thing i missing in the deafault flightplanner is option to set the transition fix point

I agree 100% and find this to be annoying

Edited August 29, 20205 yr by SirDan

@PurdueKev  It might dpend upon the specific approach being used because you shouldnt have to do anything special to get the g/s. Try doing approaches that other people have tried with success and see if it works for you too. If it does then you know the problematic approach you tried was likely bugged OR it was not a WAAS appraoch.

Edited August 29, 20205 yr by hangar

Just now, PurdueKev said:

Do you mind sharing what you you had to do differently to activate the RNAV approach? For example I can get the King Air to display and follow the lateral guidance but not vertical.

1. Find the Charts for the approach you are using to determine waypoint altitude, I found the Alt on the Garmin is accurate in most cases. 2 Be at  the assigned alt. 3. Activate Approach in the Garmin. 4. When on the procedure, activate AP APPR. You will notice the Magenta Diamond on the PFD follow the Vertical GS when it is captured. Make sure the Magenta Diamond is not below the GS or it wont capture just as ILS. You will see it move when on the GS path..

3 minutes ago, Adrian123 said:

1. Find the Charts for the approach you are using to determine waypoint altitude, I found the Alt on the Garmin is accurate in most cases. 2 Be at  the assigned alt. 3. Activate Approach in the Garmin. 4. When on the procedure, activate AP APPR. You will notice the Magenta Diamond on the PFD follow the Vertical GS when it is captured. Make sure the Magenta Diamond is not below the GS or it wont capture just as ILS. You will see it move when on the GS path..

Thank you!

Hope that made sense. Not the greatest "technical writer" in the world. 😉

46 minutes ago, Adrian123 said:

Hope that made sense. Not the greatest "technical writer" in the world. 😉

I would add that for some approaches, I find myself above the glidepath, with the magenta diamond at the bottom, rather than at the top. If that happens, you have to descend manually, at least until you are again below the "glidepath"... By that time you may as well handfly it to the runway.

I may add, I performed these with the TBM930. True Bert. You must be below the glide path or at it.

10 hours ago, Bert Pieke said:

Just to illustrate this... My standard test approach (since the FSX days) is R01L at KTPA.

I typically come in via PIE to FITPA, and fly at 2000 feet AGL.

This does not work here... but I CAN fly the approach at 1000 feet AGL and it works.

(As I found out via trial and error..)

This particular approach seems to ignore the altitude restrictions until you hit WELIT (which intercepts as it should at the published 1,300ft). Once there the g/s seems to work fine.

So I just make sure I cross Fitpa & Snork at their published alts of 2,600 and at snork I make my way down to 1,300 to meet the g/s at 1,300 as I cross WELIT.

I noticed in the g1000 the alts did not get entered but they did in the g3000.

Dunno if the issue is with the navdata itself or how the gps units are interpreting it. Guess you'd have to look inside the nav data to get an idea.

Edited August 29, 20205 yr by hangar

Today I was cleared  to the first waypoint of an IFR  low altitude route at a NEGATIVE (-2140989489) feet or something like that, and ATC was mighty displeased that I was busting my altitude by more than 300 feet.

Tried cancelling and creating the flight plan in the air - kept getting the same weird number.  Started the flight completely over with the same IFR route and everything was fine.  Being intermittent like that, IMO doesn't sound like my bug at least was in the data. It makes me think there is an overflow bug of some kind of in the code where your number just comes up "craps" occasionally.