This past weekend I had a friend from Alaska come to Colorado to shoot ELR At my Range.
We have targets every 100 yards to 1775, and this weekend we added a second target to 1815 yards, why not.
James came down with only 110 rounds of ammunition, 60 for his 300NM, and 50 for a 37XC, the focus is quality, not quantity. We wanted to look at confirming the software, gaining confidence in the systems, working in the wind, and being able to successfully engage targets on command.
So we have goals in mind and I am working on a process for guys who want to engage in ELR Shooting and being able to reference the data in a meaningful way. We are looking for patterns here, as an example, we learned if we round his software down to the nearest tenth the impacts were much better. They did trend low, but lower was easier to spot, to adjust with, and keeps everything on the target or at least very close in the FOV. We found even low we still impacted the plate very well, and with most of the shots, the targets were very close to the waterline.
I have an idea for a plotting system or databook layout as we do things slightly differently than in the past. The idea focuses on less of a book or more a folder that holds your electronics and well as giving you something for notes. It's more of a battle board design vs a traditional databook as I don't think we work the same as we once did.
We had great conditions, the first day was a very light wind, 2 to 3 mph. Perfect for collecting data. The second day the winds grew from 3 to 8 and then ending up on the final shots around 12MPH before jumping to 20+ on the way home.
Hits were all solid:
Actual vs Predicted
One of the keys to shooting ELR is determining the software's ability to stay on track. We find the software is fickle at these ranges but so is the ability to correctly range the target. I used my Vectronix as well as knowing the layout of the range. Ranging was a big key, so much so I realized for every shot we needed a checklist not just for the range, but also for the conditions. We found a single lapse in updating the atmosphere at beyond 2000 yards resulted in a .1 variation. This was just an 800ft DA change, but it was enough to be visible. That point can put you over the top or just in front of a target.
Through our recording keeping, we found the pattern, round low, then manage the wind. WTF added an additional "F" to the equation. Normally WTF is Wind, Target, Fundamentals, but in this case, it was Wind, Target (range) Field Conditions .. weather
I am happy to say we hit a lot more first-round impacts than we missed and every target was pretty much an odd range, we just moved to a spot that gave us a decent FOV on the targets, dropped down, ranged it, and engaged them. This is helpful with the software because we had to be right and we see where the variation lies at these distances.
The plates as big as they are can only suffer .2 mils of variation elevation wise. The math might say otherwise, but the reality was, in the cases, we purposed adjusted off and then back on we found .2 was the limit, any dancing of the turrets past that probably means a miss.
SD & CE,
it's wrong, just stop, I get it, but it's wrong.
I did not use it once but we calculated the effects after the fact, so We had SD & CE turned off, but that does not mean we did not check it every shot to see what the computers fed us. Wrong, enough said, it's wrong.
Windwise I had Wind Finder Pro and a local Airport less than 4 miles away. So I had solid prevailing wind data. Wind Finder Pro gave me 3 MPH. I read an average of 2 MPH at my location and used that on the first day. Our hits were solid with more first-round hits than misses.
It's the wind, that's it, I actually shot a video on this in real-time but I hesitate to post it because people with next to no experience doing this will argue the other direction. My hit rate is unmistakable, so while I understand what the math says, it's wrong.
My calls are solid,
As I said, I did a video of this during the shots, so it's not revisionist history, it's in the moment.
I really am tired of arguing the fact, but let's be honest, without these built-in excuses what are guys gonna blame when they miss. We turned it off and never mentioned it during the shot, only after to see where the computer would have put the shot vs my call.
Dope the wind, seriously, we are truing against data with it included we dont' need it twice.
The last comment on the subject, check your numbers, run them with and without and look at the wind, what is it doing We had wind from the left, so that would be more right-leaning drifts, but even still it's the wind call, not the drifts.
">
We have targets every 100 yards to 1775, and this weekend we added a second target to 1815 yards, why not.
James came down with only 110 rounds of ammunition, 60 for his 300NM, and 50 for a 37XC, the focus is quality, not quantity. We wanted to look at confirming the software, gaining confidence in the systems, working in the wind, and being able to successfully engage targets on command.
So we have goals in mind and I am working on a process for guys who want to engage in ELR Shooting and being able to reference the data in a meaningful way. We are looking for patterns here, as an example, we learned if we round his software down to the nearest tenth the impacts were much better. They did trend low, but lower was easier to spot, to adjust with, and keeps everything on the target or at least very close in the FOV. We found even low we still impacted the plate very well, and with most of the shots, the targets were very close to the waterline.
I have an idea for a plotting system or databook layout as we do things slightly differently than in the past. The idea focuses on less of a book or more a folder that holds your electronics and well as giving you something for notes. It's more of a battle board design vs a traditional databook as I don't think we work the same as we once did.
We had great conditions, the first day was a very light wind, 2 to 3 mph. Perfect for collecting data. The second day the winds grew from 3 to 8 and then ending up on the final shots around 12MPH before jumping to 20+ on the way home.
Hits were all solid:
Actual vs Predicted
One of the keys to shooting ELR is determining the software's ability to stay on track. We find the software is fickle at these ranges but so is the ability to correctly range the target. I used my Vectronix as well as knowing the layout of the range. Ranging was a big key, so much so I realized for every shot we needed a checklist not just for the range, but also for the conditions. We found a single lapse in updating the atmosphere at beyond 2000 yards resulted in a .1 variation. This was just an 800ft DA change, but it was enough to be visible. That point can put you over the top or just in front of a target.
Through our recording keeping, we found the pattern, round low, then manage the wind. WTF added an additional "F" to the equation. Normally WTF is Wind, Target, Fundamentals, but in this case, it was Wind, Target (range) Field Conditions .. weather
I am happy to say we hit a lot more first-round impacts than we missed and every target was pretty much an odd range, we just moved to a spot that gave us a decent FOV on the targets, dropped down, ranged it, and engaged them. This is helpful with the software because we had to be right and we see where the variation lies at these distances.
The plates as big as they are can only suffer .2 mils of variation elevation wise. The math might say otherwise, but the reality was, in the cases, we purposed adjusted off and then back on we found .2 was the limit, any dancing of the turrets past that probably means a miss.
SD & CE,
it's wrong, just stop, I get it, but it's wrong.
I did not use it once but we calculated the effects after the fact, so We had SD & CE turned off, but that does not mean we did not check it every shot to see what the computers fed us. Wrong, enough said, it's wrong.
Windwise I had Wind Finder Pro and a local Airport less than 4 miles away. So I had solid prevailing wind data. Wind Finder Pro gave me 3 MPH. I read an average of 2 MPH at my location and used that on the first day. Our hits were solid with more first-round hits than misses.
It's the wind, that's it, I actually shot a video on this in real-time but I hesitate to post it because people with next to no experience doing this will argue the other direction. My hit rate is unmistakable, so while I understand what the math says, it's wrong.
My calls are solid,
As I said, I did a video of this during the shots, so it's not revisionist history, it's in the moment.
I really am tired of arguing the fact, but let's be honest, without these built-in excuses what are guys gonna blame when they miss. We turned it off and never mentioned it during the shot, only after to see where the computer would have put the shot vs my call.
Dope the wind, seriously, we are truing against data with it included we dont' need it twice.
The last comment on the subject, check your numbers, run them with and without and look at the wind, what is it doing We had wind from the left, so that would be more right-leaning drifts, but even still it's the wind call, not the drifts.
">