Kansas City Chiefs: Ten Worst Seasons in Team History

Worst seasons in Kansas City Chiefs history: No. 1, 2012 (2-14)

Sigh.

The 2012 season for the Kansas City Chiefs was just downright horrible from the first snap of the season to the final snap of the season. It was one of the few times during a season where I just couldn’t wait for football to be over with so that I didn’t have to watch the Chiefs get embarrassed.

It was THAT bad.

The Chiefs were an absolute joke and were the laughing stock of the NFL that year. It was excruciating to watch week after week.

It was bad to the point where just a few minutes into the first quarter, you knew the game wouldn’t end well. I’m as big a Chiefs fan as they come and even I couldn’t stomach watching how bad the Chiefs were that year. It was painful.

I’m as big a Chiefs fan as they come and even I couldn’t stomach watching how bad the Chiefs were that year. It was painful.

The 2011 season provided some hope for Chiefs fans heading into 2012, as the team showed some spark that year. Instead, we were treated to horrible football and a season that fans want to forget ever existed.

Romeo Crennel had taken over as the team’s interim head coach after Todd Haley was fired midway through 2011, so 2012 was his first full year on the job. Yeah, let’s just say Crennel wasn’t cut out for this whole head coach thing.

One of the biggest problems on the team was that the offense was downright horrendous. Those problems stemmed from the quarterback position (or lack thereof).

Matt Cassel was the unquestioned starter heading into the season, but showed pretty early on that he was not the answer for the team (more on that later).

Next: More on the 2012 season