Blocking Below Waist Questions

Submitted by tdcarl on

I don't like to complain about officiating, but we won and these are actually some legitimate questions.

So I saw it mentioned somewhere else that there was a rule change to prevent players outside of the tackle box from being cut down by a block below the waist.

The NCAA website says:

Offensive players in the tackle box at the snap who are not in motion are allowed to block below the waist legally without restriction. All other players are restricted from blocking below the waist with a few exceptions (for example, straight-ahead blocks).

So were these blocks on CB/Safeties legal because they straight on? Or were the refs just not calling it when they should have? I wouldn't put that past them based on the fact that they were seemingly following Arena Football rules about players in motion.

O Fo Sho

September 8th, 2012 at 9:01 PM ^

How about the defensive holding 2x on Big Will!? I'm not sure about he first one, but I was annoyed after the second one. So I replayed it 10x and still have no clue of what he did. He gets chopped at the knees and falls down and he gets a flag.... Oh well....

ShadowStorm33

September 8th, 2012 at 9:02 PM ^

Speaking of wtf penalties, what was up with the two holding calls on BWC? I was at the game so I couldn't see, but I don't think I've ever heard of a holding call on a d-lineman before...

cjd3mtsu

September 8th, 2012 at 9:16 PM ^

Did anyone notice in the first half that the H-back went in motion towards the line of scrimmage at least three times as the ball was about to be snapped? How is that not illegal motion? 

goblue81

September 8th, 2012 at 9:34 PM ^

There were several obvious illegal procedure infractions they missed.  In the live blog, someone mentioned this isn't the Arena League...

  • There one TD was aided by the H-Back going all arena league and getting to our secondary to chop his legs before the play even developed (whether the chop is legal or not I'll leave to more informed individuals).  
  • Then the critical play at the end of the game where the entire backfield went in motion at least a good 1/2 second before the snap.  That allowed them to get to the edge for the first down and potential doom!

The officiating was ok for the most part but the lack of false starts on AFA was pretty bad.  Also, since ESPN2's coverage was spectacular (snark snark cyan screen), we never got to see a replay of BWC's so called holding penalties.  I can see one happening in a game, but 2 is either the officials or BWC being derp.

RakeFight

September 8th, 2012 at 9:37 PM ^

I'm not going to defend ABC/ESPN, especially after losing the video feed in the final 3 minutes of the game, and switching us to the USC game rather than just giving us audio or any other kind of updates... but it's impossible to show replays when the offense on the field is playing hurry-up/no-huddle.

FreddieMercuryHayes

September 8th, 2012 at 10:18 PM ^

I feel like when we have those 6'+ corners as upperclassmen it won't be such a big deal.  But frankly, there's not much you can do against a well excecuted cut block.  Hell, we saw that happen on Denard's 87 yard ND run in 2010.  And AF does A LOT of cut blocks.  That's their WR's primary function.  They're good at it.

Drill

September 8th, 2012 at 10:16 PM ^

I was one of the people yelling about it throughout the game.  I know on at least 2 of the TDs, one of our players who would have had a shot at being in position to stop the TD, they were cut below the waist and it definitely didn't look straight on.

vablue

September 9th, 2012 at 5:25 AM ^

I thought the ball spots today were horrendous.  It seemed like AF got an extra yard or two any time the ball went to the sideline and we got a yard less every times we went out of bounds.  Maybe it was just my bias, but this seemed like a somewhat subtly badly officiated game.  No huge blown calls, but a lot of little things that were let go. Except of course the guy in motion moving toward the line of scrimmage, that was not subtle at all.