header pic

Perhaps the BEST B1G Forum anywhere, here at College Football Fan Site, CFB51!!!

The 'Old' CFN/Scout Crowd- Enjoy Civil discussion, game analytics, in depth player and coaching 'takes' and discussing topics surrounding the game. You can even have your own free board, all you have to do is ask!!!

Anyone is welcomed and encouraged to join our FREE site and to take part in our community- a community with you- the user, the fan, -and the person- will be protected from intrusive actions and with a clean place to interact.


Author

Topic: Terrible Calls That Benefitted Your Team

 (Read 2871 times)

Kris60

  • All Star
  • ******
  • Default Avatar
  • Posts: 2514
  • Liked:
Terrible Calls That Benefitted Your Team
« on: January 23, 2019, 01:09:47 PM »
I think several years ago I started this exact thread but it was quite a while ago and it’s an interesting topic to me.  Fans can typically rattle off a laundry list of botched calls that hurt their team but the list gets much shorter if you ask them to list bad ones that were beneficial.  Here are three (two football, one basketball) that come to mind for me.

1. 2005 vs. Louisville- This has become a fairly iconic game in WVU history.  The Mountaineers erased a 24-7 4th quarter deficit  and went on to win 46-44 in triple OT.  It was also sort of the unofficial coming out party for the White/Slaton duo for WVU.  But the win may not have happened without a botched call on an onside kick in the 4th.  The kick was popped in the air and never touched the ground and the UL kid who tried to field it was hammered by WVU players and the Mountaineers recovered. By rule any kick that doesn’t touch the ground the receiving team has to have an opportunity to field it.  A flag was initially thrown but then picked up.

2.  2006 vs. Rutgers.- Another pretty significant win in the Rich Rod era was another triple OT classic against one of the best teams in RU history.  But in the 2nd quarter deep in RU territory Steve Slaton appeared to fumble and a RU defender scooped it up and was running by himself to the end zone when whistles blew the play dead.  For whatever reason, the play wasn’t reviewed and WVU ran another play.  Afterwards, ESPN showed the play again and it was clearly a fumble that should have resulted in a Rutgers TD.

3. 2015 vs.Kansas- Down 61-60 to KU in the final seconds WVU Point Guard Juwan Staten executed a beautiful spin move on a drive to the basket and finished with a layup that proved to be the game winner for the Mountaineers.  But one of the reasons it was so pretty was that Staten clearly took 3 steps after picking up his dribble.  It should have been a walk and KU ball.

Anyone got any for their teams?

Brutus Buckeye

  • Hall of Fame
  • *****
  • Posts: 11235
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #1 on: January 23, 2019, 01:13:04 PM »
I'll defer to mcterps
1919, 20, 21, 28, 29, 31, 34, 35, 36, 37, 42, 44
WWH: 1952, 54, 55, 57, 58, 60, 61, 62, 63, 65, 67, 68, 70, 72, 74, 75
1979, 81, 82, 84, 87, 94, 98
2001, 02, 04, 05, 06, 07, 08, 09, 10, 12, 13, 14, 15, 16, 17, 18, 19

ELA

  • Global Moderator
  • Hall of Fame
  • *****
  • Posts: 20305
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #2 on: January 23, 2019, 01:29:05 PM »
  • Not a singular call, but a series of non-calls in a game that meant little to MSU but everything to Iowa, a BTT Quarterfinal back in maybe like 2014?  MSU was the #1 seed and Iowa was the #8 and needed a win to get into the tourney, and they simply didn't call like 4 MSU fouls in the final couple of minutes.
  • Another basketball one, MSU-Illinois, the officials went to the monitor and called a common foul on Illinois.  It was a foul, but you can't go back and review for a common foul.  I think the resulting free throws allowed MSU to cut the deficit from 3 to 1 in the final minute.
  • MSU trip of Desmond Howard on a 2 point conversion in 1990 that allowed MSU to upset #1 UM
  • Pitt got called for a phantom hold in 2007 that negated a late go ahead TD, that allowed MSU to hold on and win

SFBadger96

  • Starter
  • *****
  • Default Avatar
  • Posts: 1243
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #3 on: January 23, 2019, 01:31:23 PM »
I like this topic, but I can't think of examples. Getting away with one doesn't sear itself in the memory the same way getting hosed does.

Entropy

  • Starter
  • *****
  • Posts: 1432
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #4 on: January 23, 2019, 01:32:13 PM »
vs MSU... WR ran out of bounds and came back for a big play on the drive that ended up winning the game.   But I'd never publicly admit it.

