clock menu more-arrow no yes mobile

Filed under:

49ers vs. Chiefs breakdown: How to kill a drive with penalties, sacks

Penalties and sacks can kill a drive, regardless of how promising. It happened on Sunday against the Kansas City Chiefs, and we've got the GIFs to prove it.

Ezra Shaw

The second half is barely underway, the Kansas City Chiefs have just taken a 17-13 lead on the back of an Alex Smith touchdown pass and the San Francisco 49ers are looking to get it back sooner rather than later. There's 11:56 on the clock in the third quarter and responding with a touchdown would be the best scenario.

Of course, things rarely work out with the ideal situation. The 49ers started off that drive in normal fashion -- a failed screen play to running back Frank Gore -- but from there it started to look pretty positive. Gains of 18, 16, 9 and 13 yards set the 49ers up in the red zone.

It's there that San Francisco committed its first offensive penalty and allowed its first two offensive sacks. After driving close to 60 yards, the 49ers quickly lost nine of them and faced a 4th and 24 situation. Needless to say, they didn't end that drive with the lead, though Phil Dawson did manage to hit a 52-yard field goal to bring the score to 17-16.

Since two of the 49ers' three allowed sacks came on this drive, I thought it might be cool if I instead just took a look at the drive and how it eventually broke down. The third sack I'll cover in a GIF dump on Wednesday. Whatever the case, here we go:

1st and 10 at SF 23: Kaepernick pass to Gore for 1 yard

Play 01 (Failed Screen)

Let's get this out there in the open: nobody is surprised that the 49ers failed to get anything done on a screen pass. It technically went for negative yardage, but very little about this play looked good. From Gore having a tendency to cut inside to the blockers not realizing this tendency, it simply didn't work. The 49ers are not good at running screens. This is a fact of life.

2nd and 9 at SF 24: Kaepernick pass to Boldin for 18 yards

Play 02 (Boldin Catch)

This is a solid play for many reasons. The most obvious of which, to me, is that you can clearly see Colin Kaepernick moving through his reads before settling on wide receiver Anquan Boldin. The offensive line is blocking well -- well enough for Kaepernick to step up into his throw -- and Boldin is well-covered, but that rarely matters. Just a solid play that the Chiefs couldn't do much to prevent.

1st and 10 at SF 42: Kaepernick pass to Crabtree for 16 yards

Play 03 (Crabtree Catch)

This was wide receiver Michael Crabtree's lone reception of the game, but he certainly made the most of it. I love watching Crabtree with the ball in his hands, and he picks up another 7 yards or so making the Chiefs look a little silly. The offensive line, once again, blocked pretty well for Kaepernick, sealing off the left side by design and allowing Kaepernick to throw it to Crabtree as he breaks back on his route. It worked exactly as it was drawn up, it seems.

1st and 10 at KC 42: Gore rush for 9 yards

Play 04 (Gore Run)

I have good news for everyone here: Mike Iupati is still good at running into fools really hard. Some were starting to doubt this given that he has been a liability in pass protection, but Iupati pulls out and leads the way on this run. Interestingly enough, Iupati doesn't actually collide with anybody right away, but he is sealing off the edge, even if that just entails scaring the crap out of Dee Ford, No. 55 on the Chiefs. Look at that guy run away, man.

2nd and 1 at KC 33: Gore rush for 13 yards

Play 05 (Gore Run)

Iupati gets through again on this run, but it's fullback Bruce Miller who I should have mentioned in the flavor text on the GIF. Miller collides hard with the guy trying to break through the right side of the line, and the block allows Gore to continue up the left side where he wanted to go. Most-importantly: Gore makes it to the 20-yard line and the 49ers are officially in the red zone.

1st and 10 at KC 20: False Start penalty on Iupati

Then this happens. The 49ers committed just two penalties on the day (three, but one was declined) with one being the customary neutral zone infraction on outside linebacker Ahmad Brooks. This one was a false start call on Iupati, which I didn't GIF because ... why would I? Suffice to say it's pretty clear there's a tad bit of movement on that side, and that's enough.

Maybe this is exactly what the Chiefs needed. The 49ers were driving and simply getting a second to collect your thoughts can be huge in any situation. Maybe the Chiefs coaches needed that little bit of extra time to draw up these next plays. I don't know -- all I know is penalties sinking drives isn't something new in the NFL. For the "sunk drive" portion of the post, continue on.

1st and 15 at KC 25: Kaepernick sacked for -2 yards

Play 06 (Sack 01)

This one is pretty ugly, for the fact that left tackle Joe Staley seems to have his guy pretty solidly stopped for the most part, then the guy pulls a move at the last second that sends Kaepernick scrambling. Kaepernick got away slowly, which sucks, and it was enough for Jonathan Martin's guy to get a hold of Kaepernick from behind and get the sack. The play is pretty clearly on Staley and Martin, though Kaepernick didn't exactly show stellar pocket presence.

2nd and 17 at KC 27: Kaepernick rush for -2 yards

Play 07 (Designed Run)

I'm all for designed runs for Kaepernick at this point. He's proven effective running them, especially when it's a well-designed play. I do not believe this one is a well-designed play. I don't think this is an option play, for the record, I think he's supposed to run it here. But I also think everyone else on the play isn't totally clear on what they're supposed to be doing. Everyone on the right side -- the side Kaepernick runs to -- doesn't really do anything and the play just goes nowhere. Greg Roman has to do better than that with his play design.

3rd and 19 at KC 29: Kaepernick sacked for -5 yards

Play 08 (Sack 02)

Alex Boone got annihilated on this play. Dontari Poe took Boone and tossed him aside like a small child. Unfortunately, this seems to happen once per game with all offensive linemen outside of center Daniel Kilgore, which is odd. Boone turns back and watches Poe get to Kaepernick and can do nothing about it. Just brutal.

Play 08 (Sack 02) 02

Oh did you guys want to see more? Sorry for the slight pause, the broadcast paused for awhile there and I did what I could with the angle. But man ... look at this play. Look at it.

4th and 24 at KC 34: Dawson field goal is good from 52 yards

Remember in Week 1 when Dawson missed a field goal and 49ers fans started to panic? I don't blame anybody given that David Akers suffered a collapse that was impressively massive when in San Francisco. But Dawson was automatic in Week 5, kicking field goals of 31, 55, 52, 27 and 30 yards. This one was from 52 yards and it pulled the 49ers within one point of the Chiefs. He would go on to kick two more, to win the game.