Clock Error
The SEC admitted the refs erred when allowing the playclock to run after an offensive penalty (Alabama had the ball late and was trying to run the clock out).
http://espn.go.com/college-football/story/_/id/11694663/southeastern-co…
Essentailly, the same thing happened near the end of the Michigan - Rutgers game, but I don't remember seeing a big deal made of it. Barring a first down, not getting that extra run-off would have forced Rutgers to punt it back to Michigan.
October 14th, 2014 at 12:12 PM ^
I never played high school I played Midgets than for NMH Prep than college than club. My toolness worked... Your team already was discussing my toolness behavior before the game started therefore I won the battle before it even started. I think the most PIM's I racked up in a season was 44 which is pretty low. Most of it was roughing and stuff after the whistle.
There's still no fighting in college you're suspended for a game after and sometimes more. Jr's and prep is where your talking about that I'd pay a price and trust me I did. I've got some good cuts on my face to show for it. I think the first fight I got in when I was in college the kid just whaled on my head even after he got me down on the ice. I got sitched up under my chin and he got booted.
I think your definition of excessively cheap and mine are different. Mine is within the rules and game itself, you assume I sucker punched people and just ran around like a goon. I never once hurt anyone or did something to someone that other players themselves already do. I was really good at pissing you off. Theres a difference in sticking your leg out because you missed a check and kneeing someone or taps to the ribs back of the legs etc which is what I did. I just did it all game long which is why I said excessive. Most guys do it a few times a game I never stopped. Against the boards and in the front of the net is where I did most of the damage.
Regardless your entiled to your opinion.
I didn't even know who Todd Brost was... Never even heard of the guy. I wasn't scrawny I was just short.
October 14th, 2014 at 12:46 PM ^
You're pretty full of yourself dude. You won nothing. You're just that annoying little jackoff on the other team who thinks he's hot shit because he's "tapping people on the back of the legs."
Annoying little fok is what you are.
October 14th, 2014 at 1:26 PM ^
October 14th, 2014 at 1:11 PM ^
Yeah, when is Andrew Shaw going to get what's coming to him? Oh wait.
October 14th, 2014 at 1:41 PM ^
October 14th, 2014 at 8:36 AM ^
It wasnt a big deal because Michigan is irrelavent at the moment.
October 14th, 2014 at 8:55 AM ^
Sent from MGoBlog HD for iPhone & iPad
October 14th, 2014 at 9:02 AM ^
No but Alabama is
October 14th, 2014 at 9:02 AM ^
October 14th, 2014 at 9:03 AM ^
October 14th, 2014 at 9:28 AM ^
October 14th, 2014 at 10:33 AM ^
October 14th, 2014 at 2:23 PM ^
I guess my intent was obvious. Alabama has racked up some national championships and has only one loss this year, therefore their game has playoff implications.
October 14th, 2014 at 10:37 AM ^
Here's the original discussion on MGoBlog
http://mgoblog.com/mgoboard/clock-rule-ru-illegal-motion-play
From page 54 (FR-54) of the rules:
http://www.ncaapublications.com/productdownloads/FR14.pdf
Unfair Clock Tactics
ARTICLE 3. The referee shall order the game clock or play clock started or stopped whenever either team conserves or consumes playing time by tactics obviously unfair. This includes starting the game clock on the snap if the foul is by the team ahead in the score. The game clock will start on the ready-for-play signal after Team A throws an illegal forward or backward pass to conserve time (Rule 3-3-2-e-14) (A.R. 3-4-3-I-V).
October 14th, 2014 at 9:28 AM ^
Yeah I was freaking out about this after our game. And immediately after that ASU got the ball with 20 seconds left, just like we would have had, and proceeded to pull off the improbable win over USC. Anything can happen. I made a thread on here, but I think it got taken down.
October 14th, 2014 at 9:59 AM ^
The bigger issue in the Rutgers game was the catch for a first down that should have been automatically reviewed, required Michigan to burn a timeout for a review, then was still ruled an incompletion even after conclusive video evidence to the contrary.
October 14th, 2014 at 10:37 AM ^
October 14th, 2014 at 10:49 AM ^
It happened near the black hole which prevents on field viewers from seeing what all 109,001 in the stands and on TV can clearly see.
October 14th, 2014 at 11:55 AM ^
If there's any chance it's an interception they should let it play out when you've got one guy running to the end zone. If it's actually an interception you then either have a TD or a M ball on the fifty (or whatever the spot was) with the play blown dead because of the possibility PSU had thrown an incomplete pass.
With the review system in place they should eliminate a scenario where M actually did intercept but didn't get a TD out of it.
October 14th, 2014 at 12:15 PM ^
When they allowed Hollowell to return it I thought it was because it was a catch and then a fumble. It OBVIOUSLY bounced.
Unless the refs were trying to give the call more leeway to be overturned (calling it an interception instead of a fumble recovery in which a catch would have to be overturned), I don't see how they missed the bounce.
October 14th, 2014 at 12:18 PM ^
I agree with you in this case, but I think they should be really cautious about blowing a play dead in that scenario. If letting this obvious one slide is a symptom of them taking that approach I think they have it right in the big picture.
October 14th, 2014 at 1:54 PM ^
First--I will concede that your view is also the official view. The officiating manuals I could find online indicate that if a replay is in place, the official is encouraged to let the play "play out".
But asking officials to make an incorrect call is where the potential for a huge problem comes into play.
What if the ref thinks one thing happened (an incomplete pass, say) but he doesn't call what he thinks happened? So he lets the play "play out," as though it is a completion and a fumble, but it turns out that there is a technical error and the camera pointing at the play didn't record anything, or wasn't pointed correctly, and no other cameras have a good enough angle to overturn the call--the call that shouldn't have been made in the first place.
So the refs who saw the play correctly as an incomplete pass but intentionally called it incorrectly as a catch & a fumble are now stuck with 2 options: either (1) stick by their incorrect call and look like idiots to the television audience, (2) over-rule their own call as a group and look like idiots to everybody.
October 14th, 2014 at 2:00 PM ^
I don't think there's any disagreeing with your third paragraph. The officials need to make sure that they have those cameras placed correctly and that there are enough angles on the ball that they won't miss anything, especially something obvious like this incomplete pass.
I wouldn't ever advocate intentionally calling something incorrectly, what I would say is that they should need a very high degree of certainty before stopping a player from running into the end zone along with erring on the side of caution. In this case the ball bounced twice and I would have no problem with the official blowing his whistle here, but not at the expense of getting it wrong in the other direction somewhere down the line.
October 14th, 2014 at 10:44 AM ^
The clock error was made in broad daylight w/ everybody looking on in at least two games over the past two weeks. (How many times has it occured but not reached national attention?) No judgment was involved.
The NCAA rule committee needs to send a reminder to all of its officials. Not only is the rule explicit, it should be intuitive also. How did two full crews get it wrong in two weeks?
October 14th, 2014 at 10:32 PM ^
October 14th, 2014 at 10:47 AM ^
The entire Rutgers ref/call situation was a joke. How anyone could think that that wasn't a catch is beyond me. It cost us a TO, and add to that the clock error, and this really is an instance in which the refs seriously screwed Michigan.
October 14th, 2014 at 12:29 PM ^
October 14th, 2014 at 3:00 PM ^