Flight simulator ATC not recognising your ILS? Diagnose runway, navdata, flight-plan and receiver mismatches, then restore the correct approach clearance.
In a general flight simulator, ATC usually does not detect the radio signal your aircraft is receiving. It recognises an ILS from its own airport and navigation data, active-runway logic and ATC flight-plan state. A runway mismatch, an unfiled procedure or a skipped hand-off commonly prevents the expected ILS clearance.
Does ATC detect whether I have tuned the ILS?
No. Loading an ILS in the FMS or tuning its frequency does not normally notify built-in ATC. ATC selects and clears an approach from its database; your aircraft’s receivers then capture the localiser and glideslope independently.
Some simulators monitor your position to decide when you are established, but that is not the same as reading the NAV receiver. Our explanation of how built-in ATC turns route and runway data into clearances covers this separation in more detail.
| Symptom | Likely problem | Check first |
|---|---|---|
| ATC never offers the ILS or assigns another approach | ATC, flight plan or navdata | Active runway, IFR plan and procedure availability |
| ATC clears the ILS, but no localiser appears | Aircraft navigation setup | Frequency, active receiver and NAV source |
| Localiser captures, but glideslope does not | Intercept geometry or approach mode | Intercept from below and confirm APP is armed |
How do I fix an ILS approach ATC will not recognise?
- Confirm that the runway really has an ILS. An approach labelled LOC, localiser-only, RNAV or RNP is not a full ILS. One runway end having an ILS does not mean the opposite end has one, either. First verify the runway, frequency, course and approach type against reliable ILS data.
- Compare the scenery, ATC and avionics runway designations. These can use different databases. Add-on scenery may show a renumbered runway while built-in ATC or a third-party FMS still uses its former number. Select the designation recognised by ATC, update the conflicting data where supported, or temporarily remove the scenery or avionics add-on causing the mismatch.
- Put the approach into ATC’s flight plan. Programming the aircraft’s FMS alone may not update the separate route held by menu-driven ATC. File an IFR plan to the correct destination and select or request the intended approach where the simulator permits it. Remember that a STAR is an arrival route, not the approach itself.
- Check the active runway and ATC sequence. ATC may choose a different runway because of wind, airport configuration or its own simplified runway-selection logic. Listen to the airport information, contact each assigned controller and acknowledge the approach clearance. Skipping a frequency change or leaving an instruction unanswered can stall scripted ATC.
- Separate an ATC failure from an ILS capture failure. Once ATC has said you are cleared for the ILS, it has recognised the approach. If the needles remain absent, check the receiver and navigation-source requirements: use the active rather than standby frequency, select VLOC or NAV instead of GPS/FMS where required, and confirm the correct receiver is driving the instruments.
- Approach the glideslope from below. Being too high can prevent vertical capture even when the localiser works correctly. Arm approach mode before interception and avoid joining at an excessive angle. If lateral guidance works but vertical guidance does not, review localiser and glideslope capture logic.
- Reset a stuck ATC state. Request vectors or another approach if those options exist. Otherwise, cancelling and refiling IFR, reloading the flight, or temporarily disabling a replacement ATC add-on can reveal whether two systems are competing or the original clearance state has failed.
Why does ATC offer RNAV or a visual approach instead?
ATC offers another approach when its active runway or database does not make the ILS the preferred available procedure. Retuning the aircraft cannot change that selection.
- The wind favours a runway without an ILS.
- The airport database lacks the ILS or uses a different runway number.
- The planned approach was entered only in the aircraft, not in ATC’s route.
- The flight was filed VFR rather than IFR.
- The simulator’s built-in ATC uses simplified approach-selection logic.
- The selected procedure is localiser-only, despite appearing similar to an ILS in the list.
Where the ATC menu allows it, request the ILS or choose a different instrument approach before accepting the final clearance. If the option never appears, concentrate on the active runway and database mismatch rather than repeatedly changing the radio.
Can I fly the ILS if simulator ATC does not recognise it?
Yes, during an offline practice flight you can cancel or disregard built-in ATC and fly a valid ILS using the correct chart, frequency and intercept. Verify that the physical runway, navigation database and radio signal all agree before relying on the guidance.
During a session with live human controllers, request the ILS and wait for clearance instead of flying an unassigned procedure. If ATC has already issued an ILS clearance but the aircraft will not capture it, the fault is in the navigation setup or intercept—not ATC recognition.