Jump to content

The Chop Block Rule


Recommended Posts

From the NFL rule book:

 

A chop block is a foul by the offense in which one offensive player (designated as A1 for purposes of this rule) blocks a defensive player in the area of the thigh or lower while another offensive player (A2) occupies that same defensive player in one of the circumstances described in subsections (1) through (10) below.

 

The penalty on Incognito was not a penalty.

Link to comment
Share on other sites

  • Replies 119
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

From the NFL rule book:

 

A chop block is a foul by the offense in which one offensive player (designated as A1 for purposes of this rule) blocks a defensive player in the area of the thigh or lower while another offensive player (A2) occupies that same defensive player in one of the circumstances described in subsections (1) through (10) below.

 

The penalty on Incognito was not a penalty.

 

It was a bad call!

 

@MikePereira

#NYGvsBUF To me, it's at the waist. It has to be at the thigh or blow, I don't think it's a chop block. #NFLonFOX

 

@PrescottRossi

ChopBlock: 2nd OL engages defender "in area of waist". Initial contact @ waist-borderline. IMO push to thigh got him https://vine.co/v/e2iWOr20g2l

Link to comment
Share on other sites

That rule was put in place to stop the increasing incidences of guys getting their legs cut from the side. It was turning into an epidemic and they finally made it a point of emphasis to protect the DL's legs. Not in a month of Sundays did I ever think I'd see some jackwagon interpret it from the ribs down.

Link to comment
Share on other sites

From the NFL rule book:

 

A chop block is a foul by the offense in which one offensive player (designated as A1 for purposes of this rule) blocks a defensive player in the area of the thigh or lower while another offensive player (A2) occupies that same defensive player in one of the circumstances described in subsections (1) through (10) below.

 

The penalty on Incognito was not a penalty.

agreed...and i did not think it was close...and the Bills will get an apoolgy and still have a loss

Edited by plenzmd1
Link to comment
Share on other sites

This penalty has not been called correctly all season. The refs are calling it tighter than the rulebook, and it's not reviewable to make sure they got it right. Coaches should know this, especially Buffalo's staff because Clay was called for a WTF chop block in week 1.

 

To be safe, teams should consider this blocking technique to be dead. It's a penalty risk every time it happens, regardless if it executed correctly (according to the rule book) or not.

Link to comment
Share on other sites

Another crew headed by a rookie referee. I can't recall so many marginal or inconsistent calls (one series they let the dbs be physical, the next they're calling it the exact opposite way). At least four clearly blown calls made by guys in no position to throw that flag.

 

The London game this morning was just as bad (23 penalties for 240+ yards). Hard to "sell the NFL" to a foreign and/or younger audience if they're going to make it flag football and 50+ FanDual / Draft Kings commercials...

Link to comment
Share on other sites

This penalty has not been called correctly all season. The refs are calling it tighter than the rulebook, and it's not reviewable to make sure they got it right. Coaches should know this, especially Buffalo's staff because Clay was called for a WTF chop block in week 1.

 

To be safe, teams should consider this blocking technique to be dead. It's a penalty risk every time it happens, regardless if it executed correctly (according to the rule book) or not.

MOST teams should consider this blocking technique to be dead. Some will still be able to get away with it.
Link to comment
Share on other sites

It was a penalty. He was trying to go low.

No, he was trying to send the message that he could go low at any time he wanted because there had been some liberties being taken with guys legs shortly before that.

He knew exactly what he was doing and made sure the block was legal but still got a point across.

This league has been chock-full of over-officious jerks for a few years now and it looks like it's finally coming to a head.

Link to comment
Share on other sites

It was a penalty and a stupid one. Didn't do anything in terms of buying TT more time. Wasn't even worth the risk

What is wrong about a double team? That is what it looked like to me. BTW,you can search and search and never find me blaming the refs..and i am not saying Bills win the game if this call is not called. Just think this was the wrong call

Link to comment
Share on other sites

No, he was trying to send the message that he could go low at any time he wanted because there had been some liberties being taken with guys legs shortly before that.

He knew exactly what he was doing and made sure the block was legal but still got a point across.

This league has been chock-full of over-officious jerks for a few years now and it looks like it's finally coming to a head.

 

Even if that is what he was doing, which I highly doubt, why do it? It didn't have any effect on the play and didn't buy TT more time. How does showing the league that the refs are jerks help the Bills? It was a dumb play by Ingognito.

Edited by Wayne Cubed
Link to comment
Share on other sites

Problem was there was no need for RI to even touch the guy.

From the game thread so I don't have to re-type it:

 

I said it earlier and I'll say it again, when you have an athletic QB that runs like TT does, there is no time that you shouldn't be looking around for a block. Yes, it ended up being unnecessary, but Incognito doesn't know that at the time. For all he knows, the play is breaking down behind him and TT is getting ready to run. He isn't engaged so he finds the nearest guy and engages, LEGALLY. It was good play and is what everyone on that OL should be doing.

 

Edited by Acantha
Link to comment
Share on other sites

×
×
  • Create New...