Chiefs’ MVN Reader Justin Puts It Best: This Is Hard to Watch
The Denver Broncos gained 156 yards and scored 2 TDs in their first 2 possessions. The Chiefs didn’t come close to matching those totals in 4 quarters.
What happened is actually easy to describe. How it happened is a much different question.
It would not be fair to describe this game as a drubbing or a mauling. It would not be fair because it would give the Chiefs too much credit. It would imply that they showed up.
The individual numbers are bad enough. No sacks for Jared Allen. Kolby Smith averaged 0.9 yards per rush on 13 carries. Brodie Croyle averages 4.55 yards per attempt. Only one sack for the whole defense, and zero turnovers. Looking beyond the numbers were worse. The defensive line allowed the Denver RBs to choose from any one of three wide-open gaps to run through. The linebackers were nowhere to be found on running or passing plays. The corners bit on every fake by the receivers, and the safeties constantly overpursued.
The offense? Well, not much needs to or should be said. A bad offensive line was depleted, which could only lead to disastrous results. Receivers dropped easy passes (can we really call Kris Wilson a receiver, or a football player, anymore?). Denver pass rushers got to Croyle seemingly before the offensive linemen knew the ball was snapped. Kolby Smith tried valiantly to run through a wall that simply had no holes.
Perhaps worse is that the Chiefs looked like a team in disarray. Samie Parker, despite not being injured, was inactive because the Chiefs wanted to give Jeff Webb (who himself got a benching from kick-return duties) and Bobby Sippio a chance to prove their worth (though Webb has failed in just about every other of his numerous opportunities this year). The Chiefs started Boomer Grigsby at FB, and perhaps their best designed play of the day was a pass to him. The defense, though largely composed of the same starting players, had absolutely no communication with each other.
Are the Chiefs playing for a high draft pick? You would almost hope so, given their level of play of late, but it could just as well be that this team really is as bad as the media experts thought they were before the season started. Either way, Justin put it best: this is [really, really] hard to watch.
This entry was posted
on Monday, December 10th, 2007 at 11:31 am and is filed under Analysis.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
THE AUTHOR
RECENT ARTICLES BY DIVISION RIVALS
ARCHIVE
SPONSORS
Online Seats
Kansas City Chiefs Tickets football tickets
Ticket Specialists
Kansas City Chiefs Tickets Kansas City Royals Tickets
Coast to Coast Tickets
Kansas City Chief Tickets Kansas City Royals Tickets Big 12 Championship Tickets Banquet 400 Race Tickets Kauffman Stadium Seating Chart
Great Seats
Kansas City Chiefs Tickets Tickets - Kansas City Royals Superbowl Tickets NFL Tickets Concert Schedules
7 Responses to “Chiefs’ MVN Reader Justin Puts It Best: This Is Hard to Watch”
December 10th, 2007 at 12:13 pm
Lose them all, Chiefs - seriously, if you’re not going to bother playing, the fans may as well reap the “reward” of a high-draft pick.
Knowing this team, and their history, they will win their final 3 games and go 7-9, thereby putting us right around #18-20 in the draft. Too low for an impact stud, too high to consider the season successful.
What an embarrasment - bring on the Royals. At least it looks like they care some of the time.
RB
December 10th, 2007 at 1:05 pm
7-9 wont put us near pick#20. Im thinkin more like 15. I really hope we can get Jake Long, the stud OT out of Michgan.
December 10th, 2007 at 2:11 pm
Chris- there’s some question about Long’s pass-blocking abilities. There’s some speculation that, for now, he’s best suited at RT (which, of course, would still be a huge upgrade over what we have right now).
I also disagree with the assertion that you can’t find a stud at 20. You can. It’s not as obvious, but hey, the Chiefs have done awfully well at #20 the past 2 years (Hali & Bowe).
What I’d prefer is to have a higher pick to use as trade bait. This team needs a lot more than just 1 top-10 pick. It badly needs some depth.
December 10th, 2007 at 7:00 pm
Phil — could you clarify? I thought we had 11 draft picks (including the Michael Bennett pick) going into next year, but I keep hearing 10. Which is it?
I think if we end up with a top 10 pick (we will), we should definitely snag the best corner in the draft, which right now looks like an Antoine Cason out of Arizona — currently ranked 8th on rivals.com. That would be perfect and would justify a high pick on an impact position.
I think the O-line picks can come throughout the draft, but we have to pick up at least 3-4 on the first day.
Thanks for quoting me too!
jbopp
December 11th, 2007 at 9:51 am
Justin,
The hang-up might be that the terms of the Tynes, Bennett, and Sims trades were not disclosed (same with Trent Green, but the details of that trade leaked out pretty quickly). If the Chiefs got 2008 picks for all 3, that brings them to 11 picks.
We’ll find out for sure at the end of the season, when the draft order is set. My guess is that they have 11 picks, with a ton of picks in the 5th-7th rounds.
December 11th, 2007 at 1:02 pm
the top corner is Malcolm Jenkins from Ohio State through most peoples eyes as well as my own. I’ve looked into a lot of mock drafts and Cason is usually the third corner behind Jenkins and Aqib Talib of Kansas. We could get Cason at around the 20th pick, but Sam Baker would prolly also be availble around there, so Baker would prolly be chosen over Cason.
March 4th, 2008 at 6:42 am
[…] move on without our ’secret weapon,’” while Home of the Chiefs blogger Phil Yoon asked back in December “can we really call Kris Wilson a receiver, or a football player, anymore?” […]
Leave a comment