Fix iniBuilds A350 ILS capture in MSFS by checking approach tuning, LS and APPR modes, intercept geometry, navdata and scenery conflicts.
In Microsoft Flight Simulator, the iniBuilds A350’s ILS usually fails because the wrong approach or frequency is loaded, the receiver has not identified the localiser, APPR was armed too late, or the aircraft is above the glideslope. Verify the FMS arrival, show the LS scales, intercept below the beam and arm APPR.
How do I make the iniBuilds A350 capture the ILS?
The A350 must receive the correct station and approach it with valid Airbus capture geometry; engaging the autopilot alone will not find an ILS.
- Load the actual ILS approach. Select the destination runway, ILS approach and appropriate transition in the aircraft’s FMS. An imported route is not proof that the arrival is active, and an RNAV or RNP approach will not provide conventional localiser and glideslope guidance. If the route came from the World Map, confirm the procedure rather than assuming it transferred intact; our guide to setting runways and procedures in the MSFS flight planner explains where incomplete plans commonly arise.
- Check the tuned ILS. Compare the frequency and front course shown by the A350 with the selected approach. The FMGS should normally auto-tune the station when an ILS arrival is selected, but a stale manual entry can override that tuning. Clear the incorrect manual entry or tune the intended ILS through the aircraft’s radio-navigation controls.
- Confirm reception. Look for the ILS identifier and deviation indications. If there is no ident, the aircraft has not established a usable signal; pressing APPR repeatedly will not correct the frequency, range, runway or navdata problem.
- Display the LS scales. Press the LS pushbutton for the relevant pilot display. This exposes the localiser and glideslope indications but does not arm capture by itself.
- Use sensible intercept geometry. Approach the localiser from its front side at roughly 30 degrees or less, level at the published intercept altitude and below the glideslope. Avoid trying to capture after crossing the centreline or descending onto the beam from above. See our MSFS ILS interception walkthrough for the complete positioning sequence.
- Arm APPR and read the FMA. With the flight directors on, press APPR before reaching the localiser. The Flight Mode Annunciator should show
LOCandG/Sarmed, followed by capture annunciations as each beam is acquired. If only LOC was selected, APPR still needs to be armed for glideslope capture.
Does the LS button activate the ILS in the A350?
No. LS controls the display of landing-system information; APPR arms localiser and glideslope guidance. This distinction causes many apparently dead ILS approaches because the diamonds are visible, yet no capture mode is armed.
The FMA is the authoritative indication, not the illuminated button. The iniBuilds A350 is not identical to an A320, but our breakdown of Airbus approach-mode logic provides useful context for armed, captured and active modes.
What does each ILS symptom mean?
| Symptom | Most likely cause | What to check |
|---|---|---|
| No ident or deviation scales | Wrong frequency, excessive range, wrong side of the runway or scenery/navdata conflict | Selected approach, manual tuning, station position and add-on scenery |
| LS scales appear but nothing captures | LS is displayed, but APPR is not armed | FMA for armed LOC and G/S modes |
| LOC is armed but never captures | Large intercept angle, wrong front course or crossing from behind the antenna | Heading, centreline position and runway direction |
| LOC captures but G/S remains armed | Aircraft is above the beam, too close to the runway or only LOC mode was selected | Published intercept altitude and APPR selection |
| Modes capture and then disconnect | Controller input, conflicting bindings or an autopilot disconnect | FMA messages, flight controls and duplicated AP bindings |
Why does the localiser capture but the glideslope not?
The usual cause is intercepting the glideslope from above or selecting LOC without subsequently arming APPR. Remain level at the published altitude so the glideslope pointer moves down towards the centre, then allow the aircraft to capture it from below.
If the pointer is already below the centre when APPR is armed, the aircraft is above the beam. Do not force a steep descent to chase it; reposition for another intercept or fly a missed approach. Also confirm that the selected procedure is a full ILS rather than a localiser-only approach.
What if the A350 still receives no ILS signal?
If the ident and deviation scales remain absent with verified tuning, isolate whether the fault belongs to the A350 or to Microsoft Flight Simulator.
- Test the same ILS with a default aircraft. If that aircraft also receives nothing, use our simulator-wide ILS fault checklist to investigate the airport, navdata and simulator configuration.
- Test the A350 at another default airport. Successful reception there points to the original airport or scenery rather than the aircraft.
- Remove unrelated add-ons temporarily. Duplicate airport scenery and third-party navdata can redefine a runway or navigation aid. Test with unrelated Community packages disabled, keeping the A350 itself installed.
- Check the aircraft package. Install the latest compatible iniBuilds A350 update available through its original delivery system, restart the simulator and load the aircraft directly into a fresh session.
Weather and visibility do not switch an ILS transmitter off in MSFS, although they can change the runway assigned by ATC. A runway change therefore requires another check of the selected approach, tuned frequency and inbound course.
Why does the ILS capture but the A350 not autoland?
ILS capture and autoland are separate stages. Captured LOC and G/S modes prove that guidance is working, but autoland also depends on the runway’s capability, the required autopilot configuration, landing preparation and the expected LAND, FLARE and rollout annunciations.
If the aircraft follows both beams but those later FMA indications do not appear, troubleshoot the autoland configuration rather than retuning the ILS. Remain prepared to disconnect the automation and fly the missed approach if the annunciations or guidance are not correct.