NXS Gone Bad?

[6BRinNZ]

Hi,

has anyone had a NF NXS 5.5 -22 x56 go bad. The last couple of shoots I have been out on I have had very inconsistent results...I thought maybe it was me and had discounted it being the scope as it is a NF NXS...but the more I thought about it....

I will go up to the range and check, but I thought I would ask if anyone has problems with this model, I do know of the BR models playing up but haven't heard of an NXS being a problem....I though the 5.5 - 22 x 56 was made for 50 cal...I'm only using a 6br...less than 200 rounds through it.

Thanks in advance.

 

[tenring]

Certainly any scope can "go bad". You need to amplify that statement. I would try a different scope next. If all else fails, call NF. Their customer service is tops.

 

[6BRinNZ]

Amplify - basically I am having issues with elevation, windage appears to be ok, I use it for varminting and crank elevation...the rifle is very accurate and the first time I went out I hit pretty much everything I pointed at out to 500yrds. Since then I have had inconsistent results, I have had to allow 1-2 moa (elevation) more than I would expect (I am using berger drop charts and Brian litzs G7 BCs) and also missed no brainer shots at around 200yrds. Other times I have connected repeatedly at 440yrds.

When i first zeroed at the range I thought the clicks moved a little more than I expected (over an inch at 200yrds)...but seemed to come right.

All of this could just be me and I will go up to the range and check but thought I would ask as I just can't explain it - even allowing for poor technique, wind etc etc....but -to me the nxs seem to have such an impressive rep....

Thanks

 

[CaptainMal]

Just stick a bore-sighter in, look and move things around. When I think a scope might be bad, that's the first thing I do.

Simple. You can watch all adjustments and power changes with pretty good detail.

 

[Mark Walker in TX]

Time for a box test....

 

[fdshuster]

As Mark said, time for a box test and/or mount a different scope that is known to be trouble-free.

 

[6BRinNZ]

Thanks guys, it will be another two weeks before I can get up to the range....at least you don't think I am nuts suspecting the scope...

 

[NateHaler]

I think it's quite likely it's you/range estimation/conditions that are to fault for your missed shots, and not the scope.

There is NO substitute for actual observed data vs. ballistic software and predictions based on BC or whatever. The latter is fine to get you in the neighborhood. Relying on it further is a mistake. You need to shoot your rifle and loads in the intended conditions to understand what your comeups and windage need to be.

Blaming the scope as the likely culprit, while understandable (because it's easy), isn't going to rule out the much likelier factors.

Distance, altitude, humidity, temperature, wind, load performance, and your ability to integrate all of those into a shooting session is the trick. I've observed a world-record holding long distance shooter completely missing a (big) target at 600y -- because he hadn't anticipated the load performance at a different altitude in different weather.

Good luck solving your challenge. And if you shoot the box test, be sure to really crank some elevation and windage in the process. In other words, don't shoot a 4" box test at 100m. Crank in 3 meters of adjustment at a distance of at least 300 meters to see what's happening. And if your range estimation while varminting is off, then you'll miss. Are you using a rangefinder?

 

[brian427cobra]

I expect to break my scopes, so I always buy scopes with lifetime warrenties like Nightforce, and Premier Reticles, I am no Leupold fan, great warrenty in a crappy product IMHO.

 

[mikecr]

There is NO substitute for actual observed data vs. ballistic software and predictions based on BC or whatever. The latter is fine to get you in the neighborhood. Relying on it further is a mistake. You need to shoot your rifle and loads in the intended conditions to understand what your comeups and windage need to be.

Well, for those of us who occasionally shoot beyond ’intended’ /BR conditions, ballistic software predictions -using whatever- works pretty damn good.

I've observed a world-record holding long distance shooter completely missing a (big) target at 600y -- because he hadn't anticipated the load performance at a different altitude in different weather

And this is an example of where ballistic predictions are beneficial, and should have been part this ‘record-holding’ shooter’s routine….
So what was your contention here?
That thread starter should rely on observed data, rather than ballistic prediction, while integrating everything into a shooting session,, but that it’s likely him/range estimation/conditions that are to fault for his missed shots?
I can’t conclude any basis here, for whatever you’re suggesting…

Anyway,,
I have had an NXS throw me into a tail-chase-o-thon, because I too resisted the notion of a scope problem. Eventually sent it to NF, they said it was a lens bedding issue & fixed it with a 2 day turnaround(amazing). I’ve since read where others ran into this on forums. Seems rare but possible.
NF did not charge. They returned the same serial# scope to me, and the problem was gone. No problem since.
Save yourself the saga, and send it to NF for checkout.

 

[6BRinNZ]

NateHaler - yes I do use a range finder, my drop charts are also compensated for elevation (the berger tool shows settings if you hover over the pressure I think it is). My hand loads are trimmed deburred and loaded to the granule, so outside of the me and wind factor there isn't much more I can do. the winds on the day were only 2 mph (yep got a wind meter as well) so balistically there didn't seem to be anyway the wind could throw things out this much for elevation.

What i will do is check the scope at the range as this seems easy enough to do.

Mikecr - thanks for the info I have had a brand new leupold go west on me and know personally of a couple of NF BRs that broke...unfortunately from this part of the world it is about a two month turn around...

I guess my big concern is if it isn't the scope...then what the heck could it be....anyways i guess I will answer this question once I am done testing.

All - Once again thanks for the input it is appreciated.