The there is zero reason for the kicking team to initiate contact.

If they don't want to impede our path to the ball carrier, great!

Elmer Dobkins said:

---

farmer2010 said:

---

aggiedad7 said:

---

The Collective said:

---

Gamecast says block in back. I assumed it got corrected vs what was originally signaled, but you guys could be right.

---

Ref himself said block below the waist and did the proper motion for that. Game cast is wrong.

---

Correct. Original call was block below the waist on the receiving team. Penalty is half the distance to the goal. Then, about a minute of awkward chit chat between Greg and Sean with no further explanation or replay. Then, referee cuts back in with a correction, penalty was on the kicking team, and play quickly resumes with the ball near the 40 yard line, again with no further explanation of the penalty or replay, or even a shot or mention of Elko questioning the call.

It all seemed really odd.

---

30 yard swing, opened up the sip play book, and at that point in the game, the officiating crew had plenty of other ones to pull out of their sleeves if necessary. Under 10 minutes, it was Greg Sankey time.

---

Its not really a 30 yard swing. The only way that is possible is if they literally called our guy for blocking below the waist when in fact he was blocked below the waist.

It was likely an aggie rolling into a longhorn player below the waist. Unless really incidental and minor contact or blocked into a player that causes it, it is not a judgment call. It is a foul every time. Yes, it is rare for a defender to do it. But it happens.

It wasnt a situation where they called it against us when it was supposed to be against him. Just a miscommunication when they huddled on the foul call.

OBJTEX said:

---

Elmer Dobkins said:

---

farmer2010 said:

---

aggiedad7 said:

---

The Collective said:

---

Gamecast says block in back. I assumed it got corrected vs what was originally signaled, but you guys could be right.

---

Ref himself said block below the waist and did the proper motion for that. Game cast is wrong.

---

Correct. Original call was block below the waist on the receiving team. Penalty is half the distance to the goal. Then, about a minute of awkward chit chat between Greg and Sean with no further explanation or replay. Then, referee cuts back in with a correction, penalty was on the kicking team, and play quickly resumes with the ball near the 40 yard line, again with no further explanation of the penalty or replay, or even a shot or mention of Elko questioning the call.

It all seemed really odd.

---

30 yard swing, opened up the sip play book, and at that point in the game, the officiating crew had plenty of other ones to pull out of their sleeves if necessary. Under 10 minutes, it was Greg Sankey time.

---

Its not really a 30 yard swing. The only way that is possible is if they literally called our guy for blocking below the waist when in fact he was blocked below the waist.

It was likely an aggie rolling into a longhorn player below the waist. Unless really incidental and minor contact or blocked into a player that causes it, it is not a judgment call. It is a foul every time. Yes, it is rare for a defender to do it. But it happens.

It wasnt a situation where they called it against us when it was supposed to be against him. Just a miscommunication when they huddled on the foul call.

---

From the 10 to the 40 is 30 yards. SMH

I was also bothered by the clock not stopping on two first downs and an out of bounds in the fourth quarter.

Ag in ATL said:

---

OBJTEX said:

---

Elmer Dobkins said:

---

farmer2010 said:

---

aggiedad7 said:

---

The Collective said:

---

Gamecast says block in back. I assumed it got corrected vs what was originally signaled, but you guys could be right.

---

Ref himself said block below the waist and did the proper motion for that. Game cast is wrong.

---

Correct. Original call was block below the waist on the receiving team. Penalty is half the distance to the goal. Then, about a minute of awkward chit chat between Greg and Sean with no further explanation or replay. Then, referee cuts back in with a correction, penalty was on the kicking team, and play quickly resumes with the ball near the 40 yard line, again with no further explanation of the penalty or replay, or even a shot or mention of Elko questioning the call.

It all seemed really odd.

---

30 yard swing, opened up the sip play book, and at that point in the game, the officiating crew had plenty of other ones to pull out of their sleeves if necessary. Under 10 minutes, it was Greg Sankey time.

---

Its not really a 30 yard swing. The only way that is possible is if they literally called our guy for blocking below the waist when in fact he was blocked below the waist.

It was likely an aggie rolling into a longhorn player below the waist. Unless really incidental and minor contact or blocked into a player that causes it, it is not a judgment call. It is a foul every time. Yes, it is rare for a defender to do it. But it happens.

It wasnt a situation where they called it against us when it was supposed to be against him. Just a miscommunication when they huddled on the foul call.

---

From the 10 to the 40 is 30 yards. SMH

---

