CF Junkie
Gold $$ Contributor
charlie b,
I looked more carefully at your pictures and tried to determine if the velocity differences in each group had any relationship to the position of the particular round on the target.
The 23.2 load would lead me to believe a higher velocity would result in a bullet position that is slightly lower.
But the 23.3, 23.4 and 23.5 loads seem to violate that result that the higher velocity would have a lower POI.
I generally get the same result with slightly higher muzzle velocities.
I find that 0.1 gr of powder results in 10 to 11 fps change in predicted velocity. Your velocity numbers don't seem to result in that kind of difference.
I'm not sure this particular velocity ladder can be relied upon to make a decision on accuracy.
The 23.2 group seems to be the most consistent for 3 groups, but the two loads with velocities the closest (9 fps) are the furthest apart and the two close groups have velocity differences of 29 fps.
The 23.3 gr load has the two closest rounds (with a velocity difference of 38 fps almost touching with the higher velocity very slightly lower while the round with a velocity difference of 21 fps is lower still and to the right. The 23.3 load actually might be your best velocity group of the ladder if the #11 round wasn't off to the right (possible shooter induced variation) and the highest velocity round was actually higher than the two slower rounds.
The 23.4 load result show a larger separation that 23.2 for rounds with velocity difference of 4 fps with the slowest round and fastest round with just about the same vertical position for POI even though the velocity difference is 37 fps.
The 23.5 load result seems to follow the premise, but the higher velocity round (by 22 fps) was much lower than the 23.2 load would predict.
Most of the single round separations are to the right of the two groups with the closest velocity, with the exception of the 23.2 & 23.5 groups.
Part of the reason I don't have much confidence in velocity ladders is that the natural powder/primer burn variation seems to have about the same extreme difference in velocity as 0.2 grains of powder (about 22 fps).
Other than consistency in individual round position, there isn't any real basis for judging on the base of velocity.
That probably shows my personal bias.
I generally try to decide on the best load for a powder/bullet combination based upon the overall average group size for at least 10 to 20 5-round groups.
I believe that is statistically more accurate.
I decide upon choosing that I have a sufficient number of groups based upon the Standard Deviation of the group sizes within the sample. If the St Dev is small (around 0.030) , the variance is relatively small, so I could make my decision based upon a 10 group average. If the St Dev is larger, I continue to shoot groups until I get a larger sample up to a limit of 20 groups.
It takes a lot more rounds to make a decision, but once you decide, I then shoot a lot of groups using the best load for that bullet/powder combination.
That approach seems to work for me, but it is not a low cost solution.
I looked more carefully at your pictures and tried to determine if the velocity differences in each group had any relationship to the position of the particular round on the target.
The 23.2 load would lead me to believe a higher velocity would result in a bullet position that is slightly lower.
But the 23.3, 23.4 and 23.5 loads seem to violate that result that the higher velocity would have a lower POI.
I generally get the same result with slightly higher muzzle velocities.
I find that 0.1 gr of powder results in 10 to 11 fps change in predicted velocity. Your velocity numbers don't seem to result in that kind of difference.
I'm not sure this particular velocity ladder can be relied upon to make a decision on accuracy.
The 23.2 group seems to be the most consistent for 3 groups, but the two loads with velocities the closest (9 fps) are the furthest apart and the two close groups have velocity differences of 29 fps.
The 23.3 gr load has the two closest rounds (with a velocity difference of 38 fps almost touching with the higher velocity very slightly lower while the round with a velocity difference of 21 fps is lower still and to the right. The 23.3 load actually might be your best velocity group of the ladder if the #11 round wasn't off to the right (possible shooter induced variation) and the highest velocity round was actually higher than the two slower rounds.
The 23.4 load result show a larger separation that 23.2 for rounds with velocity difference of 4 fps with the slowest round and fastest round with just about the same vertical position for POI even though the velocity difference is 37 fps.
The 23.5 load result seems to follow the premise, but the higher velocity round (by 22 fps) was much lower than the 23.2 load would predict.
Most of the single round separations are to the right of the two groups with the closest velocity, with the exception of the 23.2 & 23.5 groups.
Part of the reason I don't have much confidence in velocity ladders is that the natural powder/primer burn variation seems to have about the same extreme difference in velocity as 0.2 grains of powder (about 22 fps).
Other than consistency in individual round position, there isn't any real basis for judging on the base of velocity.
That probably shows my personal bias.
I generally try to decide on the best load for a powder/bullet combination based upon the overall average group size for at least 10 to 20 5-round groups.
I believe that is statistically more accurate.
I decide upon choosing that I have a sufficient number of groups based upon the Standard Deviation of the group sizes within the sample. If the St Dev is small (around 0.030) , the variance is relatively small, so I could make my decision based upon a 10 group average. If the St Dev is larger, I continue to shoot groups until I get a larger sample up to a limit of 20 groups.
It takes a lot more rounds to make a decision, but once you decide, I then shoot a lot of groups using the best load for that bullet/powder combination.
That approach seems to work for me, but it is not a low cost solution.










