What do runway lights mean, and how do pilots use them?

Runway lights show pilots the runway’s usable edges, landing threshold, centreline, touchdown zone and end. White usually defines the runway, green marks the threshold from the approach direction, and red marks the far end or warns that little runway remains. Their pattern and viewing direction matter as much as colour.

In our Aviation & Real-World Flying coverage, we use the real-world meanings below. Flight simulators aim to reproduce the same system, although scenery quality, lighting controls and national standards can produce differences between airports.

Runway light colours explained

Under widely used ICAO and FAA conventions, white defines the runway, green identifies a landing threshold, red identifies the runway end, and yellow gives a caution that the end is approaching.

Not every runway has every system. Installation depends on runway category, approach capability and the applicable national standard. Exact spacing and the length of yellow or colour-coded caution zones can also differ, so published aerodrome information takes precedence over a general rule.

How do runway centreline lights show runway remaining?

Runway centreline lights are normally white until approximately 900 metres or 3,000 feet remain, alternate red and white until approximately 300 metres or 1,000 feet remain, and then show red to the runway end.

The sequence is directional and may look different when viewed from the opposite end or through a simulator’s free camera. These transitions provide situational awareness, not an exact stopping-distance measurement. A take-off rejection or landing-performance decision must be based on the aircraft’s calculated performance and operating procedure, not on waiting to see red lights.

What do runway touchdown-zone lights look like?

Runway touchdown-zone lights are symmetrical rows of short white light bars beside the centreline, normally beginning just beyond the threshold and extending for no more than about 900 metres or 3,000 feet.

On a shorter runway they usually end near the midpoint. Their purpose is to identify the touchdown region and improve visual perspective in poor visibility; they do not guarantee that every point within the illuminated area is a suitable touchdown point for every aircraft.

What are runway threshold identification lights, and are they runway end lights?

Runway threshold identification lights are flashing white lights placed on either side of the landing threshold; they are not the steady red runway end lights seen during the landing or take-off roll.

In ICAO-style terminology they may be abbreviated as RTIL. In the United States, the same basic aid is commonly called a runway end identifier light system, or REIL, despite being positioned to identify the approach end. It supplies no glidepath information and does not indicate that the runway is clear or that an aircraft is cleared to land.

The steady green threshold lights form a line across, or immediately beside, the runway. At a displaced threshold that green line sits farther down the pavement. The pavement before it may be available for taxiing, take-off or landing rollout from the opposite direction, but only as published; it is not available for touchdown in the displaced-threshold direction.

Where a runway end and the reciprocal landing threshold occupy the same location, directional fittings can show green to an approaching aircraft and red to an aircraft looking towards the end from the runway. Our focused explanation of why threshold and runway-end colours change with viewing direction covers this easily misunderstood arrangement.

Approach lighting is separate again. It is the patterned array extending outward before the threshold, sometimes with sequenced flashers; our guide to how approach-light arrays help pilots acquire and align with a runway explains the common layouts. PAPI, VASI and T-VASIS are visual glidepath indicators rather than runway lights. For a four-light PAPI, two white and two red normally mean on path, more white means high, and more red means low; see our practical explanation of reading PAPI indications for the limitations and simulator technique.

How are runway lights different from taxiway lights?

Runways are principally identified by white edge or centreline lighting, while taxiways normally use blue edge lights and green centreline lights.

• Blue lights mark taxiway edges.
• Green in-pavement lights normally mark a taxiway centreline. Unlike a runway threshold, they run along the pavement rather than forming a transverse green line across it.
• Flashing or alternating yellow runway guard lights draw attention to a runway holding position.
• Red stop-bar lights mean stop. If a clearance appears to conflict with an illuminated stop bar, the pilot should hold and clarify the instruction.

A green taxiway centreline leading towards a runway is a common source of wrong-surface confusion. Before entering or landing, pilots cross-check the runway number, approximate magnetic heading, pavement shape, chart and flight instruments rather than following whichever set of lights appears brightest.

How do pilots use runway lights during landing and take-off?

Pilots use runway lighting to identify the correct surface, control alignment, judge the touchdown area and monitor runway remaining, but never as a substitute for clearance, charts or aircraft performance calculations.

