VOR navigation not working in MSFS 2020? Fix inactive NAV frequencies, GPS/VLOC selection, reception, avionics power and autopilot capture.
VOR navigation in Microsoft Flight Simulator 2020 usually fails because the frequency is still in standby, the CDI is set to GPS, the receiver has no power, or the aircraft is outside line-of-sight range. Activate the correct NAV frequency, select VLOC/NAV, then confirm reception by hearing the station’s Morse identifier.
How do I make a VOR work in MSFS 2020?
The quickest fix is to check the receiver, signal and CDI source in that order.
- Verify the VOR and frequency. Use a station shown in the simulator’s World Map or aircraft navigation database. An old chart may list a VOR that has been decommissioned or assigned a different frequency.
- Switch on the avionics. Check the battery, alternator or generator and avionics master as appropriate for the aircraft. Some detailed add-ons also model electrical buses and circuit breakers.
- Tune the NAV radio. Enter the frequency in NAV1 or NAV2, not COM. If it appears in the standby window, press the frequency-transfer button to make it active.
- Select the matching CDI source. Choose NAV1, VOR1 or VLOC1 when using NAV1; choose the corresponding NAV2 source when using NAV2. A magenta GPS indication means the CDI is still following the flight plan rather than the VOR.
- Identify the station. Enable NAV1 or NAV2 audio and listen for the Morse identifier, or check the decoded identifier on glass avionics. No identifier, no TO/FROM indication and a NAV warning flag usually mean there is no valid signal.
- Set the course. Turn the OBS or CRS control until the desired course is selected. The CDI should move as the selected course changes.
- Intercept the radial. Fly a heading that crosses the selected course rather than expecting the needle to point directly towards the station.
If the instrument indications themselves are unfamiliar, our practical guide to tuning and interpreting VOR and NDB receivers explains CDI deflection, TO/FROM flags and station identification.
Why does the VOR needle stay centred or show an OFF flag?
A centred needle can be a valid course indication, but an OFF or NAV flag means the receiver does not have a usable signal.
| Symptom | Likely cause | What to check |
|---|---|---|
| NAV or OFF flag with no TO/FROM indication | No valid VOR signal | Active frequency, avionics power, range, altitude and terrain |
| Frequency displayed but nothing responds | Frequency remains in standby or the wrong receiver is selected | Transfer it to active and match NAV1/NAV2 to the CDI source |
| Magenta CDI follows the flight plan | GPS is selected | Change the CDI source to NAV/VOR/VLOC |
| Needle centred with a valid identifier and TO/FROM flag | Aircraft is on the selected course | No fault; confirm the OBS course and TO/FROM sense |
| Needle becomes unstable over the station | Cone of confusion | Continue through the station and expect the TO/FROM indication to change |
| VOR works but no distance appears | No paired DME or no DME receiver | DME is separate from the VOR course signal and is not available at every station |
A mistake we see constantly is treating the selected OBS course as a bearing pointer. VOR radials extend from the station. If an aircraft west of a station is flying east towards it, it is on the station’s westerly radial but normally selects an easterly inbound course.
Why is the G1000 showing GPS instead of the VOR?
The G1000 will ignore the tuned VOR for CDI guidance until its navigation source is changed from GPS to the appropriate NAV receiver.
Tune and activate the frequency in NAV1, press the CDI source control until NAV1 or VOR1 is shown, and set the course with the CRS control. Select NAV1 on the audio panel if you need to hear the Morse identifier. Labels vary slightly between avionics implementations, but the essential choice is GPS versus NAV1/NAV2.
If the frequency-transfer key, FMS knob or NAV fields do not respond, the radio problem may actually be an input-focus or control-binding fault. Follow our checks for unresponsive G1000 knobs and navigation fields before changing the flight plan or reinstalling the simulator.
Why won’t the autopilot track the VOR?
The autopilot will track a VOR only when the CDI is using that NAV receiver and the aircraft is positioned to capture the selected course.
- Select NAV1 or NAV2 as the CDI source. If GPS remains selected, NAV mode follows the programmed flight plan instead.
- Set the intended OBS course. Confirm that the CDI, TO/FROM indication and station identifier are sensible.
- Intercept using heading mode. Approach the course at a reasonable angle rather than flying parallel to it or engaging NAV with full-scale deflection.
- Arm NAV mode. Watch the autopilot mode annunciation to confirm that NAV changes from armed to captured.
Engaging NAV does not command an immediate turn directly towards the VOR. Capture logic varies by aircraft, and some autopilots will not capture a course when the CDI is fully deflected, the intercept angle is excessive or the aircraft is already flying away from the selected course. Use NAV rather than an approach mode for ordinary en-route VOR tracking.
Can a VOR be missing or out of range?
A correctly configured receiver can still show no signal when the station is absent from the simulator’s navigation data or blocked by distance, low altitude or terrain.
VOR reception is primarily line of sight. Climbing may restore reception, while mountains can block a station that appears close on the map. Each station also has a defined service volume, so receiving a distant high-altitude VOR does not prove that every station should work at the same distance.
Navigation databases change as real-world VORs are removed or frequencies are revised. If an external chart disagrees with Microsoft Flight Simulator 2020, test a station and frequency shown inside the simulator. Conflicting third-party navigation-data packages can also create mismatches between the World Map and cockpit avionics.
What should I test if every VOR has stopped working?
A controlled flight in a stock aircraft will separate a simulator-wide failure from an aircraft, add-on or controller problem.
- Choose a known station. Start roughly 10–20 NM from a VOR displayed on the World Map, at a safe altitude with clear terrain.
- Use a default aircraft. A stock aircraft with a conventional NAV receiver or G1000 removes custom-avionics variables.
- Set NAV1 manually. Activate the frequency, select NAV1/VOR1 as the CDI source and verify the identifier.
- Disable interference. On PC, temporarily move third-party packages out of the
Communityfolder and restart the simulator. Pay particular attention to avionics and navigation-data add-ons. - Check assistance features. AI piloting or radio assistance may retune radios or alter navigation behaviour; review the MSFS navigation assistance settings.
- Inspect controller assignments. Duplicate bindings can repeatedly swap frequencies, turn the OBS or change the CDI source. Our MSFS 2020 control troubleshooting steps cover profile conflicts and unintended inputs.
If the stock aircraft receives the test VOR, the simulator’s basic navigation system is working. Re-enable aircraft, avionics and navigation-data add-ons one at a time until the failure returns; that identifies the conflicting package without disturbing the whole installation.