Referee Tra Blake’s crew assigned to work Chiefs-Broncos game

The #Chiefs pulled rookie referee Tra Blake and his crew for the first time this season for their Week 17 tilt with the #Broncos.

Rookie referee Tra Blake has been assigned to officiate the Kansas City Chiefs Week 17 game against the Denver Broncos according to Football Zebras.

Blake is in the midst of his third season as an NFL official in 2022. He was promoted from umpire to referee this season in order to replace the recently-retired Tony Corrente. He’s the first official to be promoted to a referee role since Land Clark was promoted to the referee role back in 2020.

Blake has not officiated a regular-season game for the Chiefs or the Broncos this season, but he was assigned to Kansas City’s preseason Week 1 game against the Chicago Bears. His crew called just two penalties for 11 yards against the Chiefs during that game and seven total penalties.

Through 14 games officiated this season, Blake’s crew comes in just behind Carl Cheffers and Clete Blakeman’s crew with 177 total penalties called. His crew has averaged 12.64 penalties per game with 85 on the home team and 92 on the away team. This crew also has tied for the third-fewest dismissed penalties in the NFL.

Like every crew, offensive holding (31) and false start (28) are the most frequent penalties called. Where this crew differs is that they call roughing the passer (12) more frequently than other crews in the NFL. The next-closest crew has four fewer roughing penalties called this season. The Broncos are tied with six other teams for the third-most roughing penalties this season (4), while the Chiefs are tied for the fourth-most (3) with 10 other teams. Unnecessary roughness is also among the top-called penalties by this crew (12), which is tied for the second-most in the NFL this season. Denver and Kansas City are both tied for the fourth-most in the league on unnecessary roughness penalties with six on the year.

[mm-video type=playlist id=01eqbwa53mtds520q2 player_id=01eqbvhghtkmz2182d image=]

[listicle id=143652]

The worst officiating moments from a NFL Week 15 that was full of them

Week 15 in the NFL has been full of awful officiating decisions. Here are the three games that were most affected by those mistakes.

Perhaps the NFL’s officials were confused by the fact that there were games on Saturday and Sunday in Week 15. Perhaps the NFL’s officials were thinking about the last-minute things on their holiday shopping lists. Or maybe it was just late-season exhaustion. Whatever it was, there were a lot of really bad calls in the NFL’s Week 15, and that’s in a season where there have been a lot to date.

Bad officiating is especially notable in the 2022 season, and Week 15 really stood out. Here’s why it’s a problem. Through Sunday’s games, there have been an NFL-record 101 games decided by a touchdown or less.

Per NFL Research, 14 of 15 games that have been completed in Week 15 have been within one score (eight points) in the fourth quarter and there have been 171 games within one score (eight points) in the fourth quarter this season, the most such games through the first 15 weeks in NFL history.

More than ever, the NFL’s idea of competitive balance has come true, but also more than ever, the NFL’s purported idea of officiating competence has been exposed as perhaps an unreachable goal.

Clearly, changes need to be made in the offseason, but before we get into that, let’s review the three games in which the most bad calls happened, and how those calls affected the final result.

Officials explain odd calls on Vikings CB Chandon Sullivan’s two reversed touchdowns

Vikings cornerback Chandon Sullivan had two touchdowns called back by officials against the Colts. Here’s how it was all explained.

Not that it mattered in the end, as the Minnesota Vikings engineered the greatest comeback in NFL history in their 39-36 overtime win over the Indianapolis Colts, but the Vikings also had two fumble return touchdowns by cornerback Chandon Sullivan reversed in this game, and neither reversal made a lot of sense.

With 7:03 left in the first half, and the Colts already up 23-0, Indianapolis quarterback Matt Ryan threw a short pass to receiver Michael Pittman, who fumbled at the Indianapolis 40-yard line. At that point, cornerback Chandon Sullivan picked the ball up and rumbled for a touchdown.

Or so he thought. Referee Tra Blake ruled that Pittman’s forward progress had been stopped, negating the touchdown.

“The ruling on the field was that the runner’s forward progress had been stopped,” Blake told pool reporter Chip Scoggins of the Minneapolis Star Tribune after the game. “Once he’s wrapped up by the defender and his forward progress is stopped, the play is over. So, any action that happens subsequently after that is nullified because the play is dead. That was the ruling on the field.”

