ILS not captured
-
I did a short RNAV-only (no GPS) hop from EGNS to EGPK. All went well until intercepting the localizer, while the aircraft was on a heading, with the autopilot HDG and ALT modes engaged. The localizer needle started moving in, but the Baron continued on the HDG.
I quickly double-checked that the NAV/GPS selector displayed NAV and not RNAV. I confirmed it was displayed the amber NAV. I also double-checked the HSI source was set to NAV 1 and not RNAV. The selection was correct. Less important, but the DME indicator was also correctly configured for the approach, with the N1 selected.
The aircraft should have captured the localizer. I also tried turning off HDG as well as the APP mode and re-engaging APP, to no avail. I eventually disengaged the autopilot and landed manually.
This was not the first time it occurred. Out of the 17 flights I conducted since I bought the Baron on the 15th, I encountered this issue 3 times.
Oddly enough, my previous two flights (EGNS to EGGP and EGGP to EGNS) were also no GPS flights, using RNAV only, and I had no issues capturing the ILS in Liverpool and later in the Isle of Man.
-
Same happened today, using the 3rd party KLN90 GPS. Approaching KOMA, vectored around by SayIntentions AI. HDG mode active, I switch NAV sources from GPS to NAV.
Localizer comes creeping in, APP mode armed and displayed. Nothing happens, aircraft continues on the HDG. I adjust the HDG bug to capture, disengage AP, disengage FD, re-enable FD and AP, engage APP mode, nothing. No capture. Landing manually.
-
I tried this too, doing a quick RNAV flight from KPAE to KBLI. On approach into KBLI runway 16, I'm able to capture the localizer using RNV/APR on the KNS-81, approach mode on the autopilot, and RNAV selected on the GPS-NAV control selector. But while the HSI displays glideslope indicators, the autopilot doesn't capture the GS. My assumption is that I'm doing something wrong, but I did notice one thing.
According to a KNS-81 manual I found online, the unit should recognize an ILS frequency and display no radial or distance information. What happens instead is that I can input both radial and distance data for an ILS frequency. Maybe the unit isn't properly recognizing ILS approaches? Or maybe I'm setting it up wrong. I'm not sure.