How can I safely update the FSX navaid database and radio frequencies?

Updating FSX navaids/frequencies (safely) — what’s realistic

FSX’s built-in navaid/airway database is basically “baked in” (it lives in the sim’s scenery .BGL files), so there isn’t one single “official” Microsoft-style update that brings the whole world up to current-day data. What people typically do is update it in a couple of safe, controlled ways depending on what you actually need.

1) First: make sure FSX itself is fully patched
If you installed from the original discs, step one is confirming you’re not on the very early RTM version.

Why it matters: it won’t modernize the navdata, but it does avoid a lot of stability issues before you start adding anything.

2) Decide what you’re trying to “match”
There are really two different “databases” people talk about:

• FSX world navaids/ILS/VOR/NDB/frequencies (scenery BGL-based)
• FMS/GPS navdata used by certain add-on aircraft (often updated separately from the sim)

If you mainly fly default aircraft using the default GPS and ATC, you’re dealing with the first one (the FSX scenery data).

If you fly a study-level airliner with its own FMS, that aircraft may have its own navdata system, and updating that doesn’t necessarily update FSX’s underlying VORs/ILS, etc.

3) The “safe” approach for updating FSX navs is via reputable scenery tools/add-ons
The usual safe method is installing a trusted, well-known navdata/scenery update package that replaces/overrides the old navaid/ILS data with new BGLs. That’s generally how it’s done in FSX—by adding updated scenery layers that contain corrected navaids, ILS positions/frequencies, etc.

Practical safety tips before you touch anything:

• Create a restore point in Windows (or at least a full backup of your FSX folder).
• Back up your fsx.cfg and your scenery.cfg (those are the two that tend to get changed).
• Install one change at a time and test at a known airport (so you can roll back if needed).
• Avoid random “navdata packs” from file-hosting sites. Stick to established flight sim communities/vendors only.

4) Understand the limitation: airports vs navs
Even if you update navaids globally, a lot of “frequency/ILS mismatch” pain in FSX comes from the fact that many stock airports are outdated too. If you install updated airports (AFCAD-type changes) without matching navaid updates (or vice versa), you can end up with:

• ILS that doesn’t line up with the runway
• ATC assigning old runway/frequency combos
• A chart showing one ILS, FSX still tuned to another

So the cleanest results usually come from updating airports in the areas you fly most (or using a coordinated set of updates), not necessarily trying to “fix the entire planet” in one shot.

A few quick questions so I can point you to the right/safest path

• Which exact FSX do you have installed: FSX “boxed” (Deluxe/Acceleration) or FSX: Steam Edition?
• Are you mostly flying default aircraft, or add-on aircraft with an FMS?
• What’s your main goal: matching real-world charts for IFR (ILS/VOR airways), or just making ATC/runways/frequencies less “ancient” at your favorite airports?
• Any add-on scenery already installed (even just a few airports/mesh/landclass)?

Answer those and I can tell you the least risky way to get you updated without turning your FSX install into a science project.