Sounds good, except that’s not what happened. On the replay, you can see that Sullivan had Pittman in the grasp, Pittman was arching forward, trying to make extra yards, and it was the hit by linebacker Brian Asamoah that rocked Pittman back. Sullivan stripped the ball just after Pittman moved backward, so we don’t actually know whether Pittman would have kept trying to make additional yards were it not for that hit. If you want to argue that Asamoah’s hit stopped Pittman’s forward progress, that’s an entirely different matter.

There is also the small matter of when the whistle was blown, signifying a dead ball.

“We see plays where running backs extend plays or plays not be blown as fast,” Scoggins asked Blake. “How do you determine when forward progress is? Is there a certain amount of time?

“Forward progress ends once the runner is not making progress towards his goal line any longer. Once we determine that, the play is over.”

Blake also confirmed that forward progress calls are not reviewable, for whatever nonsensical reason.

Sullivan’s bad luck with this particular crew was only beginning. With 3:28 left in regulation, Indy running back Deon Jackson clearly fumbled at his own 38-yard line. Sullivan picked the ball up, and appeared to score another return touchdown.

No dice, as Blake once again ruled against him. This time, the call was that Jackson was down by contact, which clearly wasn’t the case. Upon review, the Vikings were awarded the ball, but there was nothing to be done about the touchdown that should have counted and didn’t. The score was 36-28 Colts at that point, so Blake and his crew were pretty fortunate that the comeback that happened, happened.

“The original ruling on the field was that the runner that was in the pile was down by contact,” NFL Senior Vice President of Officiating Walt Anderson told Scoggins. “Subsequently, a Minnesota player got it back. We had a look and could tell right away that the runner was still up when the ball came loose. We had a good view that it was a clear recovery by Minnesota No. 39.  But the ruling on the field was the runner was down by contact. There was a subsequent loose ball and then a recovery by Minnesota and an advance. Minnesota challenged that and by the time they challenged, we had good views. We had an expedited review to announce that it was a fumble, and we had a clear recovery. But all we could do was give Minnesota the ball at the spot of the recovery.

“It’s technically a dead ball when the officials rule that he’s down by contact. However, the replay rules do allow you to award the defense the ball if that recovery is clearly a fumble and if that recovery is in the immediate continuing action from when the ball comes loose. But you cannot give an advance.”

After the ruling, Sullivan was handed a 15-yard unsportsmanlike contact penalty for taking his helmet off and throwing it on the field, and who on earth could have blamed him?

This, Blake and his crew seemed to see unusually clearly.

“I could feel why he was so frustrated.,” Vikings head coach Kevin O’Connell said of Sullivan. “The first one, they just ruled forward progress stopped. When they do that, doesn’t matter if I agree or disagree with the call. It’s out of my hands at that point. I cannot challenge that. Then I was able to challenge the other one and get that ball out, get that ball back. Some of those stops defensively we had, we just kept on urging them to keep going at the football, see if we can change the game, which we thought we did at that one point, but unfortunately we didn’t. Sully is one of those guys that keeps battling. Veteran player, smart, tough. You don’t win a game like this and hold the team to three points in the second half without guys like Sully gutting it out.”

The NFL has discussed points of emphasis over the years regarding officials holding their whistles on fumbles they think aren’t fumbles to avoid this exact scenario, but we are where we are with that.

4 Lions who must have good days for Detroit to beat the Green Bay Packers

4 Lions who must have good days for Detroit to beat the Green Bay Packers

The 1-6 Detroit Lions attempt to climb out of the NFC North basement when they host the 3-5 Green Bay Packers in Week 9. A win over Green Bay would be a huge lift to a Lions team in desperate need of some positive energy and results.

It’s not out of the question for Dan Campbell’s Lions to pull off the win. Green Bay has lost four games in a row. The Packers rank near the bottom of the league in scoring and also sport one of the worst run defenses.

If the Lions are to pull off the upset in Ford Field, it will require a strong team performance. These four Lions in particular need to have strong games in order for Detroit to extend the win streak against Aaron Rodgers and the Packers to two games.