Monday, February 4, 2013

Catchable

I still don't quite know exactly where I stand on the  most infamous "non-call" in Super Bowl history.

But I know this: do NOT call that ball "un-catchable."

No, no. NO sir. Very, very, catchable. In fact, might have been another PERFECT throw from the kid.

9 comments:

  1. The last 3 minutes of this game were just terrible as far as officiating goes.

    The non-call was awful and the holding by the Ravens' offensive line on the safety play was ridiculous.

    ReplyDelete
  2. I have no problem with the no call on the pass because every receiver in the game immediately objects when he remotely thinks he was interfered with and Crabtree did not in this case. As far as the holds on the safety, I'm sure they were told to to waste more time. If they are taking a safety anyway, who cares if there are 10 holding penalties in the endzone on that play?

    ReplyDelete
  3. holding penalty in endzone doesn't matter, it would of been called a penalty in the endzone and a safety...same result as running out of bounds!

    ReplyDelete
  4. I think the no-call on last play was defensible as both players were being "handsey". Did anybody else feel, however, that Baltimore was offsides a bunch in fourth quarter? Seems they were through mighty quick on a number of snaps. Might have been exceptional timing but I also think maybe some missed offsides calls?

    ReplyDelete
  5. In my opinion, rb is right on the last throw in the endzone. Yes, there was a lot of contact from the Raven, but there was just as much on the part of the 49er.

    Holding is such a BS call for the simple fact that the rule's definition changes from play to play -- and that if the refs wanted to, they could find holding on every play. That being said, the only change the holding play on the safety would do is add a few seconds back on the clock.

    Either way, it really comes down to this -- if the 49ers could have scored more than 6 points in the first half, they could have easily won this with their performance in the second half. I was pleasantly surprised at how back and forth this game was.

    ReplyDelete
  6. Thank goodness this game wasn't decided by a flag on an arguable situation. Let 'em play. The call that sucked wasn't the officials non-call, it was the play call.

    ReplyDelete
  7. Or how about the wasted timeout? As Czabe says all the time...never call a timeout to save the 5 yards. This was just 1 play. How about the blatant holding non-calls on the Niners earlier in drive. Twice Niner lineman tackled Ravens from behind. No flag. Very bad one on the dropped pass play to Vernon Davis. I say good non-call on the play in question. And, Niners got away with one on the out of bounds late hit on Flacco on their last 4th quarter drive. So many plays. Lots of ifs and buts. Ravens win. Quit complaining Niners fans. Pitchers and catchers report for your World Series Champs very soon.

    ReplyDelete
  8. You're completely wrong, Czabe! Crabtree was looking for a back shoulder pass and Kaep threw a fade. That's why Crabtree initiated contact and pushed off (ie: see Ravens CB on ground). NO Call = Good call

    Boom..Roasted

    ReplyDelete
  9. Watching the reply, the contact is initiated at the 2 yard line, which is within the 5 yard contact zone. Then, once the ball was in the air, Crabtree gets his hands on the back of Smith's helmet and pushes him to the ground. If anything Crabtree should have had a flag thrown on him. I think the no call was the right call in that situation. Ironically, I think if Crabtree hadn't been fighting with Smith he would have gotten a PI call.

    The sadder thing was Jimmy Hard Paw's play selection. Had he not blown his timeouts SF would have had many more options, and personally, I think that the passes were the wrong calls. SF was in the same situation in the NFC championship game vs. Atlanta, and they ran the read option to Gore and scored out of it.

    ReplyDelete