ChiefsPlanet
Page 10 of 18 « First 6789 10 11121314 Last »
Show 80 post(s) from this thread on one page

ChiefsPlanet (https://chiefsplanet.com/BB/index.php)
-   Nzoner's Game Room (https://chiefsplanet.com/BB/forumdisplay.php?f=1)
-   -   Chiefs Reflections on a Rat****ing (https://chiefsplanet.com/BB/showthread.php?t=235296)

milkman 10-17-2010 04:42 PM
Quote:
Originally Posted by dirk digler (Post 7097894)
It would have been looked like a risky call.

It was a high reward high risk play. The safe play would have to run it or throw a safe pass. You just need 2 yds not 30
The problem is that Cassel decided he was going to Moeaki from snap.

He never looked anywhere else.

But even that would not have mattered had he thrown the ball in front of Moeaki and the safety, because Moeaki had position.

It was a pathetic pass, plain and simple.

dirk digler 10-17-2010 04:43 PM
Quote:
Originally Posted by milkman (Post 7097896)
How many third and short yardage situations had they converted by running the ball?

The Texans had stuffed us on nearly every third and short run throughout the game.

Almost every third down conversion came via the pass.
In my mind why not run it and if you don't get it go for it on 4th down

KC kid 10-17-2010 04:44 PM
Quote:
Originally Posted by dirk digler (Post 7097910)
In my mind why not run it and if you don't get it go for it on 4th down
Probably would have run some more time off the clock too, but noooooo we wanna pass. Look, he is not Peyton Manning. He should not have to be for people to think he had a good game

milkman 10-17-2010 04:45 PM
Quote:
Originally Posted by dirk digler (Post 7097910)
In my mind why not run it and if you don't get it go for it on 4th down
Not in that position at that point in the game.

You convert or punt.

There is no other option.

KC kid 10-17-2010 04:45 PM
Quote:
Originally Posted by dirk digler (Post 7097910)
In my mind why not run it and if you don't get it go for it on 4th down
Especially since we had not stopped them in 3 straight possessions. Once I saw Colquitt, I knew we had lost.

dirk digler 10-17-2010 04:46 PM
Quote:
Originally Posted by milkman (Post 7097907)
The problem is that Cassel decided he was going to Moeaki from snap.

He never looked anywhere else.

But even that would not have mattered had he thrown the ball in front of Moeaki and the safety, because Moeaki had position.

It was a pathetic pass, plain and simple.
He would have had to throw it short because Wilson was right there to make the play. But a LB was a few yds in front of Moeki so he had to get it over him.

ChiefsCountry 10-17-2010 04:46 PM
Quote:
Originally Posted by dirk digler (Post 7097910)
In my mind why not run it and if you don't get it go for it on 4th down
Play action was the right call, just the wrong execution.

milkman 10-17-2010 04:47 PM
Quote:
Originally Posted by KC kid (Post 7097913)
Probably would have run some more time off the clock too, but noooooo we wanna pass. Look, he is not Peyton Manning. He should not have to be for people to think he had a good game
The clock is the one reall good argument that can be made for running in that situation.

But the fact is, even if you run the ball when you fail to convert, you are still going to leave enough time on the clock for the Texans to mount a drive.

dirk digler 10-17-2010 04:48 PM
Quote:
Originally Posted by milkman (Post 7097917)
Not in that position at that point in the game.

You convert or punt.

There is no other option.
I don't know. If your D isn't stopping them and your O only needs 2 yds and has been running at huge clips all day long I think they could get 2 yds in 2 plays to end the game.

It is kind of like how the 2003-2004 Chiefs Offense had to play because they couldn't trust the d.

milkman 10-17-2010 04:48 PM
Quote:
Originally Posted by dirk digler (Post 7097920)
He would have had to throw it short because Wilson was right there to make the play. But a LB was a few yds in front of Moeki so he had to get it over him.
Cassel was making good throws all day.

He picked a terrible time to revert to Crapsel.

KC kid 10-17-2010 04:48 PM
Quote:
Originally Posted by milkman (Post 7097923)
The clock is the one reall good argument that can be made for running in that situation.

But the fact is, even if you run the ball when you fail to convert, you are still going to leave enough time on the clock for the Texans to mount a drive.
but you make them use a timeout or run it to the 2 min warning. Of course, the way the D played, they only needed 60 seconds. The gone in 60 seconds defense today

Bearcat 10-17-2010 04:49 PM
Quote:
Originally Posted by DaneMcCloud (Post 7097889)
You're ****ing stupid.

Cassel is paid $15 million dollars a year to WIN games for the Chiefs, not shit the bed.

He shit the bed on the final possession, plain and simple.
Eh, I wouldn't blame any QB for not driving 61 yards in :28 for a GW TD... yeah, Cassel shit the bed on that drive, but winning the game at that point is a lofty expectation, if not a unreasonable one, for any quarterback.

milkman 10-17-2010 04:50 PM
Quote:
Originally Posted by dirk digler (Post 7097932)
I don't know. If your D isn't stopping them and your O only needs 2 yds and has been running at huge clips all day long I think they could get 2 yds in 2 plays to end the game.

It is kind of like how the 2003-2004 Chiefs Offense had to play because they couldn't trust the d.
You simply don't risk leaving them that short a field.

dirk digler 10-17-2010 04:50 PM
Quote:
Originally Posted by ChiefsCountry (Post 7097921)
Play action was the right call, just the wrong execution.
I am not opposed to a play action pass just not the one we ran.

KC kid 10-17-2010 04:51 PM
People make too much a fuss about what Cassel makes. There are lots of highly paid players on that D that choked the game away. People just can't stand Cassel because of personal prejudice and do not even WANT to see him succeed


All times are GMT -6. The time now is 08:56 AM.
Page 10 of 18 « First 6789 10 11121314 Last »
Show 80 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.