What is flight simulator navdata, and how do you update it?

For flight simulators in general, navdata is the coded database of airports, runways, navaids, fixes, airways and instrument procedures used by the simulator, route planner and aircraft avionics. Update each component with its supported AIRAC package or navdata manager, then verify that all of them report—and actually use—the same cycle.

What does flight simulator navdata contain?

Navdata contains the machine-readable records needed to build, display and follow a route. Depending on the simulator and database, those records can include:

• Airport identifiers, runway positions, thresholds and elevations
• VORs, NDBs, localisers and associated frequencies
• Intersections, reporting points and waypoint coordinates
• Airways and permitted route directions
• SIDs, STARs, approaches, transitions and missed-approach legs
• Courses, altitude restrictions and speed constraints

There is rarely one universal database for the whole installation. The simulator map, built-in ATC, GPS, advanced aircraft FMS and external planner may each read a different source. A mistake we see constantly is updating one of those sources and assuming the others changed with it.

Navdata is not airport scenery, terrain, satellite imagery or a set of charts. It can describe a runway or procedure, but it does not repaint the runway, move a terminal building or supply a human-readable approach plate. Simulation navdata must never be used for real-world navigation.

What is a navdata cycle, and how does AIRAC work?

A navdata cycle identifies the effective edition of the database, usually following the aviation industry's 28-day AIRAC schedule. AIRAC stands for Aeronautical Information Regulation and Control and coordinates the effective dates of significant navigation changes.

Flight-simulation packages commonly use a four-digit YYNN label: the first pair identifies the year and the second pair is that year's cycle sequence. Cycle boundaries do not follow calendar months. The terms navdata cycle, nav data cycle and navigation database cycle generally refer to this same edition identifier, although not every simulator database displays one.

An expired database does not stop working. It may simply lack newer fixes, airways, frequencies, runway identifiers or procedure revisions. Some avionics show NAV DATA OUT OF DATE when the simulated date falls outside the database's validity period.

How do you identify the latest AIRAC cycle?

The active AIRAC cycle is the one whose published effective period covers the date being simulated. Check the cycle number and effective dates shown by the authorised data package, navdata manager or avionics information page rather than trying to infer it from the month.

The newest package available for download may be the next cycle released ahead of its effective date. Some FMS units also hold active and secondary databases, so copying a new package into the secondary slot does not necessarily make it active. Check the IDENT, STATUS, NAV DATA or equivalent information page after installation.

Do you need the latest AIRAC cycle?

You need a recent, matching AIRAC cycle for present-day IFR routes, online ATC, procedure-heavy flying and reliable flight-plan imports. Casual VFR flying and an older self-contained installation can usually continue with an older database.

Matching data is often more useful than mixed-age data. A planner and FMS on the same older cycle will generally produce fewer unknown waypoints than a current planner feeding a much older aircraft database. Historical flights may deliberately use period-appropriate data, while unsupported legacy avionics should not be forced to read a newer, incompatible format.

AIRAC data is licensed. Use an authorised package, the simulator's supported update service or one of the legitimate free AIRAC update options and their documented limits; do not install copied databases from an unknown source.

How do you update navdata for flight simulators?

A reliable update changes every database involved in the flight and then proves that the intended software is reading it.

1. List every navdata consumer. Include the simulator map and ATC, built-in GPS, add-on FMS or FMC, external planner and any career or dispatch utility.
2. Record the installed cycles. Check each component's information page before changing files. A displayed date range can be used when no four-digit cycle number is shown.
3. Select the exact target package. Flight simulator data packages are specific to a simulator, version, aircraft or utility. Files intended for one FMS format cannot safely be copied into another because the cycle number happens to match.
4. Back up and close the software. Preserve manually edited files and any application database or profile that an importer will modify. Close the simulator, planner and related utilities before running an installer.
5. Install through the supported method. Use the simulator's update service, a recognised navdata manager or the manual folder described by the product documentation. Confirm the actual library path rather than accepting an old path left from a previous installation.
6. Remove conflicting packages. Do not leave two custom navdata packages active for the same target unless the documentation explicitly requires both. Package priority can make an older database override the new one.
7. Restart and rebuild indexes if required. Some simulators scan navigation files at launch; others retain a cache until it is rebuilt. Let indexing finish before loading a flight.
8. Verify the cycle and its contents. Check the cycle shown in the cockpit, then inspect a known SID, STAR or approach. An installer reporting success proves that files were copied, not that the aircraft opened them.
9. Regenerate old flight plans. A saved route may still contain fixes or procedure transitions selected from the previous cycle. Rebuild and export it after the planner and aircraft agree.

