Need HELP with ILS in King Air or TBM

Can someone here point me in the right direction or go thru the steps to perform an ILS landing in the King Air or TBM. I’ve watched every video on You Tube over and over and I can capture the Localizer but NEVER the glideslope. I get to the final approach fix at the correct altitude but it never captures the glideslope. I’ve tried everything and give up. I’m sure it’s probably something simple that I’m doing wrong but I have no idea what. Appreciate any help! Thanks

I could be wrong but have you tried switching your nav source from gps to nav(purple to green)

2 Likes

Did you put the localizer frequency correctly (it needs to be done manually)? Did you activate Appr mode? Were you in correct height (glide slope needs to be captured in specific altitude and usualy at specific waypoint)?

Yes switched nav source from gps to Loc1

Yep, loc freq put in manually, activated approach mode and as far as I know i’m at correct altitude, following chart and ATC.

Do you intercept the glideslope from below? That is to say: do you see the glide slope indicator (little diamond) on the top of the instrument, as you wait for it to gently come down when you enter the ILS?

I suppose it could be a layman’s error to intercept the ILS from too short a distance, so just veryfing that. It’s not impossible to intercept a glideslope from above (pretty standard in Amsterdam Schiphol for instance) but it sure is less comfortable.

1 Like

Yes the little diamond starts at the top and come’s down as I enter the ILS. It gets to the middle and keeps falling all the way to the bottom.

Ah… Right… Are you perhaps using a bravo honeycomb throttle hardware? Or something similar?

Because I do, and when I keep the mode-selector button in the Vertical Speed-mode, it will refuse to follow a glide path. It’s like its holding the autopilot V-speed mode in zero, regardless of whatever I’m telling it software wise.

Whenever I turn the knob on the hardware to heading-mode instead, it follows the approach mode as it should.

2 Likes

Did you see the correct localizer DME name and frequency shown in the bottom left corner on FD? What was shown on autopilot info display on FD? Approx in the midle of the FD at the top in the altitude mode window? Was it showing G/S armed, I mean was there G/S written in blue?

This mode-selector I mean.

You might have solved the problem. I’m using a Bravo and the mode selector is in VS. Let me try it in heading mode and see if that fixes the problem. Thanks for the tip! I’ll let you know if that fixes it.

2 Likes

There was (or is?) a bug relating to this in the Bravo default configuration in MSFS.

If I remember correctly, placing the left knob in the VS position (or passing it on the way to another position) caused it to also activate VS-mode as if pressing the VS button.

So if your config is based on the default, this is one thing to check. Just ignore, if I’m completely off track, here. :sunglasses:

That solved my problem SkyVagarant. Captures everytime now, I’ve tried to different approaches. Thanks so much for that suggestion, I never would have figured that one out. Thanks guys for all the replies! Back to happy flying!

SU brought out issues with the Honeycomb Bravo AP controls. And now that they’re constantly changing the SDK in the background, those seem to be getting worse.

I’ve since unbound every AP control on my Bravo and all these strange nav issues have gone away for the most part.

I think this is the issue that is identified above:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.