Three Questions: Kansas City Chiefs Running Backs

Jan 4, 2014; Indianapolis, IN, USA; Kansas City Chiefs running back Knile Davis (34) runs the ball during the first quarter of the 2013 AFC wild card playoff football game against the Indianapolis Colts at Lucas Oil Stadium. Mandatory Credit: Andrew Weber-USA TODAY Sports

Can we rely on Knile Davis to be on the field?

Knile Davis, maybe more than any other Chiefs draft pick in 2013, proved his value to the team with his excellent performance in the second half of the season and as a backup in the playoff game against Indianapolis. While his opportunities were limited relative to the season as a whole, Davis took advantage of his opportunities. A touchdown return against Denver, a stellar first half against San Diego in week 17 with a backup offensive line, and a wonderful performance in the playoffs flashed what he can bring as a counter to Charles.

The issue is whether or not we can count on him to be there when we need him. A major knock on Davis coming out of the draft – one I would argue was far more concerning than his fumble problems – was his inability to stay healthy. He had injury issues throughout high school, injury issues throughout college, and suffered a serious injury in his first season in the NFL. If Davis cannot stay healthy then what kind of worth does he really bring to the team?

All of the raw skills are there for Davis to be a great back in the NFL. He has the power to run through you, the elusiveness to run around you, and the speed to run by you. His kickoff return against Denver in Kansas City was one of his greatest displays of all of these talents in one play. None of those talents mean anything if he cannot stay on the field.

To some degree, this makes 2014 a pivotal year for Davis. He needs to prove he can at the very least stay on the field for a 16-game season and produce in a backup role. Should the injury issues continue to surface then Kansas City may have a serious problem at running back moving forward.