What does a navdata manager actually update?

A navdata manager downloads or installs supported packages into registered simulator and add-on targets; it does not turn all navigation systems into one shared database. Each listed target normally receives its own format and installation path.

• Use a manager when several supported aircraft and planning tools need the same cycle or when automatic path detection is reliable.
• Use a manual package when the exact add-on documentation requires one and the manager does not support that target.
• Use the simulator's built-in delivery system on platforms where external file access is unavailable or where the core database is maintained by the simulator itself.

If a manager says a package is installed but the FMS still shows the old cycle, check the selected product profile, aircraft variant and destination library. Multiple simulator installations, moved package folders and an aircraft with its own database are more common causes than a damaged AIRAC download.

What about the NeoFly Navdata Merger?

The NeoFly Navdata Merger is an application-specific import or reconciliation utility, not a general AIRAC provider or a replacement for a navdata manager. It only affects the data that the supported NeoFly release is designed to read; it does not update the simulator's world map, airport scenery or an aircraft FMC.

Compatibility and accepted source data can change between NeoFly releases, so use the instructions supplied for the exact installed build rather than guessing at folders. Close NeoFly first, back up its career or profile data using its supported method, and confirm the source cycle before merging. If NeoFly and the cockpit still disagree, inspect their databases separately.

Where does each simulator get its navdata?

The correct update route depends on which simulator and avionics layer is producing the route or procedure.

Why do the FMC and flight planner show different navdata?

The planner and FMC usually disagree because they are reading different cycles, different database targets or different interpretations of the same procedure.

• NAV DATA OUT OF DATE: compare the simulated date with the active database validity period. For a historical flight the warning may be expected; for present-day flying, install and activate the appropriate cycle.
• A procedure appears in the planner but not the FMC: compare cycle numbers, airport and runway identifiers, then confirm that the aircraft's own target was updated. Some simulated avionics omit procedure legs or transitions they cannot interpret.
• The installer succeeds but the old cycle remains: check for the wrong product profile, an inactive secondary database, an obsolete library path or another package overriding the update.
• An imported route contains unknown waypoints: rebuild the route with the same cycle used by the aircraft. Manually deleting unknown fixes may create an invalid airway connection.
• Procedures or waypoints appear twice: disable duplicate custom packages and rebuild any navigation index or cache. Do not merge files manually unless the add-on explicitly documents that process.
• Both products show the same cycle but still differ: test a specific waypoint and procedure. One product may use scenery-derived airport data, apply different procedure filters or lack support for a particular leg type.

Cycle labels alone are not enough. The quickest practical test is to select one recently changed procedure at a familiar airport in both the planner and cockpit, then compare its runway, transitions and key fixes.

Does updating navdata update airports, runways or charts?

Updating navdata changes coded navigation records, not the visual airport or its charts. After a real runway renumbering, the FMS may show the new identifier while older scenery still has the previous number painted on the ground.

Fix that visual mismatch with compatible airport scenery, not by repeatedly reinstalling the AIRAC package. Charts are also a separate product unless a package explicitly says otherwise, and simulator ATC may retain another airport database even after the aircraft FMS has been updated.

When the planner and cockpit agree but the runway, taxiways or buildings do not, the remaining fault is normally scenery. When the airport looks correct but procedures or fixes are missing, investigate the navdata target, package priority, avionics support and cache instead.