Picking your VFR checkpoints and the landmarks that disappear at altitude

Choosing VFR checkpoints for cross-country flight is one of the most undertaught skills in flight training. The landmarks that look obvious on a sectional chart often vanish at 3,500 feet AGL in haze or low sun. The key is selecting features that are large, high-contrast, close to your course line, and spaced 8 to 12 minutes apart — giving you reliable position fixes without burying your head in the chart.

Why Do Checkpoints Disappear at Altitude?

The most common mistake student pilots make is picking checkpoints that are too small. A water tower, a single-track railroad, or a small private grass strip may look prominent on the sectional, but from the cockpit they shrink to specks. Add haze, low sun angle, or surrounding trees, and they vanish entirely.

Power lines, railroad tracks, and small roads become nearly invisible above about 2,500 feet AGL. Those thick black dashes on the chart are deceptive. In practice, a single-track railroad running through forest cannot be spotted unless you are directly overhead at low altitude.

When you can’t find a checkpoint, stress builds fast. You fall behind the airplane, drift off heading, and the entire plan starts to unravel. The fix is simple: pick bigger landmarks from the start.

What Makes a Good VFR Checkpoint?

Four rules separate checkpoints that work in the real world from checkpoints that only work on paper.

Rule 1: Big beats small, every time. The best checkpoints are features you cannot miss — interstate highway interchanges, large lakes, river bends, towns, airports, and mountain ridges. These are visible from 10 to 15 miles away. You need only a two- to three-second glance to confirm your position, and that is not enough time to hunt for a water tower in a green field.

Rule 2: Choose features with contrast. A checkpoint only works if it looks different from its surroundings. A brown field next to other brown fields is useless. A lake surrounded by forest is ideal because water and trees look completely different from altitude. Season matters — in summer, look for water, paved surfaces, and clearings that break up the green-and-brown landscape. In winter with snow cover, roads and rivers become dark lines against white and jump out immediately.

Rule 3: Keep checkpoints on or near your course line. A landmark eight miles off to one side may be unreachable visually if you drift even slightly off course. A checkpoint within one to two miles of your course line stays in your field of view despite small heading errors. It also tells you immediately whether you’ve drifted left or right based on which wing it passes under.

Rule 4: Space them 8 to 12 minutes apart, no more than about 15 miles. At typical training speeds in a Cessna 172 or Piper Cherokee, 15 miles equals roughly 8 to 10 minutes of flight. That interval lets you confirm position, note timing, and check ground speed before the next fix. Going 25 to 30 miles between checkpoints risks being five or six miles off course before you realize it. Stacking them every three miles buries you in the chart instead of flying the airplane.

How Do You Build a Checkpoint List?

Start by drawing your course line on the sectional, then scan for what falls directly on or near it.

Airports along the route are ideal checkpoints. Runways are visible from the air, they are clearly depicted on the chart, and they double as emergency landing options. A nearby town provides additional confirmation.

Highway intersections — especially interstate interchanges — are unmistakable. The cloverleaf pattern of a major interchange is visible from miles away. Avoid generic secondary roads, which all look alike from altitude.

Rivers, especially bends and confluences, give you high-confidence position fixes. Where two rivers meet is a point you can identify with certainty. Rivers also function as line features — even between checkpoints, a river running parallel to your route acts like a guardrail that keeps you oriented.

Lakes and reservoirs work well when they have distinctive shapes. A long, narrow reservoir looks nothing like a round farm pond. Large water bodies remain visible in haze when ground features wash out.

Towns are reliable if they’re large enough — a population of a few thousand with visible streets and structures. A town next to a river bend or highway junction gives you two confirming features at once.

How Should You Document Your Checkpoints?

On your navlog, go beyond just listing checkpoint names. Write a brief description of what you expect to see — for example, “town on the south side of a river bend with a highway running east-west through it” or “L-shaped lake with an airport just north of the east end.”

This technique does two things. It forces you to study the chart before flight, building a mental picture of the route. And it gives you something specific to scan for instead of staring at a sea of green hoping something appears.

Build a mental movie of the flight before you fly it. You should be able to close your eyes and narrate what appears out the window at each stage: the interstate passing beneath you at the five-minute mark, the lake appearing on the left at thirteen minutes, the airport and town on the right at twenty-two minutes. That mental rehearsal is your insurance policy when the cockpit gets busy.

Why Do Checkpoints Matter for Timing and Ground Speed?

Checkpoints are not just for position — they are the backbone of dead reckoning. When you cross a checkpoint, note the exact time (not rounded to the nearest five minutes) and compare it to your planned time.

Two minutes late to your first checkpoint means a stronger headwind component than forecast, which changes your fuel calculation for the entire trip. Three minutes early means a tailwind — your next checkpoint will appear sooner than expected.

This is the Airman Certification Standards in action. Your examiner wants to see that you planned a ground speed based on winds aloft, then confirmed it with real data. That only works if your checkpoints are identifiable and your timing is precise.

What Does a Real Checkpoint Plan Look Like?

Consider a cross-country from central Pennsylvania to western Maryland on a southwest course.

Your first instinct might be a small private airstrip ten miles out — but a 2,000-foot grass runway with no buildings is invisible from altitude. Skip it.

Instead, your first checkpoint at 12 miles is a town where a state highway crosses a river — three confirming features in one location. At 22 miles, an elongated reservoir sitting in a valley between two ridgelines — unmistakable shape and contrast. At 35 miles, a public airport right on your course line with a town just east of the field.

Each checkpoint is big, high-contrast, and on the course line. That plan works in the real world.

How Do You Get Better at Picking Checkpoints?

Debrief every cross-country. Which checkpoints did you spot easily? Which were harder than expected? Did anything surprise you? Each flight teaches you what works from the air versus what only works on paper. Students who debrief consistently build better plans every time and develop the judgment that turns cross-country planning from a chore into a trusted skill.

For deeper study, Chapter 16 of the FAA Pilot’s Handbook of Aeronautical Knowledge and the Aeronautical Information Manual both cover pilotage and dead reckoning navigation in detail.

Key Takeaways

• Pick checkpoints that are large and high-contrast — interstate interchanges, lakes, river confluences, towns, and airports beat water towers and railroad tracks every time
• Keep checkpoints within 1-2 miles of your course line so small heading errors don’t put them out of visual range
• Space checkpoints 8-12 minutes apart (roughly 10-15 miles at typical training speeds) for manageable workload
• Write descriptions, not just names on your navlog, and rehearse a “mental movie” of the route before flying
• Use exact checkpoint times for ground speed checks — dead reckoning only works with precise timing and identifiable landmarks