Skip to main content

Around the League

Presented By

Washington Redskins implode amid Shanahan rumors

Mike Shanahan might be cleaning out his office for good this time.

With rumors of Shanahan's exit swirling, the Washington Redskins imploded in a 45-10 loss to the Kansas City Chiefs at FedEx Field on Sunday.

The Redskins coach's squad was a disaster in every facet of the game. Speculation has Shanahan interested in the Houston job. If Texans owner Bob McNair sees the tape of this game, Shanahan won't be on the list of candidates once he's shown the door in Washington.

Here's what else we learned in Sunday's game:

  1. CBS broadcaster Solomon Wilcots called the Redskins' special teams the poorest display he's ever seen. They went on to allow a kickoff return for a touchdownafter that statement. Special teams coordinator Keith Burns' unit has been an unmitigated disaster all season. Tight end Niles Paul suggested earlier in the season that players aren't buying in to Burns' coaching.
  1. Shanahan said he only pulled quarterback Robert Griffin III for Kirk Cousins in the fourth quarter because the game was out of reach. Interestingly, Shanahan would not commit to Griffin as the Week 15 starter. By Monday morning, it might not be Shanahan's call to make.
  1. Chiefs running back Jamaal Charles added to his All-Pro resume with his highest rushing output of the season. Charles' 13 touchdowns leads the league.
  1. It's hard to blame Redskins fans for checking out early. By halftime, there were tumbleweeds rolling through FedEx Field.
  1. The St. Louis Rams are watching the Redskins' dumpster fire with amusement. As part of the RGIII trade, the Rams have Washington's first-round draft pick. If things break their way over the final three weeks, it could be the No. 1 overall selection.

The "Around The League Podcast" is now available on iTunes! Click here to listen and subscribe.

This article has been reproduced in a new format and may be missing content or contain faulty links. Please use the Contact Us link in our site footer to report an issue.

Related Content