Fix FSX ILS localizer capture problems: check NAV1 tuning, NAV/GPS source, APR mode, intercept angle, back course and scenery alignment.
FSX usually fails to capture the ILS localizer because NAV1 has the wrong or standby frequency, GPS is still the navigation source, APR mode is not armed, or the intercept is too steep or too late. Select the front-course ILS, switch to NAV, and intercept it shallowly with APR armed.
This applies to FSX and FSX: Steam Edition, particularly their default aircraft. Add-on avionics may label the modes LOC, APP or APPR and may require a different arming sequence.
How do I set up localizer capture in FSX?
- Confirm that the runway has an ILS. Check the approach and frequency in your installed simulator data. FSX uses legacy navigation data, so a present-day real-world chart may show a frequency or procedure that does not match the simulator.
- Tune the frequency into NAV1. Transfer it from the standby window into the active window. If the panel supports navigation audio, identify the station rather than assuming the displayed frequency is correct.
- Select NAV as the source. Move the NAV/GPS selector to NAV. A GPS route or magenta course can remain visible while the autopilot is following GPS rather than listening for the localizer.
- Set the published inbound course. Raw localizer sensing comes from the tuned frequency, but setting the front course gives a sensible display and is required by some add-on avionics. Do not select BC for an ordinary front-course approach.
- Establish a shallow intercept. Use heading mode or hand-fly towards the localizer at roughly 20–30 degrees. Join far enough from the runway for the needle to become active; do not fly parallel to the beam or wait until after crossing it.
- Arm approach mode. Select APR, APP or LOC as appropriate for the aircraft. On many default panels, heading mode continues commanding the intercept until the localizer captures.
- Watch the mode and CDI. As the needle centres, the autopilot should turn onto the inbound course and the localizer mode should become active. Hold the assigned altitude until glideslope capture if flying the complete ILS.
For the complete sequence from tuning through landing, see our step-by-step FSX ILS procedure. A mistake we see constantly is arming APR with the aircraft already crossing the beam at a large angle.
Why does FSX pass straight through the localizer?
Passing through an active localizer normally means the autopilot was not armed to capture it, the wrong navigation source was selected, or the intercept geometry exceeded what the aircraft could manage.
| Symptom | Likely cause | What to check |
|---|---|---|
| No localizer needle movement | Wrong frequency, NAV1 still on standby, out of range or avionics off | Active NAV1 window, station identifier and avionics master |
| Needle moves but aircraft holds its heading | APR/LOC not armed or GPS remains selected | Autopilot annunciations and NAV/GPS selector |
| Aircraft overshoots and oscillates | Intercept too steep, too fast or too close to the runway | Reposition for an earlier, shallower intercept |
| Needle gives reversed or confusing commands | Wrong runway end, reciprocal localizer or back-course setup | Front-course frequency, inbound course and BC mode |
| One aircraft fails but a default aircraft works | Add-on avionics or aircraft configuration | Aircraft-specific source and approach-mode procedure |
If interception is the sticking point, our explanation of how to join and track a localizer without overshooting covers the geometry in more detail.
Why is the CDI centred but the aircraft is not pointing at the runway?
A centred CDI with the nose angled slightly away from the runway is usually a normal crosswind crab, not a localizer fault. The localizer controls the aircraft’s ground track; the heading must differ from the runway course when wind is pushing the aircraft sideways.
If the aircraft tracks a line physically beside the runway while the CDI remains centred, that is different. The airport may have a genuinely offset localizer, or add-on scenery may place the runway and navigation aid inconsistently. Use our checks for an off-centre FSX localizer to distinguish a valid offset approach from a scenery conflict.
How can I tell whether the aircraft or airport is faulty?
A short comparison test identifies most remaining FSX localizer problems.
- Fly the same approach with a default aircraft. If it captures correctly, the add-on aircraft’s avionics procedure or configuration is responsible.
- Try a known ILS at a different stock airport. If only one airport fails, suspect its frequency, runway data or add-on scenery.
- If every aircraft and airport fails, recheck NAV1 activation, the NAV/GPS source and the autopilot mode before changing simulator files.
- If scenery is involved, check its priority and look for two airport packages defining the same location.
What if the localizer captures but the glideslope does not?
Localizer and glideslope capture are separate events. If lateral guidance works, NAV1 tuning and the navigation source are probably correct; the usual remaining causes are joining above the glideslope, failing to arm APR, or using an aircraft that does not support automatic vertical capture. Follow our FSX glideslope capture checklist rather than retuning a localizer that is already working.