All 11 of Dak's Fumbles Analyzed

Ken

Well-Known Member
Messages
16,598
Reaction score
17,270
1st vs Carolina: 3rd and 7 down 16-8 with 1:39 left: No one open, starts to run to the right at 2.72 seconds, is cut off by a defender and reverses field. Fumbles the ball while being tackled. 3rd and 7 would have been 4th and 16 from our own 16. Didn’t exactly cost us the game but it was a legitimate fumble. I argue the Coverage sack caused this more than anything else.


2nd- Week 4 against Detroit: 2nd and 3 at Dallas 32- Empty set, Dak stepping up into the pocket and while in the act of throwing, has the ball knocked out from a defender at 2.29 seconds. Has the presence of mind to pick it up and throw it away. None of this is his fault and he actually saved the game by making this play as it was just before the 2 minute warning and we were down 24-23.


3rd: week 6 vs. Jacksonville: 2nd and 9 at Jax 32: In shotgun, while performing an RPO with Zeke, the ball looks to be knocked out by Zeke as he was running past on the fake, ball bounces up to Dak and he actually gained a yard.

4th- week 6 vs Jacksonville: 2nd and 7 at Jax 25: haha, again, Dak takes off scrambling after 2.37 seconds…ball slips out of his hand while running and bounces back into his hands for a 7 yard gain and a first down.

5th- Week 7 vs Washington- 4th and 1- Fumbles on a sneak. Totally on Dak and this one pissed me off because I have been screaming for them to utilize the qb sneak because it should be unstoppable and he goes and fumbles it when they try it. Washington recovered.


6th Week 7 vs Washington- 3rd and 14- After 4 seconds trying to find someone open, he gets caught sacked and fumbles into the end zone. Bad fumble, Washington scored on this fumble. I know he was trying to make a play but he can’t take a sack let alone fumble in that situation. 2 bad fumbles this game.

7th- Week 9 vs Tennessee- 3rd and 13- After 3.4 seconds in the pocket, is tackled trying to run away and while trying to fight for yardage, is stripped by Woodyard. Should have done something else after there was no one open at 3 seconds…again…trying to make a play on 3rd and long. No one open…Tennessee recovered.

8th-Week 10 vs. Philly- 3rd and 8- After 3 seconds in the pocket, starts to scramble to the right evading a defender, then pats the ball out of his own hand. Picks it up and throws incomplete. Not the worst thing in the world at all…wish he didn’t do that but no harm, no foul.

9th- Week 12 vs Washington- 2nd and 4- Designed RPO run to right, Fumbles as he is going out of bounds after getting the first down. Watching this, his right foot was already out of bounds and then fumbles…should not have even been a fumble. 1st down…


10th- Week 13 vs N.O.- 3rd and 7 New Orleans 19- Ball is knocked out of his hand by defender while resetting to throw in 2.5 seconds. Recovers own fumble for no gain. Hardly his fault on this one.

11th Week 13 vs N.O.- 3rd and 5 on N.O. 6- Sacked in 2.4 seconds from his blind side. A little more time and no holding by Collins and it is likely a TD to Gallup over the middle. Not much he could do here…imo. Wish he hung onto it but Collins was the problem here…not Dak.


Out of the 11 Fumbles:
  • 5 were turnovers
  • 4 were for positive yards or no gain.
  • 4 were 2.5 seconds or less by a defender.
  • 4 were as a runner
  • 2 are hanging in the pocket too long, what he is bashed for...
  • 1 shouldn't have been a fumble.
Hope this helps clear up the latest fallacy about this qb.
 

adamknite

Well-Known Member
Messages
4,222
Reaction score
800
It's hard for me to blame a QB when he gets hit from his blind side and strip sacked unless he's just holding onto the ball for a good minute... sometimes I think people forget that this game is played against other teams filled with a roster of other NFL talented players. Sometimes those players just make great plays too. A few of those plays I'll put on Dak squarely, but it's not nearly as bad as it's been portrayed. IMHO.
 

Ken

Well-Known Member
Messages
16,598
Reaction score
17,270
There's everyone in the world who understands this, and then there's you.
Yes, the guy who goes and actually breaks down the actual fumbles so we are all singing off the same sheet of music instead of just blindly repeating the "he fumbled 11 times, he sucks" mantra.

He has had some bad ones...most are not though.
 

Ken

Well-Known Member
Messages
16,598
Reaction score
17,270
What difference does it make that 4 were as a runner, he still needs to hold on to the ball. Never seen a qb get so many excuses
The difference is....he gets knocked for being a bad qb because he fumbles "holding onto the ball too long".

It just is a fallacy and I want to make sure that is clear.
 

Ken

Well-Known Member
Messages
16,598
Reaction score
17,270
It's hard for me to blame a QB when he gets hit from his blind side and strip sacked unless he's just holding onto the ball for a good minute... sometimes I think people forget that this game is played against other teams filled with a roster of other NFL talented players. Sometimes those players just make great plays too. A few of those plays I'll put on Dak squarely, but it's not nearly as bad as it's been portrayed. IMHO.
Thank you...this is the point of this thread. I am glad this isn't lost on all..
 

erod

Well-Known Member
Messages
37,883
Reaction score
58,476
Yes, the guy who goes and actually breaks down the actual fumbles so we are all singing off the same sheet of music instead of just blindly repeating the "he fumbled 11 times, he sucks" mantra.

He has had some bad ones...most are not though.
Breaks down? Lol, there's more predetermined bias in that than a campaign speech.

Open. Your. Eyes.
 

G2

Taco Engineer
Messages
24,452
Reaction score
26,199
Other than loss of down and possible yardage, I don't get hung up on fumbles unless they are turned over. There really is no reason other than not holding on to the ball well enough IMO.
It's like I won't blame a lineman for getting pushed into the QB and he throws an INT. It's on the QB.
 

ConstantReboot

Well-Known Member
Messages
11,232
Reaction score
9,892
The difference is....he gets knocked for being a bad qb because he fumbles "holding onto the ball too long".

It just is a fallacy and I want to make sure that is clear.

Our oline needs to protect him better. Or we need to run plays that take less than 2 seconds to develop.
 

Kage

Well-Known Member
Messages
307
Reaction score
660
Other than loss of down and possible yardage, I don't get hung up on fumbles unless they are turned over. There really is no reason other than not holding on to the ball well enough IMO.
It's like I won't blame a lineman for getting pushed into the QB and he throws an INT. It's on the QB.


Even if we recover the fumble, its still bad to have the ball on the ground and a chance at it being a turnover.
 

G2

Taco Engineer
Messages
24,452
Reaction score
26,199
Even if we recover the fumble, its still bad to have the ball on the ground and a chance at it being a turnover.
I'm clearly talking about the fumbles that are NOT turned over.
 
Top