Looney ... The Morning After: Philadelphia

[Mr. Laz]

The Morning After: Philadelphia

By Josh Looney
Posted 5 hours ago
Chiefs show grit, but still not a win

Mr. Kansas City himself called me shortly before kickoff last night. Bill Grigsby is the best. When it comes to re-living Chiefs history, there are few better sources than ‘Ole Grigs.
Anyway, he asked me if I had a Chiefs record book handy, which I did. Grigs wanted to test his Chiefs knowledge.

“Now correct me if I’m wrong,” Grigsby said. “But the first time that the Eagles and Chiefs played each other was in 1972, and the Eagles won that game 21-20.”

He was correct; and then, of course, went on to tell a story from that day in Chiefs history.

Grigsby’s tale involved the Chiefs being three-touchdown favorites against Philly. The Eagles were woefully bad that year, 0-5 when they visited Arrowhead (they’d finish 2-11). Unfortunately, for the Chiefs, there was a pre-game alarm as to what was about to come.

“I get out there and our United States flag that’s flying at the top of Arrowhead is upside down,” Grigsby explained. “(Former GM)Jack Steadman was running around like Catfish Hunter with a no-hitter in the ninth inning and the bases loaded.

“Now remember this,” Grigsby continued. “The teams had never played before and the Chiefs were three touchdown favorites with a flag flying upside down. That means, in international code, ‘distress.’”

The “distress” call went out early once again against the Eagles at Arrowhead on Friday night. This time in the first contest played at the Chiefs newly renovated home.

The Chiefs fumbled on the first play from scrimmage, giving Philadelphia the football on the Kansas City 22 yard line. When Eagles RB LeSean McCoy sprinted his way for an 18-yard touchdown just 50 seconds into the contest, things looked bad. When the Chiefs fumbled on their third play from scrimmage and punted on their fifth, things looked worse.

On the Chiefs next offensive series, QB Matt Cassel’s pass hit off of TE Tony Moeaki’s hands and landed in the arms of Eagles CB Trevard Lindley. That’s when it looked like the Eagles rout was on.

“I don’t know that it could start a lot worse than it did, both offensively and defensively,” head coach Todd Haley said after the game.

But in this instance, the rout wasn’t on.

The Chiefs defense came alive, forcing five consecutive punts after allowing an Eagles field goal near the end of the first quarter. Kansas City front-line players would notch their first turnover of the preseason, tally four sacks and exit midway through the third quarter holding a 14-10 lead; it was something that seemed improbable just a quarter and a half prior.

“They say in boxing that it’s not how hard you punch, it’s how you react after you’ve been punched,” Haley said. “We took a couple of pretty good body blows; they might have been a couple of head shots, hay-makers, whatever you want to say, but guys fought back and made plays.”

How many times have we seen the Chiefs start the game in a similar fashion over the past few seasons, only to get run out of the building?

Last year’s game against the Eagles immediately comes to mind, as does the game against the Giants and that 2008 drubbing in Carolina. There are other examples as well. Call it the “here we go again,” or “same old, same old” type of feeling, but things turned around differently at The New Arrowhead last night.

“I think it was just the ‘want to,’” LB Demorrio Williams said. “Early on we probably hung our heads down but I think the guys realized what type of team we have and guys came out and just fought to win the game. We are trying to win this year and trying to bring Arrowhead back.”

Whatever it was, it was something to build on.

While Williams and Andy Studebaker did their best to provide a spark with a pair of sacks, the Chiefs offense didn’t come alive until a bizarre penalty grounded the Eagles. Cassel connected on eight consecutive passes in a 16-play drive that was extended by the fourth-down delay of game penalty on Philadelphia’s punt return team. It was a play that finally kick-started the Chiefs offense.

The span of time between that penalty and when the Chiefs starters were removed from the game was the best that the Chiefs have looked as a team thus far in 2010. The team was physical on both sides of the football and made plays that amount to what it takes to win in the NFL.

The overall play before that penalty, and then after the removal of the starters, is what has to be nixed before the regular season begins.

Three to Like

QB Takedowns

Finally! The Chiefs recorded their first sack of the preseason, and they did it in pairs.

Demorrio Williams played like a maniac on Friday night, finishing with a pair of sacks, a diving pass breakup and five tackles. Andy Studebaker pitched in with two sacks of his own and DL Dion Gales added another quarterback takedown in the fourth quarter to give the Chiefs a quintet of sacks on the evening. It was the first time since September 23, 2007 (vs. Minnesota) that the Chiefs recorded five or more sacks in single game.

“That is really important,” Williams said of the Chiefs notching a handful of sacks. “Especially to put their offense in a second and long, third and long, things like that are huge. On third down we got some pressure on the quarterback and gave our other guys a chance to make plays.”

The numbers could have been even better, had the Chiefs finished off a few more chances at wrapping up Kevin Kolb, Mike Vick and Mike Kafka.

Gritty Defensive Effort

The defense as a whole turned in an extremely solid performance, especially in the second and third quarters.

They weathered an early storm from Philadelphia; a storm that was trying to turn ugly in a hurry. Physicality was at a pre-season high with big hits all over the field, including a wicked stick by Derrick Johnson. The defense was blue collar, gritty, gutsy…whatever you want to call it…they played the game the way that it is meant to be played.

“Defensively we played together as a unit,” said S Kendrick Lewis, who had an interception. “Everyone was on the same page and we blitzed them a little. Guys were getting free and making plays and applying pressure. On the back end we did our thing as far as coverage is concerned but as a unit, it all worked in our favor.”

In the end, holding Philadelphia to just 5-of-17 on third down made a big difference in the way the night went defensively.

Rushing Roles

The offense didn’t have its best day as a unit, but the Chiefs run game offers something to look forward to heading into the regular season.

Both of the Chiefs speedsters, Dexter McCluster and Jamaal Charles, averaged around six yards a carry and got loose in the open field. Situationally, the Chiefs bigger backs turned in some solid runs too. Thomas Jones was able to convert third-and-short situations, as was Jackie Battle, and Jones found the end zone on an 11-yard carry to get the Chiefs back on top in the third quarter.

It’s clear that the Chiefs are aiming to be a running football team.

Three for Improvement

Finding a Way to Win

How much better would Chiefs fans feel if Kansas City’s reserves could have just forced a three-and-out on Philadelphia’s final series? Or even a turnover on down in the Red Zone?

Instead of kneeling on a win, the Chiefs were dealt a loss in the game’s final minute.

For some, it doesn’t matter. The starters dug their way out of an early hole, took the lead and brought some swagger back to Arrowhead. For others, it doesn’t matter who was on the field; the Chiefs found a way to lose a tight game. Preseason or not, we’ve seen this outcome before and it’s not any fun.

Wherever you stand, there’s something to be said for the confidence that is built in successfully finishing off an opponent.

Turnovers Crush Chances

Before the Chiefs were on the board, they had already dug themselves into a two turnover hole. Kansas City’s turnover ratio is now at -7 (eight giveaways, one takeaway) this preseason. Dick Vermeil used to have some sort of turnover chart built with winning percentages based off of negative, positive and neutral finishes in the turnover department.

I don’t have that chart handy, but the Chiefs have lost the turnover battle in all three preseason games of 2010 and own a 0-3 record in those contests.

Philadelphia, by the way, scored their first 10 points on series’ that followed a Chiefs turnover.

Starting Fast

The Chiefs need to fix this broken record before the regular season gets under way.

[ChiTown]

Originally Posted by Just Passin' By

The lineman failed to engage the opposing lineman, thus allowing the defender to get his hands in the air. No further explanation is needed.

That's a rich explanation right there, Mrs. Cassel.

[SAUTO]

Originally Posted by Baby Lee

Yes, absolutely no need to explain why a QB who throws nowhere but the flat with any accuracy turned a ****ING flea flicker into a checkdown pass after wandering back up into the pocket, for no more reason than it seemed the easiest place to which to mosey.

Why don't we go full reerun and have those RB receiving passes in the flat run right back to the middle of the field to be tackled by a DLman?

maybe some here should watch the replay, the long reciever was COVERED from what i saw on the flea flicker.
Posted via Mobile Device

