KCKingdom
Fansided

Kansas City Chiefs: Pros and cons of cutting Jeremy Maclin

Dec 27, 2015; Kansas City, MO, USA; Kansas City Chiefs wide receiver Jeremy Maclin (19) celebrates after catching a touchdown pass against the Cleveland Browns in the first half at Arrowhead Stadium. Mandatory Credit: John Rieger-USA TODAY Sports
Dec 27, 2015; Kansas City, MO, USA; Kansas City Chiefs wide receiver Jeremy Maclin (19) celebrates after catching a touchdown pass against the Cleveland Browns in the first half at Arrowhead Stadium. Mandatory Credit: John Rieger-USA TODAY Sports /
facebooktwitterreddit
Prev
4 of 6
Next
Kansas City Chiefs wide receiver Jeremy Maclin (19) – Mandatory Credit: John Rieger-USA TODAY Sports
Kansas City Chiefs wide receiver Jeremy Maclin (19) – Mandatory Credit: John Rieger-USA TODAY Sports /

PRO: MISSING IN MAC-TION

Okay, so we might not want to say it out loud, but Jeremy Maclin wasn’t good last season. Sure, his first season in Kansas City was spectacular, but his follow-up to that was not good.

The former Mizzou Tiger only appeared in 12 games and caught 44 passes for 536 and two touchdowns. The Chiefs were constantly trying to get Maclin involved in the passing game, but he just didn’t look as good as he did in the past.

Maclin was banged up during 2016 and also missed time due to personal reasons. He has struggled with injuries throughout his career and the fact of the matter is that if you’re making $10 million a year, you have to stay healthy (if only Justin Houston, who makes way more than that, would get that memo).

Perhaps the Chiefs know something about Maclin’s health and that’s another reason why he was let go, but if we’re judging his release off of the 2016 season, fans shouldn’t be too surprised.