Not trying to argue. Player tackled on 25 or so. There was a illegal BBW. Called on texas a&m. Stands to reason he either did or didnt. If he didnt, there is no foul. Not a foul for illegal BBW on texas. It is zero or plus 15. Not minus 15 or plus 15.

annie88 said:

---

I was also bothered by the clock not stopping on two first downs and an out of bounds in the fourth quarter.

---

So, again, bothered by something because you don't know the rules?

annie88 said:

---

I was also bothered by the clock not stopping on two first downs and an out of bounds in the fourth quarter.

---

don't try to understand the clock anymore. it's f-ed.

OBJTEX said:

---

Ag in ATL said:

---

OBJTEX said:

---

Elmer Dobkins said:

---

farmer2010 said:

---

aggiedad7 said:

---

The Collective said:

---

Gamecast says block in back. I assumed it got corrected vs what was originally signaled, but you guys could be right.

---

Ref himself said block below the waist and did the proper motion for that. Game cast is wrong.

---

Correct. Original call was block below the waist on the receiving team. Penalty is half the distance to the goal. Then, about a minute of awkward chit chat between Greg and Sean with no further explanation or replay. Then, referee cuts back in with a correction, penalty was on the kicking team, and play quickly resumes with the ball near the 40 yard line, again with no further explanation of the penalty or replay, or even a shot or mention of Elko questioning the call.

It all seemed really odd.

---

30 yard swing, opened up the sip play book, and at that point in the game, the officiating crew had plenty of other ones to pull out of their sleeves if necessary. Under 10 minutes, it was Greg Sankey time.

---

Its not really a 30 yard swing. The only way that is possible is if they literally called our guy for blocking below the waist when in fact he was blocked below the waist.

It was likely an aggie rolling into a longhorn player below the waist. Unless really incidental and minor contact or blocked into a player that causes it, it is not a judgment call. It is a foul every time. Yes, it is rare for a defender to do it. But it happens.

It wasnt a situation where they called it against us when it was supposed to be against him. Just a miscommunication when they huddled on the foul call.

---

From the 10 to the 40 is 30 yards. SMH

---

Not trying to argue. Player tackled on 25 or so. There was a illegal BBW. Called on texas a&m. Stands to reason he either did or didnt. If he didnt, there is no foul. Not a foul for illegal BBW on texas. It is zero or plus 15. Not minus 15 or plus 15.

---

except it literally wasn't called on Texas A&M.

That happens when a player on the kicking team runs down the field and goes low on a player who is coming to block them. This protects knees and lower body injuries. Happens some but mostly it's accidental when a guy running down gets thrown down or is tripping and goes low.

TexasRebel said:

---

OBJTEX said:

---

Ag in ATL said:

---

OBJTEX said:

---

Elmer Dobkins said:

---

farmer2010 said:

---

aggiedad7 said:

---

The Collective said:

---

Gamecast says block in back. I assumed it got corrected vs what was originally signaled, but you guys could be right.

---

Ref himself said block below the waist and did the proper motion for that. Game cast is wrong.

---

Correct. Original call was block below the waist on the receiving team. Penalty is half the distance to the goal. Then, about a minute of awkward chit chat between Greg and Sean with no further explanation or replay. Then, referee cuts back in with a correction, penalty was on the kicking team, and play quickly resumes with the ball near the 40 yard line, again with no further explanation of the penalty or replay, or even a shot or mention of Elko questioning the call.

It all seemed really odd.

---

30 yard swing, opened up the sip play book, and at that point in the game, the officiating crew had plenty of other ones to pull out of their sleeves if necessary. Under 10 minutes, it was Greg Sankey time.

---

Its not really a 30 yard swing. The only way that is possible is if they literally called our guy for blocking below the waist when in fact he was blocked below the waist.

It was likely an aggie rolling into a longhorn player below the waist. Unless really incidental and minor contact or blocked into a player that causes it, it is not a judgment call. It is a foul every time. Yes, it is rare for a defender to do it. But it happens.

It wasnt a situation where they called it against us when it was supposed to be against him. Just a miscommunication when they huddled on the foul call.

---

From the 10 to the 40 is 30 yards. SMH

---

Not trying to argue. Player tackled on 25 or so. There was a illegal BBW. Called on texas a&m. Stands to reason he either did or didnt. If he didnt, there is no foul. Not a foul for illegal BBW on texas. It is zero or plus 15. Not minus 15 or plus 15.

---

except it literally wasn't called on Texas A&M.

---

You guys dont get it. There obviously was miscommunication by officiating crew. Exact same thing happened at OU/LSU game. White hat announced holding on defense. After a conference and long pause he reversed the call. H on offense.

