Find the FS2004 panel folder and panel.cfg, identify panel variants and aliases, and fix hidden extensions or files saved in the wrong place.
In FS2004 (FS9), each aircraft’s panel folder normally sits at [FS2004 folder]\Aircraft\[aircraft folder]\panel, with panel.cfg directly inside it. If that aircraft’s aircraft.cfg has a value after panel=, FS2004 uses the matching panel.[value] folder instead. This per-aircraft file is separate from the global FS9.cfg file.
What is the exact FS2004 panel.cfg path?
The path starts in the directory containing fs9.exe, then continues through Aircraft and the individual aircraft’s folder. If you installed FS2004 somewhere other than its original default location, use our guide to locating the FS2004 installation directory.
- Open the main FS2004 folder containing
fs9.exe. - Open
Aircraft. FS2004 uses this directory rather than the newerSimObjects\Airplanesstructure found in later simulators. - Open the folder for the required aircraft.
- Open
panel, or the applicablepanel.[suffix]folder. - Look for
panel.cfgdirectly inside that folder.
A typical full path is C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\Aircraft\[aircraft folder]\panel\panel.cfg, but the drive and installation directory can differ. The aircraft’s displayed name also need not match its folder name; that display name comes from a title= entry in aircraft.cfg. Our explanation of the standard FS9 aircraft folder structure shows how the model, panel, sound and texture folders fit together.
Which panel folder is FS2004 actually using?
The panel= line in the selected aircraft variation’s [fltsim.x] section determines which panel folder FS2004 loads.
| Entry in aircraft.cfg | Panel folder used |
|---|---|
panel= | panel |
panel=wide | panel.wide |
panel=cargo | panel.cargo |
Check the particular [fltsim.x] entry for the livery or variation you selected. Different variations in the same aircraft folder can point to different panels.
Shared panel aliases
A very short panel.cfg may contain an alias instead of its own instrument and window definitions. For example, alias=SomeOtherAircraft\panel tells FS2004 to load the panel from that other aircraft beneath the main Aircraft directory.
Follow the alias to find the working panel configuration. Do not replace an alias merely because the local file appears unusually small; sharing a default aircraft’s panel is normal for many add-ons.
Why can’t I find panel.cfg?
The usual causes are a hidden file extension, the wrong panel variant, an alias, or an aircraft package extracted one folder too deeply.
- Hidden extensions: Windows may display
panel.cfgsimply aspanel. Enable file-name extensions in File Explorer and check the file type. - Wrong panel folder: Inspect the selected variation’s
panel=entry. A value such aspanel=widepoints topanel.wide, notpanel. - Nested installation: A common extraction mistake produces
Aircraft\AircraftName\AircraftName\panel. The inner aircraft contents must be moved up one level. - Missing file: If the active panel folder has no configuration and no alias, the installation may be incomplete. Re-extract or reinstall the aircraft package.
- Wrong destination:
panel.cfgdoes not belong in FS2004’s globalGaugesfolder. Gauge files may go there, but the panel configuration remains with the aircraft.
Do not confuse this file with FS9.cfg, which stores simulator-wide preferences elsewhere in Windows. We have a separate explanation of where the global FS9.cfg file is stored.
Can I edit panel.cfg safely?
Yes, provided you back up the original and edit it as plain text while FS2004 is closed.
- Copy
panel.cfgand rename the copy to something such aspanel.cfg.bak. - Open the original in a plain-text editor.
- Save it as
panel.cfg, notpanel.cfg.txt. - Reload the aircraft after saving; restart FS2004 if the change is not picked up.
If FS2004 is installed under a protected Program Files directory, Windows may block the save or place an edited copy elsewhere. Edit a copy outside the protected directory, then copy it back and approve the administrator prompt. For a complete cockpit swap, follow our replacement-panel installation procedure rather than overwriting files without checking aliases and panel variants.