NFL: Interception a bad stat.

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
Classic example is the last 2 plays in the Eagles - Chargers game.

brees throws a pass, his WR has it slip thru his hands to an eagles defender.

NEXT play, McNabb throws a pass, his WR catches it and then gets hit and it pops out of his hands into a chargers defenders hands.

sucks that the QB gets blamed for both of those.
 

KLin

Lifer
Feb 29, 2000
30,426
744
126
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.
 

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
Originally posted by: KLin
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.

agreed, an interception is an interception, but there should be a stat or category of int that allows you to assign the int to either the WR or the QB.

 

KLin

Lifer
Feb 29, 2000
30,426
744
126
Originally posted by: PlatinumGold
Originally posted by: KLin
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.

agreed, an interception is an interception, but there should be a stat or category of int that allows you to assign the int to either the WR or the QB.

I disagree since the WR didn't throw the ball.
 

hdeck

Lifer
Sep 26, 2002
14,530
1
0
yeah thats one reason why i hate people that live and die by stats when you try to engage in an argument with them
 

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.

agreed, an interception is an interception, but there should be a stat or category of int that allows you to assign the int to either the WR or the QB.

I disagree since the WR didn't throw the ball.

so if the receiver cradles the ball but before his two feet are down he gets hit and the ball pops out, that's automatically the QB's fault?? :roll:

or how about a really really catchable pass, the kind these guys catch 9 / 10 times, the wr lets it slip thru his hands to a defender and the defender INT's it, that's the QB's fault?

i understand a defender deflecting it being held against the qb, but when your own WR deflects it to the defender than that's not the QB's fault.

 

KLin

Lifer
Feb 29, 2000
30,426
744
126
Originally posted by: PlatinumGold
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.

agreed, an interception is an interception, but there should be a stat or category of int that allows you to assign the int to either the WR or the QB.

I disagree since the WR didn't throw the ball.

so if the receiver cradles the ball but before his two feet are down he gets hit and the ball pops out, that's automatically the QB's fault?? :roll:

or how about a really really catchable pass, the kind these guys catch 9 / 10 times, the wr lets it slip thru his hands to a defender and the defender INT's it, that's the QB's fault?

i understand a defender deflecting it being held against the qb, but when your own WR deflects it to the defender than that's not the QB's fault.


Who said anything about fault? That's the rule. If the WR never had possession of the ball, and it ends up in the hands of a defender, it's an interception. blame it on the WR, but the QB still gets the pick on him since he threw the ball. I don't see anything wrong with it.
 

Argo

Lifer
Apr 8, 2000
10,045
0
0
Well, acording to the same logic TD is a bad stat as well. How many times have we seen a QB throw a 5 yard pass and then the receiver makes 3 guys miss and run it 50 yards for a TD?
 

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.

agreed, an interception is an interception, but there should be a stat or category of int that allows you to assign the int to either the WR or the QB.

I disagree since the WR didn't throw the ball.

so if the receiver cradles the ball but before his two feet are down he gets hit and the ball pops out, that's automatically the QB's fault?? :roll:

or how about a really really catchable pass, the kind these guys catch 9 / 10 times, the wr lets it slip thru his hands to a defender and the defender INT's it, that's the QB's fault?

i understand a defender deflecting it being held against the qb, but when your own WR deflects it to the defender than that's not the QB's fault.


Who said anything about fault? That's the rule. If the WR never had possession of the ball, and it ends up in the hands of a defender, it's an interception. blame it on the WR, but the QB still gets the pick on him since he threw the ball. I don't see anything wrong with it.

Since the QB threw the ball, no matter how perfect in timing or location but because the WR couldn't hang on to the ball the QB gets a negative stat against him? STUPID.


obviously reading is not a strong suit for you.

yes, i did say who was at fault. the op was about that.

Classic example is the last 2 plays in the Eagles - Chargers game.

brees throws a pass, his WR has it slip thru his hands to an eagles defender.

NEXT play, McNabb throws a pass, his WR catches it and then gets hit and it pops out of his hands into a chargers defenders hands.

sucks that the QB gets blamed for both of those.



 

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
Originally posted by: Argo
Well, acording to the same logic TD is a bad stat as well. How many times have we seen a QB throw a 5 yard pass and then a receiver maked 3 guys miss and run it 50 yards for a TD?

you almost got it, but WR get credit for catching TD passes, yes or no?


do WR get blamed AT all for INT's? NO.

