Chiefs Cassel Is Failing Chiefs - Page 13

Hammock Parties · 10-25-2009, 07:30 PM

http://kan.scout.com/2/912917.html

It’s easy to blame the Chiefs’ terrible pass defense or rotten, handicapped offensive line play for Sunday’s 37-7 blowout at the hands of the San Diego Chargers. But you can do that every week. At some point you have to call out the highest-paid player, so it’s time to lay it at the feet of Matt Cassel.

There’s no question Cassel shares some of the blame for the Chiefs’ 1-6 start. He blew a game against the Oakland Raiders in Week 2 but it was nothing compared to what transpired inside a soggy Arrowhead Stadium Sunday. The Chiefs had 19 net passing yards and zero passing first downs at halftime against the Chargers, and even that total was “inflated” by a two-minute drill. At one point, Cassel had dropped back to pass eight times and completed one pass for a grand total of two net yards.

When it was all over, Kansas City had only three passing first downs despite Cassel’s 25 attempts. His 25.3 quarterback rating, a horrifying statistic in a vacuum, appears even more revolting when you consider that it was the lowest rating a Chiefs’ starter has posted since Tyler Thigpen melted down in Atlanta a year ago.

Yes, we’re now revisiting a level of incompetence from KC’s passing game that we haven’t seen since Herm Edwards was trying to save his job by throwing Thigpen to the wolves.

Sunday’s game was that bad. The Chiefs appeared to be a team that cannot field even an average passing attack, and this came at home against a San Diego team with a mediocre secondary and a terrible pass rush. I’m not sure Shaw-knee Merriman touched Cassel, but it really didn’t matter.

As soon as his pocket became congested against the Chargers, Cassel looked lost. The play was dead. And when Cassel did throw, the results were less than inspiring. Specifically, his accuracy hit the bottom of the barrel against the Chargers.

In the second quarter, Cassel threw an awful pass that was intended for newly-activated wide receiver Lance Long. It was underthrown and nearly intercepted. On the next play, Long got a step deep on his coverage, but once again the pass was underthrown and Long was forced to reach back awkwardly in a failed attempt to catch it.

Were they difficult throws? Sure. But Cassel is the highest-paid Chief. He’s supposed to be a difference maker. He failed to make a difference. The Chiefs, already down 14-0 at that point, couldn’t really afford to punt again, but had to because they simply couldn’t move the ball through the air. At all.

A few plays later, Cassel badly skipped a ball to a wide-open Dwayne Bowe, who would have picked up a first down. It wasn’t a difficult throw, and Cassel had a perfect pocket to pass from. He just dumped the ball right in the dirt. Is there really any excuse for that from the highest-paid Chief?

But what really stings is, at one point, Kansas City had a chance to get back in the ball game. They were down 13 points, had been out-gained 2-to-1, and Arrowhead Stadium was a drippy, depressing, scene. But on their first possession of the third quarter, the Chiefs had scored, then KC’s defense had stuffed San Diego’s offense, and all the momentum was on Matt Cassel’s side.

It was at that point that he dropped back to throw, stepped up and heaved one of those long, graceful, arcing spirals you always see in slow motion on NFL Films highlights. For a brief second, Chiefs fans may have seen Jamaal Charles breaking open, seen the ball sailing through the air and thought – this is it! Matt Cassel is about to throw a 65-yard touchdown pass, no one can run down Charles, and this place is about to go crazy! We’re back in this game!

And then the pass fluttered off to the right as Charles made a hopeless stab at an over-the-shoulder miracle catch. The ball thumped into the wet grass and slipped away, just like the opportunity.

Cassel blew it, and he blew the next play when he badly overthrew a wide, wide open Bobby Wade streaking down the right sideline for what was, at least, a 20-yard gain and potentially a touchdown. The pass wasn’t even close. Wade would have needed a last-second gust of hurricane-force wind to catch up to it.

And that was it. On third and long, Cassel scrambled for two meaningless yards, the Chiefs punted, the Chargers torched KC’s defense for another long touchdown. Game over.

