TexasRebel said:

---

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.

---

Wedgebuster says "hold my beer while I initiate contact".

Would the wedge buster touch the wedge if the ball carrier was not behind it?

watched the play on skycast.
you can see it, barely, on the edge of the screen.
looks like an Aggie had engaged a sip, above the waist...
then an Aggie fell into the sips legs.. hence the flag.
however, it was on the edge of the screen. you can't see it plainly.
ETA
Looch said it was legit penalty
fwiw

TexasRebel said:

---

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.

---

Did you watch the NFL video I posted showing exactly what you say doesn't happen? It isn't common but it also isn't a 1 in a million event.

Seasoned Lifeguard said:

---

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

---

A chop block by definition takes two guys to commit- one guy blocking high and another blocking low...one guy going low when or where he can't (downfield, outside the interior line, on a kickoff or punt etc) is blocking below the waist

Chop Block
ARTICLE 3.
A chop block is a high-low or low-high combination block by any two players against an opponent (not the ball carrier) anywhere on the field, with or without a delay between blocks; the "low" component is at the opponent's thigh or below. (A.R. 9-1-10-I-IV). It is not a foul if the blockers' opponent initiates the contact. (A.R. 9-1-10-V)

fla_agfan said:

---

Elmer Dobkins said:

---

jp95 said:

---

Notice it never got re-played on tv.

---

This.

---

I went back and looked... saw the flag thrown, but not the penalty itself

---

That's because it didn't happen. It was the obligatory 15 yarder to get them back in it after we had just gotten it back to a 3 point game.

We tried to tell all you "bring back the game" **** wits.

TexasRebel said:

---

Would the wedge buster touch the wedge if the ball carrier was not behind it?

---

In many cases, yes, because that is what his coaches assigned him to do.

Great summary from a wedge buster in the old days talking about going at the legs to take out the wedge.
https://jerseymanmagazine.com/wedge-busting-in-the-old-nfl/

Well then that's just dumb.

If he was between the wedge and ball carrier, would he go after the wedge?

TexasRebel said:

---

Well then that's just dumb.

If he was between the wedge and ball carrier, would he go after the wedge?

---

In many cases, yes. If he tries to go around it, he likely won't touch the ball carrier and that leaves the wedge players to go block another one of his teammates. With your logic, every member of the kicking team should dodge all blocks and there should be no contact on a kick return.

This was a normal kick situation but it is likely one of our players took on the return blocker by going low and yes by rule, both players in that case are blocking.

Blocking definition from the NCAA rule book. Note it doesn't say offense or return team just opponent.
ARTICLE 1.
Blocking is obstructing an opponent by intentionally contacting him with any part of the blocker's body.

jimmo said:

---

watched the play on skycast.
you can see it, barely, on the edge of the screen.
looks like an Aggie had engaged a sip, above the waist...
then an Aggie fell into the sips legs.. hence the flag.
however, it was on the edge of the screen. you can't see it plainly.
ETA
Looch said it was legit penalty
fwiw

---

Logic. Reasoning. Has no place in a good ole fashioned conspiracy

Kansas Kid said:

---

TexasRebel said:

---

Well then that's just dumb.

If he was between the wedge and ball carrier, would he go after the wedge?

---

In many cases, yes. If he tries to go around it, he likely won't touch the ball carrier and that leaves the wedge players to go block another one of his teammates. With your logic, every member of the kicking team should dodge all blocks and there should be no contact on a kick return.

This was a normal kick situation but it is likely one of our players took on the return blocker by going low and yes by rule, both players in that case are blocking.

Blocking definition from the NCAA rule book. Note it doesn't say offense or return team just opponent.
ARTICLE 1.
Blocking is obstructing an opponent by intentionally contacting him with any part of the blocker's body.

---

Again, why would anyone on the kicking team want to obstruct anyone except the ball carrier?

Let's make it simple.

By rule, any time and offensive and defensive player make contact (excluding the ball carrier), they are both blocking. If either go low except inside the tackle box, it is a low block. If two players on the same team make contact with an opponent with one above the waist and one below the waist, it is a chop block no matter where on the field it occurs.

For some reason known only to him, our player went low and they either called chop block or a low block. Either way, it was a 15 yard penalty on us. Players do dumb things all the time which is why most fouls are called.

Why would any player ever go across the line before the snap or lineup with 5 or more in the backfield? Because they make mistakes and in the play in question, our player made a mistake in going low.

So it's a penalty to trip while being blocked.

Got it.

[/sarcasm]

Kansas Kid said:

---

Let's make it simple.

By rule, any time and offensive and defensive player make contact (excluding the ball carrier), they are both blocking. If either go low except inside the tackle box, it is a low block. If two players on the same team make contact with an opponent with one above the waist and one below the waist, it is a chop block no matter where on the field it occurs.

For some reason known only to him, our player went low and they either called chop block or a low block. Either way, it was a 15 yard penalty on us. Players do dumb things all the time which is why most fouls are called.

Why would any player ever go across the line before the snap or lineup with 5 or more in the backfield? Because they make mistakes and in the play in question, our player made a mistake in going low.

---

Ok, simple enough. Show us a video clip of our player(s) doing this "dumb thing" for which they were penalized 15 yds.

If you have ESPN, go to the sky cast at 2:27:35 and you can see it somewhat although the camera isn't as clear as you would like because our player is shielded from view somewhat by two other players.

If it would have been on tu, the mark off would have been the spot of the foul so they would have had the ball at the 7 1/2 since it would have been half the distance to the goal from the spot of the foul which was the Texas 15. Instead, it was marked from the end of the run since it was on us which meant the 37. (It should have been the 36 since the runner was tackled at the 21.

So we had a player getting blocked by three players, and our guy decided to forget he was on the kicking team and block for the knees?

This is getting more and more ridiculous. No wonder the Jayhawks are a football powerhouse.

Either way I think we should have flooded the field with water bottles. Seems to be a pretty effective way of getting officials to change their minds.

dixichkn said:

---

Either way I think we should have flooded the field with water bottles. Seems to be a pretty effective way of getting officials to change their minds.

---

Dixichkn wins this thread! Tko in round 1045

Kind of shocked this thread wasn't bumped last night with the illegal low block on Indiana when they were on defense. Perfect example of the call, yet rebel will still cry it will never happen

Defense isn't kickoff.