Well, that sucked (but I'm going to dance anyway). Can we bench the 1st team defense for a play or two next week for what was essentially a turnover? From what would have been 4th and 7 and a punt to a continued Pittsburgh drive on an obvious incomplete pass. Anyway, here is your Kansas City Chiefs news from across the internet.
Mellinger: Chiefs Discover New Ways To Fail from KC Star
But looked at from other angles, the Chiefs found new ways to embarrass themselves. So we picked up a few more anecdotes to rehash if and when owner Clark Hunt decides to make major changes.
He already had all the reasoning he needs, but an unforgettably creative one came in the third quarter when the Chiefs did the Chiefs-est thing of the season: a "group celebration" penalty for a touchdown that didn't count on their way to 1-8. The refs called back the score on a penalty, but did enforce the penalty.
So to review: the guys tied for the worst record in the league got flagged for celebrating a touchdown that never happened. This is officially the cockiest terrible team in NFL history.
Lost Points Haunt Chiefs from KC Star
They were the two touchdowns that got away.
Had either one of them held up in the third quarter, the Chiefs likely would have escaped the rain and wind at Heinz Field with a shocking upset of the Pittsburgh Steelers instead of falling 16-13 in overtime.
Primetime Overtime... from The Mothership
In OT, luck seemed to be with the visiting Chiefs. Winning the coin toss and receiving the ball first, Kansas City set up deep in its own territory. With chants of "Defense" echoing across the three rivers, the Steelers responded. A Matt Cassel pass intended for Bowe was intercepted by Steelers LB Lawrence Timmons at their own 28 and promptly returned for 25 yards, setting up K Shaun Suisham's third and final FG, this one a 23-yard game winner.
The Chiefs now return to Kansas City for a three-game home stand starting this Sunday, November 18 against the Cincinnati Bengals.
The 1929 Buffalo Bisons are able to rest comfortably again, their NFL record for futility at the start of an NFL season safe despite the efforts of the 2012 Chiefs.
That's not much consolation for the Chiefs, who took their first lead of the season against the Steelers in their ninth game. They couldn't hold the lead, losing 16-13 in overtime on a cold, rainy night.
Postgame Notes: Chiefs At Steelers from The Mothership
Johnson's Defensive Performance: LB
Derrick Johnsonforced a fumble of RB Isaac Redman. It was his first forced fumble of the season and the 17th of his career. His 17 forced fumbles rank him fourth all time in Chiefs history. He registered 13 tackles (12 solo) in the game. It marks his third double-digit tackle performance of the season. With those 13 tackles, he now has 827 career tackles, tying DB Kevin Ross (827) for fifth in team history.
Baldwin's Return To Pittsburgh Is Disappointing from KC Star
Baldwin, in his first return to Pittsburgh since being taken by Kansas City in the first round of the 2011 draft, caught just one pass in the Chiefs' 16-13 loss to the Pittsburgh Steelers on Monday night.
And worse, he was knocked out of the game after nearly coming up with a 40-yard reception in the fourth quarter.
How did the defense look under new defensive coordinator Gary Gibbs?
The pass coverage was outstanding, forcing Ben Roethlisberger to hold the ball longer than he wanted. It resulted in a third-quarter sack by Justin Houston that sent Roethlisberger to the locker room because of a shoulder injury.
Steelers Drop Chiefs; Big Ben Hurt from The Associated Press via FOX Sports
The Steelers survived a scare from lowly Kansas City on Monday night, winning 16-13 in overtime when Lawrence Timmons intercepted Matt Cassel on the second snap of the extra session and Shaun Suisham hit a 23-yard field goal one play later.
It took some of the sting out of watching Roethlisberger head to the locker room, and ultimately the hospital, with a busted right shoulder after getting slammed to the turf by a pair of Kansas City linebackers in the third quarter.
The Kansas City Chiefs have only one win on the season, but they do lead the NFL in celebrating touchdowns that never happened.
In one dizzying, depressing, hilarious sequence during the third quarter of Monday night's 16-13 overtime loss to the Pittsburgh Steelers, the Chiefs celebrated like they hadn't played with a lead all season.
The Chiefs won a game, of course, beating the New Orleans Saints in overtime back in Week 3. But they went nearly 489 minutes of regulation game time before tasting the sweet nectar of a lead. This is remarkable, especially when you consider how many people believed the Chiefs were actually going to win the AFC West.
(You know who you are.)
Chiefs Penalized 15 Yards For Celebrating A Non-Existent Touchdown from Yahoo! Sports
Yes, the Chiefs were hit with a 15-yard penalty for celebrating a touchdown they didn't score. Instead of fourth-and-7 at their own 26, the Steelers now had a first-and-10 at their own 41.
NFL rules state that any personal fouls or unsportsmanlike conduct penalties stay in effect even if a play is reversed, and that's completely understandable if the penalty is based on an illegal hit or something else that affects player safety. You go after a guy's knee, you should be penalized no matter what. But this is a weird kink in the rules that the NFL needs to change.
Wrap-Up: Steelers 16, Chiefs 13 (OT) from ESPN
So many mistakes: The Chiefs outplayed Pittsburgh but had too many dumb mistakes, penalties and drops. The Chiefs did it all. Yes, there were some questionable calls, but the Chiefs looked like a team that is supposed to be 1-8.
KCChiefs.com Photo Gallery: Chiefs vs Steelers
KCChiefs.com Video: Chiefs vs Steelers Highlights
KCChiefs.com Video: Chiefs Postgame Press Conference
KCChiefs.com Video: From The Podium: Matt Cassel
KCChiefs.com Video: Inside The Locker Room: Week 10