Learn VFR checkpoint navigation: choose clear landmarks, build a nav log, correct drift, avoid false matches and recover safely after a missed checkpoint.
Navigate with VFR checkpoints by plotting a course on a current chart, choosing prominent features at sensible intervals, and recording each checkpoint's heading, distance and expected time. In flight, identify features in sequence, compare actual progress with the plan, correct for drift, and maintain terrain, airspace and weather awareness.
In real-world aviation, this method is called pilotage, normally supported by dead reckoning: heading, groundspeed and elapsed time tell you where to look, while outside references confirm where you are. GPS can provide valuable backup, but it should not replace continuous positional awareness.
How do you plan a route using VFR checkpoints?
Plan the route from a current aeronautical chart, then turn it into a short navigation log that can be read without prolonged head-down time.
- Draw the intended track. Check terrain, controlled and restricted airspace, obstacles, suitable cruising altitudes and diversion options. Our guide to interpreting the symbols and airspace on a sectional chart covers the chart-reading detail.
- Select checkpoints along or close to the track. Include an unmistakable feature near the departure point, intermediate position checks, each turn point and a feature that helps locate the destination.
- Add catch lines. A coastline, motorway, railway or broad river beyond a checkpoint can warn that you have flown too far. Features on either side of the course can also bracket your position.
- Calculate headings and times. Account for forecast wind, magnetic variation and, where relevant, compass deviation. Record the distance, expected groundspeed, leg time and estimated time of arrival at each checkpoint.
- Brief each feature before departure. Note what it looks like, which side of the aircraft it should appear on and what nearby features confirm its identity. A checkpoint does not have to be flown directly overhead; passing abeam is often easier to recognise.
Start timing when established on course from a known position, not simply when the aircraft begins moving. That prevents taxi, departure routing and circuit time from corrupting the first estimate.
What makes a good VFR checkpoint?
A good checkpoint is prominent, unique from your viewing altitude and easy to relate to the intended track.
| Reference | Why it works | Common trap |
|---|---|---|
| Coastline, large lake or distinctive river bend | Visible from distance and recognisable by shape | Haze, low sun or seasonal water levels can obscure detail |
| Major road or railway crossing | Two linear features create a precise fix | Similar junctions may sit close together |
| Large town beside another feature | The feature combination is easier to identify than the town alone | Urban areas can merge and expand beyond charted boundaries |
| Airfield, quarry or reservoir | Often has a distinctive outline or contrast | Small private strips and minor industrial sites can be difficult to see |
| Tower or mast | Precisely charted and useful at close range | Thin structures are poor long-range visual references |
Choose checkpoints by elapsed flying time, not an arbitrary distance. Checks roughly every five to ten minutes are often practical, but a fast aircraft, demanding airspace or feature-poor terrain may require different spacing. Too many points create cockpit workload; too few allow a small heading error to grow unnoticed.
A mistake we see constantly is selecting a generic town or road because it lies exactly on the line. A slightly offset but unmistakable reservoir or road-and-rail crossing is usually better. Confirm a checkpoint with at least two independent cues, such as its shape, orientation and relationship to another feature.
How do you use checkpoints while flying?
Fly the planned heading and use the expected time to focus your search in the correct area rather than chasing every visible landmark.
- Aviate first. Hold altitude, attitude and heading while maintaining an effective lookout.
- Anticipate the checkpoint. Shortly before its estimated time, review its shape, relative bearing and surrounding features.
- Identify it positively. Match more than one characteristic before declaring the checkpoint found. Avoid forcing the terrain to fit your expectation.
- Record the actual time. Compare it with the estimate and revise later arrival times if the groundspeed differs from the plan.
- Correct methodically. Estimate whether the error came from wind, inaccurate heading, timing or incorrect identification. Make one measured correction, then verify its effect at the next feature.
The approximate one-in-60 rule helps quantify drift: after 10 NM, being 1 NM off track represents about 6 degrees of track error. If the wind remains similar, this is more useful than making repeated small turns towards individual landmarks.
Do not descend below a legal, terrain-safe altitude merely to identify a feature. Marginal visibility can make a legally VFR flight unsuitable for dependable pilotage, especially when checkpoints are far apart or terrain offers little contrast.
What should I do if I miss a checkpoint?
If a checkpoint does not appear near its expected time, maintain control, stop making unplanned turns and establish what you know before attempting to recover the route.
- Check heading, elapsed time, wind and groundspeed for an obvious error.
- Look for large linear features, terrain boundaries or prominent landmarks rather than the missing small checkpoint.
- Use all available navigation equipment, including GPS, VOR or direction-finding assistance, instead of protecting the purity of a pilotage exercise.
- Climb for better visibility and radio coverage only when weather, terrain, aircraft performance and airspace make that safe and legal.
- Contact the appropriate air traffic or flight information service early and state plainly that your position is uncertain.
Flight following does not replace navigation or authorise entry into controlled airspace, but it can provide useful support. We explain what VFR flight following provides and how to request it.
How does VFR checkpoint navigation differ in a simulator?
In flight simulators, use the same chart-heading-time-reference cycle, but allow for differences between the chart database and rendered scenery.
Large coastlines, lakes, motorways and cities are usually safer choices than individual buildings or masts. Autogenerated scenery may omit a real feature, photogrammetry can make it difficult to recognise, and roads or water boundaries may not perfectly match the chart. Our explanation of how recognisable scenery supports VFR flying in Microsoft Flight Simulator helps when choosing simulated references.
A moving map is best treated as a verification tool during pilotage practice: estimate your position first, then reveal or consult it to check the result. For more detailed preparation, simulator flight-planning tools that show terrain and airspace can help build checkpoint-based routes without making the cockpit map your primary means of navigation.