HawkRiderFan wrote:Ok so it wasn't just me. I instantly started having flashbacks to Baltimore 03.
getnasty wrote:Yeah something went wrong there, i was thinking the same thing. I think they should have either started the clock after it was spotted or had a 10 sec run off, or maybe both.
cboom wrote:Wilson is the worst QB I have seen as a Hawks fan. And I have been around long enough to see them all.
SharkHawk wrote:There was also some BS on the clock at the end of the first half. They added 3 seconds at Belicheck's demand that should NOT have been added (at least according to my DVR watching of the play several times). That left a second on the clock that would have allowed the Patsies to kick a field goal if it weren't for the correct grounding call (thank goodness for that). I was surprised the announcers didn't catch it.... all they caught was Fouts saying "there should be 2 seconds on the clock!" I found it quite interesting that a former QB didn't even know the grounding rule. My wife is screaming "grounding grounding and the clock should be gone!" and I'm yelling "GROUNDING GROUNDING TEN SECOND RUN OFF!". Fouts is stroking his luscious beard and calling the field goal already. Goober.
HawkRiderFan wrote:I tried asking Pereira on twiiter but apparrenly he was only watching our game long enough to complain that they got the interference wrong on the Edwards TD and that it should have been offensive interference
The Radish wrote:
Hey Jon, one thing wrong with your analogy. Fouts is now clean shaven. hahahahaha
SharkHawk wrote:There was also some BS on the clock at the end of the first half. They added 3 seconds at Belicheck's demand that should NOT have been added (at least according to my DVR watching of the play several times).
Damn replacement refs! Always screwing things up.
jfurdell wrote:NFL rule reference:
Article 2 Following any timeout (3-36), the game clock shall be started on a scrimmage down when the ball is next snapped,
except in the following situations:
(f) If the game clock is stopped after a down in which there was a foul by either team, following enforcement or
declination of a penalty, the game clock will start as if the foul had not occurred, except that the clock will start on the
(1) the foul occurs after the two-minute warning of the first half;
(2) the foul occurs inside the last five minutes of the second half; or
(3) a specific rule prescribes otherwise.
(i.e. They got it right.)
SalishHawkFan wrote:Well, I get what you're saying about they don't start the clock, but look at the play again and there is no penalty. No second man went in motion. And the flag comes out the moment Brady starts to go down. It's pretty obvious to me that the only reason the ref threw that flag was to have an excuse to stop the clock and buy NE more time. It's not like we Seahawk fans haven't seen this kind of manipulation by the refs over and over for decades now. That's why I immediately suspected what was going on and that's why I wasn't surprised when I went back on DVR and saw it was so obvious.
I also have it DVR'd and watched it again. The penalty was for illegal motion; the player in motion #84 was moving forward at the snap (hey look at that, it's Branch). There are two flags; the first one comes from the wing official on the near side of the field (the side Branch was on) and it's in the air before Brady was pressured. The other wing official on the far sideline does have a late flag; it's possible the man in motion away from him is supposed to be his responsibility.