Fix missing FS2004 stall and landing-gear warning sounds by checking trigger logic, sound.cfg, WAV files, aliases and panel gauges.
Missing stall and landing-gear warnings in FS2004 usually mean the aircraft's sound.cfg references absent WAV files, its sound alias is broken, or a gauge that generates the alert is missing. First test a default aircraft; then check sound settings, the aircraft's Sound and Panel folders, aliases, and gauge installation.
Should the stall or gear warning be sounding?
A silent warning is not necessarily a fault because FS2004 only plays it when the aircraft's trigger conditions are met. Test from the cockpit at a safe virtual altitude, using a known default aircraft before changing any files.
- Stall warning: this responds to angle of attack rather than a particular indicated airspeed. Slow the aircraft with the wings level and increase the angle of attack until the horn should activate, then recover.
- Gear-up warning: use a retractable-gear aircraft with the gear raised. The horn normally depends on low throttle, flap position or both; the exact logic varies by aircraft.
- Fixed-gear aircraft: these have no reason to produce a gear-up warning.
- Gear movement sounds: hydraulic, motor, wind and locking noises are separate from the gear-up warning horn.
Some warning sounds are audible only, or much more clearly, inside the cockpit. Testing solely in an external view can therefore produce a false diagnosis.
How do I tell whether the problem is global or aircraft-specific?
A default-aircraft comparison quickly separates an FS2004 audio fault from a broken add-on.
- Test the default Cessna for the stall warning. Use a default retractable aircraft separately for the gear-up warning.
- Check the master sound state. Press
Qonce and listen for other simulator audio, then inspect FS2004's sound controls and the Windows volume mixer. - Compare another aircraft. If stock warnings work but one add-on remains silent, leave the global settings alone and repair that aircraft.
- Reload after each change. Select another aircraft and return, or restart FS2004, so its panel and sound configuration is loaded again.
| Symptom | Most likely cause |
|---|---|
| No sound of any kind | Master mute, sound settings, Windows output routing or FS9.cfg |
| Normal audio but no warnings in any default aircraft | Damaged configuration or missing default warning files |
| Default warnings work; one add-on fails | Broken Sound-folder alias, missing WAV files or panel gauge |
| Only one warning is absent | Missing warning section, wrong filename or unmet trigger condition |
If all FS2004 audio is affected, work through our FS2004-wide audio and Windows output checks before editing the aircraft.
How do I repair the aircraft's warning sound files?
When default warnings work, inspect the affected aircraft's own configuration and keep a backup before editing anything.
- Find the active sound set. Open the aircraft's
aircraft.cfgand inspect thesound=line in the active[fltsim.x]entry. A blank value normally selects the standard Sound folder; a suffix selects a correspondingly suffixed Sound folder. - Check for an alias. If
sound.cfgaliases another aircraft, confirm that the target aircraft and its Sound folder are installed. Renaming or removing the donor aircraft breaks the alias. - Inspect the warning entries. Conventional FS2004 sound configurations typically use
[STALL_WARNING]and[GEAR_UP_WARNING_SOUND]. Eachfilename=value must have a matching WAV file in the selected sound set; the extension is commonly omitted in the configuration. - Restore files as a matched set. Reinstall the aircraft's original Sound folder or sound package. Copying only
sound.cfgcan make matters worse when it references WAV files that were not copied with it.
A mistake we see often is borrowing a Sound folder from another aircraft without updating its alias or filenames. Our aircraft-specific cockpit-sound diagnosis covers the related folder, alias and incomplete-definition failures.
Can I copy warning sounds from another aircraft?
Copying a horn WAV alone rarely fixes the fault because sound.cfg still needs the correct filename and trigger section. Restore the aircraft's intended configuration and audio files together; do not replace a gauge-driven warning system with stock sound entries unless the add-on's instructions specifically call for that change.
What if the warning is generated by a panel gauge?
Many complex FS2004 add-ons generate warning audio through a panel gauge instead of the standard sound sections. In that case, an apparently complete Sound folder can still produce no stall or gear horn.
Inspect panel.cfg for missing or edited gauge lines and confirm that the supplied .gau or .cab files are installed where the package expects them, commonly the main Gauges folder or the aircraft's Panel folder. Do not delete an invisible or zero-sized gauge merely because it draws nothing; add-ons often use such gauges to run warning logic.
If panel instruments are also blank or FS2004 reports missing gauges, follow our instructions for repairing missing FS2004 add-on gauges. For a package containing separate panel, gauge and audio components, verify the correct panel and sound-pack folder placement rather than repeatedly copying files into the aircraft root.
When should I reset FS9.cfg or restore default files?
Reset FS9.cfg only when the warnings fail in multiple default aircraft after the normal audio controls have been checked. Close FS2004, back up %APPDATA%\Microsoft\FS9\FS9.cfg, rename the original file, and start the simulator so it creates a clean configuration.
This resets simulator preferences, so recheck sound levels, display options and controller assignments afterwards. If a clean configuration does not restore stock warnings, recover the affected default Sound folders and WAV files from a clean backup or the original FS2004 installation media rather than overwriting unrelated add-on aircraft.