That's not the way it works. As soon as you signal for a fair catch you shouldn't have to worry about any defender so you concentrate on the ball and getting to the spot to make the fair catch. It is up to the coverage player to not interfere with you, not you to get away from him.On the muffed punt, the official call was that ISU touched the punt. But you can’t say with any certainty that he actually did touch it.
On replay, there’s absolutely no way to tell if it touched him or not. I’m fine with that part of the call on the field standing, there was no clear and obvious evidence to overturn it - but also nobody can tell me flat-out “the returner touched the ball first” because nobody can tell that on the replay. He might have, he might not have, but there’s no proof, and that’s why the call stood.
Picking up the flag for fair-catch interference was extremely dicey, though.
I know returning kicks is very difficult, but that returner should have gotten away from the Iowa cover guy as soon as he saw him barreling at him. (And don’t get me started on the later play with the kickoff return guy signaling fair catch when he wasn’t even the guy fielding the kick. That was really boneheaded.)
As far as catch interference, there is no way you can pick up the flag saying he was blocked into the returner when the blocker is between you and the returner AND you shed the block. Blocking into the returner is for when the blocker is pushing you into the returner not when he is keeping you away. He was trying to push the blocker into his own returner (like iowa players are coached to do) and when the blocker bailed out to avoid that he couldn't stop his momentum. That is NOT being blocked into the returner. This was a no brainer fair catch interference and should have never been called a muffed punt. He had the ability to avoid the contact by letting up and keeping clear of the return man when the return man signaled fair catch way before the contact.
Last edited: