clock menu more-arrow no yes

Filed under:

Lions Beat Chiefs And 10 Things To Remember From The Game

New, comments
DETROIT, MI - SEPTEMBER 18:  A wide view from the end zone during a NFL game between the Kansas City Chiefs and the Detroit Lions at Ford Field on September 18, 2011 in Detroit, Michigan.  The Lions won 48-3 (Photo by Dave Reginek/Getty Images)
DETROIT, MI - SEPTEMBER 18: A wide view from the end zone during a NFL game between the Kansas City Chiefs and the Detroit Lions at Ford Field on September 18, 2011 in Detroit, Michigan. The Lions won 48-3 (Photo by Dave Reginek/Getty Images)
Getty Images

We're not going to be doing a whole lot of review from this game because, frankly, it's too painful to keep watching what the Kansas City Chiefs did out there but I do have 10 things to remember from their game with the Detroit Lions.

It wasn't that bad early on. The Lions started off with the ball and scored on their first possession. From there, the Chiefs made them punt three consecutive times while KC drove into Detroit territory twice. The Chiefs running game was clicking and it seemed they were able to move the ball on them. I thought the Chiefs still had a shot until midway through the second quarter or so.

Jamaal Charles went down with about 8:24 remaining in the first quarter. It was the sixth offensive play of the games for the Chiefs and the sixth consecutive rushing play to start the game. It's a small sample size but that tells me the Chiefs were planning on sticking to their strengths in this game.

I think we knew the Charles injury was bad. You look at the video and you can tell. It just looks bad and it looks painful. Pretty much the opposite of the ACL injuries to S Eric Berry and TE Tony Moeaki. Neither of those looked serious at the time.

2009 NFL draft is looking worse. Especially if K Ryan Succop isn't looking good. Maybe this is just me being extra snippy because the Chiefs lost so bad but Succop's missed field goal hurt. Well, at the time I thought it hurt. I didn't realize it wouldn't ultimately matter but Succop missed a 44-yarder he should've made. He hit 86 percent of his field goals in year one, which was nice. But dropped to 77 percent in year two and it seems he doesn't have much range.

The Chiefs sort of stopped the run. Todd Haley says that's always the Chiefs No. 1 goal. But that's only because the Lions had no trouble passing the ball. Detroit's top two backs combined for 25 carries for 82 yards, a little over three yards per carry.

Dexter McCluster fumbled...again. Seriously, this is becoming a problem. RB Jamaal Charles had a fumbling problem and that made Haley very upset, visibly upset. I don't know what to do with McCluster because, despite his fumbling issue, the Chiefs need him. Charles is gone so McCluster is one of the guys who will help to replace him.

Five turnovers for Matt Cassel this season. He had an interception last week, another three picks this week and also fumbled one away. Just as a reference, Cassel had seven picks all of last season.

More personal fouls for the Chiefs. Two on the first drive alone as CB Brandon Carr was flagged for extending a fight and DE Glenn Dorsey had a roughing the passer call. Being bad is one thing. Being bad and undisciplined is another. That sorta stuff reminds me of the Monday Night Meltdown with Marty in 1998.

Did the Lions run the score up? They were up 41-3 with just over five minutes remaining in the game and, with their backup quarterback in, they went for it on fourth down getting the touchdown. That's definitely running the score up. Is that a bad thing? Not in my opinion. I'm sure there's a sportsmanship rule here but, in my opinion, if you can't stop it, don't play.

The Chiefs were huge underdogs at nine points. And nine points wasn't nearly enough.