Matt Cassel Injury: Update on Kansas City Chiefs Star's Injury

The Chiefs walked into Arrowhead favored and on the brink of going a game above .500; instead, KC walked out 4-5, and their starting quarterback in a cast.

Cassel was beat into the ground, getting sacked four times and hit an absurd 12 times. He sustained an unknown injury in the game, and a timetable for his return to action has not yet been given.

Fantasy Impact:

You shouldn't be starting Cassel anyways. The miserable protection, and the fact that he's unlikely to be 100 percent, makes him even less likable from a fantasy perspective.

If you're starting him because you are still enamored by his streak of four 250-yard outings in five games, this may be just the wake-up call you need to pursue a legitimate option at quarterback.

Who's the Backup?:

Tyler Palko came into the game and went 5-of-6 against Denver's D. Make no mistake about it though: the Chiefs are in trouble if the undrafted QB out of Pittsburgh ends up getting the nod next week. He may be 28, but he's grossly inexperienced.

Devastation Scale: 5/10

Like the walking boot that has become so trendy around the league, the cast we saw Cassel in doesn't mean he's got a shattered arm and won't be in action. We shouldn't jump to conclusions and assume that his injury is long term.

What They're Saying

Todd Haley says that he yanked Cassel because he was "beat up" according to the Denver Post's Lindsay Jones. It's unclear if an injury prevented him from carrying on, or if Haley didn't want to run the risk of getting his starter hurt even worse.

''I was a little banged up, so that's what kept me out,'' said Cassel after the game, refusing to elaborate on the situation. ''I wanted to go but I was told not to.''

CBS Fantasy Football indicates Cassel was seen in a cast on his right arm, but are not able to say exactly what the injury is.