What's new
Fantasy Football - Footballguys Forums

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Notable Plays called back due to penalties (1 Viewer)

Troy Williamson just had a 37 yard catch called back on a horrible offensive pass interference call. Not even close to a penalty.

 
2-15-SF43 (11:37) A.Smith pass short right to A.Bryant to PHI 8 for 49 yards.

PENALTY on SF-M.Robinson, Chop Block, 15 yards, enforced at SF 43 - No Play.

 
Neil Rackers 75 yard field goal attempt squashed when Stl changed their mind and accepted a penalty after they had already declined it.

 
Denver 1st and goal at the two and Tom Nalen was called for a phantom hold call where Vince Wilfork just kinda fell forward and Tom let him......eventually settling for a FG.

 
Marvin Harrison missed 40 yd pass for TD because DB pulling / hanging off his jersey....no flag thrown.

Edit: yeah, not exactly matched to the thread, but still a "near miss" which I think is the true spirit of this thread???

 
Last edited by a moderator:
The Texans defense (Shante Orr) had a 77 yard defensive fumble recovery for a TD in the 4th quarter nullified by an uneccessary roughness call after Thomas Johnson hit Brunell well after the fumble recovery.

 
Last edited by a moderator:
How about the Torry Holt TD that got called as incomplete (pushed OB in the back of the end zone).... very easy call, that was screwed up. :shakinghead:

 
Last edited by a moderator:
prosopis said:
Neil Rackers 75 yard field goal attempt squashed when Stl changed their mind and accepted a penalty after they had already declined it.
Wasn't that funny? Rackers looked PIzzED that they weren't going to let him try it!
 
Not a penalty, but a bad bad bad call.Reggie Wayne lost a 52 yard catch on a bad review.
Absolutely agreed. There was NO 'overwhelming visual evidence' to take away that catch, despite Dierdorf's bleating on and on about it in the booth.
I think it was the right call, just a bad rule. The NFL rule is you have to control the ball through the play. It was a semi-diving catch where he clearly caught it, tucked it, one foot down, kneed down but then dropped it when he made contact with the ground. Per NFL rule that is incomplete. If he had been running down the field and the same thing happens it is "the ground can't cause a fumble". I don't like the rule. If you clearly catch it/tuck it and get your feet down it should be a catch. Same with that stupid "football move" rule.
 
Not necessarily penalties, but the Vikings should have had about 5 interceptions this week. One which hit Sharper in the hands, should have been a td return.

 
Not a penalty but Reggie Wayne had around a 30 yard catch to the one and was fighting but could not get in..Manning bootlegged the next play in for a TD.

 
Not a penalty, but a bad bad bad call.Reggie Wayne lost a 52 yard catch on a bad review.
Absolutely agreed. There was NO 'overwhelming visual evidence' to take away that catch, despite Dierdorf's bleating on and on about it in the booth.
I think it was the right call, just a bad rule. The NFL rule is you have to control the ball through the play. It was a semi-diving catch where he clearly caught it, tucked it, one foot down, kneed down but then dropped it when he made contact with the ground. Per NFL rule that is incomplete. If he had been running down the field and the same thing happens it is "the ground can't cause a fumble". I don't like the rule. If you clearly catch it/tuck it and get your feet down it should be a catch. Same with that stupid "football move" rule.
Actually, if a player is running down the field, falls and lose the ball when he hits the ground, it's a fumble. Ground absolutely CAN cause a fumble. It's only when there' s contact that the "ground can' t cause a fumble" rule comes into play.
 

Users who are viewing this thread

Back
Top