Fix blank avionics screens in MSFS by checking electrical power, display dimmers, controller bindings, add-on conflicts and aircraft files.
Blank avionics screens in Microsoft Flight Simulator usually mean the aircraft’s avionics bus has no power, a display dimmer is at zero, or a controller is repeatedly sending an off command. If those checks pass, test a default aircraft without Community add-ons; one-aircraft failures normally indicate an outdated, conflicting or damaged package.
What does the black-screen pattern tell you?
The way the displays fail usually identifies where to start troubleshooting.
| What you see | Likely cause | Best first test |
|---|---|---|
| Every display is black after starting at a stand | Battery, generator, external power or avionics bus is off | Power the aircraft correctly or try a runway start |
| Cockpit lights work, but the PFD and MFD are black | Avionics bus is unpowered or display dimmers are down | Check the avionics master and each display’s brightness control |
| Only one display is black | Local brightness, display-source control or aircraft-specific fault | Turn up that unit’s dimmer and check display or reversion controls |
| Screens boot, then switch off | Power source was lost, battery is discharging or hardware sent an off command | Confirm a generator remains online, then test a fresh control profile |
| Only one aircraft is affected | Incorrect start-up state, outdated add-on, missing dependency or damaged installation | Test a default aircraft, then load the affected aircraft without companion mods |
| Several unrelated aircraft are affected | Global binding, third-party package, suspended session or incomplete update | Restart fully and test with minimal hardware and no Community packages |
| The panel display works but its popped-out window is black | Pop-out or rendering problem rather than aircraft power | Close and reopen the pop-out, then restart the simulator |
How to fix blank avionics screens in MSFS
Use this order in both MSFS 2020 and MSFS 2024 so that a simple power or brightness problem is not mistaken for a broken installation.
Supply proper electrical power. At a cold-and-dark stand, switch on the battery and connect an appropriate source: external power, an APU generator or engine-driven generators, depending on the aircraft. An external-power
AVAILABLEindication does not necessarily mean the source has been selected, and a generator switch cannot supply power until its engine or APU is running.In light aircraft, check the alternator or generator and the avionics master if fitted. In larger aircraft, verify that the required buses and bus ties are configured. Battery power alone may not feed every avionics bus and cannot sustain the aircraft indefinitely.
Raise every relevant display dimmer. PFD, MFD, engine, centre and standby displays may have separate controls. Flood lighting and integral panel lighting are not the same as display brightness, so an illuminated cockpit does not prove the screens are turned up.
Try one runway start. Load the same aircraft ready for departure. If its screens work there, the simulator and display rendering are probably sound; the fault is more likely a missed electrical step or saved aircraft state. Some complex add-ons preserve their own panel state, so use a ready or turnaround state from the aircraft’s tablet when one is provided.
Test a clean control profile. Search the affected device’s assignments for terms such as battery, avionics, alternator, generator, master, electrical and brightness. Exact command names vary between simulator and aircraft versions. Pay particular attention to physical toggle switches and rotary axes, which can send an off state or force brightness to zero as soon as the cockpit loads.
Disconnect extra controllers. Close the simulator, disconnect switch panels, spare throttles and other non-essential hardware, then test with only a mouse, keyboard and primary controller. Reconnect one device at a time. If the problem returns, rebuild that device’s profile rather than restoring all old assignments at once.
Restart the simulator completely. Do not resume a suspended session for this test. On Xbox, fully quit Microsoft Flight Simulator and restart the console; on PC, close the simulator and launcher before reopening them. This is especially useful when the fault appeared after an aircraft or simulator update.
Run a clean add-on test. On PC, move everything from the
Communityfolder to a temporary folder outside it, then test a default aircraft. Renaming an add-on while leaving it insideCommunitydoes not reliably disable it because the simulator may still scan the package. Our guide to managing Community-folder mods in MSFS 2020 explains the package workflow; the same isolation principle applies to MSFS 2024 even though its content handling differs.Repair only the affected content. Confirm that the simulator, aircraft and required avionics or framework packages have finished installing and updating. If one aircraft remains broken, remove and reinstall that aircraft before considering a full simulator reinstall.
Why are the screens black when the cockpit lights work?
Cockpit lighting and avionics are often connected to different electrical buses, so illuminated panels do not prove that the glass cockpit is powered.
A common mistake is switching on the battery and assuming the entire aircraft is live. The dome light, flood lights and several standby instruments may work while the avionics master is off or the main display bus remains disconnected. Check the electrical page or bus indications if the aircraft provides them.
If only one unit is dark, start with its local dimmer. Also check any display-source, display-transfer or reversionary controls and, where the aircraft models them, the relevant circuit breaker. Do not reset random breakers simply to make the screen light up.
Why do the avionics switch on and then go black?
Displays that boot and then die usually indicate either a disappearing power source or a controller command that arrives after the flight loads.
Watch the electrical system first. An aircraft may begin on battery power, then lose its screens because external power was disconnected before the APU or engine generator took over. Generator voltage, bus voltage or battery-discharge indications will usually reveal this.
If electrical power remains stable, test the controls. Yokes, throttle quadrants and home-cockpit panels commonly have duplicated battery or avionics assignments. A brightness axis can cause the same symptom by continually commanding its minimum value.
What if only one aircraft has blank displays?
If default aircraft work normally, treat the affected aircraft and its dependencies as the fault until another test proves otherwise.
Remove liveries, panel replacements, avionics mods and aircraft-specific utilities before removing the base aircraft.
Check whether the aircraft expects a particular power-up sequence or selectable panel state.
Confirm that all dependencies supplied with the aircraft are installed and compatible.
Reinstall the package if files may be incomplete or damaged.
An extra nested folder, incomplete installer run or missing dependency can leave an add-on partly functional. Our aircraft add-on installation and package-structure guide covers those checks without requiring a complete simulator reinstall.
A lit screen with frozen knobs, greyed-out fields or an unresponsive cursor is not a blank-screen power fault. Use our separate troubleshooting for powered Garmin and FMS controls that do not respond in MSFS 2024.
What if every aircraft has black screens?
Black displays across several unrelated aircraft point to a simulator-wide control, content or session problem rather than several aircraft failing at once.
On PC
Test a default aircraft on a runway with an empty Community folder and only essential controllers connected. If Safe Mode is offered after an abnormal exit, it is also useful for a clean-content test. Restore packages and hardware in small groups until the fault returns.
If the problem began directly after a graphics-driver change or rendering override, return that change to its previous or default state for one test. This should be a late step, not the first response to a fault isolated to one aircraft.
On Xbox
Fully quit Microsoft Flight Simulator rather than resuming it, restart the console and test a default aircraft. If the fault followed a content installation, remove or disable the most recent package through the simulator’s content management and retest.
If blank displays accompany crashes, missing packages or other simulator-wide faults in MSFS 2024, follow our broader checks for package conflicts, damaged content and cache-related instability. Clearing the rolling cache alone is not a primary avionics fix because it mainly stores scenery data.
How can I stop blank avionics screens returning?
Separate control profiles and disciplined add-on testing prevent most repeat failures.
Keep different profiles for light aircraft, airliners and switch-panel hardware.
Install or update add-ons in small batches so a conflict is easy to identify.
Retest important aircraft without optional liveries and panel mods after simulator updates.
Allow content operations to finish before launching a flight or shutting down the simulator.
Use a full restart when cockpit state, controls or content behave abnormally.