med358-boise
Well-Known Member
Do any of you guys do calculations calculating expected shot error or dispersion and "tolerance stacking"?
Let me give an example, so I shoot a 284 Win with a Barnes 145 LRX @ 2925.
So at 600 yards with my typical environmentals (temp, altitude, humidity), I know that a 1 mph incorrect wind call is 2.5" of error, and at 4 mph an 1/8th of an error of in wind value is 1.25 inches, my .5 MOA rifle has an expected dispersion of 1.5 inches, and 1 crosshair width of error is 1.25 inches so if those stack in the same direction that is 6.25 inches of error so the likelihood of hitting a 10 inch target on the first shot could be pretty low.
Do any of you folks do similar calculations to establish rules of thumb for whatever "pre-shot" planning or shot taking decision purposes? I am not suggesting that this is run for every scenario
For me, the application determines who buys lunch? and there is of course the right to opt out of the bet but opting out to often subjects me to at least 10 minutes of ridicule about every other day for a week.
(edited for clarity)
Let me give an example, so I shoot a 284 Win with a Barnes 145 LRX @ 2925.
So at 600 yards with my typical environmentals (temp, altitude, humidity), I know that a 1 mph incorrect wind call is 2.5" of error, and at 4 mph an 1/8th of an error of in wind value is 1.25 inches, my .5 MOA rifle has an expected dispersion of 1.5 inches, and 1 crosshair width of error is 1.25 inches so if those stack in the same direction that is 6.25 inches of error so the likelihood of hitting a 10 inch target on the first shot could be pretty low.
Do any of you folks do similar calculations to establish rules of thumb for whatever "pre-shot" planning or shot taking decision purposes? I am not suggesting that this is run for every scenario
For me, the application determines who buys lunch? and there is of course the right to opt out of the bet but opting out to often subjects me to at least 10 minutes of ridicule about every other day for a week.
(edited for clarity)
Last edited: