How do I download and install an ATR 42-300 in FS2004?

Our closest ATR 42-300 base package is for FSX, not a native FS2004 release, so we would not install it in FS9. For a dependable FS2004 ATR download, use the complete FS2004 ATR 42-500 package, or install a 42-300 archive only when its description explicitly names FS2004.

Which ATR download should I choose for FS2004?

Choose the ATR 42-500 package when you want a complete aircraft known to be intended for FS2004; choose a 42-300 only if the file is specifically labelled for FS2004 or FS2004/FSX.

How can I tell whether the download is a complete aircraft?

A complete FS2004 aircraft normally includes aircraft.cfg, an .air file and model, panel, sound and one or more texture folders. A repaint usually contains only a texture folder and a block of text to add to aircraft.cfg.

A mistake we see constantly is installing a repaint as though it were the aircraft itself. Our advice on identifying complete FS2004 downloads and repaints explains the distinction. Do not assume an ATR 42-300 repaint will fit an ATR 42-500; the model shape, texture mapping and configuration can differ.

Can the FSX ATR 42-300 be converted to FS2004?

An FSX aircraft cannot be made FS2004-compatible merely by moving its folder or editing the simulator name in aircraft.cfg. The model, gauges and configuration may use FSX-specific formats that FS9 cannot load.

Some older packages support both simulators, but the documentation must say so or provide separate FS2004 files. If a download is listed only for FSX, treat it as incompatible with FS2004 rather than risking crashes, an invisible exterior model or a broken panel.

How do I install a compatible ATR 42 in FS2004?

A compatible ATR installs by placing its complete aircraft folder under Flight Simulator 9\Aircraft, then merging any supplied gauges and effects into the matching FS9 folders. The broader FS2004 add-on installation procedure covers unusual package layouts.

1. Close FS2004 and make a backup. Back up any existing aircraft folder or shared file that the package proposes to replace.
2. Extract the archive first. Unzip it into a temporary folder rather than copying files directly from the compressed archive.
3. Find the actual aircraft folder. Open any outer wrapper folders until you reach the folder containing aircraft.cfg and the .air file.
4. Copy that folder into FS9. Place it under Flight Simulator 9\Aircraft. After copying, the expected structure is Flight Simulator 9\Aircraft\[aircraft folder]\aircraft.cfg, not another duplicate folder level deeper.
5. Install the supporting files. If the archive supplies separate Gauges or Effects folders, merge their contents into the corresponding folders in the main FS2004 directory. Keep gauge .cab files intact and do not overwrite existing shared files without a backup.
6. Start FS2004 and select the aircraft. Check the manufacturer, aircraft model and variation fields in the aircraft selection screen; their wording comes from the package's aircraft.cfg and may not match the ZIP name exactly.

If the download uses an installer, run it only after confirming that it explicitly supports FS2004, and point it at the main Flight Simulator 9 folder rather than the Aircraft subfolder.

Why does the ATR not appear or work in FS2004?

An ATR that fails to appear is usually nested one folder too deep, missing its base model or not actually built for FS2004.

• No entry in the aircraft menu: confirm that aircraft.cfg and the .air file sit directly inside the aircraft's folder. Check that the sim= entry refers to the supplied .air filename.
• Only a texture folder was supplied: this is a repaint and requires the precise base aircraft stated in its documentation.
• Invisible aircraft or a crash while loading: remove the package and verify its simulator version. An FSX-only model is a likely cause.
• Blank panel or missing instruments: copy the supplied gauge files into the FS9 Gauges folder, leaving any .cab archives unopened. Some panels also depend on gauges from another required package.
• Missing livery: in each [fltsim.x] entry, a value such as texture=example requires a matching texture.example folder.
• Files copied but changes do not stick: Windows may redirect writes when FS2004 is installed under a protected system folder. Extract elsewhere, then copy with suitable permissions and check that the files reached the real FS9 directory rather than VirtualStore.