Chiefs Cassel Shares Blame In Chiefs' Loss - Page 2

Hammock Parties · 09-20-2009, 08:10 PM

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

Since the third week of preseason, the talk in Kansas City has been about quarterback Matt Cassel’s health, when he’d be ready to start. That question wasn’t answered until Sunday morning when Cassel got the nod to play against Oakland. It’s the answer everybody in Kansas City was looking for, but in hindsight, maybe it wasn’t the best answer.

Cassel squandered a chance to put points on the board at the end of the first half Sunday and threw two costly interceptions after halftime. If the Chiefs even so much as convert a field goal at the conclusion of any of the possessions Cassel made mistakes on, they force overtime, at least.

Cassel’s injury didn’t affect him against the Raiders, and in fact, he appeared rather unfazed by his left knee as he scrambled all over the field in an attempt to make plays. I’m not calling for Brodie Croyle to be the starter, but it’s entirely possible the outcome of Sunday’s 13-10 loss may have been swayed if someone else were under center. On all three blunders, the Chiefs were in Oakland territory. JaMarcus Russell was supposed to be the quarterback on the field Sunday who beat himself with bad mistakes, not Cassel.

The debacle that was KC’s clock management in the first half wasn’t entirely Cassel’s fault. Somehow, the Chiefs were forced to burn two timeouts in the first quarter, and it appeared getting the plays in from the sideline was the catalyst for those wasted timeouts. Head coach Todd Haley focused on that issue.

“We’ve got to be better, because when you use timeouts early in a game like that it usually comes back to haunt you some way or another,” he said. “We can’t do it. To me, one of my top three things here is to have an intelligent team (it’s at the top of the list). That includes all of the coaches and players. We didn’t show that today…I’m not going to make excuses. We have methods to get plays called that we didn’t get done. We have all the technology in the world and we didn’t get it done.”

Some fault also lies at the feet of Dantrell Savage, who was unable to get out of bounds at the end of the first half. Of course, some credit for that belongs to Oakland’s defense. However, it was a poor decision by Cassel to even throw the ball to Savage, who had no prayer of scoring. As close as Kansas City was, that little check-down pass, even if Savage had managed to get out of bounds, wouldn’t have made a field goal attempt any easier for Ryan Succop. Cassel should have thrown it away or taken a shot in the end zone.

Both second half interceptions were inexcusable. Sure, Oakland safety Michael Huff made a terrific play on the second pick, but Cassel overshooting his receiver made that a possibility. Huff’s first takeaway was an egregious error. Cassel was trying to squeeze the ball where it wouldn’t fit, and Huff took advantage.

Of course, if Kansas City’s secondary had taken advantage of a couple interception opportunities, Cassel’s errors would have been overshadowed. In the first half, Brandon Flowers jumped a route and let a pick-six slide right through his fingers. If he hauls that in, the Chiefs win. Also, on Oakland’s game-winning drive, Maurice Leggett had the chance to haul in an interception that would have sealed a victory for the Chiefs. It would have been a tough play to make, but it was makeable nonetheless.

This game is not a microcosm of what Cassel’s career will be. I don’t think he’ll consistently make multiple errors that cost his team the game, but he did Sunday. I’m not calling for his job and again, I’m not lobbying for Croyle. I’m not second-guessing the decision to ink him to a long-term deal, but we should recognize he was in error.

Something else that was obvious Sunday was the atrocity of the personal foul called on Wallace Gilberry during the Raiders’ game-winning drive. Russell fell over on his own accord, and was not forced down by a Chief, so Gilberry and Tank Tyler jumped on the quarterback to down him by contact.

Flagging Kansas City for that was a horrid call, and neither the telecast with Solomon Wilcots nor the radio broadcast with Mitch Holthus and Len Dawson caught that. It was an obvious error, and one that quite possibly cost Kansas City the win. If the ref makes the correct call, the Raiders are facing a second-and-18 situation on their own side of the field instead of a fresh set of downs on KC’s 47-yard line.

However you look at it, the Chiefs are 0-2, and the naysayers will crawl out of the woodwork soon. If you want to generalize about the Chiefs after every game, like many do, you can say Cassel stinks and the Chiefs are terrible, but I advise against that line of thought.

If you thought it was damning last week that the Chiefs lost despite being plus two in the turnover margin, then you have to think it was promising they nearly won despite being minus two this week. If you thought it was encouraging the Chiefs hung in there on the road against a good team that put up over 500 total yards of offense, then you have to admit it’s not so promising they lost to a bad team at home that was out-gained, 409-166.

