Not calling grounding twice
- Thread starter Leonard23
- Start date
QB was getting hit-going down and dumped it 5 yds short of RB. Cook didn't even look at the RB. Grounding.
The receiver doesn't need to be looking at the QB. And if the refs feel the QB's throw was altered by being hit, they'll give him even more leeway.
A
anon_xekqhstck0ygt
Guest
The second screen the running back was no where near the play, Cook knew he was toast he chucked it as he fell back.
A few yards. Probably a few more if the throw is altered by a defender.
Not a throw, he tried to spike it and it was at least 5 yds short of an eligible receiver that the QB didn't even see.
Complete ******** non call. Awful. Cannot believe they let that go. Then a phantom holding. That changed the game.
First one was a "maybe" - with a senior QB on the #4 team I can see him getting the call.
But, that second one, when he was in the air already, on his way to the ground, not looking at anyone... that was complete BS... horrible, horrible call....
But, that second one, when he was in the air already, on his way to the ground, not looking at anyone... that was complete BS... horrible, horrible call....
Agree. The 1st? I could possibly understand that being let go.
But that 2nd one was absolutely ridiculous. -Cook didn't even begin to get rid of the ball until he was hit, in the grasp of the RU defender, his feet off the ground and his body being driven backward and down towards the turf. At that point, he simply chucked it away toward nobody in particular. ...And yes, #3 for MSU, who I believe was the supposed "receiver in the area", might have been in the stadium and on the field, but he was no closer to catching that ball than I was.
that one was bad.......and unfortunately for Rutgers , that also seemed to be a turning point .....qb's generally don't get the call once they get drilled and are on their way down like that