1. Brief the installation: Check the expected approach, threshold position, lighting systems, reported outages and any displaced threshold. An absent centreline or touchdown-zone system may be normal for that runway.
2. Confirm the runway: Match the runway number and heading, then cross-check the threshold, edge-light pattern and navigation instruments. Illumination alone does not prove that a runway is assigned, open or unoccupied.
3. Acquire the approach path: Use the approach-light array for alignment and PAPI or VASI as a vertical-path cross-check. A visual glidepath indication is most reliable near the extended centreline and does not replace a published instrument procedure or obstacle-clearance requirement.
4. Cross the threshold: Pass over the green threshold lights at the planned height. Do not aim to touch down on them; the aiming point and touchdown zone lie farther along the runway.
5. Control the flare and roll: Look well down the runway and use the centreline and edge lights to detect drift. Yellow edge lights, changing centreline colours and red end lights show that the available distance is reducing.
6. Vacate positively: Reduce speed before turning, identify the intended taxiway and transition to its blue edge or green centreline lighting. Do not mistake a nearby parallel taxiway for another runway.

During take-off, the edge and centreline lights provide directional references in the same way. The colour-change zones offer a late-runway warning, but take-off decision speeds and rejected-take-off actions must already have been calculated and briefed.

Can pilots land using runway lights alone?

Runway lights can provide the main outside references for an authorised visual night landing, but they cannot replace weather minima, runway clearance, a stable approach, performance calculations or required instrument indications.

Under instrument rules, seeing part of an approach-light system does not automatically permit descent all the way to the runway. The visual references required below a decision altitude or minimum descent altitude depend on the jurisdiction and operation. Lighting failures may also raise minima or make a particular approach unavailable.

A line of lights over dark, featureless ground can create misleading height and distance impressions. Pilots counter this black-hole effect by maintaining the planned vertical profile, checking flight instruments and using PAPI or VASI where available. If the runway cannot be positively identified or the approach becomes unstable, the correct response is a go-around.

Can pilots turn runway lights on themselves?

Pilots can activate runway lighting at some non-towered airports, but only where a published pilot-controlled lighting system is installed.

A common United States arrangement responds to three, five or seven microphone transmissions on the published frequency within five seconds, selecting progressively higher intensity. This is not a worldwide rule, and the frequency, timing, available settings and operating period must be checked rather than guessed. Our guide to radio-click lighting sequences and their limitations explains the normal procedure.

At controlled aerodromes, air traffic control normally selects the intensity. Excessive brightness can produce glare in rain, fog or a dark cockpit, so pilots may request a lower setting when conditions and local procedures permit.

What runway-light mistakes cause trouble?

The most serious errors come from reading one colour in isolation instead of interpreting its position, pattern and viewing direction.

• Confusing different red indications: Red PAPI lights indicate a low approach. Red runway centreline or end lights indicate that little or no runway remains, while a red stop bar means stop before entering the protected area.
• Aiming at the green threshold lights: The threshold is the start of landing-available pavement, not the intended touchdown point. Trying to land on the green line reduces threshold-crossing height and increases undershoot risk.
• Following the brightest pavement: A parallel taxiway, road or different runway can look more prominent than the assigned surface. The runway identifier, heading and instruments must agree.
• Expecting every lighting system: Many valid runways have no centreline lights, touchdown-zone lights or threshold identification lights.
• Treating lights as proof of availability: A closed, occupied or unsuitable runway may still be illuminated. Clearance and published status govern its use.
• Using colour changes as precise distance markers: They divide the last section of a runway into broad zones. They do not account for speed, slope, contamination, wind or braking action.

Why do runway lights look wrong or disappear in a flight simulator?

If runway lighting looks wrong at one airport, the likely cause is that airport’s scenery data or a conflicting add-on; if it is wrong everywhere, check rendering, exposure, display calibration and lighting controls.

1. Confirm that the lights should exist: Compare the simulated runway with its published lighting information. A mistake we see often is assuming that every instrument runway must have centreline or touchdown-zone lights.
2. Check the viewing direction: Threshold, runway-end and colour-coded centreline lights are directional. Slewing behind a fitting or approaching the reciprocal end can reveal a different colour or make the lamp appear unlit.
3. Isolate scenery conflicts: Temporarily disable overlapping airport packages and test the simulator’s default airport scenery. Duplicate packages can place two thresholds, suppress lighting objects or create mismatched runway elevations.
4. Review image settings: Excessive exposure, bloom, HDR brightness or display black level can wash out white lights and make red lights dominate. If all airports are affected, test a neutral display preset before changing scenery.
5. Check activation behaviour: Pilot-controlled lighting is not modelled consistently across simulators and add-on airports. Some installations illuminate automatically, while others depend on a simulator command or scenery-specific control rather than microphone transmissions.

Daylight, haze and viewing distance also affect apparent intensity. Testing the same runway at night in clear weather helps separate a scenery fault from normal visibility and rendering behaviour.