We don't like it either, Trent. (Photo via the AP)

Flashback to Week 1 of the 2006-07 season:

After returning in Week 11 against the Raiders after a nine game hiatus, Trent went 4-3 as the starting QB in our final 7 games. He had 7 TDs and nine INTs in that stretch and lost three fumbles. His best game was, far and away, was the Cleveland game in which he quietly put up 4 passing TDs. Here is a quick rundown of Trent's stats after he returned:

• Oakland: 9/16, 102 yards, No TDs or INts
• Denver: 13/22, 161 yards, No TDs and 1 INT
• @ Cleveland: 24/32, 297 yards, 4 TDs and 1 INT
• Baltimore: 15/27, 178 yards, 1 TD and 2 INTs
• @ San Diego: 23/41, 185 yards, No TDs and 1 INT
• @ Oakland: 12/24, 148 yards, 1 TD and 1 INT
• Jacksonville: 14/21, 181 yards,1 TD and 2 INTs

In 6 out of the 7 games, Trent had one passing TD or less. In three of those games, he had ZERO passing TDs. No wonder there was a city-wide campaign to ditch Trent in favor of Damon Huard. At least with those stats, AP can claim that we should have stuck with Huard.

Unfortunately, we are looking at one of those Bledsoe-Brady situations (Yes, I know that Bledsoe came back to play for the Cowboys but doesn't that seem like a couple of centuries ago?) in which what was a great starter goes down and is virtually forgotten about because the backup plays so well. Does it suck for Trent Green that after years of fantastic, loyal service that he is pushed aside over the course of one season? You're damn right its unfair. But this is also the National Football League. This is also Kansas City. And this is also a city that is losing patience, year after year, with having a perennial "almost made it" team. So, when things are going well in the case of Huard starting in Weeks 2 through 8, people have a right to be pissed off when we bring back a QB that did not get the job done.

And thats what this whole list comes down to in a nutshell. Did the player that was hired to play a specific position (in this case an extremely important one) excel, survive, or bomb within the expectation we had of them? Trent Green bombed this year. He should have never come back as the starter and if he didn't, he would be nowhere on this list. But he did and he played poorly down the stretch of a playoff run and in the playoff game against the Colts.

Trent's place on this list pains me, as I'm sure it does many a Chief fan. But we can't hold on to favorites that aren't performing at a level needed to make a championship run. And so, Trent Green, despite your professionalism and fantastic play for the City of Fountains, you are most deserving of AP's Most Disappointing Chief of 2006-07. You had a steady job and the hearts and minds of the Kansas City faithful in your hands and you could not hold on to them during the most grueling and important moments of the 2006-07 season.

When you're in Kansas City, there are a few things you don't do. You don't try to pull any BS about how Memphis BBQ or North Carolina BBQ is the best in the world. You don't ask if we all live on a farm. And you NEVER, NEVER give the citizens of this great city a reason to EVER, EVER think of Lin Elliot EVER AGAIN.

You see, Lawrence Tynes is a decent kicker. When he lined up for field goals this season, I felt pretty damn good about him making anything 45 yards or less. He had many fantastic kicks this season and there is no real statistical reason to have him on this list anywhere. But his 26 yard miss in the playoff game against Indy was so horribly heartbreaking. I immediately flashed back to Lin Elliot's three missed field goals on January 7th, 1996. And that game was against who else but Indianapolis. Fortunately for Tynes, the Chiefs lost by more than a field goal in 2007, as opposed to 1996 game which ended up with Indy winning 10 to 7.

After 1996 (and the departure of Nick Lowery), you have to understand that in Kansas City we don't ask much out of our kickers. Make the field goals you're supposed to make. Make your longer attempts at least come close to the uprights. And above all, whatever the situation, just don't look like a completely inept NFL player.

Is it fair for Tynes for pay for the mistakes of a NFL kicker turned Texas real estate agent? No it is not. But when you miss a chip shot field goal, against Indianapolis, in the playoffs, you are part of a larger entity in Kansas City called the Ultimate Disappointment.

You're right, Coach. Ten interceptions last year was too many. I'll tone it down. (Photo via Lawrence -Journal)

Oh the hype. The talent. The skill. The wonder that is Ty Law. Brings you back to right before training camp, doesn't it? With Ty Law, we're Super Bowl contenders, right?

I'll be honest with you here since what I've said is easily accessible via the search function to the right. I bought into the Ty Law hype. Did I think Ty Law made us Super Bowl bound? No. Did I think he was a fantastic addition to a weak defense? Of course. Its difficult to argue against the talent of a player who had 10 interceptions in the previous season.

In his first season with the Chiefs, Ty Law had 4 INTs, 1 sack and 61 tackles. To Law's credit, the 61 tackles was the second highest total of his career. But its difficult to forget the various slips and big missed tackles he had, especially in the Pittsburgh game. Really what it comes down to and why Ty Law is on this list at #3 is that he didn't have any big plays. Take a look at the link above to see his career stats and you'll notice that in the vast majority of his seasons, he had at least one (sometimes two) long INT returns for TDs. Game changing plays. Think Champ Bailey last year in the playoffs.

It would have been impossible for Ty Law to live up to the hype that surrounded his debut as a Kansas City Chief. But he's on this list because, for the most part, he wasn't much better than Patrick Surtain.  

Ty Law as a KC Chief [Arrowhead Pride]

Ty Law: Most Exciting Pick Up Since Joe Montana [Arrowhead Pride]

The Kansas City Chiefs Win in a Close One [Arrowhead Pride]

News, news, and more news [Pats Pulpit]

Ty Law Signs with Chiefs; Reunites with Edwards [Pats Pulpit]

Where have you gone, Dante Hall? (Photo via Union-Tribune)

Dante Hall is an unfortunate player to have to put on this list, after he's given Chiefs' fans some fantastic moments in his career. But guess what? Its not 2003 anymore and opposing teams are not afraid of Dante Hall.

2006 was a pretty horrible year for Dante. He had his fewest return attempts (punt and kickoff) since 2001, his lowest kickoff return average (22.8) since 2001 and in case you didn't notice he only put up one return TD this season. If you look at his career stats, you see his numbers in almost all categories go up from his first season in 2000, peak around 2003/2004 and are now steadily dropping off. I know it isn't fair to place a lot of this blame squarely on Dante Hall but he still has to rank as one of the most disappointing players this season.

Lets forget stats for a moment and say what everyone is thinking: Dante Hall has become a joke in Kansas City. After being mentioned as a possible MVP candidate midway through the 2003 season, Hall's returns now have Chiefs' fans yelling, "Just run FORWARD dammit!!!" I am not proud to admit that every time Dante touched the ball this year, I was satisfied if all he did do was run forward. The dodging, the ducking, the reversing field makes him look like some backyard amateur who wants a TD everytime instead of doing what he's supposed to do- set the offense up with good field position.

Will we ever see the Dante of old? Most definitely not. The glory days of Dante's unheralded skill and the skill of the Chiefs' special teams are long, long gone. And I hate to say it but if he is going to have more unproductive seasons at special teams, why the hell is Dante Hall even on this team?

Interesting Records to Look Forward to this Season [Arrowhead Pride]

2003 Playoff Memories [Arrowhead Pride]

2006 Grades [Arrowhead Pride]

You need to work to call it dirty work. (Photo source from SI.com)

Kyle Turley, formerly of the Saints and Rams, had the unenviable position of attempting to replace Willie Roaf at left tackle for the Kansas City Chiefs. In preseason, I wasn't yelling from the rooftops that Kyle Turley was going to be a fabulous LT. I figured he would be part of the emergency surgery O-line that it looked like the Chiefs were going to have. They just needed to keep all of the pieces together long enough to get through 60 minutes of football.

Alas, Turley ended up being a bust. His previous back problems became a recurring problem and he only saw action in 7 games this season. I never realized how ineffective Turley really was until I searched the website here for his name. What comes up? A whole bunch of pre-game injury reports.

I'm calling Turley a disappointment not because of his high expectations- there weren't any- but because he attempted to fill a high profile Chiefs' position and couldn't even make it out of the gate.

Kyle Turley is No Willie Roaf [Arrowhead Pride]