Gunsmithing Remage Headspace help

Rwh5217

Private
Minuteman
Aug 14, 2020
3
2
New to the site and building first bolt gun so take it easy on me.

So I am assembling my Remington 700 with a remage barrel from criterion. I have stripped the bolt down with the exception of the extractor. I insert the go gauge hooking it on the extractor and sliding it into the chamber. Bolt handle drops all is good. Same process with no go- bolt handle does not drop- all good. Headspace seems right. So I reassemble the bolt and throw a case in the chamber and it will not go. Feels like the extractor is not making it over the rim of the case. Probably user error here but like I said I’m just learning. Any help would be great!
 
A case or a round? A fired case or a virgin case? A sized fired case or unsized fired case? Can you move the extractor with screw driver? There have been some bolts made with out enough clearance for the extractor to move.
 
carefully remove it, and look under the ends. The extractor is like a little leaf spring. It has to bend so it can pop over the case rim. The ends of it have to be able move so it can bend. The extractors are cheap enough, I would try another one. If you don't see anything under this one stopping its movement. There have been reports of a few bolts that the groove the extractor rides in was not cut deep enough, so there is no room for the extractor to move. Some shcmutz underneath it can cause the same problem.
 
Gentlemen I appreciate the feedback. So to add more detail- I assembled the rifle no issues. Sent it to be cerokoted and immediately after that couldn’t chamber a round. Second guessed myself on the head spacing so checked it again and all was fine. Took it to a gunsmith today as I did not want to remove the extractor on my own and didn’t have one to replace it. He found a “burr” on the extractor rivet that he knocked off and it will now chamber a round. You really have to send it home but he said it should loosen up a little as i cycle it. He also said cerakote around the extractor may have caused an issue as well. Appreciate everyone’s input!