Chaos in Kansas City: Brian Branch Suspended after the Lions’ Frustrating Loss Filled with Missed Calls and Controversy
A Heated Ending Overshadows the Game
The Detroit Lions’ 30–17 loss to the Kansas City Chiefs on Sunday night was already frustrating, but what happened after the final kneel-down made it worse.
Lions safety Brian Branch was suspended one game without pay for unsportsmanlike conduct after striking Chiefs wide receiver JuJu Smith-Schuster across the facemask. The incident occurred seconds after the game ended, leading to a brief brawl between players from both teams.
Branch admitted his actions were “childish,” saying he reacted out of frustration after being blocked illegally from behind earlier in the game. “I’m tired of people doing stuff in between the plays, and refs don’t catch it,” he said. “They were trying to bully me out there. I shouldn’t have done it.”
Head coach Dan Campbell condemned the act, calling it “inexcusable” and apologizing to Andy Reid, Patrick Mahomes, and Smith-Schuster after the game. “That’s not what we do here,” Campbell said.
Missed Calls Create Mounting Frustration
Branch’s frustration wasn’t without context. Late in the fourth quarter, Smith-Schuster appeared to block Branch illegally from behind, a dangerous play that went uncalled. It wasn’t the first time Detroit felt slighted by the officiating crew; the Chiefs finished the night with zero penalties, a nearly unheard-of statistic in modern NFL play.
Additionally, late in the fourth quarter of the game, Travis Kelce appeared to lose control of the ball after being tackled on a key third-down play, but officials ruled him down by contact before Detroit could recover. Replays showed the ball clearly moving before Kelce’s knee hit the turf, yet no review was initiated. The Chiefs quickly ran their next play, and Detroit’s chance to turn the game around vanished.
The lack of calls did not go unnoticed by fans or players. Detroit safety Kerby Joseph took to social media after the game, reposting clips and fan reactions, accusing officials of favoritism toward Kansas City. The hashtag #KCRefs quickly began trending as frustrated Lions fans vented online.
Early Touchdown Reversal Sets the Tone
Even before tempers flared, Detroit had reason to be frustrated. On the Lions’ very first drive, a creative trick play seemed to end in a touchdown when running back David Montgomery threw a pass to Jared Goff in the end zone. However, after a lengthy discussion, officials called the play back for illegal motion on Goff. According to referee Craig Wrolstad, Goff “failed to re-establish as a back” before going in motion.
Many Lions players and fans questioned why the flag was thrown so late. Former offensive lineman T.J. Lang said the sequence “looked like someone upstairs made the call” after the fact. “If you see it, you call it right away,” Lang said. “You don’t wait a full minute and then take away a touchdown.” The Lions had to settle for a field goal, setting the tone for a night where officiating felt inconsistent and one-sided.
Suspension Adds to Detroit’s Defensive Challenges
Branch’s one-game suspension comes at a tough time for a defense already dealing with injuries to D.J. Reed and Terrion Arnold. The NFL said Branch’s act was “aggressive and unwarranted,” and pending appeal, he will miss the Lions’ Week 7 Monday Night Football matchup against the Tampa Bay Buccaneers.
In the end, the frustration in Kansas City wasn’t just about officiating; it was about missed chances, as well. The Lions had opportunities to take control early but failed to capitalize, with dropped passes, drive-killing penalties, and a few stalled red-zone trips keeping the door open for the Chiefs. While questionable calls and a missed review on Travis Kelce’s fumble didn’t help, Detroit’s own mistakes made the ultimate difference.
Now at 4–2, the Lions remain atop the NFC North, but Sunday served as a hard reminder: if they want to prove they belong among the league’s elite, they’ll have to learn how to handle the chaos and not contribute to it.