Jump to content

A350 not catching Localizer for ILS


Recommended Posts

Posted

A350 seems to have a bug or maybe not not sure. But everytime I try to do an autoland the localizer beam does not appear. I have done an autoland before on the A350 and only seemed to have this problem after 1.18

  • Like 1
Posted

Hello,

Does this happen at every scenery? If no, are you using a custom scenery for whatever airport you're flying into? If yes, please try using the default scenery to rule out any conflict on that end.

Thank you 

Eddie
Community Manager 
iniBuilds Ltd. | inibuilds.com

Posted

Sometimes the LOC ident doesn’t autotune and that could be due to some scenery problems, nav updates or even sim updates. Cross check your NAV IDENT page in the KCCU as part of your approach briefing and make sure you have the LOC IDENT, frequency and course on the ILS field. If you don’t, then that’s why you can’t intercept the LOC. But the good news are that you can always insert the IDENT and it will automatically populate all the necessary fields (ILS frequency, course)

Posted (edited)
19 hours ago, Hi58 said:

A350 seems to have a bug or maybe not not sure. But everytime I try to do an autoland the localizer beam does not appear. I have done an autoland before on the A350 and only seemed to have this problem after 1.18

Edited by Dimitrios
I have the same problem !!!
Posted
11 hours ago, Eddie said:

Hello,

Does this happen at every scenery? If no, are you using a custom scenery for whatever airport you're flying into? If yes, please try using the default scenery to rule out any conflict on that end.

Thank you 

I was not using a scenery and I also double checked the ILS frequency 

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...