The Eagles-Chiefs clash on Sunday night was easily the most anticipated game of the NFL’s Week 2 schedule. A rematch of last season’s Super Bowl, it carried more weight for the Kansas City Chiefs, who entered the contest desperate to avoid a dreaded 0-2 start after a disappointing opening-week loss to the Los Angeles Chargers in Brazil.
For Chiefs fans, this wasn’t just about a regular-season victory; it was about redemption against the Philadelphia Eagles, the very team that denied them back-to-back Lombardi Trophies last February.
However, everything the Chiefs feared came true. The Kansas City Chiefs once again fell to Jalen Hurts and company, losing 20-17 at Arrowhead Stadium. That result dropped Andy Reid’s squad to 0-2 for the first time since 2014.
The opening half of the game lived up to the hype, showcasing the physicality and intensity expected from two championship-caliber teams. Saquon Barkley powered into the end zone late in the first quarter with a 13-yard touchdown to give Philadelphia the early advantage.
Kansas City responded in the second quarter. Harrison Butker drilled a 56-yard field goal before Mahomes brought Arrowhead to its feet with a 20-yard touchdown scramble. Just when it looked like the Chiefs would enter the break with momentum, Eagles kicker Jake Elliott silenced the crowd, nailing a stunning 58-yard field goal as time expired. The teams went into halftime deadlocked at 10-10.
The second half proved decisive. Philadelphia edged ahead in the third quarter on Elliott’s 51-yard field goal, then extended their lead in the fourth when Jalen Hurts muscled in from a yard out. Kansas City had a chance to swing the momentum back when they reached the red zone, but a Mahomes pass intended for Travis Kelce was intercepted by rookie safety Andrew Mukuba, arguably the game’s turning point.
Mahomes refused to go down quietly, connecting on a 49-yard touchdown strike to Tyquan Thornton with just over three minutes left. But it wasn’t enough. The Eagles’ defense held firm in the closing moments to secure a 20-17 road victory.
For Kansas City Chiefs, Mahomes completed 16 of 29 passes for 187 yards with one touchdown and one interception, adding 66 rushing yards and a rushing score. But without suspended wideout Rashee Rice and injured rookie Xavier Worthy, the Chiefs’ offense looked limited. Kelce, meanwhile, struggled to make a significant impact, fueling visible frustration on the sidelines.
This marks the third straight loss for Kansas City if you include last season’s Super Bowl defeat. The defending champions now find themselves in rare and unfamiliar territory, starting 0-2 and facing growing pressure. History is not on their side; only four teams have ever reached the Super Bowl after losing their first two games.
The Chiefs will aim to turn things around when they travel to face the New Orleans Saints in Week 3 at Caesars Superdome on Sunday, September 21. Kickoff is scheduled for 1:00 p.m. ET.
“We played two good football teams and made mistakes in big moments,” Elite Quarterback Patrick Mahomes Blames Costly Mistakes for Chiefs’ 0-2 Start
After the game, Patrick Mahomes didn’t shy away from addressing the team’s struggles. The two-time MVP acknowledged that starting 0-2 is unfamiliar territory for both him and head coach Andy Reid, but insisted the team isn’t far from getting back on track.
“We played two good football teams and made mistakes in big moments, stuff that we’re not used to doing,” Mahomes admitted. “It’s one guy here or there, it’s not like we’re missing by much. I know it sucks to hear for the fans, but I feel like we’re close. Obviously, we’ve never been 0-2, but we’ve dealt with challenges and we’ve lost games.”
Mahomes pointed to his interception at the goal line, a pass intended for Travis Kelce that went straight into Andrew Mukuba’s hands, as an example of the costly miscues that defined the night. Though Kelce took responsibility on the sidelines, Mahomes insisted it was his own mistake, saying he threw the ball too early.
Despite the rocky start, Mahomes maintained confidence. He stressed that the Chiefs’ issues aren’t systemic but rather small execution errors that can be corrected. Still, the urgency is undeniable. With back-to-back losses and an unforgiving schedule ahead, Kansas City knows its margin for error is shrinking fast.
Read Also: Commanders RB Austin Ekeler Suffers Torn Achilles vs. Packers, Out for Remainder of 2025 Season
Frequently Asked Questions (FAQs)
When was the last time the Kansas City Chiefs started a season 0-2?
The Chiefs last opened a season with back-to-back losses in 2014, before Patrick Mahomes became the starting quarterback. That year, they went on to finish 9-7 and missed the playoffs, a reminder of how dangerous a slow start can be.
What was the final score of the Eagles vs. Chiefs game in Week 2?
The Philadelphia Eagles defeated the Kansas City Chiefs 20-17 at Arrowhead Stadium. The game was tight throughout, but a late interception thrown by Patrick Mahomes proved costly for Kansas City.
Who were the standout performers in the Eagles’ victory?
Jake Elliott was crucial, drilling three field goals, including two from beyond 50 yards. Jalen Hurts also added a rushing touchdown, while rookie safety Andrew Mukuba made the game-changing interception in the fourth quarter.
Who do the Chiefs play next after their 0-2 start?
Kansas City will face the New Orleans Saints in Week 3 at Caesars Superdome on Sunday, September 21, with kickoff set for 1:00 p.m. ET. The matchup provides a chance for the Chiefs to finally secure their first win of the 2025 season.