Redskins

Quick Links

Jammal Brown's 2012 cap hit is 4.55 million

638520.jpg

Jammal Brown's 2012 cap hit is 4.55 million

Before getting started here, it needs to be made clear that the Redskins are long way from releasing Jammal Brown. Mike Shanahan described his hip as being a little sore and perhaps the injury is indeed minor even though it is to an area of his body that is of great concern.However, the possibility that the Redskins will move on from Brown by the time the regular season starts has to be considered. Late last year Shanahan told the media that Brown has to be able to stay healthy if he is going to be on the team. If an MRI reveals that there will be issues with his hip that are likely to last all season long, Browns roster spot could be in jeopardy.Unfortunately, the Redskins did not write any injury protection for themselves into the contract that Brown signed after the lockout ended last year. The deal was for 5 years and 27.5 million with 8.2 million guaranteed. One mechanism that teams, including the Redskins, have used for injury protection is per-game roster bonuses. A portion of the players salary will be tied to being on either the 53-man roster (i.e. not on injured reserve) or being on the 46-man game day roster. Since they dont have any of those mechanisms in Browns contract they will be on the hook for his entire 3.25 million salary if he is on the roster for the first game of the season (salaries become guaranteed for the season at that point). They also are on the hook if they put him on injured reserve before the season.If they decide to move on without him, the smart move would be to get him to where he could pass a physical and the release him before the season starts. That would knock his salary off of the books for this year, leaving his 1.3 million prorated singing bonus as dead cap.The Redskins would pay for this move in 2013. They would have the remaining 3.9 million left on his signing bonus charge left on the books that they would have to eat in dead cap. However, they could roll over the 3.25 million savings from this year into next, so it would be about 700,000 short of a wash.Again, the Redskins have no plans to do anything with Jammal Brown right now and he remains on the roster. But if they do decide to let him go the net cap impact would not be too difficult to manage even with them having to deal with the remaining 18 million of the NFLs salary cap penalty.

Quick Links

Need to Know: Final thoughts on Redskins vs. Giants

eli_manning_vs_redskins_usat.png
USA Today Sports Images

Need to Know: Final thoughts on Redskins vs. Giants

Here is what you need to know on this Thursday, November 23, seven days before the Washington Redskins play the Dallas Cowboys at AT&T Stadium.

Timeline

Today’s schedule: Redskins Kickoff 7:30 NBC Sports Washington; Redskins vs. Giants, NBC, 8:30  

Days until:

—Redskins @ Cowboys Thursday night (11/30) 7
—Redskins @ Chargers (12/10) 17
—Cardinals @ Redskins (12/17) 24

Final thoughts on Redskins vs Giants

Look out for Eli—There are many reasons why the Giants are 2-8 but Eli Manning is not one of them. He isn’t nearly the turnover machine he has been for much of his career. His interception percentage this year is 1.6; he hasn’t been under 2.3 percent interceptions this decade. Manning only has 14 touchdown passes but considering that Odell Beckham, who went out in the fourth game of the season, still leads Giants wide receivers in touchdown receptions, that’s not bad.

Running game stuck—What makes Manning’s performance even more impressive is the fact that he doesn’t get much support from a running game. The Giants are 26th in the league with 920 yards. They have gained some traction lately after installing Orleans Darkwa as the starting running back; he is averaging 4.8 yards per carry for the season and 71 yards per game over the last three games. The Redskins certainly don’t want to let him get going tonight.

Reverting to reality—The Giants ranked 32nd in total defense in 2015. They dropped millions on free agents such as Janoris Jenkins, David Harrison, and Olivier Vernon and jumped to 10th. Now, this year they are 31st and equally bad against the pass (29th) and the run (30th). Health hasn’t been a huge issue, although Vernon has missed a few games and Jenkins was suspended. Redskins fans know full well that spending sprees don’t necessarily make for permanent improvements and Giants fans are learning it this year.

Keys to winning

  • Run the ballThe Redskins are 4-2 this year when rushing for 90 yards or more.
  • Continue to protect the ball—The Redskins have turned the ball over just twice in their last three games.
  • Don’t give them hope—The Chiefs let the Giants hang around last week and New York stole a win. The Redskins need to get on top early and mash down on the gas pedal.

Prediction—It’s hard to see a scenario where the Redskins lose this one. Even in their injury-depleted state they are battling every game and the same can’t be said for their opponents today. The weather forecast is for cold temperatures but not much wind, ideal conditions for Cousins to throw for 300 yards. For once, the Redskins get up early and keep going.

Redskins 31, Giants 13

Stay up to date on the Redskins. Rich Tandler covers the team 365 days a year. Like his Facebook page Facebook.com/TandlerNBCS and follow him on Twitter @TandlerNBCS.

Tandler on Twitter

In case you missed it

Quick Links

Everybody thinks the intentional grounding call against Kirk Cousins was wrong, except Troy Aikman

cousins_aikman.jpg

Everybody thinks the intentional grounding call against Kirk Cousins was wrong, except Troy Aikman

The referees made a fairly obvious mistake last week in the Redskins loss to the Saints when they flagged Washington quarterback Kirk Cousins for intentional grounding late in the game. 

Let's be honest: the call was terrible.

Cousins never felt a pass rush on the play, and was very obviously throwing the ball away. Jay Gruden talked about the play on Monday, and could not figure out how a flag came out in that situation. 

We had two receivers in the area. Quarterbacks throws it away all the time that are uncatchable balls whether they are in the pocket or not. As long as there is a receiver in the area, you can throw it whether they are looking or not. Guys run bad routes – one guy runs a hitch and he’s supposed to run a go and the quarterback throws the go ball, it’s not grounding. So I don’t know why the confusion.

The NFL even reached out and apologized to Redskins team president Bruce Allen for the blown call, a hollow gesture that did not generate much excitement from Cousins (via 106.7 the Fan). 

Whatever they do to say, ‘we’re sorry, wrong call,’ it’s tough because there’s nobody bringing that up in February or March when we're making decisions about which direction to go with the organization. We appreciate the clarification but you know it really doesn’t do much.

If you're keeping score, the NFL, the Redskins head coach and the Redskins quarterback all know the call was wrong. 

You know who doesn't think the call was wrong? Fox analyst, and former Cowboys Hall of Fame QB, Troy Aikman.

Grounding? Free rusher? Decide for yourself below.