Fix FS2004 waypoints missing after an AIRAC update by checking FMC format, install path, cycle mismatches, scenery BGLs and retired fixes.
Waypoints usually disappear after an FS2004 AIRAC update because the new data was installed for the wrong FMC, placed in the wrong folder, mixed with files from another cycle, or no longer contains a renamed or retired fix. FS2004’s stock GPS, add-on FMCs and flight planners use separate navigation databases.
What causes waypoints to disappear after an AIRAC update?
Missing waypoints after an AIRAC update usually indicate a database-target or compatibility problem rather than damaged FS2004 aircraft or scenery. An AIRAC cycle is a revision of real-world navigation data, but its files are not universal; our explanation of cycle revisions and database mismatches covers the underlying distinction.
- The wrong database was updated: FS2004’s default GPS, Map view and flight planner obtain facilities from active scenery BGL files. An add-on FMC normally reads its own database, while an external planner may use a third one.
- The package is for another FMC: each gauge or navigation programme expects a particular file structure. For example, simpleFMC’s FS2004 package has its own waypoint and airway files; data intended for another FMC will not be converted automatically.
- The files went into the wrong folder: multiple FS2004 installations, an extra nested folder created during extraction, or Windows redirecting writes into
VirtualStorecan leave the working gauge on its old database. - Two cycles were mixed: replacing only some waypoint, airway or procedure files can produce missing fixes and broken routes. One complete, internally consistent dataset is safer than a mixture of old and new files.
- The waypoint genuinely changed: AIRAC revisions can rename, relocate or withdraw fixes. A saved route built against an older cycle may therefore become invalid after a correct update.
- It is a procedure-only fix: some FMCs keep terminal procedure fixes separately from their global waypoint list. Such a fix may work when the SID, STAR or approach is selected but remain unavailable through a normal direct-waypoint search.
Which FS2004 navigation database needs fixing?
The database to repair is the one in which the waypoint fails, not necessarily the package that was most recently installed.
| Symptom | Most likely explanation | What to check |
|---|---|---|
| Missing from the stock GPS and Map view, but present in the FMC | Only the FMC database was updated | Active FS2004 scenery and navdata BGLs |
| Present in the stock GPS, but missing from the add-on FMC | Wrong FMC format, folder or index | The add-on’s own navdata directory and displayed cycle |
| Present in a planner, but rejected by the FMC | The planner and FMC use different cycles | Cycle and package format in both programmes |
| Missing only from an old saved route | The fix was renamed, retired or moved into procedure data | Rebuild the route using the installed cycle |
| Most waypoints at one airport or across a region are absent | Incomplete files, an airport identifier mismatch or conflicting BGLs | Procedure coverage, scenery priority and duplicate navdata packages |
How do I restore the missing FS2004 waypoints?
The quickest reliable fix is to identify the affected database, return it to one complete known-working cycle, and then reinstall the correct format into the folder actually read by FS2004 or the add-on.
- Identify where the waypoint is missing. Compare the same identifier in the stock GPS or Map view, the add-on CDU and the route planner. Do not rely solely on the map display because its zoom and filtering can hide intersections that remain in the database.
- Record the active cycle. If the FMC shows a cycle identifier or validity dates, note them. The stock FS2004 GPS does not necessarily report the cycle used by an add-on FMC.
- Back up the working files. Copy the entire active navdata folder or recently installed BGL package before deleting or replacing anything. If a previous complete cycle is available, restoring it is a useful test: if the waypoint returns, the change lies in the new dataset.
- Verify the package format. Confirm that the update names the exact FMC, gauge or FS2004 BGL system being used. An FS2004-compatible AIRAC package for one product is not automatically compatible with another.
- Check the real installation path. Compare the files’ locations and dates with the add-on’s instructions. Look for duplicate FS2004 folders, an extra directory level created during extraction and a redirected copy under
VirtualStore. An installer success message does not prove that the gauge is reading those files. - Install one complete cycle. Remove only the old files identified by the add-on’s instructions, then install the full replacement set together. Do not retain selected procedure or airway files from another cycle.
- Restart FS2004. Many gauges load their database when the simulator or aircraft starts. If the add-on documents an index or cache rebuild, perform that documented procedure rather than deleting unidentified files.
- Rebuild the route. Once the planner and FMC use matching cycles, create the route again instead of repeatedly importing the old file. If the fix was withdrawn, use the replacement routing from the installed cycle rather than copying obsolete data back into the database.
- Test for a BGL conflict. If the waypoint is missing from the stock GPS, temporarily disable the recently added navdata or scenery layer in the Scenery Library, restart FS2004 and retest. If it returns, resolve the package priority or duplicate BGL rather than moving default scenery files at random.
Why is the waypoint in my planner but not the FS2004 FMC?
A planner and an FS2004 FMC can display different waypoints because each reads its own database. Exporting a route transfers route information; it does not install the planner’s waypoint definitions into the receiving FMC.
Match the AIRAC cycle in both tools and use the correct data format for the FMC. If matching cycles still disagree, check whether the identifier belongs only to a terminal procedure or whether one product uses an older airport identifier. Avoid substituting guessed coordinates inside a SID, STAR or approach because that can create an incorrect flight path.
Do I need to update FS2004 scenery as well?
You need an FS2004 scenery or navdata BGL update only when the missing waypoint affects the built-in GPS, Map view or flight planner. Updating visual airport scenery alone will not populate an add-on FMC, and installing FMC data will not update the stock GPS; our FS2004-specific guide to stock navaids and navdata explains which files control each system.
Newer AIRAC data can also contain changed airport identifiers, runway designations and procedures that FS2004’s original scenery does not represent. In that case the FMC database may be correct even though the airport layout or stock GPS remains outdated. Keep each database internally consistent rather than combining unrelated FMC files, procedure files and replacement BGLs.