Chiefs 30, Raiders 27: The Free Wins Are Over. The Giveaways Aren't

I predicted Raiders 30, Chiefs 27.

So technically, I absolutely nailed the final score. Right there on the record.

I just got one minor detail wrong.

The teams.

And somehow that makes this one hurt even more.

Because the Raiders didn't get embarrassed by Kansas City on Sunday. They didn't look like frauds. They didn't spend four quarters hanging on for dear life against Patrick Mahomes. For most of the afternoon they looked like they belonged exactly where they were: undefeated, playing for first place in the AFC West, trading punches with the team that has tortured this franchise for most of the last decade.

The Raiders led 13-10 at halftime. They led 19-17 with less than five minutes remaining. They finished with 437 yards of offense, held the ball for nearly 36 minutes and ran 20 more plays than Kansas City.

Then they gave up 13 points in 19 seconds of game clock.

That's the game. That's the entire damn game.

Kansas City escaped Allegiant Stadium with a 30-27 win, improving to 4-0 while Vegas falls to 3-1. And the frustrating part isn't that Patrick Mahomes finally did Patrick Mahomes things for four quarters. He didn't. The Raiders had this game, and then, in one ridiculous sequence, they handed it away.

19 Seconds That Changed Everything

Let's start there, because there's really nowhere else to start.

With 4:53 remaining, Matt Gay drilled his fourth field goal of the afternoon, a 48-yarder, to put Las Vegas up 19-17. You're at home. The defense has frustrated Mahomes for almost the entire game. The stadium is alive. You're less than five minutes from 4-0 and control of the AFC West.

Finish the game.

Instead, on third-and-5 from the Kansas City 40, Mahomes found Tyquan Thornton behind the Raiders defense for 55 yards, setting the Chiefs up at the Vegas 5. Thornton was hurt at the end of the play and had to be carted off. Hopefully he's alright. Quay Walker was flagged for unnecessary roughness on top of it, which moved the ball from the 5 to the 2.

One play later, Kenneth Walker punched it in from two yards out. Kansas City missed the two-point conversion.

23-19. Still fine. Four-point game, 3:21 on the clock, and Kirk Cousins had been moving the football all afternoon.

Go answer.

Except the offense never got the chance.

On the kickoff, Dareke Young fielded the ball at the 6 and took it out to the 21. Jeffrey Bassa knocked it loose, Jack Cochrane recovered it at the Raiders' 22, and the very next snap was Kenneth Walker again. 22 yards. Touchdown. 30-19.

That's 19 seconds of game clock between Walker's two touchdowns. The Raiders went from leading Patrick Mahomes 19-17 to trailing 30-19 without their offense running a single play. ESPN's win-probability model had Las Vegas at roughly one in four after the Thornton bomb. After the second Walker touchdown, it was under one percent.

That's not getting outclassed. That's not some brilliant Andy Reid chess match. That's a football game detonating in your hands.

And when you're trying to prove you're a contender, you cannot do that.

The Plan Worked. Right Up Until It Didn't.

I spent most of the preview on one idea: don't obsess over shutting Mahomes down. Make him miserable. Hit him. Get pressure without constantly blitzing. Make him work for everything. It's the same formula I broke down in the Chargers film room, and the same one the chaos machine piece was built around.

For three quarters, that's basically what happened.

Mahomes finished 15-of-30 for 225 yards, two touchdowns and no interceptions. Fifty percent completions against Patrick Mahomes? I'll take that every single Sunday. Kansas City converted five of 13 third downs. Travis Kelce caught two passes for 15 yards. The Chiefs had 10 points through three quarters.

The opening drive set the tone. The Raiders kicked off, Walker was stuffed on fourth-and-2 at midfield (Nakobe Dean got him), and Vegas needed four plays to answer. That's almost word for word the dream sequence from the preview: the defense gets a stop, then the script finds the end zone. Cousins hit Ian Thomas for 27 yards on a play fake, the Chiefs defense bit, and Thomas was wide open. Exactly the kind of execution you want against Steve Spagnuolo.

Quay Walker dropped Mahomes for a seven-yard loss right at the goal line before the half, after Thornton's 42-yarder put Kansas City at the Vegas 5. The Chiefs got inside the five with 1:50 left in the half and walked away with a 28-yard field goal. Maxx Crosby and Adam Butler met Mahomes in the backfield together in the third quarter. That's the goal-line stand and the pass rush working exactly like they're supposed to.

