The Official Forum  

Go Back   The Official Forum > Football
Register FAQ Community Calendar Today's Posts Search

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old Wed May 27, 2009, 10:08pm
Official Forum Member
 
Join Date: Jan 2009
Posts: 79
Took 7 months for me to ask??

During a game, our OL doubled the DT. In the process of this, one of our lineman slips and unintentionally hit the already engaged DT in the knee area. A plenalty was thrown, but when we asked the white hat who threw the flag what happened, he said the line man slipped and unintentionally hit the kid. Is this still a flag? Thanks
Reply With Quote
  #2 (permalink)  
Old Wed May 27, 2009, 10:52pm
Official Forum Member
 
Join Date: Aug 2004
Location: Randolph, NJ
Posts: 1,936
Send a message via Yahoo to waltjp
Was your OL already contacting the defender when he slipped or did he slip during his charge resulting in his initial contact being with the defender's knee? If it was the latter I say it's a good flag. Safety trumps slipping.
__________________
I got a fever! And the only prescription.. is more cowbell!
Reply With Quote
  #3 (permalink)  
Old Thu May 28, 2009, 06:44am
Official Forum Member
 
Join Date: Jul 2004
Location: NE Ohio
Posts: 7,620
Quote:
Originally Posted by Rule 2-3-8
Chop block is a delayed block at the knees or below against an
opponent who is in contact with a teammate of the blocker in the free-blocking
zone.
Nothing in there about intent, so an "accidental" chop block is still a chop block.
__________________
Cheers,
mb
Reply With Quote
  #4 (permalink)  
Old Thu May 28, 2009, 09:22am
Official Forum Member
 
Join Date: Mar 2008
Posts: 1,593
Quote:
Originally Posted by mbyron View Post
Nothing in there about intent, so an "accidental" chop block is still a chop block.
Like so many things we see in a football game, you have to actually see what happened to determine whether it was legal or not. The "Chop Block" definition does not mention intent, but it does require there has to be a "block", which doesn't necessarily include any type of contact.

Football players bump into each other all over a football field in ways that never quite make to the level of being a "block". So although a "chop BLOCK", may always be a chop BLOCK, that doesn't mean every contact between two players constitutes being a "block" of any sort.

Thjat's why it's so important that we see the entire action, not just the tail end of it. From the way this situation was described, it sounds like the White Hat's internal review system overruled his initial response and he corrected himself, which is not necessarily a bad thing.
Reply With Quote
  #5 (permalink)  
Old Thu May 28, 2009, 10:21am
Chain of Fools
 
Join Date: Jan 2005
Posts: 1,648
If I accidentally clip you, its still a clip. If I accidentally jump the snap count, its still a false start.

Some fouls don't have mitigating factors. Sounds more like he was letting the coach know so as not to chew his player's butt for the foul, as much.
Reply With Quote
  #6 (permalink)  
Old Thu May 28, 2009, 12:58pm
Official Forum Member
 
Join Date: Aug 2000
Posts: 14,616
Quote:
Originally Posted by TrojanHorse View Post
During a game, our OL doubled the DT. In the process of this, one of our lineman slips and unintentionally hit the already engaged DT in the knee area. A plenalty was thrown, but when we asked the white hat who threw the flag what happened, he said the line man slipped and unintentionally hit the kid. Is this still a flag? Thanks
It makes no difference whether it was intentional or not, the defender could have still been injured: which is why the rule exists. Flag.
__________________
"...as cool as the other side of the pillow." - Stuart Scott

"You should never be proud of doing the right thing." - Dean Smith
Reply With Quote
  #7 (permalink)  
Old Thu May 28, 2009, 01:18pm
Official Forum Member
 
Join Date: Mar 2008
Posts: 1,593
Quote:
Originally Posted by BktBallRef View Post
It makes no difference whether it was intentional or not, the defender could have still been injured: which is why the rule exists. Flag.
Gentlemen, with all due respect, acknlowledging and agreeing that a "clip" is always a "clip" and a "chop block" is always a "chop block", does NOT mean that every type of contact, including that which may be incidental, forced or otherwise not measuring up to the definition of a "block", with an opponents lower extremities, is automatically either a clip or a chop block, nor automatically, merits a flag.

One of the most basic and overriding aspects of officiating is that one should see the entire action to determne if any mitigating circumstances might have been in play that would prevent the action from being designated as a foul.
Reply With Quote
  #8 (permalink)  
Old Thu May 28, 2009, 02:37pm
Official Forum Member
 
Join Date: Jan 2009
Posts: 79
That's why I pose the question. I never argued the fact that a penalty was called, but I asked because the white had called a chop, but then told me it was accidental because he said the player was going to drive the DT up the field, he lost his footing and blocked below the waist.
Reply With Quote
  #9 (permalink)  
Old Thu May 28, 2009, 03:33pm
Official Forum Member
 
Join Date: Mar 2008
Posts: 1,593
Quote:
Originally Posted by TrojanHorse View Post
That's why I pose the question. I never argued the fact that a penalty was called, but I asked because the white had called a chop, but then told me it was accidental because he said the player was going to drive the DT up the field, he lost his footing and blocked below the waist.
Another "basic aspect of officiating" is when asked a question about a play you didn't see, keep your response to the letter of the rule, rather than try and address the possible slant applied to the question.

As others have suggested, intent is not a factor in any of the rules under discussion, however what you may recall being told may, or may not, exactly reflect what the official intended to impart to you. How that particular play may have been called reflects specifically what that particular official observed on that particular play.

