Install a replacement cockpit panel in FS2004 safely: use the correct folders, preserve the virtual cockpit and fix blank or missing gauges.
To install a replacement cockpit panel in Microsoft Flight Simulator 2004 (FS9), close the simulator, extract the download, back up the aircraft’s existing panel folder, then copy the new panel files and supplied gauges to the locations specified by its documentation. Reload the aircraft and test the 2D and virtual-cockpit views.
Which replacement panel should I install?
Use a panel explicitly made for FS2004 or FS9, preferably for the exact aircraft and engine type you intend to fly. FSX, Prepar3D and later Microsoft Flight Simulator panels are not automatically compatible, even when their folders and configuration files look similar.
Check whether the download is a complete replacement, an optional panel variant or an alias to another installed aircraft. Also look for required gauges, sounds or modules. A complete package may depend on every supplied component; our worked Boeing 737 replacement-panel example shows why the panel and gauge installation instructions must be read together.
Where do FS2004 replacement panel files go?
Aircraft-specific panel files normally go under Flight Simulator 9\Aircraft\AircraftFolder\panel, while shared gauges normally belong in the main FS2004 Gauges folder.
Find the active folder containing fs9.exe instead of assuming FS2004 is installed on a particular drive. FS2004 uses an Aircraft directory; do not put its aircraft panels in the SimObjects\Airplanes structure used by later simulators.
| Package content | Usual destination | What to check |
|---|---|---|
panel.cfg and panel bitmaps | Flight Simulator 9\Aircraft\AircraftFolder\panel | panel.cfg must be directly inside the active panel folder, not under panel\panel. |
.gau files, gauge CAB files or gauge folders | Flight Simulator 9\Gauges | Follow the package instructions and do not unpack a gauge CAB unless specifically told to do so. |
A folder such as panel.wide | The aircraft’s main folder | The selected [fltsim.x] entry in aircraft.cfg must contain panel=wide. |
| Panel sound files | Usually the main Sound folder or a named subfolder | Preserve the archive’s folder structure because gauges may expect an exact path. |
| Modules or other dependencies | The location specified by the documentation | Do not place every supplied file in Gauges; install each component according to its type. |
Some aircraft use panel variants or aliases instead of a plain panel folder. Our explanation of FS2004 panel folders, variants and alias paths covers how FS9 decides which folder to load.
How do I replace the FS2004 panel safely?
The safest installation method preserves the original aircraft and stages the downloaded files outside the simulator first.
- Close FS2004. Do not replace panel, gauge or module files while the simulator is running.
- Extract the archive to a temporary folder. Never run the panel from inside its ZIP file or copy the ZIP itself into the aircraft directory. Inspect the extracted folders before moving anything.
- Read the included documentation. Confirm the target simulator, aircraft, required dependencies and whether the package replaces the standard panel or adds a selectable variant.
- Locate the correct aircraft folder. Work from the FS2004 installation containing the
fs9.exeyou actually launch. If you have several copies of an aircraft, check its exact folder rather than choosing one by a similar name. - Back up the original panel. Copy the complete
panelfolder somewhere outside the FS2004Aircraftdirectory. Back upaircraft.cfgas well if the instructions require apanel=change. - Install the new panel files. For a direct replacement, the final path should end with
AircraftFolder\panel\panel.cfg. A mistake we see constantly is copying the archive’s outer folder as well, producingpanel\panel\panel.cfg. - Install gauges and other dependencies. Copy each item to the location named by the documentation. If a shared gauge with the same filename already exists, back it up before replacing it; other aircraft may depend on that copy.
- Configure a panel variant if required. If the new folder is named
panel.wide, for example, setpanel=widein the appropriate[fltsim.x]aircraft variation. Leave the entry empty when using the ordinarypanelfolder unless the package says otherwise. - Load the correct aircraft variation and test it. Check the main 2D panel, every pop-up window, radios, engine instruments and the virtual cockpit. Turn on the battery, avionics and engines before treating an unpowered display as a missing gauge.
How do panel variants and aliases work?
A panel= entry selects a matching panel folder, while an alias= entry tells FS2004 to use a panel installed under another aircraft.
For example, panel=wide selects panel.wide. Because this setting belongs to an individual [fltsim.x] section, one livery may show the replacement while another still uses the original panel.
An aliased panel.cfg contains a path pointing to a donor aircraft and panel folder. That donor aircraft must remain installed under the expected folder name. Moving, renaming or deleting it breaks every aircraft that uses the alias.
Why is the replacement panel black or missing gauges?
A black or incomplete panel usually means FS2004 cannot find a bitmap, gauge or dependency referenced by panel.cfg.
- No 2D panel appears: confirm that a cockpit panel view is selected, then check the active variation’s
panel=entry and the location ofpanel.cfg. - The background is black or absent: look for missing bitmap files, incorrect filenames or an extra nested folder. The bitmap named in the relevant panel window section must be available where the configuration expects it.
- The background appears but instruments are blank: reinstall the required
.gau, CAB and gauge folders. Also check the aircraft’s electrical and avionics power. - Only one livery or variation fails: inspect that variation’s
panel=value and verify that the correspondingpanel.namefolder exists. - An alias produces no panel: verify that the donor aircraft and the panel folder named by
alias=are installed at that exact relative path. - The old panel still appears: you may have edited another aircraft copy, another FS2004 installation or the wrong
[fltsim.x]variation. On protected Windows installations, legacy file writes may also be redirected to VirtualStore, leaving two different copies of the configuration. - FS2004 crashes while loading the aircraft: restore the original panel first. An incompatible binary gauge or module is a common cause; add the replacement components back in stages to isolate it.
- The panel is too large, too small or off-centre: installation has probably succeeded, but its window dimensions do not suit your display. Use our guidance on correcting FS2004 panel size and position rather than moving files again.
If FS2004 displays a trust or security prompt for a third-party gauge or module, approve it only when you recognise and trust the package. Refusing a required component can leave blank instrument positions. Restart FS2004 after changing gauges or modules so they are loaded afresh.
Will a replacement 2D panel update the virtual cockpit?
A replacement 2D panel does not add or rebuild an FS2004 virtual cockpit because the three-dimensional cockpit geometry is part of the aircraft model.
The virtual cockpit’s instrument mappings are often defined by [Vcockpit] sections in the same panel.cfg. Replacing that file with a 2D-only version can therefore leave the 3D cockpit model present but remove its working gauges.
Choose a package that explicitly supports the target aircraft’s virtual cockpit. Do not blindly paste old [Vcockpit] sections into the new file: gauge names, coordinates and model textures must match. Our guide to how FS2004 virtual cockpits depend on the aircraft model explains why a panel download alone cannot create one.
How do I restore the original FS2004 panel?
Remove the replacement panel folder and return your backed-up panel folder to the aircraft directory. Restore the saved aircraft.cfg if you changed a panel= entry, then select the same aircraft variation and test it again.
Restore overwritten shared gauges only from backups you made during installation. Do not delete added files from Gauges, Sound or Modules indiscriminately, because another installed aircraft may now use them.