Fix an add-on aircraft with no sound by checking audio settings, sound folders, aliases, dependencies and simulator compatibility.
A downloaded add-on aircraft usually has no sound because its sound files are missing, nested in the wrong folder, or referenced by a broken alias. It may also be a repaint or AI model with no player sounds, an incompatible legacy conversion, or a simulator-wide audio setting. Test another aircraft first.
Across Microsoft Flight Simulator 2020/2024, FSX, Prepar3D and X-Plane, the key distinction is whether only the add-on is silent. If stock aircraft also have no audio, the add-on is probably not the cause.
How do I identify what is causing the missing sound?
The quickest test is to load a default aircraft at the same airport with its engine already running. This separates an aircraft-package fault from a muted simulator, incorrect output device or operating-system mixer problem.
| Symptom | Likely cause | First check |
|---|---|---|
| Every aircraft and the interface are silent | Global audio or output-device problem | Simulator volume sliders, system mixer and selected playback device |
| Only one downloaded aircraft is silent | Missing files, broken alias or incompatible package | Aircraft folder and installation instructions |
| Exterior sound works but the cockpit is silent | Missing interior events, camera-state problem or incomplete sound set | Internal and external camera views |
| Only one livery or variant is affected | Incorrect variant configuration or missing base aircraft | The package's required dependencies |
| Only AI aircraft are silent | Missing AI-specific sound folder | soundai rather than the player-aircraft sound folder |
Start the test from a runway rather than cold and dark. Headset simulation, closed-canopy attenuation and a stopped engine can make a working aircraft seem unusually quiet. If default MSFS aircraft are silent too, use our checks for simulator-wide Microsoft Flight Simulator audio faults.
Which aircraft sound files and folders should I check?
A valid sound installation must match the folder structure expected by that simulator; copying files into the first folder named after the aircraft is not enough.
- FSX and Prepar3D: A flyable aircraft normally has a
soundfolder containingsound.cfgand sound files, or a configuration that aliases another installed aircraft's sound folder. The aircraft folder also normally sits alongside itsmodel,panelandtexturefolders. Our FSX aircraft-folder installation guide shows the expected hierarchy. - Microsoft Flight Simulator 2020 and 2024: The package root normally contains its package metadata, including
manifest.jsonandlayout.json, with the aircraft assets deeper inside. Do not extract only the visible aircraft directory or transplant an FSXsoundfolder into a modern MSFS package. The audio may use packaged event banks rather than ordinary WAV files. - X-Plane: Sound assets may use a conventional
soundsfolder or an FMOD-based structure associated with the aircraft's.acffile. FMOD sound definitions and banks are aircraft-specific; a missing bank, required plugin or incompatible aircraft version can leave the model silent. Filename case also matters on case-sensitive operating systems.
A mistake we see constantly is an extra directory level after extraction. If opening the installed aircraft folder reveals another identically named folder before reaching the configuration and model files, the package is probably nested one level too deep.
How do I fix a silent downloaded aircraft?
Fix the package methodically rather than replacing random sound files, as an unrelated sound set can hide the original installation error.
- Confirm the scope. Test a stock aircraft, interface sounds, cockpit sounds and an exterior view. If everything is silent, correct the global audio problem first.
- Check what you downloaded. A repaint contains textures and depends on a separately installed base aircraft. An AI model may have no player-cockpit sounds, while some freeware packages require a named donor aircraft or sound pack.
- Extract the archive again. Extract it to a temporary location, inspect the folder hierarchy, and then copy the complete package to the simulator's proper add-on location. Do not move isolated files unless the included instructions explicitly require it.
- Inspect aliases and dependencies. In FSX or Prepar3D, open
sound.cfgwith a text editor. If its[fltsim]section contains an alias, the named aircraft and sound folder must exist exactly where the simulator expects them. Our FSX sound-folder and alias instructions cover this repair in detail. - Match the simulator generation. An FS2004 or FSX aircraft may display in a newer simulator yet still have incompatible gauges, animations or audio. Use a package explicitly made for your simulator, or a documented conversion rather than assuming visual compatibility means full compatibility.
- Perform a clean reinstall. Remove the faulty copy before reinstalling so that obsolete configuration files are not mixed with the new package. On consoles, where package folders are not user-accessible, remove and reinstall the aircraft through the simulator's supported content-management system.
- Test without conflicts. Temporarily remove duplicate versions and aircraft-specific audio modifications. Add them back one at a time after the unmodified aircraft produces sound.
Why is there still no audio when sound.cfg exists?
A sound.cfg file is an index, not proof that the referenced audio is present. Its entries can point to missing filenames, an absent alias target or files left elsewhere in the downloaded archive.
Check that the referenced sound folder has actual audio assets and that filenames have not been changed. Avoid renaming files merely to make an error disappear: engine state, viewpoint and aircraft system events may each call different sounds, so one repaired filename can still leave start-up, shutdown or cockpit audio missing.
Can I copy sounds from another aircraft?
Copying or aliasing another sound set is suitable only when the simulator supports it, the donor represents a compatible engine type, and its licence permits reuse. In FSX and Prepar3D, a correct alias is usually cleaner than duplicating the entire folder.
Modern MSFS and FMOD-based X-Plane aircraft often bind audio events to that specific model, so dropping in a legacy sound folder will not work. Use an aircraft-specific replacement package and follow its instructions rather than mixing sound systems from different simulators.
What if only AI add-on aircraft have no sound?
AI aircraft may use a separate audio structure and should not be diagnosed as though they were flyable cockpit aircraft. In FSX, AI packages commonly use a soundai folder; a normal sound folder may not provide the expected traffic audio.
Place AI sound files only where their documentation specifies and keep them inside the correct aircraft package. Our FSX AI sound installation example demonstrates the separate soundai arrangement. Other simulators handle traffic audio differently, so an FSX AI sound package should not be copied into MSFS or X-Plane.