Apparently, based on his final action, he did not consider the contact he observed to constitute a "block" below the waist or the low end of a chop block. If he believed there was some initial contact with the opponent prior to slipping and falling low that would likely affect his judgment as well.
Reply With Quote
  #10 (permalink)  
Old Thu May 28, 2009, 10:11pm
Official Forum Member
 
Join Date: Sep 2005
Posts: 289
According to NCAA umpires I know, if a backside guard reach blocks low on a defender who engages into the front side center whose intent is not to block him, but reach block himself, it is still a chop block. We can not judge intent.
Reply With Quote
  #11 (permalink)  
Old Fri May 29, 2009, 07:27am
Official Forum Member
 
Join Date: Mar 2004
Location: Germany
Posts: 204
Here is a good example of needing to get the description as exact as possible.

Quote:
Originally Posted by TrojanHorse View Post
During a game, our OL doubled the DT. In the process of this, one of our lineman slips and unintentionally hit the already engaged DT in the knee area.
Quote:
Originally Posted by TrojanHorse View Post
the player was going to drive the DT up the field, he lost his footing and blocked below the waist.
In your first quote you say they were involved in a double team and the lineman slipped low.
In your second quote you say the lineman was going to block and slipped low.

(Note: I only know NCAA - FED might be different).
There is an important distinction here, since the rule says the INITIAL contact needs to be below the waist.
If the lineman was involved in blocking high, and slipped low, I would say no penalty - but one might come out if the official only saw that later part of the action.
If the lineman was trying to block and slipped and made the first contact low, I have a penalty. Intent is not part of the rule, only the contact.
Reply With Quote
  #12 (permalink)  
Old Fri May 29, 2009, 03:30pm
Official Forum Member
 
Join Date: Mar 2004
Posts: 2,193
Quote:
It makes no difference whether it was intentional or not
Actually, it DOES matter, though I'm not necessarily disagreeing with your opinion here as its based on the OP play. On that one, obviously, you'd have to see it, but the key question is: did the offense gain an advantage? Yes = flag; no = pass on it.

However, if it is clearly unintentional you are more likely than not to pass on the call. Here's an example that happened in one of my games last year: sweep or pass play to the flat, offensive lineman out there blocking and ends up face down on the ground (no foul involved). Right behind him is his teammate who's engaged with a defender and they both trip over the guy on the ground, who might have been in the process of getting up (I didn't actually see this). Chop block? No way, even though by definition, it fits (and the fact that the coach is yelling for it).
Reply With Quote
  #13 (permalink)  
Old Sat May 30, 2009, 03:12am
Archaic Power Monger
 
Join Date: Mar 2007
Location: Houston, TX
Posts: 5,983
You apply advantage/disadvantage to a chop block call?
__________________
Even if you’re on the right track, you’ll get run over if you just sit there. - Will Rogers
Reply With Quote
  #14 (permalink)  
Old Sat May 30, 2009, 12:30pm
Official Forum Member
 
Join Date: Aug 2000
Posts: 14,616
Quote:
Originally Posted by ajmc View Post
Gentlemen, with all due respect, acknlowledging and agreeing that a "clip" is always a "clip" and a "chop block" is always a "chop block", does NOT mean that every type of contact,...
I didn't say that it did. But intent is NOT an issue. Most players don't intend to grab a facemask, but that doesn't mean it's not a penalty.

The referee was there and he disagreed with you. That's why he threw the flag.

Quote:
Originally Posted by Texas Aggie View Post
Actually, it DOES matter, though I'm not necessarily disagreeing with your opinion here as its based on the OP play. On that one, obviously, you'd have to see it, but the key question is: did the offense gain an advantage? Yes = flag; no = pass on it.
A chop block is a safety issue. It has nothing to do with advantage/disadvantage.
__________________
"...as cool as the other side of the pillow." - Stuart Scott

"You should never be proud of doing the right thing." - Dean Smith
Reply With Quote
  #15 (permalink)  
Old Sat May 30, 2009, 09:04pm
Official Forum Member
 
Join Date: Feb 2007
Posts: 2,876
Quote:
Originally Posted by BktBallRef View Post
A chop block is a safety issue. It has nothing to do with advantage/disadvantage.
I think it does. It's like the insanity defense. Sure, the act was committed, but punishing it wouldn't deter anyone in a similar position from doing it.

The penalty doesn't make anyone more safe after the fact, only as a deterrent to doing it, either deliberately or negligently. In the case of the player face planting on the ground, possibly getting up, and participating unintentionally in what fits the definition of a chop block, it would do no good to the game to penalize it if the team derived no advantage from it and it was accidental -- not only accidental in the sense of unintentional, but accidental in the sense that it couldn't've been avoided by a reasonable modification of anyone's playing style or assignment.

In the original case, where a slip resulted in a low block, you might judge that the positioning and blocking assignments of team A could be chosen to produce a lesser or greater chance of an accidental chop block by such means, which would give a reason to penalize if one occurred. In the face plant case where the engaged players stumbled over him, no way.

Robert in the Bronx
Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Things I forgot after 11 months away..... Rich Basketball 11 Sat Dec 15, 2007 09:59am
4 months later, another ejection Rich Baseball 7 Mon Sep 10, 2007 09:50am
First games in five months (long post - sorry) Mark Padgett Basketball 18 Sat Jul 02, 2005 02:50pm


All times are GMT -5. The time now is 09:40pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1