SB Nation - Sean Ryan

Bills Fantasy Friday: Week 14 Start 'Em/Sit 'Em

Kurupt — Fri, 11 Dec 2009 13:30:14 -0000

The Buffalo Bills return to the field this Sunday as they travel to Arrowhead to face the 3-9 Kansas City Chiefs. It's safe to say, this won't be one of the marquee games this weekend. There also aren't many fantasy options available either. Coming off a rotten performance in Toronto against the New York Jets, the Bills are looking for a rebound performance against a team that just got waxed at home by the Denver Broncos, 44-13. Knowing how bad these two teams are, this could be an ugly one. Are there any players worth starting from this game as many of you are beginning your fantasy playoffs this week? Let's find out.

Quarterbacks
Ryan Fitzpatrick - After a stunningly decent two week stretch, Fitzpatrick came crashing back to Earth with his horrendous 98-yard performance against the Jets. He completed just 9 of 23 passes at 4.3 yards a pop. It was ugly and the only positive was he rushed for 32 yards! After facing the NFL's top ranked pass defense last week, he'll get a bit of a respite as the Bills will be going up against the 28th ranked passing defense. The Chiefs have allowed 250.8 yard per game, 8.0 yards per attempt and 21 touchdowns thus far. Looks appetizing, right? Well, it's Ryan Fitzpatrick we're talking about here. Don't even consider starting him unless your league starts four QB's per team. Verdict: Sit 'Em

Matt Cassel - Cassel has been a major bust for the Chiefs so far. The $63 million man has played so poorly that even Trent Edwards has a higher quarterback ranking. He's completed just 53.9% of his passes at 5.7 yards per attempt. Like Fitzpatrick, don't even think about rolling with Cassel. Verdict: Sit 'Em

Running Backs
Fred Jackson - After an excellent game against the Dolphins, Jackson struggled against the Jets last week. He finished with 13 rushes for 31 yards and added 24 yards on 3 receptions. But the Chiefs defense isn't the Jets defense. Expect Jackson to have a nice bounce back game this week. This late in the season, sometimes the best fantasy players arrive as the result of great fantasy matchups. This could be one of those arrivals. If Jackson gets the majority of the touches, or at least a solid 60/40 ratio, don't be surprised if he has one of the better games of his career. He's a great flex play and makes for a pretty solid RB2 play this week. Verdict: Start 'Em

Marshawn Lynch - Lynch had a nice performance last week with six rushes for 60 yards and a touchdown. It was probably the best he's ran all season, but he only had those six rushes. He'll likely get more carries this week, but Jackson seems like the better play and first option. I wouldn't be surprised by a very good performance out of Lynch, but at this point it's much more likely he'll end up with another 10 carry, 30 yard performance. He could be a nice flex option, especially if he gets any red zone carries, but I wouldn't even consider him in a two running back league. Verdict: Sit 'Em

Jamaal Charles - Charles has been one of the biggest fantasy surprises over the past month. The Chiefs have finally given him the majority of the touches and he's rewarding them with back-to-back-to-back-to-back nice games, including at least one touchdown in each of the past four games. He's averaged over 75 rushing yards per game in that stretch, continues to return kicks (including one for a TD against the Steelers) and is a big play RB in the passing game. The Chiefs will rely on him early and often. He should get 20+ touches and could reward fantasy owners with RB2 or even borderline RB1 numbers. For leagues awarding points for return yardage, Charles is an even better option. Verdict: Start 'Em in all leagues

Wide Receivers
Terrell Owens - Like Fitzpatrick, Owens was coming off back-to-back good games, and just like the big-headed QB, he struggled to put up numbers against the Jets. He should put up better numbers again this week, though it's hard to predict big numbers out of anyone in this passing game. I think the Bills will look to continue getting the ball to him downfield, so if they can hit on a big play, Owens might put up those big numbers here. This will be the last time I'm recommending a Bills' WR all season. Love it. Savor it. Cherish it. Verdict: Start 'Em

Lee Evans - Evans continues playing the Invisible Man in the Bills' offense. The team just can't get him the ball and I refuse to believe it's solely on the QB and play calling. At some point, Evans needs to play consistently right? Don't bother with him, although as typical with Evans, just as you write him off he responds with a monster game before fading into the sunset once again. If you have the stomach, roll the dice. Since you likely have better options, go with them. Verdict: Sit 'Em

Dwayne Bowe - In case you haven't been keeping up with the Chiefs this year, Bowe will be missing his fourth consecutive game for violating the league's substance abuse policy. Don't say I've never looked out for your best interest, Bills friends. Verdict: Duh

