Find why landing lights do not illuminate the runway, then isolate power, bindings, add-on effects, graphics and scenery faults.
In a flight simulator, landing lights illuminate a limited patch of ground, not the whole runway from approach distance. If no beam appears while taxiing at night, common causes are missing electrical power, a wrong switch or binding, a broken add-on effect, or a renderer/scenery surface that does not receive projected light.
Across Microsoft Flight Simulator, FSX, Prepar3D and X-Plane, the quickest diagnosis is to separate an aircraft fault from a global graphics or scenery fault. A mistake we see constantly is treating a visible glowing lamp as proof that its beam is working.
Lamp glow versus projected light
A glowing lamp is not proof that the simulator is projecting light onto the ground. The visible bulb, bloom or flare may be one effect, while the cone that illuminates pavement is a separate projected light.
Older simulators and converted aircraft may mix legacy effect files with newer dynamic lighting. That can leave a bright lamp on the model but no light pool beneath it. Retractable landing lights introduce another trap: the light can be switched on electrically while its housing remains stowed or points in the wrong direction.
What does each symptom mean?
The exact symptom usually identifies which part of the lighting system has failed.
| Symptom | Likely cause | Best next test |
|---|---|---|
| No glowing lamp and no ground light | Electrical power, switch position, failure state or control binding | Operate the cockpit switch with the mouse and check the aircraft's electrical buses |
| Lamp glows but no ground pool appears anywhere | Missing projector, legacy effect, model configuration or renderer incompatibility | Try a default aircraft at the same location |
| Default aircraft works but one add-on does not | Add-on installation, dependency or aircraft configuration fault | Restore the original add-on files and required effects |
| The aircraft works at other airports | Custom runway material, elevated surface or scenery compatibility problem | Test on a default runway |
| Light appears externally but is weak from the cockpit | Camera exposure, windscreen tint, reflections or cockpit lighting | Dim panel and flood lighting, then compare internal and external views |
| The beam appears only close to the ground | Normal beam range or mounting angle | Test while stationary on a dark taxiway |
How do I isolate a landing-light fault?
A controlled aircraft-and-airport comparison will locate the fault faster than changing several graphics settings at once.
- Create a dark test: use full night, clear weather, a flat default airport and a default aircraft loaded with its engines and electrical systems running. Stop on a taxiway or runway away from bright apron floodlights.
- Use the virtual cockpit switches: turn each landing light off and on with the mouse rather than a keyboard, controller or hardware panel. Check separate left, right, nose and retractable-light controls where fitted.
- Confirm electrical power: make sure the generators or alternators are online and the relevant buses are powered. A battery switch alone may not provide enough power, and detailed add-ons can model load shedding or failed bulbs.
- Inspect the aircraft externally: look separately for a glowing lamp and a pool of light on the pavement. Compare the taxi lights; if they illuminate the ground but the landing lights do not, the renderer can probably project light and the fault is aircraft-specific.
- Swap aircraft without moving: load a standard aircraft at the same airport, time and weather. If it works, leave the global graphics settings alone and repair the affected add-on.
- Swap airports: test the same aircraft on a default runway. A failure confined to one custom airport points to its surface materials or scenery geometry rather than the aircraft.
- Check bindings and failures: remove duplicate light assignments and temporarily disable simulated failures. A cockpit switch that snaps back or changes without input usually indicates a latching hardware switch or conflicting assignment. For Microsoft Flight Simulator, follow our MSFS light-binding and switch-conflict checks.
- Return to a clean rendering setup: restore supported graphics defaults and disable third-party shader or lighting modifications for the test. Change one item at a time so that the result identifies the cause.
If only an add-on fails, reinstall the correct package and its dependencies before editing configuration files. Legacy FSX aircraft often reference an effect name in aircraft.cfg, commonly under [LIGHTS], which must correspond to the required .fx file in the simulator's Effects folder. Our FSX add-on light-effect troubleshooting covers those checks in detail.
Do not copy FSX effect files into Microsoft Flight Simulator, X-Plane or modern Prepar3D aircraft. Their lighting systems and package formats differ, and a brightness modification will not repair a missing projector or incompatible model.
When is weak runway illumination normal?
Weak illumination is normal when the runway is beyond the useful range or angle of the aircraft's beam. Landing lights are conspicuity and short-range illumination tools, not searchlights capable of lighting an entire runway from several miles away.
- A landing-light beam is aimed farther ahead than a taxi light, so its brightest area may not be visible directly beneath the nose.
- Automatic exposure can hide the beam at dusk, under apron floodlights or when bright cockpit displays dominate the view.
- Fog, cloud and heavy precipitation scatter the light and can make the beam visible while reducing the detail seen ahead.
- A raised nose attitude, sloping runway or unusually high-mounted light can move the brightest patch outside the current camera view.
Test at walking or taxiing speed in full darkness. If a defined patch appears ahead of the aircraft, the light is functioning even if it does little to the runway during the earlier stages of an approach.
Are runway lights controlled by aircraft landing lights?
No. Runway edge, threshold, centreline and approach lights belong to the airport scenery; the aircraft's landing lights only illuminate nearby surfaces. If the whole airport lighting system is missing, troubleshoot the scenery, time-of-day logic or simulator settings instead. Our night-landing visibility checklist explains the other lighting and visual-reference checks that matter after the aircraft beam is working.