Learn how to install Project Airbus aircraft in FSX or Steam Edition, identify base packs and repaints, and fix missing models or effects.
Project Airbus is the name of a freeware aircraft-development group best known for detailed Airbus models. To install one in FSX or FSX: Steam Edition, extract the archive, copy the complete aircraft folder into SimObjects\Airplanes, then place any separate Effects or Gauges files in the matching FSX folders as documented.
What exactly is Project Airbus?
Project Airbus is not an official Airbus product, a simulator or one universal installer. The name refers to freeware Airbus models produced by the group, as well as complete aircraft packages and repaints assembled around those models.
Packages carrying the Project Airbus name can differ substantially. One may contain a ready-to-fly aircraft, while another provides only a base model, a texture set or a panel added by another developer. The Project Airbus name alone does not guarantee a virtual cockpit, FMC, sound set or particular flight deck.
How can I tell whether I have a full aircraft or a repaint?
The contents of the extracted archive reveal what type of package you have.
| Package type | Typical contents | What to do |
|---|---|---|
| Complete aircraft | aircraft.cfg, an .air file and model, panel, sound and texture folders | Copy the complete aircraft folder to SimObjects\Airplanes. |
| Base model | The core aircraft files, sometimes with one basic livery | Install it before adding repaints made for that exact model and engine variant. |
| Repaint only | A texture.name folder and a supplied [fltsim.x] entry | Add it to the matching installed base aircraft; it cannot work by itself. |
| Installer package | An executable plus documentation or installation files | Follow its manual and confirm that it targets the correct FSX installation. |
How do I install a complete Project Airbus aircraft?
A complete Project Airbus package installs like another manually packaged FSX aircraft, but its wrapper folders and shared effects require careful checking.
- Read the included documentation. It should identify the required simulator, base model, engine variant and any separate panel or effects files. Prefer a package explicitly labelled for FSX rather than FS2004 or FS9.
- Find the active FSX root folder. Common boxed-FSX and Steam locations on 64-bit Windows are
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator XandC:\Program Files (x86)\Steam\steamapps\common\FSX. Your path will differ if FSX or the Steam library was installed elsewhere; the correct root containsfsx.exe. - Extract the archive to a temporary folder. Do not open or run the aircraft directly from its ZIP file. Inspect the extracted folders before copying anything.
- Copy the actual aircraft folder. Place the folder containing
aircraft.cfgdirectly insideFSX\SimObjects\Airplanes. A mistake we see constantly is double nesting, such asAirplanes\Package Name\Project Airbus A320\aircraft.cfg; the folder directly underAirplanesshould normally be the one containing the configuration file. - Install shared files only where instructed. Copy the contents of a separate top-level
Effectsfolder intoFSX\Effects, and separate gauge files intoFSX\Gaugeswhen the documentation requires it. Leave gauges already supplied inside the aircraft's panel folder there. This worked Project Airbus A321 package with separate Effects files shows the usual arrangement, while our wider FSX add-on folder guidance covers other bundled file types. - Start FSX and select the aircraft. Look under Airbus, Project Airbus or the manufacturer name defined by the package. Enable
Show all variationsin the aircraft selector if only one livery is visible.
Back up files before approving an overwrite, particularly if another package has already installed a gauge, effect or modified configuration file with the same name.
How do I install a Project Airbus repaint?
A Project Airbus repaint works only with the exact base model for which it was created, including the specified aircraft and engine or model variant.
- Install the required base aircraft first. A repaint for one model or engine variant should not be forced onto a different variant simply because both are from the same Airbus family.
- Copy the texture folder into the base aircraft folder beside its existing texture folders.
- Back up and edit
aircraft.cfg. Append the supplied[fltsim.x]block and changexto the next consecutive unused number. Do not replace the entire configuration file unless the instructions explicitly require it. - Check the references. A line such as
texture=namemust matchtexture.name;model=variantmust matchmodel.variant; andsim=must match the aircraft's.airfilename without the extension.
This example separating an A321 base aircraft from its additional Project Airbus liveries illustrates why a texture download alone may not appear in FSX.
What if the package uses an installer?
An installer can automate the same folder placement, but older installers may default to the boxed-FSX path even when FSX: Steam Edition is installed.
When asked for the simulator location, select the root folder containing fsx.exe, unless the package specifically asks for SimObjects\Airplanes. After installation, verify that the aircraft physically exists in the active FSX folder. The Project Airbus A319 package combining an installer and installation manual is an example of why package-specific instructions still matter.
Why does the Project Airbus aircraft not appear in FSX?
A missing aircraft is usually caused by the folder structure, a repaint without its base model or an invalid reference in aircraft.cfg.
- Wrong folder level: confirm that
aircraft.cfgis inside the aircraft folder directly underSimObjects\Airplanes. - Wrong FSX installation: Steam libraries and multiple FSX installations can leave files in an unused copy of
SimObjects\Airplanes. - Repaint without a base model: a texture folder and
[fltsim.x]text do not constitute a complete aircraft. - Broken configuration entry: check that each
[fltsim.x]section has a uniquetitle=value and validsim=,model=andtexture=references. - Aircraft selector filtering: enable all variations and search under the manufacturer and type values specified in
aircraft.cfg. - FS2004 package in FSX: some older models may load partially, but incompatible gauges, materials or model features can fail. Use an FSX-prepared package where available.
White or invisible surfaces usually indicate a missing texture, an incorrect texture reference or a repaint paired with the wrong model. Missing lights, smoke or other visual effects normally mean the supplied .fx files were not copied into FSX\Effects. Blank gauges point instead to missing or incompatible panel dependencies.
Does Project Airbus include a virtual cockpit or FMC?
No, the Project Airbus name by itself does not promise a virtual cockpit or FMC. Many packages centre on the exterior aircraft model and pair it with a default, two-dimensional or separately merged panel; other releases add a custom panel or flight-management functions.
Check the package description and screenshots before installation. If the exterior model works but there is no virtual cockpit, that may be the intended configuration rather than an installation fault.