Chris Chambers - From the abyss, Chris Chambers has been surprisingly good since joining the Chiefs after being cut by the Chargers. Prior to last week's 11-yard stinker, Chambers racked up 17 receptions for 319 yards and 3 touchdowns in four games. I think last week is a lot closer to what Chambers will be doing the rest of the season. If you are stuck, I'd go with Chambers over Evans (for example), but don't in expecting much against the league's 4th best pass defense. Verdict: Sit 'Em

Tight Ends
Shawn Nelson, Sean Ryan - I'm lumping them together because even though they have the same pronunciation for differently spelled named, they will probably put up the same stats for different teams. Verdict: Sit 'Em

Kickers
Rian Lindell - Lindell had two field goals against the Jets last week and continues to be consistently okay as a fantasy kicker. However, okay isn't what you should be looking for. As always, go with a kicker for a better offense. Verdict: Sit 'Em

Ryan Succop - Yeah, I forgot who their kicker was and had to look it up. I suggest you treat him the same way and disregard him totally. Verdict: Sit 'Em

Defense/Special Teams
Buffalo D/ST - The Bills make for a sneaky play this week against a poor Chiefs offense. The Chiefs OL and QB's have been a part of 40 sacks this year, 2nd most in the NFL. However, surprisingly enough, they've only turned it over 15 times thus far. If the Bills can get after Cassel, look for a decent number of sacks and the potential for some turnovers. Maybe they'll even get another pick six in Arrowhead again! Unless you have a quality D/ST with a bad matchup (i.e. Denver against the Colts, Cincinnati against the Vikings, Arizona against the 49ers on the road), you'll probably steer clear of the Bills. Verdict: Sit 'Em

Chiefs D/ST - Even against the Bills, I wouldn't consider starting the Chiefs D/ST. Verdict: Sit 'Em

Sleepers
Buffalo D/ST - See above

Chris Chambers - Even though I could never imagine starting him, Chambers has indeed become the Chiefs go-to receiver. If Cassel can get the passing game going, Chambers could be in line for some good numbers this week.

**********

In what might be the last game any Bills player might have a relevant fantasy performance, let's hope we see some offensive production this week. Another ugly season can't end soon enough, but one more quality performance will at least give us a positive for this team heading into the Holidays! Good luck to any of you (except Brian) who may be taking part in your league's fantasy playoffs this week. Go Bills!

Who Should the Kansas City Chiefs Cut, Re-sign, and Keep for 2010?

Jon Yoon — Wed, 09 Dec 2009 16:00:17 -0000

by Charlie Riedel - AP

View full size photo »

It's hard not to let my frustrations get the best of me when writing about this year's lowly Chiefs. Rather than vent and curse and scream, I'm going to instead focus my frustrations on a few specific players who I believe are bringing the team down. Some have played their way off the roster and probably out of the NFL; others have played their way out of a starting job; still others have been monumental disappointments.

Let's look at this position by position, starting with the offense.

Quarterback: I've been very patient with Matt Cassel. I understand the situation he's in--his supporting cast isn't great, his receivers are dropping easy passes, and his offensive line has been shaky and inconsistent in pass protection. I get all those things.

That being said, there are a few things that scare me about Cassel. Despite improved protection over the past few games, he is still inconsistent with his downfield throws. In many cases, he's not hitting his receivers in stride and he's making far too many goofy mistakes for a player of his experience level. The excuses are over. His pass protection has gotten better and he is now surrounded by a decent running game. Yet, we're not seeing much improvement from him. All that Cassel has done this season is prove that he's a lousy quarterback for three quarters, but a pretty decent one in the fourth quarter (assuming the Chiefs are still in the game).

I'm not saying Cassel has played his way out of the job, but he certainly hasn't done anything to justify keeping it or securing his place as the QB of the Future. It would be reckless for the Chiefs to enter this offseason without bringing in another strong option at QB. Worst case, Cassel ends up playing really well and the Chiefs can trade their backup away. If the Chiefs don't bring in a strong young option now, it could set the franchise back two or more years.

Because if there is any QB who can push Cassel for a starting job, he's not currently on the roster--Brodie Croyle is too injury prone and Matt Gutierrez is as big of a longshot as you'll find in the NFL. Cassel's poor performance this season has led me to question whether Pioli's loyalties might be clouding his judgment. I like Cassel. I like his work ethic and I want him to succeed, but if he becomes the indisputable starter going into 2010 with no competition, it will really compromise Pioli's no-nonsense, high accountability environment he's building toward. If Pioli is gung-ho about sticking with Cassel next season without bringing in a competitive option, he better be right, or else it could be a decision that haunts him for the rest of his career.

