FS2004 freezes when selecting a flight? Isolate a corrupt .FLT or weather file, aircraft, scenery or FS9.cfg with safe, step-by-step checks.
FS2004 (FS9) usually freezes when selecting or loading a flight because a saved .FLT file, its .WX weather file, the chosen aircraft, or scenery at the departure airport is damaged or incompatible. Start with a default aircraft, stock airport and clear weather; the result tells you which component to isolate.
Where does FS2004 freeze when selecting a flight?
The point at which FS2004 stops is the best clue to the faulty file or add-on.
| Where it freezes | Most likely cause | Decisive test |
|---|---|---|
| Opening the Select a Flight list | Malformed saved .FLT file or an inaccessible user Documents folder | Move user-created saved-flight files outside the Flight Simulator Files folder |
| Loading one particular saved flight | Damaged .FLT, .WX or referenced aircraft, route or scenery | Recreate the same flight manually instead of loading the save |
| Choosing or previewing one aircraft | Faulty aircraft model, texture, configuration or package | Select a default FS2004 aircraft |
| After Fly Now with one aircraft | Panel, gauge, sound or shared module problem | Use the same airport and weather with a default aircraft |
| At one airport or in one area | Add-on scenery, duplicate AFCAD, mesh or AI traffic | Use a default aircraft at a different stock airport |
| With every new stock flight | Damaged FS9.CFG, global module, graphics setting or broader installation problem | Generate a clean FS9.CFG and repeat the stock test |
A Windows “Not responding” message does not by itself prove that FS9 has crashed. The simulator can stop repainting its window while a complex gauge, aircraft or scenery area loads. A repeatable stop under the same conditions, especially when the equivalent default flight loads normally, is stronger evidence than the displayed loading percentage.
How do I isolate the cause without reinstalling FS2004?
A clean comparison flight separates a bad save or add-on from a simulator-wide fault.
- Back up the user files. Close FS2004 and copy the
Flight Simulator Filesfolder from your Documents location. Back upFS9.CFGas well before resetting it later. - Bypass the saved flight. Use Create a Flight rather than loading the troublesome entry. If opening the saved-flight list itself causes the freeze, move its user-created contents to a temporary folder outside
Flight Simulator Files. - Run a stock test. Choose a default Cessna or another default aircraft, a stock airport, simple clear weather and daytime conditions. Do not load an old route or saved weather.
- Change one variable at a time. Test the suspect aircraft at the stock airport, then the default aircraft at the suspect airport. Add the route and weather only after those tests pass.
- Remove AI traffic from the test. If the problem follows an airport, temporarily set airline and general aviation traffic to zero. A damaged AI aircraft may be loaded only near certain airports.
- Create a fresh save. Once the flight works, save it under a new name rather than overwriting or reusing the suspect file set.
If only the original save fails, replace that save. If the freeze follows the aircraft, inspect its package. If it follows the location, isolate scenery and AI traffic. When every default combination fails, move on to FS9.CFG and global modules.
A mistake we see constantly is changing the aircraft, airport, weather and traffic together. That may make the flight load, but it leaves the actual cause unknown.
What is the FS2004 weather file, and can it cause a freeze?
The FS2004 weather file associated with a saved flight normally has a .WX extension and stores the weather state that FS9 restores with that flight.
| File | What it contains | What failure can look like |
|---|---|---|
.FLT | Saved aircraft state, position and references used by the flight | The flight list or loading process hangs, particularly if a referenced add-on is missing |
.WX | Weather saved with the flight | FS2004 stops while restoring that flight's weather |
.PLN | An optional flight plan and route | The saved route fails to load or refers to unavailable navigation data |
These user files are normally found in Documents\Flight Simulator Files; older Windows installations may display Documents as My Documents. If Documents has been redirected or synchronised, use its actual Windows location.
- Close FS2004. Do not move files while the simulator is running.
- Find the suspect set. Identify the
.FLTand same-named.WXfile. Include the associated.PLNwhen that saved flight uses one. - Move, do not delete. Put the set in a temporary folder outside
Flight Simulator Files. - Rebuild the flight. Start FS2004, select static clear weather and recreate the aircraft, airport and route manually.
If the recreated flight works, leave the old weather file out and make a new save. If merely opening the saved-flight list freezes FS9, move all user-created flight sets out, then return them in small batches until the bad set is identified.
A local .WX companion file is separate from an external weather programme or a real-world-weather download. Disable the external programme and test with static weather if the freeze occurs while weather is being injected rather than while a saved flight is selected.
What should I fix when only one aircraft freezes?
A freeze tied to one aircraft points to that aircraft's model, panel, gauges, sound or configuration rather than the saved flight system.
If FS2004 stops while displaying the aircraft selection preview, start with the model, texture and aircraft configuration. If the preview works but loading stops after Fly Now, the panel, gauges and shared modules become more likely.
Restore the complete aircraft from its original FS2004-compatible package or remove it temporarily. Do not copy a similarly named gauge from another aircraft: gauges can depend on specific versions or supporting modules. Never empty the simulator's Gauges or Modules folders wholesale, because default and working add-on aircraft may share their contents.
Our aircraft, panel and gauge isolation procedure covers the next checks when a newly installed aircraft causes the failure.
What if the freeze follows one airport?
A failure confined to one airport usually comes from local scenery or an AI aircraft loaded in that area.
Disable the airport's add-on entry in the Scenery Library, close FS2004, restart it and load the default version of the airport. Restarting matters because scenery files already loaded by FS9 may remain in use until the programme closes.
Common causes include duplicate AFCAD files, incompatible scenery BGLs, missing object libraries, nearby mesh and overlapping airport packages. If setting both AI traffic sliders to zero fixes the flight, inspect traffic packages and AI aircraft added shortly before the problem began; restore the sliders only after the faulty package has been removed or replaced.
What if every FS2004 flight freezes?
If a default aircraft at a stock airport also freezes, rebuild FS9.CFG before changing or reinstalling the main simulator files.
- Close FS2004 completely.
- Open its configuration folder. Enter
%APPDATA%\Microsoft\FS9in the Windows Run box or File Explorer address bar. - Rename the configuration file. Change
FS9.CFGtoFS9.CFG.old. Do not delete the backup. - Start FS2004. FS9 should create a fresh configuration file.
- Test before restoring settings. Load a default aircraft at a stock airport with clear weather and AI traffic disabled.
If the fresh file works, rebuild display, sound and control settings manually. Copying every old setting straight back can restore the fault. If it makes no difference, close FS2004 and restore the original configuration.
Next, isolate only known third-party modules and global scenery entries, one at a time. Our clean FS2004 baseline test for modern PCs provides the wider sequence for frame-rate limits, configuration files and add-on isolation.
If FS9 cannot create or retain its new configuration, add-ons cannot write their files, or the simulator behaves differently under a protected installation folder, use our Windows 10 and 11 compatibility checks for FS2004. Those permission and legacy-component problems are broader than a corrupt saved flight.
Will reinstalling FS2004 fix the flight-selection freeze?
Reinstalling is justified only when a clean stock flight still fails after saved flights, FS9.CFG, third-party modules and add-on scenery have been isolated.
An uninstall may leave the same files in Documents, AppData or the FS2004 installation folder. Restoring those files immediately can restore the freeze as well. After reinstalling, test the unmodified simulator first; return aircraft, scenery and saved flights in small batches only after the stock test works.