The Chiefs had missed their window of opportunity to get back in the game. When you’re a 1-6 team, those chances don’t come along that often. The highest-paid player on the team has to seize the moment. Matt Cassel failed to do that, and right now he is failing the Chiefs. His performance Sunday was as bad as anything we saw from Thigpen a year ago, and could have been worse. Cassel’s three interceptions could have easily been five. If Bowe doesn’t make a sensational play on the end-zone boundary, the Chiefs don’t even score.

Chiefs fans love to laugh at Oakland’s JaMarcus Russell, who is completing only 45.6 percent of his passes. But Cassel is now keeping him company, just four spots above at 54.8 percent. Cassel is 34th in the NFL in yards per attempt (note that there are only 32 starting quarterbacks) and the Chiefs have the league’s worst third-down conversion rate.

Are the questions that arose around Cassel last season in New England still an issue? It’s hard to argue otherwise. The Patriots had a woeful deep passing game a year ago and Sunday, Charles might as well have been Randy Moss getting wide open down the field only to watch the ball sail over his head. There are no shortage of plays where Cassel holds onto the ball and takes a sack, and at this rate, after taking 47 sacks with the Patriots and already another 23 this season, he may wind up as the most-sacked quarterback in the league over the last two seasons. These are not trends that should be ignored.

The saddest part may be that at times, Cassel actually shows signs of being the franchise quarterback he’s paid to be. Sunday, he made a spectacular throw to Long that would have gone for a touchdown had it not been dropped. He threw gorgeous passes to Bowe for clutch, game-tying touchdowns against the Raiders and Cowboys. He has protected the ball well, been a good teammate, played with heart and determination and said all the right things.

But the Chiefs are 1-6, have one of the league’s worst passing games, and here we are comparing Cassel to Thigpen and Russell. After Sunday, it’s hard to argue he hasn’t been a giant disappointment. The Chiefs had a chance, if only for the briefest of moments, and Cassel failed them. His contract demands success.

**DaneMcCloud** · 10-26-2009, 01:11 PM

Quote:

Originally Posted by BossChief

Waters took over half way and wasnt quite the all pro waters quite yet, he was a dlinemen a few short weeks back iirc.

In 2002, we added Roaf and Waters really started to show up and "the line of fame" was built.

You are incorrect.

Waters was originally signed as an undrafted college free agent by the Cowboys as a tight end. After he was cut, he came to KC and played in 6 games in 2000. He moved into the starting guard position in 2001 and by 2004, was a Pro-Bowler.

None of that negates the fact that the 2001 offensive line was far superior to the 2009 version.

Chiefnj2 · 10-26-2009, 01:16 PM

Quote:

Originally Posted by DaneMcCloud

You are incorrect.

Waters was originally signed as an undrafted college free agent by the Cowboys as a tight end. After he was cut, he came to KC and played in 6 games in 2000. He moved into the starting guard position in 2001 and by 2004, was a Pro-Bowler.

None of that negates the fact that the 2001 offensive line was far superior to the 2009 version.

It was superior in hindsight. Walking into 2001 what did you have other than Shields? A LT in Tait who many thought was soft and couldn't cut it at LT. Waters was just starting out on the OL. Weigman was a castoff. Riley was thought of as a bad RT.

Titty Meat · 10-26-2009, 01:16 PM

lol this thread coming from the same guy who also said this week the Chiefs offense would start to improve. How the **** do you have a job writting about footnall?

Sweet Daddy Hate · 10-26-2009, 01:17 PM

Quote:

Originally Posted by DaneMcCloud

You're right.

It was bad luck that Brady had his ACL shredded by Bernard Pollard.

And not just bad luck for Brady...

SDChiefs · 10-26-2009, 01:20 PM

Quote:

Originally Posted by JASONSAUTO

he went 11-5 with that team.how many times has that happened. the pats are 5-2 this year so he's on track to have about the same record. they werent going undefeated WITH brady last year

Brady came in this year and struggled getting back from his injury. Hes gotten his feet under him now and they will finish better than 11-5. Because Brady is a good QB and Cassel is not. Thigpen could have won 11 games with last years Pats team. And he is in no way a great QB.

