Help a Newb: I don't understand what qualifies for pass interference

3 years ago by pingwax to c/NFL

I'm a Broncos fan, but was watching a rerun of the Dolphins/Texans second pre-season game today - I didn't especially care about the outcome or know anything about either team.

At 14:42 in the second quarter, Thompson threw a long ball to Wilson Jr. As Wilson Jr closed in and started to reach for the ball, the defender (Ward) grabbed at Wilson's right bicep, then pushed down on Wilson's right hand and wrist. Wilson tried to make a one handed catch with his left hand, but was now off balance and fell.

It seems to me that Wilson possibly had chance to catch the ball - if his arm hadn't been grabbed. No one - not even the players - seemed to think it was an issue. The commentators said it was good coverage.

I just can't get my head around it, what are the criteria for pass interference? This and what qualifies as roughing the passer seem super arbitrary.

CMLVI 2 points 3 years ago

It's almost always judgement calls. Same as holds and many other non-procedure penalties. Holding happens a lot more than it's called, but it doesn't generally effect the play, so it isn't called. Some calls just get missed; pointing to a singular play in one game as an example of not understanding PI may be doing yourself some injustice; it seems like you know what PI is, just that it was a missed call in that game.

As far as good coverage is concerned, there is hand fighting when going up for passes, as WR and DB. I think generally as long as the contact is kept to hands, it doesn't get called. If you're draping an arm, or if you are impeding the WRs path, it's gonna get called. Contact with the bicep, without seeing it, may be inconsequential. The contact with the hand/wrist is somewhat to be expected.

save

path: 0 2929386, hotness: undefined, score: 2, children: 2

pingwax 1 point 3 years ago

Thanks for the ideas; I've read the rule, so I "know" what the definition is, but the man - real life application of the rule is confusing as hell :). It seems like this was a missed call, but since even the receiver rolled with it, I guess they either know something I don't, or maybe this is just younger players in a preseason game. Just have to keep watching and trying to figure it out.

save

path: 0 2929386 2978329, hotness: undefined, score: 1, children: 1

CMLVI 1 point 3 years ago

Oh definitely. Also, unless it's egregious, in an important game, or against a defender they are struggling with or have history with, players won't normally argue non-calls too much. Plus, with it being a pre-season game, stakes are much lower, so guys aren't as wrapped up in the outcome. For players trying to make the cut, they're usually judged by their film rather than game result, so it likely wouldn't be held against him for not making the catch either.

save

path: 0 2929386 2978329 2988339, hotness: undefined, score: 1, children: 0

lotanis 1 point 3 years ago

One component that affects it is that the defender is allowed to compete for the ball. So if they've got their head round to see it and are going for it then they're given more leniency than if they just check someone's progress while running downfield.

So, roughly (although it IS incredibly subjective): pulling on an arm in a way that prevents a defender getting to the position to catch the ball=bad. Pulling on an arm while you're both trying to get to an incoming ball=ok.

save

path: 0 2978248, hotness: undefined, score: 1, children: 1

pingwax 1 point 3 years ago

Subjective rules suck, but I also don't have any better ideas. I don't remember the defender turning around, but you could be right. It all happens so fast in real life that maybe they just didn't notice or realize. Or maybe it was a completely legitimate play and I have wrong expectations. Just have to keep watching.

save

path: 0 2978248 2978367, hotness: undefined, score: 1, children: 0