Chronograph data: what to record and why

The chronograph is the single most important piece of test equipment most handloaders own, and it’s also the piece of equipment most likely to generate data that gets logged badly.

The reason isn’t that handloaders don’t understand the numbers. It’s that the chronograph hands you a wall of numbers per string, and most of them are noise. Knowing which ones are signal — and which ones are worth writing down for a load you might want to reproduce in two years — is the difference between a chronograph being a development tool and being a $400 stopwatch.

This is a practical guide to what to record from a chronograph session, and what to leave on the screen.

The shots vs. the string

A typical chronograph session gives you two layers of data.

Individual shot velocities. What each round measured. Useful while you’re shooting, for spotting fliers and pressure drift. Mostly noise once the session is over.

String statistics. Average, standard deviation, extreme spread, sample size. These are the numbers a load is described by.

A handloader’s job, while you’re shooting, is to make sure the chronograph is registering every shot cleanly so the string stats are real. A handloader’s job, after the session, is to record the string stats and forget the individual shot velocities unless something specifically interesting happened.

If you find yourself transcribing every shot from a chronograph display into a notebook, you are doing too much. Write down the four or five numbers that describe the string, and a sentence about anything unusual. That’s the actual data.

The numbers worth keeping

For every load you chronograph, write down these.

Sample size. How many rounds were in the string. A 3-shot SD is approximately meaningless. A 10-shot SD starts being useful. A 20-shot SD is honest. If your SD looks great on a 5-shot string, write down “5 shots” alongside it, so future-you knows how much to trust it.

Average velocity (mean). The middle of the string. The number you’d quote to a friend. This is the number that pairs with your charge weight and barrel length to identify the load.

Standard deviation (SD). How tightly the velocities cluster around the mean. SD is the number to chase if you care about long-range consistency, because velocity variation is what spreads your vertical at distance. Most handloaders have a sense of what “good” looks like for the cartridge and barrel — under 10 for a tuned load is a reasonable bar for many bottlenecks, more is acceptable, less is usually a clue you’ve found a real node.

Extreme spread (ES). Difference between the highest and lowest shot in the string. Less informative than SD because it’s just two data points, but it’s the number that screams loudest when something is genuinely off (one shot 60 fps off the rest is interesting and SD won’t say so as clearly).

Distance from muzzle. Three feet, ten feet, fifteen. Doesn’t affect chronograph numbers much in absolute terms, but consistency between sessions matters if you’re going to compare strings honestly. Write it down once for your setup and use the same distance every time you can.

That’s the bulk of it. Five numbers per load. The first one (sample size) is the one most handloaders forget to record and the one that determines whether the other four are worth anything.

What’s worth a note, not a number

Some things deserve a free-form note, not a stats field.

Conditions. Temperature most importantly. Powder velocity is temperature-sensitive in degrees-per-fps amounts that absolutely add up between a 40°F morning and an 85°F afternoon. Write down the temp.

Fliers. One round that came in 80 fps low. Note it. Was there a hangfire? Did the round feel weird going in? Did you flinch? Was it the round you weren’t watching the muzzle from? A flier with a story is sometimes worth excluding from the SD calculation. A flier without a story is data and stays in.

Pressure signs at velocity. This is the joining of two layers — your chronograph tells you a charge weight is hitting 2,810 fps; your bolt lift tells you whether you should be there. Pressure trumps velocity. Always.

The position of the chronograph. Indoor, outdoor, off a tripod, off a bench, ambient light conditions. Optical chronographs especially can give you weird readings under fluorescent lights or in cross-lighting. Notes about setup help you spot a “5-shot string with one number 200 fps off” as a setup problem, not a load problem.

The bigger number to ignore

Many chronograph apps now offer min, max, mean, median, mode, SD, ES, kurtosis, skewness, coefficient of variation, and 95% confidence interval for every string.

Most of that is statistical theater applied to a 10-shot sample.

A 10-shot sample of muzzle velocities is not a population. It’s a tiny sample of a much larger distribution. Higher-order statistics like kurtosis and skewness require a real sample size to be meaningful — hundreds of shots, not tens. Recording them for a 10-shot load development session is recording numbers that look precise without being informative.

Stick with the basics. Mean, SD, ES, sample size. They are the numbers that handloaders have used for fifty years to evaluate loads. They are still the numbers worth keeping.

How chronograph data ties into the rest of the session

A chronograph reading in isolation is interesting but not actionable. The reading-plus-recipe is actionable.

If you write down:

6.5 CM, 140 ELD-M, 41.8 H4350 (lot K2103), Federal 210M, Lapua brass FL-sized, .020 jump, 22” barrel, 10 shots, avg 2,762, SD 6.3, ES 18, 68°F, sea level

…you have a load. You can come back to it next year and reproduce it. The chronograph number is doing its job.

If you write down:

Average 2,762, SD 6.3

…you have a chronograph string. You don’t have a load. Even if the numbers look great.

The chronograph data is one layer of session data — the results layer. There’s a related guide on the other two layers of session data and why most reloading notes go bad in two years — recipe and context. Chronograph numbers without the other two layers are an anecdote.

A note on chronograph types

This isn’t a chronograph review, but a quick note since the data quality depends on it.

Optical chronographs (the classic screen-and-rod design) are accurate when set up well and prone to noisy readings when lighting is wrong. The fix is usually a diffuser or moving the chronograph to consistent light.

Magnetospeed-style (bayonet-mount, magnetic) are usually consistent but slightly higher than optical readings of the same shot due to where they measure — close to the muzzle. Don’t compare numbers between chronograph types without acknowledging that.

Doppler radar chronographs (LabRadar, Garmin Xero, etc.) give you a velocity per shot and downrange retained velocity, are easy to set up, and produce some of the cleanest data available to amateur handloaders. They’re also expensive enough that not everyone has one. If you have one, the data quality is usually excellent. If you don’t, an optical chronograph carefully set up is plenty for serious load development.

Whichever you use, write down which one. A 2,762 fps reading from a LabRadar and a 2,762 fps reading from a Magnetospeed have ever-so-slightly different meanings. Future-you, looking at the number a year from now, will appreciate knowing.

The short version

For each load, in each chronograph session, write down:

• Sample size
• Average velocity
• SD
• ES
• A line about conditions and anything unusual

Tie it to the recipe and the firearm. Don’t bother with the higher-order statistics for small samples. Don’t transcribe every individual shot — record the string and any specific shot that had a story.

Then go shoot the load again next season and see if those numbers reproduce. The point of writing them down is so you can answer that question.