**BossChief** · 10-26-2009, 01:21 PM

Quote:

Originally Posted by JASONSAUTO

dane the guy consistently has one of the best lines in the nfl sorry. he is a great QB but he has problems when pressured

Jason, I often agree with you're take on subjects BUT

go to a colts board and say they have always had one of the best lines in the NFL.

it is an untrue statement. Their line has struggled since Glenn retired after their superbowl win.

They arent in the same zipcode of suck that ours is in, but they have been a NFL average line at best and have recently struggled with numerous injuries.

Peyton is GREAT at shuffling around in the pocket and has one of the quickest releases in NFL history.

Teams dont blitz because of that and the fact he is so smart he sees the blitz and disects the defense to find the wide open reciever....Cassel sees that blitz and stops looking downfield.

Cassel will never be a top ten QB

SDChiefs · 10-26-2009, 01:26 PM

Quote:

Originally Posted by BossChief

Jason, I often agree with you're take on subjects BUT

go to a colts board and say they have always had one of the best lines in the NFL.

it is an untrue statement. Their line has struggled since Glenn retired after their superbowl win.

They arent in the same zipcode of suck that ours is in, but they have been a NFL average line at best and have recently struggled with numerous injuries.

Peyton is GREAT at shuffling around in the pocket and has one of the quickest releases in NFL history.

Teams dont blitz because of that and the fact he is so smart he sees the blitz and disects the defense to find the wide open reciever....Cassel sees that blitz and stops looking downfield.

Cassel will never be a top ten QB

Hes not even a top 32 QB

**BossChief** · 10-26-2009, 01:27 PM

Quote:

Originally Posted by DaneMcCloud

You are incorrect.

Waters was originally signed as an undrafted college free agent by the Cowboys as a tight end. After he was cut, he came to KC and played in 6 games in 2000. He moved into the starting guard position in 2001 and by 2004, was a Pro-Bowler.

None of that negates the fact that the 2001 offensive line was far superior to the 2009 version.

you're right. I had to look it up. iirc didnt he play some center that year while transitioning?

Lots of stuff clouding my memory from that long ago.

**DaneMcCloud** · 10-26-2009, 01:29 PM

Quote:

Originally Posted by Chiefnj2

It was superior in hindsight. Walking into 2001 what did you have other than Shields? A LT in Tait who many thought was soft and couldn't cut it at LT. Waters was just starting out on the OL. Weigman was a castoff. Riley was thought of as a bad RT.

Well, Tait did just fine. Waters was in the Pro-Bowl three years later and many thought he should have been there sooner. Weigman wasn't a "castoff" but a part time player with the Bears. Riley was not thought of as being "bad" but he was a psycho. After his contract was up, he started for New Orleans.

But regardless, it was superior, no matter how you look at it.

Frankie · 10-26-2009, 01:36 PM

Quote:

Originally Posted by suds79

I really think people should stop drawing comparisons to Trent Green. Yes we all know Trent had a bad 1st year and then went on to be really good.

But is that the exception or the rule? We can't just assume Cassel will turn out the same way.

Will Cassel be better next year? I don't know. I think it's really up in the air right now.

But how many guys have had a bad 1st year and then... had a bad 2nd year also? Then followed up with a 3rd?

Sometimes guys struggle simply because they're not that good.

All I'm saying, is Cassel SHOULD NOT be judged or analyzed for his performance behind this sorrowful O-line. The comparison tp Trent is just to point that out.

Frankie · 10-26-2009, 01:38 PM

Quote:

Originally Posted by BigChiefFan

He's done a remarkable job given the talent he has to work with. Yesterday, he played poorly, but I would still have to give solid marks for his performance to date.

The same.

**SAUTO** · 10-26-2009, 01:39 PM

Quote:

Originally Posted by BossChief

Jason, I often agree with you're take on subjects BUT

go to a colts board and say they have always had one of the best lines in the NFL.

