Controversial calls

Submitted by 615Wolverine on
First INT Bamas CB threw our WR out and there was no flag. Gardners play where he was interfered and they waived off pass interference was bs. Interfering with the punter was also bs. That face mask of Rawls early in the first half was not called. Countess play where he got hurt was the same exact play where Floyd hit a Bama player and was called for a block in the back. Yet Countess play there was no flag??? Bamas a good team but if we had gotten couple these calls it would been a differant story.

koolaid

September 2nd, 2012 at 5:40 AM ^

The refs are responsible for many of those 30 points.  Reason: momentum.  They killed our momentum on a bad call at the beginning of the game, no-called on two block in the backs on our punts, giving away crucial field position, and generally helped Alabama along until they had a hefty lead.  Who knows what would have happened if it was called fair?  

Muttley

September 2nd, 2012 at 11:48 AM ^

That and eight yards and a cloud of turf. The good news is that there aren't any Alabamas on the remainder of our schedule. Denard's effectiveness is proportional to the square of the space he operates in, and that's the minimum he'll see all year. (In fact, I think Borges was trying to avoid getting Denard pounded. Didn't work out so well on the pick.)

jmblue

September 2nd, 2012 at 1:09 AM ^

He's talking about the play where Roundtree was shoved out of bounds by the Alabama corner who then picked off Denard's pass.  Obviously, the refs are not the primary, secondary or tertiary reason we lost, but that was about as bad a PI no-call as I've seen.

 

Space Coyote

September 2nd, 2012 at 1:14 AM ^

I'm pretty sure the CB shoved Roundtree before the pass was made, which is allowed, and therefore not PI. I was angry about it at first too, but take a second look.

I thought the most annoying call was the block in the back call on the long kick return. The ref was like one of those basketball refs that waits to blow the whistle depending on if the shot goes in or not. Once he saw Northfleet break a long return, he threw the flag about 10 seconds late.

MGoRob

September 2nd, 2012 at 12:42 AM ^

While in nearly every game there is going to be a miss call or two for either team, the blatant lack of calls on the multiple helmet-to-helmet hits I saw was egregious.  Alabama defenders were leading with their helmets all night.  I was outraged.

At least it wasn't the Sun Belt refs calling the game.  That was worst.  And a closer game.

StraightDave

September 2nd, 2012 at 12:45 AM ^

the defender can hit the receiver beyond 5 yards as long as the ball is not in the air.  So the play by the Bama DB was legit.

1464

September 2nd, 2012 at 12:47 AM ^

Two things.

That was like 7-8 yards past the line. 

Also, if the ball wasn't in the air, Denard must have led him in assumption that he could crab walk at a dead sprint.

WolverineMac

September 2nd, 2012 at 12:47 AM ^

We got beat by a better team and calls or non calls mattered little. Our lines were abused and that was the game.

We just got handed a blueprint for where we want to be and how far we need to go to get there. Two years. Go Blue!

94-99

September 2nd, 2012 at 12:54 AM ^

Michigan got destroyed period.  No calls could have helped.  The only thing that would have helped was a running clock.  I love Michigan, and think the season will end fine, but this post makes me sick.  We got man handled from start to finish.  Saban is slimy, but he is still light years ahead of Hoke.

Nothing.But.10ve

September 2nd, 2012 at 12:59 AM ^

Agreed with your post until the end.  I do not think games like this reflect the coaches too much.  This was literally men vs. boys.  I would take Hoke over any coach in the country, that does not change after tonight.  No judgments can be made about him until his talent (the back to back to (future) back top-5 recruiting class talent) is on the field.  

Chippewa Blue

September 2nd, 2012 at 1:04 AM ^

I mean yeah the refs were god awful but if we get some of those calls it's what? 34-14? Or something like that. There were quite a few super annoying calls though, would of pissed me off a lot more if it was a tight game and they would of made a difference.

South Bend Wolverine

September 2nd, 2012 at 1:07 AM ^

Not getting the hate on this post.  The refs *were* horrendous.  Repeatedly missing blocks in the back on punts all the way up until we did one is just one thing on the list.  That said, with good officiating we would still have lost by 3 scores.  It's just frustrating to watch.

Space Coyote

September 2nd, 2012 at 1:13 AM ^

Defenders can make contact with the offensive player as far as they want downfield, as long as the ball isn't in the air. The first pick, the WR got thrown before the ball was thrown.

I, too, thought the refs were pretty bad, mostly in 'bama's favor, but they were pretty bad both ways. That roughing the passer call was helpful. Denard had just thrown the ball and was hit in the chest, bad roughing call IMO.

In the end, the game wasn't even close, and these threads are annoying and embarassing.

Michigan_Mike

September 2nd, 2012 at 1:39 AM ^

Agreed. If this truly is the rule then every defensive back would be shoving players down regularly.

It was a penalty and a game changing one. Unfortunately a call there would not have saved us from a beating, but it might have brought the score significantly closer. It would have at the very least taken a touchdown away from them.

Space Coyote

September 2nd, 2012 at 1:55 AM ^

"Defensive pass interference is contact beyond the neutral zone by a Team B player whose intent to impede an eligible opponent is obvious and it could prevent the opponent the opportunity of receiving a catchable forward pass. When in question, a legal forward pass is catchable. Defensive pass interference occurs only after a legal forward pass is thrown. It is not defensive pass interference:

 
3. When a Team B player legally contacts an opponent before the pass is thrown"
 
Trust me, it's not a penalty to make contact downfield before the ball is thrown. It's annoying that you act like you know the rule and make a claim about it being a game changing no-call when you don't actually know the rule. It's fine to say "I think it's a penalty" and not be so declaritive, but quit spreading false information and teaching other fans incorrect information, it makes our fanbase look stupid. Stating it like you know when you don't is annoying ignorant.
 
By the way, This also explains why DG should have got a PI call, because it is questionable if that ball would have been catchable if not for the contact. There are a few exceptions, such as you can't tackle the guy (defensive holding) and you can't charge at a guy and just pop him after one yard, but neither of those apply here, when the defender was running in stride with the WR and shoved him.

caup

September 2nd, 2012 at 12:05 PM ^

A DB CANNOT jack a wide receiver OFF HIS FEET (!) while he's running a pass route, regardless of wether the ball is released yet.  And since it was an obvious pass play and Denard was in the procees of throwing the ball TO THIS WR that either gets called 100 PERCENT OF THE TIME or it is a BLOWN NON-CALL 100 PERCENT OF THE TIME.

Space Coyote you are not a football ref, so just stop it. You are wrong here. Move along. We get killed by 3 scores regardless.