umchicago

November 21st, 2015 at 8:41 PM ^

that's not the best angle.  i was watching it.  he started to lose control as he was falling. then the ball does hit the ground.  this replay makes it appear the ball he drops the ball as he's getting up.

that said, i hate the "complete the process" rule.  my thought is that if you have 3 different points down; ie 2 feet and a knee, i don't care what happens when you hit the ground.  in this case, the guy has like 4 points down, much like calvin johnson did.

DetroitBlue

November 21st, 2015 at 8:48 PM ^

Serious question: are we getting jobbed by the refs because of Harbaugh's loud and blatant reactions to flags? I get that big ten refs are genuinely bad at their jobs, but I haven't seen bad calls/no calls going both ways. We've been getting the short end of the stick for weeks now and it's at the point where it doesn't seem like a coincidence anymore



Sent from MGoBlog HD for iPhone & iPad

Greg McMurtry

November 21st, 2015 at 9:03 PM ^

I think he bobbled it. Look at 6-8 seconds, when he falls it's in his right hand, then at 7 seconds it's between his legs in neither hand, then when he stands up it's in his left hand. It's not the dropping of the ball at the end. I only watched the clip, didn't watch the game or hear the call or anything, so not sure what refs said.



Sent from MGoBlog HD for iPhone & iPad

TennBlue

November 21st, 2015 at 10:26 PM ^

1) Catch the ball while standing and make a "football move" to prove you have possesion and then the pass is complete and the receiver becomes a runner.

2) If caught when falling, the ball has to be kept in control until the play is completely over. No "football move" involved. Player must demonstrate complete control throughout the process of the catch.

The confusion here is people not keeping the two clauses separate. If he was falling down, it doesn't matter how many steps he takes or what moves he makes. Clause 2 applies and what matters is maintaining control.

In this case, the refs seem to have ruled that since he fell down he had to maintain control of the ball, and he didn't - therefore it's incomplete.

 

By the way, the "process of the catch" rule has been around since 1911 and the burden of proof has always been on the receiver of the forward pass to demonstrate complete control of the ball. The default has always been that if there is any doubt, the pass is incomplete - so this is not some new thing that has been cooked up in the last few years. It's always been like this.

Squader

November 21st, 2015 at 10:38 PM ^

Ok, but the question obviously becomes "how many steps must be taken before falling before you are considered to have done something other than fall?" If a running back took three steps into the endzone and then fell and dropped the ball, no one would say he didn't carry the ball through the endzone for three steps. How many steps must a receiver take before his fall is far enough removed from the catch to not transform the catch into a non-catch?

....also that last part is why this keeps coming up. It's so obvious to everyone watching that e.g. Calvin Johnson caught the ball that when the rule declares up to be down, people get upset. I'm not saying the rule was incorrectly applied, but it's possible it's a badly defined rule.

 

TennBlue

November 21st, 2015 at 10:47 PM ^

He caught the ball in the endzone, so it has to be a completed catch before the touchdown can be awarded. And completing the catch means maintaining control when falling down.

He fell down and lost control of the ball, therefore it was not a catch. Since it was not a catch, he never had possession in the endzone and it's not a touchdown.

Again, you're getting two different rules confused. If he caught the ball at the 1 yard line, then carried across the line and fell down, that's a completed pass and a touchdown the instant he crosses the goal line. It then doesn't matter if he falls down, as the play is already over.

Catching a pass in the endzone means you have to complete the pass, first and foremost, before anything else can be ruled on.

Squader

November 21st, 2015 at 11:07 PM ^

Your example I think gets at exactly what people don't like here. If he catches the ball at the one, takes three steps while crossing the plane, and then falls down but the ball comes out, it's a touchdown (right?). If he catches the ball in the endzone, takes three steps in the endzone, and then falls down with the ball coming out, it's not a touchdown. I accept you're correct about what the rule says, but why should this be the case? 

 

TennBlue

November 21st, 2015 at 11:23 PM ^

Making a clean catch at the 1 turns the receiver into a runner. Then he runs the ball across the goal line. That's no different from anybody running it in from any distance, so it's not controversial at all.

If he initially contacts the ball at the 1, but then juggles it across the line and drops it as he falls, then he has never had possession of the ball beyond the goal line. It's an incomplete pass, not a touchdown.

Same is true for a ball caught in the endzone. Make a clean catch, demonstrate clear possession, and the receiver becomes a runner possessing the ball beyond the goal line. Touchdown. An incomplete pass means there was never possession, so it's not a TD.

Demonstrating possession of the ball is easy when you stay on your feet. That's the "football move  and one foot inbounds"  clause. If you catch the ball falling down, though, you can't advance it any further - so the only way you can demonstrate possession is by maintaining complete control even after you fall down.

CoverZero

November 21st, 2015 at 9:12 PM ^

I did not see the play live, but if that TD on the clip was overturned.... well its Stunning... even by Big Ten Shit standards.

wow

Dawkins

November 21st, 2015 at 9:14 PM ^

Thats not a catch. Its similar to what happened to calvin johnson and dez bryant. Those were called correctly as well.

MichiganMAN47

November 21st, 2015 at 9:20 PM ^

All the calls hinge on the definition of indisputable. You should have other people up there so that someone has the opportunity to dispute... So someone can't overturn plays like this or Barrett's TD.

the fume

November 21st, 2015 at 9:34 PM ^

That was not a catch, because he actually bobbles it twice.

 

It's hard to see on that video, but on the TV replays you could see when he's taking his first several steps, the ball is moving in his stomach. No possession yet, so these first 3 steps he takes well in bounds are irrelevant.

 

He finally gains control as he's going down and does still have a foot down, but he hits the ground immediately after and completely bobbles the ball out of bounds. At that point, he would need to maintain control to complete the process like any other sideline catch.

Swayze Howell Sheen

November 22nd, 2015 at 8:56 AM ^

"If you need two paragraphs to If you need two paragraphs to explain why that wasn't a catch, you've lost the argument."

This is the strangest argument I have ever seen. What if he needed 1 1/2 paragraphs? Where is the cut off for arguments that are automatically wrong?

Also, let me try a shorter form:

That was not a catch, because he actually bobbles it twice. On a different replay, when he first "catches" it, the ball is actually being bobbled; then, as he regains control and is falling, he bobbles it while hitting the ground. Thus he never had firm possession."
 
Boom - ONE PARAGRAPH!
 

BornInA2

November 21st, 2015 at 9:37 PM ^

My current working theory: Delaney doesn't give a shit about the quality of officiating because it doesn't negatively affect revenue. Plus he can go out and hire half-blind, Taco Bell rejected nitwits on the cheap and give himself another fat raise with difference.

Yep, these officials brought to you by the same asshat that brought Maryland and Rutgers to the Big 10-14.

Greg McMurtry

November 21st, 2015 at 9:40 PM ^

Here's the rule: If a player goes to the ground in the act of catching a pass (with or without contact by an opponent) he must maintain complete and continuous control of the ball throughout the process of contacting the ground, whether in the field of play or in the end zone. This is also required for a player attempting to make a catch at the sideline and going to the ground out of bounds. If he loses control of the ball which then touches the ground before he regains control, it is not a catch. If he regains control inbounds prior to the ball touching the ground it is a catch.



Sent from MGoBlog HD for iPhone & iPad

DT76

November 21st, 2015 at 9:44 PM ^

Wisconsin got boned earlier in the game on a punt return touchdown called back due to fair catch signal misintepreted. Same signal the same guy used later in the game that wasn't seen as a fair catch.

 

Not that I feel bad for them though.

AmayzNblue

November 21st, 2015 at 9:52 PM ^

Yeah, the end of the NW/Wisky game was atrocious. Matt Millen immediately defended the refs by saying it was the right call....while watching slow motion replay of the Wisconsin receiver catching and holding the ball for 2.5 steps until going out of bounds. Just pitiful.



Sent from MGoBlog HD for iPhone & iPad

SaigonBlue

November 21st, 2015 at 10:04 PM ^

If THAT was not a TD, then there is NO WAY the UNC "TD" in OT against VT was a TD.

But the B1G refs thnk PSU wears shoulder pads as jocks, so yeah....

Mind-boggingly incompetent.