How do I install and update the Zibo 737-800 in X-Plane 12?

For a Zibo 737 X-Plane 12 download, use the official Zibo Mod release thread, choose the newest full package explicitly labelled for XP12, then apply only its matching XP12 patch if required. Extract B737-800X to X-Plane 12/Aircraft; never install an XP11 build or a patch-only archive as the complete aircraft.

Zibo 737 X-Plane 12 download: which archive should I choose?

The authoritative download location is the Zibo Mod project’s B737-800X information, installation and download-links thread in the X-Plane.org Forums. Use only the files linked by the project maintainers there; unofficial mirrors may contain an old full package, a patch without its required base or files altered by a third party.

The official distribution normally separates the complete aircraft from smaller fixes. The folder name B737-800X alone does not prove that an archive supports X-Plane 12 because XP11 packages can use the same folder name.

The XP12 full archive expands to an aircraft folder named B737-800X. Some extraction utilities add an outer directory named after the archive; if that happens, open it and copy the inner B737-800X folder rather than preserving the extra wrapper.

How to install Zibo 737 in X-Plane 12

Install the complete XP12 package as a standalone aircraft at X-Plane 12/Aircraft/B737-800X.

1. Close X-Plane 12. Aircraft and plugin files should not be replaced while the simulator is running.
2. Find the active X-Plane installation. Open the directory containing the X-Plane 12 executable, then its Aircraft folder. Check this carefully if you have Steam and standalone installations, or copies on several drives.
3. Extract the full archive to a temporary location. Do not open the aircraft from inside the ZIP file. Our folder, extraction and backup guidance for X-Plane add-ons covers the same file-management rules in more detail.
4. Locate the extracted B737-800X folder. This is the folder that contains the aircraft’s .acf file and supporting directories, including its aircraft-local plugins folder.
5. Copy that folder into Aircraft. The finished path must be X-Plane 12/Aircraft/B737-800X.
6. Check for double nesting. Open the installed folder. You should immediately see the .acf file and aircraft folders, not another directory named B737-800X.
7. Launch X-Plane 12 and select the Zibo aircraft. Laminar Research’s default 737 remains a separate aircraft and must not be overwritten.

A layout such as Aircraft/B737-800X/B737-800X is wrong. Move the inner folder up one level so that the .acf file sits directly inside the final B737-800X directory.

Leave Zibo’s included plugins inside the aircraft folder. Moving them to X-Plane 12/Resources/plugins can stop the tablet, systems or cockpit controls from working correctly.

How to update Zibo 737

Choose the update from the installed base version and the requirements in the official XP12 release notes, not simply from the highest patch number.

1. Record the installed version. Load the working aircraft and note the version shown by the Zibo tablet or the version display identified by the project documentation. Do not rely on an old ZIP filename left in your Downloads folder.
2. Check the latest XP12 release notes. Confirm the required X-Plane branch, full-package baseline and whether the patch is cumulative or depends on an earlier fix.
3. Choose full package or patch. Use a fresh full package if this is a first install, the existing aircraft came from XP11, its version is unknown or the required baseline does not match. Use the patch only when the release notes explicitly support your installed base.
4. Back up personal content. Save liveries and any documented user configuration you intend to retain. Keep the backup completely outside Aircraft, or X-Plane may detect it as a second aircraft. Our guide to installing and preserving Zibo liveries explains the correct livery layout.
5. Extract the patch separately. The patch archive presents a B737-800X folder or the corresponding aircraft contents. Do not run it as a standalone aircraft.
6. Merge the patch with the installed folder. Copy its B737-800X contents into X-Plane 12/Aircraft/B737-800X, preserve the directory structure and overwrite matching files. Do not create B737-800X/B737-800X.
7. Restart and verify. Launch X-Plane 12, load the Zibo 737 and compare the tablet’s version readout with the target version in the release notes. Check Log.txt if the aircraft-local plugins fail to initialise.

On macOS, Finder’s whole-folder Replace operation can remove destination files that are not included in a small patch. Merge the patch contents into the existing aircraft folder; do not replace the complete aircraft directory with the smaller patch directory.

Is there an official Zibo 737 updater?

There is no project-supported official Zibo updater application; the supported process is to install the full package and patches manually according to the project’s release notes.

Programs described as a Zibo Updater are third-party tools, not the authoritative source for releases. They may be convenient, but their compatibility with a particular XP12 package, patch format or installation path cannot be assumed.

• Check compatibility first: the updater must explicitly support X-Plane 12 and the release branch you are installing.
• Confirm the selected simulator path: it should point to the active X-Plane 12 installation, not an XP11 copy or an unused installation on another drive.
• Record the starting version: compare the aircraft’s own version display with the updater’s proposed target.
• Make an external backup: copy B737-800X outside the Aircraft directory before allowing the tool to modify files.
• Prefer manual installation when uncertain: if the tool cannot identify the required full-package baseline, patch prerequisites and target version, use the project’s documented manual process instead.

If an updater leaves mixed or incomplete files, do not continue layering patches over them. Restore the backup or perform a clean full-package installation.

When should I perform a clean Zibo installation?

A clean installation is the safer choice after a major base-package change, an unknown update history or faults that began after applying patches.

Test a clean aircraft before restoring liveries or configuration files. An obsolete preference file can recreate the same fault even when the aircraft itself was installed correctly.

Why is the Zibo 737 missing or not working after installation?

Most failed Zibo installations are caused by double nesting, an XP11 package, an incomplete extraction, mixed patch files or installation into the wrong X-Plane copy.

• Aircraft missing from the selection screen: verify that an .acf file is directly inside Aircraft/B737-800X and that you launched the X-Plane installation you modified.
• Two Zibo aircraft appear: remove old copies and backups from every folder beneath Aircraft.
• X-Plane reports an incompatible or damaged aircraft: confirm that the full package is explicitly for XP12 and reinstall it before applying the matching patch.
• Tablet, displays or cockpit controls are dead: make sure the aircraft-local plugins directory is intact, then inspect Log.txt for plugin loading errors.
• Files are blocked on macOS: review the operating system’s security message and approve only components obtained through the official project distribution, then restart X-Plane.
• The fault appears only in an X-Plane beta: verify that the Zibo release notes declare support for that simulator branch.

Once the aircraft loads correctly, our Zibo tablet, controls, IRS and FMC setup guide covers the initial configuration needed before flight.

Does a Zibo update also update the FMC navigation data?

No. Updating the Zibo aircraft does not update X-Plane 12’s navigation database or AIRAC cycle.

If the FMC works but lacks an expected waypoint, SID or STAR, treat that as a navdata issue rather than reinstalling the aircraft. Follow our instructions for checking and updating the X-Plane AIRAC cycle separately.