hence your logic is flawed.
 

KLin

Lifer
Feb 29, 2000
30,426
744
126
Originally posted by: PlatinumGold
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.

agreed, an interception is an interception, but there should be a stat or category of int that allows you to assign the int to either the WR or the QB.

I disagree since the WR didn't throw the ball.

so if the receiver cradles the ball but before his two feet are down he gets hit and the ball pops out, that's automatically the QB's fault?? :roll:

or how about a really really catchable pass, the kind these guys catch 9 / 10 times, the wr lets it slip thru his hands to a defender and the defender INT's it, that's the QB's fault?

i understand a defender deflecting it being held against the qb, but when your own WR deflects it to the defender than that's not the QB's fault.


Who said anything about fault? That's the rule. If the WR never had possession of the ball, and it ends up in the hands of a defender, it's an interception. blame it on the WR, but the QB still gets the pick on him since he threw the ball. I don't see anything wrong with it.

obviously reading is not a strong suit for you.

yes, i did say who was at fault. the op was about that.

Classic example is the last 2 plays in the Eagles - Chargers game.

brees throws a pass, his WR has it slip thru his hands to an eagles defender.

NEXT play, McNabb throws a pass, his WR catches it and then gets hit and it pops out of his hands into a chargers defenders hands.

sucks that the QB gets blamed for both of those.


Apparently you can't have a civil discussion without throwing out insults. :roll:
 

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
Originally posted by: PlatinumGold
Originally posted by: KLin
That's the rule. If Greg lewis gets both his feet down, then he gets hit and the ball comes loose it should be a fumble instead of an interception.

agreed, an interception is an interception, but there should be a stat or category of int that allows you to assign the int to either the WR or the QB.

I disagree since the WR didn't throw the ball.

so if the receiver cradles the ball but before his two feet are down he gets hit and the ball pops out, that's automatically the QB's fault?? :roll:

or how about a really really catchable pass, the kind these guys catch 9 / 10 times, the wr lets it slip thru his hands to a defender and the defender INT's it, that's the QB's fault?

i understand a defender deflecting it being held against the qb, but when your own WR deflects it to the defender than that's not the QB's fault.


Who said anything about fault? That's the rule. If the WR never had possession of the ball, and it ends up in the hands of a defender, it's an interception. blame it on the WR, but the QB still gets the pick on him since he threw the ball. I don't see anything wrong with it.

obviously reading is not a strong suit for you.

yes, i did say who was at fault. the op was about that.

Classic example is the last 2 plays in the Eagles - Chargers game.

brees throws a pass, his WR has it slip thru his hands to an eagles defender.

NEXT play, McNabb throws a pass, his WR catches it and then gets hit and it pops out of his hands into a chargers defenders hands.

sucks that the QB gets blamed for both of those.


Apparently you can't have a civil discussion without throwing out insults. :roll:

i'm always civil to people who read the OP before responding, but to people who try to get away with one liners, no, i'm not civil to them.
 

Argo

Lifer
Apr 8, 2000
10,045
0
0
Originally posted by: PlatinumGold
Originally posted by: Argo
Well, acording to the same logic TD is a bad stat as well. How many times have we seen a QB throw a 5 yard pass and then a receiver maked 3 guys miss and run it 50 yards for a TD?

you almost got it, but WR get credit for catching TD passes, yes or no?


do WR get blamed AT all for INT's? NO.

hence your logic is flawed.

WR getting a TD can be easily called. Placing an INT on WR is subjective. In the Eagles games both QBs put their receivers in bad situations on those 2 Ints. It's just too hard to call when an INT is receivers fault and when not. And considering that this call doesn't affect the game NFL will never bother with this.

They probably can get an official scorer, like in baseball but I don't think he'll be used as much in NFL.
 

Ready

Golden Member
Jan 16, 2003
1,830
0
0
And then there are those times when the WR makes those one handed grabs and the QB gets full credit for those also.
 

pyonir

Lifer
Dec 18, 2001
40,856
321
126
Originally posted by: hdeck
yeah thats one reason why i hate people that live and die by stats when you try to engage in an argument with them

You mean like PlatinumGold?

;)
 

shimsham

Lifer
May 9, 2002
10,765
0
0
what about passing yards? say a qb passes for 400yds, yet not all those yards were in the air. ie: ball in air for 10yds, wr runs for 15, 25 passing yds on qbs stats.

its a trade-off.