ILS info not displaying a320neo

[MimikriX]

@RomoRocket

it still captured the glidescope.

Still my question: how did you determine that the glideslope was captured?

[RomoRocket]

Because the 320 descended on its own at around 2-3000ft it began to descend, with auto pilot enabled obviously.

[MimikriX]

Ok, that is what I thought you would say. If you want my opinion: the around 2000 ft/min descend is not an indication for the glideslope. When the glideslope was catched correctly the descend is around 750 ft/min down to the runway. Somebody chime in please if I’m wrong.

[MimikriX]

@Neo4316

Hmm… I think your google search might have been a bit out-dated. I checked in Navigraph, and Faro has ILS for both sides of the runway. And there are two ILS approaches to RWY 10. ILS Z and ILS Y.

It may not be CAT I/II certified the same way as ILS RWY 28. But it is a certified ILS approach nonetheless. So both needs to be there and not removed.

I did some hefty Internet search and ended up in believing that Faro (LPFR)… as well as for example Pico… only have ILS cspability for one runway direction. This is based on the facts that on at least 10 different places I got charts that show both runway directions but only one of them got an ILS frequency depicted. For Faro this is rwy 28 and 109.5 MHz. I specifically searched for an ILS frequency for the Faro rwy 10 and simply couldn’t find one.

[NeoKingRthur]

That’s probably because LPFR/Faro Runway 07 doesn’t exist.

My navigraph charts only has a single runway with 2 directions. Both directions have ILS capability.

LPFR ILS 10 = 110.50
LPFR ILS 28 = 109.50

So depending which direction you’re approaching the runway. As long as you have these frequency tuned in, your ILS should work.

[RomoRocket]

I can’t remember precisely what height I was but the a320 descended to runway with autopilot engaged, so is it must have captured the glidescope.

Anyway I tested at a few other airports yesterday such as Heathrow and ILS info displayed, so must have just been a bug.

[FiendishLime281]

you mean capture the LOCALIZER for ILS. “capture de ILS” isnt bad expression but is not specify because the ILS have the LOC and GS and when you say only ILS isnt specify witch one you want to say.

[RomoRocket]

Thanks, as said earlier Im not familiarised with the terms.

[FiendishLime281]

the intention of my comment is that you acquire knowledge since you are new

[RomoRocket]

Oh yeah for sure. Thank you.

[MimikriX]

Sorry, my fault: I meant rwy 10. I did correct it in my post.
Thanks a lot for providing the frequency for rwy 10: I’ll give it a try.

Update: I just now landed in Faro ILS rwy 10.
I had a bit of a problem becaus while descending the AP left the glide path two times (suddenly went into a climb) but after manual correction and re-enabling the AP everything went well. I think that is why planes still need real pilots!

PS: signing up for Navigraph just now…

[geloxo]

Since SU9 when you select the assigned approach on the MCDU it fails many times to include the ILS frequency of the assigned approach. You can see that the assigned ILS is set but the frequency is not tuned and you need to tune it manually. It´s not happening on the Neo only but also in the 747.

Cheers

[mdapol]

I don’t think the 747 has automatic ILS tuning IRL.

[geloxo]

At least the 400 model has it. This is from the 747-400 operating manual.

Cheers

[mdapol]

Interesting. But since you should always double check the frequency it’s not really a big problem.

That being said I’m hearing other reports from other planes and even the NXi that this may be a system wide issue

[geloxo]

You are right. I always check it too using the flight charts data. It’s the best to avoid errors.

Cheers