Jump to content
View in the app

A better way to browse. Learn more.

Our Beloved Ducks Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Posted
  • Moderator
No.

I've seen many plays flagged for targeting that seemed like incidental contact but the non call last night seemed like a text book example of it to me. Does anybody know how the replay booth could watch that in slow motion and say nope? That looked full force, head lowered for to create impact then crown to crown impact. If that wasn't targeting, then how does the less severe incidents get so regularly called? This call seems far from consistent.

No.

#1 Because the player made a football move he wasn't defenseless, despite the fact he was been restricted by another tackler. This is a major oversight of the rule that can and should be fixed.

#2. The region of his helmet that made contact was just outside of what is considered the crown of the helmet per the current rule.

On a reddit game thread evn the PSU fans were asking about why it wasn't targeting.

The rule is still a work in progress and I expect the Ducks football program is going give the B1G offices heck for fixing the rules so players don't get hurt in this situation that clearly meets the intent of what the rule is trying to prevent, yet rules it acceptable.

  • Moderator
No.

Unfortunately, it is probably going to take a player down for the count with a major concussion before they reverse these dangerous, hairsplitting rule changes.

No.

If you ask me, it's targeting. There was helmet to helmet contact and the defender did seem to launch himself.

Incidental contact is often something where the offensive player moves in a split second and there is no way for the defender to move.

Also... The targeting rule is all about safety theatre not player safety. I wrote the article below a few years ago but I think it's still relevant to this.

https://fishduck.com/2022/03/the-targeting-rule-is-not-about-player-safety/

No.

One other point. That's also irrelevant.

I don't think the PSU player's action was malicious. He wanted to make a play and Limar was already low to the ground, he may have already been down.

But intent has no say in the rule. There are some actions players take that it looks intentional and malicious and I do believe those should be punished more than incidental contact.

The reality is that to make this rule really about player safety any helmet to helmet contact that takes place should result in all parties involved leaving the game to get checked out by a third party doctor/medical specialist to assess for concussion.

Ejection from the game should only be enacted if the conduct appeared malicious which goes to intent which is always difficult to determine but somehow you just know it when you see it. I know players are no longer required to leave the stadium for targeting but are effectively suspended for 1 half of game play.

I probably can write more on this topic and there is a lot more to get into but the rules are play right now are for show and frustrating.

No.

When they start excusing it by saying, "well, that looked closer to hairline impact, rather than actual 'crown' of the helmet", methinks somebody is looking for a way to excuse...

Create an account or sign in to comment

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.