Broncos Fans Will Hate What This Chiefs Missed Call Just Confirmed

A missed call on a crucial play adds fuel to the controversy as Travis Kelce candidly admits the Chiefs' questionable advantage over the Broncos.

The Chiefs opened Monday Night Football with a break they probably shouldn’t have gotten, and Travis Kelce knew it.

Kansas City’s first touchdown drive nearly ended before it started. Denver’s Bo Nix threw an interception on third down to rookie cornerback Mansoor Delane, handing the Chiefs the ball at the Broncos 46-yard line. A few plays later, Patrick Mahomes scrambled in for a five-yard touchdown, only for the score to come off the board because rookie left tackle Khalil Benson was flagged for holding.

Then came the next snap, and the play that set off the biggest reaction of the night.

Mahomes took off again, this time from 15 yards out, and Broncos safety Talanoa Hufanga was in position to stop him short of the goal line. But Travis Kelce was clearly holding him, and the officials let it go. Mahomes dove into the end zone, and the touchdown stood.

Joe Buck and Troy Aikman pointed out the foul on the broadcast, but the flag never came. Kelce later acknowledged exactly what happened when he talked with his brother Jason Kelce on the New Heights YouTube show.

“It was definitely a questionable play," Travis Kelce said with a smile while his brother guffawed out loud. "That’s one of those where you get up slowly like, 'Please don’t be any laundry on the field.'

Had the man up by his neck. Can't do it.

Almost cost us. And to be honest, that would have been Pat Mahomes's second rushing touchdown called back in two plays because he literally did the same thing...

And that would have taken us out of the red zone."

Had the officials thrown the flag, Kansas City would have been pushed back to a 2nd-and-goal from the 25-yard line. Instead, the touchdown counted, the extra point made it 7-0, and Mahomes had a score in his first game back after his multi-ligament knee injury.

Denver answered with a strong 68-yard drive capped by a 19-yard touchdown pass from Nix to tight end Evan Engram, but that only brought the Broncos even instead of giving them a lead. From there, things unraveled.

The Broncos were flagged seven times and struggled on both sides of the ball. Kansas City was also penalized seven times, though Kelce’s hold wasn’t the only missed or ignored issue in the game. Benson, the source article noted, held Broncos rush linebacker Nik Bonitto on almost every pass-rushing snap.

Even with that missed call hanging over the night, Denver still made too many mistakes to survive. Sean Payton’s team spent most of the game beating itself, and the Chiefs took advantage.

For Broncos fans, though, the Kelce hold will linger as another example of the benefit of the doubt Kansas City seems to get on a week-to-week basis. Denver now turns to Week 2 against the Jacksonville Jaguars, with the game set for Empower Field at Mile High, though that didn’t help them last year in a 34-20 Week 16 loss to Jacksonville.

In Other News...

Broncos Linebacker Trouble Could Force A Familiar Reunion

Denvers Week 1 loss put a spotlight on a linebacker group that never looked settled, and Alex Singletons return from injury did not smooth things over the way the Broncos hoped. With the middle of the defense under scrutiny, the search for help has already started to feel less like a luxury and more like a necessity if the Broncos want to avoid letting one shaky opener become a longer-term problem.

Cody Barton is the name that keeps surfacing because he brings both familiarity and a possible opening. The Titans linebacker struggled in their opener and could be pushed aside if Tennessee chooses to lean into younger options, which is the kind of roster shift that can put a veteran on the move. For Denver, the appeal is obvious: Barton already knows the organization, and in a spot where the Broncos need steadier play fast, a familiar face might end up looking like the simplest fix. [Read more 🡒]

Alex Singleton Debate Just Got More Heated In Denver

Alex Singletons Week 1 stat line looked busy in the box score, but the tape told a more complicated story for a Broncos defense that came out of the loss to Kansas City with tackling questions hanging over it. Singleton led Denver with 16 tackles, yet some of the missed stops around him became part of the larger conversation about how cleanly the defense played in the opener.

Singleton has already acknowledged the Broncos need to tackle better and said he believes the group will improve this week, but the debate around his performance has only grown louder. His agent added fuel to it on social media by blasting Broncos media coverage as ignorant and incompetent, turning what might have stayed a football discussion into a more pointed one for a team trying to move on quickly from Week 1. [Read more 🡒]

Broncos Need One Offensive Change After Bo Nixs Rough Debut

The Broncos spent the early part of the week sorting through what went wrong in Bo Nixs debut, and the first answer seems to start with the offense around him. In a Week 1 loss, Denvers run-pass balance and some of the situational calls from offensive coordinator Justin Webb left Nix navigating a tough opening assignment against a defense that was able to pressure the rookie and disrupt the rhythm the Broncos wanted to build.

Nixs difficulties were not just about one rough stretch, either. He was dealing with poor pass protection, dropped passes and penalties that kept the offense from settling in, which makes the upcoming matchup with the Jacksonville Jaguars a useful early test of how much can be fixed in a hurry. Denver does not need a full overhaul in Week 2, but it does need a cleaner plan to give its quarterback a chance to play faster and more comfortably. [Read more 🡒]