Archived

This topic is now archived and is closed to further replies.

charlottenian

Will Beason be a Panther next year?

99 posts in this topic

depends completely on the response we get when he is dangled above the trade block. as he hovers there, and yes he is already hovering, interest will generate. If that interest is watered down with "injury-prone" red flags and noone will pay what he is worth and tries to steal him belicheat style, then we will keep him. that is the only way we will keep him. and it is quite likely.

Share this post


Link to post
Share on other sites

I think that rumors of Beason's demise may be premature. I told everyone he would struggle this year so I don't know why folks were surprised. On the other hand, by next year he could start for us and do a good job. While I agree he would be an expensive linebacker next year, I think I would try and restructure his contract next year and keep him and make decisions to trade or cut him until 2014 when we know what he can or can't do. He is still a leader on this team and one which has been sorely missed.

Share this post


Link to post
Share on other sites

not sure if you realize but beason has had 2 surgeries this year.knee and shoulder

Share this post


Link to post
Share on other sites

Actually the cap hit as a June 1st designation will be 6 million for 2013 and 2014 which is the 3 years of 4 million apiece split between 2 years.

That is how I understood the implications of June 1st cuts as well until about 2 months ago. One of the posters here (don't remember who exactly) claimed that under the current CBA, June 1st cuts are charged with the 1st year allocation equal to what was designated for that contract year (in this case, $4 million) with the balance hitting the next year. After doing some research, I found that is indeed correct. It is still spread over two years, but the hit is not equal.

Share this post


Link to post
Share on other sites

I think that rumors of Beason's demise may be premature. I told everyone he would struggle this year so I don't know why folks were surprised. On the other hand, by next year he could start for us and do a good job. While I agree he would be an expensive linebacker next year, I think I would try and restructure his contract next year and keep him and make decisions to trade or cut him until 2014 when we know what he can or can't do. He is still a leader on this team and one which has been sorely missed.

Beason will struggle next year for some of the same reasons he was going to be struggling this year....

I think Beason was a great leader but in many aspects I think he could be someone to get in Luke's way going forward. This is going to be Luke's D going forward IMO. Too many chefs in the kitchen sometimes doesn't work.

Share this post


Link to post
Share on other sites

Look at this and answer the question yourself:

7/29/2011: Signed a six-year, $51.338 million contract. The deal contains $25 million guaranteed, including a $20 million signing bonus.

2012: $1.25 million

2013: $5.25 million

2014: $6.5 million

2015: $7.5 million

2016: $8.75 million

2017: Free Agent

Let's just put it this way- release Beason and it becomes a cap hit unlike much of the league has never seen before. The cap hit would make Sean Gilbert's look minimal.

What do those figures represent? They don't add up to 25, 20, or 51. All that matters is how much of his signing bonus is left to pay.

Share this post


Link to post
Share on other sites

What do those figures represent? They don't add up to 25, 20, or 51. All that matters is how much of his signing bonus is left to pay.

The cap hit is about $13M if they release him at the end of this year- see panther55's post on the previous page...

Share this post


Link to post
Share on other sites

not sure if you realize but beason has had 2 surgeries this year.knee and shoulder

But the issue with Beason is still that the Achillles surgery limited him and kept him from being in football shape which impacted getting hurt again.

The labrum in the shoulder was torn but depending on the size and location may or may not have been season ending. As for the knee surgery, that was a simple scope to check out the strained knee and wasn't serious. If we had needed him back he might have been kept from IR if he had been healthy otherwise. But given he was struggling, we had Kuechly, and signed him to a long contract, there was no reason to not put him on IR.

Share this post


Link to post
Share on other sites

The cap hit is about $13M if they release him at the end of this year- see panther55's post on the previous page...

But again keep in mind we can take the hit over 2 years with the majority hitting in 2014. A lot depends on what they want to do with the rest of the roster.

Share this post


Link to post
Share on other sites

That is how I understood the implications of June 1st cuts as well until about 2 months ago. One of the posters here (don't remember who exactly) claimed that under the current CBA, June 1st cuts are charged with the 1st year allocation equal to what was designated for that contract year (in this case, $4 million) with the balance hitting the next year. After doing some research, I found that is indeed correct. It is still spread over two years, but the hit is not equal.

I would be interested in seeing that link. I was unaware of that.

This link doesn't mention it at all.

http://www.askthecommish.com/SalaryCap/faq.aspx

Share this post


Link to post
Share on other sites