invalid fair catch signal

Donate To GopherHole
hello-world said:
Because I don't think you can review kick-catch interference. The only penalty that I know you can review is targeting which has a specific exception built into the rule book. There are only a few penalties you can review and they all have explicit exceptions (e.g., targeting, illegal forward pass, too many men on the field).

These aren't the same call. Waving for a fair catch is part of the play (it's not a penalty) and therefore reviewable by default.
Click to expand...

Just saw your post after my post. I believe your last comment is my answer.
 

hello-world said:
This is the thing that drives me most crazy. I saw it. I didn’t understand why NBC wasn’t showing it. I started to think that I was wrong, and then I saw the notebook, and the commentators still didn’t get what was going on.

The most controversial thing about that call was that the commentators didn’t see it on the play.

There was a reason that every Gopher on the field was standing flat footed by the returner and that led to what happened next.
Click to expand...
Yeah they kept only showing the replay from right before he caught it and ran. I almost immediately thought he was fair catching it. The text book way to pause and return legally is Douglas returning it at Wisconsin for a TD.
 


cncmin said:
but what will he do about it? So far, the kick and punt return teams have been about as bad as any I can remember, but I don’t see changes there.
Click to expand...
Panthadad2 said:
Yeah, I think it should have been blown dead by the rule. The ref following the play was off camera so it's tough to know if they called it on the field. I don't think they actually throw a flag but wave over their head as it occurs. My only question is why it was reviewed.
Click to expand...
It’s a reviewable play by rule. There is no flag or yardage. It just comes back to where they possess the ball.
 

I remember in 2014 against Wisconsin, Alex Erickson got a long return called back when he did something similar i believe.

I did not know that any waving of the arms meant fair catch, but it makes sense. You’re baiting the opponent to lay up.

Also, all it did was give them the ball at their spot. They only had to go about 15-20 yards to have a shot at a FG with the wind. The call didn’t mean Iowa had to promptly allow a sack and then throw a game ending INT.
 


I just went back and watched a replay on DVR. The refs did actually call it an "invalid fair catch" which should have been a 5-yard penalty from the spot at the 46. They never did assess the penalty and spotted the ball at the 46. I'm still confused.
 

Panthadad2 said:
I just went back and watch a replay on DVR. The refs did actually call it an "invalid fair catch" which should have been a 5-yard penalty from the spot at the 46. They never did assess the penalty and spotted the ball at the 46. I'm still confused.
Click to expand...
There is no penalty on that play. it just call a invalid fair catch. No penalty on the play.
 

gophersfan said:
There is no penalty on that play. it just call a invalid fair catch. No penalty on the play.
Click to expand...
I am not saying this is the rule, but it totally could fit under delay of game logically.
 

If I was looking at it from a Hawkeye perspective, I would be miffed that if was an obvious fair catch signal then it should have been blown dead right away.

Letting the play go leaving it subject for review is a terrible look. Would suck to have an injury result of that.

For Iowa fans, I am shedding a tear. Crocodile tears.
 



gophersfan said:
There is no penalty on that play. it just call a invalid fair catch. No penalty on the play.
Click to expand...

That's my understanding too. The ball is dead and goes back to the spot where it occurred.
 

I could have sworn that I saw him waving for a fair catch on the live broadcast, and I was confused by the return.

But I can be biased, so I went into my DVR to check. Not only did I see it, the ref saw it, and multiple Gopher players saw it too. It wasn't even questionable. His arm was clearly over his shoulder.

1697939483047.png
 

hello-world said:
Because I don't think you can review kick-catch interference. The only penalty that I know you can review is targeting which has a specific exception built into the rule book. There are only a few penalties you can review and they all have explicit exceptions (e.g., targeting, illegal forward pass, too many men on the field).

These aren't the same call. Waving for a fair catch is part of the play (it's not a penalty) and therefore reviewable by default.
Click to expand...
 

Attachments

  • F9AVb7nWYAANDB8.jpeg
    F9AVb7nWYAANDB8.jpeg
    72.3 KB · Views: 14

gophersfan said:
There is no penalty on that play. it just call a invalid fair catch. No penalty on the play.
Click to expand...

The internet machine tells me it's 5-yard penalty. Maybe not. I'm not looking up the rule book.
 




Ope3 said:
If I was looking at it from a Hawkeye perspective, I would be miffed that if was an obvious fair catch signal then it should have been blown dead right away.

Letting the play go leaving it subject for review is a terrible look. Would suck to have an injury result of that.

For Iowa fans, I am shedding a tear. Crocodile tears.
Click to expand...
South Dakota State/Southern Illinois has a not dissimilar play today. SIU returner waived a shoulder height back arm waive (intending fair catch) as he retreated to field a punt kicked over his head. He fielded the ball, stopped, and two SDSU gunners pulled up, looked to the ref, no whistles, so then preceded to tackle the returner. Then were flagged for P.I. Bizarre sequence.
 






GophersInIowa said:
How often does the returner waive people away that much and then still field the ball? It’s very rare.
Click to expand...
Still field the ball AND return it. It almost never happens. We used to call it poison because NO ONE is supposed to touch it.

People are confusing that they've seen tons of returners waive off their teammates and nothing being called with seeing tons of returners waive off everyone, field it, and return it (almost never happens).
 



I didn’t read all 109 posts, but in real time from row 63 on that side of the field, the guy definitely lifted his arm for a fair catch. I don’t know if it slowed any Gophers down, but he definitely signaled. If he would have been hit, it would have been a penalty.
 

Have you ever seen this called in a game before?

I didn't even know this was a rule before today. Suspect a lot of people are the same.
 

@Holy Man he definitely didn't raise his arm above his head, but he also definitely was signaling to his teammates to get away from the ball.

It's pathetic that he lied about that to media. He claimed in the post-game interview he was just trying to keep his balance, but that is such a silly little lie by a bitter little boy.
 

IIt


salzie said:
Both are true
1. It was correct application of rule
2. Crappy rule

I'll take i
Click to expand...

salzie said:
I get why ia fans are upset

I don't think they have leg to stand on


All I meant but didn't properly articulate
Click to expand...
Not a crappy rule. Punt returners are often defenseless. If this guy has returned punts all season, he should know the rule.
I officiated high school games and we always explained that waving your hand but not above your head is an invalid fair catch and a penalty. The call was correct.
 


You remember it being called before? What did the guy do that got it called?
 

We once beat Wisconsin on something that most would consider some bull shit. It's still a win, and I tempered the "Well did we deserve it?" stuff with recollections of bad calls when we were in Madison that would have changed the game.

They'll say it's bull shit, but they didn't care whenever you got close to winning so why should you when they did? In a few months, it'll just be memes.
 

You must log in or register to reply here.



Top Bottom