Lack of quality WR's hurting Cassel & Chiefs

[KChiefs1]

http://arrowheadaddict.com/2010/11/0...ng-the-chiefs/

Lack Of Quality Receivers Hurting The Chiefs
Updated 11/09/2010 10:58 AM
by Patrick Allen


It is time to throw Kansas City Chiefs QB Matt Cassel a bone.

If you've been reading this site for more than a couple of weeks, you know that I have been highly critical of Cassel. I have particularly been hard on him about his completion percentage which has spent more time on the wrong side of 60 percent than I would like. However, now that we are halfway through the season I think it is time to give the Chiefs signal caller another look.

After giving it much thought I think that Matt Cassel is in a very tough position with this year's team. He is a Quarterback with no receivers.


Scott Pioli has had a lot of his bets pay off this season but one of his failures has been the resigning of WR Chris Chambers. I think even Pioli was worried about Chambers which is why he waited so long to resign him and in the interim, tried to trade for Anquan Boldin. It came down to the Chiefs and the Ravens battling for Boldin's services and in the end, the Ravens were willing to give up more draft picks than the Chiefs. For the record, I think Pioli did the right thing, especially considering the talent level of his 2010 draft class. Boldin woul dhave helped out a lot this year but these rookies will be more valuable in the long run.

After failing to make the trade for Boldin, Pioli resigned Chris Chambers. He also drafted WR Dexter McCluster who he figured could be a solid outlet for Cassel in the slot.

He was kind of right.

McCluster is a dynamic weapon but he wasn't ready to step in and be an impact receiver from day one. Most of the damage McCluster has done this season has come when he has lined up in the backfield. That doesn't mean that McCluster isn't going to turn in to a good receiver, it simply means he is a rookie who wasn't that experienced at receiver to begin with, learning to play the position at the NFL level. It was always going to take time.

The other side of the Chambers/McCluster bet, however, is what has hurt the Chiefs and Cassel the most. Chambers is a bum. I don't know if he just got old or if he really does quit once he gets paid. I'm not sure what goes on in the head of a guy who would get a restraining order against a woman and then marry her a few months later. All I do know is that they guy hasn't shown up this year and it doesn't appear he is going to show up any time soon. He is dead weight but unfortunately, he is all we've got.

Before being overly critical of Cassel, you have to look at what the dude is working with. He's got Bowe and then…er…

McCluster (injured)

Terry Copper

Chris Chambers

Verran Tucker

Seriously? Look, the way Chambers is playing he would probably get cut by most NFL teams at this point. Tuker and Copper wouldn't even BE on other NFL teams. Maybe Copper would sneak on a squad as a special teamer but you can bet your behind he wouldn't be lining up at receiver.

Cassel is doing the best he can with what he has to work with. The last two games he has had three targets:

Dwayne Bowe

The team’s best receiver is actually having a pretty decent season. He has a few drops but for the most part, he has been very productive.

Tony Moeaki

Moeaki is the Chiefs second best wide receiver and he is a freaking tight end!

Jamaal Charles

The team’s third best wide receiver, Jamaal Charles, is also the leagues best second string running back.

When McCluster comes back, he’ll slide back in tot he #3 slot and Charles can go back to being a backup running back.

And before you all start going gaga over Verran Tucker, remember that his spectacular TD catch from Sunday is his ONLY catch in the three weeks that he has been active. This isn't an indictment on Tucker. The dude has potential but he isn't getting open and right now, that is what Cassel needs.

The reason the Chiefs threw so much against the Raiders is because Oakland wasin single coverage all day long with no safties. People have been talking about how Oakland's strategy was an indictment on Cassel. They've been saying the Raiders didn't believe Cassel could beat them. I disagree with this. I think the Raiders believed the Chiefs receivers couldn't beat them and they were right. Look Bowe has never been a burner but you are telling me not Chambers, Copper or Tucker could put a good enough move on their man to blow by them and get wide open over the top? If the Raiders tried that kind of crap on the Indianapolis Colts Peyton Manning would throw for 37 touchdowns. Every time Cassel completed a pass Sunday, his man was covered pretty well. There were very few passes that went to wide open receivers.

While watching Sunday's game, the guy across from me kept bemoaning that Cassel wasn't throwing the ball. He wasn't throwing it because he can't see wide open receivers. He wasn't throwing it because there were no open receivers. It is obvious that the Chiefs and Cassel have made it a priority to take care of the football. Cassel is under strict instructions not to force passes and to get rid of the ball if he senses trouble, even if that means throwing it away. He has been doing that and the results, for the most part, have been positive.

