What's new
Fantasy Football - Footballguys Forums

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Game Thread W9 - San Diego V Houston (1 Viewer)

That grounding call would be fine if the refs were consistent about it. He was obviously throwing it away on purpose, and he wasn't out of the pocket.

But since they almost never call that when a receiver is anywhere near the ball, they shouldn't have called it that time either.

 
Last edited by a moderator:
That grounding call would be fine if the refs were consistent about it. He was obviously throwing it away on purpose, and he wasn't out of the pocket.

But since they almost never call that when a receiver is anywhere near the ball, they shouldn't have called it that time either.
His purpose doesn't matter. Rivers has at least once thrown at a nearby covered receiver's feet to evade a sack and also an interception. Here's the way the rule reads:

Intentional grounding will be called when a passer, facing an imminent loss of yardage due to pressure from the defense, throws a forward pass without a realistic chance of completion.

He had a chance of completing a pass to Dreesen; the issue is not the accuracy of the pass, it's how realistic of a chance there is at completing it.

and

He wasn't in imminent danger of a sack. He had a pocket and didn't even seem particularly hurried. He stepped and threw.

Awful call.

 
There's a certain running back who dominated the first half of the game. He did not touch the ball on that drive.
See what I was talking about earlier? Don't know what Kubiak is doing sometimes. They throw it underneath to Foster now and what does he do? Only gains 33 yards!
 
That grounding call would be fine if the refs were consistent about it. He was obviously throwing it away on purpose, and he wasn't out of the pocket.

But since they almost never call that when a receiver is anywhere near the ball, they shouldn't have called it that time either.
His purpose doesn't matter. Rivers has at least once thrown at a nearby covered receiver's feet to evade a sack and also an interception. Here's the way the rule reads:

Intentional grounding will be called when a passer, facing an imminent loss of yardage due to pressure from the defense, throws a forward pass without a realistic chance of completion.

He had a chance of completing a pass to Dreesen; the issue is not the accuracy of the pass, it's how realistic of a chance there is at completing it.

and

He wasn't in imminent danger of a sack. He had a pocket and didn't even seem particularly hurried. He stepped and threw.

Awful call.
The chance of completing it was pretty near zero. The only way he would have completed that pass is if he were hit as he released it and the ball popped up in the air nowhere near its intended target (which was the bench on the sideline).I agree it was a terrible call. But it's not a terrible call based on the way the rule is written, IMO; it's a terrible call based on the way it's typically enforced.

 
Last edited by a moderator:
Congrats San Diego, I knew those field goals would come back to haunt us.

Hou on pace for another 8-8 mediocre year. yay...

 
It's November. No surprise that the Chargers are heating up. They simply don't lose in Nov and December, even on the road with guys off the street starting at WR and their #1 offensive threat missing the first game of his career.

Can't say enough about AJ Smith for putting together such a deep roster, or Norv Turner for a brilliant gameplan today.

 
Perfect example of why you should always take the FG when there is plenty of time left in a game, especially if you're ahead. I just don't understand going for it there. If they had another 3 on the board, you don't have to go for the TD on that last drive,

 
Last edited by a moderator:
That grounding call would be fine if the refs were consistent about it. He was obviously throwing it away on purpose, and he wasn't out of the pocket.

But since they almost never call that when a receiver is anywhere near the ball, they shouldn't have called it that time either.
His purpose doesn't matter. Rivers has at least once thrown at a nearby covered receiver's feet to evade a sack and also an interception. Here's the way the rule reads:

Intentional grounding will be called when a passer, facing an imminent loss of yardage due to pressure from the defense, throws a forward pass without a realistic chance of completion.

He had a chance of completing a pass to Dreesen; the issue is not the accuracy of the pass, it's how realistic of a chance there is at completing it.

and



He wasn't in imminent danger of a sack. He had a pocket and didn't even seem particularly hurried. He stepped and threw.

Awful call.
The chance of completing it was pretty near zero. The only way he would have completed that pass is if he were hit as he released it and the ball popped up in the air nowhere near its intended target (which was the bench on the sideline).I agree it was a terrible call. But it's not a terrible call based on the way the rule is written, IMO; it's a terrible call based on the way it's typically enforced.
Yes, it was a terrible call based on the way the rule is written. The nearest defender was three yards away.
 
Yes, it was a terrible call based on the way the rule is written. The nearest defender was three yards away.
He didn't throw it away to stop the clock. He thew it away because he had nobody open. That's not a reason that saves him from a grounding call. (Pretend, for example, that instead of throwing it way out of bounds, he threw it into the ground a few feet in front of him with no eligible receivers anywhere near the area. Would anyone doubt that that was grounding?)
 
Last edited by a moderator:
Yes, it was a terrible call based on the way the rule is written. The nearest defender was three yards away.
He didn't throw it away to stop the clock. He thew it away because he had nobody open. That's not a reason that saves him from a grounding call. (Pretend, for example, that instead of throwing it way out of bounds, he threw it into the ground a few feet in front of him with no eligible receivers anywhere near the area. Would anyone doubt that that was grounding?)
Pretend, for example, he throws it fifteen feet out of the end zone when his receivers are covered but no defender is around him.The rule, as stated, cites imminent loss of yardage due to pressure from the defense as one of the elements of the penalty.
 
Last edited by a moderator:

Users who are viewing this thread

Back
Top