Dead Reckoning, the First Checkpoint, and the Groundspeed Check That Rewrites Your Whole Flight Plan

SUMMARY: The first-checkpoint groundspeed check reveals whether your VFR flight plan matches reality - and protects your fuel reserves before it’s too late.

The single most useful thing you can do on a VFR cross-country happens about ten minutes after takeoff: the first checkpoint groundspeed check. You time your leg to a known landmark, divide distance by time, and discover your actual groundspeed in today’s real winds - not the forecast your plan was built on. Do it early and you catch wind errors, fix your ETAs, and protect your fuel reserves while you still have every option open.

Why Your Flight Plan Is Just a Prediction

Your nav log is a prediction, and nothing more. The night before, you sat down with a sectional, a plotter, a flight computer, and the forecast winds aloft, and you predicted the future. You declared you’d make 110 knots over the ground and cross a particular town at a particular second after level-off.

Here’s the part that catches people: that prediction was built on forecast winds, not real ones. Someone at the Aviation Weather Center made their own prediction about the wind at 6,000 feet over your route, hours before you showed up. You built your entire nav log on top of their guess.

So you have a prediction stacked on a prediction - and you launch anyway. That isn’t a flaw. That’s flying. Cross-country navigation has worked this way since before Lindbergh: you make the best plan you can, then go up and find out how wrong it is. The fixing is the skill. The planning is just the starting point.

Pilotage vs. Dead Reckoning: What’s the Difference?

Pilotage is navigating by looking out the window. You see a lake, you find the lake on the chart, you know where you are. It’s the most natural thing in the world.

Dead reckoning is navigating by heading, speed, and time. You point the airplane on a computed heading, hold a known airspeed, start a clock, and calculate where you must be - even when you can’t see a single useful landmark. Haze, unfamiliar terrain, a stretch of Nebraska where every intersection looks like the last one. Dead reckoning still works when pilotage runs out.

And the name has nothing to do with anybody being dead. The best guess is that it’s “ded” reckoning, short for deduced - you deduce your position. The morbid spelling just stuck around because pilots think it sounds cool.

The two tools work together: you use dead reckoning to make the prediction, and pilotage to check it. The check happens at your first checkpoint.

How Do I Do a Groundspeed Check at the First Checkpoint?

Set the scene. You’ve picked a good first checkpoint, leveled off at cruise altitude, set cruise power, leaned the mixture, and noted the exact time you crossed your departure fix. Write it down - on the log, on the tablet, somewhere you can subtract from later. Not in your head.

Then fly, and watch for the checkpoint. The moment it slides under your wing, note the time again. Now do the one piece of arithmetic that makes you a navigator:

1. Time between checkpoints (subtract your two logged times).
2. Distance between checkpoints (straight off the chart).
3. Distance ÷ time = groundspeed - your actual groundspeed, in these real winds, at this real weight and power setting.

Make it concrete. Say your first checkpoint is 15 nautical miles from where you started timing, and you planned for 120 knots. At 120 knots, 15 miles should take 7.5 minutes.

You look down. It took 9 minutes.

Stop - that’s the whole game. Fifteen miles in nine minutes is about 100 knots over the ground, not 120. The wind isn’t doing what the forecast promised. You’ve picked up roughly 20 knots of headwind you didn’t plan for.

Why You Can’t Just “Average It Out”

The temptation is to shrug: it’s one checkpoint, it’ll average out. It won’t. A 20-knot error on the first leg is a 20-knot error on every leg going that direction. It compounds. Every checkpoint comes later than planned, the gap widens the whole way, and your fuel burn - also planned around groundspeed - is now wrong in the direction that hurts.

So you don’t shrug. You rewrite the plan, in the air, right now. Take the distance remaining to your next checkpoint (or all the way to your destination) and recompute the time using 100 knots, not 120. On a flight computer or an app, that’s ten seconds of work: set groundspeed, read time for distance. Now the ETAs down the rest of your log are honest.

How Does Groundspeed Affect My Fuel Reserves?

Here’s what nobody tells students plainly: your fuel reserve isn’t protected by the number on the fuel gauge - it’s protected by whether your groundspeed assumption is still true.

If you’re moving 20% slower over the ground, you’re spending 20% more time in the air to cover the same distance, burning fuel the entire time. The airplane burns by the clock, not by the mile. It doesn’t care that you’re going slower.

