Scope not tracking or something else?

[huntoregon]

I have a 7PRC with a Leupold VX-6 that has always shot great with factory ammo. I recently started working up a load for it and shot it over a chronograph today. Got muzzle velocity and zeroed at 100 yards. Setup a target at 625 yards, plugged in gun/bullet data into my Kestrel 5700 and it called for 11.25 MOA elevation. Cranked the turret up and shot high. Turned the scope down 1 MOA and shot again, hit steel this time but the very top of the target around 8-9" high so I could have dialed another MOA down and still been alright. I checked another bullet drop app and it called for real close to the Kestrel. I doubt velocity is that far off. I don't know what else to think other than the scope is not tracking properly. Any ideas?

 

[Rob01]

All the rest of your variables and environmentals set up right in your program?

Easy way to test if it's the scope by just putting another scope on and see what happens.

 

[SteveALA]

Have you trued your coefficient? Look up Barbour Creek on you tube and search for James' video to do that

 

[Teri Anne]

I have a 7PRC with a Leupold VX-6 that has always shot great with factory ammo. I recently started working up a load for it and shot it over a chronograph today. Got muzzle velocity and zeroed at 100 yards. Setup a target at 625 yards, plugged in gun/bullet data into my Kestrel 5700 and it called for 11.25 MOA elevation. Cranked the turret up and shot high. Turned the scope down 1 MOA and shot again, hit steel this time but the very top of the target around 8-9" high so I could have dialed another MOA down and still been alright. I checked another bullet drop app and it called for real close to the Kestrel. I doubt velocity is that far off. I don't know what else to think other than the scope is not tracking properly. Any ideas?

When testing anything, especially bullet drop based on any of the so called applications keep in mind that these applications were developed on a computer with certain information fed into said computer for a computer analysis. No two rifles shoot the same, heck no two cartridges loaded in the same lot shoot the same as evidenced by chronograph readings. Winds shift on long range shots. I have been in 1000 yard matches where the range flags were showing the winds 180 degrees from each other at different points down range. All of these fancy applications will get you in the ball park, but when in the real world not all data is as programmed into your application. It's not your rifle, it's not your ammo, and most likely not your scope that is the issue. It is you believing that just because you set up your shot based on the Kestrel information that it will be exactly so. Not going to happen in the real world.

 

[FEENIX]

All the rest of your variables and environmentals set up right in your program?

Easy way to test if it's the scope by just putting another scope on and see what happens.

This! Regardless of the apps, the output is only as good as the input.

Known:
-- 7PRC/Leupold VX-6 has always shot great with factory ammo.
-- Zeroed at 100Y
-- With +11.25 MOA elevation @ 625Y = + 8-9"
-- Kestrel 5700 used

Unknown:
-- Bullet and BC used
-- MV

Share the unknown attributes and other pertinent information for the LRH community to help you troubleshoot.

 

[skipglo]

As stated above...true your BC...or....up your speed in your program till it matches your shots POI

 

[robpiat]

Do a box test at 100-200 yards.

 

[8andbait]

Easy way to check, do a tall target test at 50 or 100 yards. Must be exact yardage or you'll have to do some math. Do that and you will know if it's tracking or not.
I would also suggest at minimum a 10 shot group for your zero.

 

[Mike D Texas]

Something else is off, most likely in your data input.

2MOA at 625 yards is too much error to be mechanical.

I've never had my Kestrel be off more than .1 MIL out to a mile.

 

[osok-1k]

I agree that you should confirm your scope tracking with a tall target test, Leupold scopes ain't what they use to be, but then neither am I

 

[med358-boise]

If I am interperetting you OP correctly, your first shot was approximately 2.5 MOA high.

I would proceed in the following order:

1) Run a box test at 100.

2) Shoot a target at 363 yards with the appropriate calcs and see if you have a consistent error.

If item 1 proves good tracking and item shows an error consistent/proportional with the 625 yard test then I would shoot at 100, 300, and 500 without adjusting clicks and true for BC.

 

[ShtrRdy]

What kind of chrono were you using? How many shots did you measure velocity?

Did you have a Magnetospeed attached to the barrel when you zero'd the gun?

 

[WYMIKE]

Make sure the zero calculation is in fact for 100 yards. I use a 200 yard zero for most rifles. With 1/4 minute click values on your scope. re-check zero distance in the Kestral.

 

[Doom2]

All ballistic solvers are an approximation. I'm assuming you are using AB's with the Kestrel which is a very good one but it's only as good as the inputs. I don't know the bullet used but the BC may well be off or your velocity may wrong depending on the chronograph. The scope height above bore can be a factor as can be just how accurate your zero is. Ultimately what matters is what happens on target and historically that is called Dope (Data On Previous Engagements). That is what truing your ballistic solver is all about.