Anyway...I know I said it the last 2 weeks, but again...I don't see the Ravens winning next week whether they play Pittsburgh or San Diego. 3 road wins with a rookie QB and coach would be just too improbable.
Anyway...I know I said it the last 2 weeks, but again...I don't see the Ravens winning next week whether they play Pittsburgh or San Diego. 3 road wins with a rookie QB and coach would be just too improbable.
Poor poor Weltall, I can't wait to hear his excuse for this one.
I agree the no call on the Delay of Game was terrible. It was a classic Ravens victory though, force turnovers on defense and don't make mistakes on offense. It was a good game and I enjoyed it despite it being dull for a while.
I didn't hear any story about a brick being thrown.
Worst season ever for the officials.
The call on the delay of game would have been hard to blame on the referees. Until the clock is at 0 for 1 full second, there's still time there.
The lack of call on Flacco stepping out in the endzone though should have been reviewed if it's within the rules.
Did anybody else notice earlier in the game when the Titans got 2 3rd downs one after another? I might have just been seeing things though, since the announcers didn't seem to notice it either. It was on that drive that LenDale coughed it up in the red zone
edit: I thought he stepped out of the back of the end zone too lol. Completely forgot about that one
The turnovers lost them the game, the delay of game no-call COST them the game. I think there's a distinct difference. It was a terrible call on a crucial play.
You're making a huge deal out of half a second Tyche. That type of no call happens all the time in football and the ref literally has to judge by himself how long that final second is.
It's usually snapped within a half-second of hitting zero. Watching that in real time was every bit of a 2 second delay. I realize that it's snapped at zero a lot, especially with teams like Indi, that clock was just at zero for a REALLY long time. It was more than a half a second. I'd venture all of 2.
If the play clock showing 0 doesn't mean there's no time left, the play clock is useless.
Play clock was beat to death last week on espn. Bottom line that they got to was that the ref has to look at the play clock to see the 0 THEN look back and see if the ball has been snapped. So the team can go over a second and not get a call because the ref has to be the one to call it.
The only reason the ball can be snapped after 0 is because of the human element. The ref must look at the QB, then look at the clock, then look back to the QB to see if the ball is snapped. Make it reviewable or a giant siren would slove that problem.
Damn alex, you can judge seconds in slow motion with no comparison of how slow the "slow motion" is other than "super"? You really are brilliant...in the real time they just showed on fox, it was well over a second. ESPN will throw us a ticker on sometime I'm sure, and we'll have it to a 1/10th of a second.
^ This
I was wrong about the Ravens winning by Todd Heap but was right about the titans being able to "west coast" all over the Ravens D. I still think that if they had went to Heap more it would have been different, but meh.
After everything you can't deny that the Ravens deserved to be in that game. You can't deny that the Ravens were "head to head","Toe to toe" with the BEST OF THE AFC! I give the Titans that, but the best don't hand the game over in penalties. That is why the Ravens advance. The titans had plenty of chances to win, and didn't