Stays: Matt Cassel (#1 QB), Brodie Croyle (#3 QB)
Bring in: Strong competing #2 QB Option
Dump: Matt Gutierrez

Running back: The good news is that Jamaal Charles is a legit primary back. He's done an incredible job of doing a lot with very little help up front. The play that sticks out in my mind was the toss sweep against the Broncos where he almost made it out to the edge, but couldn't make it there. From what I recall, the guy that got in his way was weakly blocked by Mike Cox. I remember thinking to myself: "Man, if that was Tony Richardson a few years ago, that guy would have been leveled!"

With better blocking up front, Charles has the potential to be a very good "lightning back" who can take on about 15-20 carries a game. He needs to be more careful with the football, but hopefully he can do that with some better awareness and maybe a little bit of strength training. The problem is, Charles is not a primary back in the way LJ was. He shouldn't be a workhorse back nor should he be an all-purpose back. We saw that on Sunday. The Chiefs seemed scared to pound the rock on the goal line. It's because they don't have a "thunder" back to bulldoze forward on short yardage situations. The Chiefs need one of those backs--a big bowling ball that wears out defenses and can muscle a few tough yards on short yardage situations. It would provide more balance to their running game and create a great change of pace for Charles' shifty running style.

Kolby Smith has had a nice little career for the Chiefs, but I wonder if he'll ever play a full season ever again. Outside of Charles and Smith, the options at halfback are not good. Almost everyone in this spot is expendable. However, it's possible the Chiefs keep one of them on the roster, simply because they just have too many needs to fill. At fullback, Mike Cox has effectively played himself off the roster. He doesn't block well, he doesn't run well, and he's been invisible in the passing game. What is it you'd say... he does here? There isn't a shred of a doubt that he will be out of a job in 2010. The Chiefs must bring in a legit Fullback. Must, must, must. And it's not like it's that hard. You can get a top-notch Fullback in the late rounds of the draft.

Keep: Jamaal Charles (#1 HB)
Dump: Mike Cox, Kolby Smith, Tim Castille, Javarris Williams
Possibly retain: Dantrell Savage
Bring in: "Thunder" back. Fullback. Both can be found late in the draft. A "thunder" back might be found on another team's scrap pile

Wide Receiver:

Boy oh boy. You would think that a team coached by a Wide Receivers coach would have receivers that were better at catching the football. You would think that players like Mark Bradley and Bobby Wade, who are hanging on to their roster spot by a very thin thread, would be trying just a little bit harder to compete for their jobs.

Dwayne Bowe is a given, though based on the way he's played this season, I'm not convinced he's a legitimate #1 receiver. Chris Chambers has probably earned his spot on the 2010 roster, although we should prepare for a potential sophomore slump as he had in San Diego. If the Chiefs can find a younger receiver with #1 playmaking capability, they need to break the bank and bring him in (which might mean cutting ties with Chambers). I don't think that will happen, so for now, Chambers is a solid stopgap option. Apart from that, no receiver has played well enough to justify keeping their job.

Bobby Wade, on the whole, has not been terrible. He played like he didn't care to be there against the Broncos, but in most games, he's been a relatively solid slot option. I can't see a situation where Mark Bradley is on this team next season. He has dropped way too many passes in key situations. Lance Long, as it turns out, is not Wes Welker. He's not Ricky Proehl. He's just a guy---pretty good at getting open, but wildly inconsistent at making the catch.

Keep: Dwayne Bowe
Likely keep: Chris Chambers
Bring in: Either a #1 receiver to replace Chambers, or a strong rookie prospect to be groomed to replace Chambers
Very on the bubble: Bobby Wade, Lance Long
Dump: Mark Bradley

Tight End:

Based on the way Haley likes to use Tight Ends, I tend to think he wants a multi-dimensional tight end moreso than a one-dimensional one. He may not want a Tight End who is only stellar at receiving. I don't think he'd mind having a Tight End who was primarily a blocker. Ideally, though, I think he would like a Tight End who was equally good at both.

Leonard Pope has been the sole bright spot at the position and that's not even saying much. Pope's role should really be more situational--a great backup, but not someone I'd like to see as an every-down starter. Sean Ryan does not belong on this roster. I have no idea why he's been here this long in the first place. He can't catch. He's a horrendous blocker. What exactly is his value to the offense? Brad Cottam isn't much better. You can't tell me there aren't better options on the street than these guys.

Keep: Leonard Pope (#2 TE)
Dump: Sean Ryan and Brad Cottam
Bring in: Anyone who isn't named Sean Ryan or Brad Cottam.

Dorsey, Edwards and Krumrie Highlight Chiefs and Bills Connections

Chris Thorman — Tue, 08 Dec 2009 16:00:30 -0000

by David Duprey - AP

2 months ago: Buffalo Bills' Kawika Mitchell is carted off the field after being injured during the first half of the NFL football game against the Cleveland Browns in Orchard Park, N.Y., Sunday Oct. 11, 2009. (AP Photo/David Duprey)

View full size photo »

The normal five comments this connection post gets each week will likely be zero today because there is really nothing of interest to point out between the Kansas City Chiefs' and the Buffalo Bills' connections.

Let's see. Our nose tackle was a Bill for five seasons. One of our tight ends is from Buffalo. And Glenn Dorsey has a cousin on the team.

Whoopty do.

To make this post more interesting than it already is, can you think of some guys from earlier years that were both Bills and Chiefs? Getcha coffee ready (Yeah, that was a bad TO reference. You got a problem with that?).

Chiefs GM Scott Pioli ('88-89) and asst. GM Joel Collier ('88-89) were graduate assistants at Syracuse. Collier was born in Buffalo, NY.
Collier's father, Joe Collier, served as the Bills head coach ('66-68), leading the club to the '66 AFL Championship Game vs. Kansas City.
Chiefs DL coach Tim Krumrie held the same role with Buffalo (2003-05).
Chiefs DT Ron Edwards spent five seasons with Buffalo (2001-05).
Bills asst. to the head coach/special projects Chuck Lester was a scout for three seasons with the Chiefs ('84-86).
Chiefs offensive quality control coach Nick Sirianni is a native of Jamestown, NY.
Kansas City TE Sean Ryan is a native of Buffalo, NY.
Buffalo asst. LBs/special teams coach DeMontie Cross played ('94-96) and coached ('98-99) at Missouri.
Bills P Brian Moorman is a native of Wichita, KS and played collegiately at Pittsburg State in Pittsburg, KS.
Bills LB Kawika Mitchell is currently on IR. He entered the NFL as a second-round (47th overall) selection of the Chiefs in 2003.
Chiefs DE Glenn Dorsey is the cousin of the Bills TE Shawn Nelson.
Buffalo offensive quality control coach Nathaniel Hackett is the son of former Kansas City offensive coordinator Paul Hackett.

Let us know if you come up with any players that were Bills and Chiefs.

Leonard Pope Now the Chiefs No. 1 Tight End

Joel Thorman — Mon, 16 Nov 2009 22:24:20 -0000

More photos » by Ben Margot - AP

Chiefs coach Todd Haley is angry. (AP Photo/Ben Margot)

Browse more photos »

According to the Kansas City Chiefs latest depth chart, Leonard Pope is now the No. 1 tight end on the roster. He passed Sean Ryan, who was inactive in yesterday's 16-10 victory over the Oakland Raiders.

Pope has been more of a blocker than a receiver in his few games here. Yesterday he caught three passes for 11 yards in his first start for the Chiefs.

Will this change anything? Doubtful. The Chiefs haven't featured the tight end much in the last few games.

Savage demonted at punt returner

As expected, Dantrell Savage has been moved back to the second team punt returner. Bobby Wade is now No. 1.

Savage dropped a pass and fumbled a kickoff, which brought about some words with head coach Todd Haley as he walked off the field (CBS sure loves those shots).

After the jump, a few more interesting changes to the Chiefs depth chart as they prepare for the Pittsburgh Steelers.

Leggett ahead of Morgan at both safety spots

Does this tell you anything about what the coaching staff thought about DaJuan Morgan starting at free safety eight days ago?

Jon McGraw, back from injury, is on the first team at free safety followed by Leggett and then Morgan.

Leggett is also listed as Mike Brown's backup at strong safety.

Chambers officially opposite Bowe

After a two touchdown performance against the Jaguars, receiver Chris Chambers was still listed behind Bobby Wade on the depth chart. Today Chambers officially secures the starting nod.

This was more of a formality at this point, I think, since Wade was inactive the last two games.

Smith moves up

No surprise here. Kolby Smith is on the second team RB. Savage had a rough week, being surpassed at both running back and punt returner.

Smith carried the ball 9 times for 12 yards yesterday.

Five Things to Watch For in the Chiefs v. the Redskins

Chris Thorman — Sun, 18 Oct 2009 13:55:12 -0000

More photos » by Alex Brandon - AP

"As a first round pick out of Texas, I promise to under perform and to not exceed your expectations." (AP Photo/Alex Brandon)

Browse more photos »

Ah yes....Gameday!

Joel is headed to FedEx field as we speak to grab his credentials and plunker down in the press box for the Kansas City Chiefs v. the Washington Redskins today.

For those of us not as lucky to be attending the game in Washington, in the press box, I've put together five things that I'll be specifically watching during today's 12 PM Central time game.

To get you to click over and get you to read my brilliant ~~rambling~~ musings, here are a few teasers:

Tyson Jackson
Wade Smith at left tackle
Larry Johnson against a mediocre run defense
The emerging TE Sean Ryan
And the overall Chiefs attitude

Check 'em out, after the jump and let us know what's on your mind heading into today's game.

Tyson Jackson

A lot of the focus of the conversation has been on the offense around here. With new players on defense and a new scheme, I know I've been reluctant to into detail about how/why the Chiefs defense is playing like it's playing. Some of the struggles are the new scheme. Some of it is related to the players. And some of the struggles are because we've been playing solid opponents during the first quarter of the season.

Well today I'm going to take time to specifically watch the Chiefs first round pick DE Tyson Jackson. Like everyone has said, his position in the 3-4 defense isn't about getting his name called on TV or stats. It's about applying enough pressure by himself to lock up defenders and allow the linebackers to get penetration and stop running backs.

I'm going to be watching Jackson to see exactly how much attention he commands against an offense that ranks in the lower third of the NFL in the major categories.

Wade Smith at Left Tackle

Wade Smith gets the nod at left tackle after Branden Albert didn't make the trip to DC Maryland yesterday. Even though Smith hasn't played relatively much since becoming a Chief, I've always thought that he was on NFL rosters because he could played center, tackle and potentially even guard.

We'll see today just how versatile Wade Smith is and if the Chiefs have even bigger problems at o-line depth than we think they do.

TE Sean Ryan

Through Week 5, Ryan has 13 catches for 124 yards receiving. Traditionally, the tight end hasn't played much of a role in the Todd Haley led offense but it seems that Ryan may becoming a go-to guy for Matt Cassel.

Ryan is fourth on the team in receiving yards, trailing Bowe, Bradley and Wade respectively. We've been talking a lot about wide receiver depth around for say, oh, the last six months. Maybe Sean Ryan is another solid piece of the receiving game puzzle for KC?

Larry Johnson v. Redskins Defense

I'm sure you've heard by now that the 2009 Redskins are the only team to face six straight winless teams to open a season. That may be one of the most ridiculous stats I've ever read about in NFL football.

Partly because of the lack of talent they've faced, the Skins' defense ranks 6th in points allowed, 5th in yards allowed, 3rd in passing yards allowed but 22nd in rushing yards allowed. Hmmm. Something isn't right there and I hope LJ can take advantage of it.

The Redskins have given up103, 126, 154, 129 and 86 yards rushing respectively. The only rushing attack worthy of saying they're good is the Giants, who the Redskins played in Week 1.

Does Larry Johnson rush for over 100 yards today?

The Chiefs Attitude

The Redskins are falling apart. This is the first week that a lot of "experts" are picking the Chiefs to win. FedEx field provides no real home field advantage. Hell, it's not even in DC :)

It's tough to say the Chiefs should win this game. The Redskins are bad but so are we.

But if the Chiefs don't come out at least looking like they want to win this game and can win this game, I'm going to be angry. We have decent enough talent to beat the Redskins. It's going to come down to coaching. And we have the advantage there.

I think.

Will Todd Haley have the Chiefs fired up enough to get their first win, on the road no less?

Chiefs Third Down Woes: Play Calling, Penalties or Poor Play?

Chris Thorman — Tue, 13 Oct 2009 16:55:15 -0000

More photos » by Ed Zurga - AP

2 months ago: Kansas City Chiefs coach Todd Haley talks to an official during the second quarter of an NFL football game against the Dallas Cowboys Sunday, Oct. 11, 2009 in Kansas City, Mo. (AP Photo/Ed Zurga)

Browse more photos »

So we all know the Kansas City Chiefs have major troubles on third down. After Sunday's game, the Chiefs are now 14/68 on third down for a nice conversion rate of 20.6%. Sunday, the Chiefs were 5/17 on third downs for a conversation rate of 29%.

But, it's not like the Chiefs get to third down and inexplicably can't convert them just because it's the third play in a series. Logically speaking, it's first and second down that's hurting us the most. Especially when 8 of those 15 third downs had the Chiefs needing 10 or more yards to go for the first. And six of those actually required 15 or more yards for the first.

After the jump, I've gone over all of the Chiefs third downs they didn't convert (12 of them) to see if we can find a pattern of poor play, bad play calling, penalties or a combo of them all.

There's lots of room for debate on this one so I'm excited to see what you all have to say.

First Quarter

3rd and 11

How we got there: Mark Bradley lost two yards on a reverse and Larry Johnson only gained one yard on second down.

Verdict: Poor play calling

3rd and 3

How we got there: Jamaal Charles had a nice run for 7 yards on first down but Matt Cassel was sacked on second down. An incomplete pass to Bradley sealed the deal and the Chiefs punted.

Verdict: Poor play

Second Quarter

3rd and 15

How we got there: Larry Johnson lost six yards on first down and then only gained one yard on second down. Cassel's incomplete short pass to Sean Ryan virtually ended the series and Ryan Succop kicked his first field goal of the game.

Verdict: Poor play calling

3rd and 17

How we got there: This drive started out great with passes of 13 and 20 yards by Cassel to Sean Ryan and Dwayne Bowe respectively. A 7-yard loss on a Cassel sack and incomplete pass to Dwayne Bowe on second down put the Chiefs in a terrible third down position again.

Verdict: Poor play

3rd and 6

How we got there: What started as a solid drive at the end of the first half wound up stalling. After starting out at their own 12-yard line, the Chiefs faced 1st and 10 on their own 44-yard line. First down was an incomplete pass. Then a 15-yard pass to Sean Ryan was negated by a Brian Waters holding penalty. On 2nd and 20, Cassel hit Bradley for 14 yards. Third and six saw Cassel throw incomplete to Mark Bradley.

Verdict: Penalty

Third Quarter

3rd and 20

How we got there: The Chiefs got the ball back to start the half and only lasted five plays. After a nice first down 14-yard gain by Sean Ryan, Cassel's short pass to LJ fell incomplete on first down. Then, Cassel was sacked for a ten yard loss and yet again, the Chiefs faced third and long.

Verdict: Poor play

3rd and 3

How we got there: The final series of one of the Chiefs longest drives ended up well - with Ryan Succop putting three points on the board. On that final series, LJ rushed for two yards before two Cassel incompletions forced a punt. You can debate the merits of a pass on 3rd and short but let's face it - Larry wasn't getting that one.

Verdict: Poor play

3rd and 5

How we got there: With the ball on their own 33-yard line, LJ rushed for five yards; Cassel threw an incomplete pass to Sean Ryan on the play Branden Albert was injured on; and Cassel threw an incomplete pass to Bowe on 3rd and five.

Verdict: Poor play

Fourth Quarter

3rd and 22

How we got there: A long, long drive by the Chiefs starting with 11 minutes left in the game ended with Ryan Succop's 53-yard field goal being blocked. The final series went down like this: poor deep pass by Cassel in the direction of Bobby Wade; a Brian Waters false start; a 3-yard Jamaal Charles run; offensive pass interference on Dwayne Bowe made 3rd and 12 3rd and 22. Cassel hit Wade for a 9-yard gain but alas, it was way too short.

Verdict: Penalties

3rd and 7

How we got there: The Chiefs final drive of regulation ended with me jumping up and down yelling "Boooooooooooooowe!!!!!!" The final series of the ten play drive was uneventful aside from the TD. An incomplete pass to Bradley and a short gain by Charles gave the Chiefs 3rd and 7.

Verdict: Wash

Overtime

3rd and 15

How we got there: Cassel's 14-yard pass to Bradley on the first play of overtime got me so jacked up but I was completely deflated when Wade Smith was called for holding on the next play. A five yard run by Cassel made it 3rd and 15 which was not converted when D. Bowe caught a 10-yard pass to make it fourth down.

Verdict: Penalties

3rd and 9

How we got there: The Chiefs got that rare second chance in overtime to score but of course, they didn't. An incomplete pass and an LJ one yard run gave the Chiefs another third and long. Sorry Todd Haley. But at this point in the game, after seeing what we saw from the running game all day long, an LJ draw on second and 10 killed us.

Verdict: Poor play calling

So out of 12 third downs the Chiefs didn't convert, here's how I have the problems breaking down:

Penalties: 3
Poor play calling: 3
Poor play: 5

Thoughts on the why the Chiefs have issues with third downs? Do you feel that it's mainly one of these factors over the others? Or a combination?

Chiefs QB Cassel Compared to....Roethlisberger?

Joel Thorman — Mon, 12 Oct 2009 13:00:25 -0000

More photos » by Charlie Riedel - AP

2 months ago: Kansas City Chiefs quarterback Matt Cassel (7) recovers his own fumble as he is tackled by Dallas Cowboys defensive end Jay Ratliff during the fourth quarter of an NFL football game Sunday, Oct. 11, 2009 in Kansas City, Mo. Dallas won the game 26-20 in overtime. (AP Photo/Charlie Riedel)

Browse more photos »

In yesterday's 26-20 loss to the Dallas Cowboys, QB Matt Cassel was the second leading rusher (28) on the team, only nine yards behind leader Larry Johnson (37). His 4.0 average is better than the running back.

(And, on a side note, he still has some trouble sliding. He had a tendency to not slide but that's a whole different story.)

After the game, Cowboys nose tackle Jay Ratliff was asked about Cassel and his elusiveness.

"Yes, he might be as hard as [Pittsburgh Steelers quarterback Ben] Roethlisberger to bring down," Ratliff said. "He can create some time and make plays downfield and that’s what he did, so my hat’s off to him."At one point in the fourth quarter, Cassel had been hit by a Cowboys defender on 26 of 34 pass attempts. That includes four sacks.

"I'll have to look at the film," backup G/T Wade Smith said. "I know we wanted to keep him clean as much as possible. I'm sure he got hit but that's why he is who he is. He's going to still make plays and he's going to get up and make plays.

Despite the pass rush, a few players have noted how comfortable he looks back there, that includes Smith and tight end Sean Ryan, whose first two receptions went for first downs.

"I felt like he was comfortable all game," Ryan said after the game. If Ryan was lying, then he's got me fooled, but I agree with him. Cassel didn't look flustered despite the heavy pass rush. I mean, really, think about it. Getting hit on 26 of 34 pass attempts at one point? That's unbelievable.

"Obviously, there was a pretty good rush in his face," Ryan continued, "but he never stressed it. There were a couple of lineman that got hurt, and we were moving guys around, but he seemed calm all around."

Chiefs Players Impressed With Matt Cassel Despite Loss to the Cowboys

Joel Thorman — Sun, 11 Oct 2009 22:29:13 -0000

More photos » by Charlie Riedel - AP

Chiefs QB Matt Cassel under pressure in a 26-20 loss to the Cowboys. (AP Photo/Charlie Riedel)

Browse more photos »

Despite a 26-20 loss to the Dallas Cowboys, several Kansas City Chiefs players came away either impressed with Matt Cassel or assured that he's the guy they thought he was.

Cassel ended the overtime loss 23/41 for 253 yards and two touchdowns. He did not turn the ball over and nearly led all Chiefs with 28 yards rushing (Larry Johnson led the team with 37).

Following the Chiefs final drive in regulation, I told a reporter next to me that this is why Cassel was brought on board.

His stats weren't incredible on that last drive completing only four of eight passes, but there was just something about him. The poise and sense of calm could be felt behind a glass window in the press box.

Late in the game, 3rd and 14, pressure mounting, all eyes on the quarterback. Cassel dropped back and hit Bobby Wade across the middle for 36 yards and a huge, huge shift in confidence. Suddenly, the Chiefs actually had a shot at this thing. The next play, Dwayne Bowe jumped what seemed like five or six feet in the air and hauled in a 17 yard pass to put the Chiefs inside the 20 yard line.

It's a ball game again.

"Nothing he does surprises me," Chiefs TE Sean Ryan said. "Great athlete, great guy and he's the leader of our team. Whether he had butterflies on the inside, he didn't show anything on the outside. Everyone feeds off of that kinda stuff."

And feed off it they did as Cassel ended the drive with a 16 yard strike to Bowe for the game tying touchdown.

"That was a great drive for us," Cassel said after the game. "The offense did a great job, the receivers caught the ball, we moved the ball down the field, we were able to push the ball down the field in terms of throwing the ball.

"It was a great drive. It gave us an opportunity to win at the end, and that's all you can ask for in this type of game."

Color Wade Smith not surprised by Cassel's performance. For the leader of the team, as Smith says, this is what's expected of him.

"I don't think I learned anything. He just confirmed what we knew about him," he said. "He's our quarterback and our leader. That's pretty much it. What he did today didn't surprise me. I don't know if it surprised you all, but it didn't surprise me. That's what he's for."

Wade Smith agrees with me: That's why they brought Matt Cassel on board.

After Less Than a Week, Leonard Pope the Chiefs No. 2 Tight End

Joel Thorman — Mon, 05 Oct 2009 22:14:47 -0000

Since the loss of Tony Gonzalez, the Kansas City Chiefs have tried a handful of combinations at tight end. They signed one (Sean Ryan), released a few, drafted one (Jake O'Connell) and signed one off the street last week.

The one off the street, Leonard Pope, has in five days vaulted to the second tight end spot on the team behind Ryan.

Yes, folks, signed on Wednesday and threatening the No. 1 job by Monday. Impressive, isn't it? Well, maybe not.

Brad Cottam was inactive against the New York Giants and is now listed on the third team. O'Connell is behind him.

The rest of the changes are after the jump.

Kick returner

Jamaal Charles now the No. 1 kick returner ahead of Dantrell Savage which is interesting since he fumbled in last week's game (after repeated warnings from Todd Haley).

New players

David Herron takes the place of Monty Beisel on the third team ILB

Mike Richardson takes the place of Ricardo Colclough as third team RCB

Notable non-moves

Jovan Belcher is still behind Corey Mays at ILB.
Ryan O'Callaghan is still the No. 1 right tackle.
Gasp! There is no holder listed behind Dustin Colquitt.

Tomorrow is Transaction Tuesday so there's a good shot this won't be the final depth chart as the Dallas Cowboys come to town.

Great Fourth Quarter Makes the Chiefs' Loss to the Giants Respectable

Chris Thorman — Sun, 04 Oct 2009 20:15:59 -0000

More photos » by Charlie Riedel - AP

2 months ago: Kansas City Chiefs wide receiver Bobby Wade, left, catches a pass in the end zone for a touchdown while running back Jackie Battle (26) holds off a group of New York Giants defenders during the fourth quarter of a their NFL football game Sunday, Oct. 4, 2009, in Kansas City, Mo. The Giants won the game 27-16. (AP Photo/Charlie Riedel)

Browse more photos »

Chiefs lose, 27 to 16. Stats are here.

Well everyone, I'm glad the Chiefs at least closed the gap in the fourth quarter against the Giants. What was looking to be a blowout turned out to be a respectable showing by KC against a great Giants team.

Here are my quick post game thoughts. Chime in with your defensive and offensive MVPs in the comments.

The Good

Two turnovers by the defense. A fumble recovery caused by Tamba Hali and a Brandon Flowers INT off of a Giants WR Mario Manningham tipped pass were defensive highlights. Hali's strip and fumble were Derrick Thomas-esque.
CB Brandon Carr had some great plays deep in the secondary.
RB Larry Johnson ran with an attitude and energy we haven't seen in a while. He fell forward, broke tackles and looked sharper on his cuts than at any point this season.
RB Jamaal Charles had a 53-yard kick return in the fourth quarter.
LB Mike Vrabel played a great game IMO. He constantly made plays, even if they weren't recorded stats.
TE Sean Ryan came out of the four TE mix to have a fantastic game. One TD catch and led the team in receiving with 48 yards.
WR Bobby Wade had a great TD catch at the end of the game on a busted play. Matt Cassel made a heck of a pass to make that play too.

The Bad

The Chiefs had three fumbles. They only lost one of them but this is a continuing problem.
QB Matt Cassel had a couple of deep ball opportunities that he overthrew.
WR Dwayne Bowe had a couple of missed catches that could be considered drops.
I know the o-line has its issues but I felt like Matt Cassel held on to the ball too long on a few of the sacks.
LT Branden Albert continues to get spooked into penalties.
Matt Cassel didn't have any picks but he could have easily had two or three off of tipped passes.
Goal line play calling was off IMO. Too many passes, not enough runs.
The Chiefs offensive line was again inconsistent. Not as bad as last week but not good either. They're improving, which is why they're in the Bad list and not the Ugly list.

The Ugly

RB Jamaal Charles fumbled on the opening kick off, setting a terrible tone for the rest of the game. His inability to hold on to the football is becoming a huge liability.
The passing game was atrocious for most of the game, except for the fourth quarter. Cassel ended up going 15/32 for 127 yards and two fourth quarter TD passes.
The post halftime onside kick was too risky of a call. Straight out of a video game.

Give us your defensive and offensive MVPs for the Chiefs in the comments. I'm choosing Sean Ryan and Brandon Carr. We'll have more for you later.

Poll

Grade the Chiefs overall performance today.

A

4 votes

B

27 votes

C

261 votes

D

483 votes

F

250 votes

1025 votes | Poll has closed