I know it’s the same message I shared last week, but it’s still way too early to draw conclusions about the Chiefs’ 2009 season. Last week, their defense looked bad, except for a couple big plays. This week, their defense looked great, except for a couple big plays. Last week, their quarterback managed the game well and protected the ball, but made no spectacular plays. This week, not so much. That is the ebb and flow of the NFL.

Sometimes teams get lucky, but the really good teams tend to put themselves in the right place at the right time more often. I don’t think anyone is surprised the Chiefs aren’t ready to be one of those really good teams just yet. Don’t panic and hit the eject button on this season yet, and try not to level any final judgments either.

**Bane** · 09-20-2009, 08:29 PM

Quote:

Originally Posted by KcMizzou

Maybe we do only win 3-4 games this season... fine. It's not just about this season.

Its never just about this season.Thats pee wee bullshit!!!

donkhater · 09-20-2009, 08:29 PM

Fans of the Chiefs would do themselves a great service to disconnect themselves from the success of this team as it relates to wins and lossses. To think that his team was to look and perform like an average team this early in the season was wishful thinking.

I was encouraged by their performance in Baltimore. Despite being clearly out manned, they made smart decisions, played relatively error free, smart football.

I think that smart team is lurking in this squad and Haley will pull it out of them. I'd be (and may very will be) discouraged if the same thing is happening after the bye week. I think Cassel is clearly an upgrade at QB. As he gets healthier and the offense begins to mesh more, I think we will see a good, decent squad on that side of the ball. World beaters? No. But solid.

The other side of the ball is just outmanned. No amount of scheming can make up for the lack of speed, strength and talent. If Haley and Pioli had to start from scratch, one might think that Flowers, Carr and Jackson would be the only current starters that they would definitely pick out to keep. Everyone else can be upgraded. They need playmakers in the worst way.

milkman · 09-20-2009, 08:31 PM

Quote:

Some fault also lies at the feet of Dantrell Savage, who was unable to get out of bounds at the end of the first half.

No, dumbass (whoever you are), none of the fault lies at Savages feet.

He gave a yeoman's effort to get out of bounds, but had no chance.

The fault there lies squarely, and solely, at Cassel's feet.

That is simply not a pass that should have ever been thrown.

You throw the ball the end zone, or you throw the ball away.

It was a piss poor decision, and by far his biggest mental error.

Mecca · 09-20-2009, 08:31 PM

Quote:

Originally Posted by DeezNutz

We have a much better chance this coming week than we do in the following 5. Both these teams playing tonight will hand us our ass.

I think that being a game in Philly is the biggest problem, I don't think Philly is gonna drop back to back home games.

**Bane** · 09-20-2009, 08:32 PM

Quote:

Originally Posted by milkman

No, dumbass (whoever you are), none of the fault lies at Savages feet.

He gave a yeoman's effort to get out of bounds, but had no chance.

The fault there lies squarely, and solely, at Cassel's feet.

That is simply not a pass that should have ever been thrown.

You throw the ball the end zone, or you throw the ball away.

It was a piss poor decision, and by far his biggest mental error.

Careful the Casselites will attempt to hang you for this one!!!

Mama Hip Rockets · 09-20-2009, 08:33 PM

Quote:

Originally Posted by KcMizzou

People are insanely unrealistic.

is it insanely unrealistic to think the chiefs can beat the mother****ing oakland raiders at home?

milkman · 09-20-2009, 08:35 PM

Quote:

Originally Posted by bane_58

Careful the Casselites will attempt to hang you for this one!!!

Doesn't matter.

People can't seem to look at the games with an objective eye.

Cassel did some good things and some bad things.

DJ's left nut · 09-20-2009, 08:36 PM

Quote:

Originally Posted by donkhater

they need playmakers in the worst way.

It all comes down to this, really.

The NFL has become a playmaker's league. If you don't have a legitimate game-changer on both sides of the ball, you're spinning your wheels.

The Chiefs don't have anyone on either side, IMO. In reality, I don't even see anybody with that kind of potential.

Flowers can be a Pro-Bowl CB, but he won't be Asomugha, he won't be Woodson in his prime. He's not going to be a guy that shuts down a passing game, makes a pick and runs it back, IMO. He'll be more like Surtain when Pat was in his prime. A great player, but needs a Jason Taylor with him.

On offense, I just don't see it happening with Bowe. I think we see what we're going to get with him. He'll have a 1300 yd season or two, but he's not going to be among the elite at any point. Cassel isn't that guy either. We really don't have a consistent playmaker anywhere on this team.

It's a paradox. The team's closer to being respectable than I thought, yet somehow further away from being a legit contender than I though...if that makes any sense.

**Bane** · 09-20-2009, 08:36 PM