Here's the thing, though. A lot of the Mahomes box score is three throws: 41 yards to Xavier Worthy, 42 to Thornton, 55 to Thornton. That's 138 of his 225 passing yards. On his other 27 attempts, he threw for 87 yards.

You can live with that. Most weeks you win with that.

Patrick Mahomes Didn't Beat The Raiders. Kenneth Walker Did.

Walker carried 22 times for 177 yards and two touchdowns. That's 8.0 yards per carry. Kansas City as a team ran for 189 yards at 7.3 a pop.

I flagged this exact matchup in the preview. Vegas entered the game 19th against the run, allowing 116.3 yards a game, against one of the best rushing attacks in football. Eventually something had to give.

It was the Raiders.

Walker had three runs of 21 or more yards, and they added up to 119 of his 177. The big one came on the last snap of the third quarter: a 76-yarder that put Kansas City at the Vegas 8. Thornton caught the touchdown on the second snap of the fourth, a three-play, 84-yard drive that took 40 seconds, and a 13-10 Raiders lead turned into a 17-13 deficit before anybody had finished sitting back down.

Take that single carry away, and Walker averaged 4.8 on the other 21. That's a perfectly fine day for a back, and it's absolutely a day a defense can live with.

But you can't take it away. That's the point.

The Raiders could make Mahomes uncomfortable because they were generating pressure. They could survive some of his third-down magic. They could keep Kelce quiet. None of it matters if Kansas City can simply hand the football to Walker and watch him run through you. Mahomes is already difficult enough to defend when he has to execute 10-play drives. Letting Walker erase eight of those plays for him is suicide.

Four Field Goals In A Three-Point Loss

Here's the other number that's going to bother me.

Four.

Matt Gay made field goals from 32, 48, 44 and 48 yards. Gay did his job. That's not criticism of the kicker. It's criticism of the possessions that ended with him standing on the field.

I wrote this before the game: touchdowns, not field goals. Well. There you go.

ESPN has the Raiders at 0-for-2 in the red zone. One of those trips ended with a field goal. The other was the fourth-and-2 from the Kansas City 18 on the opening drive of the second half, and it deserves its own paragraph, because Vegas actually had three points. Gay's 41-yarder was good. A Kansas City illegal formation penalty wiped it off the board, and the Raiders took the five yards and went for it. Cousins' pass to Jeanty fell incomplete. Zero points. The Raiders had just come out of halftime with the ball, a 13-10 lead and the chance to start the second half the way I'd drawn it up. They left with nothing.

Then there's the 53-yard Dylan Laube kickoff return that opened the fourth quarter and put the ball at the Kansas City 45. The drive produced 19 yards and a 44-yard field goal. That's the short field I've been asking for all season, and it turned into three points.

The numbers say Vegas should have won this game. The Raiders held the ball for 35:42 to Kansas City's 24:18. They gained 437 yards to the Chiefs' 399. They ran 78 plays to 58. They had 28 first downs to 18. Kansas City was dramatically more explosive, 6.9 yards per play to the Raiders' 5.6 and 7.3 a carry to 2.8, but another part is simple: Vegas kept turning productive drives into three points. Kansas City turned its opportunities into seven.

That's the difference between an offense that's good enough to compete and one that consistently wins games like this.

The Raiders can't leave the field saying "well, at least we got points." Not against Kansas City. Not when first place is on the line. Not when you're trying to become the team that ends the Chiefs' run atop this division. When you're inside scoring range against Mahomes, three points sometimes feels like losing four.

Sunday was the perfect example.

Kirk Cousins Was Good Enough To Win This Game

The final throw is going to dominate the box score. It shouldn't dominate the evaluation.

Cousins finished 31-of-52 for 365 yards, two touchdowns and one interception, and he was never sacked. Was he perfect? No. There were misses. There were drives Vegas failed to finish. There were moments Kansas City's four-man rush sped up the offense. But Cousins gave the Raiders more than enough quarterback play to win this game.

And he didn't fold when the game looked dead. Down 30-19 after the Walker, kickoff fumble, Walker nightmare, Vegas could have rolled over. Instead Cousins marched the Raiders 65 yards in five plays and found Brock Bowers for a 20-yard touchdown with 1:46 remaining. Then he hit Cody White for the two-point conversion.

30-27. Suddenly Allegiant was alive again.

They'd come back from 11 down in 76 seconds of game clock.

