Update Level-D 767 SID and STAR procedures in FS2004, verify the AIRAC cycle, and fix missing or mismatched routes in the FMC.
To update SID and STAR procedures in the Level-D 767 for FS2004, install an AIRAC package made specifically for the Level-D 767, not a general FS2004 navdata or scenery update. Back up the existing database, install with FS2004 closed, then confirm the new cycle on the FMC IDENT page.
How do I install a Level-D 767 AIRAC update?
The safe method is to replace the complete Level-D navigation database with a compatible cycle rather than copying individual procedure files.
- Record the installed cycle. Load the Level-D 767, open the FMC IDENT page and note the active database cycle or date range. This gives you a reliable before-and-after check.
- Obtain the correct package. Use a licensed AIRAC dataset explicitly labelled for the Level-D 767 and your FS2004 installation. Packages made for another aircraft or FMC are not interchangeable, even when their AIRAC numbers match.
- Close FS2004. Also close any flight planner or utility that could be reading the Level-D database.
- Back up the old database. In a standard installation it is commonly under
<FS2004>\Level-D Simulations\navdata. Installation paths vary, so confirm that you are inside the active FS2004 folder and copy the entire navdata folder somewhere safe. - Run the updater or extract the package. For an automatic installer, select the active FS2004 installation and the Level-D 767 target. For a manual package, follow its included folder structure exactly. A mistake we see constantly is creating a second nested
navdata\navdatafolder, which the FMC will not read. - Reload the aircraft. Start FS2004 and load the Level-D 767 afresh so its gauges initialise against the replacement database.
- Verify the cycle. Return to the IDENT page and confirm that its cycle identifier or validity dates have changed.
For the CDU page sequence and aircraft-specific terminology, consult the Level-D 767 operating documentation information.
Does updating FS2004 itself change Level-D procedures?
No. The Level-D FMC database, FS2004 airport scenery and FS2004's own navigation data are separate layers.
- Level-D FMC database: supplies the SIDs, STARs, approaches, airways and fixes displayed by the 767 CDU.
- Airport scenery: determines the runways, taxiways and airport layout visible in the simulator.
- FS2004 navigation data: feeds the simulator's GPS, map and radio-navigation environment. Updating it does not automatically replace the Level-D database.
Stock FS2004 ATC also does not start assigning coded SIDs and STARs merely because the Level-D FMC has been updated. See our explanation of how FS2004 navaids and add-on navigation databases differ if both layers need attention.
How can I tell whether the procedures were updated?
The update has worked only if the IDENT page shows the replacement cycle and the expected procedures appear on the DEP/ARR pages.
- Enter the airport as the route origin or destination before checking its procedures.
- Select the airport's departure or arrival page, then inspect the available runway, procedure and transition choices.
- Build a short test route and check that the first or last procedure fixes appear in the correct order.
- Compare the encoded procedure with a chart from the same AIRAC cycle whenever possible.
Procedure names, transitions and runway assignments change between cycles. Our guide to interpreting SID and STAR charts explains how to compare fixes, transitions and altitude constraints with the FMC.
Why is a SID or STAR still missing?
Missing procedures usually result from an incorrect installation target, mixed AIRAC cycles or a mismatch between modern procedure data and FS2004-era airport scenery.
| Symptom | Likely cause | Fix |
|---|---|---|
| IDENT still shows the old cycle | The updater wrote to another FS2004 installation, lacked permission to replace files or created a nested folder. | Locate the FS2004 folder actually being launched, inspect the Level-D navdata location and reinstall the package there. |
| The cycle changed, but procedure lists are empty | The origin or destination has not been entered, or the package is incomplete or incompatible. | Enter both airport identifiers on the route page. If the lists remain empty, restore the backup and install a complete Level-D-format package. |
| Only one airport or procedure is missing | The airport identifier, runway or procedure changed between cycles, or the legacy FMC cannot represent part of a newer procedure. | Check the airport identifier and AIRAC date. Some modern procedures or leg types may be omitted or simplified for an older FMC implementation. |
| The FMC shows a runway absent from the scenery | The AIRAC database reflects a runway addition or renumbering that the installed airport scenery does not contain. | Do not use a procedure tied to a non-existent runway. Use a procedure compatible with the visible airport layout or install matching airport scenery. |
| A procedure name differs from the chart | The chart and FMC use different AIRAC cycles, or the FMC uses a shortened encoded name. | Compare transitions and fixes rather than relying on the displayed name alone. |
| Waypoints are rejected or route legs disappear | A saved route, flight planner and the Level-D FMC are using different database cycles. | Rebuild the route against one cycle and use our checks for waypoints missing after an FS2004 AIRAC update. |
| A route discontinuity remains | The procedure contains vectors, separate transitions or legs that do not connect automatically. | Compare the legs with the chart before closing the discontinuity; never delete one blindly. |
An AIRAC update does not rewrite an existing FS2004 flight plan or saved company route. Reselect the departure and arrival after changing cycles, and rebuild any route that contains obsolete fixes.
Can I copy SID and STAR files from another aircraft?
No. Navigation files are formatted for a particular add-on, and copying another aircraft's procedure database can produce empty lists, rejected fixes or FMC errors. The procedure coding also contains runway links, transitions, leg definitions and constraints—not just waypoint names.
If no newer package exists in the legacy Level-D format, use the newest compatible package you legitimately have rather than converting files intended for another FMC. Keep charts and route planning aligned with that database cycle, and retain the backup so you can recover from a failed update.