|
Post by Penn State fan on Sept 15, 2019 21:31:21 GMT -5
So the kick catch interference call in the fourth quarter was a big moment for the refs in Pitt-Penn State Can’t find the gif anywhere, but the game (and the call) is probably on YouTube and Twitter. Summary: The Penn State play hit the Pitt player while tackling him on a punt. The Pitt player did NOT call for a fair catch, and touched the ball before any contact was made. However, kick catch interference was still called. Not sure if the Halo rule still applies?? Replay is at 1:32:34 of the video below
|
|
|
Post by zebrastripes on Sept 15, 2019 21:44:56 GMT -5
If you would actually take the time to look up the rule yourself (something that I’m sure is too hard for you given how you normally post), you would see that KCI has nothing to do with whether or not the receiver signals for a fair catch.
Yes, this is a foul. Hate to break it to you.
|
|
|
Post by Penn State fan on Sept 15, 2019 21:50:00 GMT -5
If you would actually take the time to look up the rule yourself (something that I’m sure is too hard for you given how you normally post), you would see that KCI has nothing to do with whether or not the receiver signals for a fair catch. Yes, this is a foul. Hate to break it to you. I agree with you that it has nothing to do with a fair catch, but I would argue that there was no contact before the ball got there. That’s where I am confused about whether it has anything to do with contact or not. Agree that it has nothing todo with a fair catch.
|
|
|
Post by Penn State fan on Sept 15, 2019 21:53:08 GMT -5
If you would actually take the time to look up the rule yourself (something that I’m sure is too hard for you given how you normally post), you would see that KCI has nothing to do with whether or not the receiver signals for a fair catch. Yes, this is a foul. Hate to break it to you. Pause it at 1:32:36 No contact and he has the ball
|
|
|
Post by 75er on Sept 16, 2019 9:02:42 GMT -5
It is a kick catch interference foul if, before the receiver touches the ball, the kicking team man enters the area in front of the receiver, and extending 1 yard in that front area. This essentially requires the gunner to "break down" or slow down in front to allow an opportunity to catch the kick. If there is any question about the interference, it is to be called a foul.
|
|
|
Post by zebrastripes on Sept 16, 2019 9:14:36 GMT -5
If you would actually take the time to look up the rule yourself (something that I’m sure is too hard for you given how you normally post), you would see that KCI has nothing to do with whether or not the receiver signals for a fair catch. Yes, this is a foul. Hate to break it to you. Pause it at 1:32:36 No contact and he has the ball Again, it's clear you haven't bothered to look up the KCI rules yourself. Contact is not a requirement for KCI.Please stop polluting this forum with your garbage and ignorance.
|
|
|
Post by Penn State fan on Sept 16, 2019 9:33:38 GMT -5
It is a kick catch interference foul if, before the receiver touches the ball, the kicking team man enters the area in front of the receiver, and extending 1 yard in that front area. This essentially requires the gunner to "break down" or slow down in front to allow an opportunity to catch the kick. If there is any question about the interference, it is to be called a foul. OK. Understandable that they called it then. Would rather be safe than sorry, and it is very close to one yard. Still not sure whether it was the right call, but I could see the point of throwing the flag. Don’t want a missed KCI.
|
|
|
Post by zebra80 on Sept 16, 2019 9:45:41 GMT -5
Dude, its a foul...
|
|
|
Post by FredFan7 on Sept 16, 2019 9:48:10 GMT -5
PSF, time to move to Week 4. You got the rules explanation and interpretation. I understand you don't like the call as a fan, but the crew got it right.
Thanks for your contributions to the forum.
Moving on.
|
|