Then came the part nobody wants to talk about. Vegas tried an onside kick and Kansas City recovered at its own 45. The Raiders spent their last two timeouts stopping the clock on two Walker runs, and on third-and-8 the snap got away from Creed Humphrey. Mahomes recovered it, the Chiefs punted, and Matt Araiza's 52-yarder was downed at the Raiders' 1-yard line with 1:26 to go.

Cousins had no timeouts, 99 yards to go and one chance. He got it to the Kansas City 49 on 11 plays, with a 12-yard conversion to Jeanty on fourth-and-10 and a 23-yard completion to Tre Tucker with 25 seconds left. One more chunk play and Gay potentially gets a chance to tie it.

Instead, with 10 seconds remaining, Xavier Nwankpa intercepted Cousins at the Kansas City 36. Game.

I'm not going to pretend it was a good throw. It wasn't. But I'm also not putting this loss primarily on Cousins because of a desperation interception with 10 seconds left. The Raiders had already lost control of this game several minutes earlier.

Brock Bowers Is Still Brock Bowers (And The Tight Ends Ate)

Another positive buried underneath the loss: the tight ends ate.

Brock Bowers: 6 catches, 86 yards, a touchdown, on 11 targets.

Michael Mayer: 8 catches, 82 yards.

Ian Thomas: 2 catches, 32 yards, and the opening 27-yard touchdown.

That's 16 catches for 200 yards and both Raiders touchdowns from the tight end room. We've spent years watching Travis Kelce create matchup nightmares for the Raiders. It's pretty satisfying to finally have a group that can make Kansas City's defense deal with the same type of problem.

Bowers' touchdown late was especially impressive. Cousins escaped pressure, kept the play alive and found Bowers working across the end zone. That's the connection the Raiders are going to need when games get ugly.

And this game got ugly.

The Jeanty Receiving Game Was Exactly What I Wanted

This might be the prediction from the preview I'm happiest about.

I wrote that if Kansas City clogged the running lanes, Kubiak shouldn't slam Ashton Jeanty into the defensive front 20 times out of principle. Get him in space. Screens. Matchups on linebackers. Jeanty's Year 2 test has been one of this site's running storylines, and Sunday was a good chapter.

Vegas did it. Jeanty managed 58 yards on 15 carries, but he caught six passes for 68 yards on eight targets, including a 28-yard catch-and-run down the sideline. That's 126 yards from scrimmage with the traditional running game never really getting going. I said five or six targets in the preview. He got eight.

Keep doing that. Jeanty doesn't need 100 rushing yards every week to alter a game.

The problem is that the Raiders still need to figure out the rushing part. Vegas finished with 72 rushing yards on 26 attempts, 2.8 a carry. Mike Washington Jr., who I wanted to see get a handful of early opportunities, carried nine times for 18 yards. There was nothing there. Kansas City controlled the line of scrimmage on traditional runs. I flagged losing Jackson Powers-Johnson against Chris Jones in the preview, and to the line's credit, Cousins was never sacked. But when you put 72 yards next to Walker's 177 on the other sideline, it's probably the biggest statistical mismatch of the game.

Special Teams Giveth. Special Teams Taketh Away.

This one is brutal, because special teams almost won the game.

I've been talking about short fields and complementary football all season. Laube's 53-yard return was exactly that, and the return unit has consistently created opportunities. Then, minutes later, special teams produced the play that might have decided the whole game.

Young fumbles the kickoff. Kansas City recovers. Walker scores on the next play.

It's difficult to imagine a more extreme example of how valuable, and how dangerous, special teams can be. One return gives your offense life. Another effectively costs you seven points without the defense even getting a chance to recover.

You don't get to make that mistake with three minutes left against Kansas City. You just don't.

Hezekiah Masses Didn't Get No. 4

Alright. I have to take this one.

I planted the flag. I predicted Hezekiah Masses would pick off Patrick Mahomes for his fourth interception.

Didn't happen. It's graded as a miss on the scoreboard.

The logic wasn't crazy. Masses finished with seven tackles and two passes defended, and Mahomes was uncomfortable all afternoon. But Kansas City's quarterback did the one thing championship quarterbacks absolutely have to do when they're not playing their best football: he didn't give the Raiders the ball.

The Raiders are still first in the NFL with nine takeaways. On Sunday they got zero. Kansas City got two.

That's probably your ballgame.

This Is Why Turnover Margin Matters More Than Yardage

Look at the final numbers without the score:

