Skip to content
Microsoft Flight Simulator 5 min read

iniBuilds A350 OIS unavailable in MSFS: how do I fix it?

Adam McEnroe
In short

Fix the iniBuilds A350 OIS unavailable message in MSFS by checking power, equipment settings, updates, brightness, liveries and package conflicts.

In Microsoft Flight Simulator, the iniBuilds A350 OIS is usually unavailable because the aircraft is not fully powered or initialised, the OIS is disabled in aircraft configuration, or the package is outdated or conflicted. Apply stable electrical power, wait for loading to finish, enable the OIS, then update and test without third-party add-ons.

What does the OIS unavailable message mean?

The OIS, or Onboard Information System, has not entered its normal operating state. If both OIS displays are unavailable, we would first suspect aircraft power, incomplete initialisation, equipment configuration or damaged package files.

An unavailable page inside an otherwise working OIS is a different problem. Individual functions can depend on the installed A350 version, external data or features that are not modelled in that build.

SymptomMost likely causeFirst check
Both OIS displays show unavailablePower, initialisation or package problemLoad a ready-to-fly state and wait for the aircraft to finish loading
OIS works in a ready state but not cold and darkStartup sequence or insufficient electrical powerComplete the electrical and APU sequence
One display is blackBrightness or an individual display stateCheck that unit's brightness control
Only charts or one application are unavailableAccount, data connection or version-specific limitationCheck the relevant service and aircraft version
Failure began after an updateOld dependency, mixed files or add-on conflictUpdate, isolate and repair the aircraft package

How do I restore the iniBuilds A350 OIS?

  1. Identify what is unavailable. Check whether both complete OIS units fail or only one application. Do not reinstall the aircraft for a chart-only or single-page problem.
  2. Test a ready-to-fly aircraft state. Load the A350 on a runway or use its supplied ready state, then allow the cockpit to finish initialising. If the OIS works there, the installation is probably sound and the cold-and-dark sequence needs attention.
  3. Establish stable electrical power. Turn on the batteries and connect external power or start the APU as appropriate. Main cockpit screens can illuminate before every secondary system is ready, so allow the OIS time to initialise. Our A350 electrical power and cold-start procedure covers the complete sequence.
  4. Check the display brightness. A screen at minimum brightness can look dead even though the unit is running. Adjust the dedicated OIS control before cycling aircraft power.
  5. Check the equipment configuration. Open the aircraft's EFB or configuration interface and inspect its equipment options. If your installed build exposes an OIS setting, ensure the units are fitted or enabled, apply the change and reload the aircraft. If you use a saved aircraft state, test without it in case it restores the disabled setting.
  6. Update the complete A350 package. Close MSFS, update through the same installation channel used for the aircraft, and restart the simulator. Do not combine files from different releases or installation sources. Our summary of the A350 v1.1.1 OIS-related changes illustrates why OIS behaviour can differ between aircraft builds.
  7. Run a clean add-on test. Use a bundled livery and temporarily remove third-party A350 liveries, cockpit modifications and toolbar utilities. On PC, test with a clean Community folder while retaining the required A350 package if it is installed there. The package, cache and livery checks in our A350 conflict troubleshooting procedure also apply when cockpit systems fail to initialise.
  8. Repair or reinstall only after the clean test fails. Remove the A350 and its associated package components using the appropriate content manager or installer, restart MSFS, then install a fresh complete copy. If the failure started after a simulator update, follow our post-update aircraft compatibility checks before reinstalling unrelated content.

Why is the OIS black instead of showing unavailable?

A black OIS is usually an off, brightness or power symptom; an explicit unavailable message points more towards initialisation, configuration or software. Check brightness first, then compare the affected unit with the OIS on the other side of the cockpit.

If one unit works and the other does not, a simulator-wide network or chart-data failure is unlikely. Reload the aircraft after confirming the individual display control and equipment configuration.

Why are only OIS charts unavailable?

If the OIS itself opens but its charts do not, the core aircraft system is working. Check the chart-provider sign-in, entitlement and internet connection, then sign out and back in if the aircraft offers that option.

A chart-only failure does not normally justify deleting the A350. Likewise, a single unavailable application may be version-dependent; update the aircraft, but accept that a function not implemented in that build cannot be restored through power cycling.

When is a clean reinstall justified?

Reinstall the A350 when both OIS units remain unavailable in a ready-to-fly state, with stable power, a bundled livery, no optional add-ons and the latest complete package available through your installation channel. If the fault survives that reinstall, record the simulator edition, platform, A350 package version, livery, starting state and whether one or both units fail; those details distinguish a reproducible aircraft defect from a configuration problem.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members