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 Sat Nov 04, 2006, 06:29pm
Official Forum Member
 
Join Date: Aug 2000
Location: Texas
Posts: 1,305
How can you judge they "deliberately" went offside on the KO?

Initially it was reported that that the rule this year would be that inside the last 2 minutes of a half the clock would not start on KO's until ball was legally touched after the kick. However, that is not what it actually ended up being. It would be easy to put that little change in if they choose to do so.
Reply With Quote
  #2 (permalink)  
Old Sat Nov 04, 2006, 06:38pm
Official Forum Member
 
Join Date: Aug 2003
Posts: 10
Your point is well taken - it's very difficult to judge whether a team is guilty of USC in this situation. However when a nationally ranked team, has all players but one go offsides twice in a row - methinks something is rotten in Denmark. One could argue that it is possible for it to happen, one can also argue that bumblebees can't logically fly either.

Unsportsman-like Conduct will become one of the most difficult rules to apply in the future. And one of the most important rules if we are to keep football a sport that follows a defined code of ethics.

I would say that the fault (if one can call it a fault - I do) lies primarily with the coaches. Again this is not an instance of one individual breaking a rule or crossing a line. Here we have one or more coaches that have willingly and knowingly coached their players to (again this is my opinion) break the rules to gain an unfair advantage.
__________________
NC RTP
Reply With Quote
  #3 (permalink)  
Old Mon Nov 06, 2006, 11:03am
Official Forum Member
 
Join Date: Sep 2006
Posts: 41
That's the problem with rules designed for TV. Not for the game of football. People always stretch rules or find loopholes or test limits, however you want to say it. I don't think it USC, just testing the limits. I think it was a very smart play by Wisconsin, and shows the stupidity of make rules for TV. But I guess just like everthing $'s rule. TMO
Reply With Quote
  #4 (permalink)  
Old Mon Nov 06, 2006, 11:47am
MJT MJT is offline
Official Forum Member
 
Join Date: Oct 2004
Location: Alton, Iowa
Posts: 1,796
Quote:
Originally Posted by TXMike
How can you judge they "deliberately" went offside on the KO?
TXMike, the 2nd time they did it, I am interpreting it to be deliberate. If a team has 2 FStarts within the last 5 seconds of the play clock, in the last 2 mintues of the game are you going to start the clock on the RFP the 2nd time? I'm sure you are, and the rules support us in doing so.

The second time they did this, I think the official has the opportunity, within the rules, to set the clock back to the time it was before the KO, and start the clock on the snap. I'd be VERY suprised if the NCAA does not make some allowances for this next year. They, more than the NF, seem to take care of these types of things pretty quickly. Pretty easy change, something like this... "after a 2nd consecutive offisides on the kicking team, team R can take the ball 5 yards from the DB spot and the clock will be reset to the time it was before the kick."
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
Penn St./FSU Safety? shave-tail Football 9 Wed Jan 04, 2006 09:33am
Wisconsin FB Officials ssmith Football 2 Tue Nov 01, 2005 09:26am
Wisconsin officials wisref2 Football 2 Fri Oct 14, 2005 09:49am
State Government Defeated in Attempt to Control State Association mikesears Football 14 Wed Apr 20, 2005 07:35am
Wisconsin LDUB Baseball 5 Sun Jul 25, 2004 10:59am


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



Search Engine Friendly URLs by vBSEO 3.3.0 RC1