Starting a new thread to not derail the GDU v GTN question:
In this post the poster @Watzlavick has not captured the GP and appears that he thought he should have.
We have a similar approach here which has a 3.4degree path (OPs has a 3.6)
This approach hasn't changed in 4y in my case, however Garmin has in the last DB cycle has coded an intermediate point into the database between the IF and the FAF (the plate hasn't changed) which now means the VNAV won't transition GP because the geometry has the flightpath attempting to intercept the bogus GP from above in-between the IF and the FAF.
Previously VNAV would run to the IF at which time it would seamlessly transition to the (advisory) GP.
Im sure it's related to the service advisory issued by Garmin in the wake of the Steamboat CFIT (where the pilot appears to have remained coupled to an advisory GP below the MDA).
However, they just unilaterally changed it which meant I never left VNAV and was staring at a full deflection fly up GP at the FAF despite being exactly on profile - which got my attention. I disconnected and manually flew it, but I was rattled enough to go digging into what's changed.
see below. same approach, same plate (hasn't changed since 2022) -different database coding - big change in behavior. Id have thought worthy of explanation.
I understand it's an LNAV only but the advisory GP has been there forever prior and there's no danger of busting the MDA on the advisory GP in this case. certainly feels like lawyers getting involved in DB coding.
Pre DB change, the AP is in APR and has transitioned from VNAV and captured the GP at the IF.
Post DB Change. Note the insertion of the SH06 waypoint into the procedure which stops everything sequencing. In still in VNAV well below full deflection on the "new" GP despite being exactly on the 3.4 profile at the FAF.
Avionics Panel Layout... 3 - G3X or 2 w/ a 750xi
OK finished plane people - I know you're going to like what you have but anyone have input on 3 - G3X w/ a 650xi vs. 2 - G3X with a 750? I have the aerosport carbon panel and to do 3 - G3x with the 750 makes you have to remote a bunch of stuff. I have to make room for SDS controller and...
vansairforce.net
In this post the poster @Watzlavick has not captured the GP and appears that he thought he should have.
We have a similar approach here which has a 3.4degree path (OPs has a 3.6)
This approach hasn't changed in 4y in my case, however Garmin has in the last DB cycle has coded an intermediate point into the database between the IF and the FAF (the plate hasn't changed) which now means the VNAV won't transition GP because the geometry has the flightpath attempting to intercept the bogus GP from above in-between the IF and the FAF.
Previously VNAV would run to the IF at which time it would seamlessly transition to the (advisory) GP.
Im sure it's related to the service advisory issued by Garmin in the wake of the Steamboat CFIT (where the pilot appears to have remained coupled to an advisory GP below the MDA).
However, they just unilaterally changed it which meant I never left VNAV and was staring at a full deflection fly up GP at the FAF despite being exactly on profile - which got my attention. I disconnected and manually flew it, but I was rattled enough to go digging into what's changed.
see below. same approach, same plate (hasn't changed since 2022) -different database coding - big change in behavior. Id have thought worthy of explanation.
I understand it's an LNAV only but the advisory GP has been there forever prior and there's no danger of busting the MDA on the advisory GP in this case. certainly feels like lawyers getting involved in DB coding.
Pre DB change, the AP is in APR and has transitioned from VNAV and captured the GP at the IF.
Post DB Change. Note the insertion of the SH06 waypoint into the procedure which stops everything sequencing. In still in VNAV well below full deflection on the "new" GP despite being exactly on the 3.4 profile at the FAF.