it is an untrue statement. Their line has struggled since Glenn retired after their superbowl win.

They arent in the same zipcode of suck that ours is in, but they have been a NFL average line at best and have recently struggled with numerous injuries.

Peyton is GREAT at shuffling around in the pocket and has one of the quickest releases in NFL history.

Teams dont blitz because of that and the fact he is so smart he sees the blitz and disects the defense to find the wide open reciever....Cassel sees that blitz and stops looking downfield.

Cassel will never be a top ten QB

the point remains that when peyton is pressured he's no where near the same Qb he gets happy feet.

**DaneMcCloud** · 10-26-2009, 01:43 PM

Quote:

Originally Posted by JASONSAUTO

the point remains that when peyton is pressured he's no where near the same Qb he gets happy feet.

You're wrong.

And furthermore, if all it took was pressure, why wouldn't opposing defensive coordinators just bring the house on each and every passing down?

Oh, that's right. Because Peyton would shred their secondary with his quick release, resulting in touchdowns.

Duh.

**DaneMcCloud** · 10-26-2009, 01:47 PM

Quote:

Originally Posted by Frankie

All I'm saying, is Cassel SHOULD NOT be judged or analyzed for his performance behind this sorrowful O-line. The comparison tp Trent is just to point that out.

You are, of course, wrong.

If he was playing magnificently behind this line, would you say the same thing about him?

He locks onto receivers, won't throw downfield, won't throw into traffic and looks like a deer in the headlights. This offensive line sucks ass but Cassel has just shown nothing.

Sweet Daddy Hate · 10-26-2009, 01:48 PM

Quote:

Originally Posted by Frankie

All I'm saying, is Cassel SHOULD NOT be judged or analyzed for his performance behind this sorrowful O-line.

So we're back to the Thiggy/Croyle excuse then?

