KFC 225 Garmin 530 Glideslope capture

[redraider]

Hello Mooneyspacers,

 

I am having difficulty capturing the glideslope on RNAV approaches using the KFC 225 and Garmin 530.  When approaching final and glideslope comes alive, sometimes the autopilot will capture and fly the glideslope, sometimes not.  I suspect user error.

Any advice?

[thinwing]

Yeah ,first off ,if being vectored to the approach ,ask the controller for a vector well outside of the initial fix to give the box time to compute raim and message autopilot guidance available.Than there should be time manually enable guidance .If vectored in tight ,this doesn't happen and you get that flashing apr mode indication,and you won't couple.

[Marauder]

Hello Mooneyspacers,
 
I am having difficulty capturing the glideslope on RNAV approaches using the KFC 225 and Garmin 530.  When approaching final and glideslope comes alive, sometimes the autopilot will capture and fly the glideslope, sometimes not.  I suspect user error.
Any advice?

I don’t have a King but I suspect the intercept requirements are similar. On my STEC, the plane must be at least 60% below the glideslope centerline and no more than 50% deviation from the localizer at the FAF. Those conditions must exist for 10 seconds for the coupling to happen.

I would look for the “conditions” section of the King’s intercept requirements and see what it requires. One thing I found lacking in the STEC manual is the weak description of how RNAV approaches work with the autopilot.


Sent from my iPhone using Tapatalk Pro

[LANCECASPER]

On 5/11/2018 at 10:57 AM, redraider said:

Hello Mooneyspacers,

 

I am having difficulty capturing the glideslope on RNAV approaches using the KFC 225 and Garmin 530.  When approaching final and glideslope comes alive, sometimes the autopilot will capture and fly the glideslope, sometimes not.  I suspect user error.

Any advice?

It looks like the answer came on the other place you posted the question.

It's probably best just to post it once.