Wanna talk about the chop block?

kirbee

Jolly Good Fellow
Joined
Aug 7, 2002
Messages
1,977
I'm not the run of the mill blame the refs guy, nor do I think all refs always suck. However, I rewound that play where chop block was called several times and was mystified. I saw our OL fire out low, which happens every play. That's not a chop block. A chop block is when a player is engaged high and another player takes the legs out. I didn't see it anywhere. Did you?

That really was a huge call because Tech was chewing up chunks of yardage and if Tech scores on that drive it changes everything.
 
I'm not the run of the mill blame the refs guy, nor do I think all refs always suck. However, I rewound that play where chop block was called several times and was mystified. I saw our OL fire out low, which happens every play. That's not a chop block. A chop block is when a player is engaged high and another player takes the legs out. I didn't see it anywhere. Did you?

That really was a huge call because Tech was chewing up chunks of yardage and if Tech scores on that drive it changes everything.

I haven't rewatched the play but I think the rule can be interpreted that a cut block to an already engaged defender (regardless of high or low) can be called a chop block.
 
CPJ was giving the ref an earful after that call. Lots of &*)@#$ before he said something to the effect of that was not a chop block. He was ticked. CPJ is pretty good at blaming the right person on a call. If it's his player, then he will get in their face and he does the same for a ref.
 
Kirbee, I'm not sure I would know a chop block if it came up and bit me on the arse, but I will say this: a good case could be made for that being the single biggest play of the game. At least as far as a momentum killer. We were really rolling before that play, if I remember correctly, and we didn't do much right for the rest of the game after that call. No telling how much difference it would have made if that call isn't made.
 
At the touchdown club today CPJ said he was still looking for that chop block on the tape. He said the refs were yapping about it before the game so he knew they were going to call it - just a matter of when.

He said that call was one of the two biggest turning points in the game. The other of course being the fumbled punt.
 
I still think the fumbled punt was the turning point in that game.

It doesn't mean the call was correct though. ACC refs, putting the ACC in Another Crappy Call.
 
At that exact point, I wrote here (during the game) that the North Carolina Conference Refs just went into action. They make that call just as Tech is starting to show some strength. Amazing.
 
On the next play the refs called a holding and Dwyer was hit 10 yards out of bounds at the end of the play. He was so far out of bounds that he was past the white out of bounds area when he was hit. That holding call should have been offset by the out of bounds hit.
 
I still think the fumbled punt was the turning point in that game.

It doesn't mean the call was correct though. ACC refs, putting the ACC in Another Crappy Call.


HA!

The fumbled punt was BECAUSE of that ACC call!!! It negated a big gain for us!

When is this **** going to end!?!?!?!?!
 
I hope Drad really gets onto the ACC about this in the offseason. The bad thing about this block technique is that no one else uses it, so the refs aren't use to seeing it. The refs are just seeing a guy go low and are assuming its a chop block.
 
Another thing CPJ mentioned today was that he is going to be giving a presentation to the ACC refs in the off-season in his blocking technique/scheme vs. the chop block.

He was serious.
 
Let me ask if I remember correctly

Without the chop block call we have the ball around the 15-17, first down. With the chop block and the holding call on the next play we end up punting from midfield? Or did we lose it on a turnover then?
 
At the touchdown club today CPJ said he was still looking for that chop block on the tape. He said the refs were yapping about it before the game so he knew they were going to call it - just a matter of when.

He said that call was one of the two biggest turning points in the game. The other of course being the fumbled punt.

Yeah, that's what I thought.

Can we get some refs to maybe yap about the holding against our DL then? I'm guessing Derrick Morgan probably has a permanent mark around his neck from all the hooking he gets.

Off topic: Who's going to return punts now? Any know if there are any Rhino's anywhere with eligibility?
 
Re: Let me ask if I remember correctly

Without the chop block call we have the ball around the 15-17, first down. With the chop block and the holding call on the next play we end up punting from midfield? Or did we lose it on a turnover then?

It was the pooch punt from FG formation where the coverage stopped running at the 10 yard line instead of going to the goal line to stop the ball. NC went 3 and out and then Jones fumbled the punt and it was over.
 
i finally found it!

here it is, it was on sale at ACCrefscantsee.com

choppingblock.jpg


CPJ should send one of these to every ACC ref in the off-season!
 
Re: Let me ask if I remember correctly

Without the chop block call we have the ball around the 15-17, first down. With the chop block and the holding call on the next play we end up punting from midfield? Or did we lose it on a turnover then?

We had to punt due to the crap call.

Then we hold them to 3 and out

Then roddy fumbled the punt.

Game.
 
I'm not the run of the mill blame the refs guy, nor do I think all refs always suck. However, I rewound that play where chop block was called several times and was mystified. I saw our OL fire out low, which happens every play. That's not a chop block. A chop block is when a player is engaged high and another player takes the legs out. I didn't see it anywhere. Did you?

That really was a huge call because Tech was chewing up chunks of yardage and if Tech scores on that drive it changes everything.

I watched it in slow motion several times yesterday and couldn't find it. Also, on the next play, they called CE for holding when the NC db pulled CE's jersey as the db was going down. And then they totally ignored the late hit on Dwyer.

Worst case, they penalize us for holding back to the 50, and penalize NC 15 to the NC35 and it's 1st and 10.:mad:
 
I haven't rewatched the play but I think the rule can be interpreted that a cut block to an already engaged defender (regardless of high or low) can be called a chop block.
No, the rule is pretty clear and it's high and low.
 
Back
Top