Chiefs Cassel Is Failing Chiefs - Page 4

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.

**tyler360** · 10-25-2009, 09:16 PM

Quote:

Originally Posted by Raised On Riots

I can imagine that watching this guy play from the stands with a good view of the entire field would be enough to make ones head explode.

The only reason it did not explode was because of the rain. His reads are just as bad as a rookie

smittysbar · 10-25-2009, 09:18 PM

Quote:

Originally Posted by chiefzilla1501

It's a reeruned argument. In the first half, the ball was out within 3 seconds. If it wasn't out, it was because he was flushed by a defender within those 3 seconds.

It's an argument that people keep rattling off because they heard somebody else say it.

The accuracy issues are an issue. Claiming that a QB who doesn't have enough time to hold onto the ball too long holds the ball too long is ridiculous.

He held onto it it to long last year also, sure you have an excuse for that as well

Sweet Daddy Hate · 10-25-2009, 09:24 PM

Quote:

Originally Posted by tyler360

The only reason it did not explode was because of the rain. His reads are just as bad as a rookie

Here, you need a General Piolio's Fried Chicken Nappy Meal; works every time!

**luv** · 10-25-2009, 09:24 PM

Quote:

Originally Posted by tyler360

I went to the game today and sat in the rain for the whole game. Cassel to me just does not look like he has the "it" factor. He missed so many open recievers today. It just really bugs me how he can be so bad game after game after game like this.

But it's NEVER his fault.

chiefzilla1501 · 10-25-2009, 09:33 PM

Quote:

Originally Posted by smittysbar

He held onto it it to long last year also, sure you have an excuse for that as well

Because you keep saying "as well." It's not a ****ing issue this year. You're basically recycling an argument you heard somebody else used and you're ignoring the piles of evidence that show otherwise.

**luv** · 10-25-2009, 09:34 PM

Quote:

Originally Posted by chiefzilla1501

Because you keep saying "as well." It's not a ****ing issue this year. You're basically recycling an argument you heard somebody else used and you're ignoring the piles of evidence that show otherwise.

That he holds onto the ball when he should throw it away, or that he can't hit a receiver?

chiefzilla1501 · 10-25-2009, 09:37 PM

Quote:

Originally Posted by luv

That he holds onto the ball when he should throw it away, or that he can't hit a receiver?

I've said that his inability to hit an open receiver is a problem.

Holding on to the ball is NOT a problem. And in most cases, he can't throw the ball away because there is usually a pass rusher surrounding him in all directions. For as much shit as he takes for taking the fetal position, when you're surrounded, the only thing you can do is protect the ball. Unless people are recommending he move backward and take a 10-yard bigger loss.

**luv** · 10-25-2009, 09:39 PM

Quote:

Originally Posted by chiefzilla1501

I've said that his inability to hit an open receiver is a problem.

Holding on to the ball is NOT a problem. And in most cases, he can't throw the ball away because there is usually a pass rusher surrounding him in all directions. For as much shit as he takes for taking the fetal position, when you're surrounded, the only thing you can do is protect the ball. Unless people are recommending he move backward and take a 10-yard bigger loss.

Okay. He's played 6 games this year. At what point do we start looking at other options?

Sweet Daddy Hate · 10-25-2009, 09:43 PM

Quote:

Originally Posted by luv

That he holds onto the ball when he should throw it away, or that he can't hit a receiver?

Complete the following sentences:

A _____ fell from a tree in the fall.

The Who broadcast a "farewell concert" in the early 80's from Toronto's Maple _____ Gardens.

I was raking my lawn, but I missed one single _____ that got caught in the sidewalk crack.

TRR · 10-25-2009, 09:48 PM

Jay Cutler threw 3 INT's today and the Bears got crushed by the Bungles....does this mean that Cutler is terrible too?

This Cassel hate is ridiculous. He had a bad game...move on. The whole team sucks.
Posted via Mobile Device

chiefzilla1501 · 10-25-2009, 09:49 PM

Quote:

Originally Posted by luv

Okay. He's played 6 games this year. At what point do we start looking at other options?

If that option was on the roster, that'd be one thing. But it's not. Croyle could be a good QB but you can't count on him to play a healthy 16 games.

I don't know the answer to this. Unfortunately, I don't think you get much more options after this season either. No QBs on the open market and probably the worst QB class in the history of the draft. I think the best you can do is just surround him with better players in 2010 and see if that makes a difference. If he's not good then, then you have a 2011 draft class that could have two outstanding QBs that are legit top 5 picks.

Mecca · 10-25-2009, 09:50 PM

Quote:

Originally Posted by luv

Okay. He's played 6 games this year. At what point do we start looking at other options?

It's not going to happen, that's Pioli's boy. They are tied, Cassel is starting for the next 3-4 years regardless of how bad he is.

Sweet Daddy Hate · 10-25-2009, 09:51 PM

Quote:

Originally Posted by chiefzilla1501

I think the best you can do is just surround him with better players in 2010 and see if that makes a difference. If he's not good then, then you have a 2011 draft class that could have two outstanding QBs that are legit top 5 picks.

Ah...dare to dream.

**DaneMcCloud** · 10-25-2009, 09:52 PM

Quote:

Originally Posted by TRR

Jay Cutler threw 3 INT's today and the Bears got crushed by the Bungles....does this mean that Cutler is terrible too?

This Cassel hate is ridiculous. He had a bad game...move on. The whole team sucks.
Posted via Mobile Device

Are you joking?

Cutler ****ing sucks ass. I've been saying this for YEARS. Unlike all the other asswipes that thought Denver would fail without him, I've stated all along they'd be further ahead as a team with him gone.

Denver's 6-0. Chicago's 3-3.

BTW, Cutler hasn't QB'd a winning team since HIGH SCHOOL.

WildTurkey · 10-25-2009, 09:52 PM

Quote:

Originally Posted by TRR

Jay Cutler threw 3 INT's today and the Bears got crushed by the Bungles....does this mean that Cutler is terrible too?

This Cassel hate is ridiculous. He had a bad game...move on. The whole team sucks.
Posted via Mobile Device

This..... he's played 6 games for probably the least talented team in NFL history... shit even the best QB's in the NFL need some help... anyone who claims it's all his fault is a ****ing moron

10-25-2009, 07:30 PM
Hammock Parties I'll be back. Join Date: Nov 2002 Casino cash: $810478	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,432

10-25-2009, 09:48 PM	#55
TRR The Priest and I Join Date: Mar 2003 Location: CO Casino cash: $9420185	Jay Cutler threw 3 INT's today and the Bears got crushed by the Bungles....does this mean that Cutler is terrible too? This Cassel hate is ridiculous. He had a bad game...move on. The whole team sucks. Posted via Mobile Device
Posts: 7,370

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