I saw a prop bet go by that caught my eye. It was built around the longest penalty in the game. They set the over-under at 15.5 yards.

The only penalties that go over 15 yards are on pass interference, so it’s basically a question of whether there will be a PI call accepted of 16-plus yards.

On the one hand, there’s the commonly held belief that when the action moves into the playoffs, the tendency is for the referees to let them play. That was the case for most of the NFC Championship game last week, until there was the huge call on Kevin King at the end.

But at the same time, Kansas City and Tampa Bay are both teams that will take some shots downfield. In Tyreek Hill and Mecole Hardman, KC has a couple of burners who can get downfield (and Sammy Watkins and Demarcus Robinson aren’t slugs either – Watkins had a key long reception in last year’s Super Bowl).

And with the Bucs, they’re overloaded with wide receivers and have the coach with the strongest history of liking to push the ball downfield. It seems like every time I see the Bucs, there’s a long throw on the first or second possession, as if they want to remind the defense of that danger. Mike Evans (pictured) tends to be their most favored receiver on long balls, and he’s a big guy, where he’s often battling for positioning against the defensive back.

I thought this would be an interesting question to explore.

Looking at the stats, they do back up the notion that these offenses will get the ball downfield. In the regular season, only one team (Houston) connected on more passes of 20-plus yards. Kansas City and Tampa Bay were 2nd and 3rd in that category, each connecting on an average of slightly more than 4 passes of 20-plus yards per game.

If there are more passes being attempted to wide receivers downfield, that should increase the odds of a pass interference penalty of 16-plus yards.

RECEPTIONS OF 20-PLUS YARDS
TeamNo
Houston70
Kansas City69
Tampa Bay67
Buffalo66
Las Vegas59
Atlanta59
Detroit58
Minnesota58
Green Bay57
Indianapolis56
San Francisco55
Carolina55
LA Chargers54
Dallas50
LA Rams50
Denver49
Pittsburgh48
Arizona45
Seattle45
Cleveland45
Jacksonville45
Tennessee44
New Orleans44
Philadelphia43
Chicago42
Washington40
Miami40
NY Jets39
Baltimore38
New England38
NY Giants36
Cincinnati35

(Note: Kansas City strangely had only 8 completions of 40-plus yards, which is slightly below the league average – 15 other teams had at least 9. I guess opponents are so worried about Hill that they’re tending to drop their guys into coverage more often.)

The other question here is the “let them play” theory – the idea that officials will be less willing to get involved in determining the outcome of the game. That appeared to be the case in the NFC Championship game a couple of years ago, when Nickell Robey-Coleman was able to avoid a pass-interference penalty, helping the Rams win at the Superdome.

But if we take a step back and look at the bigger picture, it doesn’t seem like officiating gets turned off in Super Bowls. In the last 10 years, teams have averaged 5.8 penalties for 46 yards in championship games.

PENALTIES IN SUPER BOWLS
YearTeamNoYds
2010Green Bay767
2010Pittsburgh655
2011New England528
2011N.Y. Giants424
2012San Francisco533
2012Baltimore220
2013Seattle10104
2013Denver544
2014Seattle770
2014New England536
2015Denver651
2015Carolina12102
2016New England423
2016Atlanta965
2017New England15
2017Philadelphia635
2018L.A. Rams965
2018New England320
2019Kansas City424
2019San Francisco545

That’s not wildly different from what those teams did in the regular season. Those teams averaged 6.6 penalties for 58 yards in those years. The league averages in those teams (including all teams) was 6.5 penalties for 56 yards. So in a rough sense, penalties in Super Bowls tend to be down by almost 1 per team (for 12 yards). That’s slightly lower, but it doesn’t quite reach of the level of referees putting their whistles away.

In short, I don’t anything too conclusive on the prop bet of the longest penalty being 15.5 yards. I don’t feel strongly about it either way.

—Ian Allan