Did you see the way the refs tried to hose Miami on the previous drive? All of those PI calls? They must have thought they were reffing a Coach Alphabet Soup game over at Cameron Indoor Stadium instead for Duke football.

And as far as one of the player's knees being down, it was too close to tell, even on the replay. Glad to see it happen after how they tried to hand it to Duke.

While I accept the premise that they couldn't change the touchdown call based on the knee being down, it is Duke that was ripped off. No way the refs didn't see the block in the back at the Miami 15. But I'll even give them that. Everybody misses one here and there. The big ripoff came when they claimed they picked up the flag that they did throw based on their review of the replay. A penalty like a block in the back is NOT reviewable, so they should not have picked it up. It should have been Miami's ball somewhere around the 40-yard line with no time left on the clock. Game over, Duke wins.

(11-01-2015 07:43 AM)Zombiewoof Wrote:  While I accept the premise that they couldn't change the touchdown call based on the knee being down ...

Why?

Duke announcing crew
https://soundcloud.com/bill-zeoli/duke-i...um=twitter

They missed the block in the back on the 15, but there were 3 big mistakes they made that should have called back the TD.

1) His knee really was down. The attached article shows that.
2) They "reviewed" the block in the back penalty they did call which is not allowed.
3) A 12th Miami player was on the field. I am 99.99% certain the SB writer doesn't know the rules of football. He says it would have been a dead ball foul if the player doesn't interfere. 12 men on the field is not a judgement call. It should have been called back with Miami penalized. With the clock run out, the game would have been over.

Shame such a crazy, entertaining ending was mishandled by the refs.

http://www.sbnation.com/college-football...ding-play-

It was one hell of a "play" but Christ it was as legal as a jailbreak.

I didn't think there should have been a flag on the last play. It was really weird it coming back (and not sure it should have been), but I thought it was a good no call at least intially. I don't know about the knee, but didn't think there was enough to overturn.

Nevermind the Miami guy running down the field during the play with his helmet off in his hand.....yeah, pay no attention to that. We allow the idiots at Miami to get away with such because we all pity them and their "less than stellar" recruits that no respectable institutions are willing to take.

There should have been a flag for that alone or for one of the many blocks in the back but the knee being down before the lateral? These officials just seriously boned their own conference with this bone headed play officiating.

(11-01-2015 07:43 AM)Zombiewoof Wrote:  The big ripoff came when they claimed they picked up the flag that they did throw based on their review of the replay. A penalty like a block in the back is NOT reviewable, so they should not have picked it up. It should have been Miami's ball somewhere around the 40-yard line with no time left on the clock. Game over, Duke wins.

FWIW, the ref crew says the flag was picked up due to conference, not the video review. I don't necessarily buy it, based on the ref's initial comments before he went back "under the hood," but that is the official story

The ACC has now suspended the entire officiating and replay crew from the Miami-Duke game, citing 4 errors on the game-ending kick return (but none of the previous errors that benefitted Duke).

(11-01-2015 12:50 PM)Wedge Wrote:  The ACC has now suspended the entire officiating and replay crew from the Miami-Duke game, citing 4 errors on the game-ending kick return (but none of the previous errors that benefitted Duke).

Well according to the ACC, the SB guy was right. I don't understand why, but it is a judgement call-a dead ball foul to have 12 players on the field if they are not deemed to be a participant. Strange.

But there were lots of mistakes and the ACC took action.

http://sports.yahoo.com/blogs/ncaaf-dr-s...28927.html

(11-01-2015 01:25 PM)bullet Wrote:  

(11-01-2015 12:50 PM)Wedge Wrote:  The ACC has now suspended the entire officiating and replay crew from the Miami-Duke game, citing 4 errors on the game-ending kick return (but none of the previous errors that benefitted Duke).

Well according to the ACC, the SB guy was right. I don't understand why, but it is a judgement call-a dead ball foul to have 12 players on the field if they are not deemed to be a participant. Strange.

But there were lots of mistakes and the ACC took action.

http://sports.yahoo.com/blogs/ncaaf-dr-s...28927.html

That's one rule that makes sense. If anyone, player, coach, ballboy, whomever, wanders on the field out of excitement, and the play is unaffected, enforcing the penalty as a dead ball foul seems right.

(11-01-2015 01:40 PM)Wedge Wrote:  

(11-01-2015 01:25 PM)bullet Wrote:  

(11-01-2015 12:50 PM)Wedge Wrote:  The ACC has now suspended the entire officiating and replay crew from the Miami-Duke game, citing 4 errors on the game-ending kick return (but none of the previous errors that benefitted Duke).

Well according to the ACC, the SB guy was right. I don't understand why, but it is a judgement call-a dead ball foul to have 12 players on the field if they are not deemed to be a participant. Strange.

But there were lots of mistakes and the ACC took action.

http://sports.yahoo.com/blogs/ncaaf-dr-s...28927.html

That's one rule that makes sense. If anyone, player, coach, ballboy, whomever, wanders on the field out of excitement, and the play is unaffected, enforcing the penalty as a dead ball foul seems right.

This guy didn't "wander" onto the field if you have seen the video. He ran all the way to the hashmarks before the guy got into the end zone.

(11-01-2015 01:53 PM)bullet Wrote:  

(11-01-2015 01:40 PM)Wedge Wrote:  That's one rule that makes sense. If anyone, player, coach, ballboy, whomever, wanders on the field out of excitement, and the play is unaffected, enforcing the penalty as a dead ball foul seems right.

This guy didn't "wander" onto the field if you have seen the video. He ran all the way to the hashmarks before the guy got into the end zone.

In that particular case yes that is true, but the reason Wedge stated is likely why the rule exists.