MarqHusker

  • Team Captain
  • *******
  • Default Avatar
  • Posts: 5502
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #5 on: January 23, 2019, 01:54:41 PM »
I'll select a different MSU game, 2012. At East Lansing,  In a game with a lot of PI calls on both sides.   Darqueze Dennard got flagged for it in the final 20 seconds covering Kenny Bell. I had a great vantage standing very low in the sideline section near the 10 yard line.  It kept drive alive and Nebraska scores a TD w 6 seconds left to win by 4.  T Mart ran wild and threw like shit that day.  A normal game I guess.  Maxwell was pretty awful too. I think Bell had at least 35 carries.

NickSmith4Three

  • Red Shirt
  • ***
  • Posts: 193
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #6 on: January 23, 2019, 02:44:18 PM »
Daniel Dufrene definitely fumbled on his long run against OSU in '07.

847badgerfan

  • Administrator
  • Hall of Fame
  • *****
  • Posts: 25181
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #7 on: January 23, 2019, 04:19:56 PM »
I like this topic, but I can't think of examples. Getting away with one doesn't sear itself in the memory the same way getting hosed does.
Roughing the punter doesn't ring a bell?
U RAH RAH! WIS CON SIN!

SFBadger96

  • Starter
  • *****
  • Default Avatar
  • Posts: 1243
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #8 on: January 23, 2019, 04:22:39 PM »
Running into the punter does, but that was a good call. A tough one for MSU, but the right one.

Similarly, the Kyle Orton fumble that Scott Starks returned was a touch call for Purdue, but the right one.

I did see some Miami fans thought the Badgers got away with a lot of holding in the 2018 Orange Bowl, but that's not really what this post is about (I don't think).

Hmm, a little googling shows a lot of remarks about Davidson taking/embellishing "charges" in basketball.
« Last Edit: January 23, 2019, 04:30:47 PM by SFBadger96 »

847badgerfan

  • Administrator
  • Hall of Fame
  • *****
  • Posts: 25181
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #9 on: January 23, 2019, 04:31:44 PM »
Running into the punter does, but that was a good call. A tough one for MSU, but the right one.

Similarly, the Kyle Orton fumble that Scott Starks returned was a touch call for Purdue, but the right one.

I did see some Miami fans thought the Badgers got away with a lot of holding in the 2018 Orange Bowl, but that's not really what this post is about (I don't think).
Running, yes. I still feel dirty about that one. As for Orton.. Starks had a lot of face mask on that play. Big break there. Screw Miami.
U RAH RAH! WIS CON SIN!

grillrat

  • Player
  • ****
  • Default Avatar
  • Posts: 591
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #10 on: January 23, 2019, 04:40:10 PM »

Similarly, the Kyle Orton fumble that Scott Starks returned was a touch call for Purdue, but the right one.

Cough Cough FACEMASK Cough

For basketball, I can freely admit there have been a few times that Purdue has benefitted from a call.  The game @ Michigan last year was a big one (Haas and the Michigan defender were tangled up and the call went against Michigan, could have gone either way).  There was also that game in Madison in Robbie Hummel's first or second year where Badger fans swear that Hummel fouled the player going to the basket in the final seconds of the game, but it was a no-call.  That was back in that time period where the Badgers NEVER lost in the Kohl Center (though since there was never a call on Krabby's concussion-inducing-elbow-to-the-face of Lewis Jackson, I'll call those two a wash).
In football.....Ummmmmm…..
...Hmmmmmm…..
Has Purdue football ever benefitted from a call that I thought was "getting away with one"?
I don't think that's allowed. :49:

mcwterps1

  • All Star
  • ******
  • Posts: 3152
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #11 on: January 23, 2019, 08:31:07 PM »
I'll defer to mcterps
Oh, we have a few.  Made me chuckle.
I don't always call out every play, and I know I'm hard on certain calls to the point of rage, but I'm very objective when it comes to officiating believe it or not.
I'll yell, "come on!" at times, only to see a replay and say, "yeah, good call". 
You guys just never see that, and I only really remember the bad calls that go against us, but I've seen them. 
I've seen more no calls though TBH. 
Michigan State the other night....Bruno used his elbow to get around the defender under the rim. 
Not sure which football game, but we accidently ran a reverse, and I swear there was a block in the back not called that should have been, and Terps at the game said there were 2 on that play. 

FearlessF

  • Hall of Fame
  • *****
  • Posts: 37495
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #12 on: January 23, 2019, 08:34:40 PM »
vs MSU... WR ran out of bounds and came back for a big play on the drive that ended up winning the game.   But I'd never publicly admit it.
there was visible contact
"Courage; Generosity; Fairness; Honor; In these are the true awards of manly sport."

847badgerfan

  • Administrator
  • Hall of Fame
  • *****
  • Posts: 25181
  • Liked:
Re: Terrible Calls That Benefitted Your Team
« Reply #13 on: January 23, 2019, 08:42:05 PM »
UNL NEVER got a good call. MNC's and all. NEVER.
U RAH RAH! WIS CON SIN!

 

Support the Site!
Purchase of every item listed here DIRECTLY supports the site.