Page 1 of 1

Worst Call of the Year?

Posted: October 10th, 2008, 11:32 pm
by The Ancient Enemy
I know everyone was in an uproar over Lockergate after the BYU game, but the rule technically IS in the rule book.

Tonight, I watched the Louisville / Memphis game, and despite outgaining UL 2-1 in yardage, Memphis gave up a defensive TD and TWO special teams TDs to lose the game.

But at the end, there were two very, very bad calls, both in favor of Louisville. RB Victor Anderson was hit at the line of scrimmage, spun around and fell on his back. He slid about a yard and a half, and ended up right on the yellow line. They showed it from 3 different angles and there was no chance he was on the first down marker. The refs said it was a first down. They reviewed it and called it the other way.

Then, on the last drive of the game, Memphis needed to make a huge stop on 3rd and 2 and made an amazing play to stop the RB at the line. The refs gave Louisville a first down, and it was not even close. We're talking a tackle at the line of scrimmage, with the game clearly on the line, and they gave UL a first down. They did not even review it.

I am hoping that as technology advances, we can eliminate refs making what are very clear errors. Granted, Memphis should not have given up 3 garbage TDs, but that first down was not even close. I'd say it was the worst call I've seen this season so far.

Anyone see anything worse?

Re: Worst Call of the Year?

Posted: October 11th, 2008, 12:06 am
by deliverance
I don't think this one is worse, but UT vs. Colorado had a bad call, in my opinion. The Colorado kick returner stepped out of the endzone with the ball crossing over the goal line, so it should have been a safety. They reviewed it and still called it a TD. That's just one I can think of off the top of my head.