An NFL rule explained how the Chiefs got away with holding before the Dolphins' crucial roughing penalty
The refs correctly did not call this holding.
Despite looking like the league’s most dangerous offense for much of the regular season, the Miami Dolphins saw their 2023 campaign come to an end on Saturday in a frigid game at Arrowhead Stadium. And though the offense was quiet throughout the night, the Dolphins could’ve had a chance to get the ball back down 12 points with 13 minutes to play.
Yet, a no-call on an apparent holding and a roughing the passer penalty extended the drive, which result in a Chiefs touchdown. Dolphins fans were fuming about the no-call, but it turns out that the refs were correct to swallow the whistle on the play.
Ignore the blatant hold on the left tackle and call a roughing the passer to bail the Chiefs out on 3rd and 20. It’s beyond laughable at this point anymore. Key moments and it never fails. pic.twitter.com/L4AvE9hsBR
— jtchags2208 (@ChagnonJason) January 14, 2024
We do see an apparent hold by the Chiefs’ Donovan Smith on Justin Houston. But there’s a reason it wasn’t called: the rip-move exception. A rip move is a pass-rush technique where the rusher will rip through the protection by going low and swinging through in almost an uppercut motion.
Houston tried to do that on the play, and NFL rules allow offensive linemen to counter rip moves with blocks that would normally be called holding.
in the rulebook and everything pic.twitter.com/PZyG7G2nQZ
— Nate Tice (@Nate_Tice) January 14, 2024
When the refs identified the rip move, they allowed for Smith’s hold to go uncalled. The Dolphins, of course, didn’t help themselves either by roughing Patrick Mahomes at the end of the play. That’s what really made the difference — the hold/non-hold would have resulted in a Chiefs punt had that roughing never occurred. A similar play happened last year during the Chiefs-Bengals game.
While the refs did call the play correctly, fans still had plenty of thoughts on the play and how little broadcasts mention the rip-move exception.