Earlier this week, Chiefs coach Romeo Crennel announced that Matt Cassel would be his starting quarterback against the Bengals on Sunday. This move was predicated on the fact that Brady Quinn was still recovering from a concussion that he suffered.
Crennel did add that Quinn was "doing a lot better," and he wasn't kidding, because Quinn has already been cleared by the Chiefs for Sunday's game.
But here's the rub: Quinn will still back up Cassel against Cincinnati.
This is odd because, well, Quinn's supposed to be Kansas City's starter. Cassel suffered a concussion in Week 5, and Quinn took over for him. Even when Cassel returned from the injury, Quinn remained the starter, a decision that surprised everyone including Quinn himself.
Quinn eventually suffered his own in-game concussion, played while concussed for a bit, didn't get cheered by fans for getting injured and was eventually replaced by Cassel.
Now Quinn's healthy enough to play (he's the backup, after all), but Cassel's going to continue to start.
None of this is logical, primarily because it flies in the face of the "can't lose your job to injury" notion. Not that Crennel should be beholden to such an idea, but he now has given away the quarterback job to both the starter and the backup because of injury.
And it's not like either one is working out. The Chiefs are 1-8. Since Cassel's initial injury, they've scored six, 10, 16, 13 and 13 points in five games. Neither Quinn nor Cassel is going to become the magic quarterback solution in KC, but it would be nice if Crennel showed some consistency at something other than being inconsistent.
For more NFL news, rumors and analysis, follow @EyeOnNFL on Twitter, subscribe to our RSS Feed watch Pro Football 360 daily at 3 p.m. ET and NFL newsletter. You can follow Will Brinson on Twitter here: @willbrinson.