How do I update navdata in FSX?

FSX has no single navdata updater. Its built-in GPS, Flight Planner and ATC read navigation records from scenery BGL files, while most add-on FMCs use separate AIRAC databases. Update FSX with a compatible scenery-based navdata package, then update each add-on aircraft with the dataset made for that exact product.

In Microsoft Flight Simulator X (FSX) and FSX: Steam Edition, navdata is not one database. A mistake we see constantly is updating an airliner FMC and then expecting the default GPS, map and ATC to change. They will not, because those systems read different files.

Which FSX navdata are you trying to update?

Choose the update according to where the outdated waypoint, frequency, procedure or runway appears.

AIRAC is the 28-day publication cycle used for operational aeronautical changes. In FSX usage, an “AIRAC update” usually refers to an add-on FMC database. The stock simulator has no central AIRAC folder or cycle selector, and FSX service packs or Steam client updates do not refresh its navigation data.

How do I perform an FSX navaids update for the built-in GPS?

To update the stock GPS, map and Flight Planner, install an FSX-compatible BGL package as scenery rather than copying an FMC AIRAC database into the simulator.

1. Check exactly what the package changes. Some FSX navaids updates cover VORs, NDBs and intersections only. Others include airways, approaches, airport identifiers or localiser records. Do not assume that a package labelled “navdata” replaces every part of the world database.
2. Confirm the supported FSX edition. Boxed FSX and FSX: Steam Edition can coexist, and older installers may select the boxed installation or an obsolete registry path. Our guidance on avoiding boxed-versus-Steam add-on path problems explains how to identify the installation that is actually being launched.
3. Back up files that will be replaced. Prefer a removable scenery layer when the package supports one. If its instructions require overwriting stock BGL files, retain untouched copies and a list of every replaced file.
4. Install the supplied BGL files as directed. A scenery-based package commonly has a structure such as Addon Scenery\Navdata Update\scenery, with an optional texture folder beside it. Select the parent folder containing scenery when adding the area. Do not put an add-on FMC database here; FSX cannot interpret it as scenery.
5. Activate and prioritise the scenery area. Place a global navigation layer above the default world scenery. Detailed airport add-ons normally remain above it unless the package documentation specifies another order. Follow our instructions for adding, enabling and prioritising an FSX scenery layer if the area is installed but does not appear in the simulator.
6. Disable competing global updates. Two packages may redefine the same VOR, intersection or airport record. Running both can produce duplicates or make the result depend on scenery priority and BGL exclusion rules.
7. Restart FSX. Allow the simulator to rebuild its scenery database before loading a flight.

How can I confirm that the FSX navdata update loaded?

Verify one documented change in the default map or GPS, such as a revised identifier, frequency or waypoint position. The stock GPS does not provide a dependable AIRAC-cycle display, so a specific change listed by the package is a better test.

Create a new flight plan for the test. An existing .PLN file may retain old identifiers or coordinates and can make a successful database update look faulty. If none of the advertised changes appears, check that the scenery area is enabled, that it belongs to the FSX installation being launched and that Windows allowed the installer to write the files.

How do I install an AIRAC update for an FSX add-on FMC?

An add-on FMC needs the AIRAC format written for that exact aircraft or avionics package; a download described only as “for FSX” is not specific enough.

1. Identify the actual avionics product. Similar-looking FMCs from different aircraft can use unrelated file formats and folder structures. A repaint or aircraft variant may also rely on a shared avionics installation elsewhere in FSX.
2. Select its supported database target. Confirm that the AIRAC package explicitly lists the aircraft, FMC, FMS or GPS product. Do not rename or convert files intended for another unit unless the add-on developer documents that method.
3. Close FSX and back up the existing database. Files held open by the simulator may not be replaced cleanly.
4. Install into the active add-on directory. The FSX root folder is not always the correct destination. Some products store data inside the aircraft folder; others use a shared add-on directory. Check the installer path instead of accepting an automatically detected boxed or Steam location without verification.
5. Replace the cycle rather than merging it. Combining files from different cycles can leave duplicated waypoints, missing procedures or mismatched indexes. Use the supported updater or the product's documented manual replacement process.
6. Check the displayed cycle. Many advanced FMCs show the database cycle on an IDENT or status page. If the old cycle remains, inspect the target path, file modification dates, write permissions and any active-versus-secondary database selection supported by the unit.
7. Test a known procedure or waypoint. Use an item confirmed as present in the installed cycle rather than assuming every missing route is a database fault.

Updating one aircraft does not update another aircraft, the default GPS, FSX ATC or airport scenery. It also does not make default ATC read and follow the SID or STAR selected in an add-on FMC.

Is there a free way to update FSX AIRAC data?

Sometimes. Free-of-charge, or de forma gratuita, updates can be legitimate, but they may cover selected navaids or airports rather than provide a complete worldwide database for the latest AIRAC cycle.

• Freeware BGL corrections can update parts of the stock FSX GPS and Flight Planner database. Check their geographical coverage, source date and uninstall instructions.
• Databases supplied with an add-on are legal for that product but may represent an older cycle.
• Free airport facility updates can correct a particular runway, ILS or frequency without replacing global navigation data.

For many advanced add-ons, access to the latest licensed AIRAC cycle requires a paid data service. Do not use copied subscription files or databases taken from another user's installation; apart from the licence issue, they may be incomplete or built for another FMC. Our guide to legal free AIRAC and simulator-navdata options explains what can be updated without an unauthorised download.

Do runway, ILS and airport changes need a separate update?

Yes, when the real-world change affects airport geometry or local facility records, a navdata update alone is often insufficient.

An FMC cycle may rename a runway and include procedures for it, but it cannot repaint the FSX runway, move taxiways or alter parking positions. Conversely, new airport scenery may show the renamed runway while an old FMC continues to list the former approach. For these cases, use an appropriate airport BGL and follow our explanation of updating FSX airport facilities, runways and ILS data.

Why do the FMC, GPS and scenery still disagree?

Disagreement usually means that only one database was updated, the files went to the wrong FSX installation, or another BGL is overriding the change.

• The change appears in the FMC only: the aircraft AIRAC update worked, but the scenery-based FSX database and airport remain old.
• The change appears in the default GPS only: the BGL update loaded, but the add-on FMC still has its previous cycle or was installed to the wrong folder.
• No advertised stock changes appear: check the Scenery Library tick box, layer priority, installation path and package coverage.
• Runways, parking positions or ILS signals are duplicated: two airport facility BGLs are active. Disable the lower-priority obsolete file rather than adding another correction on top.
• A frequency changed but the runway did not: the package may update navigation records without changing airport geometry or textures.
• A waypoint exists but the route still fails: rebuild the .PLN file and check whether the connecting airway or terminal procedure was included in the update.
• The FMC still reports the old cycle: verify the product-specific target, write permissions and active database selection. Installing an AIRAC package into the FSX root rarely updates every aircraft automatically.
• The add-on has no supported update format: some legacy avionics use a fixed or proprietary database. A generic AIRAC package cannot safely be forced into them.

For predictable results, keep the aircraft AIRAC, global BGL update and detailed airport scenery from reasonably compatible data periods. Never leave multiple worldwide navdata layers active and assume scenery priority will resolve every overlapping navaid or airport record.