![]() |
It's clear that #51 was not going after the kick, and was instead going after Moeaki.
I HATE Denver. Now that I've gotten that out of the way, someone please educate me what was illegal. I'm serious. |
Quote:
Hopefully he isn't hurt as badly as that staggering indicaated he could be. |
It was a routine block for an on-side kick play. The return team players are coached to blow up the on coming players from the kicking team.
Come one guys, you're not Todd Haley. You're better than this, right? |
Quote:
But it's hard to see whether it was an intentional headshot. |
Quote:
|
Yeah, nothing wrong here. Standard block, and Moeaki got his lunch served.
Hope he's alright. |
looked like a clean hit...Tony needs to pay better attention in those situations
|
I really like Moeoki, but you have to admit, that video was funny as hell. I played it over again about 5 times and was laughing to the point of crying the way he staggered around. Not laughing at his injury, it just struck me funny.
|
Clean block ? Helmet to helmet is not a clean block.
|
Quote:
|
Quote:
It was a clean hit - he was the hammer and Moeaki was the nail. Shit happens, it's a contact sport. There was some helmet to helmet contact, but it was during a block and Mays didn't make himself a projectile. It was a hard, clean hit by a guy that was fired up because his team was winning. Moeaki was going through the motions a little bit because the game had gotten away and got his bell rung. Lesson learned - Moeaki won't go at 80% anymore. |
Quote:
If shit happens, then why didn't Mays make the EXACT SAME block on the very next onside kick attempt ? |
Quote:
|
Quote:
|
Come on guys, some of you are still butthurt over this game. It was a shellacking, we got nailed due to our safeties being back up and 3rd stringers. Denver took advantage of this and had something to prove after the game last year.
Just get over it ..... it was a hard, legal hit, it's football. |
All times are GMT -6. The time now is 08:28 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.