Why won't simulator ATC recognise your ILS? Diagnose missing approach offers, silent ATC, failed capture and Fenix A320 NO NAV INTERCEPT.
In a general flight simulator, first separate three faults: if ATC will not offer an ILS, check the IFR plan, active runway and navigation data; if ATC is unavailable, check radios, audio and the ATC service; if a cleared ILS will not capture, check aircraft tuning, source, approach mode and intercept geometry.
Which part of the ILS sequence has failed?
ATC clearance, radio reception and autopilot capture are separate stages. A mistake we see constantly is treating any failure during an approach as an ATC problem.
| Symptom | System to troubleshoot | First check |
|---|---|---|
| ATC never offers the ILS | ATC plan, runway or navigation data | IFR plan, active runway and procedure availability |
| There is no ATC menu, response or audio | Communications or ATC service | ATC availability, active COM frequency and audio selection |
| ATC clears the ILS, but no localiser appears | Aircraft navigation setup | Frequency, receiver, navigation source and approach mode |
| Localiser captures, but glideslope does not | Procedure type or intercept geometry | Confirm a full ILS and intercept the glideslope from below |
Fenix displays NO NAV INTERCEPT | FMGS route geometry | Active leg, discontinuities and waypoint position |
Does ATC detect whether I have tuned the ILS?
No. Built-in simulator ATC does not normally determine your requested approach by reading the ILS frequency or approach selected in the aircraft. ATC and the aircraft's navigation receivers are usually separate systems.
ATC can clear an ILS before you tune it, while the aircraft can receive and follow an ILS without an ATC clearance. Programming the approach in an MCDU, FMS or EFB also does not necessarily add it to the simulator's ATC flight plan.
How do I fix an ILS approach that ATC will not recognise?
- Confirm that the assigned runway actually has the expected ILS. Opposite runway ends may have different facilities, and 27L, 27C and 27R are separate runways. Check that the published procedure is a full ILS rather than RNAV, RNP, localiser-only or a visual approach.
- Give the simulator ATC its own IFR flight plan. A route entered only in the aircraft may not reach built-in ATC. Load or send an IFR plan through the simulator's planning system where required, with the correct destination and approach. Our guide to setting up an IFR flight and keeping the ATC and FMS plans aligned explains this separation. A STAR is an arrival route, not an ILS approach.
- Check which runway ATC considers active. Wind, airport configuration and simplified runway-selection logic may make ATC favour another runway. Request the desired approach if that option is available. Retuning the ILS cannot change ATC's runway choice.
- Compare the runway names in the scenery, ATC and avionics. Runways are periodically renumbered as magnetic headings change. Older scenery or navigation data may use the former designation while the aircraft uses the new one. Test without replacement airport scenery if the mismatch began after installing it; our checks for incorrect simulator ATC instructions and data conflicts cover the other common causes.
- Complete every hand-off and acknowledgement. Scripted ATC can stall when an instruction remains unanswered, a frequency change is skipped or the wrong controller is selected. An approach clearance and a landing clearance are also different instructions.
- Reset a stuck ATC sequence. Request another approach or vectors if the simulator offers those options. Otherwise, cancel and refile IFR or reload the flight. If an ATC add-on is installed, do not let it and built-in ATC control the same flight simultaneously.
Why does ATC offer RNAV or a visual approach instead?
ATC offers another approach when its selected runway or database does not make the ILS the preferred available procedure. That decision does not prove the aircraft's ILS receiver has failed.
- The wind favours a runway without an ILS.
- The airport database lacks the ILS or uses another runway designation.
- The flight was filed VFR rather than IFR.
- The intended approach exists only in the aircraft's flight plan.
- The runway has RNAV, RNP or localiser guidance but no full ILS.
- The simulator uses simplified approach-selection logic.
Do not accept an RNAV clearance and assume it includes permission to substitute an ILS. The lateral guidance, vertical guidance and minimums are not interchangeable.
There is no ATC at all - what should I check?
If there is no ATC menu, text, voice or controller response, troubleshoot the communication system before the ILS. A missing approach procedure cannot silence every ATC facility.
- Confirm that the selected ATC service is enabled and available for the flight.
- Make sure the aircraft has electrical power and its COM radios are operating.
- Place the required frequency in the active window rather than standby.
- Select the correct transmit and receive channel on the audio panel and raise its volume.
- Contact the correct facility from a plausible radio range.
- Check whether text appears without speech. That points to an audio or voice setting, not an ILS fault.
- Do not assume multiplayer traffic includes human ATC. Multiplayer, built-in ATC and controller services are separate features.
- Test the same airport in a default aircraft. Failure in both aircraft suggests a simulator or ATC configuration issue; failure only in the add-on points towards its power, radio or audio state.
Why is iniBuilds A350 ATC not working?
With the iniBuilds A350 in Microsoft Flight Simulator, first determine whether ATC itself is missing or the aircraft is merely failing to capture a cleared approach. Changing autopilot modes cannot restore an absent ATC service.
- No IFR clearance or approach is offered: make sure the simulator holds an IFR flight plan. A route loaded only in the A350 avionics or EFB may remain separate.
- The cockpit ATC page does nothing: an aircraft datalink or ATC page is not automatically the interface for built-in voice or menu-driven ATC.
- ATC text appears without sound: inspect simulator voice settings, COM volume and the audio-panel receive selection.
- You cannot transmit: verify that the controller frequency is active and the intended VHF radio is selected for transmission.
- ATC clears the ILS but no guidance appears: ATC has recognised the approach. Check the selected procedure, ILS tuning, displayed identifier where modelled, approach mode and flight-mode annunciator.
ATC cleared the ILS, but the aircraft will not capture it
Once ATC has issued an ILS clearance, the recognition problem is over. Missing localiser or glideslope guidance is now an aircraft setup, signal or intercept problem.
- Verify the exact runway and procedure. Confirm that the frequency and front course belong to the cleared runway and that the procedure includes a glideslope.
- Check the active receiver. The frequency must be active rather than in standby, and the correct NAV receiver must drive the flight instruments.
- Select the correct navigation source. Aircraft with a GPS or FMS versus NAV or VLOC selector normally need the radio-navigation source for ILS capture.
- Display and identify the signal. Look for localiser and glideslope scales and, where modelled, confirm the ILS identifier. Displaying the scales alone does not arm the autopilot.
- Arm LOC or APPR and read the FMA. A lit pushbutton only confirms that a mode was requested. The flight-mode annunciator shows whether the localiser and glideslope are armed or captured.
- Correct the intercept geometry. Join the localiser at a moderate angle and intercept the glideslope from below. ATC vectors that leave the aircraft too close, too high or on the wrong side of the localiser may make capture impossible.
If you need the complete setup and capture sequence, use our practical ILS procedure covering tuning, source selection and intercept geometry. If no aircraft receives a correctly configured ILS at that airport, suspect missing or displaced scenery data rather than the autopilot.
Why does the Fenix A320 show NO NAV INTERCEPT?
In the Fenix A320, NO NAV INTERCEPT normally means the FMGS cannot construct or capture the requested managed route from the aircraft's present position. It is not confirmation that ATC rejected the approach or that the ILS transmitter has failed.
What does Airbus NAV mode do?
Airbus NAV is the managed lateral mode that follows the route held in the FMGS. Pulling the heading selector uses selected HDG; pushing it requests managed NAV when a valid route leg can be captured.
NAV does not capture an ILS by itself. The LOC pushbutton arms localiser capture only, while APPR arms the localiser and glideslope for a full ILS. The LS pushbutton displays the landing-system scales and information but does not arm either capture mode.
Fenix A320: NO NAV INTERCEPT is not an ILS or ATC error
The message concerns managed-route geometry. It can appear after a direct-to, an impossible inbound-course entry, a route discontinuity or incorrect sequencing into the missed approach. An ATC clearance does not repair those FMGS conditions.
Before ILS capture, the FMA should show the active lateral mode, such as HDG or NAV, in green, with LOC armed in blue. When APPR is armed for a valid ILS, G/S should also appear armed in blue. During capture, LOC* changes to green LOC, followed by G/S* and green G/S. The APPR button light alone is not proof of capture.
How do I recover from NO NAV INTERCEPT in the Fenix A320?
- Use selected heading while diagnosing the route. Pull the heading selector and fly an appropriate cleared heading. The FMA should show
HDGas the active lateral mode. Do not keep pushing for managed NAV while the FMGS has no capturable leg. - Identify the active leg. On the MCDU F-PLN page and navigation display, find the waypoint the FMGS is actively trying to reach and the leg leading to it. Do not assume that a waypoint visible farther down the approach is already active.
- Inspect and clear route discontinuities correctly. Scroll from the active leg through the arrival and approach. If
F-PLN DISCONTINUITYblocks a route that should be continuous, insert the missing waypoint or use the MCDU clear function to remove the discontinuity. Do not erase an intentional vector or manual leg; remain inHDGuntil cleared to a suitable fix. - Check whether missed-approach legs are active. If the FMGS has sequenced beyond the landing runway into the missed approach when you intend to continue the approach, reselect or rebuild the correct arrival and approach, or use a direct-to to a cleared approach fix ahead. If you are genuinely going around, keep the missed-approach route and follow the clearance.
- Select a valid waypoint ahead. Choose a waypoint clearly forward of the aircraft and in the intended route sequence. A direct-to behind or abeam the aircraft can demand an excessive turn or produce geometry that NAV cannot intercept.
- Create an intercept in selected HDG. Turn so the projected aircraft track crosses the active FMGS leg before its end, preferably at a moderate angle rather than parallel to it. If an entered inbound course points away from the leg or never crosses it, cancel that entry and use heading mode to establish workable geometry.
- Re-engage managed NAV only when the leg is capturable. Push the heading selector once the active waypoint is ahead and the aircraft's track will intersect the active route.
NAVshould appear armed in blue and then active in green; it may become active directly when the aircraft is already close to the path. IfNO NAV INTERCEPTreturns, stay inHDGand rebuild or reselect the leg. - Use APPR for the ILS. When cleared and positioned to intercept the localiser, display the LS information and arm
APPR. Do not wait for managed NAV to capture the localiser. Our A320 ILS mode and FMA sequence covers the remaining approach steps.
Which common Fenix trigger applies?
| Trigger | What has happened | Correct response |
|---|---|---|
| Direct-to behind or abeam | The chosen fix requires a reversal or gives poor forward geometry | Use HDG, then select a valid fix ahead |
| Inbound course misses the active leg | The entered course is parallel to, points away from or never crosses the leg | Remove the impossible course or use HDG to make a real intercept |
| Route discontinuity | The FMGS has no continuous managed leg to follow | Insert the missing fix, clear a valid discontinuity or fly the vector in HDG |
| Missed-approach leg left active | The FMGS is following the go-around sequence instead of the landing approach | Restore the correct approach leg unless a go-around is intended |
| NAV used to capture the ILS | Managed routing has been confused with radio localiser capture | Use LOC for lateral-only capture or APPR for the full ILS |
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 runway, frequency, course, navigation source and intercept. The aircraft does not need ATC recognition to receive the localiser and glideslope.
Do not self-clear an approach when flying with live human controllers. Request the ILS and wait for clearance. Remember that approach clearance permits the approach procedure; it is not the same as landing clearance.
Miscellaneous error strings
Does dbyjaathc identify an ATC or ILS fault?
No. dbyjaathc is not a standard ILS mode, Airbus FMA indication or recognised simulator ATC error. It may be a callsign, username, truncated log entry or mistyped term. Record where it appeared and the complete surrounding message rather than treating it as an ILS frequency, procedure identifier or autopilot mode.