:format(webp)/cdn.vox-cdn.com/photo_images/1449193/GYI0062467690.jpg)
The Kansas City Chiefs signed WR Chris Chambers halfway through the 2009 NFL season. He made his debut in Week 9 against the Jacksonville Jaguars. It was a debut that got Chiefs fans excited: three catches, 70 yards, and two touchdowns. Over the next eight weeks, the Chiefs made Chambers one of their most frequent targets.
Chambers was rewarded for his hard work with a contract extension last March.
Fast forward to the 2010 season. After a relatively slow start, Chris Chambers was a surprise, healthy scratch from the lineup in Week 6. He sat that game against the Houston Texans and the next week against the Jacksonville Jaguars. Over the next five weeks, Chambers was on the 45-man game day roster. But he wasn't a big target for the Chiefs' offense - Chambers was only targeted 13 times in those fives games, with eight of those coming against the Broncos when they shut Dwayne Bowe down in Week 11.
In the last three weeks of the season, Chambers has started but wasn't targeted against the Seahawks; was inactive against the Broncos in Week 13; and made one catch for ten yards in garbage time last week against the San Diego Chargers.
Sure sounds like a guy who's on the way out, doesn't it? If given the chance over these next three games, Chambers has the ability to make the Chiefs think twice about letting him go. The guy can play well. But he seems to have lost his motivation this year.
My gut tells me Chris Chambers is not a Kansas City Chief in 2011. Can he change my mind, and hopefully the Chiefs' mind over the next three games? I really doubt it.