The Kansas City Chiefs had a chance to steal a win from the Denver Broncos, but a late first-and-goal sequence unraveled and left them with a 28-24 loss instead. A false start penalty wiped out what would have been a potential game-winning touchdown, and Travis Kelce didn’t hide from the mess afterward.
Kelce, who played despite injury concerns earlier in the week, put together a solid stat line with five catches for 67 yards. That was second on the team behind rookie Emmett Johnson, who finished with 128 receiving yards. Even at 37, Kelce remains a central piece of the offense, leading Kansas City with 343 receiving yards while sharing the team lead in receptions with 24 and touchdowns with two.
But the numbers didn’t soften his frustration. Kelce pointed the finger at himself while talking about the Chiefs’ recent issues.
“The reality of things is that we got to fix a lot. And the little things, mistakes.
And is starts with the person that you're looking in the mirror. And I'm one of them.
I've been frustrated with myself on how long I've been in the league and the procedural stuff that's happened for the past three games,” Kelce said.
“I gotta be better for my teammates. That sets the tone for a lot of people in this room and everybody's just got to up the ante from that.”
It’s not clear exactly what Kelce meant by “procedural stuff,” though he did go in motion on the controversial fourth-and-goal play when a Rashee Rice touchdown was called back because of the false start. Whatever the specifics, the Chiefs are now dealing with back-to-back losses to the Seattle Seahawks and Broncos after opening the year unbeaten.
That’s a different kind of pressure for a team that has long been able to absorb mistakes and still find a way through. Right now, the margin for error looks a lot smaller. If Kansas City wants to stay in the hunt for another championship, the clean-up has to happen fast.
In Other News...
Chiefs Let A Frustrating Broncos Loss Expose A Bigger Problem
A frustrating afternoon in Denver ended with the Chiefs on the wrong side of a 28-24 loss, and the final sequence only added to the irritation. Patrick Mahomes still put up 321 yards and three touchdowns, but Kansas City could not finish when it mattered most, including a key goal-line chance that came up empty late.
The bigger concern was how the offense let a winnable game slip away after a crucial penalty derailed a fourth-down attempt and the final drive never produced the decisive answer. Even the postgame reaction spilled beyond the field, with Brittany Mahomes taking to social media to criticize the referees call, a sign of how sharply the loss landed around the team. [Read more 🡒]
Chiefs Fans Have Every Reason To Be Furious Over This Flag
The late-game sequence in Denver left Chiefs fans with plenty to argue about, because Kansas City seemed to have the winning touchdown in hand on a fourth-and-goal snap before the flag changed everything. What had looked like the defining play of the night instead turned into a stoppage that flipped the pressure right back onto the offense, and the debate over the call quickly spread beyond the stadium.
The reaction was immediate, with fans and commentators questioning whether the movement on the line really justified the penalty. Former Fox Sports host Skip Bayless weighed in, and even Brittany Mahomes joined the chorus of voices wondering about the decision, underscoring how a single judgment call can dominate the conversation long after the game is over. [Read more 🡒]
Mahomes Draws Heat After Chiefs Loss But Video Missed One Detail
The Chiefs second straight loss left plenty of frustration to go around, especially after a late false start penalty helped derail a game they still had a chance to win. Patrick Mahomes made his displeasure with the officiating clear afterward, and the reaction only grew louder when Brittany Mahomes took to social media to criticize the calls as Kansas City slipped to 5-2.
A viral clip then added another layer to the postgame buzz, suggesting Mahomes had brushed off Broncos quarterback Bo Nix instead of offering the usual handshake. But the video did not tell the full story, and the moment became part of the larger conversation around a Chiefs team already dealing with the sting of back-to-back defeats and the scrutiny that comes with them. [Read more 🡒]