• Frank's Lesson's Contest

    We want to see your skills! Post a video between now and November 1st showing what you've learned from Frank's lessons and 3 people will be selected to win a free shirt. Good luck everyone!

    Create a channel Learn more
  • Having trouble using the site?

    Contact support

Hornady Black 6.5 creedmoore FPS not matching

Maassasin

Private
Minuteman
May 3, 2021
3
0
Fort Polk
The other day my buddy and I took out our savage axis precisions his is a .270 and mine is a 6.5 creedmoor. He had brought a chrono to check his reloaded rnds FPS and we decided to test mine and it showed 1930 fps, through a 24" barrel. The box said that the FPS shoud be around 2600 fps through a 26" barrel. I know an inch is about 50 fps difference but 700 fps difference?? Has anyone else had this issue?
 
I actually can't imagine that is correct. Yeah there will be a difference, but 1930 sounds way off to me. Did you confirm that muzzle velocity at any distance?
 
We had the chrono out at 7m, 10m and 15m away. I shot 20 rnds and they were staedy 1930-1950 fps. My buddy had shot 10 rnds of reloaded 270 and they were steady at 2760-2770 fps. Not sure the name of the chron9 but it was brand new out the box, and he had called me to stop and pick up a 9v so it had a brand new battery. I did put a flutted bolt sleeve and a bolt lift kit on it, I can see more the bolt face friction washer its not completely crushed between the bolt face and sleeve, could that be an issue? It shoots though no issues.
 
Agree - something is way off with that Crono...

Shooting this out of two different rifles with a Magnetospeed and verified out to 1250 yds. I was getting in the 2750 to 2800 FPS range at max - here is the data across 35 rounds from a 6.5CM 24" Bergara HMR Pro. A Curtis Custom with 26" barrel was in a similar range with a little over 2800.


Series
1​
Shots:
35​
Min
2731​
Max
2800​
Avg
2769​
S-D
17.4​
ES
69​
55 deg64% humidity
30.33hg
SeriesShotSpeed
1​
1​
2757​
ft/s
1​
2​
2754​
ft/s
1​
3​
2741​
ft/s
1​
4​
2758​
ft/s
1​
5​
2763​
ft/s
1​
6​
2734​
ft/s
1​
7​
2731​
ft/s
1​
8​
2770​
ft/s
1​
9​
2776​
ft/s
1​
10​
2769​
ft/s
1​
11​
2798​
ft/s
1​
12​
2782​
ft/s
1​
13​
2784​
ft/s
1​
14​
2783​
ft/s
1​
15​
2776​
ft/s
1​
16​
2754​
ft/s
1​
17​
2740​
ft/s
1​
18​
2750​
ft/s
1​
19​
2761​
ft/s
1​
20​
2785​
ft/s
1​
21​
2777​
ft/s
1​
22​
2800​
ft/s
1​
23​
2777​
ft/s
1​
24​
2770​
ft/s
1​
25​
2772​
ft/s
1​
26​
2778​
ft/s
1​
27​
2780​
ft/s
1​
28​
2775​
ft/s
1​
29​
2769​
ft/s
1​
30​
2751​
ft/s
1​
31​
2778​
ft/s
1​
32​
2765​
ft/s
1​
33​
2794​
ft/s
1​
34​
2778​
ft/s
1​
35​
2794​
ft/s
----------------
 
We have atns'so we were getting a zero at a 100yds and zeroing our ABLs so couldn't tell you what the drop was past that, but I was worried because for the ballistics profile in the atn you have to set a profile with velocity and grain so when we laser the target it adjust auto and when I was seeing 1930FPS I was getting a little frustrated because I know that isn't right.
 
An optical chrono should be set 10' in front of the muzzle, not 21' or further.
Make sure you're shooting through the upper center and that you don't have the sun directly overhead.
Yeah, and put a good battery in it.
 
  • Like
Reactions: MarshallDodge
Make a blast shield in front of the chrony with a small window to shoot through or use a cardboard box to put the chrony in and again shoot through a small hole. Sometimes it’s picking up shockwaves or muzzle blast. Also color the projectile with a dark sharpie to help it get picked up by the sensor. Light direction, cloudy/clear skies can also have an impact on it as well.
 
QuickLoad with H4350 as the powder and a 140 grain ELD-M seated at COL of 2.825" says that would be around 30 grains of powder...well below the minimum recommended load (and likely below what would yield safe and consistent combustion). As others have said, likely a chrono issue barring some weird failure while manufacturing that ammunition.

The issue isn't too uncommon...at least the second time I've come across it in the past month. Sometimes it's a chrono setup error, or poor shot detection. Sometimes it's a conditions/atmospherics issue.