Fix an X-Plane 12 add-on aircraft that will not load by checking compatibility, folders, plugins, dependencies and Log.txt errors.
An add-on aircraft usually will not load in X-Plane 12 because it targets an older simulator version, was extracted incompletely, has an incompatible aircraft plugin, or lacks a required component. Confirm X-Plane 12 support, reinstall the full package under Aircraft, test without third-party global plugins, then inspect Log.txt immediately after the failure.
What does the loading failure tell you?
The point at which the aircraft fails helps identify the cause before you start moving files or resetting X-Plane.
| Symptom | Likely cause | First check |
|---|---|---|
| Aircraft is absent from the selector | Wrong installation, missing .acf file or menu filtering | Use our checks for an aircraft missing from the selection screen |
| Error appears before the cockpit opens | Unsupported or damaged .acf file, missing files or version mismatch | Confirm the package explicitly supports X-Plane 12 |
| X-Plane hangs or closes while loading | Aircraft plugin failure, global plugin conflict or damaged installation | Test the aircraft without third-party global plugins |
| Aircraft loads with blank displays or dead systems | Its custom plugin did not start, activation is incomplete or the aircraft is unpowered | Check aircraft power and then Log.txt |
| Stock aircraft also fail | Simulator, graphics, preference or system-level problem | Repair X-Plane before troubleshooting the add-on |
How do I fix an X-Plane 12 aircraft that will not load?
- Test a stock aircraft first. Load one of X-Plane 12's included aircraft at a simple airport. If that also fails, the add-on is unlikely to be the root cause; remove third-party global plugins temporarily and repair the simulator's core files with its installer.
- Verify X-Plane 12 compatibility. An X-Plane 11 aircraft may appear in the menu yet fail when an older custom plugin or system tries to start. Check the package description and included documentation rather than assuming every
.acffile is forward-compatible. Our explanation of X-Plane 11 add-on compatibility with X-Plane 12 covers the differences. - Confirm that you are modifying the active installation. Multiple X-Plane copies are common, particularly after retaining an older version or making a backup. Follow our steps for finding the X-Plane 12 installation actually being launched.
- Install a freshly extracted copy. A typical location is
X-Plane 12/Aircraft/My Aircraft/My Aircraft.acf. Keep the suppliedobjects,plugins, cockpit and other folders with that.acffile. Do not run the aircraft from inside its archive, merge it into a stock aircraft, or place its aircraft-specific plugin under the globalResources/pluginsfolder. See the correct aircraft and mod folder layout if the package structure is unclear. - Check the complete package and its requirements. Some downloads are updates, liveries or expansion files rather than a complete aircraft. Others need a base package, supplied runtime, separate component or successful activation. Read the included documentation and make sure every archive part was downloaded and extracted.
- Check operating-system support. A custom plugin must include a compatible binary for Windows, macOS or Linux. Security controls can block an otherwise valid plugin, while older plugins may not support the processor architecture being used. Only approve blocked code when it came with a package you trust.
- Rule out a plugin conflict. Close X-Plane and move only third-party global plugin folders out of
Resources/pluginsto a temporary location; leave simulator-supplied components untouched. Test again, then restore third-party plugins individually. Keep any plugin supplied inside the aircraft's own folder where the developer placed it. - Read the log before reinstalling again. Open
Log.txtfrom the X-Plane 12 root folder immediately after the failed attempt. If the package still fails after the specific error has been addressed, remove its existing folder and extract a clean copy rather than overwriting old files.
Where is Log.txt, and what should I look for?
Log.txt is in the main X-Plane 12 folder and records the aircraft, plugins and resources loaded during the last session. Copy or inspect it before starting X-Plane again because the next launch replaces the previous session's log.
Search from the bottom upwards for the aircraft's folder name, its plugin name, ERROR, failed modules and missing files. The final line is not automatically the cause; it may only show what X-Plane was doing when another component failed.
- Unsupported or unreadable aircraft file: use a release intended for X-Plane 12 and download it again if corruption is possible.
- Repeated missing objects or resources: the archive is incomplete, the folder structure was changed, or a path uses letter case that does not match on a case-sensitive system.
- Aircraft plugin could not load: check operating-system support, security blocking, required components and processor compatibility.
- Errors affecting several aircraft: investigate global plugins, graphics drivers, simulator files and system resources instead of repeatedly reinstalling one aircraft.
Can an X-Plane 11 aircraft be converted for X-Plane 12?
Simple X-Plane 11 aircraft sometimes open in X-Plane 12, but loading successfully does not prove that the flight model, instruments or custom systems work correctly. Aircraft with compiled plugins need compatible plugin builds and usually require an update from their developer.
Work on a copy if you open or save an older aircraft in X-Plane 12. Do not overwrite your only original, because saving may make it unsuitable for the older simulator without fixing incompatible plugins.
What if the aircraft loads but the cockpit screens are blank?
Blank displays usually mean the aircraft is unpowered or its custom systems plugin failed, rather than the model itself failing to load. First apply external power or start the aircraft according to its checklist; some aircraft deliberately load cold and dark.
If power is available, check whether the aircraft's plugin appears in X-Plane's plugin management interface and inspect Log.txt for that plugin. Recheck activation and required components, and do not move the aircraft-specific plugins folder into X-Plane's global plugin directory.