# @thekansascitystar on Instagram

- **Type:** Image
- **Original URL:** https://www.instagram.com/p/Cw8HypNtkoP
- **Gondola URL:** https://gondola.cc/posts/8564921-thekansascitystar-instagram
- **Thumbnail:** https://img.gondola.cc/tr:w-,h-,fo-auto/thumbnails/af54306b14.jpg
- **Posted:** 2023-09-08T17:34:55.000+00:00
- **Account Owner:** Kansas City Star (@thekansascitystar) — https://gondola.cc/thekansascitystar

## Caption

There came a sequence at the close of the first half in Thursday night’s Chiefs game when Patrick Mahomes just plain took over. The running game was non-existent. A case of the drops had infected more than half the receivers room. 

But who cares? The Chiefs still had the quarterback. And in this sequence, Mahomes turned third-and-17 into a dime for 34 yards and a first down, then followed a secondary read for 26 more, and then tossed a go-ahead touchdown. 

He tried to do it all himself, and for a while, it looked like he just might. 

Until his coach took the ball out of his hands in the fourth quarter.

The Lions beat the Chiefs 21-20 in an NFL season opener in which so very little went right offensively for the defending champions — other than Mahomes. 

We could chat for a long time about how many points the Chiefs lost on dropped passes alone. But on a night in which Mahomes actually was going right, the Chiefs put the game in the hands of just about everyone else. 

The kicker. The punter. The defense. Heck, even the third-string tight end.

So why not Mahomes? Read Star columnist Sam McDowell’s full commentary at the link in our bio. 

📸: @wagsphoto

## Stats

- **Views:** 0
- **Likes:** 1,054
- **Shares:** 0
- **Comments:** 44

## Credits

| Name | Username | Profile | Role |
| --- | --- | --- | --- |
| Kansas City Star | @thekansascitystar | https://gondola.cc/thekansascitystar | Newspaper |
| Nick Wagner | @WagsPhoto | https://gondola.cc/WagsPhoto | Photographer |

---
Copyright (c) Gondola