UConn beats UoL because of stupid refs

wow didn't see the end. what happened? When I left for the gym in the 3rd qtr it was 16-7 Louisville i think, could've looked at it wrong. UConn got the W?
 
It's great for Randy, he is a great guy and a very good football coach.
 
That was one of the weakest fair catch calls I have ever seen, and no way it was legally a fair catch.. He didn't really wave his hand, he just gestured once at the air, very late in the kick. If I was on the kicking team, I would have popped him. It's a tough spot for the kicking team though...I've seen the same thing happen before, and it seems to be 50/50 on whether the refs will penalize you for a hit on an illegal fair catch signal(whether it's too late or not really a fair catch signal).

I don't really understand why that's not reviewable though. It seems just like reviewing if a guy stepped out of bounds or not, in that you could say it DID occur and take away yards, but you could never give back yards by saying it didn't occur.
 
Clearly a fair catch signal, no matter how weak you think it was. He raised his hand over his head, waved it and then ran the ball. No brainer for the refs, should have been a penalty from the spot on UConn.
 
ncjacket said:
Clearly a fair catch signal, no matter how weak you think it was. He raised his hand over his head, waved it and then ran the ball. No brainer for the refs, should have been a penalty from the spot on UConn.
Click to expand...

It was very clearly an undecided attempt at a fair catch signal. It says right in the article that

The official definition of a fair-catch signal in the rule book calls for a player to raise his hand above his head and wave it back and forth more than once, something Taylor didn't do.
Click to expand...

The biggest indication that it wasn't actually a fair catch signal is the fact that the guy ran with the ball after making it! Obviously the returner didn't think he was able to get the fair catch, and he's the one who was trying to do it. Either that or he was specifically trying to exploit the rules, in which case maybe the rules need to be looked at.
 
It clearly should have been a penalty for an improper fair catch. There's another rule clearly in the book to catch these half hearted fair catches and even deceptive faux "fair catches". The guys on the telecast read both rules.
 
ramblinwise1 said:
It clearly should have been a penalty for an improper fair catch. There's another rule clearly in the book to catch these half hearted fair catches and even deceptive faux "fair catches". The guys on the telecast read both rules.
Click to expand...

Is there? I thought there might be, but I looked in the rulebook and I couldn't find anything about it. As far as I could tell, the section on fair catches is only a page and a half long, and doesn't say anything about that. Personally, I would like a rule like that, and I would also like one that applies to fake spikes. If we keep having these things, defenders will be forced to play these plays out, and eventually a QB or lineman will get smeared and injured after spiking a ball because the defenders didn't know if the spike was honest or not.
 
They just made this call in the USC-Notre Dame game. Zbikowski (sic) was waving his arms to get other ND players away then he fielded it on a bounce and ran it and they called him for invalid fair catch call and it results in dead ball at the point of fielding it. It should have been the call last night.
 
Here's the definition of the fair catch:
SECTION 7. Fair Catch
Fair Catch
ARTICLE 1. a. A fair catch of a scrimmage kick is a catch beyond the
neutral zone by a player of Team B who has made a valid signal during a
scrimmage kick that is untouched beyond the neutral zone.
b. A fair catch of a free kick is a catch by a player of Team B who has made
a valid signal during an untouched free kick.
c. A valid or invalid fair catch signal deprives the receiving team of the
opportunity to advance the ball, and the ball is declared dead at the spot
of the catch or recovery or at the spot of the signal if the catch precedes
the signal (Rule 6-5-1-a Exception).
d. If the receiver shades his eyes from the sun, the ball is live and may be
advanced.
Valid Signal
ARTICLE 2. A valid signal is a signal given by a player of Team B who
has obviously signalled his intention by extending one hand only clearly
above his head and waving that hand from side to side of his body more
than once.
Invalid Signal
ARTICLE 3. An invalid signal is any signal by a player of Team B that does
not meet the requirements of a valid signal (Rule 6-5-3).
Click to expand...
There is no rule about "faux" catches explicitly, basically the rule is that anything that can be construed as a fair catch (except blocking your eyes from the sun!) counts as one. If it is an improper signal (i.e., putting your hand up there for any other reason than block your eyes from the sun), the play is blown dead and you are penalized.

Which is why the call last night was terrible - that play should have been blown dead either way. The Louisville player did not want to get penalized (even though he would've been in the right even with the correct penalty) and no one else really had a chance to tackle the guy.
 
"d. If the receiver shades his eyes from the sun, the ball is live and may be
advanced."

uh. huh.
 
He signaled for a fair catch --which affected the defenders who saw it --and then he ran the ball. Should have been called.
 
In other news, they shafted us on the deal during Army, at least according to Wes's broadcast. (I listened to the game, didn't watch it) Wes said our boy was shielding his eyes from the sun and the refs called it a fair catch signal.
 
You must log in or register to reply here.
Back
Top