Quote:

Originally Posted by thurman merman

is it insanely unrealistic to think the chiefs can beat the mother****ing oakland raiders at home?

Thank you! Clearly its insane to think we can win a home opener....I guess were supposed to think we cant win at all so when we do its a big friggn surprise.

**DeezNutz** · 09-20-2009, 08:36 PM

Quote:

Originally Posted by Mecca

I think that being a game in Philly is the biggest problem, I don't think Philly is gonna drop back to back home games.

Any road game is a huge problem for this team. But they didn't play scared in Baltimore, so I expect to see a composed group in Philly.

Hammock Parties · 09-20-2009, 08:37 PM

Quote:

Originally Posted by DeezNutz

Any road game is a huge problem for this team. But they didn't play scared in Baltimore, so I expect to see a composed group in Philly.

I think our offensive line is going to get completely destroyed.

It's gonna take a miracle not to lose by 3 scores.

boogblaster · 09-20-2009, 08:42 PM

The ball at the half should never been thrown, called or anything, the correct call was kick the field goal ... The offense shot themseleves in the foot on two many false starts ... plus the last drive by the fade shouldn't have been allowed .....

milkman · 09-20-2009, 08:44 PM

Quote:

Originally Posted by boogblaster

The ball at the half should never been thrown, called or anything, the correct call was kick the field goal ... The offense shot themseleves in the foot on two many false starts ... plus the last drive by the fade shouldn't have been allowed .....

There were 14 seconds on the clock when the ball was snapped on that play.

That is enough time to take two shots to the EZ, but only to the EZ.

**Bane** · 09-20-2009, 08:45 PM

Quote:

Originally Posted by milkman

Doesn't matter.

People can't seem to look at the games with an objective eye.

Cassel did some good things and some bad things.

I'll give you that and I agree he did some good and some bad.He shouldn't get all the blame but he's supposed the be the leader and the leader always get the blame.

DJ's left nut · 09-20-2009, 08:48 PM

Quote:

Originally Posted by milkman

There were 14 seconds on the clock when the ball was snapped on that play.

That is enough time to take two shots to the EZ, but only to the EZ.

Agreed, this isn't high school.

In the NFL, you have to be able to trust that your QB is not going to do something that MFing stupid. That close to the end zone, it's easy to just fire it out the back without fear of a penalty. There was no excuse for a dump into the flats.

That was on Cassel all the way. I like the aggressive coaching by a staff that is trying to win its players over. It was stunningly poor execution by Cassel.

