How do you make a safe night landing in a flight simulator?

To make a safe night landing in a flight simulator, brief the runway and missed approach, dim the cockpit, use instrument guidance, stabilise early, and positively identify the runway. Hold the correct speed and glide path, flare from the normal sight picture, and go around if alignment, stability or visual references become uncertain.

In our Aviation & Real-World Flying guidance, we treat a simulated night approach like the real procedure. Darkness removes terrain texture and peripheral height cues, so a runway that looks easy to reach can still produce a dangerously low, fast or misaligned approach.

How do you set up for a safe night landing?

Set up the aircraft, approach and missed-approach plan before descending into the busiest part of the flight.

1. Choose the runway deliberately. Check wind, visibility, cloud, runway length, surface condition, elevation and available lighting. Prefer a runway with dependable vertical guidance while learning; a short runway, strong crosswind and black-hole approach should not be combined unless that is the exercise.
2. Brief the procedure and escape route. Note the final approach course, relevant altitudes, minima, touchdown zone and first missed-approach altitude and heading. Our explanation of briefing an instrument approach chart covers the symbols and restrictions to check before arrival.
3. Set and cross-check the instruments. Enter the local altimeter setting in the correct units, tune and identify any required navigation aid, select the correct CDI or navigation source, and confirm that the loaded GPS procedure matches the intended runway. A scenery and navigation-data mismatch can leave an approach pointing beside a renumbered or repositioned runway; do not force the landing if that happens.
4. Reduce cockpit glare. Dim panels and displays until they remain readable without reflecting on the windscreen or destroying outside vision. Keep a consistent cockpit viewpoint. An unusually high, low or zoomed-in camera position changes the apparent flare height.
5. Configure before final approach. Complete the landing checklist, extend gear and flaps as required, set the target speed, trim the aircraft and establish a steady descent. Arm spoilers, autobrake or other systems only when appropriate for the aircraft.
6. Respect the approach minima. At a decision altitude, make the required landing or missed-approach decision there. On an MDA procedure, remain at or above the MDA until the required visual reference exists and begin the miss no later than the missed approach point. Seeing the airport beacon or general city lighting is not the same as identifying the runway environment; our guide to using approach minima in a simulator explains the distinction.
7. Transition gradually to outside references. Keep cross-checking speed, attitude, vertical speed and alignment after acquiring the runway. A mistake we see constantly is abandoning a stable instrument scan, staring at the lights and allowing the aircraft to sink below the glide path.

Which approach is safest at night?

At night, use an approach with reliable lateral and vertical guidance when the aircraft, runway and procedure support it.

Selecting approach mode on the autopilot does not make every aircraft capable of autoland. Monitor every capture, and be prepared to disconnect or go around if the automation follows the wrong source, overshoots the localiser or fails to establish a stable path.

How do you recognise the correct runway lights at night?

The correct runway is identified by its orientation, markings, approach-light pattern and runway lighting—not by one bright row of lights alone.

• Runway edge lights are normally white, with yellow caution lighting near the far end on some instrument runways.
• Threshold lights facing an arriving aircraft are green; runway-end lights seen while looking towards the end are red.
• Runway centreline lights, where installed, begin white and transition through red-and-white to red near the end.
• Taxiway edge lights are blue, while taxiway centreline lights are generally green. Do not line up with a taxiway simply because it is the brightest pavement.
• PAPI lights normally show two white and two red on the intended path. More white means high; more red means low.

Lighting layouts vary by airport and simulator scenery, so compare the whole pattern with the chart and heading. Our detailed guide to interpreting runway, threshold, centreline and PAPI lights shows how the systems fit together.

If expected lights are absent, first go around. Some simulated airports use pilot-controlled lighting, while others illuminate automatically or depend on scenery configuration. Landing lights also have limited range and may not reveal the pavement until late final; they are not a substitute for approach or runway lighting.

What descent rate should you use at night?

Use the same stabilised glide path as in daylight, with instruments providing the primary height and descent-rate cross-check.

For an approximate three-degree path, multiply groundspeed by five to estimate vertical speed in feet per minute: 90 knots is about 450 feet per minute, 120 knots about 600, and 150 knots about 750. Use groundspeed rather than indicated airspeed because wind changes the required rate of descent. The aircraft's published technique and the actual electronic or visual glide path take priority over this shortcut; see our practical three-degree glide-path method for the full calculation and correction technique.

Why can the runway look too high, low or far away?

Night visual illusions distort apparent height and distance, particularly when the runway is surrounded by darkness.

• Black-hole illusion: A brightly lit runway beyond dark water or unlit terrain can make the aircraft seem higher than it is, encouraging a low approach.
• Runway-width illusion: A narrower-than-expected runway can make the aircraft appear high and lead to a low approach. An unusually wide runway can produce the opposite response.
• Runway slope: An upsloping runway tends to look higher; a downsloping runway tends to look lower.
• Lighting intensity: Very bright lights can make the runway seem closer, while dim lights can make it appear farther away.
• Simulator rendering: Exposure, bloom, haze, display black level and scenery quality can hide terrain or exaggerate individual lights. Adjust these after the flight rather than continuing an unsafe approach.

A small disagreement between PAPI and an electronic glide path can occur because they may be designed around different eye, antenna or threshold-crossing geometry. Do not chase each indication with abrupt pitch changes. A large or persistent disagreement calls for a setup check or go-around.

How should you flare for a night landing?

Flare using the aircraft's normal technique while shifting your gaze towards the far end of the runway and using edge-light movement for height perception.

Keep the runway centreline stable in the windscreen, reduce power as appropriate for the aircraft and raise the nose smoothly to arrest the descent. Do not flare solely because the landing-light beam suddenly reaches the pavement, and do not use one fixed radio-altimeter callout or pitch attitude for every aircraft.

After touchdown, lower the nose as required, maintain directional control and apply spoilers, reverse thrust and wheel braking according to the aircraft. Watch the remaining runway rather than fixating on the nearest lights, particularly after a long float or on a wet surface.

When should you go around during a night approach?

Go around whenever the runway cannot be positively identified, the aircraft is unstable or a safe touchdown within the intended zone is no longer assured.

• The required runway references are not visible at the applicable minimum.
• The aircraft is on the wrong runway, taxiway or parallel approach path.
• Airspeed, sink rate, configuration or alignment needs large or repeated corrections.
• The aircraft remains materially above or below the intended glide path.
• Cloud, fog, glare or scenery rendering causes visual references to disappear.
• A bounce, balloon, prolonged float or late touchdown consumes too much runway.
• Automation behaves unexpectedly or the navigation path does not agree with the 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 limits. At an unfamiliar or poorly lit airport, using the earlier gate is the safer choice.

Apply go-around power, control pitch, retract drag-producing devices in the aircraft's normal stages, establish a positive climb and follow the published missed-approach route and altitude. Do not retract all flap at once or turn towards the airport lights without checking the missed-approach instructions.