AR15 Buffer Retainer Problem

[photog_shooter]

I took one of my AR's out this afternoon for some sub-zero shooting. It fed like a champ, no issues at all. I returned home with it and when I was putting it down, I heard a small rattle coming from inside the gun. I pulled the rear takedown pin and as I was about to open the upper/lower halves, I noticed that the buffer tube and spring were not being held back by the retainer. After closer inspection and testing, I found out that cocking the gun with the charging handle, now not only cocks the rifle, but it also pops the buffer retainer, allowing the buffer tube and spring to move forward into the firing mechanism area. Obviously something is wrong here but I'm a noob in the AR world and I'm not really sure what the exact problem is. Any help would be appreciated. Thanks!

 

[Greenhorse six]

Ether your buffer tube isn't threaded in enough or the part of it that's over the retainer is nicked and not holding it in place , you should be able to look and see if that's the case though .

 

[mustang979]

Buffer tube is not installed properly. When it is threaded the correct amount, it will limit the travel of the retainer without binding it.

 

[Sqr]

The buffer is not threaded in far enough to hold the retainer down, or the spring and retainer hole location is incorrectly drilled. On some lower receivers this hole is slightly off forcing the buffer to stop on the retainer and not the back of the BC when it is into battery. You can google for the tell tail signs of the marks left on the buffer face from the retainer pin as it slams into it. If this continues to happen it can force the pin from under the buffer tube popping it out.

 

[Lexthedestroyer]

Could also possibly be the buffer tube working its way out if the castle nut hasn't been properly staked, although I imagine you would notice (loose tube, stock canted). Pics would likely help.

 

[photog_shooter]

It's fixed (for now). Hopefully it stays fixed, I guess only time will tell though. It was working fine when i was out, so I found it odd that this issue would just suddenly come up when I got back home. Oh well, c'est la vie I guess.