Inibuilds A320neo ILS G/S and Landing Troubles

[Ebear1989]

Hi there,

I’ve recently dipped my toes into the world of simming on Xbox, and I’m currently flying the Inibuilds A320. However, when it comes to landing, it feels like I’ve signed up for a crash course… quite literally! Over the past few days, I’ve attempted the same short flight (EGKK/EGCC) about 12 times. Everything goes smoother than a buttered runway until I hit the Top of Descent (TOD). From there, it’s like my A320 decides it’s auditioning for a role in a disaster movie.

Here’s the issue: initially, I couldn’t get the aircraft to descend properly from FL240. I’d enter 3000ft into the autopilot, set it to managed mode, and sit back, expecting a flawless descent. Instead, the aircraft sticks to the constraints like glue but then ends up so high that intercepting the LOC and G/S feels as likely as winning the lottery. So, I started descending sooner, completely ignoring the constraints and ATC (sorry, virtual controllers), and would arrive at 3000ft on final. In theory, this should mean it captures the G/S, but nope, the A320 just flatlines at 3000ft like it’s scared of heights. I’m at the point where I’m considering offering the plane a nice cup of tea to calm its nerves.

It shows LOC* is engaged, but then it just cruises at 3000ft, waving goodbye to the G/S like it’s an ex it’s trying to avoid. After trying this about a dozen times, I’m seriously considering if the A320 has something against landing at EGCC. I’m sure the problem is with my procedure and not the aircraft itself, so if anyone can spot what I’m doing wrong, I’d be eternally grateful (and so would my virtual passengers).

For reference, here’s the flight I’m attempting:

Departure:
EGKK / LGW 08R - LAM1Z

Arrival:
EGCC / MAN ILS05R - EVO1M
LOC/ILS IMC/111.55

My routine, which clearly needs some work, is as follows:

• 5nm from TOD: Start descent (3000ft - managed mode)
• At DAYNE (last waypoint before final approach): Press LS
• On the turn to final approach at 3000ft: Press LOC
• Once on final: Press APPR

This is where the magic doesn’t happen – the aircraft just stays at 3000ft and misses the G/S like it’s too cool to land.

I’m confident I’m setting up everything correctly, from importing the flight plan from SimBrief to loading the weights and configuring the MCDU, including entering the arrival and departure in the F-PLAN. However, my A320 clearly disagrees.

[DulcetMite89521]

The STAR ELVOS1M you describe above has an altitude constrain of FL80 and 230 KTS at DAYNE so if you are descending in managed mode (DES mode on PFD) - the aeroplane will NOT descend below FL80 until it is passed DAYNE (Airbus systems are quite smart) even if you have selected 3000ft in FCU (Flight Control Unit). The only way to get out of this is to use open descend mode or vertical speed mode. Or you will need to delete the altitude constrain in MCDU.

Also I am not sure what routing are you following after DAYNE - as in reality you will expect radar vectors to final approach course. If you are trying to intercept glideslope from above - it won’t work. If you see right pink diamond (glideslope) on LS underneath, you are high on profile and will need to manually intervene and get the plane down to catch up with pink diamond. I have attached a screenshot underneath of how PFD should look like when the airplane is fully established on ILS in approach mode.

Need bit more info to figure out why the airplane is not following ILS. Have you checked your NAV radios to ensure that ILS has been tuned in?

[OliveAmoeba3772]

You don’t need to press LOC, just APPR when you see the magenta diamond heading down as you are about to intercept the G/S. Watch out for winds if you are using managed descent. If you get above profile as shown in the MCDU or the green dot on the altitude tape use the speed brake to get you back on track. I’m

[BigCow74]

A couple things. A screenshot of your PFD G/S diamond near where you are expecting capture could be helpful. There are some good suggestions above to help debug. Also make sure your baro is set so there’s no error in your altitude that could make you miss capture by being too high.

All that said, the ini A320 v2 tends to be too high on profile. There was a discussion about this in the main thread a while back. I experience that as well, and usually need to intervene to get down quicker. Perhaps drag is not completely accurate in the flight model.

[crazyhorsejesol]

I repeated your flight,same data . When you are at CF035 just before the last turn right make sure you are at 3000ft .You can activate LS and Loc. You can see the alt magenta diamond on the right . At CF05R you are just below it ! So on final ,make sure you are at 3000ft then activate Loc and Appr before reaching FF05R checking that you are still below the Alt magenta diamond on the right so G/S will be engaged. I did an autoland without problems.

[Boeingspeedbird]

Sometimes g/s doesn’t capture at some airports. Put your platform altitude 100-200 feet below the published limit for course fix and final fix. I’ve followed various tutorials and guides and now press Appr at about 5000 to arm the loc and g/s capture (after pressing the LS button just below FL10. Make sure you’re also managing speed by selecting approach phase in the McDU much earlier than the decel point on the profile.

[Ebear1989]

Hey all,

Thanks so much for all the help so far! I gave it another shot this morning, but unfortunately, I’m still getting the same result. This time, though, I made sure to take some screenshots to give you a better idea of what’s happening.

My current hypothesis is that, even though I’m at 3000ft to capture the G/S, I might actually need to be a fraction lower for it to work properly.

Below are some images that show what’s happening. In the flight chart, I’ve indicated the transition from DAYNE that I’m using, and you can see the G/S is at 3000ft.

Any thoughts on this? Could being just slightly lower make the difference, or is there something else I might be missing?

The RADIO NAV is tuned to the correct ILS frequency.

I’m at 3000ft and below the Megenta diamond as I bank round the final approach.

But then loose the glide slope on the final approach.

[Ebear1989]

Thanks for the suggestion! I’m going to give it another go, and I have a feeling you might be onto something. Setting myself 100ft below the G/S capture altitude might just do the trick. I’ll try that on my next attempt.

You also mentioned selecting the approach phase in the MCDU, which I’m not currently doing! I haven’t seen that step in any of the procedures I’ve been following. Could you explain what you mean by this and how I should be using it? It sounds like it might be the key to getting this right.

Thanks again for all the help!

[Ebear1989]

This is really helpful—thank you! I realised I’ve been missing the step of pressing APPR before reaching FF05R. I was waiting to straighten up before engaging approach mode. Do you think this could be the cause of my issue?

You can see on one fo the screenshots I just shared that I’m passed FF05R with everything set except APPR.

[BigCow74]

@Ebear1989

everything set except APPR

Yes that would be the cause.

[crazyhorsejesol]

On your 3rd pic you are just below the magenta diamond and you must press Appr immediately because after the turn ,when on final, you are going to miss it! As shown on your 4th pic.
Of course you can press Appr even 3-4 miles before the turn ,to be on the safe side.
This is a quite sharp turn on final and there isn’t much time left to act.In this case you shouldn’t wait to see the horizontal magenta diamond first ,as shown on you 4th pic , but press Appr even if only the vertical diamond is on sight (as it is during the turn)… and G/S will be captured .

[Boeingspeedbird]

Flybywire docs are really helpful and straightforward:

A320neo Pilot Briefing - MCDU - FlyByWire Simulations Documentation

[Boeingspeedbird]

Approach button on autopilot panel needs to be selected way before (the LS button only tunes the receivers, but does not engage the approach to action the incoming signals). I press approach at about 5000.

[Boeingspeedbird]

3000 at 7 miles out and no slats and flaps means you won’t be managing the energy / speed. As above, need to engage the approach phase on the MCDU so that auto throttle can manage the speed automatically to VAPP as you select increasing flaps.

[OliveAmoeba3772]

Here’s an overview for reference.

https://1drv.ms/b/s!AtQsPXDLGL9vgdlljR1fZaC6BXBYNA?e=EBIzp5

[DulcetMite89521]

From your above screenshots it looks like you forgot to arm APPR or approach mode - remember LOC mode only tracks Localiser, it won’t track glideslope. In order for autopilot to track glideslope - you need to press approach mode, you need to do this while the pink diamond is above. If you press approach once pink diamond is significantly lower - it won’t work. The airplane will stay at 3000ft in this case.

Also you haven’t got flaps down by 7.0 NM - Managing your energy on descend is going to be very difficult. I use rule of thumb which is used by most operators - At 10 NM speed 180kts with Flaps 1/2 depending on weight and type, By 5NM 160kts or lower with gear down and flaps in Landing config.

[Ebear1989]

Hello all you helpful folk. I can’t thank you enough as you’ve made my night. I managed to successfully land the bird and in pretty murky weather too.

Following all of your suggestions, being a fraction lower, enabling stuff sooner, getting them ■■■■ flap out it was a success.

Now on to greater things and some more adventurers flights.

Thanks

[Boeingspeedbird]

Excellent. Well done. Here’s to more successful flights.

[DanDaredum]

Yeah just be under the glide slope with approach and LS buttons pressed to capture. Never press localizer button.

[DulcetMite89521]

Well done! Airbus is more simpler to fly for pilots but the systems and computers behind it are quite complex. Nevertheless enjoy the true art of flying!