Well a G1000 on a NPA is either descending using V/S mode to an altitude capture (MDA) or on an advisory G/P where it won’t descend below the altitude bug.
What airframe G1000 system are you referring to? I could get a G1000/GFC700 Perspective system in a SR22TN to level off at an altitude if it was in VS or VNV mode, but not in approach mode following a GS or advisory GS. Other than that, it just announced minimums (settable to the nearest 20 feet). The Perspective System I am familiar with did not support VNV on an approach beyond the IF prior to the FAF. Beyond the IF, the VNV based on Baro VNAV could not be used, the only vertical guidance available beyond the IF is a WAAS/SBAS derived glidepath for an approach.
I could get a G1000/GFC700 Perspective system in a SR22TN to level off at an altitude if it was in VS or VNV mode, but not in approach mode following a GS or advisory GS.
My experience (not in SR22) too.
I assume Jason was referring to an NPA without +V
As NCYankee suggests, my autopilot won’t level off on a glideslope. I don’t think any will – should have made that clearer. Only on a NP approach (VS hold etc) will it do that.
Also I have 100ft, not 10ft, increments on the altitude preselector (KFC225).
I found mine would level off on a +V but not an LPV or LVAV/VNAV
I found mine would level off on a +V but not an LPV or LVAV/VNAV
What airframe? I have never seen this on the G1000/GFC700 systems for Cirrus, Beechcraft, and Diamond. How would the system know which altitude to level off at as this is not fixed for a given approach, for example different category aircraft, circling or not, remote altimeter, or other outages such as approach lights, etc. In the G1000 systems I am familiar with, the only level off is based on VNV prior to the IF or a selected altitude with VS or IAS (FLC) mode.
Mine levels off based on selected altitude.
I found mine would level off on a +V but not an LPV or LVAV/VNAV.
In all G1000/GFC700 installations I am familiar with the following happens:
During LNAV+V approach the autopilot will follow the +V advisory path, stepping-down to each +V advisory level in turn (provided VNV is enabled and the “assigned” ALT is set to below the final advisory level). If one wants the A/P to follow the advisory GlidePath, capture of GP must be enabled before the final track has been intercepted. When on GP (as when on the GlideSlope during an ILS) the autopilot WILL NOT LEVEL OFF regardless what the “assigned” altitude or baro-minimums (at References) have been selected. The only way I know of to make the GFC700 level off is to press the ALT button ….
Mine levels off based on selected altitude.
It must be someting special about Meridian then?!
JasonC,
For the third time, I ask what airframe are you talking about. You have ignored answering my question again.
Edit, I see ANTEK has answered my question. It is with the Meridian.
The VNV you are describing is not +V which currently only exists on LNAV final approach. The VNV is programmed into the flightplan and uses a Baro VNAV technique to make programmed descents. The versions of VNV on the G1000 that I am familiar with, do not provide vertical guidance on the approach once past the IF and proceeding to the FAF.
Jason is not ignoring you, NCYankee!
It is a beautiful summery New Year’s Eve here.
Most likely JC is by the pool, sipping Fosters through a straw and minding the shrimps on the Barbie 
No that was Antek’s description. It is a Meridian and I do mean the advisory glideslope not the VNAV. I will try it when back and confirm.
And Antek is right. I admit to being in holiday browsing mode so any ignoring is purely by accident!
But the most important correction is that Australians don’t actually drink Fosters. We keep it to export to England.
