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
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
Let's argue about BC's
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="jwp475" data-source="post: 475033" data-attributes="member: 3776"><p>I had trouble with my drops not matching Exbal. I tried different BC's trying to make it work, but I found that I could make it match at certain distances by tweaking the BC not all distances.</p><p> So I went back to square one and started check every variable, score height, zero, reticle level and even re chrono'ed my load.</p><p> </p><p> When I originally chronographed my load the day was very sunny and bright. I average velocity with the 300 SMK was 2820. When I re-chronograhed my load I got 2791. </p><p></p><p> Using 2791 FPS my drops now matched with the published BC. 2790 was the corrected velocity in Exbal when I used the trajectory validation feature.</p><p></p><p> I believe that when a carefully measured BC is not match ones actual trajectory it is because there is an input error that one has missed</p><p></p><p> Makes life much easier when you live near sea level and are planing a hunt at 7,000 or 10,000 feet elevation if the data from your ballistics program can accurately predict your settings without needing to re shoot at the varied distances to confirm</p></blockquote><p></p>
[QUOTE="jwp475, post: 475033, member: 3776"] I had trouble with my drops not matching Exbal. I tried different BC's trying to make it work, but I found that I could make it match at certain distances by tweaking the BC not all distances. So I went back to square one and started check every variable, score height, zero, reticle level and even re chrono'ed my load. When I originally chronographed my load the day was very sunny and bright. I average velocity with the 300 SMK was 2820. When I re-chronograhed my load I got 2791. Using 2791 FPS my drops now matched with the published BC. 2790 was the corrected velocity in Exbal when I used the trajectory validation feature. I believe that when a carefully measured BC is not match ones actual trajectory it is because there is an input error that one has missed Makes life much easier when you live near sea level and are planing a hunt at 7,000 or 10,000 feet elevation if the data from your ballistics program can accurately predict your settings without needing to re shoot at the varied distances to confirm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
Let's argue about BC's
Top