Matt Cassel is the single biggest thing holding this team back. If he plays better, regardless of the 2-3 drops, we beat the Colts. He is 4 games into his 2nd season with KC and he still hasn't shown that he is worth the money the Chiefs have given him.
It's not just me that can see it either, read some of what the media has to say after the jump.
Don Banks from SI.com:
"That's why it's a shame quarterback Matt Cassel is still holding his team back at times. I did see at least three drops by Kansas City pass catchers (Dwayne Bowe, we're looking in your direction), but Cassel just can't threaten a defense consistently yet. He finished with 156 yards passing and no touchdowns."
Read more: http://sportsillustrated.cnn.com/2010/writers/don_banks/10/10/snap.judgments/1.html#ixzz123mer8fb
Jason Cole from Yahoo Sports:
"Sadly for Kansas City, it didn’t have enough offense to pull off the upset. Between a pair of big drops by wide receiver Dwayne Bowe (one that would have been a touchdown) and the general ineffectiveness of quarterback Matt Cassel (he finished 16-of-29 for 156 yards), the Chiefs had only one drive of longer than 55 yards and reached the Indianapolis 10-yard line only once."
I am sure there will be more people out there that will continue to realize that Matt Cassel is not the answer at QB for Kansas City, and no matter what our Defense or Special Teams does, the team will go only as far as Cassel will take them. Unfortunately, that won't be far if he continues his unreliable and mediocre play.
Poll
Is it time to stop thinking of Cassel as a starting NFL QB?
Yes (149 votes)
No (50 votes)
Not Sure (29 votes)
228 total votes



There are 67 Comments. Load Now.
Shortcuts to mastering the comment thread. Use wisely.
C - Next Comment
X - Mark as Read
R - Reply
Z - Mark Read & Next
Shift + C - Previous
Shift + A - Mark All Read
Comment Settings
Live comment alert: Hide it!
Comments for this post are closed.