Does Adrian Peterson make sense with the Kansas City Chiefs?
By Matt Conner
Adrian Peterson will hit free agency, but do the Kansas City Chiefs make any sense as his new home?
The Minnesota Vikings have officially decided to part ways with Adrian Peterson and, at the very least, allow the veteran running back to explore the open market. They’ve declined to exercise the option in his contract for ’17.
The longtime Vikings running back is destined to be a first-ballot Hall of Fame player one day, but the question remains whether or not he will play for another team before then. He’s certainly still able to carry the load on the ground for some team, and perhaps the Vikings and Peterson will reach a new deal to keep him with the franchise on new terms, but it’s more than likely that AP will be playing for someone else instead.
Most projections will likely have Peterson still playing close to his franchise home by remaining the NFC North. The Green Bay Packers make sense as a destination and will be familiar territory for Peterson. But given that the veteran will likely want a chance to make an impact and also earn a Super Bowl ring, he also might consider Kansas City.
The Chiefs are a loaded team with impact players all over the roster who just happen to have a significant need at running back. Jamaal Charles is coming off of another significant injury and can’t seem to stay healthy. Spencer Ware proved last year that he’s more of a complementary back, and Charcandrick West or even C.J. Spiller should not be counted on heading into the regular season. If they contribute something positive, that’s a bonus.
Peterson’s fit on the Chiefs could come into question, but he’s an underrated pass catcher who has averaged 40 catches per season when he’s healthy, and is a more well-rounded back than the average fan might believe.
It’s certainly a longshot, but Peterson is also a rare talent who deserves at least some level of consideration now that he’s available on the open market.