After tuning the ILS frequency and pressing APPR, the A350 does not capture the localizer or glideslope and continues on its previous lateral and vertical mode.
Expected result: APPR arms, the aircraft captures the localizer, then the glideslope, and flies the ILS down to the runway.
Actual result: APPR is pressed and the ILS frequency is tuned, but the aircraft never captures.
I also experienced a similar issue with A359 on approach to WSSS when it was featured as a hub a couple of days ago. As a temporary fix, I always update my FPL to the runway that I’m about to intercept to.
as of now bro i use RNP/RNAV for all of my app since ILS is pretty unreliable even in KSEA earlier the ILS G/S didn’t even capture after tuning in and still the issue remains and no response from devs aswell atm.
I have flown for over 3000 hours and have never encountered the issue of being unable to capture ILS as you mentioned. I wonder what is your operational procedure during approach? I have flown the B77W and A35K the most, as well as other aircraft such as A380, A359, A320 series, B737 series, and B787 series. Every approach and landing can capture ILS normally.
Why not switch your LNAV from GPS to NAV when you approach the runway? You should switch the GPS to NAV and then turn on APPR to capture ILS. Since you have set NAV on the landing runway, you will not capture ILS with GPS.
In the past version, I have been landing like this for more than 3,000 hours. Most pilots are the same. Your advice is indeed useful, but it does not mean that my previous method is wrong. You can ask most people if they land ILS when connecting GPS. It’s just that this version There was an error (BTW, yesterday I still used to use the method I used to use to use to land successfully in PVG)