Quote:
Originally Posted by BWillie
True. But there should be a stat of "should have been interceptions + interceptions that are the QBs fault".
The Kelce one wouldn't apply because the stat tracker isn't going to know the exact route he was supposed to run but perhaps a stat exists that removes tipped ints that the WR or TE just bobbled up into the air. Also just because the defender had the ball hit him in the chest and didn't catch it the exact same as the ones they do catch. They are the same bad throw. Not acknowledging the difference is being results oriented.
My hope is QBR reflects these types of things (I know QB rating does not) but I doubt it.
There is also a HUGE difference in WHEN the interceptions take place. If you are winning 24-17 in the 2nd Quarter on 1st and 10 and a QB forces one. Horrible decision. If you are down 31-10 with 2 minutes left in the 3rd quarter and it's 3rd and 9 and you try to get one in there to give your team a chance. The fact that the QB threw the ball to try to win the game but it was intercepted doesn't even matter. It's actually probably a GOOD THING because a QB caring about their stats just takes the quick out for an easy 4 yards yet lowered the probability of winning the game.
Basically the interception stat is a horrible stat without context.
|
There is a subject element to ESPN's QBR so they may.