How do I install add-on aircraft in FlightGear?
To install add-on aircraft in FlightGear, we usually download the aircraft package, extract it to an aircraft folder outside the main FlightGear program directory, then tell FlightGear where that folder is by adding it to the aircraft search path. If the folder structure is correct, the aircraft should then appear in the launcher’s aircraft list.
How FlightGear add-on aircraft installation works
FlightGear does not use a single universal “one-click installer” for most third-party aircraft. In practice, an add-on aircraft is normally a folder containing the aircraft model, panel, systems, sounds, liveries and a configuration file that FlightGear reads when it starts.
The important part is not just copying files somewhere at random. FlightGear has to know where that aircraft folder lives, and the folder itself must be extracted correctly.
What is the best place to put FlightGear aircraft?
We strongly recommend keeping add-on aircraft in a separate folder that you control, rather than mixing them into FlightGear’s own built-in aircraft directory. That keeps updates cleaner and makes troubleshooting far easier.
| Location | Good idea? | Why |
|---|---|---|
| Inside FlightGear’s main installation folder | Usually no | Program updates can overwrite files or make it harder to see what is stock and what is add-on. |
| Separate custom folder such as an “Aircraft” folder in Documents or another drive | Yes | Easier to manage, back up, remove and add to FlightGear’s search path. |
| Multiple separate aircraft folders | Yes | Useful if you want to organise aircraft by source, type or testing status. |
How to install add-on aircraft in FlightGear step by step
Download the aircraft package from a trusted source. If you need freeware downloads for simming in general, we keep our own library at Fly Away Simulation downloads.
Create a dedicated add-on aircraft folder. This can be anywhere convenient on your system, as long as you can find it easily later.
Extract the archive fully. Most aircraft come as a compressed archive, so do not leave it as a ZIP or similar file and expect FlightGear to read it directly.
Check the folder structure. When you open the aircraft’s main folder, you should see the aircraft files themselves, not another identical folder nested inside it. Double-nested folders are one of the most common reasons an aircraft does not show up.
Add that folder to FlightGear’s aircraft search path. In current FlightGear builds this is typically done in the launcher or settings area where additional aircraft folders or add-on paths can be added. Point FlightGear to the folder that contains your aircraft folders.
Restart or refresh FlightGear if needed. Some versions detect changes only after a restart.
Select the aircraft from the aircraft list. If the install is correct, it should now appear like any other aircraft.
What folder structure should I have?
This is where many installs go wrong. Your custom aircraft folder should usually look something like this in principle:
Your custom Aircraft folder > Aircraft name folder > aircraft files
What you do not want is this:
Your custom Aircraft folder > ZIP extraction folder > another aircraft name folder > aircraft files
If FlightGear is pointed at the wrong level, it may scan the folder and find nothing usable. The aircraft’s main folder normally contains its model and configuration files directly, not buried inside another redundant wrapper folder.
How do I add the aircraft folder to FlightGear?
The exact wording varies a bit between FlightGear versions, but you are generally looking for a setting in the launcher related to additional aircraft locations, add-on paths or aircraft search paths.
In broad terms, the process is:
Open the FlightGear launcher before starting a flight.
Find the add-ons or aircraft paths setting. This may be under settings, advanced options or a similar section depending on your build.
Add your custom aircraft folder, not necessarily the individual aircraft itself unless that is how your setup is organised.
Save the setting and let FlightGear rescan.
Search for the aircraft by name in the aircraft selector.
Some advanced users also set aircraft paths with command-line options. That works well, but for most people the launcher is simpler and less error-prone.
Why the aircraft may not appear in the launcher
If your add-on aircraft does not show up, the cause is usually one of a small number of issues rather than a broken simulator.
The aircraft is still compressed in a ZIP or other archive.
The folder is nested one level too deep after extraction.
FlightGear is pointed at the wrong folder.
The aircraft needs supporting files or shared dependencies that were not included.
The aircraft was made for a different era of FlightGear and is no longer fully compatible.
The aircraft folder name or file layout was changed accidentally during extraction.
FlightGear needs a restart before it rescans the aircraft paths.
Do all FlightGear aircraft work with every version?
No. That is one of the bigger gotchas with FlightGear add-ons.
Some aircraft are maintained actively and work well on recent builds. Others were designed for much older systems, older cockpit code or older instrument logic and may load with missing gauges, broken switches, errors in the log, or poor systems behaviour. If an aircraft installs correctly but still behaves strangely, compatibility is often the reason.
What if the aircraft includes extra folders or dependencies?
Some packages are self-contained and can simply be dropped into your aircraft directory. Others rely on shared libraries, common materials, instruments or other supporting packages.
If the download includes a readme, install notes or package instructions, follow those closely. In FlightGear, the aircraft itself may only be one part of the package, so copying only the visible aircraft folder can leave out the files it depends on.
Should I install aircraft into the default FlightGear Aircraft folder?
You can, but we usually advise against it unless you have a specific reason. A separate add-on folder is cleaner and safer.
If you put third-party aircraft into the simulator’s own folders, it becomes much harder to tell which files belong to FlightGear and which came from an add-on. That matters when you update, remove old content or diagnose a broken aircraft.
How to remove an add-on aircraft cleanly
Removing an aircraft is normally straightforward.
Close FlightGear.
Delete the aircraft’s folder from your custom aircraft directory.
Leave the search path in place if you still use that folder for other aircraft, or remove the path if you no longer need it.
Restart FlightGear and confirm the aircraft no longer appears.
Quick troubleshooting checklist
If you want the shortest route to a fix, check these in order:
Is the aircraft extracted? Not still zipped.
Is the folder structure correct? No unnecessary extra parent folder.
Did you add the right path? FlightGear must point to the folder containing the aircraft folders.
Did you restart FlightGear? Some changes are not picked up immediately.
Does the aircraft require extra packages? Read any included instructions.
Is the aircraft too old for your FlightGear build? A clean install does not guarantee compatibility.
The short version
For most installs, the winning method is simple: extract the add-on aircraft to a separate custom aircraft folder, add that folder to FlightGear’s aircraft search path in the launcher, then restart and select the aircraft. If it does not appear, the problem is usually the folder level, not the aircraft itself.