KC Chiefs: Should Chiefs Re Sign Joe McKnight


The KC Chiefs saw a lot of season ending injuries occur to their players in 2014. Despite those injuries, the Chiefs were able to go 9-7 and barely missed out on the playoffs.

One of those season ending injuries was to running back Joe McKnight, who up until last year, hadn’t experienced a ton of success in the NFL. After being drafted in the fourth round by the New York Jets in 2010, McKnight failed to score a touchdown during his three seasons there and was released before the 2013 season.

McKnight was out of football during the 2013 season, but signed with the Kansas City Chiefs for the 2014 season. No one really expected McKnight to fill a huge role due to the fact that the Chiefs had both Jamaal Charles and Knile Davis at the running back spot, but when Charles went out with an injury, McKnight stepped up big for the Chiefs.

Live Feed

Top 5 pending free agents the 49ers should go after in 2024
Top 5 pending free agents the 49ers should go after in 2024 /

Niner Noise

  • 3 Offseason Moves the Patriots Still Need to Make After Signing Ezekiel ElliottChowder and Champions
  • When does 2024 NFL Free Agency start?Still Curtain
  • Do Dalvin Cook, Ezekiel Elliott contracts lay groundwork for NFL RBs?FanSided
  • NFL Rumors: 3 running backs Dolphins need to sign after missing on Dalvin CookFanSided
  • 3 Cowboys backup plans after Ezekiel Elliott signs with PatriotsFanSided
  • It was week three against the Miami Dolphins and the KC Chiefs were 0-2 on the season and in desperate need of a win to save their season. Charles had been ruled out against the Dolphins due to an injury he sustained against the Broncos the week prior. Davis took his spot and did a terrific job, rushing for 132 yards and a touchdown, and doing exactly what was needed of him in a must win game.

    McKnight did his job too. As the backup running back, McKnight had himself a game against the Dolphins. He ended his day in Miami with six receptions for 64 yards and two receiving touchdowns from Alex Smith. Too bad McKnight wasn’t listed as a wide receiver that day, you know because of that whole no touchdowns to a wide receiver stat that we’re all tired of hearing.

    Just a few days after that game, McKnight tore his Achilles in practice and was ruled out for the rest of the season.

    Going into 2015, things haven’t changed as far as the Chiefs’ running back situation goes. Charles is still the main man and Davis is his right hand guy. As it turns out, McKnight is currently an unrestricted free agent and may not even be in Kansas City next season.

    More from Chiefs Free Agency

    Adam Teicher of ESPN wrote a short piece on McKnight being a free agent back in March and felt that he was only worth keeping due to possible injuries that could occur to Charles and Davis. He didn’t seem to think keeping McKnight was a vital move for the Chiefs.

    Even after his explosive performance against Miami, it doesn’t seem likely that the Chiefs will re-sign McKnight mainly due to their other options at running back behind Charles and Davis. Right now the other running backs on the roster are Cyrus Gray, Keshawn Hill, Spencer Ware, and Charcandrick West.

    The Chiefs have had Gray since drafting him in 2012, Hill is a rookie, Ware is a second year guy, and West seems to have potential. Any of these guys could fill the third running back role headed into 2015, but the Chiefs saw what McKnight could do when a fire was lit under him, and man the results were pretty impressive.

    So I ask you Chiefs Kingdom… Should the Chiefs re-sign Joe McKnight for the 2015 season?

    Next: 5 Worst Draft Picks In Chiefs History

    More from KC Kingdom