[Just Passin' By]

Originally Posted by JASONSAUTO

maybe some here should watch the replay, the long reciever was COVERED from what i saw on the flea flicker.
Posted via Mobile Device

Doesn't matter. The deep receivers could all have dropped dead of heart attacks and people here would still be complaining about Cassel. It's not about figuring out what happened. It's about bitching about Cassel.

[SAUTO]

yep just watched it again.

chambers was covered even trent said so.

cassel didnt wander anywhere. he stepped into the throw to chambers and didnt throw it. then he stutter stepped and threw it to bowe on a crossing route. the line let the defender knock it down.

but the long ball (chambers) had two defenders in the area.
Posted via Mobile Device

[TEX]

Originally Posted by notorious

I am not going to accect a ****ing thing. Cassel sucks ass, and Pioli made a terrible error in judgement trading for him.

The only way we as fans should cut Cassel any slack is if he starts producing. If that happens, you will see a large amount of the pissing and moaning subside.

If we just accept what we have, the Chiefs will never win.

This. Plus the Chiefs do not have a legit starting QB on the roster. They need to fix that.

[Coach]

Originally Posted by Just Passin' By

Cassel hasn't been anywhere near as bad as he's been portrayed on this board.

I touched the issue on this thread.

http://www.chiefsplanet.com/BB/showt...232598&page=19

But will copy and paste it on here, just to save everybody the trouble.

Originally Posted by Coach

While he was here in KC for one season, he did play in NE for a season, if I am not mistaken, and numberous of posters here, before and during the 2009 season pointed out the flaws that Cassel had during his time in NE, and that has carried over here to KC. Namely the issue here is that he holds on to the ball too long/unaware of his surroundings that he takes unacceptable sacks.

Last year, he was given a chance, especially at a stage where the offensive line play was actually better during the end of the season, and that Charles became a legitimate playmaker that the Chiefs needed in a bad way. The first half of the 2009 season, I gave him several passes due to the fact that our offensive line play was a big steaming pile of shit, and Larry Johnson's infamous 2.7 YPC, and the receivers was also full of steaming pile of shit as well.

Now when the offensive line play was improved at the end of the season, awful as it may seem, just barely passable, plus with the addition of Charles of having a legitimate threat to score whenever he touches the ball, you'd think with those two improvements, the QB play should have improved, other than having a steaming pile of shit receiving corps. Unfortunately, with the improvement of offensive line play and the addition of Charles, Cassel's play actually was worse.

On Oct 26 in 2009, is the date that Larry Johnson's twitter incident came into light. That set the motions of him getting suspended and having his ass cut, which prompted Charles into the starting role in November. Before Charles, the Chiefs total rushing, as a team, before Week 10 (since there are 16 games, split it to 2 8 games), was 788 yards on 208 attempts, which translate into a 3.8 YPC.

During that first 8 games, Cassel's numbers was 125 completions, 225 attempts (55.6 comp. %) for 1256 yards. 5.58 YPC, 10 TD's, 5 INT's with a QB rating of 77.2. Given the situation and offensive line play, along with Larry Johnson not contributing to anything, it's "passable" considering the situation(s) involved.

Now, the last 8 games of the season, as a team, from Week 10 to 17, the Chiefs total rushing, as a team, was 219 attempts for 1148 yards, a 5.2 YPC. Some of this can be contributed to Charles, but also better line play as well.

During that last 8 games, Cassel's numbers was 146 completions, 268 attempts (54.5 comp. %) for 1668 yards. 6.22 YPC, 6 TD's, 11 INT's with a QB rating of 63.8. That is unacceptable due to the fact that the offensive line play gotten better and having Charles being involved.

His numbers did not improve, which it SHOULD have when the line play was better and Charles was doing something that Larry Johnson couldn't do. Cassel's play DID not improve, in fact, it actually regressed worse than his first 8 games. Had his numbers stayed the same or shown SOME improvement, he wouldn't have this much criticism on the board.

And finally, as far as the GM is concerned, the first year during his watch was an abortion of all ages. Drafting Tyson Jackson? Ouch, that's going to hurt this franchise more than it's going to do good. McGee? Brutal. It's really sad that the only person that actually had more value than he was slotted in his pick was Succop. Giving Cassel that big contract, even though he was under KC's control for the next two years during that time, if I am not mistaken. And finally, it was really sad just to have the twitter incident was probably the final straw that had to make him get rid of him. I would have gotten rid of LJ by week 4/5 since it was apparent he was done. But the Chiefs had to drag it out till Week 9, unfortunately.

The second year, the jury is still out on that, but, it has shown some promise. This year's draft picks may (or may not, depending on who you speak to) be one of the good draft picks KC had in some time. Berry, that's obvious. McCluster, I liked the pick. Arenas, I also liked the pick. We all saw what he's capable of doing on special teams, and I think he'll develop into a nice fine nickel corner. Kendrick Lewis is looking like a good pick, based of his play on pre-season. Again, I know it's early, but in my opinion, it is favorable so far. Still does not take out the sting of drafting Jackson though.

[SAUTO]

Originally Posted by Just Passin' By

Doesn't matter. The deep receivers could all have dropped dead of heart attacks and people here would still be complaining about Cassel. It's not about figuring out what happened. It's about bitching about Cassel.

bowe was the right read there, he had a lb iirc running with his back to the qb and had a step on the defender covering him. he was open when the ball left matts hand.
Posted via Mobile Device

[Just Passin' By]

Originally Posted by JASONSAUTO

bowe was the right read there, he had a lb iirc running with his back to the qb and had a step on the defender covering him. he was open when the ball left matts hand.
Posted via Mobile Device

Oh, I wasn't questioning your analysis. I was just noting that it doesn't matter to a large group of posters on this board.

[the Talking Can]

our 63 million dollar franchise QB, who by consensus is surrounded by new 'playmakers' in DMC and Brokaki, earns a 64 QB rating in his longest outing of the preseason in which he throws for 85 yards (including a gift int on the goal line that a ham handed LB dropped)...

and he's being praised, and simultaneously absolved of all responsibility, by his fart sniffing pats fan stalker...


can someone explain how a QB puts up such shit numbers and is then praised for playing well?

[Just Passin' By]

Originally Posted by Coach

I touched the issue on this thread.

http://www.chiefsplanet.com/BB/showt...232598&page=19

But will copy and paste it on here, just to save everybody the trouble.

Cassel developed some bad habits over the course of last season, because he spent the first half of the year running for his life and having to throw the ball to people who usually weren't open, and who often couldn't catch the ball even when they were. His play still shows the effects of that, because it's obvious that he has absolutely no confidence in that line. It's the sort of thing happens with most quarterbacks during games when the team is getting overwhelmed. It happened enough to Cassel last year that he's expecting it every game now, and the important thing moving forward is what he does about it, because he definitely let it get to him over the course of last season. His attitude on the field is also something I'd be worried about if I were the coaching staff, because he's at the point where he's letting every failed play get to him in a way you can see on the field, and his teammates are certainly going to notice that.

But noting those issues, and bitching about everything the man does, are two different things. He made some very nice throws against Philadelphia, and he had the team in the game when he left the field, yet some of the posters here are acting as if he went 0-for-60 and knifed six little old ladies during the timeouts.

[Just Passin' By]

Originally Posted by the Talking Can

our 63 million dollar franchise QB, who by consensus is surrounded by new 'playmakers' in DMC and Brokaki, earns a 64 QB rating in his longest outing of the preseason in which he throws for 85 yards (including a gift int on the goal line that a ham handed LB dropped)...

and he's being praised, and simultaneously absolved of all responsibility, by his fart sniffing pats fan stalker...


can someone explain how a QB puts up such shit numbers and is then praised for playing well?

Well, Can:

If the incomplete to Chambers is on Chambers, that would have had an impact on Cassel's numbers despite his making a good throw.

If the incomplete to Jones was because Jones got caught up, or because of a read difference due to his inexperience in the system, that would have a negative impact on Cassel's numbers despite his making the right throw.

If either Moeaki or the wide receiver was in the wrong spot, that's not on Cassel, because 2 receivers had run routes into the same 5 yard area. Even if he wasn't in the wrong spot and the throw was a bit off, moeaki should have caught the damned ball, which would have removed the INT from Cassel's sheet and would have added yards.

If the incomplete to Bowe was because Bowe was too slow in adjusting to coverage, or because he didn't come back properly, that would impact Cassel's numbers despite it being the right throw.

I also didn't absolve Cassel of responsibility. I posted: "getting those cleared up would go a long way in helping to evaluate Cassel's performance last night". That's different than the take you had in the game thread, for example, where you decided to bitch at Cassel over the incompletion to Chambers.

[Sweet Daddy Hate]

Originally Posted by Baby Lee

Nothing about the checkdown, knocked down, drifting back INTO the pocket ****ING flea flicker?

That play transcended Benny Hill to an impromptu Fellini film.

Quality work, Sir.


Would anyone else really like to pistol-whip JPB at this point?

I mean; ****...

[DeezNutz]

Expecting Brokaki to catch that ball is laughable. A better approach would be not to expect your "franchise" QB to complicate a horrible decision by throwing a horrible ball.

And if Cassel is still "suffering" from poor line play at the beginning of last year, he's a bigger waste than I assumed.

[Coach]

Originally Posted by DeezNutz

Expecting Brokaki to catch that ball is laughable. A better approach would be not to expect your "franchise" QB to complicate a horrible decision by throwing a horrible ball.

And if Cassel is still "suffering" from poor line play at the beginning of last year, he's a bigger waste than I assumed.

That ball shouldn't have been thrown in there in the first place. It was well defended by the Eagles.

[Mr. Laz]

Originally Posted by JASONSAUTO

yep just watched it again.

chambers was covered even trent said so.

cassel didnt wander anywhere. he stepped into the throw to chambers and didnt throw it. then he stutter stepped and threw it to bowe on a crossing route. the line let the defender knock it down.

but the long ball (chambers) had two defenders in the area.
Posted via Mobile Device

watch is again and look for Bowe being open on the crossing pattern over the middle.

single coverage
cornerback was 2/3 yrds behind him on his hip
no linebackers between cassel and bowe(that i could see)

easy completion and maybe a touchdown if Bowe turns it upfield quickly