Turn off FSX “DON'T SINK” and “TOO LOW” GPWS alerts safely, with the aircraft.cfg fix and steps for add-ons that ignore it.
FSX has no universal GPWS off switch. For aircraft using the stock GPWS logic, back up aircraft.cfg and set max_warning_height = 0 in its [GPWS] section. Reload the aircraft. If warnings continue, they come from an add-on gauge or module and must be inhibited through that aircraft’s panel or configuration.
This applies to boxed FSX and FSX: Steam Edition. The setting is aircraft-specific, although every livery defined by the same aircraft.cfg will inherit it.
How do I disable the stock FSX GPWS?
The stock system can be disabled by setting its maximum warning height to zero.
- Close FSX and back up the file. Open the relevant aircraft’s installation folder and make a copy of
aircraft.cfg. Our guide to finding and safely editing aircraft.cfg covers Steam paths and Windows permission problems. - Find the GPWS section. Search for
[GPWS], then change its existing entry tomax_warning_height = 0. Do not create a second GPWS section. - Add the section if necessary. If the aircraft uses stock FSX logic but has no GPWS section, add one
[GPWS]heading followed bymax_warning_height = 0. - Save it as a CFG file. Preserve the original filename and plain-text format; do not let the editor create
aircraft.cfg.txt. - Reload the aircraft. Select another aircraft and switch back, or restart FSX, so the configuration is read again.
You do not need to delete the other sink-rate values in that section. With the stock implementation, a maximum warning height of zero prevents the GPWS warning envelope from becoming active.
Why do GPWS warnings continue after the edit?
If max_warning_height = 0 has no effect, the aircraft is probably generating its warnings through a custom XML gauge, compiled gauge or add-on module.
| Warning source | Typical clue | Correct approach |
|---|---|---|
| Stock FSX GPWS | The aircraft reads the [GPWS] section | Set max_warning_height = 0 |
| Modelled add-on system | The cockpit or aircraft options include GPWS controls | Use the documented master or mode-specific inhibit control |
| Custom panel gauge | The CFG change does nothing and no cockpit switch is provided | Use the gauge’s configuration, or disable only the separate GPWS gauge after making a backup |
Check the aircraft’s cockpit and configuration utility first. Controls labelled G/S INHIBIT or TERR INHIBIT are not necessarily master mute switches: the former normally targets glideslope alerts, while the latter may affect only terrain modes.
Editing panel.cfg is a last resort. Remove or disable a gauge only when it is clearly a separate GPWS component; an integrated gauge may also drive the primary flight display, radio altimeter or annunciators. Never alter a shared gauge package merely to silence one aircraft.
FSX radio-altitude callouts and GPWS alerts are also not one universal sound service. Our explanation of how aircraft-dependent altitude callouts work helps distinguish a callout gauge from the simulator’s stock GPWS logic.
Can I silence only “DON'T SINK” or “TOO LOW”?
The stock max_warning_height method disables the GPWS as a whole; it does not select individual phrases.
A custom add-on may expose separate warning options or store each phrase as an aircraft-specific sound file. Change those only when the gauge documentation identifies them, and rename rather than delete files so they can be restored. The normal aircraft sound.cfg does not always control GPWS audio because gauges can play sounds directly.
Pressing Q or reducing FSX cockpit sound is a blunt workaround. It can suppress engines, switches, stall warnings and other useful audio as well, while some custom modules may ignore the cockpit-volume control.
Should I disable GPWS or fix the warning trigger?
Keep GPWS enabled when the warning reflects the aircraft’s actual flight path or landing configuration; disable it when the system is inappropriate for the aircraft, malfunctioning or repeatedly triggered by faulty scenery.
- “DON'T SINK” after take-off or during a go-around: the system has detected a loss of radio altitude during the climb phase. Establishing a positive climb is the correct response; see the fuller explanation of what the “DON'T SINK” warning means.
- “TOO LOW” near the runway: check gear, flaps, descent path and whether the aircraft is configured to land. Some systems append “GEAR”, “FLAPS” or “TERRAIN”, which identifies the triggering mode.
- Warnings at one particular airport: test the same approach without third-party scenery or terrain mesh. A runway-elevation conflict can make the radio-altitude logic believe the aircraft is dangerously close to terrain.
- Warnings immediately after loading: reload the aircraft and allow custom gauges to initialise. Saved flights can restore an unexpected flight phase or panel state.
To restore the stock warnings later, put back the original max_warning_height value from your backup rather than guessing a replacement threshold.