How do I fix Aircraft Initialization Failure in FS2004?

FS2004 shows “Aircraft Initialization Failure” when a flight requests an aircraft the simulator cannot load. Start a new flight with an untouched stock aircraft. If that works, repair the named add-on, repaint or saved flight; if stock aircraft also fail, reset fs9.cfg and restore damaged default files.

What does Aircraft Initialization Failure mean?

In Microsoft Flight Simulator 2004 (FS9), this message means the selected or start-up flight refers to an aircraft that FS2004 cannot initialise. The aircraft named in the message is the best clue: it identifies the package or livery to check first.

A saved flight records an aircraft identity that corresponds to a title= entry in aircraft.cfg. Loading fails when that title no longer exists or the associated aircraft has a missing AIR file, invalid model reference, incomplete base package or incorrect folder structure.

Will a stock flight fix Aircraft Initialization Failure?

A stock flight fixes the error when FS2004’s default or saved flight still requests an add-on that has been removed or renamed. It also provides the quickest diagnostic test: if a fresh flight using an untouched Microsoft aircraft loads, the simulator’s core aircraft system is working.

The useful stock flight fix is to select a default aircraft such as the Cessna Skyhawk 172SP, create a new flight, save it and make that the start-up flight. Do not open the old saved flight during this test. If the stock aircraft works but the original aircraft does not, reinstalling the whole simulator is unnecessary; repair the affected add-on instead.

How do I get it to work?

1. Write down the aircraft named in the error. Also note whether the failure occurs at start-up, after opening a saved flight or only after selecting a particular livery. Graphics, weather and scenery settings are not the first place to look when one aircraft is named.
2. Test a completely new flight. Choose an untouched stock aircraft rather than a third-party model or an old saved flight. If it loads, replace the stale start-up flight and continue with the aircraft-specific checks below.
3. Remove the suspected add-on temporarily. Close FS2004 and move that aircraft’s complete folder outside FS2004\Aircraft. Do not move Microsoft’s default aircraft. Start FS2004 with the fresh stock flight, then reinstall the add-on from a clean copy if the error has gone.
4. Regenerate fs9.cfg if FS2004 fails during start-up. Close the simulator, enter %APPDATA%\Microsoft\FS9 in Windows Run or File Explorer, and rename fs9.cfg to fs9.cfg.old. FS2004 creates a new configuration file on its next launch. Renaming is safer than deleting because the old file remains available for comparison.
5. Restore preferences only after testing. A fresh fs9.cfg resets settings such as controls, display and sound options. Test a stock flight before copying any settings back; otherwise the original fault may be reintroduced.
6. Check the installation if stock aircraft still fail. Temporarily remove recently added third-party aircraft and restore missing default files from the original FS2004 installation source. A reinstall is a last resort, not the first response to one broken add-on.

Repairing the aircraft that causes the error

A working FS2004 aircraft normally has aircraft.cfg and at least one corresponding .air file at the top level of its own folder. A mistake we see constantly is an extra wrapper directory created during extraction: FS2004\Aircraft\AircraftName\AircraftName\aircraft.cfg will not work as intended.

The correct structure is FS2004\Aircraft\AircraftName\aircraft.cfg. Use our guide to finding the FS2004 Aircraft folder and spotting incorrectly nested packages if the installation path is uncertain.

Make a backup before changing any configuration. Windows may hide known file extensions, so confirm that an edited file has not become aircraft.cfg.txt. Our safe aircraft.cfg editing procedure explains the backup, naming and plain-text editing precautions.

• Check sim=. If a variant contains sim=MyPlane, the same aircraft folder must contain MyPlane.air. The setting does not include the .air extension.
• Check model=. A blank value uses the model folder, while model=vc uses model.vc. The selected folder needs a valid model.cfg whose model reference points to the required model file.
• Check title=. Every installed variation should have a unique title. If an old saved flight used that title, changing it breaks the saved flight’s aircraft reference even when the rest of the package is valid.
• Validate folder suffixes. Values such as texture=blue, panel=wide and sound=custom refer to texture.blue, panel.wide and sound.custom. Blank values use the unsuffixed folders.
• Inspect panel aliases. A panel folder may contain its own files or point to another aircraft. A missing target, misplaced panel.cfg or broken alias can stop an add-on loading correctly; see how to locate panel.cfg and verify panel folder references.
• Confirm simulator compatibility. An aircraft made only for FSX, Prepar3D or a later Microsoft Flight Simulator cannot be converted for FS2004 simply by placing it in the FS9 Aircraft folder.

Repaints and missing base aircraft

Most repaints are not complete aircraft. They provide a texture folder and a [fltsim.x] block for a specific base model, but not the AIR, model, panel and sound files required to initialise that model.

Install the texture folder inside the required base aircraft and add the supplied entry to that aircraft’s existing aircraft.cfg. Give it the next unused sequential [fltsim.x] number, keep title= unique, and preserve the base model’s correct sim=, model=, panel= and sound= values.

A missing texture normally causes a visual problem rather than an initialisation failure. The failure usually begins because the repaint entry points to a non-existent AIR file, model or base package. Never replace the entire aircraft.cfg with a repaint author’s example without backing up and merging the required entry carefully.

When stock FS2004 aircraft fail too

If an untouched Microsoft aircraft still fails with a newly generated fs9.cfg, the problem is broader than one saved flight or repaint. Default aircraft files may be missing, or a third-party installation may have replaced a shared or stock file.

Move only third-party aircraft out of FS2004\Aircraft, test again with the clean configuration, and restore damaged default files through the original FS2004 installer or installation media. Do not borrow random AIR or configuration files from another aircraft: those files are matched to a particular model and flight dynamics, and mixing them can replace the error with incorrect handling or another loading failure.