Make safer night landings in a flight simulator with a stable approach, correct lighting, instrument cross-checks and clear go-around limits.
To make a safe night landing in a flight simulator, brief the runway and missed approach, dim the cockpit, use an instrument-guided descent where available, verify the runway visually, and stabilise early. Hold the correct approach speed and glide path, flare using runway perspective, and go around whenever alignment, speed or visual references become doubtful.
In our Aviation & Real-World Flying guidance, we use the same priorities as real night operations: preparation, instrument cross-checking and disciplined go-around decisions. Darkness removes many peripheral height cues, so a runway that looks clear can still produce a dangerously low or unstable approach.
How do you set up for a safe night landing?
A safe night approach begins before descent, with the runway, weather, navigation equipment and missed approach prepared.
- Choose the runway and check conditions. Review wind, visibility, cloud, runway length, airport elevation and available lighting. Prefer a runway with reliable approach guidance and avoid adding a strong crosswind or short runway unless that is the skill being practised. Some simulators model pilot-controlled lighting; others illuminate airports automatically or use different radio controls.
- Brief the approach and go-around. Know the final approach course, minimum altitude, expected glide path, touchdown zone and initial missed-approach track. Identify nearby parallel runways and taxiways so that rows of blue taxiway lights are not mistaken for a runway.
- Set the instruments correctly. Enter the local QNH or altimeter setting, tune and identify the required navigation aid, select the correct CDI or navigation source, and confirm any GPS procedure is loaded in the proper sequence. Set useful heading and altitude references before workload rises.
- Dim the cockpit. Keep instruments readable without flooding the cockpit with light. Overbright panels and displays reduce the ability to see faint runway and terrain cues. Configure the aircraft's external lights for the phase of flight; our guide to navigation, beacon, strobe and landing-light functions explains what each system is intended to do.
- Stabilise early. Establish the landing configuration, trim, final approach speed and normal descent rate without large power or pitch changes. For a three-degree path, groundspeed multiplied by roughly five gives a useful descent-rate cross-check in feet per minute, although the aircraft's own procedures take priority.
- Confirm the runway visually. Runway edges are primarily white, threshold lights facing the approach are green, runway-end lights are red, and taxiway edges are blue. A four-light PAPI normally shows two white and two red on the correct path; more red means low and more white means high.
- Flare from the normal sight picture. Near the threshold, shift the view farther down the runway and use peripheral edge-light movement to judge height. Do not use the landing-light beam as an improvised height gauge. After touchdown, maintain directional control and use the aircraft's normal braking, spoiler and reverse-thrust procedures; see our runway stopping and rollout guidance for the next phase.
Which approach is safest at night?
A correctly configured instrument approach provides the strongest protection against night visual illusions, even when the weather is technically clear.
| Approach | Choose it when | Main caution |
|---|---|---|
| ILS | The runway has a usable ILS and you want precise lateral and vertical guidance. | Verify the frequency, inbound course, navigation source and localiser/glideslope capture rather than assuming the autopilot has followed them. |
| RNAV or other instrument approach | The aircraft, navigation database and runway support the selected procedure. | Not every procedure supplies a usable vertical path. Observe the published step-down altitudes and minima. |
| Visual approach with PAPI or VASI | Visibility is good, the runway is positively identified and continuous visual guidance is available. | Dark terrain, water or sparse lighting can make the aircraft drift below the proper path without appearing obviously low. |
Microsoft Flight Simulator pilots can use our MSFS 2024 ILS setup and capture procedure when instrument guidance is available. For a visual arrival, follow the detailed method for judging runway alignment, PAPI indications and glide path, but keep checking the flight instruments until touchdown is assured.
Why do night landings look different?
Night landings feel harder because darkness removes the texture and peripheral references normally used to judge distance, height and sink rate.
- Black-hole approach: A bright runway surrounded by dark terrain or water provides too little information for reliable height judgement and can draw the aircraft below the intended path.
- Runway-width illusion: A narrow runway can make the aircraft seem higher than it is, encouraging a low approach; an unusually wide runway can produce the opposite effect.
- Lighting intensity: Very bright runway lights can make the airport appear closer, while dim lights can make it appear farther away. Use the glideslope, PAPI and instruments rather than apparent brightness.
- Simulator rendering: Exposure, bloom, display brightness and scenery quality can hide terrain or exaggerate lights. If visual guidance is missing or conflicts materially with a correctly configured instrument path, go around or use another runway instead of forcing the landing.
When should you go around at night?
Go around whenever the aircraft is not stable or the runway environment cannot be identified and maintained with confidence.
- The runway, not merely the airport lighting, is not positively identified.
- Airspeed, sink rate, configuration or alignment requires aggressive corrections.
- The approach remains below the proper visual or instrument glide path.
- Visual references disappear because of cloud, glare, fog or scenery limitations.
- The aircraft drifts towards a taxiway, parallel runway or runway edge.
- A hard bounce, prolonged float or late touchdown leaves insufficient runway.
For simulator practice, 1,000 feet AGL in instrument conditions and 500 feet AGL on a genuinely visual approach are useful stabilisation gates, not universal aircraft limitations. At a dark or unfamiliar airport, applying the earlier gate is the safer choice. Follow a stricter aircraft or operator procedure whenever one is provided.