So when the first checkpoint tells you you’re slow, the next question isn’t “will I be late.” It’s “will I still land with my reserves intact.” That’s the question that keeps you alive.

The regulations, in FAR 91.151, require 30 minutes of reserve for day VFR and 45 minutes at night. Those are legal minimums, not targets - your personal reserve should be fatter. And the first checkpoint is where you find out, early, whether today’s winds are quietly eating into it.

The beauty of doing this ten minutes in instead of ninety is options. Ten miles out with full tanks, you can pick a closer alternate, add a fuel stop, or turn around - all easy decisions. Ninety minutes in, wondering if the next fuel is reachable, all of them are terrible. The check is trivial. The timing of the check is everything. A pilot who runs it is never surprised by their fuel state - they knew twenty minutes ago it would be tight, and already did something about it. That’s what staying ahead of the airplane actually looks like: subtraction and division at the first checkpoint.

What Makes a Good Checkpoint?

A lot of plans fall apart here, before the airplane even moves. A good checkpoint has three qualities:

• It’s unique. Pick something that can only be the thing you think it is: a single tower in a field, a dam, a bend where two rivers actually join, a railroad crossing a highway at an angle, a town with a distinctive grain elevator. Avoid one of four identical towns in a row, or a road intersection in a grid where every mile looks the same. If you can’t tell it from its neighbors at three miles out, it’s not a checkpoint - it’s a coin flip.
• It’s ahead and off to the side, not under the nose. Anything directly beneath you vanishes under the cowling right when you need it. A feature you watch approach and slide past your wingtip gives you time to confirm it, catch the time, and think.
• It works from altitude. That pretty little pond on the sectional may be invisible under summer haze from 6,000 feet, or dried up in August. Roads, rivers, ridge lines, and towers read well from high up; small ponds and individual buildings often don’t. Pick features with size and contrast.

One more tip: place your first checkpoint farther out than feels natural - ten, twelve, fifteen miles, not two miles off the departure end. You need distance for the math to mean something. Over three miles, a few sloppy seconds on the stopwatch turns into a huge phantom groundspeed error, because you’re dividing a tiny distance by a tiny time. Over fifteen miles, those same seconds barely move the answer. Longer legs give you cleaner numbers.

What Does the Checkride Examiner Actually Want to See?

The Airman Certification Standards (ACS) devotes an entire area of operation to cross-country flight planning and navigation, and it splits the world exactly the way we’ve been talking: pilotage and dead reckoning on one side, navigation systems (radios and GPS) on the other.

In the pilotage and dead reckoning task, the standard isn’t “get there.” It’s that you can identify landmarks, navigate by dead reckoning, verify your position, and - here’s the phrase that matters - “correct for and record differences between your preflight groundspeed and heading calculations and the actual values found in flight.”

Read that again. The examiner is quite literally looking for the groundspeed check. Not whether you nailed the forecast - nobody nails the forecast - but whether you catch the error and fix it. A student who crosses the first checkpoint, notes it’s two minutes late, quietly recomputes groundspeed, and revises the rest of the log has just shown the examiner the exact skill the ACS is built around, without saying a word. That’s a pass.

The failure mode is just as instructive: the student locked onto the magenta line, staring at the moving map, never looking outside. They can find the airport - but ask them what their groundspeed is doing versus plan, or ask them to divert with the screen dark, and it falls apart. The GPS is a wonderful tool. It is not a substitute for knowing whether your plan is true.

Do the check even when the box is working - especially then. The day the GPS quits over unfamiliar ground, the pilot who’s been quietly running the groundspeed check every leg already knows their heading is good, knows their real speed, and has a clock running and a plan on paper. They just keep flying. Dead reckoning carries them home. The pilot who outsourced everything to the magenta line is suddenly very alone up there.

Key Takeaways

• Your flight plan is a prediction built on forecast winds. The skill isn’t planning - it’s catching how wrong the plan is and fixing it in the air.
• Run the groundspeed check ~10 minutes in: log your time at the leg start and again at the checkpoint, then divide distance by time for your true groundspeed.
• Don’t average out errors. A wind error on leg one compounds through every leg going that direction - rewrite your ETAs and fuel using the real number.
• Fuel reserves are protected by an accurate groundspeed, not the fuel gauge. The airplane burns by the clock; FAR 91.151 requires 30 min day / 45 min night VFR reserves as legal minimums.
• Pick checkpoints that are unique, off to the side, visible from altitude, and 10–15 miles out so timing errors don’t blow up your groundspeed math.