Cassel is doing a fine job of hitting Moeaki and Bowe when they are open. He is fairly efficient at hitting Charles when he comes out of the backfield. Before Dexter McCluster got injured, Cassel started finding him more down field as well. He just doesn't have the tools he needs in the receiving game. Philip Rivers might be able to succeed with receivers off the street but Cassel is no Philip Rivers. * I think the Chiefs passing game is going to continue to struggle until they get Dexter McCluster back. I think the presence of McCluster helps both Bowe and Moeaki. It will also keep Jamaal Charles in the backfield where he belongs. With the absence of McCluster, the Chiefs have been using Charles a little more in the passing game because they know they need another threat out there. *

The*Cassel lead Chiefs will likely never be a passing team but if they don’t get some more help at the WR position soon, KC’s air attack will stay grounded.

[milkman]

Originally Posted by Just Passin' By

Cassel does not make either look worse than they are. Frankly, I have no idea how you can even put forth that notion, especially since the O-line/Cassel combination has looked pretty darned good this season.

Cassel made the Pats line look worse than they were until Josh McDumbasss started to use a shotgun as his base offense in New England, and as bad as the line was last year, he made them look even worse.

Cassel has made progress in this area this year, a testament to the work of Charlie Weis.

[ForeverChiefs58]

Originally Posted by Just Passin' By

Sack% last year was 7.9. So far this season, it's down to 4.9, which is lower than

Brady
Roethelisberger
Flacco
Rivers
Schaub


and many more.

If you throw the ball 10 yards into the stands the other team can't intercept it.

When was the last time you saw him take a hit as he completes a pass? I'll give you a hint, they have him throw as soon as he starts shitting his pants.

[chiefzilla1501]

Originally Posted by Just Passin' By

Sack% last year was 7.9. So far this season, it's down to 4.9, which is lower than

Brady
Roethelisberger
Flacco
Rivers
Schaub


and many more.

It's a silly argument because those guys throw a lot more and they throw deep a lot more, which requires more time in the pocket.

I like that Cassel has improved his ability to get rid of the ball. But let's not pretend that the run-heavy, screen-heavy offense that doesn't throw deep a lot doesn't have a lot to do with this.

And yes, Big Ben takes a lot of sacks. That's just the way he plays the game. As does Rodgers. But they more than compensate.

