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.
-
I have not had any issues, just tested ILS at 6 different airports with duke and baron using tds 750. I have heard issue may be pms related somehow. Aside from that some reports may be user error...
Hmm, it seems I misunderstood the OP here. It looks like he's using the nav 1 radio for ILS approach, while I thought he was using the KNS 81. I haven't had any problems with ILS approach using any other equipment aside from the KNS 81, so I don't have the same problem.
@kityatyi my advice, if you haven't tried it yet, is if you have the PMS 750, uninstall that and try the ILS approaches again. Maybe try uninstalling the KLN 90, too. The PMS 750 in particular has caused me problems at least once in the past, even when I don't have it loaded into the plane. Another thing to try, if you use Navigraph navdata, would be uninstalling and reinstalling the navdata.
-
Hi,
I do not have the PMS. Only have what comes with the package. It's completely a matter of hit or miss. The same config sometimes yields to a successful ILS capture, sometimes the ILS does not capture. Yes, the indications are fine, the needles move as they should, but HDG mode remains active, APP remains armed but not activated. So far I only noticed this behavior when I was using a config which included the KNS81 RNAV computer, in which case, the issue happened more than 50% of the time. Yes, I always use the NAV 1 radio for the ILS approach, change the NAV source well in advance, change HSI source, the DME source. Everything is well prepared for the capture. I also tend to use HDG mode to intercept the localizer, even when my RNAV waypoint could achieve the same, I switch to HDG mode and expect the LOC to take over - but it does not happen consistently. I never noticed this before I started to use the RNAV computer. In the early BS days, the RNAV computer wasn't working with the autopilot and so I never chose a RNAV panel config - never experienced the problem of non-captured ILS either. But since I bought the new Baron, and since then the Duke, knowing the RNAV can be used with the autopilot, I actually use it a lot - and interestingly, the issue with the ILS appeared. Therefore, I dare to say this behavior is somehow related to the RNAV system and its methods of utilizing the autpilot. Perhaps 3rd party scnery also play a role here (I only fly to 3rd party scenery, never use stock ones, except for those "enhanced" ones). So it may be more than just one thing. -
I did four flights in the Baron today, and on the last one I used the 3rd Party KLN90B GPS. The flight was to EGGP. ATC gave me vectors for the ILS RWY 27 approach. As I no longer needed to follow the GPS, I switched the NAV source from GPS to NAV. I had the ILS tuned into NAV 1 (111.75) and the course set on the HSI. The ILS was identified and the needles started to creep in. I was in HDG mode, with APP armed. But the localizer was never captured, the Baron continued in HDG mode. I tracked the localizer in HDG mode, then disengaged HDG mode, clicked APP but nothing happened. Turned off the F/D and the A/P completely, back on, hit APP, nothing. I eventually landed manually.
It would appear to me this issue does not occur with the GNS 530/430 but it does occur when either the Black Square RNAV system or the KLN90B panel config is used. I am yet to fully verify if the GNS 530/430 aren't affected but I can't recall this happening with that GPS config.
I will download the free PMS and see if the issue happens with it.