Morning, the option to "deselect SLS" should result in FLS being defaulted. At the moment this isn't the case.

Thanks

7 hours ago, Adrian350 said:

Morning, the option to "deselect SLS" should result in FLS being defaulted. At the moment this isn't the case.

Thanks

Hi, are you able to record a video adding the issue, I am not as familiar with SLS/FLS unless I'm just mis-remembering. Thank you

I’m not entirely sure how it works on the 350, but I imagine it’s the same as generic Airbus logic.

FLS is a system which allows rnav approaches to b be flown with the same indications as ILS approaches.

It’s often an option rather than default, and can only be used on rnav approaches with a straight approach.

If you activate the LS push button and there is a straight in approach with FLS available, the final approach modes will be

F-G/S and F-LOC.

But for any rnav approach if you don’t activate LS you should get FINAL, APP NAV and then FINAL APP when both are captured.

Similarly if you try to use LS but it’s a curved approach and FLS is not available it still should be FINAL, APP NAV, and then FINAL APP.

But the a350 is currently treating all rnav approaches as FLS an it seems to be impossible to get the standard FINAL, APP NAV, and FINAL APP.

15 minutes ago, dectenor2 said:

I’m not entirely sure how it works on the 350, but I imagine it’s the same as generic Airbus logic.

FLS is a system which allows rnav approaches to b be flown with the same indications as ILS approaches.

It’s often an option rather than default, and can only be used on rnav approaches with a straight approach.

If you activate the LS push button and there is a straight in approach with FLS available, the final approach modes will be

F-G/S and F-LOC.

But for any rnav approach if you don’t activate LS you should get FINAL, APP NAV and then FINAL APP when both are captured.

Similarly if you try to use LS but it’s a curved approach and FLS is not available it still should be FINAL, APP NAV, and then FINAL APP.

But the a350 is currently treating all rnav approaches as FLS an it seems to be impossible to get the standard FINAL, APP NAV, and FINAL APP.

Got it, thanks.

I'll pass this along to the team.

Hi,

First of all, the A350 does not have a FINAL, APP NAV or FINAL APP modes. Please do not implement these. Unlike in the older Airbuses, FLS is installed by default in the A350 and it is used for RNP approaches with LNAV/VNAV and LNAV minimas. It can also create an "ILS-like" indication for some LOC and VOR approaches.

As Adrian said, when you press the DESELECT SLS button, it should give you the FLS indication so that you can fly an RNP approach with LNAV/VNAV or LNAV minima. Now it seems to give you the vertical guidance of the APP DES mode, which is only meant for the RNP AR approaches. In the current version, it looks like the FLS is only available for those RNP approach procedures, which do not have a LPV SBAS approach associated with them.

This is how it looks like at the moment. This approach (EDDH RNP 23) has LPV, LNAV/VNAV and LNAV approaches in the same procedure. The default is LPV (flown with SLS). When you press the DESELECT SLS button, it brings up the vertical guidance of the APP DES mode (in the screenshot).

This is the FLS indication (the double diamonds) you should get after pressing the DESELECT SLS button:

Edited May 26May 26 by ool

1 hour ago, ool said:

Hi,

First of all, the A350 does not have a FINAL, APP NAV or FINAL APP modes. Please do not implement these. Unlike in the older Airbuses, FLS is installed by default in the A350 and it is used for RNP approaches with LNAV/VNAV and LNAV minimas. It can also create an "ILS-like" indication for some LOC and VOR approaches.

I was able to find information corroborating your statement here within the Safety Airbus Website as I agree with this being the case as it's something I've been told before, what I had logged was regarding Deselecting SLS, I still am working on keyboard clarity when addressing multiple issues in one post; https://safetyfirst.airbus.com/lets-use-xls/?airbus-iframe=true&airbus-post=2048

Hi,

Yes that's the idea, if you deselect SLS the display should revert to an FLS approach.

On that note, having just come back from SFO, the SLS for runway 10L is offset, however it appears the model you have can only generate a straight in SLS path so you cant fly the approach correctly?

Thanks

Adrian

On 6/2/2026 at 8:11 AM, Adrian350 said:

On that note, having just come back from SFO, the SLS for runway 10L is offset, however it appears the model you have can only generate a straight in SLS path so you cant fly the approach correctly?

I think this is part of the same issue that is described here: https://forum.inibuilds.com/topic/36854-a350-fls-course-is-incorrect-with-rnpldavor-offset-approaches-show-runway-course-instead/

I checked few approaches in the sim and there were a couple of issues in the Inibuilds aircraft. I tried to make detailed examples, so it would be easier to see and fix the problems.

1. For the approaches using FLS that have a Missed Approach Point (MAP) before the runway threshold, the course for the FLS beam should be the course that leads to Missed Approach Point (MAP) (FCOM: "the course that is stored with the MAP in the navigation database"), not the runway track.

2. The runway waypoint (waypoint named according to runway, e.g. "EGLL27R") is added even if it should not be part of the approach procedure. I think this is partially the reason for the issue number 1. See examples below.

Here is Taipei RCSS RNP 28, the same approach as described in the link above. According to the procedure, there should be no runway waypoint RCSS28. The correct sequence should be JOHNT - VANES (MAP) - DENIS and then rest of the missed approach procedure. Since MAP is located before runway threshold, the final approach course for the FLS should be the course leading to VANES = 272, not the runway track 277. I think this is an issue with the Inibuilds A350 and not with the navigation database, since some other add-ons are able to show the same approach correctly.

Here is Bangkok VTBS RNP 20L. In this approach, the missed approach point is named as "BS781", which is located at the runway threshold (+-0.14NM), and it is also the anchor point for the FLS beam. In the Inibuilds A350, BS781 is correctly the missed approach point. However, there is also a "VTBS20L" waypoint, which shouldn't be there, since MAP in the procedure is not defined in format "ICAO code + rwy ident", but as a waypoint. The correct sequence for the waypoints would be BS780 - BS781 - DE20L - BS601 etc.

As the MAP is located on the runway threshold, the correct FLS beam course is the course of the final-approach flight leg. In this case it is the same as runway track, but in Adrian's example of KSFO 10L LPV approach, there is a difference, and that is probably the reason the approach path is incorrect.

As a last example, Frankfurt EDDF RNP X 25L. In this approach procedure, the Missed Approach Point is on the runway threshold and it is named by the ICAO code and runway ident "EDDF25L". So in this case, the runway waypoint is correctly there and the waypoint sequence is fully correct.

3. FLS should not be available, if:

• Missed Approach Point (MAP) is before runway threshold, AND

• The difference between final approach course and the runway course is more than 50 degrees.

In this case, there should also be a "NO FLS FOR THIS APPR" message in the FMS message area.

Example: Split LDSP RNAV Visual 23 the difference between final approach course and runway track is 169 degrees and missed approach is before runway threshold, so the FLS should not be available for this approach. See also the final approach course for FLS, which is according to the runway track (see point 1) and the "LDSP23" waypoint, which should not be part of the procedure and it messes up the whole missed approach procedure (see point 2, the correct sequence would be RORKA - SP502).