How do I download and install missions in FSX?

To download and install missions in Microsoft Flight Simulator X (FSX), save the package to a temporary folder, extract it, and copy its mission folder into FSX’s Missions directory without changing the internal structure. Copy any supplied reward files to Rewards, restart FSX, then select Missions on the startup screen.

Download the correct FSX mission package

Choose a mission explicitly made for FSX or FSX: Steam Edition, rather than one for FS2004, Prepar3D or Microsoft Flight Simulator. You can browse our FSX freeware and mission downloads; packages commonly arrive as ZIP archives, EXE installers or MSI installers.

Read the download description and included README before copying anything. Some missions require FSX Acceleration, a particular aircraft, additional scenery or other files supplied with the package. Missing dependencies can leave the mission visible but unable to load correctly.

Where is the FSX Missions folder?

The correct destination is the Missions folder inside the FSX installation root, not the Documents folder or the location where the ZIP was downloaded.

Your path may differ if Windows, FSX or the Steam library was installed on another drive. In the steps below, FSX root means the folder containing fsx.exe, Missions, SimObjects and the simulator’s other main folders.

A typical finished path resembles FSX\Missions\Category\MissionName. The final mission folder often contains files such as .FLT, .WX and .SPB, plus its own sound, image or supporting folders.

How do I install an FSX mission from a ZIP file?

A ZIP mission should be fully extracted before its files are copied into FSX.

1. Close FSX. The simulator will not reliably detect a mission added while it is running.
2. Extract the archive. Use Windows’ extraction option and open the resulting folder. Do not drag individual files directly from the compressed ZIP into FSX.
3. Read the instructions. The package may specify a mission category or include an exact folder tree. This manual-install mission example demonstrates the usual extract-and-copy method.
4. Copy the mission folder. Place it under the category supplied by the archive or named in the README. If the archive already contains a top-level Missions folder, merge its contents with FSX\Missions; do not create FSX\Missions\Missions.
5. Install companion files. If the archive contains top-level folders such as Rewards, SimObjects, Effects or Sound, merge them with the matching folders in the FSX root as instructed. For example, this mission package using both Missions and Rewards folders shows why copying only the main mission folder may be insufficient.
6. Check the folder depth. A correct layout resembles FSX\Missions\Category\MissionName\mission-file.FLT. Extra wrapper folders such as MissionName\MissionName are a common reason downloads do not appear.
7. Start FSX and open Missions. Find the category named in the README and select the newly installed mission.

If Windows requests administrator approval when copying into Program Files, approve it only for a package you trust. When asked to replace an existing file, stop and make a backup first; an updated mission may intentionally replace its own files, but unrelated FSX files should not be overwritten blindly.

How do EXE and MSI mission installers work?

An EXE or MSI mission package normally copies its files automatically, but its detected FSX path must be checked before installation.

Close FSX, run the installer and follow the package’s instructions. If it asks for the FSX directory, select the actual installation root containing fsx.exe unless the documentation specifically requests the Missions folder. After installation, verify that the new folder appeared under the correct Missions directory.

Older installers sometimes detect the boxed FSX location even when only Steam Edition is installed. They may report success while writing to an unused Microsoft Flight Simulator X folder, or Windows may redirect files from a protected directory into VirtualStore. Search for the installed mission’s folder name, then move its files into the real Steam installation while preserving the supplied structure.

Are downloaded missions compatible with FSX: Steam Edition?

Most missions built from standard FSX mission files work in FSX: Steam Edition when placed in the correct Steam folder and when all required aircraft and scenery are available.

The usual problem is an old installer targeting the boxed edition’s directory, not the mission itself. Missions containing legacy gauges, DLLs or other add-on components can have additional requirements; our guide to boxed and Steam add-on compatibility explains those differences.

Why does my downloaded FSX mission not appear?

A missing mission is usually caused by the wrong installation path, an unextracted archive or one extra folder level.

• Nothing appears in Missions: confirm that the mission was extracted into the active FSX installation and that its files are not still inside the ZIP. Check every mission category rather than only the category opened by default.
• The installer completed but no files are present: it probably selected another FSX directory. Search for the mission folder and relocate it to the installation containing the fsx.exe you actually run.
• The mission appears but fails to load: restore the original folder structure and check the README for required aircraft, scenery, FSX Acceleration or other dependencies.
• Voices, images or objects are missing: reinstall the supporting folders supplied with the mission. Moving only the .FLT or .SPB file breaks references to nearby resources.
• The reward does not appear: copy any package-supplied reward file into FSX\Rewards, restart the simulator and meet the mission’s stated completion conditions.