Brambles
Well-Known Member
I was shooting at 690 and 942 the other day with disappointing results, pretty much my fault for not compensating for spin drift. After I dialed the drift I hit the 690 consistently...but the 942 was a bit more challenging....something wasn't jiving with my solution...
it seemed like I was getting a bit more drift than predicted, so rechecked my level, found it a slight bit off.....then went and shot a tall target test..
This is where I found out my nightforce needs to have a correction factor.
Shooting at 100 yards ....Leica 1600
10 MOA dialed (expected 10.41)equaled 10.75" = .966 c/f
20 MOA dialed (expected 20.94)equaled 21.625"= .974 c/f
30 M0A dialed (expected 31.41)equaled 32.5"= .968 c/f
So I rounded the c/f to .97 and imputed that into shooter...
Which now is gonna make me change my velocity validation since the inches drop is off now....moving from 2750 fps to 2716 fps seems to bring the data back in line....I use a chrono very little since it's not an expensive unit and I thought it was lying to me...IIRC when I was chronoing this load during development it said 2716 fps....lol...quite a lesson on having the proper inputs....
The screwy C/F was causing me to think my velocity was higher than it actually was when I did previous velocity validation..
Is this a typical acceptable nightforce correction factor ?
it seemed like I was getting a bit more drift than predicted, so rechecked my level, found it a slight bit off.....then went and shot a tall target test..
This is where I found out my nightforce needs to have a correction factor.
Shooting at 100 yards ....Leica 1600
10 MOA dialed (expected 10.41)equaled 10.75" = .966 c/f
20 MOA dialed (expected 20.94)equaled 21.625"= .974 c/f
30 M0A dialed (expected 31.41)equaled 32.5"= .968 c/f
So I rounded the c/f to .97 and imputed that into shooter...
Which now is gonna make me change my velocity validation since the inches drop is off now....moving from 2750 fps to 2716 fps seems to bring the data back in line....I use a chrono very little since it's not an expensive unit and I thought it was lying to me...IIRC when I was chronoing this load during development it said 2716 fps....lol...quite a lesson on having the proper inputs....
The screwy C/F was causing me to think my velocity was higher than it actually was when I did previous velocity validation..
Is this a typical acceptable nightforce correction factor ?