If there was a BBW on Texas and they conference and reverse it blatantly with no reason, the crew will be fired.

Guessing he misheard the official and made wrong announcement.

DimebagsGhost said:

---

That happens when a player on the kicking team runs down the field and goes low on a player who is coming to block them. This protects knees and lower body injuries. Happens some but mostly it's accidental when a guy running down gets thrown down or is tripping and goes low.

---

And honestly, if we can find a replay, that is the honest argument. I am betting if there is a mistake it what Dimebags said.

But either way, it is plus 15 one way or nothing. Not minus 15.

Really strange there was no broadcast replay on such a momentum changing call, isn't it? The fact they had already marked off the penalty yardage against Texas before the zebras huddled and then decided it was against A&M is interesting to say the least. You've really not provided any divine revelation, but we appreciate the condescending scenarios of what "likely happened ".

htxag09 said:

---

annie88 said:

---

I was also bothered by the clock not stopping on two first downs and an out of bounds in the fourth quarter.

---

So, again, bothered by something because you don't know the rules?

---

Oh yeah, that's right. They changed the rules in 2023 except for the last two minutes of each half. And I guess the guy didn't go out of bounds, but we thought he did. It was on the other side of the field.

I'm still getting used to the two-minute time out.

Old habits, die hard.

Elmer Dobkins said:

---

Really strange there was no broadcast replay on such a momentum changing call, isn't it? The fact they had already marked off the penalty yardage against Texas before the zebras huddled and then decided it was against A&M is interesting to say the least. You've really not provided any divine revelation, but we appreciate the condescending scenarios of what "likely happened ".

---

Only debating the facts. I do know that SEC officials are graded on every play. If one of theirs blocked below the waist; the officials threw; called it; then huddled in some inane conspiracy on the off chance they thought of all times, this one play would turn the game...the conference office would review the play and hammer the officials.

Already fired a crew for a mistake.

The most likely scenario is an aggie player hit a Texas player below the waist. Whether or not it rose to the level of a foul is tbd. Espn had the skycam going for the return for some reason.

It was sloppy to announce it wrong. Almost no chance it was a texas player blocking below the waist and they flipped it. That is the working theory of the paranoid on this board and in that occurence, it would be a net 30 yards.

By whom are they graded?

TexasRebel said:

---

TonyD33 said:

---

That penalty can be called on either team. I didn't see it either but the penalty was for someone going low on a kickoff, which neither the kicking nor receiving team can do.

---

But the kicking team is not blocking.
They have no reason to hit anyone except the ball carrier.

---

.

If a coverage player hits an opposing player below the waste on a kick play it's still called a "chop block" which is probably what led to the confusion on the field.

The skycast replay showed it pretty clearly. #29 on the coverage team hit a Longhorn player low and drew the flag

OBJTEX said:

---

If there was a BBW on Texas

---

Horn likes fat chicks...

Again, why would the kicking team block?

It's a simple question that hasn't been answered.

You can't see crap on the sky cam. Now you're just making stuff up.

TexasRebel said:

---

Again, why would the kicking team block?

It's a simple question that hasn't been answered.

You can't see crap on the sky cam. Now you're just making stuff up.

---

It's been answered. You don't like the answer so ignore it.

htxag09 said:

---

TexasRebel said:

---

Again, why would the kicking team block?

It's a simple question that hasn't been answered.

You can't see crap on the sky cam. Now you're just making stuff up.

---

It's been answered. You don't like the answer so ignore it.

---

Exactly. Though i disagree the skycam footage was clear. You see the aftermath but not the contact.

Blocking is term used to define any intentional contact onto an opponent (non ball carrier) with any part of your body. If a defender (whether a kicking play or not) hits a (non ball carrier) player on the team with the ball; its called a block.

There is no delineation between offense or defense. It is more common for contact to be initiated by team with ball as a block. However, tons of normal football plays have defenders blocking an offensive player. We just call it something else as fans. I can list tons. One easy example. We call when a DB makes contact with a wr in press coverage at the LOS something like a "chuck" or "jam". But by rules it is a block.

If the DB dove at legs of wr, it would be BBW and a foul.

Again, you dont like answer because you want to find a conspiracy.

It may have been a bad call. It might have been a good call. I cannot really see it from skycam angle. But it was not a net 30 yard difference.

Again, you're neglecting the fact that nobody on the kicking team wants to make contact with anyone except the ball carrier.

This isn't a regular play.
There is no forward pass to cover.

