Tikka Performance billet .223 magazine

[BurnOut]

I just received a billet .223 magazine for use with factory (or factory replacement) T3 bottom metal/plastic, and I have to say that I am VERY pleased with it. We all know that all T3 actions are the same length, whether they're fitted with a .223 Rem-class barrel, a .308 Win-class barrel, or a 30-06-class barrel, with only the bolt stop differing between the short and long action configurations of the action its self (and the diameter of the bolt face, obviously).

While the T3 action is limited in regard to OAL for true long action cartridges (IMO), this configuration is fan-friggin'-tastic for short action (either .223 Rem-class or .308 Win-class) setups, because it allows for as much cartridge length as you could reasonably desire.

In any event, the Tikka Performance billet .223 mag takes advantage of this, and offers a measured internal dimension of ~2.62... when cartridges in this (.223 Rem) class have "official" OALs of 2.26! I have some .204 Ruger loads that are right at .200" over the SAAMI length at 2.46x" (running the Berger 55 gr projectiles), and they fit in the mag with room to spare. I was counting on having single feed these rounds, but it now looks like I have the option of running them in the mag.

Anyhow, just wanted to spread the good word... two thumbs up from me!

 

[spife7980]

And they feed well and dont get all slipped up on one another with all that rattling around space??

 

[BurnOut]

I've only played with it at home (read: I haven't tried shooting from the mag yet), but so far so good on my ballistic-tipped rounds (the longest of which is 2.348"), but something goofy is going on when I try to feed the 2.46x" rounds... it's like they're coming out of the mag too nose-high and getting caught on something. If I slide the bolt forward to grab one from the mag, it'll get jammed up coming out of the mag... but if I release forward pressure on the bolt and let the nose of the cartridge drop, it then feeds fine.

I plan to see if I can figure out what's causing the issue, but haven't had a chance to do so yet.