How do I update navdata and navaids in FS2004?

To update navigation data in Microsoft Flight Simulator 2004 (FS2004), install an FS2004-compatible global navdata scenery package for the simulator’s GPS, map, flight planner and ATC; update each add-on FMC with its own supported AIRAC format; and use airport AFCAD files for local ILS corrections. Back up existing BGL files and never stack overlapping updates.

Which FS2004 navigation database needs updating?

FS2004 does not have one universal navigation database or a built-in live AIRAC updater. The correct method depends on which instrument or simulator function is showing old data.

Updating an FMC will not update the default GPS, and installing an AFCAD will not refresh the complete airway network. Some aircraft gauges use FS2004’s own data while others carry a separate database, so check the add-on’s documentation before replacing anything.

How do I update FS2004’s GPS and global navaids?

Install a global update explicitly made for FS2004 or FS9, preferably as a separate scenery area rather than overwriting the simulator’s original BGL files.

1. Check the package scope. Confirm that it supports FS2004 and states whether it updates VORs, NDBs, intersections, airways, airport records or approaches. Files intended for FSX or newer Microsoft Flight Simulator versions are not interchangeable with FS9 files.
2. Back up the existing installation. Save copies of any BGL files the package replaces and the active Scenery.cfg. If an older edition of the same update is installed, deactivate or remove it first.
3. Keep manual updates isolated. When the package permits a normal scenery-layer installation, create a folder such as Addon Scenery\FS9 Navdata Update\scenery and place its BGL files inside the scenery subfolder. Follow the supplied instructions if the package instead requires specific core files to be replaced.
4. Activate the scenery area. Open FS2004’s Scenery Library, add the package’s parent folder and place it above the stock scenery. A dedicated airport add-on should normally remain at a higher priority than a broad global update unless its documentation says otherwise.
5. Restart and verify the result. Check a known navaid in the Map view or default GPS, then tune its published frequency and confirm the identifier. For an ILS, test the localiser and glideslope as well as the displayed frequency.

Older installers sometimes target the wrong FS2004 folder or fail to write into a protected Windows directory. If nothing changes, inspect the actual simulator folder and confirm that the new scenery area is enabled.

How do I update an add-on FMC’s AIRAC cycle?

An add-on FMC must be updated with the database format designed for that particular aircraft or gauge. Do not place FMC waypoint or airway files in an FS2004 scenery folder unless the documentation specifically instructs you to do so.

1. Identify the database format used by the FMC, not merely the aircraft name.
2. Back up the existing database folder, including any procedures, waypoints and airway files.
3. Install one complete cycle. Mixing waypoint files from one cycle with airways or procedures from another can produce missing fixes, broken routes and discontinuities.
4. Confirm the cycle inside the FMC if it displays a database date or cycle identifier, then load a short route and check several fixes.

Legacy utilities may require data prepared for another older gauge format. For example, our notes for simpleFMC’s legacy AIRAC file arrangement explain its use of Flight1 ATR-format waypoint and airway files. That update affects the utility’s own routing data, not every navigation system in FS2004.

How do I correct one airport’s ILS or navaids?

Use an airport-specific AFCAD BGL when the problem is confined to one airport’s runways, ILS records, frequencies, taxiways or parking positions. Our collection of FS2004 airport facility updates contains examples covering individual airports and regional groups.

Deactivate any older AFCAD for the same ICAO code before installing the replacement. Put the new file in its own scenery area where possible, assign it a higher priority than default scenery and broader navdata layers, restart FS2004, and test the airport.

Experienced users can inspect or alter airport facility data with the AFCAD 2.21 airport-data editor. Keep the original BGL untouched so an incorrect runway, ILS or parking edit can be reversed.

An AFCAD changes facility data; it does not necessarily update the visible airport scenery. Moving a runway or renumbering it can therefore leave the GPS and localiser aligned with the new data while the painted runway, signs or buildings remain in their old positions. Changing an ILS frequency alone also does not guarantee that a matching approach will appear in the GPS or ATC menus.

Why is updated navdata not showing in FS2004?

The usual cause is that the wrong database was updated or another BGL has higher scenery priority.

• The FMC changed but the GPS did not: the aircraft database and FS2004 scenery database are separate.
• An old frequency still appears: search for another AFCAD or navaid BGL covering the same airport and temporarily deactivate it.
• The scenery library shows the package but nothing changed: verify that its BGL files are inside a recognised scenery subfolder and restart FS2004.
• The installer completed without changing files: confirm that it found the real FS9 installation rather than a default or obsolete path.
• Routes contain missing fixes: reinstall a complete, internally consistent AIRAC cycle for the FMC.
• The instruments work but visuals are displaced: the navigation data and airport scenery represent different airport layouts.

When diagnosing conflicts, disable one update layer at a time rather than deleting files. Stacking several global updates or multiple AFCADs for the same airport is a mistake we see constantly, and it can produce duplicate ILS signals, incorrect frequencies or mismatched runway data.

Can FS2004 use a current AIRAC cycle?

FS2004 can use newer AIRAC data only where a compatible package exists for the specific simulator component or add-on. A current FMC database does not automatically modernise the default GPS, ATC, airport scenery or approach records.

Choose the newest complete cycle supported by all parts of the aircraft add-on rather than combining unrelated files to obtain a later date. For the simulator-wide database, compatibility and consistent airport coverage matter more than the cycle number: a coherent older update is safer than a partial modern one that conflicts with FS2004’s scenery.