[Just Passin' By]

Originally Posted by milkman

Cassel made the Pats line look worse than they were until Josh McDumbasss started to use a shotgun as his base offense in New England, and as bad as the line was last year, he made them look even worse.

Cassel has made progress in this area this year, a testament to the work of Charlie Weis.

Cassel made the Pats line look worse while he got used to playing football games again. The line also was worse, because Stephen Neal was out on the PUP and his replacement was terrible. It's not a coincidence that the sack improvement began with the return of Neal to the lineup.

[BigMeatballDave]

I hate to say this, because I never root for injuries, but I would be OK if Cassel were to get a mild concussion or something. Just to keep him out the next few games to see the difference between him a Croyle.

[Just Passin' By]

Originally Posted by ForeverChiefs58

If you throw the ball 10 yards into the stands the other team can't intercept it.

When was the last time you saw him take a hit as he completes a pass? I'll give you a hint, they have him throw as soon as he starts shitting his pants.

It happened last game. Perhaps, if you tried reasonably looking at the QB instead of just ignorantly following the herd, you might understand what's happening with that Chiefs offense. I'm not saying that Cassel's playing at a Brady/Manning/Brees level, but he's playing much better than people such as yourself are giving him credit for.

[milkman]

Originally Posted by Just Passin' By

Cassel made the Pats line look worse while he got used to playing football games again. The line also was worse, because Stephen Neal was out on the PUP and his replacement was terrible. It's not a coincidence that the sack improvement began with the return of Neal to the lineup.

Yeah, that one guy gave up 30+ sacks.

[donkhater]

Originally Posted by milkman

Cassel made the Pats line look worse than they were until Josh McDumbasss started to use a shotgun as his base offense in New England, and as bad as the line was last year, he made them look even worse.

Cassel has made progress in this area this year, a testament to the work of Charlie Weis.

Yep, muster all the effort you can to not cede any ground that Cassel has improved from last year. I'll cede he's still very mediocre, but only the close-minded on this board stubbornly refuse to give him at least some credit for this team's improvement.

Cassel was awful last year. He's less awful this year. Too many people got duped into thinking that his contract automatically made him a superstar. Yes, it was a horrid decision by Pioli, but the CP still uses that as a reason not to view Cassel objectively.

[milkman]

Originally Posted by donkhater

Yep, muster all the effort you can to not cede any ground that Cassel has improved from last year. I'll cede he's still very mediocre, but only the close-minded on this board stubbornly refuse to give him at least some credit for this team's improvement.

Cassel was awful last year. He's less awful this year. Too many people got duped into thinking that his contract automatically made him a superstar. Yes, it was a horrid decision by Pioli, but the CP still uses that as a reason not to view Cassel objectively.

Where have I said that Cassel hasn't improved?

Did I not say in the very post that you quoted that Cassel has made progress?

The fact that I give credit to Weis for making progress doesn't negate teh fact that he has made progress.

Are you too ****ing stupid to recognize that?

Don't answer that.
It's rhetorical.

[Just Passin' By]

Originally Posted by milkman

Yeah, that one guy gave up 30+ sacks.

That one guy was a turnstile at right guard, and was killing the line, both with the run and the pass. Neal started the final 9 games in 2008. Here's the breakdown



Sack totals in the first 8 weeks (7 games), as Neal was on PUP and then working his way back: 28

Number of times in the first 8 weeks (7 games) that Cassel was sacked more than 3 times in a game: 5


Sack totals in the final 9 games: 19

Number of times in the last 9 games that Cassel was sacked more than 3 times in a game: 1

[BossChief]

Originally Posted by donkhater

Yep, muster all the effort you can to not cede any ground that Cassel has improved from last year. I'll cede he's still very mediocre, but only the close-minded on this board stubbornly refuse to give him at least some credit for this team's improvement.

Cassel was awful last year. He's less awful this year. Too many people got duped into thinking that his contract automatically made him a superstar. Yes, it was a horrid decision by Pioli, but the CP still uses that as a reason not to view Cassel objectively.

and some of the apologists want for him to be better sooo much that you have lowered the expectation bar so low that the guy can throw for 60 yards and some of you would be totally OK with that and be chiming the bells of "improvement"

I even made a thread showing the improvements he has made from last year, but I ran out of ammo quickly.

If you think Cassel is acceptable, you will have a hard time dealing with it WHEN we get blown out in a playoff game BECAUSE OF HIM.

[BigMeatballDave]

Originally Posted by donkhater

Yep, muster all the effort you can to not cede any ground that Cassel has improved from last year. I'll cede he's still very mediocre, but only the close-minded on this board stubbornly refuse to give him at least some credit for this team's improvement.

Cassel was awful last year. He's less awful this year. Too many people got duped into thinking that his contract automatically made him a superstar. Yes, it was a horrid decision by Pioli, but the CP still uses that as a reason not to view Cassel objectively.

He's improved. The running game certainly helps. This team has won 5 games in spite of Matt. If Croyle had started every game,(probably not likely he would last that long)they would still have 5 wins. Maybe more...

[milkman]

Originally Posted by Just Passin' By

That one guy was a turnstile at right guard, and was killing the line, both with the run and the pass. Neal started the final 9 games in 2008. Here's the breakdown



Sack totals in the first 8 weeks (7 games), as Neal was on PUP and then working his way back: 28

Number of times in the first 8 weeks (7 games) that Cassel was sacked more than 3 times in a game: 5


Sack totals in the final 9 games: 19

Number of times in the last 9 games that Cassel was sacked more than 3 times in a game: 1

That one guy was not responsible for every one of those sacks.

The change in the offense had something to do with the sack totals falling.

[BossChief]

Originally Posted by Just Passin' By

That one guy was a turnstile at right guard, and was killing the line, both with the run and the pass. Neal started the final 9 games in 2008. Here's the breakdown



Sack totals in the first 8 weeks (7 games), as Neal was on PUP and then working his way back: 28

Number of times in the first 8 weeks (7 games) that Cassel was sacked more than 3 times in a game: 5


Sack totals in the final 9 games: 19

Number of times in the last 9 games that Cassel was sacked more than 3 times in a game: 1

yeah, that will happen when you change your offense to a full blown shotgun spread

geezus

[BossChief]

Originally Posted by milkman

That one guy was not responsible for every one of those sacks.

The change in the offense had something to do with the sack totals falling.

Its like he didn't even watch his own teams games.