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
  #16 (permalink)  
Old Wed Oct 13, 2004, 06:57am
Official Forum Member
 
Join Date: Jun 2000
Location: Bloomington, IL
Posts: 1,319
Quote:
Originally posted by BigGref
Our consensus was that we bag the spot of first touching by R
Why bag R's touching? K is the only team that can "first touch".

__________________
Mike Sears
Reply With Quote
  #17 (permalink)  
Old Wed Oct 13, 2004, 07:47am
Official Forum Member
 
Join Date: Sep 2003
Posts: 36
Quote:
Originally posted by mikesears
Quote:
Originally posted by BigGref
Our consensus was that we bag the spot of first touching by R
Why bag R's touching? K is the only team that can "first touch".

You probably want to bag it for the fumble/muff.
Reply With Quote
  #18 (permalink)  
Old Wed Oct 13, 2004, 09:28am
Official Forum Member
 
Join Date: Jun 2000
Location: Bloomington, IL
Posts: 1,319
Quote:
Originally posted by JamesBond
Quote:
Originally posted by mikesears
Quote:
Originally posted by BigGref
Our consensus was that we bag the spot of first touching by R
Why bag R's touching? K is the only team that can "first touch".

You probably want to bag it for the fumble/muff.
If it is a fumble, yes. But a muff? What is the relevance of the spot of a muffed kick by R?

__________________
Mike Sears
Reply With Quote
  #19 (permalink)  
Old Wed Oct 13, 2004, 10:43am
Official Forum Member
 
Join Date: Dec 2003
Location: Little Elm, TX (NW Dallas)
Posts: 4,047
This pops up in numerous threads - bagging random spots.

Think about the purpose of the bag. It's to mark what could potentially be an enforcement spot for a penalty. Bagging a muff (or dropped snap) is improper mechanics. I've heard the argument that bagging a muff or dropped snap is done to show everyone else that you see a loose ball. Again - this is not proper mechanics (in NCAA, Fed, or NFL). Bag potential enforcement spots (or, possibly, other spots you may need... I've seen bags used properly to mark an out of bounds spot if the official needed to leave the spot for some reason (penalty cleanup, officials conference, etc), or to mark the spot that certain players leave the field.)

It should NOT be used to mark a spot that will not be needed.
Reply With Quote
  #20 (permalink)  
Old Wed Oct 13, 2004, 11:16am
Official Forum Member
 
Join Date: Sep 2003
Posts: 36
Quote:
Originally posted by mcrowder
This pops up in numerous threads - bagging random spots.

Think about the purpose of the bag. It's to mark what could potentially be an enforcement spot for a penalty. Bagging a muff (or dropped snap) is improper mechanics. I've heard the argument that bagging a muff or dropped snap is done to show everyone else that you see a loose ball. Again - this is not proper mechanics (in NCAA, Fed, or NFL). Bag potential enforcement spots (or, possibly, other spots you may need... I've seen bags used properly to mark an out of bounds spot if the official needed to leave the spot for some reason (penalty cleanup, officials conference, etc), or to mark the spot that certain players leave the field.)

It should NOT be used to mark a spot that will not be needed.
You bring up a great point that is well taken. When I wrote my response, I was thinking fumble. I agree the muff doesn't get the bag. I added the /muff because I was thinking wrong. (I plead umpire ignorance your honor. I am never around when a scrimmage kick is fielded. My crew does drop a bean bag when a free kick hits the ground to be sure it met the went ten yards and touched the ground requirement. Clearly the muff on a scrimmage kick is different.)
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



All times are GMT -5. The time now is 06:36am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1