if you've ever played football, it's not that hard a concept. If you're trying to make a tackle, like on the kickoff team for example, the return team members will try to block you.
they can't block you low anymore on kickoffs, and conversely the kickoff team cannot take on the blocker low either. that's what was called.
Same concept that under the new rules someone playing outside the tackle box can't take on a block by hitting the blocker low- i.e. a corner can't try to take a pulling guard out low and create a pile

And it was called, as expected, on the return team.

TexasRebel said:

---

By whom are they graded?

---

For college, the conference pays highly experienced current or former officials at that officials position to look at every play and grade their mechanics and judgement. They receive scores and critiques on plays where material judgement was needed by that official. Repeated bad scores lead to having your service with the conference being terminated. High scores get you better assignments, bowl games, and potential promotion. The NFL looks at these officials to see who they want to bring up as well.

The coaches call submit a limited number of plays each week to the conference for comments and review. I think the SEC allows up to 10.

TexasRebel said:

---

Again, you're neglecting the fact that nobody on the kicking team wants to make contact with anyone except the ball carrier.

This isn't a regular play.
There is no forward pass to cover.

---

Again you either dont understand football or havent played in a long time.

Kick coverage guys often initiate contact with kick return guys. Watch football. They often try to avoid contact to get around a blocker but often they have to bully/smash into/hit a blocker.

By definition, it is called a block.

You cannot initiate contact below the waist in that scenario.

It is uncommon but it happens.

No they don't.

If the return blockers don't initiate contact the kicking team certainly wouldn't engage. They go after the ball.

Definitely crazy to say the kickoff team doesn't initiate contact - none of you had the crazy son of a beetch on your high school team who's sole purpose in life was to blow up the wedge?

With that said, the call here is about as rare as holding against the defensive line which I've only seen a handful of times.

TexasRebel said:

---

No they don't.

If the return blockers don't initiate contact the kicking team certainly wouldn't engage. They go after the ball.

---

You would say the same thing on defense on a play from scrimmage yet here is the defense committing the foul and ironically, the official calling it wrong initially. This happens a lot more than people think either because the defender is trying to avoid the contact or to blow up a blocker for offense. In the days of the wedge on kickoffs, wedge busters used to do this to blow up the wedge.

Yes, it is NFL but the rules regarding low blocks are essentially the same.

https://www.footballzebras.com/2025/09/steelers-low-block-call-is-outside-of-the-tight-end-box/

See the second play in this video is for those that say the kicking team would never block low. I would love to see the block in question in our game but I have no problem believing we did it and frankly, this is a fairly easy foul to call, especially on kickoffs because players are spread out.

Kansas Kid said:

---

See the second play in this video is for those that say the kicking team would never block low. I would love to see the block in question in our game but I have no problem believing we did it and frankly, this is a fairly easy foul to call, especially on kickoffs because players are spread out.

---

Again, some on this site only want to beleive conspiracies when it comes to the Austinites. It is a low % but vocal.

Thanks for adding to discussion. And again, my point wasnt to defend if it was a proper foul call. I do agree, the television broadcast was unclear. My point was it was not a 30 yard delta. It was 15.

If space aliens ever truly reach Earth, these threads would surely be part of the electronic pull of all the data on the planet with their superior technology, and upon processing would lead them to conclude there is no intelligent life here.

TexasRebel said:

---

No they don't.

If the return blockers don't initiate contact the kicking team certainly wouldn't engage. They go after the ball.

---

the #1 thing a special teams coach says is "Run wherever the hell you want, just don't get blocked" then, right?

No, actually it's "STAY IN YOUR LANE!" That's how there is contact.

farmer2010 said:

---

Are there any replays available with alternate cameras? i.e. not the official broadcast but an overhead angle or something?

It should be really easy to spot something as odd and egregious as a chop block on the kicking team. If nothing can be discerned from that footage, an investigation should be launched into game fixing and those officials will have hell to pay.

---

New here? Some of y'all youngsters are starting to learn why so many of us never wanted to play the sips ever again. You will never get to play them on a level playing field.

KGP said:

---

TexasRebel said:

---

No they don't.

If the return blockers don't initiate contact the kicking team certainly wouldn't engage. They go after the ball.

---

the #1 thing a special teams coach says is "Run wherever the hell you want, just don't get blocked" then, right?

No, actually it's "STAY IN YOUR LANE!" That's how there is contact.

---

Yes. Stay in your lane and go after the ball carrier. Don't just seek out someone random to hit, and make sure to keep your feet.

On a normal play, the defense has reasons to initiate contact with players that aren't carrying the ball.

This was a kickoff. Your comparisons are not applicable.