This is why Calvin Johnson's catch should have been a TD
Top Comments
All Comments (127)
-
man stop bitching, let it go
-
@TheAlter95 u r prolly one of those ppl who memorize the stats, but those kids on homecoming painting their bodies and just sit on the benches thinking YOURE the cool one.
-
go lions the thumb down is for the call not the video
-
this is as bullshit as the bengals game.. /watch?v=rYxkeJNNSkw
-
@patsrule213 arizona but he got the TD just because of the effort.
-
@patsrule213 It's a gray area, you could seriously call it either way and be right. which is what I hate about the NFL. There should be no gray area, it should all be black and white, like the force out rule. Before it was interpretation, but now it's simply feet in =catch, feet out, no catch. If I were the ref, I would have thought it was not a catch by the book, but given him the TD simply for the effort. Like Harrison's head hit the ground before the ball crossed the plain in the Sb against..
-
Actually, when Calvin Johnson stretched his arm out, that was a second act, meaning that the process of the catch was completed. And last year around mid-November the league admitted that this was the wrong call. So it was a catch because he did complete the process of the catch according to the rulebook. It should of been a Td because he stretched his arm out, not because of any of the reasons that this guy is talking about.
-
wow what a terrible call! that was soo bad it reminds me of the steelers vs seahawks super bowl
When i grow up and i cant see
i wanna be a referee
fling105 8 months ago 13
What is all this bullshit about "fumbling" the ball at the end? His only "second act" was fucking setting the ball down after he scored his touchdown! What an embarrassment for the NFL. I will forever count this game as a W for Detroit.
pbandjsamich4 4 months ago 6