![]() |
|
|
|
|||
|
I said this somewhere else, but the rule does not talk about excessive celebration or says anything about premeditated celebration. The rule only talks about acts that should be considered unsportsmanlike. This is not different in other rules when it is clear that grabbing a facemask is illegal or going high and low on a block (regardless of the typical chop block). This rule clearly says throwing the ball high is illegal and is an unsportsmanlike act along with many other very specific examples of what the committee must consider illegal. The only judgment part of this was how high the ball was thrown. And it is clear this ball was thrown rather high. When the ball comes down and hits you in the head, after you have jumped into the arms of teammates and then you hit the ground, then the ball hits you in the head. That seems pretty high in my book.
For the record when I first saw this play I thought this was not a good judgment on the official’s part. Then when I actually read the rules (not just what ESPN referenced), it was clear to me the officials followed the rule. I think that took a lot of guts and was the right call. It is sad that we just turn the other cheek on obvious violations of the rules. Peace
__________________
Let us get into "Good Trouble." ----------------------------------------------------------- Charles Michael “Mick” Chambers (1947-2010) |
|
|||
|
You can't hardly go wrong as an official, I guess, if you do what the rulebook and your supervisors tell/want you to do. It does seem harsh, but if the rule is clear, the rule is clear. Unlucky. I'm going to guess that guy will never do that again.
All that said, and this is just Devil's Advocate here...do we think that what the quarterback did was intended to be unsportsmanlike? I know what the rule says. There's no argument about what the rule says. I'm asking could one see that what the intent of the rule was, its raison d'etre, was not necessarily to punish spontaneous joyous celebrations? Yes, the ball went high. No question. Did anyone really get shown up? JRut is right, though, we do tend to turn a blind eye to obvious infractions. Probably 99% of those don't happen on a last-play-of-regulation, almost-game-tying touchdown in a DI game, though.
__________________
"And I'm not just some fan, I've refereed football and basketball in addition to all the baseball I've umpired. I've never made a call that horrible in my life in any sport."---Greatest. Official. Ever. |
|
|||
|
Quote:
Peace
__________________
Let us get into "Good Trouble." ----------------------------------------------------------- Charles Michael “Mick” Chambers (1947-2010) |
|
|||
|
Quote:
I was just stepping outside the rule for just a second to ask (as I asked a veteran football official in my office this morning) if what he did violated the spirit of the rule (the reason it exists). He didn't think it did, and neither did I. But both of us (as well as the people who are important) agree that, yesindeedy, that right there is a rules violation and as harsh as it is and as bad as it might (or might not) make you feel if you call it, it is what it is. I just think that maybe that if you have to make a call that makes you feel like, "Man, I'm sorry I had to call that" afterwards (and, as has been pointed out, we don't know that the official in question felt that way - only that some of us would have felt sorry if we had to call it), maybe that's a rule that should be looked at and addressed. Sure, the simpler thing for all concerned is "don't do it, or face the consequences." Absolutely. But life's not always that simple. I feel for the kid and the team and the official, but from what I read, the player accepted responsibility and everybody moves on. This isn't the first time it's happened (not this exact scenario, but something like this) and it won't be the last. You can bet, that sure as shootin', college players are going to be handing footballs to officials in record numbers across the country going forward. Not all of them, but a goodly number, I'd bet.
__________________
"And I'm not just some fan, I've refereed football and basketball in addition to all the baseball I've umpired. I've never made a call that horrible in my life in any sport."---Greatest. Official. Ever. |
|
|||
|
Quote:
What none of us know though is what specific instruction the officials were given in regards to this rule. It sounds like the D-I guys were told specifically to flag these types of situations always so that made it a very easy call for him to make. |
|
|||
|
|||
|
Quote:
The call is a delay of game unsportsmanlike conduct foul. After a score or any other play, the player in possession immediately must return the ball to an official or leave it near the dead-ball spot. This prohibits: (a) Kicking, throwing, spinning or carrying (including off of the field) the ball any distance that requires an official to retrieve it. (b) Spiking the ball to the ground [Exception: A forward pass to conserve time (Rule 7-3-2-d)]. (c) Throwing the ball high into the air. (d) Any other unsportsmanlike act or actions that delay the game."
__________________
"...as cool as the other side of the pillow." - Stuart Scott "You should never be proud of doing the right thing." - Dean Smith |
|
|||
|
Sorry guys, I always give the benefit of the doubt to the field official who is reacting to something he sees in a split second. I can't this time. That call may have been justified by weasel wording the rule, but having seen the play live, the player DID NOT "throw the ball high into the air', he threw it over his right shoulder, backwards, straight down to the ground. It many have bounced high, but that was not visible.
This was clearly not intended as a "spike" and flagging it was an overreaction, had this play happened in the 1st quarter. The fact that it happened during the last timed down of a game, and the subsequent try could have tied the score and forced overtime, or potentially produced a potential 2 point conversion for the outright win ( not a likely choice) only adds to the unfortunate nature of the response. Perhaps the supervisor wasn't more forceful backing this call because although it may have been proper, it wasn't right. |
|
|||
|
Quote:
So the video of him throwing the ball high into the air is lying?
__________________
"And I'm not just some fan, I've refereed football and basketball in addition to all the baseball I've umpired. I've never made a call that horrible in my life in any sport."---Greatest. Official. Ever. |
|
|||
|
Quote:
Quote:
Toss a ball over your shoulder and see if it takes 4 seconds to land AND see if it hits you in the head.
__________________
"...as cool as the other side of the pillow." - Stuart Scott "You should never be proud of doing the right thing." - Dean Smith |
|
|||
|
Quote:
I'm not questioning the call or that the rule exists. I'm questioning why the rule exists. If it's delay of game, that seems pretty specious to me (and why it would then be 15 yards if it's not about showboating or grandstanding and not just 5 like every other delay of game I've ever heard of, I don't know). The call was (obviously) correct by rule. That's the way your bosses (conference, supervisor, crew chief) want it called, you call it or you do something else with your leisure time. I get that. Harsh call. Unfortunate call. Brings unwarranted attention to what we do in a negative light and lets loose every columnist who's never officiated a snap in his life, yet who writes 600 words about how we do what we do and how every call is a judgment call despite the fact they've never ever sat in a rules meeting or had our mechanics explained to them. I'm just saying I don't quite grasp why the rule exists in that form with the idea of it being called to cover that situation. I'm pretty conservative by nature, but I just don't see what harm was caused.
__________________
"And I'm not just some fan, I've refereed football and basketball in addition to all the baseball I've umpired. I've never made a call that horrible in my life in any sport."---Greatest. Official. Ever. |
|
|||
|
http://web1.ncaa.org/web_video/NCAAN...3/19830817.pdf
The rule was written into the rulebook apparently in 1983. (See page 7 of the linked document) |
|
|||
|
Quote:
|
|
|||
|
Quote:
Marv Levy's "overofficious jerk" would apply here, methinks. Not to the official making the call, but to the whole concept. I mean, come on.
__________________
"And I'm not just some fan, I've refereed football and basketball in addition to all the baseball I've umpired. I've never made a call that horrible in my life in any sport."---Greatest. Official. Ever. |
|
|||
|
The calling official, Mike McCabe, is an excellent official. But hearing Dave Cutaia speak numerous times at Camp, my interpretation of his statment is that the call is defensible by rule but shouldn't have been made. I would bet he graded it internally as a "marginal call."
Look for this call to be discussed in Dave Parry's training tape next year. |
![]() |
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| What did Tom Eades do to get mad at the SEC Officials Supervisor? | secondregionbug | Basketball | 6 | Fri Nov 16, 2007 01:49pm |
| SEC supervisor | gscsj | Football | 2 | Fri Apr 28, 2006 11:08am |
| SEC Supervisor Ousted | ShadowStripes | Basketball | 49 | Wed Dec 21, 2005 12:09pm |
| IM Supervisor | lukealex | Basketball | 27 | Sat Jul 23, 2005 06:30pm |
| To call or not to call foul ball | DaveASA/FED | Softball | 11 | Thu Jun 24, 2004 11:47am |