Why is VOR not working in Microsoft Flight Simulator?
Fix a dead VOR in Microsoft Flight Simulator by checking NAV tuning, CDI source, avionics power, station range, ident and aircraft-specific setup.
In Microsoft Flight Simulator, a VOR usually appears not to work because the frequency is in COM or standby, the CDI/HSI is still using GPS/FMS, or the aircraft is outside line-of-sight range. Power the avionics, activate the frequency on NAV1 or NAV2, select that NAV source, and verify the station ident.
What usually causes VOR not working in MSFS?
Most VOR failures in Microsoft Flight Simulator are tuning, source-selection or reception problems rather than broken navigation beacons.
- Wrong receiver: VOR and localiser frequencies use a NAV receiver, not COM. An NDB requires ADF equipment instead.
- Frequency left in standby: seeing the correct number on the radio does not mean it is active.
- Wrong CDI source: a receiver can be tuned correctly while the HSI continues displaying GPS or FMS guidance.
- NAV1/NAV2 mismatch: you may have tuned NAV2 while watching an indicator connected to NAV1.
- No valid reception: VOR is line-of-sight radio navigation, so distance, low altitude and terrain can block the signal.
- Wrong facility type: a localiser, NDB, waypoint or map fix does not provide normal VOR radials.
- Aircraft limitation: some aircraft lack a conventional NAV receiver, while others require additional electrical or avionics switches.
If the difference between radials, inbound courses, OBS settings and TO/FROM indications is unclear, see our explanation of using VOR and NDB beacons in a flight simulator.
| Symptom | Likely cause | First check |
|---|---|---|
| Correct frequency visible but no guidance | Frequency still in standby or CDI on GPS/FMS | Swap it to active and select NAV1 or NAV2 |
| Morse ident heard but CDI remains dead | Wrong display or navigation source | Match the HSI/CDI source to the tuned receiver |
| NAV flag displayed and no ident received | No valid signal, no power or wrong frequency | Check power, active frequency, altitude and range |
| Signal appears after climbing | Terrain shielding or radio horizon | Remain within the station's usable coverage |
| Needle becomes unstable over the station | Normal cone of confusion | Expect temporary unreliable indications overhead |
| VOR works but DME is blank | Station or aircraft lacks DME capability | Confirm that both the facility and aircraft support DME |
How do I fix no VOR reception in Microsoft Flight Simulator?
The fastest reliable test is to check the aircraft from power supply through to the displayed navigation source.
- Confirm the station: choose a known VOR, VOR/DME or VORTAC from the navigation data loaded in the simulator. A frequency taken from an old chart or video may refer to a renamed, changed or decommissioned facility.
- Power the receiver: switch on the battery, alternator or generators and the relevant avionics master. More detailed aircraft may place radios and displays on separate electrical buses. If the radio stack or displays are dark, work through our electrical, brightness and add-on checks for blank avionics screens first.
- Tune NAV1 or NAV2: enter the VOR frequency into a NAV receiver. Do not use COM, and do not use ADF unless the facility is an NDB.
- Make the frequency active: use the transfer control to swap the frequency from standby. The receiver listens only to the active side.
- Select the matching source: set the CDI or HSI to NAV1 if NAV1 is tuned, or NAV2 if NAV2 is tuned. A GPS or FMS indication means the display is following satellite navigation rather than the VOR.
- Use the correct instrument: analogue aircraft often have fixed NAV1 and NAV2 indicators. Glass cockpits can have independent pilot-side sources, bearing pointers and course-deviation sources.
- Set OBS or CRS: select the intended radial or inbound course. The OBS setting does not determine whether the radio receives the beacon, but the wrong course can produce confusing left/right and TO/FROM indications.
- Check the ident: enable NAV audio on the audio panel and raise the NAV receiver volume if necessary. A valid Morse ident is strong evidence that the receiver has the station. No audible ident alone is not conclusive because NAV audio may be deselected or unsupported by that aircraft.
- Climb or move closer: test from an altitude clear of surrounding terrain and comfortably inside the station's coverage. Reception on the ground or behind a ridge is not a useful test.
- Retest in a basic aircraft: use a default trainer with straightforward analogue instruments or a familiar glass cockpit. If that aircraft receives the same VOR, the beacon works and the original aircraft has a configuration or systems issue.
Why is the VOR tuned but the needle still dead?
A tuned VOR with a motionless CDI most often means the indicator is displaying the wrong navigation source.
On a glass cockpit, look for a source label such as GPS, NAV1 or NAV2. Change it to the receiver you tuned. A bearing pointer is separate from the main CDI, so seeing a pointer towards the station does not prove that the course-deviation needle is using that VOR.
In an analogue cockpit, identify which indicator is connected to each receiver. Tuning NAV2 while watching a NAV1-only indicator is a mistake we see constantly.
If a G1000 source selector, softkey or navigation field will not respond, the problem may be the avionics state or a control conflict rather than VOR reception. Our guide to diagnosing G1000 and FMS navigation-control problems covers that failure separately.
How can I tell whether the VOR signal is actually being received?
A valid ident, a cleared NAV warning flag and responsive course-deviation indications together show that the receiver has a usable signal.
Do not use DME as the only test. Not every VOR transmits distance information, and not every aircraft has working DME equipment. Likewise, a frequency associated with a localiser will only provide localiser guidance within its directional coverage; it will not behave like a 360-degree VOR.
Why will the autopilot not track a tuned VOR?
A tuned VOR does not make the autopilot follow it unless the autopilot is coupled to the correct navigation source and captures the selected course.
- Set the HSI or CDI to the same NAV receiver carrying the VOR signal.
- Select the required OBS or CRS course.
- Use heading mode to establish a sensible intercept rather than expecting capture from any position or angle.
- Arm the appropriate navigation mode and check the flight-mode annunciation to see whether it is merely armed or has become active.
- Confirm that the autopilot is using the pilot-side or navigation source you changed; complex aircraft can have separate source logic.
If the CDI responds correctly during hand flying but the aircraft does not turn towards it, the VOR receiver is working. The remaining fault is autopilot mode, source coupling or intercept geometry.
How far away can MSFS receive a VOR?
VOR range depends on line of sight, station coverage, aircraft altitude and intervening terrain, so there is no single reliable distance for every beacon.
A low aircraft can lose a station that becomes usable immediately after a climb. Terminal facilities generally serve a smaller area than en-route facilities, while mountains can block either one. Microsoft Flight Simulator may simplify parts of radio propagation, but altitude and location remain essential troubleshooting checks.
Directly over the beacon, the receiver enters the cone of confusion. The CDI can swing, and the TO/FROM indication may become unreliable for a short period. That behaviour is normal and should settle after passing the station.
Could the VOR station or navigation data be wrong?
A station-data problem is possible, but it is less common than an incorrect cockpit setup.
If one VOR fails in several aircraft while nearby stations work, suspect mismatched navigation data, local scenery or an add-on overriding that area. Frequencies from old real-world material may not agree with the data installed in the simulator.
If every VOR fails in one aircraft but works in another, investigate that aircraft's electrical system, receiver controls and source selection. If every VOR fails in every aircraft, check global control bindings, radio-assistance features and add-ons that modify navigation data.
Hardware deserves attention when a frequency, course or CDI source changes by itself. Duplicate controller bindings, a permanently active switch or a noisy rotary encoder can repeatedly overwrite cockpit selections. Saved flights can also restore an unexpected avionics state; starting a clean flight or reloading the aircraft is a useful final check.