September 29, 2024

This week, the NFL appeared to make a rather perplexing choice regarding a play from the Detroit Lions’ Week 3 matchup against the Arizona Cardinals. For helmet-to-helmet contact with tight end Trey McBride, Lions safety Brian Branch was fined $10,128; McBride, who may have started the collision, was not penalized for the offense.

A replay of the impact makes it abundantly evident that both players lowered their helmets in anticipation of contact and made helmet contact with one another, even though neither player was flagged for the collision.

For needless roughness and helmet use during the play that put Branch and Cardinals TE Trey McBride into concussion protocol last week, the NFL penalized #Lions S Brian Branch $10,128.

Regarding incorrect helmet wear, the NFL rulebook does not distinguish between rules for the offense and defense. Stated differently, the same standards apply to both sides of the ball. This is how the NFL rulebook for 2024 puts it.

ARTICLE 10. IMPERMISSIBLE USE OF THE HELMET. A player commits a foul if they:

(a) lowers his head and strikes an opponent with his helmet firmly; or

(b) butts or makes forceful contact with an opponent’s head or neck region using any portion of his helmet or facemask. Incidental contact between the mask and the helmet during a traditional tackle or block on an opponent is not prohibited under these laws.

The accident resulted in concussions for both players. Branch is anticipated to play this week against the Seattle Seahawks after clearing protocol. However, McBride has been ruled out of the Cardinals’ Week 4 matchup with the Commanders.

In Week 3, the NFL punished the Lions three more times. After the field goal that completed the first half, Branch was shown on replay slapping an opponent, for which he was fined an additional $10,128 for needless roughness. For a hit on a defenseless opponent that went unnoticed during the game, Kerby Joseph was fined $7,505, while Jalen Reeves-Maybin was penalized $11,255 for a late hit.

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *