LDA approach not correctly represented in A350

[chrispychips]

I attempted the LDA W approach, runway 22 at RJTT. In real life, after selecting LDA W 22 and inserting it into the F-PLN, there should be a LOC index along bottom of the PFD where you can monitor the raw data localizer (in this case IKL 110.1, course 277). Nearing waypoint BONDO you would arm LOC in the AFS, and then preset the FPA of minus 3 degrees. Almost at waypoint BONDO you would then pull the FPA knob and fly the approach in FPA LOC (with an FPA of -3deg).

I was not able to bring up the raw data Localizer Index at all at the bottom of the PFD. As shown in first photo, when selecting LDA W 22, by default it shows FLS with the F-LOC and F-GS index.

When deselecting FLS in the NAVAID page, it shows a VDEV brick on the right of the PFD as in the second photo. I believe this is incorrect.

The raw data Localizer index should show on the bottom of the PFD, so the approach can be flown in FPA LOC. Can you confirm that this is a bug? 

Thank you.

[Andrew Miller]

Might be worth trying this with an LOC approach to see if the behavior is identical. Not sure if it’s correct or not, but that would at least establish whether this is an LDA-specific issue.

An LDA should be handled the same as an ILS or LOC approach (depending on whether it has a glide slope or not), but I know of at least one other addon that doesn’t handle them properly, so it’s possible something needs to be fixed here, too.

[chrispychips]

Hi Andrew,

Thanks a lot for the suggestion for trying the Localizer approach for runway 22.

At Haneda Airport RJTT for runway 22, there are two separate Localizers which allow two different Localizer approaches to be performed.

One is a conventional Localizer approach which is aligned with runway 22. The Localizer Ident is IAD 108.1 with an inbound course of 222 degrees. 

The other Localizer is offset with runway 22. This offset Localizer is for the LDA approach. The Localizer Ident is IKL 110.1 with an inbound course of 277 degrees.

The LDA 22 approach into RJTT utilizes the offset Localizer IKL 110.1. The approach is similar to Kai Tak where the chart has the aircraft flying down a 3 degree slope from BONDO which should be flown in modes FPA -3.0, and LOC to an MDA of 1000ft, and then the pilot needs to bank left to align with runway 22, with a runway QDM of 223 degrees.

In real life when performing the LDA 22 approach into RJTT the A350 shows the Localizer Index on the PFD of IKL 110.1 (magenta diamond).

The iniBuilds A350 PFD does not show this, so it appears this is a bug.

Cheers.