Maroney's delay of game

[sebman2112]

I saw that replay too which showed that he was clearly inbounds. They showed a great angle from the back of the endzone after the commercial like he said. I do think that the Brady fumble was not a fumble. His knee was down, but what can you do.

Wasn't the very beginning of that replay useless? IE: at the very beginning of the replay you couldn't really see his feet that well, then as the replay went along you could see him running down the line? The first two steps where I think you couldn't really see his feet that well would have been the steps were he was out of bounds. I thought he stepped out but it really doesn't matter. On the Brady fumble I couldn't really tell if the ball came out first or not so the officials were right to let the play stand.

I actually think replay's can sometimes be confusing to those watching at home. Last week when they were showing the Cromartie PI replay they played the first few seconds in regular speed, then paused it, then went fourth with the slow-mo. Problem was the actual PI that took place was at the very beginning of the replay before they paused it and the part they actually watched was as Cromartie's arm was coming off.

 

[PatsFaninAZ]

Add me to the list that thinks, based on the view from the back of the end zone, that you can't overturn the call on the field on the non-safety. Not only did I think it was too close to call, the replay shows the official looking right at it.

On the throwing the ball, there's a new rule and it says what it says. You can't "spike or throw" the ball "after the down has ended" unless it's a touch down.

That's what Maroney did. Week three is a bit too early for me to cry "inconsistency" about a new rule. I'm sure the officials will find a happy medium on this one by week 10 or so, as the league gives each crew guidance after reviewing the films. Moreover, it's no secret that in the early stages of a new rule, the league wants it called closely to emphasize it and deter it. So, like with any rule, if you don't want to get called for it, don't freaking do it.

It was the right time to call it. The team had picked up a first down. It didn't change down or distance, just moved them 5 yards on the field. And nobody on the team (or the other team) will do it again. Or, if they do, they are meatheads. Maybe the rule is stupid. But I'm not anxious in the least to have officials trying to figure out what rules are stupid and what rules aren't.

 

[TripleOption]

Moreover, it's no secret that in the early stages of a new rule, the league wants it called closely to emphasize it and deter it. So, like with any rule, if you don't want to get called for it, don't freaking do it.

Weird. I actually heard Mike Pereira say that he was looking for a blatant spike to be called. He showed a very similar play and stated "This is not what we are looking for. This is a bad call."

But I guess you know more about what the league is looking for than the Head of NFL Officiating.

 

[rabthepat]

The rule is not consistently called yet. T.O. threw the ball between his legs last night against the Bears and did not get flagged.

 

[BradyManny]

Can anyone help me understand the penalty Maroney got for delay of game? On the replay it looked like he just flipped the ball away, sort of casually. He didn't spike it? I know the rule is new this year but I thought that one was just stupid. I mean Wes really slammed it during the Bolts game and didn't get a flag. I hope the ref's get more consistent with this one.

It was a BS call. He released the ball onto the ground, there should have been no penalty.

I'm not trying to be a conspiracy theorist here, but I do think the refs might have inflicted their own "mercy rule" on the Bills yesterday. The Brady fumble, this BS Maroney call & the failed safety call were all gifts to the Bills. Having done a little reffing (of basketball) I can say that when one team is so much dramatically superior to another, it does cross your mind to let certain things go under the assumption one team is going to destroy the other. Not saying it's right, but I think it's part of the game.

 

[The 12th Man]

Add me to the list that thinks, based on the view from the back of the end zone, that you can't overturn the call on the field on the non-safety. Not only did I think it was too close to call, the replay shows the official looking right at it.

On the throwing the ball, there's a new rule and it says what it says. You can't "spike or throw" the ball "after the down has ended" unless it's a touch down.

That's what Maroney did. Week three is a bit too early for me to cry "inconsistency" about a new rule. I'm sure the officials will find a happy medium on this one by week 10 or so, as the league gives each crew guidance after reviewing the films. Moreover, it's no secret that in the early stages of a new rule, the league wants it called closely to emphasize it and deter it. So, like with any rule, if you don't want to get called for it, don't freaking do it.

It was the right time to call it. The team had picked up a first down. It didn't change down or distance, just moved them 5 yards on the field. And nobody on the team (or the other team) will do it again. Or, if they do, they are meatheads. Maybe the rule is stupid. But I'm not anxious in the least to have officials trying to figure out what rules are stupid and what rules aren't.

I agree with you 100%. I don't know why people have to complain about every little thing. He was in bounds. I'm a huge Pats fan, but when I saw the replay with the ref staring it down the line and his feet avoiding the white, I knew it was the right call. Move on. We still dominated, alright guys.