10-25-2009, 07:30 PM
Hammock Parties I'll be back. Join Date: Nov 2002 Casino cash: $760478	Cassel Is Failing Chiefs http://kan.scout.com/2/912917.html It’s easy to blame the Chiefs’ terrible pass defense or rotten, handicapped offensive line play for Sunday’s 37-7 blowout at the hands of the San Diego Chargers. But you can do that every week. At some point you have to call out the highest-paid player, so it’s time to lay it at the feet of Matt Cassel. There’s no question Cassel shares some of the blame for the Chiefs’ 1-6 start. He blew a game against the Oakland Raiders in Week 2 but it was nothing compared to what transpired inside a soggy Arrowhead Stadium Sunday. The Chiefs had 19 net passing yards and zero passing first downs at halftime against the Chargers, and even that total was “inflated” by a two-minute drill. At one point, Cassel had dropped back to pass eight times and completed one pass for a grand total of two net yards. When it was all over, Kansas City had only three passing first downs despite Cassel’s 25 attempts. His 25.3 quarterback rating, a horrifying statistic in a vacuum, appears even more revolting when you consider that it was the lowest rating a Chiefs’ starter has posted since Tyler Thigpen melted down in Atlanta a year ago. Yes, we’re now revisiting a level of incompetence from KC’s passing game that we haven’t seen since Herm Edwards was trying to save his job by throwing Thigpen to the wolves. Sunday’s game was that bad. The Chiefs appeared to be a team that cannot field even an average passing attack, and this came at home against a San Diego team with a mediocre secondary and a terrible pass rush. I’m not sure Shaw-knee Merriman touched Cassel, but it really didn’t matter. As soon as his pocket became congested against the Chargers, Cassel looked lost. The play was dead. And when Cassel did throw, the results were less than inspiring. Specifically, his accuracy hit the bottom of the barrel against the Chargers. In the second quarter, Cassel threw an awful pass that was intended for newly-activated wide receiver Lance Long. It was underthrown and nearly intercepted. On the next play, Long got a step deep on his coverage, but once again the pass was underthrown and Long was forced to reach back awkwardly in a failed attempt to catch it. Were they difficult throws? Sure. But Cassel is the highest-paid Chief. He’s supposed to be a difference maker. He failed to make a difference. The Chiefs, already down 14-0 at that point, couldn’t really afford to punt again, but had to because they simply couldn’t move the ball through the air. At all. A few plays later, Cassel badly skipped a ball to a wide-open Dwayne Bowe, who would have picked up a first down. It wasn’t a difficult throw, and Cassel had a perfect pocket to pass from. He just dumped the ball right in the dirt. Is there really any excuse for that from the highest-paid Chief? But what really stings is, at one point, Kansas City had a chance to get back in the ball game. They were down 13 points, had been out-gained 2-to-1, and Arrowhead Stadium was a drippy, depressing, scene. But on their first possession of the third quarter, the Chiefs had scored, then KC’s defense had stuffed San Diego’s offense, and all the momentum was on Matt Cassel’s side. It was at that point that he dropped back to throw, stepped up and heaved one of those long, graceful, arcing spirals you always see in slow motion on NFL Films highlights. For a brief second, Chiefs fans may have seen Jamaal Charles breaking open, seen the ball sailing through the air and thought – this is it! Matt Cassel is about to throw a 65-yard touchdown pass, no one can run down Charles, and this place is about to go crazy! We’re back in this game! And then the pass fluttered off to the right as Charles made a hopeless stab at an over-the-shoulder miracle catch. The ball thumped into the wet grass and slipped away, just like the opportunity. Cassel blew it, and he blew the next play when he badly overthrew a wide, wide open Bobby Wade streaking down the right sideline for what was, at least, a 20-yard gain and potentially a touchdown. The pass wasn’t even close. Wade would have needed a last-second gust of hurricane-force wind to catch up to it. And that was it. On third and long, Cassel scrambled for two meaningless yards, the Chiefs punted, the Chargers torched KC’s defense for another long touchdown. Game over. The Chiefs had missed their window of opportunity to get back in the game. When you’re a 1-6 team, those chances don’t come along that often. The highest-paid player on the team has to seize the moment. Matt Cassel failed to do that, and right now he is failing the Chiefs. His performance Sunday was as bad as anything we saw from Thigpen a year ago, and could have been worse. Cassel’s three interceptions could have easily been five. If Bowe doesn’t make a sensational play on the end-zone boundary, the Chiefs don’t even score. Chiefs fans love to laugh at Oakland’s JaMarcus Russell, who is completing only 45.6 percent of his passes. But Cassel is now keeping him company, just four spots above at 54.8 percent. Cassel is 34th in the NFL in yards per attempt (note that there are only 32 starting quarterbacks) and the Chiefs have the league’s worst third-down conversion rate. Are the questions that arose around Cassel last season in New England still an issue? It’s hard to argue otherwise. The Patriots had a woeful deep passing game a year ago and Sunday, Charles might as well have been Randy Moss getting wide open down the field only to watch the ball sail over his head. There are no shortage of plays where Cassel holds onto the ball and takes a sack, and at this rate, after taking 47 sacks with the Patriots and already another 23 this season, he may wind up as the most-sacked quarterback in the league over the last two seasons. These are not trends that should be ignored. The saddest part may be that at times, Cassel actually shows signs of being the franchise quarterback he’s paid to be. Sunday, he made a spectacular throw to Long that would have gone for a touchdown had it not been dropped. He threw gorgeous passes to Bowe for clutch, game-tying touchdowns against the Raiders and Cowboys. He has protected the ball well, been a good teammate, played with heart and determination and said all the right things. But the Chiefs are 1-6, have one of the league’s worst passing games, and here we are comparing Cassel to Thigpen and Russell. After Sunday, it’s hard to argue he hasn’t been a giant disappointment. The Chiefs had a chance, if only for the briefest of moments, and Cassel failed them. His contract demands success.
Posts: 297,541

10-26-2009, 01:16 PM	#183
Titty Meat Inmem 2.0 Join Date: Aug 2007 Location: My house Casino cash: $-1222442	lol this thread coming from the same guy who also said this week the Chiefs offense would start to improve. How the **** do you have a job writting about footnall?
Posts: 78,161

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode