This isn't why the NFL instituted replay. They added it to fix obvious mistakes - a fumble where his knee was down, a receiver not getting both feet in, ball hitting the ground and being called a catch.
Not this - the ball may have been moving while at the same time his foot may have been touching turf... Or last weeks when james was reaching out and it was called no catch... or maybe the jets guy getting called for fumbling into the end zone when he never actually lost the ball. That one still irked me the most. The ball never hits the turf, but because it was like, unpossessed for a split second on a replay its a touchback? That's just ridiculous.
The stuff you see in slow motion isn't what is actually happening on the field. He caught the ball and got both feet in - touchdown. End of story.
Yeah - didnt really get that. He reached the ball over, and pulled it back. Its essentially running the ball forward and then backwards. It's not forward progress.
If you ran for the first down and ran behind it and got tackled it's not a first down. Same idea applies to this, or so i thought. The only place it doesn't is the end zone where if you break the plane its a TD and you can then bring it back.