Quote:
Originally posted by JDLJ
I agree that we'd need to see this to decide but, from the original post, I think that we have to remember that B1 has the right to block/contact A1 legally before the ball is thrown because the defender can assume A1 might block him as long as A1 is still coming towards him. In 9-2-3, the A1 is moving away from B1.
|
Not in the rule book. But in the case book, yes.
Quote:
Originally posted by JDLJ
Suudy, you seem to have had this call a lot and I don't think I've ever seen it called. You may be taking away B's right to contact a receiver before the ball is thrown. I would talk to some experienced wide guys and listen to what they say.[/B]
|
I wouldn't say a lot. Two or three times over the last 8 years. Another situation I can think of where I threw it was a TE on a crossing route 7-8 yards deep. The TE was looking back towards the QB with his hand raised and a linebacker de-cleated him. The contact was from the front and above the waist, before the ball was thrown. This act seemed intentional to prevent the TE from running his route.
Though I think I'm starting to see his (and many of your) points. Despite the fact it is an obvious pass play (the QB drops back, the receiver is running a route, the linemen are pass blocking, perhaps a receiver with a raised hand) the receiver is still a potential blocker because of his position. If the QB were to scramble, or a screen pass thrown, at that point the receiver could become a blocker. I guess I'm trying to understand the intent of the rule. The case book hints that a receiver that is not attempting to block is also not a potential blocker. "...if the receiver is not attempting to block or has gone past or is moving away, it is illegal...."
I'm starting to think I'm wrong on this one.

Am I alone in thinking the scenarios described constitute at least unfair contact?