Forums
New posts
Search forums
What's new
Articles
Latest reviews
Author list
Classifieds
Log in
Register
What's new
Search
Search
Search titles and first posts only
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Chatting and General Stuff
General Discussion
Chronographs
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Pdvdh" data-source="post: 574000" data-attributes="member: 4191"><p>I am in pursuit of knowing my MV as accurately as possible. as I believe it to be completely necessary for any ballistics program to dope my down-range hits under the variable conditions I hunt in. These conditions include elevations from sea level to 7000' ASL, temperatures from 32F to 75F, and sloping shots up to 35 degrees. I have no way to field confirm, and then develop drop charts for these variable conditions. I've proven the accuracy of my ballistics program in the locations I am able to field test it against measured down-range drops. Now I want to know the actual MV of my bullet, to give the ballistic software a chance of predicting the proper dope under the variable conditions that I later engage game under. So I think the importance of knowing the MV - as closely as possible - is all relative to the end users' needs. </p><p></p><p>That's the value of the in-field ballistics program, in my opinion. If I always hunted in the same location, and only shot at animals in a few locations, I could simply develop a drop chart for that location(s). Then I might not need to know my MV at all. Simply rely on the drop chart.</p><p></p><p>And reliably confirming the ES and SD is important to any LRH, unless he's willing to live with vertical stringing at extreme ranges.</p><p></p><p>I also confirm the BC of my bullet by recording down-range velocity at 1000 yds. Now with both MV and bullet BC confirmed out of my rifle, a good ballistics program will be able to provide me with the proper dope for my shots under widely varying conditions. Conditions that I'm unable to confirm field drops for prior to, or during, the hunt - prior to taking the shot. Unless, perhaps, I'm in a situation with circumstances that allow me to take a sighter shot off to the side of the game animal on the hillside where I can see the bullet impact, prior to then shooting at the animal.</p><p></p><p>One thing that I haven't mentioned, is the waste of my time that's prevented with the multiple chronographs. I will typically dismiss any load that yields an ES greater than 35-40 fps instantly during load development. For example, if my first two shots vary in MV by more than 40 fps, I won't even spend any more time on that specific load - if the multiple velocity data confirm my chronograph data are valid. </p><p></p><p>In the past when I only used one chronograph, I'm certain that I've wasted time on load development by respecting bogus chronograph data. Without any way of knowing better, I would respect the data. Possibly discarding a good load, or sticking with a bad load longer than necessary.</p></blockquote><p></p>
[QUOTE="Pdvdh, post: 574000, member: 4191"] I am in pursuit of knowing my MV as accurately as possible. as I believe it to be completely necessary for any ballistics program to dope my down-range hits under the variable conditions I hunt in. These conditions include elevations from sea level to 7000' ASL, temperatures from 32F to 75F, and sloping shots up to 35 degrees. I have no way to field confirm, and then develop drop charts for these variable conditions. I've proven the accuracy of my ballistics program in the locations I am able to field test it against measured down-range drops. Now I want to know the actual MV of my bullet, to give the ballistic software a chance of predicting the proper dope under the variable conditions that I later engage game under. So I think the importance of knowing the MV - as closely as possible - is all relative to the end users' needs. That's the value of the in-field ballistics program, in my opinion. If I always hunted in the same location, and only shot at animals in a few locations, I could simply develop a drop chart for that location(s). Then I might not need to know my MV at all. Simply rely on the drop chart. And reliably confirming the ES and SD is important to any LRH, unless he's willing to live with vertical stringing at extreme ranges. I also confirm the BC of my bullet by recording down-range velocity at 1000 yds. Now with both MV and bullet BC confirmed out of my rifle, a good ballistics program will be able to provide me with the proper dope for my shots under widely varying conditions. Conditions that I'm unable to confirm field drops for prior to, or during, the hunt - prior to taking the shot. Unless, perhaps, I'm in a situation with circumstances that allow me to take a sighter shot off to the side of the game animal on the hillside where I can see the bullet impact, prior to then shooting at the animal. One thing that I haven't mentioned, is the waste of my time that's prevented with the multiple chronographs. I will typically dismiss any load that yields an ES greater than 35-40 fps instantly during load development. For example, if my first two shots vary in MV by more than 40 fps, I won't even spend any more time on that specific load - if the multiple velocity data confirm my chronograph data are valid. In the past when I only used one chronograph, I'm certain that I've wasted time on load development by respecting bogus chronograph data. Without any way of knowing better, I would respect the data. Possibly discarding a good load, or sticking with a bad load longer than necessary. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Chatting and General Stuff
General Discussion
Chronographs
Top