That was a terrible, terrible call. Yes, I know the rule says you're not allowed to throw the ball up in the air. But seriously. You let that one slide. The kid just made a series of incredible plays, took the game into his own hands and took the ball into the endzone. The kids are not robots. He DESERVED to celebrate that touchdown. That wasn't right. The players aren't robots. The referees shouldn't be either. Give me a break about what the rule says. You let offensive holds slide all the time. You don't make a flimsy unsportsmanlike conduct call like that at the end of a game, and instantly wipe out what should have been an amazing clutch performance to tie the game. It was wrong.
I say if you make that call in the first quarter of the game, keep making it. That goes for fouls in basketball or strikes in baseball. Keep it consistent!
that flag would have been thrown against any college team, he didn't casually throw the ball behind his shoulder. he threw it as hard as he could into the air... 100% agree with the call.
<object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/Ap6Kn0dkbyY&hl=en&fs=1"></param><param name="allowFullScreen" value="true"></param><embed src="http://www.youtube.com/v/Ap6Kn0dkbyY&hl=en&fs=1" type="application/x-shockwave-flash" allowfullscreen="true" width="425" height="344"></embed></object>
Again, we need an edit button. Every so often I get brain farts. I hate having grammatical errors. **officiating**
They never showed a full-speed replay, but in full speed it took about 5 seconds from snap-hitting-hands to QB-falling-down. The sideline replay showed that time taking 6 seconds. The QB throws the ball in the air, and you can see it hit the QB and #15 about 3.25 seconds later. That's roughly 2.7 seconds in real time -- or 1.35 seconds up and 1.35 seconds down. Plug 1.35 into d = 0.5gt^2, and you get a height of 29 feet. That's "high in the air" by any standard, I think. IMHO, the flag was justified. (Actual times calculated in my head, but it should be roughly accurate.)
Well both Barry Switzer and Jimmy Johnson agree it was a terrible call. And after seeing the replay for myself, I would agree too. He didn't spike it, hell he didn't even toss it high in the air...he tossed over his shoulder after scoring a potential game-tying touchdown. That is a no-call and the official who called it should be ashamed.
How about you just make a 17 yard extra point? I didn't realize it was the refs fault they got the kick blocked.
Not to be totally nitpicky, but a regular PAT is about 20 yards. This one was closer to 34 or 35 yards due to the penalty. Clearly not a gimme, especially in college.
Ah - yeah I guess I got lazy with that one. Regardless, they didn't even get it past the line. I understand blaming the refs for the call.. but you can't blame the refs for getting your PAT blocked.
It was the correct call. Take issue with the stupid rule, not the enforcement of it. Oh, and that was still a very makeable PAT. Pardon me if I don't play my tiny violin.
Very high throw. Ref made the right call. This was not some little toss. He flinged (flung?) that thing really, really high. Let's say the refs don't make the call. What happens if they don't? BYU will review the tape afterwards, it's highly unlikely that THEY would miss the toss, and they would probably file some sort of protest with the NCAA. NCAA reviews the tape, and it's highly unlikely that THEY would miss the toss, so the ref would get a talking-to. The ref's know there is oversight in black-and-white cases like this (and, if you review the tape, it's black-and-white: he tossed it VERY high in the air), and they know they have to make the call.