• Yards: Raiders 437, Chiefs 399
• Plays: Raiders 78, Chiefs 58
• Time of possession: Raiders 35:42, Chiefs 24:18
• First downs: Raiders 28, Chiefs 18
• Third downs: Raiders 5-of-14, Chiefs 5-of-13
• Penalties: Raiders 6 for 30, Chiefs 8 for 59

You'd probably guess Vegas won. Then look at turnovers: Kansas City 0, Las Vegas 2. There's your 30-27. (Kansas City closed as a 3.5-point favorite, per ESPN, so the Raiders covered. That's the kind of consolation that feels worse than nothing.)

The Raiders have built much of this start around creating chaos and stealing possessions. For the first time this season, the opponent was the team stealing them. And Kansas City didn't need many: one fumbled kickoff, one interception with 10 seconds remaining, and zero giveaways of its own.

That's enough.

Grading My Own Homework

Since I'm making you read my predictions, let's grade them. The keys to the game finished 2-for-4: rush four and still get to Mahomes (hit), win on time of possession (hit), win the turnover battle (miss), and play to win (miss). The Masses flag was a miss. The Jeanty-in-space call hit. The short field off a return hit. The stop-them-then-score opening script hit too. The part where touchdowns beat field goals, which I called my biggest offensive key, is the part that got them.

On the Prediction Scoreboard, I'm 3-1 on winners, which is the same record as the team. The pick of Raiders 30, Chiefs 27 got the margin right and the winner wrong. In Beat the Blogger, that's worth exactly three points, which makes it the most valuable wrong pick I've ever made.

I Actually Feel Better About The Raiders After This Loss

And no, that's not moral-victory bullshit.

They lost. They should be pissed. You don't celebrate nearly beating Kansas City. You don't hang a banner because you had a fourth-quarter lead. The Raiders had an opportunity to announce themselves to the AFC and they didn't finish. That matters.

But there's a difference between losing because you clearly aren't on Kansas City's level and losing because you made two catastrophic mistakes in a three-point game. Sunday looked like the second one.

The Raiders didn't need five Chiefs turnovers. They didn't need some bizarre officiating decision. They didn't need Mahomes to completely implode. They went toe-to-toe with Kansas City for four quarters. They held the Chiefs to 10 points through three. They moved the football. They came back from 11 down in 76 seconds. They had the ball near midfield with a chance to tie it in the final 30 seconds.

That's not a team hoping to be competitive. That's a team that should expect to win.

And honestly? That makes the loss more annoying.

My Week 4 power rankings have Kansas City second and the Raiders sixth, which feels about right. You can also relive every snap on the game's Live page, win probability chart and all.

The Free Wins Are Over. The Giveaways Have To Be Too.

I spent the week talking shit, in the Dear Kansas City column and everywhere else. The free wins are over.

And I still believe that. Kansas City didn't stroll into Las Vegas, collect its annual victory and leave. The Raiders made them earn every bit of this one.

But here's the uncomfortable part. If you want to tell everyone the free wins are over, you can't gift Kansas City one.

A 19-17 lead. Less than five minutes left. Thirteen Chiefs points in 19 seconds.

That's a giveaway.

The old Raiders would have walked away from Sunday encouraged that they kept it close. These Raiders shouldn't. They should be furious.

Because 3-1 is still a damn good start. Because this defense is real. Because Cousins can operate this offense. Because Bowers is a monster. Because Jeanty is becoming dangerous in ways that don't show up in the rushing column. And because they just learned exactly how small the margin gets when you're playing the team you want to replace.

Kansas City leaves Las Vegas 4-0. The Raiders leave 3-1, one game back in the AFC West. And instead of wondering whether Vegas belongs in the conversation, I'm leaving Sunday thinking something much more frustrating:

They had them.

Now learn how to finish.

Just win, baby.

Your turn: think you can out-pick me? Beat the Blogger is free, takes a handle and no email, and picks lock at kickoff. Then come back and tell me in the comments where I'm wrong.

More Raiders-Chiefs reading

• Week 4 Preview: Chiefs vs. Raiders - Make Patrick Mahomes Hate Every Snap: the pick, the keys and the Walker warning.
• The Raiders Have Built the NFL's Best Chaos Machine. Patrick Mahomes Is About to Test It: why the defense works.
• Raiders 35, Saints 27: Four Straight Turnovers, One Wild Fourth Quarter, and a 3-0 Start: the last time the turnovers went the other way.
• NFL Power Rankings After Week 3: where the Raiders stood before this one.