Kansas City Chiefs: 10 Likes and 10 Dislikes from Week 7 vs Denver

3 of 3

Courtland Sutton #14 of the Denver Broncos is tackled by Morris Claiborne #20 of the Kansas City Chiefs (Photo by Dustin Bradford/Getty Images) /

10* Dislikes

*Actually, just eight.

1. The Sneak

Before the play even happened, I dreaded a sneak by Mahomes. He’s just been so hobbled: I didn’t see the point in putting him in (more of) harm’s way. Sure, other quarterbacks sneak it and don’t get hurt (see: Brady, Tom). Still, I didn’t like the call, and when he was down afterward, I started Tweeting about my displeasure.

When I saw him take off his helmet and it appeared a lot more serious than spraining an ankle, I deleted my original Tweet and instead hit send on an eloquent two-worder.

Initially, I blamed Reid, as some others have done. But after time to reflect, such an injury is just part of the game. It’s no one’s fault: not Reid’s, not Mahomes’ (not that anyone was blaming him), not whoever it was that injured Mahomes.

It’s just football. But that doesn’t change the fact that I didn’t like that play-call whatsoever.

2. Clark’s Penalty on Denver’s First Drive

Out of the gate, the Chiefs defense looked good. But then on a 3rd-and-seven, Clark’s huge mitt went across a face-mask, extending the drive for the Broncos. The Chiefs would’ve had excellent field position after that punt.

3. Rushing Offense

Still a work in progress, it appears. As mentioned, McCoy rant the ball 12 times for 64 yards. Next up was…fullback Anthony Sherman with two carries for seven yards. The Chiefs, as a team, ran it 27 times for 80 yards, which is essentially three yards-per-carry.

4. 3rd-Down Trouble

The Chiefs converted on just five of 15 third downs for the game, well below their season average of over 45%.

5. Red Zone Offense

Two trips into the red zone resulted in zero touchdowns and two field goals for the Chiefs.

6. Breeland’s Penalty on Denver’s First Drive

After Clark’s penalty extended the drive, Bashaud Breeland was later called for defensive holding on a third-down that the Broncos hadn’t converted. Refreshed by the new set of downs, the Broncos soon scored, taking a 6-0 lead.

7. Breeland & Thornhill, Burned

On Denver’s biggest offensive play of the night, wide receiver Courtland Sutton burned Breeland and Juan Thornhill for a 41-yard reception.

https://twitter.com/thecheckdown/status/1185003732531961856

The Broncos would not score on the drive.

8. The Back-Up Quarterback Situation

When Henne went down in preseason, the Chiefs coaxed Moore out of retirement. He was not a roster at all in the 2018 season after spending seven seasons as a member of the Miami Dolphins. His only real season of extended action came in his first season in Miami, back in 2011, when he appeared in 13 games, starting 12 of them. He completed just over 60% of his passes for 2,497 yards with 16 touchdown passes and nine interceptions while being sacked 36 times.

Under him, the Dolphins went 6-6.

For his career, he’s a 59.5% passer in 51 appearances, 30 of which have been starts. In total, he’s tossed 46 touchdowns compared to 36 interceptions while getting sacked 80 times. His Quarterback Rating is 81.2.

I am not enamored with this situation, but here’s the thing: however long Mahomes is down, it’s going to be Moore or Henne.

The Chiefs aren’t going out there to trade for Marcus Mariota or Eli Manning or any other quarterback currently riding the pine. (My preferred target would be San Francisco’s Nick Mullens.) And the Chiefs aren’t going to sign Colin Kaepernick or convince Tony Romo or Brock Osweiler to come out of retirement, and no, you people fawning all over him, the Chiefs will not be bringing back Matt Cassel. (I’m sorry, I had to.)

Next. KC Chiefs: Winners & Losers from Week 7 vs Broncos. dark

You don’t have to like–and I don’t–but it’s down to two guys familiar with the playbook, and those two guys are Matt Moore and Chad Henne.

With Henne still down, it’s all on Moore.

Home/Kansas City Chiefs