Fix FS2004 Aircraft Initialization Failure by resetting the default flight, rebuilding fs9.cfg, and checking add-on aircraft files and repaints.
FS2004 shows “Aircraft Initialization Failure” when the flight references an aircraft it cannot load. First select a stock aircraft in a new flight. If that works, repair or remove the affected add-on; if FS2004 fails before the menu, regenerate fs9.cfg and restore the default flight or missing stock aircraft files.
What does Aircraft Initialization Failure mean?
Microsoft Flight Simulator 2004 has found an aircraft reference but cannot initialise the corresponding aircraft. The message often names the failed aircraft, which is the most useful clue.
A saved flight identifies its aircraft through the title= entry in aircraft.cfg. Loading can fail when that title has changed, the aircraft has been removed, its folder is nested incorrectly, or a required AIR or model file is missing.
| When the error appears | Likely cause | First action |
|---|---|---|
| Only with one add-on | Broken folder structure, AIR file or model reference | Inspect or reinstall that aircraft |
| Only with one repaint | Incorrect repaint entry or missing base model | Repair its [fltsim.x] entry |
| Only with an old saved flight | The saved aircraft title no longer exists | Create and save a fresh flight |
| Before the flight-selection screen | Broken default flight or damaged fs9.cfg | Regenerate the configuration file |
| With stock aircraft as well | Missing default files or wider installation damage | Test a clean configuration and restore the installation |
How do I clear the FS2004 Aircraft Initialization Failure?
- Record the aircraft named in the message. If it identifies a specific add-on or livery, begin there rather than changing graphics, weather or scenery settings.
- Test a new flight with a stock aircraft. Select the default Cessna 172 or another untouched Microsoft aircraft. If it loads, FS2004 itself is working and the fault belongs to the original aircraft or saved flight.
- Replace the stale default flight. Create a fresh flight with a stock aircraft, save it and make it the default. An old flight may still request an aircraft whose
title=value was renamed or removed. - Regenerate fs9.cfg if FS2004 will not reach the menu. Close the simulator, open
%APPDATA%\Microsoft\FS9, and renamefs9.cfgtofs9.cfg.old. FS2004 creates a clean file at the next launch. This resets display, sound and control preferences, so keep the old file as a backup. Our FS2004 start-up troubleshooting for modern Windows covers the related configuration, permissions and default-flight checks. - Remove recently added aircraft temporarily. Move only third-party aircraft folders outside
FS2004\Aircraft, then test again. Add them back in small groups until the failure returns.
How do I repair the aircraft that causes the error?
A complete FS2004 aircraft normally has aircraft.cfg and at least one matching .air file at the top level of its folder. The correct arrangement is FS2004\Aircraft\AircraftName\aircraft.cfg, not an extra nested directory such as AircraftName\AircraftName\aircraft.cfg.
- Check
sim=. A line such assim=MyPlanerequiresMyPlane.airin the same aircraft folder. Do not include the file extension in the setting. - Check
model=. A blank entry uses themodelfolder;model=vcusesmodel.vc. That folder must contain a validmodel.cfgand the model files it references. - Make every
title=unique. Copying a variant and retaining another aircraft's title creates duplicate identities. Saved flights must refer to a title that still exists. - Validate the remaining suffixes. Entries such as
texture=blue,panel=wideandsound=custommust correspond to the appropriate suffixed folders when the package uses them. - Confirm FS2004 compatibility. An aircraft built only for FSX, Prepar3D or a newer Microsoft Flight Simulator cannot be made FS2004-compatible merely by copying its folder.
- Reinstall rather than mixing packages. Remove the damaged copy, retain any personal repaints separately, and install a clean FS2004 version. Our aircraft folder and missing-base-model checks cover the nesting and incomplete-package mistakes we see most often. For developer-level faults, use the detailed aircraft.cfg, AIR and model-reference checks.
Why can a repaint cause Aircraft Initialization Failure?
Most repaints are not complete aircraft; they contain textures and a replacement [fltsim.x] block for a specific base model. Installing that folder as a standalone aircraft leaves FS2004 without the required AIR file and model.
Place the texture folder inside the required base aircraft, copy the supplied [fltsim.x] section into that aircraft's existing aircraft.cfg, give it the next section number, and preserve the base aircraft's sim=, model=, panel= and sound= values. Never overwrite the entire configuration without first making a backup. Follow our FS2004 repaint installation procedure if the error began after adding a livery.
What if default FS2004 aircraft also fail?
If an untouched Microsoft aircraft fails with a newly generated fs9.cfg, the core installation is damaged or third-party files are affecting the whole simulator. Temporarily remove recent add-ons, then use the original installer or installation media to restore missing default aircraft files.
Do not substitute random copies of aircraft.cfg or AIR files from another package. Those files are matched to a particular flight model and folder structure; mixing them may clear one message while introducing incorrect handling or another loading failure.