FSX won’t capture the ILS localizer? Check active NAV1, NAV/GPS source, APR mode, front course, intercept angle and scenery conflicts.
FSX will not capture the ILS localizer when the correct frequency is not active in NAV1, the guidance source remains GPS, approach mode is not armed, or the aircraft reaches the beam too fast, at too steep an angle or too late. Select NAV and arm APR before a shallow intercept.
This applies to Microsoft Flight Simulator X and FSX: Steam Edition, especially their default aircraft. Add-on avionics may use LOC, APP or APPR labels and may require an aircraft-specific arming sequence.
How do I set up localizer capture in FSX?
Successful capture requires the correct radio, navigation source, front course and intercept geometry to be established before the aircraft crosses the localizer.
- Verify the approach in FSX. Confirm that the exact runway end has an ILS or localizer and use the frequency stored in your installed simulator data. Base FSX navigation data is old, so present-day runway numbers, frequencies and procedures may not match.
- Tune NAV1 and make the frequency active. Entering the ILS in the standby window is not enough; transfer it to the active NAV1 window. Do not put it in NAV2 and expect a default autopilot to couple to it. Our guide to activating NAV1 and selecting its guidance explains the radio controls in more detail.
- Identify the localizer. If the panel provides navigation audio, select NAV1 audio and check the identifier. No identifier, flags on the instrument and no needle movement usually mean the receiver has not acquired the station.
- Select NAV rather than GPS. Move the NAV/GPS selector to NAV, or use the avionics source control that performs the same job. A flight plan can remain loaded; the critical point is that the CDI and autopilot must be taking guidance from NAV1.
- Set the front-course heading. Turn the OBS or course selector to the published inbound course. This does not tune the beam, and raw localizer sensing in many default panels does not depend on it, but it makes the HSI meaningful and is required by some add-on systems.
- Establish a controlled intercept. Use heading mode or hand-fly towards the localizer at about 20–30 degrees. Be configured, at a stable speed and far enough from the runway for the autopilot to complete the turn without overshooting.
- Arm the correct approach mode. With the autopilot engaged, select APR, APP or the aircraft’s equivalent before reaching the beam. A LOC mode captures lateral guidance only on avionics that provide it; APR or APP normally arms both localizer and glideslope capture.
- Confirm capture on the instruments. The CDI should move towards the centre, the mode indication should change from armed to active, and the aircraft should turn onto the inbound track. Exact annunciations vary by panel.
APR is needed for autopilot capture, not for receiving raw localizer indications while hand-flying. For the full procedure, including altitude management and final approach, follow our complete FSX ILS setup and flying sequence.
Why does FSX fly straight through the localizer?
Flying through a moving localizer needle means the radio is receiving the beam, but the autopilot was not correctly armed, was following another source, or could not complete the intercept in time.
| What you see | Likely cause | What to do |
|---|---|---|
| No localizer needle movement | Wrong or standby frequency, NAV2 used, out of range, avionics off or mismatched navigation data | Check active NAV1, listen for the identifier and verify the approach in FSX |
| Needle moves but the aircraft holds its heading | APR or LOC was not armed, the autopilot is off, or GPS remains the guidance source | Check the autopilot mode indication and select NAV as the source |
| Aircraft turns after crossing the beam | Approach mode was armed too late | Reposition and arm it before the needle reaches the centre |
| Aircraft overshoots and oscillates | Intercept was too steep, fast or close to the runway | Intercept earlier at roughly 20–30 degrees and stabilise the speed first |
| Aircraft turns the wrong way | Wrong runway end, reciprocal course or incorrect back-course setup | Confirm the front-course approach and make sure BC mode is not selected |
| A default aircraft works but an add-on does not | Aircraft-specific source selection or mode logic | Use that aircraft’s LOC or APP arming procedure |
Do not judge capture solely by the illuminated HDG button. On many panels, heading mode controls the intercept while approach mode waits in an armed state; the localizer mode takes control only as the CDI approaches the centre.
Does the ILS approach need to be loaded in the GPS?
No. In default FSX aircraft, localizer reception and autopilot capture do not require an approach to be loaded or activated in the GPS. The correct active NAV1 frequency and NAV guidance source are enough.
Loading the approach can help with situational awareness, but leaving GPS selected makes NAV mode follow the flight plan rather than the localizer. Advanced add-on aircraft may require an FMC approach to be selected as part of their own procedure.
Why is there no localizer needle movement?
A dead CDI is a reception or instrument problem, not an autopilot capture problem.
- Check that the ILS is in the active NAV1 window rather than standby or NAV2.
- Confirm that the avionics and electrical systems supplying the navigation receiver are powered.
- Verify that the runway end actually has an ILS in your installed FSX airport data.
- Move closer and approach the front side of the localizer. Reception may be unreliable when distant, behind the antenna or well outside the normal approach sector.
- Compare the station identifier with the intended approach. A matching-looking frequency alone does not prove that the correct facility is selected.
If a modern chart disagrees with FSX, use the simulator’s stored frequency unless an installed navigation-data or scenery package deliberately updates that airport.
Could this be a back-course localizer?
For a normal ILS, use the published front course and leave BC mode off; selecting back-course mode on a front-course approach can produce reversed or otherwise confusing steering.
A genuine localizer back-course procedure uses the signal from the opposite side and requires different autopilot logic. Our back-course setup and reverse-sensing explanation covers that special case.
How can I tell whether the aircraft or airport is causing the fault?
Comparing one default aircraft and one stock airport usually isolates an aircraft configuration problem from an airport or scenery problem.
- Keep the airport and change aircraft. Fly the same intercept with a default FSX aircraft. If it captures, the original aircraft’s avionics procedure or configuration is responsible.
- Keep the aircraft and change airport. Try a familiar ILS at another stock airport. If that works, check the original airport’s frequency, runway data and installed scenery.
- Test without conflicting airport scenery. Two packages defining the same airport can leave the runway and localizer in different positions. Disable the suspected package temporarily or correct its scenery priority, then repeat the same approach.
A centred CDI does not require the aircraft’s nose to point exactly along the runway. In a crosswind, the autopilot may hold a visible crab while maintaining the correct ground track. If the aircraft follows a line physically beside the runway with the CDI centred, suspect a genuinely offset localizer or mismatched airport scenery instead.
What if the localizer captures but the glideslope does not?
Localizer and glideslope capture are separate, so successful lateral capture does not prove that the vertical approach is set up correctly.
Remain at the published intercept altitude, approach the glideslope from below and ensure APR or APP—not a lateral-only LOC mode—is armed. Also confirm that the procedure is a full ILS rather than a localizer-only approach. Use our glideslope capture troubleshooting checklist if the aircraft tracks the centreline but will not begin descending.