09-20-2009, 08:10 PM
Hammock Parties I'll be back. Join Date: Nov 2002 Casino cash: $860478	Cassel Shares Blame In Chiefs' Loss http://kan.scout.com/2/901178.html Since the third week of preseason, the talk in Kansas City has been about quarterback Matt Cassel’s health, when he’d be ready to start. That question wasn’t answered until Sunday morning when Cassel got the nod to play against Oakland. It’s the answer everybody in Kansas City was looking for, but in hindsight, maybe it wasn’t the best answer. Cassel squandered a chance to put points on the board at the end of the first half Sunday and threw two costly interceptions after halftime. If the Chiefs even so much as convert a field goal at the conclusion of any of the possessions Cassel made mistakes on, they force overtime, at least. Cassel’s injury didn’t affect him against the Raiders, and in fact, he appeared rather unfazed by his left knee as he scrambled all over the field in an attempt to make plays. I’m not calling for Brodie Croyle to be the starter, but it’s entirely possible the outcome of Sunday’s 13-10 loss may have been swayed if someone else were under center. On all three blunders, the Chiefs were in Oakland territory. JaMarcus Russell was supposed to be the quarterback on the field Sunday who beat himself with bad mistakes, not Cassel. The debacle that was KC’s clock management in the first half wasn’t entirely Cassel’s fault. Somehow, the Chiefs were forced to burn two timeouts in the first quarter, and it appeared getting the plays in from the sideline was the catalyst for those wasted timeouts. Head coach Todd Haley focused on that issue. “We’ve got to be better, because when you use timeouts early in a game like that it usually comes back to haunt you some way or another,” he said. “We can’t do it. To me, one of my top three things here is to have an intelligent team (it’s at the top of the list). That includes all of the coaches and players. We didn’t show that today…I’m not going to make excuses. We have methods to get plays called that we didn’t get done. We have all the technology in the world and we didn’t get it done.” Some fault also lies at the feet of Dantrell Savage, who was unable to get out of bounds at the end of the first half. Of course, some credit for that belongs to Oakland’s defense. However, it was a poor decision by Cassel to even throw the ball to Savage, who had no prayer of scoring. As close as Kansas City was, that little check-down pass, even if Savage had managed to get out of bounds, wouldn’t have made a field goal attempt any easier for Ryan Succop. Cassel should have thrown it away or taken a shot in the end zone. Both second half interceptions were inexcusable. Sure, Oakland safety Michael Huff made a terrific play on the second pick, but Cassel overshooting his receiver made that a possibility. Huff’s first takeaway was an egregious error. Cassel was trying to squeeze the ball where it wouldn’t fit, and Huff took advantage. Of course, if Kansas City’s secondary had taken advantage of a couple interception opportunities, Cassel’s errors would have been overshadowed. In the first half, Brandon Flowers jumped a route and let a pick-six slide right through his fingers. If he hauls that in, the Chiefs win. Also, on Oakland’s game-winning drive, Maurice Leggett had the chance to haul in an interception that would have sealed a victory for the Chiefs. It would have been a tough play to make, but it was makeable nonetheless. This game is not a microcosm of what Cassel’s career will be. I don’t think he’ll consistently make multiple errors that cost his team the game, but he did Sunday. I’m not calling for his job and again, I’m not lobbying for Croyle. I’m not second-guessing the decision to ink him to a long-term deal, but we should recognize he was in error. Something else that was obvious Sunday was the atrocity of the personal foul called on Wallace Gilberry during the Raiders’ game-winning drive. Russell fell over on his own accord, and was not forced down by a Chief, so Gilberry and Tank Tyler jumped on the quarterback to down him by contact. Flagging Kansas City for that was a horrid call, and neither the telecast with Solomon Wilcots nor the radio broadcast with Mitch Holthus and Len Dawson caught that. It was an obvious error, and one that quite possibly cost Kansas City the win. If the ref makes the correct call, the Raiders are facing a second-and-18 situation on their own side of the field instead of a fresh set of downs on KC’s 47-yard line. However you look at it, the Chiefs are 0-2, and the naysayers will crawl out of the woodwork soon. If you want to generalize about the Chiefs after every game, like many do, you can say Cassel stinks and the Chiefs are terrible, but I advise against that line of thought. If you thought it was damning last week that the Chiefs lost despite being plus two in the turnover margin, then you have to think it was promising they nearly won despite being minus two this week. If you thought it was encouraging the Chiefs hung in there on the road against a good team that put up over 500 total yards of offense, then you have to admit it’s not so promising they lost to a bad team at home that was out-gained, 409-166. I know it’s the same message I shared last week, but it’s still way too early to draw conclusions about the Chiefs’ 2009 season. Last week, their defense looked bad, except for a couple big plays. This week, their defense looked great, except for a couple big plays. Last week, their quarterback managed the game well and protected the ball, but made no spectacular plays. This week, not so much. That is the ebb and flow of the NFL. Sometimes teams get lucky, but the really good teams tend to put themselves in the right place at the right time more often. I don’t think anyone is surprised the Chiefs aren’t ready to be one of those really good teams just yet. Don’t panic and hit the eject button on this season yet, and try not to level any final judgments either.
Posts: 297,236

09-20-2009, 08:29 PM	#17
donkhater Brilliant!! Join Date: Sep 2000 Location: Indiana, USA Casino cash: $10014051	Fans of the Chiefs would do themselves a great service to disconnect themselves from the success of this team as it relates to wins and lossses. To think that his team was to look and perform like an average team this early in the season was wishful thinking. I was encouraged by their performance in Baltimore. Despite being clearly out manned, they made smart decisions, played relatively error free, smart football. I think that smart team is lurking in this squad and Haley will pull it out of them. I'd be (and may very will be) discouraged if the same thing is happening after the bye week. I think Cassel is clearly an upgrade at QB. As he gets healthier and the offense begins to mesh more, I think we will see a good, decent squad on that side of the ball. World beaters? No. But solid. The other side of the ball is just outmanned. No amount of scheming can make up for the lack of speed, strength and talent. If Haley and Pioli had to start from scratch, one might think that Flowers, Carr and Jackson would be the only current starters that they would definitely pick out to keep. Everyone else can be upgraded. They need playmakers in the worst way. __________________ The welfare of humanity is always the alibi of tyrants
Posts: 3,994

09-20-2009, 08:42 PM	#27
boogblaster MVP Join Date: Sep 2005 Location: Verdigris Valley Campsite Casino cash: $10004900	The ball at the half should never been thrown, called or anything, the correct call was kick the field goal ... The offense shot themseleves in the foot on two many false starts ... plus the last drive by the fade shouldn't have been allowed ..... __________________ WR or S please
Posts: 10,305