Thread: Trajectory Validation

Originally Posted by Pop Shot

+1

My Bushnell 6500 over-dials about the same distances as you mention. It took me a while to figure it out and get everything sorted. I thought it was my velocity then the projectiles BC but it turned out to be the scope click values. All sorted and verified now! On target out further than I can realistically shoot!

Mine is a 6500 as well. Still have it as it is a reliable scope but use it on my .223 which I rarely dial unless varmiting.

Sent from my SM-G900F using Tapatalk

Originally Posted by R93

Agree with zimmer. I had a Bushnell that was .30 per click opposed to .25

Does not explain your low MPI at 200 tho.
Is your setup and position exactly the same all the time.
If using rear support for the stock ie a bag of sorts, and if not perfect every time it will explain vertical variations as well.



Sent from my SM-G900F using Tapatalk

Not the same. 200m shooting prone off front and rear bag rest. Longer distances front and rear bag over ute bonnet to get high enough above the scrub.

Might need to go back to basics. Test scope tracking. Run loads over chrony again.

Good idea to go back to basics just to confirm stuff.

There is imo however, a position problem and a difference that will cause vertical variations when changing from shooting prone supported and standing supported.

The difference of surface your support is resting on is one thing.
Next is how the rifle is allowed to recoil.
The butt of the rifle is sitting differently in your shoulder between positions. One being more supported than the other.

Recoil is being absorbed through your body differently affecting our POI.
Try and find a way to shoot the same everytime and make a drill out of it.
Talk yourself through every setup and shot and you should see some consistency both on the range and in the field that we all strive to achieve.




Sent from my SM-G900F using Tapatalk

Forget the chrony. I use shooter, but im sure most programmes are the same.

Enter in your data and get the programme to work out your velocities and go from there. You have enough data to do it. If the 200 is an obvious error, leave that data out.

Mill is a mystery to me, I work in moa...but if you get real stuck I could convert it and plug it into shooter if you have no luck.

Kj

The others have a good point though, first validate your scope click values. Doesn't matter what they are, as if known error exists this can be accounted for too.