Chiefs Cassel Is Failing Chiefs - Page 10

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.

Frankie · 10-26-2009, 11:56 AM

Quote:

Originally Posted by stevieray

Cassel's career in KC has just started...false expectations can't and won't define it six games.

This.

CASSEL SUCKS JUST ABOUT AS MUCH AS TrINT DID HIS FIRST YEAR.

Blame Cassel for being shell-shocked. He has 0.0000000006 seconds everytime he tries to pass. He gets no help from the running game. That makes even the best of them push with the wrong pass, or hold on to the ball too long hoping somebody gets open. Put 5 LIVING guys in front of him and THEN crucify him if he sucks. .... SHEESH!

Micjones · 10-26-2009, 11:59 AM

No. Cut him now.
We've seen enough!

suds79 · 10-26-2009, 12:01 PM

Quote:

Originally Posted by Frankie

This.

CASSEL SUCKS JUST ABOUT AS MUCH AS TrINT DID HIS FIRST YEAR.

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.

Chiefnj2 · 10-26-2009, 12:03 PM

Quote:

Originally Posted by suds79

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

... and other guys struggle because their team and coaching sucks ass.

Coach · 10-26-2009, 12:03 PM

The question I have to ask is, was Trent's O-line that bad during his first year?

**SAUTO** · 10-26-2009, 12:13 PM

Quote:

Originally Posted by Coach

The question I have to ask is, was Trent's O-line that bad during his first year?

not even in the same universe as ours this year

orange · 10-26-2009, 12:16 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.

Exactly.

This post should be a smiley that people could paste into every thread with one click.

**BossChief** · 10-26-2009, 12:18 PM

Quote:

Originally Posted by Frankie

This.

CASSEL SUCKS JUST ABOUT AS MUCH AS TrINT DID HIS FIRST YEAR.

Blame Cassel for being shell-shocked. He has 0.0000000006 seconds everytime he tries to pass. He gets no help from the running game. That makes even the best of them push with the wrong pass, or hold on to the ball too long hoping somebody gets open. Put 5 LIVING guys in front of him and THEN crucify him if he sucks. .... SHEESH!

Trent may have thrown alot (24)of interceptions but at least he wasnt afraid to put the damn ball in the air.

He threw for 3800 yards and 17 tds while taking a similar amount of sacks (39)

to put it in perspective, Cassel is on pace to throw for under 2500 yards 20 tds and 13 interceptions, this year. (this is his per game average x 15 because he missed game 1) OH YEAH and 54.8% comp %

=gunshy

***Allow me to drop the Thigpen bomb once.....in 10 starts he threw for 2408 yards...18tds...12ints....386 rushing 3 tds... OH YEAH EXACTLY 54.8% completion %***

where is that $63,000,000 going?

BigChiefFan · 10-26-2009, 12:23 PM

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.

**BossChief** · 10-26-2009, 12:25 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.

We arent going to be adding Willie Roaf to our line anytime soon...not to mention Brian waters became a starter half way through trents first season. That is two probowl/hof caliber linemen added to a line that surrendered 39 sacks in 2001 and 26 in 2002

**BossChief** · 10-26-2009, 12:27 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.

based on what? <---------------this is a real question

SDChiefs · 10-26-2009, 12:29 PM

Quote:

Originally Posted by GoChiefs

He had halfway decent protection on several throws and blew them. Horribly.

Hold him accountable.

I love how people want to hold people more accountable then they actually were (Herm) but people like Cassel can do no wrong and they blame everyone else on the team. There were some dropped passes. But Cassel flat out sucked of Ryan Leaf proportions.

BigChiefFan · 10-26-2009, 12:31 PM

Quote:

Originally Posted by BossChief

based on what? <---------------this is a real question

Let's see... we have the worst O-line in football. We have the worst WR core in football. We have the worst TEs in football. We have a below average FB. We have sub-par HBs, who could quite possibly be the worst in the league, at this point. Add to that a 1st year head coach, a below average defense, and he doesn't have much to work with.

BigChiefFan · 10-26-2009, 12:32 PM

I think it's a given that Cassell played like crap yesterday. Please find me somebody saying anything to the contrary. I'm talking about his entire season and looking at from overall context.

**DaneMcCloud** · 10-26-2009, 12:38 PM

Quote:

Originally Posted by Coach

The question I have to ask is, was Trent's O-line that bad during his first year?

The answer is no.

Tait, Waters, Weigman, Shields & Riley.

I'd take that any day of the week over what the Chiefs have right now.

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

10-26-2009, 11:59 AM	#137
Micjones Whose house? Join Date: Mar 2007 Location: KCMO Casino cash: $10005180	No. Cut him now. We've seen enough! __________________ It's like when I'm right I'm right, when I'm wrong I could been right, so I'm still right cause I coulda been wrong.
Posts: 15,344

10-26-2009, 12:03 PM	#140
Coach Champs! Join Date: Mar 2004 Casino cash: $3708476	The question I have to ask is, was Trent's O-line that bad during his first year? __________________ Super Bowl IV, LIV, LVII & LVIII Champions 2020, 2021, 2023, 2024, & 2025 AFC Champions 1985 & 2015 Major League Baseball World Series Champions 1980, 1985, 2014, & 2015 Major League Baseball American League Champions 2015 American League Central Division Champs
Posts: 54,706

10-26-2009, 12:23 PM	#144
BigChiefFan MVP Join Date: Feb 2001 Location: In the Top 10 Casino cash: $9924205	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. __________________ A 35 year drought can make you thirsty.
Posts: 15,777

10-26-2009, 12:32 PM	#149
BigChiefFan MVP Join Date: Feb 2001 Location: In the Top 10 Casino cash: $9924205	I think it's a given that Cassell played like crap yesterday. Please find me somebody saying anything to the contrary. I'm talking about his entire season and looking at from overall context. __________________ A 35 year drought can make you thirsty.
Posts: 15,777