![]() |
What were your impressions of the game?
The game wasn't on in my market yesterday and radio coverage was spotty all day, so I only heard portions of the game.
Who played well? Who didn't? Were there any surprises? For example, it sounded to me like maybe Big Irish at RT was what most of us expected - a little better at run blocking, a little worse at pass blocking. Give me your take. |
1 Attachment(s)
My impression of the game?
Pretty much the same as my impression of Sam Kinison. OH....OWWWWWWW......AAAAAAAAAAAAGH!!!! |
I was disappointed by the amount of times the O-Line allowed defenders a free shot at LJ and Cassel. I remember at least 4 times defenders came into the backfield untouched by a blocker. That stuff has got to stop.
|
Big Irish > Ndukwe. No question. And McIntosh.
|
B. Albert isn't a pro left tackle
|
Our Offensive Line is officially capable of losing entire football games.
|
Big Irish did indeed do better. Not a brick wall by any means, but Cassel did have more time than in previous games.
The game was played better than last week. And there were quite a few positives. But they still made some of the same mistakes. 7 penalties. Forcing the run, and not doing it very well. LJ had a few good runs, and a few where you question whether he's closing his eyes and hoping to hit a hole. Bowe had 1 catch, and you'd swear they're designing plays away from him. The WRs cannot get any separation at all though. It's a glaring issue. Cassel was pretty inaccurate. He looks like he's trying to force things because nothing is working. Only 88 yds passing, but you can't say they were trying very hard to pass in the 2nd half. Haley seems to be making a point that they will run the ball no matter if it works or not. Our CBs had a good game. Flowers dominated. Carr wasn't too bad either. DLine didn't do a very good job in the second half. More whiffs from the LBs and safeties. It was improvement overall from last week, but very very slight. Haley continues to send mixed signals. |
is basketball season here yet?
|
I can't believe KC went into the offseason knowing the OL and pass rush were in shambles and didn't do much to address it. The OL and pass rush was poor, again. Surprise.
Pass defense sucks as well. On 3rd down, here's a novel idea. Call plays where the receivers are beyond the 1st down marker. That way, in the rare case the QB has 3 seconds to throw and throws accurately, the receiver has a greater chance of getting the first down, or more accurately with KC, dropping what should have been a first down. When you are down two scores, try passing more often down field. At least pretend you are trying to make a realistic comeback. |
Quote:
|
after Charles fumbled the kickoff and the giants scored, i didn't watch, for the first time in basically forever...
|
Quote:
|
At one point late in the game, the Chiefs had something like 8 goal to go plays, and they had a whopping -6 yds total for those plays. Pretty telling stat. We seem to piss our pants in the red zone..
|
Quote:
|
Quote:
"There's the kickoff, to Jamaal Charles, who fumbles....." That's exactly how it started...which is where I started drinking. The CBs did indeed play well but the zone coverage was getting destroyed. Flowers definitely continued to show he's capable of playing amongst the elite. Got beat bad when he underestimated Manningham's speed (50 yards). But intercepted the next pass to redeem himself. Overall, Eli had time and picked them apart, coverage is still suspect outside #24 - but most are when they have 5 seconds to get open. Not that we didn't get any pressure, Tamba had a couple series where he was making noise and Vrabel's investment continues to shock and fascinate me. For a guy I was sure didn't want to be here, he plays with a lot of emotion and is constantly around the play. That and he's vocal, extremely vocal. Offense was ugly. Buried amongst a buffet of lost blocking assignments were a few decent runs. There were, in equal parts; receptions, dropped passes, bad throws...which equated to 88 passing yards. We had nine (9) I think nearing halftime. LJ was his sporatic self. Bowe dropped at least one that was just dumb, and thus fell off the playcalling map I think... Cassel was throwing behind just about everyone by a step or a step and a half - which was scary...but he looked bothered all day too. Again, he had no time so he was constantly under completely unblocked pressure. Antonio Pierce, free reign, like he knew the snap count kind of pressure occasionally.... |
The o-line was horrible about 90% of the time. Cassel is becoming a master of the one-step drop. Speaking of Cassel, it wasn't his best day. He was consistently behind his receivers.
The defense was almost as bad. Parts of the game were reminiscent of the beating the Ravens put on KC. As far as anybody playing well, I would say the corners played well for the most part after getting smoked for the first 20 minutes of the game (which is a real good sign for Flowers - he's a guy where giving up one play doesn't screw up his whole day), Hali looked mostly competent and Dorsey looked okay, while the middle linebackers and safeties were about what you'd expect. There were no bright spots on offense. People will try to tell you the running game was better, but it really wasn't, outside of a single series in the first quarter where they were able to gain yardage on three consecutive plays (8, 7 and 5 yards) and the occasional random long run in the middle of a veritable sea of 0-3 yard carries. The passing game was abysmal. Cassel had no semblence of a pocket, the timing (and his accuracy) in the short passing game was off, screen passes didn't work. It was pretty brutal. The only reason the score was as close as it was was Manning taking himself out of the game by tripping over his own feet and bruising his heel. If he plays more in the second half, they probably end up over 30. He was just rolling us. |
Quote:
|
Quote:
LJ had 84 yards midway through the fourth quarter...then we commenced with the "draw for a five-yard loss" gameplan. The running game definitely made steps yesterday. |
Quote:
|
Haley's got a hammer and a chisel trying to take down a different concrete wall every week. He'll try this and that with little success. Eventually they'll get something that'll work or a weaker wall to work against. He's learning what works and what doesn't.
|
Quote:
|
|
Quote:
Larry had carries that went for 8, 7, 5, 4, 15, 10, 3, 19 and 7 yards. That's 9 carries for 78 yards. We got good production from the running game yesterday. If the passing game wasn't a complete cluster****, we could actually put some drives together. Sad... |
The good: Flowers and Carr were good considering the circumstances. I think Dorsey continues to improve week by week. Vrabel and Hali had a decent game. Definite upgrade at right tackle.
The bad: Our safeties are terrible. Run defense borders on terrible. Team has an aptitude to screw something up at the worst time. Offense is amazing in its ability to not get anything right. Defenses just take away Bowe and they've solved it all. Larry Johnson is looking old. Waters IMO is not what he used to be. Cassel was not great, but passable, especially considering he has little weapons and little chance to get into any rhythm |
Quote:
|
Quote:
LJ had 46 yards at halftime. |
Quote:
However, having said all that... I now concede that a.) he didn't draft/FA as well as he could have and b.) even if he knew Thigpen whacked it and Croyle might be fragile, he was probably better off NOT going after a new QB from another team but instead using that money on the O-line and D-line. Football games are won in the trenches. You can find a QB in the draft, even in a late round. And with a better O-line Thigpen and Croyle could've "held the fort" (as Parcells likes to say) until a franchise QB could be drafted/developed. In hindsight, it didn't make sense to pony up big bucks to Cassel. Don't get me wrong. I'm not saying Cassel is a bad QB. I'm not even saying it was a bad signing. I'm just saying it might have not been the best direction for the Chiefs to go given their state. Hell, Pioli could've signed a cheap re-tread like Jeff Garcia if he wanted to improve the QB situation while seeing what else he had around him. |
WRs couldn't get quick separation
O-line couldn't hold off that Giants pass rush long enough for WR to shake free You can't put the ball on the carpet on the first play of the game against a top 5 team The Chiefs got jobbed by the officials, and that took a relatively close game and turned it into a fait accompli. The D-line was unable to hold up at the point of attack Dropped passes continue to hurt the team Cassel was about a half-step behind with a lot of his throws The WRs didn't use their bodies to influence the defenders on lobs to the end zone Waters and Albert continued their struggles There were some pretty good things happening out there, given the competition. You won't hear much about them from the riled masses or the shit stirrers in the media, though. |
Quote:
LJ finished the day with 53 yards. Cassel, running for his life, had 25 yards. Don't pretend like those were designed plays. Charles had 2 carries for 24 yards, with a long of 24 yards. That came on the final drive, when it hardly mattered. So while statistically they had more than 100 yards, the stats clearly don't tell the entire story. Or even part of it. The run games still has serious, serious problems. |
Quote:
Seek help. |
Quote:
That is interesting that your numbers don't jive with the NFL numbers. Are WPI statistics figured differently? |
Well if the line sucks and the running back sucks you aren't going to have much of a running game. Duh, ok.
|
Quote:
Offensive line did better ... better run blocking and pass blocking. Cassel looked like he was expecting to get sacked so even when he didn't he still was nervous in the pocket and didn't throw the ball well. He missed 2 open receivers on long passes that would of probably been touchdowns. He threw behind the receiver on several others. Not good. Offensive play calling was weird. We would run the ball with success 2/3 times in a row and instead of using that to go play action pass, Haley would continue to run the ball until we got stuffed a few times and then go to the pass in 3rd and long. he also went to the draw play at the most unusual times. Normally you go to a draw after you have had some success throwing the ball but haley would actually go to the draw when the defense was looking run. It made no sense.. our cornerbacks got burnt sever times early in the game but then got better as the game went along. Jacobs > our linebackers return game is still rough ... Charles has a fumble problem and Wade really doesn't seem to want to have anything to do with punt returns. He pretty much looks for any excuse to fair catch it. |
Quote:
|
Quote:
|
Quote:
M. Cassel 4 25 0 12 J. Charles 2 24 0 24 J. Battle 1 3 0 3 |
I didn't watch the game.
How did O'Callaghan do? Is he at least holding up the RT position? |
Quote:
9 carries for 78 yards. Good stuff for sure. |
Quote:
|
Quote:
|
There were some good things. Most notably we did not get completely obliterated by Jacobs, which I fully expected. If you stack up the run defense from yesterday and compare it to Carolina and Tennessee from last year, major improvement. Jacobs got his and we gave up some, but given how NYG runs on everyone, I was pleased.
Got pressure occasionally, but nothing to affect a series. Coverage had some really nice bright spots, but Steve Smith was typically WIDE THE **** OPEN. Not making contested or difficult catches, WIDE THE **** OPEN. I have no clue what was going on. Our safeties blow. Boss hurt us some, but not as bad as I thought he would. It could be that our LBs are better in coverage than we anticipated or they didn't look his way because Steve Smith was typically WIDE THE **** OPEN. Cassel played like ass. He got hit a lot and was always under pressure. Always. I only remember one time where he got protection (on a 3 step drop) and threw a perfect ball. He overthrew DBowe twice. It looked like Bowe wasn't full speed. Wade biffed a WR screen. None of the WRs did...anything. Albert had a false start. Lots of missed assignments. Lots of getting blown off the ball. Lots of running draw plays, where instead of a hole, there were 2 LBs sprinting into the backfield. Lots of plays where the dude lined up over guard would step through the hole and hit Cassel/LJ right after the handoff. Just horrid line play. Horrid. Officiating was really really bad. All over the place. Unacceptably bad. Chiefs players were chippy. Lots of scuffles. Tyler got a personal foul penalty for ****ing with Bradshaw (who also got an offsetting penalty and was running his mouth all ****ing day), when given the opportunity, the D would lay some lumber, Vrable was in the face of the officials (rightfully so) quite a bit. For a team that sucks ass, they are certainly more spirited than anything we've seen here in several years. Posted via Mobile Device |
Quote:
|
Offense was putrid.
Special Teams was okay but outclassed by NYG. Defense was ripped for 400+ yards. This is a very bad football team. The thing that stood out to me the most is NY did not respect our receivers AT ALL. They had absolutely zero fear of the deep pass. For a team with as shitty an OL as KC has, for a team that is constantly allowing pass rushers to get to the QB, they are f*&#@ing <i>terrible</i> at executing screen passes! I don't know if the plays are too obvious, or if our OL is so gawdawful that they can't pull, or both? Regardless, this team cannot successfully execute a screen play. Speaking of pulling OL, we need to stop that shit right now. Every time we pull an OG for a run, the man in front of them shoots right through the gap to take our RB down for a loss. Playcalling was shit; especially in the red zone. From the six freaking yard line we ran shotgun passes on three of four snaps. The other was a shotgun sprint draw! WTF. I thought Haley wanted to build a running team? So why in the *#@$% would you go into a shotgun on the freaking goal line? Seriously, this team has some major issues. It's not all personnel. |
Quote:
|
My impression was that KC has yet to field a football team in the 09' season.
|
We still suck...
Why run routes 10 yards when its 4th and 27, no downfield passing ever |
Oh. I forgot. Corey Mays had a couple very very nice run stuffs. I wish that guy could cover.
Posted via Mobile Device |
Quote:
Haley is going to regret saying that.:LOL: |
Gretz sums up the offensive offense:
RUNNING GAME – The Chiefs ran for 105 yards, or 4.2 yards per carry. Cassel had 25 of those yards on scrambles away from pass rush pressure, so the running backs produced just 80 yards on 21 carries. Larry Johnson had 53 yards on 18 carries and now has 189 yards in four games. The Chiefs are averaging 101.5 yards per game. There was something about that performance that Todd Haley liked. “I think running the football has been an encouragement to me,” Haley said. “We set out today to try and run the football a little bit and I thought we did that some. I would say running the football is starting to show up as something we can do.” PASSING GAME – This was ugly against the Giants. Cassel was 15 of 32 for 127 yards, with two TD passes and no interceptions. The longest pass play of the game for the Chiefs was a 43-yard pitch from Cassel to TE Sean Ryan. The longest catch by a wide receiver was an 18-yarder by WR Bobby Engram. On the season, the Chiefs are averaging 145 yards passing per game. As a team, they are averaging 5.8 yards per attempt. PASS PROTECTION – The Giants defense came into the game with three sacks in three games. Everyone knew that type of production wouldn’t last long. Against the Chiefs, New York got five sacks in 37 passing plays or one every 7.4 passing plays. Cassel was hit many more times and at one point looked like he may have dinged that bad left knee of his. How was the protection Matt? “I think they’re doing a good job,” Cassel said. “They’re out there giving 110 percent each and every play.” And here was the key line from Cassel: “We’re just going to continue to work at it until we get it right.” In four games, Chiefs QBs have been sacked 13 times in 127 passing plays, that’s a sack every 10 times the Chiefs go back to pass. CONVERTING THIRD DOWNS – Last week it was 0 for 11 against the Eagles. Sunday against the Giants they were two of 15. That’s two of 26 or just about as bad as you can get. Here is the third down tale of woe: * 3rd-and-8 at the KC 23 – Cassel was flushed from the pocket ran for six yards and fumbled the ball. Cassel recovered but the Chiefs were two yards short. * 3rd-and-5 at NY 16 – Cassel’s throw to WR Bobby Engram bounced off the helmet of LB Michael Boley. * 3rd-and-9 at KC 21 – TE Sean Ryan caught Cassel’s throw but gained just four yards. * 3rd-and-10 at KC 30 – Cassel to RB Larry Johnson went for minus-one yard. * 3rd-and-9 at KC 11 – WR Bobby Wade caught a pass but was tackled for a six-yard gain. * 3rd-and-8 at KC 26 – Cassel to Engram for 18 yards and a FIRST DOWN. * 3rd-and-13 at KC 41 – Cassel’s pass to WR Mark Bradley was good for nine yards. * 3rd-and-18 at KC 16 – Bradley caught a pass for 10 yards. * 3rd-and 7 at KC 45 – Cassel was sacked for a 10-yard loss by DE Osi Umenyiora. * 3rd-and-11 at NY 30 – Incomplete pass to WR Dwayne Bowe. * 3rd-and-11 at NY 10 – Incomplete pass to Engram. * 3rd-and-7 at KC 44 – Cassel scrambles for 12 yards and a FIRST DOWN. * 3rd-and-11 at NY 11 – Incomplete pass to Johnson. * 3rd-and-2 at NY 2 – Incomplete pass to Wade. * 3rd-and-27 at KC 15 – Incomplete pass to Wade. On 11 of those 15 third downs, the distance to move the sticks was eight yards or more. Those kind of distances does not provide good chances to succeed. On third down, Cassel was six of 12 for 46 yards. |
Quote:
And dude... that's a lot to write on your mobile device... |
Quote:
|
1. Cassel is much worse than I expected he would be.
2. We are, without a doubt, the worst team in the league. 3. We are worse than at any point during the Herm era. |
Quote:
|
Quote:
I give it up to Haley and the team.. They sure show alot of fire and passion even though they suck ass 90% of the time... |
I thought straight up line played better and the running game looked better, especially considered who they were facing. Picking up blitzes is still a big issue. Way, way too many WR/TE type of screens in this offense going for no gain, especially on 3rd down. Offense never gets in sync, and forces our D to play a long time. Both Flowers and Carr had some great plays, but at the same time Smith could seem to get wide open whenever they needed a big play for a first down. Cassel still holds the ball for to long, but it isn't like we can see if anyone is getting open either.
It is really hard to tell much, when you only get 1 first down in the first half week after week, it really doesn't let you establish anything, nor can you break into your play book. Haley needs to get in a QB coach, its one thing to run the O and the Team during a game, but who is working with the QB on the sideline between series? |
Quote:
We shall see. |
Quote:
I'm not going to rag on him for having to hurry some passes due to the line, but when he does have time and still misses, he needs to be called on it. |
I do agree that this team has more fire than i've seen, it sucks the refs took out the aggressiveness from our safeties early with that shitty penalty call
|
Quote:
Also agree Fish guy. They are playing hard, regardless of the suck, they arent giving up... Reflects the passion of the Head Coach... |
Quote:
|
Quote:
|
Quote:
There's absolutely zero chance the comment has any effect on his career one way or another, because ultimately he's not going to be judged on this year alone. At the end of it all, he'll either have won enough games that people will have forgotten, or he'll have lost so many games that the comment is insignificant by comparison. Furthermore, it's kind of interesting to see so many references to the comment NOW, when almost EVERYBODY thought they'd be no better than 1-7 halfway through the season. |
Quote:
Giants averaged 4.7 yards per carry. Chiefs averaged 4.2 yards per carry. Let the spinnin wheel spin baby! |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
In general, people only regret saying things if there's real and concrete consequences. He's not gonna get fired for saying it. Furthermore, the majority of fans and media that are bitching would have been bitching with or without that comment. So even if he did care about what they think, the comment is still fairly inconsequential. |
Quote:
Oh and that Pioli is regretting hiring Haley.... Should be front sports news... |
I think Cassel played fine, yeah he was a bit behind on a couple of passes and had a couple overthrows. He also hit dbowe and wade in the hands a couple times to have them drop it.
I don't think you can blame him on the short throws on 3rd down. The defense took away anything deep, his best shot is to throw short and hope they can make a play. Realize the dude has nano seconds to make a decision with our line. I would rather him take a dump off than have osi riding him down to the ground. He also made a couple plays in the 4th quarter. He looks better than Trent did his first year. Get him a line and he will be fine. |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
I know you hate Herm and all but Gunther couldn't put together a freakin' intelligent sentence in two years as head coach. |
Quote:
:rolleyes: |
Quote:
|
Quote:
|
Quote:
|
Quote:
Why can anyone give us a link or something? CP is failing... |
All times are GMT -6. The time now is 04:53 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.