Why is the GPS not working in FS2004?

In FS2004, a GPS usually fails because the aircraft’s panel does not define a GPS window, the default GPS gauge is missing or misreferenced, avionics power is off, or the NAV/GPS selector remains on NAV. First test a default aircraft; that immediately separates an FS9-wide fault from an add-on panel problem.

Why won’t the GPS open in FS2004?

If the GPS does not open at all, check the aircraft’s electrical power and panel configuration before replacing any files.

1. Turn on electrical and avionics power. In a cold-and-dark aircraft, switch on the battery, generator or alternator as appropriate, followed by the avionics master. A GPS may remain completely black without avionics power.
2. Open it from the FS2004 menu. Use Views > Instrument Panel and select the GPS entry. Do not assume that a particular Shift-number shortcut applies to every aircraft; popup-window assignments depend on the panel.
3. Test a default FS2004 aircraft. Load a stock aircraft equipped with the default GPS and start a new flight. If that unit works, FS9 itself is healthy and the fault belongs to the original add-on aircraft.
4. Check the add-on’s installation. Reinstall its panel and gauge files into the locations specified by its documentation. Our FS2004 add-on installation checks explain the folder structure and the common nested-folder mistake.
5. Confirm that the aircraft actually has a GPS window. Some aircraft were deliberately supplied without one, while others use a custom navigation unit instead of the stock FS9 GPS.

For an add-on panel, back up Aircraft\aircraft-folder\panel\panel.cfg before inspecting it. A working popup normally needs a GPS entry in [Window Titles], a corresponding [WindowXX] section and a valid gauge reference such as fs9gps!gps_500 or fs9gps!gps_295. An aircraft using a panel alias must be checked in the aliased panel folder instead.

Do not copy an entire panel.cfg from an unrelated aircraft; that often fixes the popup while breaking the main panel, virtual cockpit or radio stack. Our explanation of how FS2004 aircraft and panel files fit together provides useful background when tracing panel and gauge references.

Why is the FS2004 GPS screen black?

A black GPS popup normally means it has no avionics power or FS2004 cannot load the gauge named by the panel.

• Only one add-on is affected: suspect its panel.cfg, an omitted custom gauge, a bad panel alias or an outdated local copy of the GPS gauge.
• Every aircraft is affected: check that the standard fs9gps.cab file is present directly in FS2004’s Gauges folder.
• The menu entry is selected but no window is visible: test a newly created flight and restore the aircraft’s original panel configuration. Saved panel state or edited window-position values can leave a popup outside the visible screen area.

FS2004 reads fs9gps.cab as a cabinet, so do not rename or unpack it merely because Windows displays it as an archive. If the original file is absent or damaged, restore it from a known-good backup or the FS2004 installation media. Avoid downloading an unidentified replacement because modified gauge packages can introduce further panel errors.

Why won’t the autopilot follow the GPS route?

FS2004’s autopilot follows the GPS only when there is an active leg, GPS is selected as the navigation source and the autopilot is in NAV mode.

1. Activate a route. Load a flight plan through Flight Planner or activate a Direct-To destination. A moving map by itself does not give the autopilot a course to follow.
2. Select GPS as the source. Move the panel’s NAV/GPS selector to GPS. The map can work normally while the autopilot is still listening to the NAV radio.
3. Engage NAV mode. Heading mode follows the selected heading bug, not the magenta GPS course. Bring the aircraft towards the active track so the autopilot can capture it cleanly.
4. Observe the aircraft’s limitations. Some add-on panels couple only to their own FMS or custom autopilot. The default FS9 GPS provides lateral route guidance but does not make the autopilot manage altitude or descent automatically.

Switch the navigation source back as required before capturing a conventional VOR or ILS, and follow the add-on aircraft’s own procedure when it differs. For route entry, Direct-To operation and waypoint sequencing, see our guide to operating the default FS2004 GPS.

Why is the GPS position or airport data wrong?

Incorrect or missing airports, navaids and procedures usually indicate old or conflicting navigation data rather than a failed GPS gauge.

FS2004’s stock database reflects the simulator’s original-era scenery data. An add-on AFCAD or other airport BGL can introduce duplicate facilities, moved runways or conflicting frequencies. If the error appears only around one add-on airport, disable that scenery temporarily and test the default airport data.

Updates must match the component being used: the stock GPS reads FS2004 scenery and facility data, while a third-party FMC may keep a separate database. Updating one does not necessarily update the other. Our instructions for updating FS2004 navaids and navigation data cover the relevant BGL, AFCAD and conflict checks.

Fastest diagnosis: if the default GPS works, repair the add-on panel; if every GPS is black, check power and fs9gps.cab; if the map works but the autopilot does not turn, check the active leg, NAV/GPS selector and NAV mode; if facilities are wrong, investigate scenery and navigation data.