Chiefs Vs. Bills Game Recap: Buffalo Gets 1st Win With 35-17 Blowout Of KC

After an ugly opener against the Jets, the Buffalo Bills responded in a big way on Sunday with a 35-17 Week 2 thrashing of the Kansas City Chiefs. The Bills offense was bruised and battered in New York, but Ryan Fitzpatrick and running back C.J. Spiller, filling in for the injured Fred Jackson, jumped all over the KC defense and pushed Buffalo to a three-touchdown lead at the half. The Bills defense would keep the Chiefs out of the end zone until the final six minutes, and the rout was on early in the second half.

Spiller started things off with the first two touchdowns of the day, bursting up the seam and off left tackle for a 17-yard score -- the only touchdown of the first quarter after a sluggish start to the game. He'd scamper in for his second touchdown just three minutes into the second quarter, taking a quick toss from Fitzpatrick, who was in the shotgun. The lighting-quick back out of Clemson immediately went toward the left pylon and cut it up with his lineman wiping out Chiefs corner Javier Arenas on the outside.

With less than five minutes in the half, Fitzpatrick would get in on the act for his first touchdown pass of the day, connecting with tight end Scott Chandler in the middle of the field. It was an easy pitch-and-catch, with Chandler beating safety Abram Elam.

The Chiefs finally ended the shutout when Ryan Succop connected on a 33-yard field goal, but the Bills would promptly ensure that no thoughts of a second-half comeback would be entertained. With the ball on their own 20, the Bills called for a designed rollout. Fitzpatrick went to his right with tight end Chandler coming across the field with him. The Bills QB hit Chandler in stride, and the tight end cut it up the right sideline for a 43-yard pickup, moving Buffalo across midfield. Two plays later, Fitzpatrick hit Stevie Johnson in the middle of the field and the speedy wideout gashed the center of the Chiefs secondary for a 41-yard touchdown. An animated gif of the score:


The Chiefs' woes would also extend to special teams, as Buffalo made it academic when Leodis McKelvin took a Dustin Colquitt punt 88 yards for another touchdown to make it 35-3 in the third.

Kansas City finally got on the board with a garbage-time touchdown, as Cassel hit Dwyane Bowe down the right sideline for a 33-yard touchdown. It was much too little and way too late, as the Bills took to the ground to salt the game away.

Fantasy Stud

Fred Jackson was inactive after sustaining an MCL injury last week against the Jets. But the explosive Spiller was there to pick up the slack, rushing 15 times for 123 yards and the first two touchdowns of the game.

Fantasy Dud

The Chiefs got down three touchdowns early, forcing the offense to try and come back through the air. The running game suffered, and Jamaal Charles, who was nursing an injury, rushed six times for just three yards.

Did They Cover?

The Bills entered the game as three-point favorites, and they easily covered.

What's Next?

The Bills will hit the road for what has become an annual game against the Browns. The Chiefs will stay on the road and face the Saints in the Superdome -- a clash between two teams looking for their first win.

Stay tuned to this StoryStream for more NFL highlights. Check out Buffalo Rumblings for more on the Bills big day and visit Arrowhead Pride of more on the Chiefs.

Check out the SB Nation Channel on YouTube

Log In Sign Up

Log In Sign Up

Forgot password?

We'll email you a reset link.

If you signed up using a 3rd party account like Facebook or Twitter, please login with it instead.

Forgot password?

Try another email?

Almost done,

By becoming a registered user, you are also agreeing to our Terms and confirming that you have read our Privacy Policy.


You must be a member of to participate.

We have our own Community Guidelines at You should read them.


You must be a member of to participate.

We have our own Community Guidelines at You should read them.




Choose an available username to complete sign up.

In order to provide our users with a better overall experience, we ask for more information from Facebook when using it to login so that we can learn more about our audience and provide you with the best possible experience. We do not store specific user data and the sharing of it is not required to login with Facebook.