Why am I not receiving VOR signals in Microsoft Flight Simulator?
If you are not receiving VOR signals in Microsoft Flight Simulator, the usual cause is not a broken VOR at all. In most cases the aircraft’s NAV radio is not tuned correctly, the frequency is still in standby, the CDI source is set to GPS instead of NAV1/NAV2, or you are simply too low or too far away for line-of-sight reception.
What usually causes missing VOR signals in MSFS?
VOR navigation in Microsoft Flight Simulator behaves much like the real thing: it depends on the correct radio, the correct source selection, and sensible geometry between your aircraft and the station. Unlike GPS, VOR is not global coverage. You can lose it because of setup errors, terrain shielding or range.
When simmers say they are “not getting a VOR signal”, they usually mean one of four things:
- The VOR frequency is not actually active on NAV1 or NAV2.
- The display is following GPS/FMS instead of a radio navigation source.
- The aircraft is outside the VOR’s usable range or below line of sight.
- The particular aircraft or avionics suite is not configured the way they expect.
How do I fix no VOR reception in Microsoft Flight Simulator?
- Make sure the avionics are powered. Turn on battery, alternator or generators as appropriate for the aircraft, then confirm the radio stack or glass cockpit is alive. In some aircraft the screens are on but parts of the nav system still need separate avionics or bus power.
- Tune the correct VOR frequency. Enter the station frequency into NAV1 or NAV2, not COM. A very common mistake is tuning the right number into the wrong radio.
- Swap standby to active. Many aircraft show a standby frequency and an active frequency. If you type the VOR into standby but never swap it across, the receiver will still be listening to the old active station.
- Select NAV1 or NAV2 as the CDI source. If the CDI, HSI or PFD is set to GPS, FMS or LNAV, the VOR needle may appear dead even with a valid station tuned. Use the CDI source button or avionics control to change to NAV1 or NAV2.
- Set the correct course. Rotate the OBS or CRS selector to the radial or inbound course you want to track. You can still receive a VOR without the ideal course set, but an incorrect OBS setting often makes the display look wrong and leads people to think there is no signal.
- Check your distance, altitude and terrain. VOR is line-of-sight radio navigation. Mountains, very low altitude and long distance can all block reception. Climbing a few thousand feet often brings the station alive immediately.
- Confirm the station is a VOR, VORTAC or VOR/DME. Not every navaid on the chart or map is a VOR. Some are NDBs, localisers or fixes only. If you tune a non-VOR frequency expecting a VOR indication, nothing useful will happen.
- Listen for or display the Morse ident. If your aircraft supports navaid identification, use it. No ident usually means no valid reception, wrong frequency, or being out of range.
- Try another aircraft. If one add-on aircraft behaves oddly, test the same station in a default aircraft with straightforward avionics. That quickly tells you whether the issue is your procedure, the location, or the aircraft.
- Restart the flight if the avionics have glitched. MSFS occasionally loads aircraft or avionics in a bad state, especially after rapid aircraft changes, saved flights or heavy add-on combinations.
Why is the VOR frequency tuned but the needle still does nothing?
This is nearly always a source selection problem. In glass cockpit aircraft, the PFD can be driven by GPS even while a VOR is tuned and receiving in the background. The radio is working, but the instrument you are watching is not displaying it.
Look for a CDI or source indicator on the PFD or HSI. If it says GPS, FMS or something similar, switch it to NAV1 or NAV2. On older steam-gauge aircraft, check whether you are looking at the indicator tied to the same NAV receiver you tuned.
VOR range and line of sight in Microsoft Flight Simulator
VOR coverage is not unlimited. Even in the simulator, you can be too low behind terrain or simply too far from the transmitter. A station that works perfectly at cruise altitude may not be receivable at circuit height dozens of miles away.
If you are flying in mountainous areas, this matters even more. The signal does not bend over ridges just because the moving map shows the navaid nearby.
| Symptom | Most likely cause | What to check |
|---|---|---|
| Frequency tuned, no needle movement | CDI source still on GPS/FMS | Switch display source to NAV1 or NAV2 |
| No ident, no DME, no VOR guidance | Wrong radio or wrong active frequency | Confirm NAV radio, then swap standby to active |
| Signal appears only after climbing | Line-of-sight limitation or terrain shielding | Increase altitude and check distance |
| One aircraft works, another does not | Aircraft-specific avionics setup | Review that aircraft’s NAV source and electrical system |
| Needle behaves oddly near overhead | Normal VOR cone of confusion | Expect unstable indications over the station |
Common MSFS-specific gotchas
GPS overrides radio navigation
This catches a lot of people in both Microsoft Flight Simulator 2020 and 2024. You may have a flight plan loaded, and the avionics quietly remain in GPS mode. The autopilot and HSI then ignore the VOR until you explicitly switch to a NAV radio source.
Assistance settings or flight setup confusion
If you spawn on an approach or load a route with avionics already configured, the sim may preselect navigation sources in ways you did not expect. We always recommend checking the active source before assuming the navaid is faulty.
Add-on aircraft behave differently
More advanced aircraft often simulate real electrical buses, radio control heads, transfer switches and navigation logic in more depth than default aircraft. If the VOR works in a simple trainer but not in a complex add-on, the issue is often aircraft setup rather than the simulator’s navaid database.
Can a VOR be out of service in MSFS?
Yes, sometimes the underlying nav database, a scenery conflict or an airport/navdata issue can cause unexpected behaviour. That said, a genuinely broken VOR in MSFS is far less common than user setup issues.
If you suspect a database problem, test several known VORs in different regions. If none of them work, the problem is almost certainly your radio, source selection or aircraft state. If only one station fails while others are fine, that individual navaid may be the issue.
What about DME, OBS and TO/FROM flags?
These are related, but they are not the same as basic VOR reception.
- DME may not be available at every VOR. A VOR can work without distance information if it is not paired with DME.
- OBS/CRS setting affects how the needle centres and what radial/course you are tracking. A bad course selection can make the indication confusing, but it does not usually stop reception altogether.
- TO/FROM indications can disappear or become unreliable when you are very close to, or directly over, the station.
Why does the VOR work in one aircraft but not another?
Because not all aircraft present NAV data the same way. In a basic Cessna with analogue gauges, the linkage between NAV1 and the indicator is usually obvious. In a modern glass cockpit aircraft, you may have multiple screens, source selectors, reversionary modes and autopilot coupling options.
In airliners and higher-fidelity add-ons, the VOR may be received correctly while the displayed guidance is filtered through a different system page or mode logic. If you can, test with a simple aircraft first. Once you know the station is working, move back to the more complex cockpit.
Quick VOR troubleshooting checklist
- Battery and avionics power on
- Correct NAV frequency, not COM
- Standby frequency swapped to active
- CDI/HSI source set to NAV1 or NAV2, not GPS
- Correct instrument selected for the tuned radio
- OBS/course set sensibly
- Within range and high enough for line of sight
- Not expecting DME from a non-DME station
- Test the same VOR in a simple default aircraft
If nothing fixes it
If you have checked power, tuning, source selection and range, try another aircraft and another VOR before digging deeper. That narrows the fault quickly. If the problem follows one specific aircraft, treat it as an aircraft setup issue; if it follows one specific station, suspect the navaid or local scenery data.
For aircraft guides, navigation tutorials and simulator downloads, our Microsoft Flight Simulator library is here: https://flyawaysimulation.com/downloads/.