Fix an X-Plane FMS that rejects waypoints, SIDs or STARs by checking entry format, runway filters, AIRAC cycles and aircraft-specific navdata.
An X-Plane FMS usually rejects waypoints, SIDs or STARs because the identifier is entered on the wrong page, the flight-plan source and aircraft use different AIRAC cycles, or the procedure is filtered by the selected airport or runway. Confirm the route context, match navdata cycles, then test the same entry in a default aircraft.
What does the rejection pattern mean?
The pattern shows whether you are dealing with one invalid identifier, missing procedure data or a wider FMS database problem.
| Symptom | Likely cause | First check |
|---|---|---|
| One waypoint is rejected | Typing error, renamed fix or identifier absent from the active cycle | Enter the exact identifier manually and check for a duplicate-fix selection page |
| Every waypoint is rejected | Wrong entry field, navdata not loaded or aircraft-specific database problem | Try a known airport or navaid in a default X-Plane aircraft |
| Waypoints work, but no SIDs or STARs appear | Airport, runway or transition filter; missing procedure support; incomplete CIFP data | Set the origin and destination, then inspect the departure or arrival page |
| Only an imported route fails | Old AIRAC identifiers or an unsupported flight-plan format | Enter the first rejected fix manually |
| A procedure appears but is not added to the route | Unselected transition, unresolved route modification or missing execution step | Review the selected runway and transition, then activate or execute the change |
How do I fix rejected waypoint entries?
Test the entry manually before replacing files or reinstalling X-Plane; this separates a route error from a database fault.
- Use the correct FMS page. Enter fixes in the route or legs area supported by that unit. A SID or STAR name is not a waypoint identifier and normally belongs on the departure or arrival procedure page.
- Enter the identifier, not the place name. Use the published fix, airport or navaid code without descriptive text. If several fixes share an identifier, select the one whose coordinates or region match the route.
- Check the airway sequence. On units that use separate airway and exit fields, enter the airway followed by a valid exit fix. Entering an airway name as though it were a waypoint will be rejected.
- Compare AIRAC cycles. Check the cycle shown by the aircraft, if available, against the cycle used to create the route. A fix can be renamed, removed or moved between cycles. Our AIRAC installation and cycle-verification procedure covers X-Plane 11 and 12.
- Inspect the Custom Data installation. Updated global navdata belongs in the X-Plane installation’s
Custom Datafolder unless the aircraft explicitly requires another location. Avoid an accidental nested folder and install a complete, coherent cycle rather than mixing individual files from different cycles. - Restart X-Plane. Navigation data is loaded during startup, so replacing files while the simulator is running does not reliably refresh an FMS. Check
Log.txtafter restarting if X-Plane reports data-loading or parsing trouble. - Test a default aircraft. If a Laminar aircraft using the default FMS accepts the waypoint but an add-on rejects it, the add-on probably uses its own database, format or update location. If both reject it, suspect the identifier, global navdata installation or route cycle.
A “NOT IN DATABASE” or “INVALID ENTRY” message does not always mean the whole database is broken. For one troublesome fix, use our identifier, syntax and database checks for rejected FMC entries before changing the complete navdata set.
Why are SIDs and STARs missing from the X-Plane FMS?
SIDs and STARs normally remain hidden when the FMS lacks the required airport context, applies a runway filter or cannot read compatible procedure data.
- Enter the correct origin and destination ICAO codes before opening the departure or arrival pages.
- Check whether the FMS expects a runway or transition to be selected first. Another unit may show all procedures initially, so the exact order is aircraft-dependent.
- Remove an unsuitable runway filter if the expected procedure serves another runway. Do not select an incompatible procedure merely to make it appear.
- Confirm that the procedure exists in the active AIRAC cycle. Procedure names and runway assignments can change, especially after runway renumbering.
- Make sure the aircraft actually supports database procedures. A basic GPS or simplified custom FMS may accept individual fixes without supporting complete SIDs and STARs.
- Check the airport code. A fictional airport, changed ICAO identifier or newly built add-on airport will not gain procedures merely because its scenery is installed.
Airport scenery supplies the visible airport; navdata supplies the coded procedures. Updating scenery alone will not add a missing SID or STAR. Our runway, transition and aircraft-capability checks for X-Plane 12 procedures cover the procedure-specific cases in more detail.
Why does an imported flight plan fail when manual entries work?
An imported plan usually fails because it contains identifiers from another AIRAC cycle, includes procedures the aircraft expects you to select manually, or uses a flight-plan format that the chosen FMS does not fully support.
Open the route and find the first rejected leg. Enter that identifier manually: if it fails, replace it with the valid fix from the aircraft’s active database; if it works, the import format or route structure is the problem. Old saved .fms files should be rebuilt rather than repeatedly reloaded after database changes.
Some custom aircraft use their own company-route format and do not interpret native X-Plane plans exactly like the default FMS. In that case, load or enter the en-route portion using the aircraft’s supported method, then select the SID, STAR and approach inside its own CDU. Follow the correct FMS route-entry and execution sequence if fixes are accepted but changes never become active.