Does “clipping” mean tripping over your own guys? I watched that video and it looks like the guys in white are diving into the feet of the other guys in white. The first one it looks like the white guy was pushed over by the red guy and then trips his teammate, the second more like the white guy just dove at the ball carrier and tripped his teammate. :dubious:
Oregon won its 2006 game against Oklahoma after recovering an onside kick that they didn’t really recover, and that they had touched first before it went 10 yards.
Assuming you know it is illegal to block a defender in the back–are you watching the same video I am? Watch number 23 for the ‘white team’ (Denver Broncos I believe)–He is one of the first defenders in the screen, and around the 6 second mark of that video he is veritably launched into the air by an illegal block delivered by number 44 of the ‘red team’ (the Kansas City Chiefs). Just as he regains his feet (around the 9 second mark) he is knocked over again by a teammate who has been blatantly blocked in the back by another Chief, not more than 15 feet from an official who is staring point blank into the whole fiasco, and who has apparently forgotten he possesses a yellow flag he is supposed to throw in such situations.
Here is the onside kick that it was determined that Oregon recovered.
KRM
Oklahoma graduate and still bitter.
That was indeed the Broncos, and that was indeed a couple illegal blocks, and I remember screaming my head off at the TV after that play for the absolutely awful officiating.
Phil Luckett was the official for the Thanksgiving Day coin toss fiasco. After being demoted to back judge, he managed to get in the way of a sure TD for Joe Horn of the Saints.
Oh, and while I consider it debatable now, I’m still pretty sure the Music City “Miracle” was a bad call. Watching it live, I thought it was egregious.
Didn’t know you couldn’t hit them from behind, no. Thanks for explaining, though. I thought it maybe meant hitting them below the knees or something, which nobody did.
Well, technically, “clipping” is behind and below the waist. Behind and above the waist is just “illegal block in the back”, but it used to be “clipping” until 10-15 years ago.
Good to know. Everything I know about football I learned in PE class in highschool. We went into the parking lot one cold and overcast day and played flag football. There was a lot of yelling about blitzes and whatnot and it didn’t really make any sense. We were all assumed to know how to play the crazy game. I wouldn’t even know where to look to find out what all is illegal.
This photo was not facemask penalty . Nope, no flag thrown.
In 1982, Nebraska lost only one game, to Penn State (the eventual national champion). This play set up Penn State’s winning TD. Just a bit outside…
If you’d like, I’ll start a MPSIMS thread to explain American football, and give you a general idea of the various penalites, and what terms like “blitz” mean.
Back to the OP, the refs blew it in the 1961 Notre Dame v. Syracuse game, which was a big deal at the time. According to wikepedia entry on then Irish coach Joe Kuharich:
“In 1961, Notre Dame faced Syracuse in South Bend and trailed, 15-14 with three seconds left to play. A desperation 56-yard field goal attempt fell short as time ran out, and Syracuse appeared to have won the game. But the Orangemen were penalized 15 yards for roughing the placekick holder, and given a second chance with no time showing on the clock, Notre Dame kicker Joe Perkowski drilled a 41-yard field goal for a 17-15 Irish victory. Syracuse immediately cried foul, claiming that under the existing rules, the second kick should not have been allowed because time had expired. It was later determined that the officials had erred in allowing the extra play, but the Irish victory was permitted to stand. The current rule which states that a half cannot end on a defensive foul was implemented as a result of this game.”
The more times I see it, the more convinced I am that the ball didn’t cross the line.
Onside kick by Oregon. Oregon not only touched the ball before it went 10 yards. Then Oklahoma recovered the ball, away from a pile of people. The refs ruled that Oregon had posession when an Oklahoma player was holding the ball. There was also a phantom pass interference call.
That wasn’t a bad call. It was the correct call of a bad rule. In other words, although it was obviously not an attempted pass, the rulebook clearly defined losing the ball while your arm is in a forward motion as an incomplete pass and not a fumble. The refs made the correct call according to the rules of the game.
Skammer, you’ve drunk the NFL Koolade. That was a fumble, plain and simple. Nobody, not even the refs, had heard of the tuck rule before. It was a bad call.
It’d been in the NFL rulebook since 1999. Obviously, Walt Coleman was aware of it.
What difference does it make if they had heard of it? The rule is pretty unambiguous:
“NFL Rule 3, Section 21, Article 2, Note 2: When a Team A player is holding the ball to pass it forward, any intentional forward movement of his arm starts a forward pass, even if the player loses possession of the ball as he is attempting to tuck it back toward his body. Also, if the player has tucked the ball into his body and then loses possession, it is a fumble.”
He was in the process of tucking it, but had not yet actually done so. By rule it’s a forward pass. Bad rule, yes. But correctly applied.
I think the two calls made in game six of the 2004 ALCS deserve a mention (Bellohorn’s homerun and A-Rod’s swipe). Kudos to the refs for getting them right eventually, but the initial calls were pretty bad (to be fair, in the case of the A-Rod play, the first base ump was blocked by Mientkiewicz).
That sound you hear is me, choking back the obvious joke. 