2Squirrels1Nut
Footballguy
Terrible grounding call. The TE was in the area, and he wasn't throwing to avoid a sack - he had a good pocket.
More than he's paying his dermatologist?What kind of spot was that? How much is Norv paying the refs?
That was a joke. Refs deciding this game.Schaub called for a BS intentional grounding.
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: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.
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!There's a certain running back who dominated the first half of the game. He did not touch the ball on that drive.
too bad the only time they do it is when they're down and need to move in a hurry.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!There's a certain running back who dominated the first half of the game. He did not touch the ball on that drive.
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.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: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.
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.
I don't see any basis to overturn that. That should be the game.
Don't know why they are gonna review it, we all know all calls go to the Chargers this game.
Well this was a fraudulent win for the Chargers here. Anyone who watched the game knows that.
We've had enough fraudulent losses, I don't careWell this was a fraudulent win for the Chargers here. Anyone who watched the game knows that.
Thought about that this morning as well. Think we have to pull for the Silver and Black.I don't know whom to root for in the KC-OAK game.
You're conceding a TD there?Again, please remove that Lightning Bolt from your profile. You're obviously not a Charger fan.Wow... Andre Johnson's knee saves the Chargers from a last second loss. Assuming the INT stands.
Yes, it was a terrible call based on the way the rule is written. The nearest defender was three yards away.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.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: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.
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.
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?)Yes, it was a terrible call based on the way the rule is written. The nearest defender was three yards away.
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.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?)Yes, it was a terrible call based on the way the rule is written. The nearest defender was three yards away.