Buccaneers lose in disappointing fashion (again), this time to Chiefs

Nov 29, 2020; Tampa, Florida, USA; Kansas City Chiefs tight end Travis Kelce (87) is brought down by Tampa Bay Buccaneers cornerback Sean Murphy-Bunting (23) during the first half at Raymond James Stadium. Mandatory Credit: Kim Klement-USA TODAY Sports
Nov 29, 2020; Tampa, Florida, USA; Kansas City Chiefs tight end Travis Kelce (87) is brought down by Tampa Bay Buccaneers cornerback Sean Murphy-Bunting (23) during the first half at Raymond James Stadium. Mandatory Credit: Kim Klement-USA TODAY Sports /
facebooktwitterreddit

Buccaneers lose in disappointing fashion (again), this time to Chiefs

The Tampa Bay Buccaneers dropped yet another game in the most disappointing fashion possible, this time to the Kansas City Chiefs at home.

Everyone knew coming into the game that beating the reigning Super Bowl champions was going to be a tall order, but the Tampa Bay faithful still had hope the team would find a way to be competitive and make the game close.

Instead, what they saw was a Buccaneers team get completely dominated, make a valiant effort just to instill a small amount of hope in a potential upset and then fall flat on their face yet again just when things were starting to potentially swing in their favor.

The Buccaneers fell behind 17-0 early on before cutting the lead to 17-7 off a Ronald Jones touchdown pass from Tom Brady with 4:29 left in the second quarter. The Chiefs added a field goal towards the end of the first half and they took a 20-7 lead into halftime.

As the Bucs trailed 27-10 heading into the fourth quarter, it seemed that it was all over but that’s exactly when the offense finally came alive. Tom Brady found Mike Evans twice for touchdowns and the second one made it a 27-24 game with 4:10 remaining.

Unfortunately, the Buccaneers made too many mistakes and fell flat on their face when it mattered most

You can blame any of the following (and more) for the loss:

  • Tom Brady’s two interceptions
  • Poor play-calling offensively
  • Ineptitude from the defense on the final drive
  • Poor coverage, especially in zone.
  • Drops from the wide-outs
  • Troubles in pass-protections from the offensive line

In the end, though, this is just a story we’re all far too familiar with.

The Bucs give us just enough hope to believe they have an opportunity and then don’t even get a chance to get the offense back on the field for a chance.

If that wasn’t bad enough, we now have to wait two weeks to see this team get back on the field. That just leaves Bucs nation with about 14 days to contemplate which of the 100 mistakes made truly cost the team the game as they continue to circle in what seems to be a never-ending pool of ‘would’ve, could’ve & should’ve.’

dark. Next. Bucs should win-out following Chiefs loss

The Bucs will be back in action Sunday, Dec. 13 at home against the Minnesota Vikings.