Sports News Without Access, Favor, Or Discretion

Bruce Arians Can't Wait For NFL's "All Bullshit" Explanation Of Controversial Blocked FG

Rick Scuteri/AP Images

Please do not drink the Flavor Aid and let anyone tell you last night’s game—at 6-6, the lowest-scoring tie since the NFL introduced overtime in 1974—was “good” or “watchable” or “a better use of your time than going to sleep early and starting the week rested.” Special-teams incompetence, an Arizona offense that couldn’t do anything against a gassed Seahawks defense (which was on the field for a comical 46:21 because Seattle’s offense was even worse), and punts, punts, punts! (Fifteen punts! More punts than points!)—That was not enjoyable football. Had that not been Cardinals-Seahawks—had it been, say, Jaguars-Titans in a Thursday game—there’d be congressional inquiries on what’s wrong with the NFL. Oh look! Jaguars-Titans is this week’s Thursday game. The NFL hates you.


And because I hate you just as much, let’s revisit last night’s stinkbomb through everybody’s favorite lens: that of rulebook minutiae!

Let’s go back, way back to early in the second quarter, before you started longing for death, before you realized you were already dead and in hell, to Seattle’s blocked field goal. It looked like a beauty of a block: Seahawks LB Bobby Wagner got a head of steam and leapt up and over long snapper Aaron Brewer to get a hand on the Chandler Catanzaro kick.

(Pay special attention to the slow-motion replay beginning at 0:34. Wagner’s left foot appears to tap or drag across Brewer’s back.)


A penalty flag was thrown on the play, then picked up by the officials. Cardinals coach Bruce Arians then threw his challenge flag, but the thing he wanted to review (we’ll get to that) was not reviewable, so Arizona was charged a timeout, one they really could have used at the end of the half.

The penalty flag, Arians would later learn, was because officials thought Wagner might have lined up too close to the long snapper. From the NFL rulebook,

When Team A presents a field goal or Try Kick formation:

(1) A Team B player, who is within one yard of the line of scrimmage, must have his entire body outside the snapper’s shoulder pads at the snap.


The officials correctly ruled that Wagner wasn’t within a yard of the line of scrimmage, so no foul.

But that wasn’t what Arians thought the penalty was. He thought, like most of us did, that you can’t leap over a blocking player unless you hurdle him completely untouched. Wagner definitely appeared to touch Brewer, though he claimed otherwise. “I didn’t touch him,” Wagner said. “So I knew I was good.” (Brewer said he felt “something” on his back during the play.)


But is touching enough for a penalty? Here’s what the rule, 12.3.1.(s), actually prohibits:

(s) Running forward and leaping in an obvious attempt to block a field goal or Try Kick and landing on players, unless the leaping player was originally lined up on the line of scrimmage when the ball was snapped.


“Landing” is not “touching.” But where’s the line between the two? That’s a judgment call. And like all judgment calls, it is not subject to review. Arians learned that the hard way. He threw his challenge flag, believing the officials had missed the contact, and ended up forfeiting a timeout on a play that wasn’t legally reviewable.

Confused? Don’t you love football? Arians was confused, and pissed:

“He touched him,” Arians said. “You saw it. Did you see it? Didn’t he touch him? Yeah, he sure did. It sure looked like it to me, but it was not ruled that way, same with the last one. He definitely touched him.

“I’m sure I’ll talk to the league and we’ll get some kind of explanation that is all bullshit, like normal.”


Share This Story

Get our newsletter

About the author