Learn why FSX GPS waypoints are missing and fix old navdata, add-on database mismatches, map filters, scenery conflicts and broken flight plans.
In FSX and FSX: Steam Edition, waypoints are usually missing from the GPS or Flight Planner because both use stock, release-era navigation data. New, renamed or withdrawn fixes may not match modern charts. Separate add-on databases, scenery conflicts, display filters and incompatible flight-plan files can also hide valid points.
What causes missing waypoints in FSX?
The most common cause is a mismatch between FSX's navigation database and the data used to create the route. The stock Flight Planner and default GPS obtain airports, intersections and radio navaids from FSX's scenery-based facility data, which reflects the aviation network around the simulator's 2006 release and does not update automatically.
The mismatch we see most often is a modern route loaded into the stock GPS. A fix may have been introduced or renamed after FSX was released, while a withdrawn identifier may remain in the simulator long after it disappeared from real-world charts.
| Where the waypoint is missing | Likely cause | What it means |
|---|---|---|
| Default GPS and Flight Planner | Old stock data or a scenery exclusion | FSX does not have an active facility record for that identifier. |
| Add-on FMC or GPS only | Separate or outdated AIRAC data | The add-on is not necessarily using the stock FSX database. |
| Map display only | Zoom level or facility filters | The point may still exist but its symbol or label is hidden. |
| Imported flight plan only | Unsupported waypoint type, stale identifier or malformed file | The importer has skipped or replaced part of the route. |
Updating an add-on aircraft's FMC does not update the default FSX GPS, and replacing FSX facility data does not automatically update every add-on unit. Boxed FSX and FSX: Steam Edition behave the same way in this respect.
How do I check whether a waypoint is absent or hidden?
A short comparison between the stock map, Flight Planner and aircraft unit will identify which database or file is at fault.
- Confirm which navigator is affected. Check whether the point is missing from the default FSX GPS, an add-on FMC, or both. Different results indicate separate databases rather than a universal FSX problem.
- Verify the identifier and coordinates. Search by the fix identifier, not only its spoken name. Check whether the modern point was renamed, moved or replaced, since reusing an old identifier can produce misleading results.
- Inspect the FSX map. Enable the relevant intersection, VOR or NDB symbols and zoom into the area. Our explanation of using FSX's map and display controls covers the filters and scale effects that commonly conceal facilities.
- Create a clean native route. Build a short plan through the same area rather than importing the original file. Follow our guide to building and editing a route with the stock Flight Planner if needed.
- Isolate scenery changes. If the point used to appear, temporarily untick the most likely navigation or scenery add-on in the Scenery Library and restart FSX. Test one layer at a time; do not delete default scenery files.
If the waypoint is absent from both the stock map and Flight Planner, FSX probably lacks the facility record. If the map shows it but an imported plan does not, concentrate on the plan format or exporter. A point found by the stock GPS but not an add-on FMC indicates an add-on database issue.
Why can the map show a waypoint that Flight Planner omits?
A waypoint can exist in FSX without being selected by the automatic route generator. Direct GPS, VOR-to-VOR, low-altitude airway and high-altitude airway routing each choose different facilities, and a fix that is not attached to the selected airway network may be bypassed.
Use the route-editing map to insert a recognised point manually rather than expecting Find Route to select it. Also remember that GPS nearest pages show a limited nearby list, not every waypoint in the worldwide database.
How can I restore or use the missing waypoint?
Choose the remedy according to where the waypoint disappears.
- New or renamed real-world fix: use an FSX-compatible navigation-data update, or place a user waypoint at verified coordinates in a compatible
.PLNfile. A user point can guide the GPS, but FSX ATC may not recognise its name or treat it as an airway intersection. - Add-on FMC or GPS mismatch: update the database specifically supported by that unit and create the route with matching data. Do not copy an aircraft's AIRAC files into stock FSX scenery folders.
- Automatic routing omission: insert the waypoint manually or select the routing mode matching the airway on which the fix lies.
- Imported flight-plan problem: export in native FSX flight-plan format. If points are still dropped, rebuild the route in FSX and compare it with the imported version; procedure records and proprietary waypoint types may not translate.
- Scenery conflict: disable the suspect layer, then repair its installation or ordering according to its documentation. Keep backups before replacing any navigation or scenery data.
Will updating FSX navdata fix every missing waypoint?
No. A stock-data replacement fixes only the facility types it actually updates, and it may leave add-on avionics, procedures, runways and ATC references on different data cycles.
Consistency matters more than having one updated component. Our overview of the limits and safe methods for updating FSX navigation data explains which databases can be changed and why backups are essential.
Why does the GPS show the waypoint but the aircraft skips it?
A visible waypoint that the aircraft flies past is normally a leg-activation or navigation-source problem, not missing navdata. Check that the intended leg is active, no route discontinuity remains, the GPS is sequencing normally, and the panel's GPS/NAV selector is set correctly where fitted.
If the route is present but the autopilot will not track it, use our GPS/NAV source and autopilot tracking checks rather than changing the waypoint database.