Quick Links

Will Josh Norman be with the Redskins in 2019?

Will Josh Norman be with the Redskins in 2019?

In 2016, the Redskins made Josh Norman the highest-paid cornerback in the NFL when they signed him to a five-year, $75 million contract. Now that deal is beginning to look like an albatross that the Redskins may want to terminate as soon as next year. 

When the contract was signed it looked like the Redskins were getting a good deal. Norman was coming off of an All-Pro season with the Carolina Panthers, who surprised everyone when they decided to rescind the franchise tag they had put on him. He was a playmaker who had intercepted four passes, returned two of them for touchdowns, and forced three fumbles. 

However, Norman would turn 29 late in his first season playing under that mega contract. He had a great contract season but prior to that, he had spent three seasons struggling at times and getting benched for stretches of games as well. These facts were glossed over by the team. 

In his 34 games in Washington, Norman has played well most of the time. He has continued to force fumbles, collecting two in each of his two full seasons in Washington. But his last interception came on December 24 of the 2016 season. He got two picks of Matt Barkley that day in Chicago. His other interception for the Redskins came earlier that year. It was off of Cody Kessler of the Browns. Norman has had none in his past 19 games. 

While the Redskins wanted to see more game-changing plays for their investment of $15 million per season, it was acceptable as long as he continued to shut down opposing receivers. According to Pro Football Focus, there were just three games last year when he allowed more than 41 yards passing against him. In six games he allowed 25 or fewer yards. 

But it has been a different story this year, particularly in the last two games. Against the Packers and Saints, he has allowed a total of 164 yards and three touchdowns. 

He hit rock bottom against the Saints. On the first defensive series, he committed a holding call that negated a third-down stop. The New Orleans drive continued and ended in the end zone. As Drew Brees continued to torch the Redskins’ secondary Norman was caught freelancing and out of position all too often. It got to the point where Jay Gruden decided to bench him for the first series of the second half. Norman went back into the game after Greg Stroman, his replacement, got burned for a touchdown. 

It’s early and things could turn around but with a quarter of the season in the books, it’s fair to consider what to do with Norman after the season is over. His cap charge goes down from almost $17 million this year to $14.5 million in 2019. That’s better but it’s still high. Based on the contracts in force right now Norman would be fifth on the list of the highest 2019 salary cap charges for cornerbacks. If he’s not playing up to that deal it will be a problem for a team that is tight on cap space next year

They could elect to release him. They would incur a dead cap charge of $6 million but save a net of $8.5 million in cap space. If they want to spread out the dead cap charge they could designate him as a post-June 1 cut and create $11.5 million in additional 2019 cap space while pushing $3 million of dead cap to 2020. 

An alternative might be to talk to Norman and attempt to renegotiate his contract, perhaps something that would reduce his $11 million salary in exchange for some incentives that would allow him to earn some of it back. It would then be up to Norman to decide if he wants to take the pay cut or if he would rather take his chances hitting the free agent market at the age of 31. 



Quick Links

Report: Officials say RFK site not an option for Redskins unless team changes name

Report: Officials say RFK site not an option for Redskins unless team changes name

As the Redskins search for a new football home in the future, the RFK Stadium site is one that is at the top of the list. However, unless the team is willing to change its name, the area becoming their new field is a non-starter, The Washington Post reported on Wednesday

Speaking with several government officials, a similar message was shared throughout. The federally owned land will not be given to the franchise if the name remains what it is today.

“I call on Dan Snyder once again to face that reality, since he does still desperately want to be in the nation’s capital,” D.C.'s nonvoting delegate to the House of Representative Eleanor Holmes Norton (D) said. “He has got a problem he can’t get around -- and he particularly can’t get around it today, after the George Floyd killing.”

“There is no viable path, locally or federally, for the Washington football team to return to Washington, D.C., without first changing the team name," D.C. Deputy Mayor John Falcicchio said.

