LB3 Posted October 4, 2015 Posted October 4, 2015 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. It was a legal play by Ingognito. End of story. Bad call.
Acantha Posted October 4, 2015 Posted October 4, 2015 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. That wasn't a planned block that was in the game plan, it was a double team after the initial block.
Wayne Cubed Posted October 4, 2015 Posted October 4, 2015 (edited) It was a legal play by Ingognito. End of story. Bad call. Except it wasn't. He went low and there was absolutely no reason for him to do it. Edited October 4, 2015 by Wayne Cubed
Bills Fan of St Augustine Posted October 4, 2015 Posted October 4, 2015 Crap call and not the only one. Nothing wrong with RI trying to legally hit someone. This is still football right? His hit was lower ribs to waist. Not even close to a "chop" at a players unprotected legs. BS call. So was the hold on Darby among others.
Acantha Posted October 4, 2015 Posted October 4, 2015 Except it wasn't. He went low and there was absolutely no reason for him to do it. I'll ask you the same question I asked someone else and didn't get an answer. What is the highest point a player can hit and be considered "low" in your definition?
Bills Fan of St Augustine Posted October 4, 2015 Posted October 4, 2015 Except it wasn't. He went low and there was absolutely no reason for him to do it. Sorry Shell Fish, he was above the waist all day long. Terrible, terrible call.
Lurker Posted October 4, 2015 Posted October 4, 2015 Another look: https://pbs.twimg.com/tweet_video/CQgFuQNWoAAYWgT.mp4 The flag was thrown by the referee standing ten yards behind Tyrod. His angle and sightline was bad, but he 'intuited' Richie's intention to go low. Psychic officiating at it's best...
Acantha Posted October 4, 2015 Posted October 4, 2015 Replay showed the play from the other direction. Much better angle.
LB3 Posted October 4, 2015 Posted October 4, 2015 Except it wasn't. He went low and there was absolutely no reason for him to do it. Except it was. He hit him at the waist. It wasn't low.
MDH Posted October 4, 2015 Posted October 4, 2015 So should he just stand around playing thumbs reverse? No, but he can engage him up top so there isn't even a question. Why dive at his hips? I agree, it wasn't a good call when seen via replay but when you dive towards a player and you end up at their feet there's a decent chance a flag will fly on that.
Bills Fan of St Augustine Posted October 4, 2015 Posted October 4, 2015 How can anyone make a case this is a "chop" block thrown at the player's legs?!
Wayne Cubed Posted October 4, 2015 Posted October 4, 2015 (edited) Except it was. He hit him at the waist. It wasn't low. Sorry Shell Fish, he was above the waist all day long. Terrible, terrible call. I'll ask you the same question I asked someone else and didn't get an answer. What is the highest point a player can hit and be considered "low" in your definition? What you all fail to realize is that he engaged the player that was already being blocked BELOW the player that was already blocking him. The league has made a POINT this year to make those calls to protect the DL Incognito PURPOSEFULLY went low on the block. He was absolutely dumb for doing it. That will get flagged EVERY time. Edited October 4, 2015 by Wayne Cubed
Nuncha Posted October 4, 2015 Posted October 4, 2015 This. X1000. And he never learns.... Rex is going to be his dumb self and won't change. All he is good for is running his mouth.
Acantha Posted October 4, 2015 Posted October 4, 2015 What you all fail to realize is that he engaged the player that was already being blocked BELOW the player that was already blocking him. The league has made a POINT this year to make those calls to protect the DL Incognito PURPOSEFULLY went low on the block. He was absolutely dumb for doing it. That will get flagged EVERY time. That has NOTHING to do with the rule!
LB3 Posted October 4, 2015 Posted October 4, 2015 (edited) What you all fail to realize is that he engaged the player that was already being blocked BELOW the player that was already blocking him. The league has made a POINT this year to make those calls to protect the DL Incognito PURPOSEFULLY went low on the block. He was absolutely dumb for doing it. That will get flagged EVERY time. There has been emphasis on ILLEGAL blocks. This wasn't illegal. It was well within the rules. Edited October 4, 2015 by LBSeeBallLBGetBall
Perry Turtle Posted October 4, 2015 Posted October 4, 2015 That wasn't a planned block that was in the game plan, it was a double team after the initial block. Right. They need to be coached up that engaging a pass rusher who is already engaged with another offensive lineman could result in a 15 yard penalty, regardless if they hit the rusher high or low. It's a crap shoot due to the way the refs are calling it on the field. Just like lineman are coached on what a ref will call when it comes to holding or blocks in the back, they have to be coached up on this too.
justnzane Posted October 4, 2015 Posted October 4, 2015 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. I don't know what anyone else is talking about. The initial contact was above the waist, thus it was legal and 7 points were stolen from us. That crew today did an injustice to the game with some really crappy calls both ways, and led to the outbursts of emotion from certain Bills. That said, Rex needs to control these boys. The NFL has a big problem with the game taking too long. Games scheduled on TV are taking longer due to more penalties and rule changes to protect the player forcing the game to be more pass dependent. Thus there are more stoppages due to penalties and incompletions which slow down the game more than a bad soccer match. If the NFL is trying to sell the game to other countries, it has to make it faster pace, thus more contact allowed on defense in the passing game and having an off field official to help expedite penalty decisions (or even communications between officials via headset).
MDH Posted October 4, 2015 Posted October 4, 2015 How can anyone make a case this is a "chop" block thrown at the player's legs?! I can easily see the flag being throw if a ref (who is watching more than just Cog) seeing a guy dive towards a player's midsection and ends up at his feet. Sure, it's not the right call (particularly when you watch the replay) but the refs have to make bang bang decisions and it's easy to nitpick things watching a replay in slow motion. Just engage him up top and don't give the ref a chance to throw the flag.
Acantha Posted October 4, 2015 Posted October 4, 2015 I can easily see the flag being throw if a ref (who is watching more than just Cog) seeing a guy dive towards a player's midsection and ends up at his feet. Sure, it's not the right call (particularly when you watch the replay) but the refs have to make bang bang decisions and it's easy to nitpick things watching a replay in slow motion. Just engage him up top and don't give the ref a chance to throw the flag. Yeah, Incognito is stupid. He just needs to make sure his block are the really mostest legal that he can make them!
Recommended Posts