DCS World ILS not working? Check aircraft compatibility, runway activation, frequency, cockpit mode and intercept geometry with this fault checklist.
ILS usually fails in DCS World because the aircraft cannot receive that beacon type, the wrong runway or frequency is selected, the receiver is unpowered, or the approach is intercepted outside the localiser and glideslope coverage. Confirm aircraft compatibility and runway data first, then test from the front course below the glideslope.
Can your DCS aircraft receive that type of ILS?
DCS World models the navigation equipment fitted to each aircraft, so an ILS frequency is useless unless the module has a compatible receiver. A mistake we see constantly is treating shore-based ILS, Russian PRMG and carrier ICLS as interchangeable systems.
| Approach aid | What the aircraft needs | Common mistake |
|---|---|---|
| Conventional land ILS | A compatible ILS or landing receiver | Entering the frequency in a communications radio instead of the dedicated navigation receiver |
| PRMG | Compatible Soviet or Russian landing equipment | Trying to tune it as a Western civil ILS frequency |
| Carrier ICLS or ACLS | Compatible naval equipment and a correctly configured carrier transmitter | Assuming a carrier channel is equivalent to a shore ILS frequency |
| No compatible receiver | No conventional ILS approach is possible | Repeatedly retuning a system the aircraft does not carry |
The DCS F/A-18C, for example, uses ICLS for carrier approaches and does not have a conventional land-based ILS receiver. An airport may therefore have a valid ILS that the Hornet cannot display. Check the module manual rather than assuming every modern cockpit supports every landing aid.
How do I troubleshoot a missing ILS signal?
Work through these checks in order, because changing several cockpit settings at once often hides the actual fault.
- Verify the runway equipment. Confirm that the DCS terrain models an ILS for the runway end you are approaching. An airport's present-day real-world chart does not prove that the terrain's represented version has the same equipment. The mission briefing, kneeboard and our guide to checking airfield information on the F10 map can help confirm the destination, runway direction and listed navigation aids.
- Use the ILS frequency, not the ATC frequency. ATC, tower and approach frequencies belong in communications radios. Enter the listed ILS frequency in the aircraft's dedicated ILS or navigation receiver, using the module's required entry format.
- Power the complete system. Check electrical power, the receiver's power or volume control, the appropriate navigation panel and any required avionics switches. Hearing a Morse identifier can confirm reception in modules that model it, but silence alone is not definitive because implementation differs between aircraft.
- Select the correct display mode. Tuning the frequency may not automatically place ILS guidance on the ADI, HSI or HUD. Select the aircraft's ILS, landing or appropriate navigation mode, and distinguish raw localiser and glideslope indications from flight-director command bars.
- Set the published front course. The course selector normally does not switch the transmitter on, so it is unlikely to explain a receiver warning flag. It can, however, make otherwise valid steering information confusing or reversed if set to the reciprocal heading.
- Intercept from valid geometry. Approach the front of the runway on or near its extended centreline, use a modest intercept angle and remain below the glideslope until capture. Capture the localiser first, then the glideslope. Approaching from behind the antenna, starting too high or joining very close to the runway can leave the needles unusable.
- Check for unintended control inputs. Duplicate axis, switch or keyboard assignments can change the course, frequency or navigation mode without an obvious warning. If cockpit controls move by themselves, audit your HOTAS and joystick bindings before reinstalling anything.
If the fault occurs only in a community aircraft, disable that aircraft and test a stock module. Then check the mod installation and its dependencies; an outdated cockpit script can break navigation displays even though the terrain beacon is working.
For a stock module, ensure the simulator is on a consistent build by bringing DCS World up to date, then use the installation's repair function if files may be damaged. Reinstallation should be a last step, not the first.
What do the ILS needles and warning flags reveal?
The instrument behaviour usually narrows the fault to reception, approach geometry or flight-director configuration.
| Symptom | Most likely causes | What to check |
|---|---|---|
| Localiser and glideslope both absent | Incompatible aircraft, wrong frequency, receiver unpowered or inactive transmitter | Aircraft equipment, runway data, receiver power and active runway |
| Localiser works but glideslope does not | Aircraft above the beam, too close to capture it or runway without a modelled glideslope | Descend below the expected path and retry farther out |
| Needle is alive but at full deflection | The signal is being received, but the aircraft is outside the approach course | Position relative to the runway centreline and selected course |
| Guidance appears reversed | Approach from the rear or reciprocal course selected | Published inbound course and runway end |
| Raw needles work but autopilot will not capture | Incorrect flight-director or autopilot mode sequence | Module-specific capture procedure; this is not an ILS reception failure |
Why does the ILS work from only one runway direction?
An ILS normally serves one runway end, and DCS does not guarantee a usable back-course approach from the reciprocal direction. Select the equipped front-course runway unless the mission documentation explicitly provides another procedure.
Some DCS airfields also apply active-runway logic based on mission wind and runway selection. A transmitter listed in the terrain data may appear silent when the opposite runway is active. Follow the assigned runway, inspect the mission wind and remember that the direction used by a weather editor may describe where the wind is coming from or going to differently from the cockpit display.
Does contacting DCS ATC activate the ILS?
Contacting ATC does not tune or power the aircraft's ILS receiver. ATC's runway assignment is still useful because it indicates the expected landing direction, but the navigation receiver must be configured separately.
Carrier approaches are a separate case: the mission creator may need to assign and activate the ICLS or ACLS channel through the carrier's mission settings. If every aircraft in a multiplayer mission loses the same carrier signal, suspect mission configuration before changing individual cockpits.
How can I isolate an aircraft or mission problem?
A controlled single-player approach is the quickest way to separate cockpit error from a broken or unsuitable mission setup.
- Use a stock aircraft known to carry conventional ILS equipment.
- Choose a runway that the DCS terrain explicitly lists as ILS-equipped.
- Start several miles out on the front course, aligned with the runway and below the expected glideslope.
- Use clear weather and make that runway the logical landing direction.
- Tune, identify and display the ILS without engaging the autopilot.
If raw localiser and glideslope indications work there, the simulator and receiver are functioning; return to the original mission and check its runway, wind, beacon type and carrier actions. If they remain absent in a clean stock setup, recheck the module procedure, remove input conflicts and repair the installation.