Super Wildcard Weekend Gamethread

DennyDoyle'sBoil

Found no thrill on Blueberry Hill
SoSH Member
Sep 9, 2008
42,297
AZ
Starting that drive with 2:30 and they ran out of time at the 50 with the two minute warning. Awful.
 
You can be lucky without ref interference. But just off the top of my had the Colts have had an interception dropped and a missed fumble recovey that a Colts player fell right on top of. Also two very close sidelines catches that were called complete on the field that led to a TD drive. The Colts also missed a gimme FG and called a toss on 3rd and goal from the 1.
How much of that is actually luck?
 

Pablo's TB Lover

Member
SoSH Member
Sep 10, 2017
5,963
There was 19 secs left at the snap before the TO, but they ran it to 14?
I was confused on that whole frigging sequence. Clock was running, then Bills called TO when I would have let the mistake cost the Colts more time. Ended up working out because the Bills would have had a completion at the 40 for a spike instead of a few incompletions then hail mary.
 

mauf

Anderson Cooper × Mr. Rogers
Moderator
SoSH Member
You can be lucky without ref interference. But just off the top of my had the Colts have had an interception dropped and a missed fumble recovey that a Colts player fell right on top of. Also two very close sidelines catches that were called complete on the field that led to a TD drive. The Colts also missed a gimme FG and called a toss on 3rd and goal from the 1.
No question they benefited from some bad play-calling and execution from the Colts, who won the battle in the trenches on both sides of the ball. Recovering Allen’s fumble is the one big stroke of luck they got. Agree to disagree on the sideline catches — making plays is making plays, and officials getting the calls right doesn’t count as luck, even though it doesn’t always happen. The only reason we’re even talking about the dropped INT was an atrocious on-field call that was reversed on replay; that was just a very nice pass-defense by the DB.
 

Commander Shears

Member
SoSH Member
Jul 24, 2005
1,019
With :28 left on the clock, the clock started when Rivers yelled ‘ready’, two seconds before the snap. The play went out of bounds at 0:21, then kept running down to 0:19. Then the clock started again as soon as the ball was placed, running down to 0:15 at the snap. What the hell?
 

scottyno

late Bloomer
SoSH Member
Dec 7, 2008
11,308
It would have made it to the end zone if the ref didn’t inexplicably mark the first down pick of 2 yards back about 3 yards so it ended up being 2nd and 11 instead of 2nd and 8 (two plays before the Hail Mary).
Apparently, the guy fumbled backwards out of bounds, which explains the yards difference. Doesn't explain the clock starting 5 seconds before they actually snapped the ball though
 

EvilEmpire

paying for his sins
Moderator
SoSH Member
Apr 9, 2007
17,184
Washington
What a terrible last drive. Still, Rivers deserves some credit for getting them back into the game.

But like with the Chargers, not quite enough.
 

shawnrbu

Member
SoSH Member
Jul 14, 2005
39,703
The Land of Fist Pumps
With :28 left on the clock, the clock started when Rivers yelled ‘ready’, two seconds before the snap. The play went out of bounds at 0:21, then kept running down to 0:19. Then the clock started again as soon as the ball was placed, running down to 0:15 at the snap. What the hell?
The clock started after the review when the ref told it to wind.

Pittman fumbled the ball backwards out of bounds. Looks like the clock resumes when the refs spot the ball in that scenario?
 

luckiestman

Son of the Harpy
SoSH Member
Jul 15, 2005
32,622
Sub-60 completion percentage with the kind of protection he got isn’t very good. League-average QB play probably wins this game for the Colts.
Count the easy drops. I have 4 in my mind.
 

Commander Shears

Member
SoSH Member
Jul 24, 2005
1,019
The clock started after the review when the ref told it to wind.

Pittman fumbled the ball backwards out of bounds. Looks like the clock resumes when the refs spot the ball in that scenario?
Ah, I forgot about that replay and that makes sense. I do think Pittman was going forward and they ran two seconds off after he was out though.
 

johnmd20

mad dog
Lifetime Member
SoSH Member
Dec 30, 2003
61,996
New York City
My god, he was awful in that sequence.
Just the worst passes and then a hail mary that was so short, it gave the Bills DBs a running start to pound the ball into the ground, making the ball utterly uncatchable.

That was a pretty big fail after getting a review gift.
 

CFB_Rules

Member
SoSH Member
Nov 29, 2016
1,603
Apparently, the guy fumbled backwards out of bounds, which explains the yards difference. Doesn't explain the clock starting 5 seconds before they actually snapped the ball though
I rewatched it. The line judge threw a bean bag indicating fumble. He ruled a forward fumble out of bounds, by rule the ball is moved back to the spot of contact and the runner is considered down at that spot (inbounds). So the clock was started as soon as the referee got word from the sideline that there was a fumble on the play.
 

AB in DC

OG Football Writing
SoSH Member
Jul 10, 2002
13,633
Springfield, VA
Rivers played well for most of the game, but those last three or four passes were just shit. I don't know what happened there.
 

normstalls

Member
SoSH Member
Mar 15, 2004
4,486
Apparently, the guy fumbled backwards out of bounds, which explains the yards difference. Doesn't explain the clock starting 5 seconds before they actually snapped the ball though
If he did truly fumble backwards out bounds,I think it makes sense. Going backwards out of bounds is considered loss of forward progress (in bounds) and doesn’t stop the clock. (99% sure on this)
 

Kliq

Member
SoSH Member
Mar 31, 2013
22,673
Rivers played pretty well today. Not sure people actually watched the game and are just assuming he was bad because he's Phillip Rivers.