Fix missing engine sound in FS2004 by checking Q mute, volume sliders, sound.cfg, aircraft.cfg entries, folder aliases and missing WAV files.
Missing engine sound in Microsoft FS2004 usually means sound was toggled off, the engine-volume control is down, or the selected aircraft has a broken sound= entry, sound.cfg, alias or WAV set. Press Q first. If default aircraft still sound normal, repair the affected add-on rather than reinstalling FS2004.
How do I tell whether FS2004 or the aircraft is at fault?
The fastest diagnosis is to test a default FS2004 aircraft with its engine visibly running.
| Symptom | Likely cause |
|---|---|
| No sound anywhere in FS2004 | Sound toggled with Q, Windows output problem or global FS2004 audio fault |
| ATC and cockpit sounds work, but every engine is silent | Engine-volume slider at zero or engines not actually running |
| Only one add-on aircraft is silent | Missing sound folder, broken alias or incomplete WAV set |
| Only one repaint is silent | Incorrect sound= value in that repaint's [fltsim.x] entry |
| Only cockpit, external or AI engine sound is missing | Incomplete viewpoint-specific or AI sound configuration |
If every default aircraft and every other type of audio is silent, use the broader Windows audio checks for FS2004. An aircraft-level repair will not fix a global output-device or DirectSound problem.
How do I repair the engine sound?
Work through these checks in order, stopping once a default aircraft or the affected add-on produces normal engine audio.
- Confirm that the engine is running. Check RPM, manifold pressure or N1 rather than relying on the propeller or fan animation.
Ctrl+Estarts engines on default and straightforward aircraft, although complex add-ons may require their own start procedure. - Press Q and check the sound sliders. Q toggles all simulator sound and is easily pressed by accident. In FS2004's sound settings, raise both the overall sound level and the engine-volume control; the engine slider can be at zero while ATC or cockpit clicks remain audible.
- Load a default aircraft. Test a default Cessna for piston sound or the Boeing 737-400 for jet sound. If the default aircraft works, leave FS2004's global configuration alone and concentrate on the silent add-on.
- Check the repaint's sound selection. Open the aircraft's
aircraft.cfgafter making a backup. Each[fltsim.x]variation has asound=line: a blank value uses the normalsoundfolder, whilesound=PWlooks forsound.PW. Replace a mistyped suffix with the one supplied by the aircraft, or leave it blank when the intended files are in the standardsoundfolder. - Inspect the folder placement. The normal layout is
FS2004\Aircraft\AircraftName\sound\sound.cfg. A common installation mistake is an extra nested aircraft directory, producing something such asAircraft\AircraftName\AircraftName\sound. Compare the package with our explanation of the correct FS2004 add-on folder layout. - Open sound.cfg and verify its alias. Some aircraft contain a complete sound configuration and WAV collection; others contain only an alias to another installed aircraft. An alias may look like
alias=B737_400\sound. The named aircraft folder and sound subfolder must exist beneath FS2004'sAircraftdirectory. Correct spelling errors, remove circular aliases and restore the intended target if it is missing. - Check the WAV collection. A full
sound.cfgreferences individual start, idle, combustion, shutdown and other samples. Missing files can make the engine silent only during one phase or RPM range. Restore the complete matching sound package instead of copying an unrelatedsound.cfg, whose filenames may not match your WAV files. - Check the real filename extensions. Windows may hide known extensions, leaving a file named
sound.cfg.txtthat appears to besound.cfg. A file merely renamed with a.wavextension is also not necessarily a compatible WAV sample. - Reload the aircraft. After saving changes, reselect the aircraft or restart FS2004 so its sound configuration is loaded again. Test both cockpit and external views.
For a closer explanation of aircraft.cfg, sound folders and aliases, see our breakdown of FS2004 aircraft folders and configuration files.
Why does only one repaint have no engine sound?
A silent repaint usually has a sound= suffix copied from another variation without the corresponding sound folder.
Compare the silent repaint's [fltsim.x] section with a working variation of the same aircraft. Do not enter a complete path on the sound= line: it selects a folder suffix, not an arbitrary directory. Also confirm that the repaint was added as a new numbered [fltsim.x] section rather than overwriting part of an existing entry.
What if only cockpit, external or AI engine sound is missing?
Sound missing from only one perspective normally points to incomplete entries or samples for that viewpoint, while silent AI traffic uses a separate AI sound setup.
- Cockpit silent, exterior audible: restore the aircraft's complete sound set rather than copying only its loud external engine samples.
- Exterior silent, cockpit audible: inspect
sound.cfgfor missing external engine mappings and verify that all referenced WAV files are present. - Sound disappears at one RPM: a specific idle, low-power or high-power sample is probably missing, damaged or named differently from its configuration entry.
- Only AI traffic is silent: check the aircraft package's
soundaifolder or AI alias, where supplied. This is separate from the flyable aircraft's normalsoundfolder. A missing AI set can be replaced with an FS2004 AI aircraft sound package.
Does FS2004 need to be reinstalled?
Reinstalling FS2004 is rarely justified when only one aircraft or repaint has no engine sound.
Restore or reinstall the affected aircraft first, keeping any custom repaints and configuration backups. Consider repairing FS2004 itself only when default aircraft have lost their original sound files and the global audio checks do not restore them.