Washington's name has been a topic of debate for years but has recently received major pushback over the past month as the nation yearns for racial justice following the murder of George Floyd.

It was also reported on Wednesday that investment firms and shareholders worth a collective $620 billion have asked Nike, FedEx and PepsiCo to terminate their business relationships with the Washington Redskins unless the team agrees to change its name.

The Redskins have expressed interest in playing on the grounds of RFK after a bill was introduced in 2019 calling for the federal government to sell the area to the city. However, the bill won't pass through Congress unless the land is used for the team under a different name. U.S. Rep. Raúl M. Grijalva (D-Ariz.), chair of the House Natural Resources Committee, referred to the current name as a "racist nickname."


Redskins owner Dan Snyder has stated in the past that he is not open to a name change, as he considers it to be an act of honor toward Native Americans. 

Washington currently plays its games at FedEx Fied in Landover, Md. Both sides would like to see the team return to the District, but for as long as they are called the Redskins, it won't happen.

“The time has ended,” Grijalva said. “There is no way to justify it. You either step into this century or you don’t. It’s up to the owner of the team to do that.”

“The city obviously would like the team back,” Norton said. “But it’s important that [Falcicchio] used the word ‘federally’ -- meaning that they now recognize that there is no hope unless this name is changed.”

Stay connected with the MyTeams app. Click here to download for comprehensive coverage of your teams.


Quick Links

Jeff Bostic shares hilarious story of Joe Bugel blaming him for a missed block that wasn't his doing

Jeff Bostic shares hilarious story of Joe Bugel blaming him for a missed block that wasn't his doing

Former Redskins coach Joe Bugel, who died on Sunday at the age of 80, impacted numerous players throughout his time in the NFL. Specifically, from 1981-89 he helped members of  "The Hogs" offensive line in Washington become one of the greatest units ever assembled.

However, for as much as Bugel loved his players and his players loved him back, the two sides were prone to some arguments. Bugel's fiery passion for the game led to some outbursts that no one was immune to. From Joe Gibbs to Russ Grimm, plenty got an earful.


That includes former Redskins offensive lineman Jeff Bostic, who was alongside Bugel during his nine seasons in Washington. On the latest Redskins Inside Look, Bostic joined former Redskins teammate and legendary running back John Riggins to share one of his most memorable stories of Bugel.

It all started when Mark May, another member of the offensive line, didn't want to hear Bugel yell at him.

“You know the biggest whiner in Redskins history is Mark May. He had missed the block and Buges was on the staff," Bostic said. "Well, May is over there telling him I missed the block."

So, with that information to go off of, Bugel prepared to shame Bostic for the failed play. As Bostic jogged to the sideline following a field goal attempt, he couldn't understand why his name was being called.

“I’m coming off the field and I hear Buges yelling ‘He kicked your a--.’ And I’m like ‘who is he talking to?’" Bostic said. "And then he said it again. I said ‘who are you talking to?' He said, 'I’m talking to you.'”


That led to Bostic showing his frustrations and sending his helmet hurdling through the air.

“I unbuttoned my helmet and threw it at him from about 15 yards away," Bostic said. "And I just left my helmet and went over and sat on the bench.”

Following the heated back-and-forth, Bugel quickly displayed the other side of his personality -- the one that cared for his players and just wanted to see them succeed. Heading over to Bostic, he wanted him to know there were no hard feelings, it was just the emotion of football getting the best of him.

"He said, ‘Hey horse you know I love you.'”

Because Bostic -- like so many other Redskins -- had a deep love and respect for Bugel, it was easy for him to take the apology and move on. However, he did want his coach to know that all the yelling was actually done for no reason because he was not the one to blame.

"I said 'You got a strange way of showing love. What you’re gonna do is when you watch the film tomorrow you’re gonna owe me an apology,'" Bostic said.

Stay connected to the Redskins with the MyTeams app. Click here to download for comprehensive coverage of your teams.