Learn how to judge distance from the runway on a VFR approach using pattern geometry, GPS, height checks, visual cues and illusion fixes.
In a general flight simulator, judge runway distance by combining a known reference—GPS distance, charted landmarks or traffic-pattern geometry—with runway perspective and your height above ground. Do not rely on apparent runway size alone. On a 3° final, expect roughly 300 feet AGL per nautical mile from the threshold.
Which cues tell you the runway distance?
No single visual cue gives dependable mileage, so we cross-check at least two sources. Treat the runway threshold as the reference point; distance to the airport centre, far end of the runway or a nearby beacon is not the same measurement.
| Cue | What it tells you | Main limitation |
|---|---|---|
| GPS or moving map | Numerical range to the selected point | An airport waypoint may represent the airport reference point rather than the threshold |
| DME | Slant range to a radio station | The station may be offset from the runway; it does not normally measure threshold distance |
| Known landmarks | Distance based on a pre-briefed visual reporting point | Requires recognisable scenery and preparation |
| Traffic-pattern geometry | A repeatable short, normal or long final | Wind and downwind spacing change the result |
| Runway perspective | Closure rate and whether the approach picture is stable | Cannot provide an exact distance by itself |
PAPI and VASI lights indicate vertical approach angle, not range. The same red-and-white indication can appear at several different distances. Our explanation of runway perspective, visual slope cues and the 3° profile shows how those references fit together.
How can you estimate distance without GPS or DME?
Without electronic distance information, establish one known point and update your estimate using pattern geometry, elapsed time, groundspeed and altitude.
- Brief a reference point. Identify a landmark about 3 or 5 NM from the threshold, or join a conventional circuit. If flying a circuit, use the techniques in our traffic-pattern spacing and turn-timing guide.
- Build consistent circuit spacing. On downwind, keep the runway at a familiar position relative to the wing. A common base-turn cue is when the threshold is roughly 45° behind the wing, but adjust for wind rather than turning at one rigid screen position.
- Use groundspeed and time. At 60 knots groundspeed you travel 1 NM per minute; at 90 knots, 1.5 NM; at 120 knots, 2 NM. Measure from a known landmark using
distance travelled (NM) = groundspeed (kt) × minutes ÷ 60. Use groundspeed, not indicated airspeed. - Cross-check altitude. If the runway is about 3 NM away on a normal 3° final, being close to 1,000 feet above runway elevation is plausible. Being at 500 feet suggests that either the distance estimate or glide path is wrong.
- Watch the aiming point. On a stabilised approach, the selected aiming point remains nearly fixed in the windscreen while the runway expands around it. If it rises, the projected path is becoming short; if it sinks, the projected path is moving farther down the runway. This shows trajectory rather than mileage, as explained in our guide to choosing and reading the landing aiming point.
How high should you be at each distance?
On a 3° approach, height changes by approximately 318 feet for each nautical mile, usually rounded to 300 feet per NM for mental arithmetic.
| Distance from threshold | Basic 300 ft/NM check | Approximate profile with a 50 ft threshold crossing |
|---|---|---|
| 1 NM | 300 ft AGL | 370 ft AGL |
| 2 NM | 600 ft AGL | 690 ft AGL |
| 3 NM | 900 ft AGL | 1,000 ft AGL |
| 5 NM | 1,500 ft AGL | 1,640 ft AGL |
These heights are above runway elevation, not necessarily above the terrain directly beneath the aircraft. Add the threshold elevation to obtain an approximate indicated altitude: a runway at 2,000 feet MSL and a target of 1,000 feet AGL gives about 3,000 feet indicated, assuming the altimeter is set correctly.
The values are checks rather than targets to chase aggressively. Visual approaches may use a different angle, and a PAPI guides the pilot's eye; wheel clearance varies with aircraft size and seating position.
Why does the runway look nearer or farther than it is?
Camera field of view, runway dimensions, slope, lighting and scenery rendering can all distort apparent distance in a simulator.
- Zoom and field of view: a narrow, zoomed-in view makes the runway look larger and nearer; a wide-angle view makes it look smaller and farther away. Keep a consistent cockpit view while learning the approach picture.
- Runway width: an unusually wide runway can create the impression of being low or close, while a narrow runway can make the aircraft appear high or far away.
- Runway slope: an upsloping runway tends to create a high-approach illusion; a downsloping runway tends to create the opposite impression.
- Wind: turning base at the usual visual point without considering groundspeed can produce a much longer or shorter final. Reassess spacing after each turn.
- Scenery detail: runway markings or buildings may appear abruptly as their level of detail changes. Use them as confirmation only, not as a measuring scale.
- Dark terrain: a brightly lit runway surrounded by darkness removes most depth cues and can lead to a dangerously low approach. Use the precautions in our simulator night-landing guidance.
For precise range, use a threshold-referenced navigation source. For visual-only flying, use a known landmark or repeatable circuit, then confirm the estimate with groundspeed, height and a stable runway picture.