MPA BA chassis level
- Thread starter Tokytong5
- Start date
- Replies 8
- Views 582
It's in a machined pocket. I don't think there is anyway to adjust it. I don't really use mine but it has been pretty accurate when I checked it against my Send It and others.
How have you determined that it's off?
How have you determined that it's off?
Yeah, if that's the case I would contact Lisa at MPA. They are great to work with. I bet it's nice having Colemans so close. That's our range too but we have a 2 hour ride to get there.
Check and make sure that your level that you are using is zeroed before checking the level of your action. You can do this on any surface, level or unlevel, as long as the bubble is not maxed out.
If you are using a factory 700 or any factory action, do not go off the flat surface of your picatinny rail. You can go by harbor freight and pick up a set a parallel bars. One of those will fit into the bolt race ways. Then you can indicate or level off of the parallel bar.
If you are using a factory 700 or any factory action, do not go off the flat surface of your picatinny rail. You can go by harbor freight and pick up a set a parallel bars. One of those will fit into the bolt race ways. Then you can indicate or level off of the parallel bar.
I've not done that yet. But I've had scopes I've pulled off other platforms that their scope mounted levels are aligned with cross hairs on plumb bob and it doesn't match. And I've tried that with numerous scopes. Also with various scopes and other levels they all work correctly when shooting with turret adjustment or holding the reticle for elevation. Unless I use the chassis level. Then it works for turret elevation but if I hold reticle it is off
I've done a lot of builds with the mpa chassis. I litterly just walked in from doing load development on a 6gt with a defiance action, mpa comp, and a leupy mark 5hd.
The level plane of the mpa built in level is not on plane with the defiance. *i checked it when i read this messge today* This is a rifle that I built for a customer. I mounted the scope with just the barreled action while I had it clamped in the mill vise.
Honestly I would just forget about the built in level. Throw a piece of tape over it. Grayboe makes stocks that has a built in level. The customer asked to have it lined up with the action. So I basically had to cut out a lot of the bedding and epoxy bed the action making sure that both the plane of the action matched the level of the level in the stock.
A couple of things to know about reticle alignment with a plumb bob string... you need to have the rifle mounted securely and level. Hence why I use my milling table vise with v blocks. You can get the reticle where it is perfectly on the string and lock it down in the rings. Then you need to do a tracking test. Make sure that the crosshair or whatever part of the reticle that you have in view of the string is tracking straight up and down and stays on the reference point on the reticle that you started with. If it tracks left or right of the string then you have to decide how you want it mounted. You either mount the scope where it is tracking straight or you mount it where the reticle is straight so that you would need to use hold over. A lot of scope manufacturers have a 5 degree tolerance for this with quality control. I am ocd and would pull my hair out when this happens. Most of the time it's on cheaper scopes but I have seen more expensive scopes do this as well over the years.
With your scope doing what it is with being straight when you are dialing and off when using holdover then they are out a few degrees. If it's not tracking straight when dialing and you are not having to accommodate for spin drift then my guess is that your vertical line is straight and when you dial it is tracking right a smidgen.
The level plane of the mpa built in level is not on plane with the defiance. *i checked it when i read this messge today* This is a rifle that I built for a customer. I mounted the scope with just the barreled action while I had it clamped in the mill vise.
Honestly I would just forget about the built in level. Throw a piece of tape over it. Grayboe makes stocks that has a built in level. The customer asked to have it lined up with the action. So I basically had to cut out a lot of the bedding and epoxy bed the action making sure that both the plane of the action matched the level of the level in the stock.
A couple of things to know about reticle alignment with a plumb bob string... you need to have the rifle mounted securely and level. Hence why I use my milling table vise with v blocks. You can get the reticle where it is perfectly on the string and lock it down in the rings. Then you need to do a tracking test. Make sure that the crosshair or whatever part of the reticle that you have in view of the string is tracking straight up and down and stays on the reference point on the reticle that you started with. If it tracks left or right of the string then you have to decide how you want it mounted. You either mount the scope where it is tracking straight or you mount it where the reticle is straight so that you would need to use hold over. A lot of scope manufacturers have a 5 degree tolerance for this with quality control. I am ocd and would pull my hair out when this happens. Most of the time it's on cheaper scopes but I have seen more expensive scopes do this as well over the years.
With your scope doing what it is with being straight when you are dialing and off when using holdover then they are out a few degrees. If it's not tracking straight when dialing and you are not having to accommodate for spin drift then my guess is that your vertical line is straight and when you dial it is tracking right a smidgen.
Last edited:
Thanks Joker. That was kind of the conclusion that I had come to. It tracks great and returns to zero no problem. Its a Razor gen II. I do fine with tracking and adjustments out to 1200 meters. I don't shoot it(6mm CM) too often past that. Everything works as it's supposed to as long as I ignore the chassis level. I just wasn't sure if this was a common issue.