Hey Chiefs Fans, Boo All You Want, but Brady Quinn Isn't Better Than Matt Cassel

Gary Davenport@@IDPSharksNFL AnalystOctober 15, 2012

TAMPA, FL - OCTOBER 14:  Quarterback Brady Quinn #9 of the Kansas City Chiefs tumbles after releasing a pass against the Tampa Bay Buccaneers October 14, 2012 at Raymond James Stadium in Tampa, Florida.  The Bucs won 38 - 10. (Photo by Al Messerschmidt/Getty Images)
Al Messerschmidt/Getty Images

There's an old saying that, "You should be careful what you wish for, because you just might get it."

Some fans of the Kansas City Chiefs would be well-served to remember that axiom, because one week after fans cheered while quarterback Matt Cassel lay injured on the field at Arrowhead Stadium, those fans got their wish with Brady Quinn taking the reins under center when the team faced the Tampa Bay Buccaneers Sunday.

The results should have surprised absolutely no one.

The Chiefs were trounced by Tampa Bay 38-10, and Brady Quinn played like, well, Brady Quinn, throwing a pair of interceptions, one of which was returned for a touchdown by cornerback Ronde Barber.

Given that Kansas City's only touchdown of the day was scored on a fumble return, the sixth-year veteran scored more points for his opponent than he did for his own team, although head coach Romeo Crennel defended his quarterback's play according to The Associated Press via Fox News.

"It was not the quarterback's fault," Crennel said. "He wasn't as sharp as he would have been if he had had plenty of reps and all that, but he wasn't the cause of it. It was a team effort that screwed things up and we've got to fix it as a team."

It may not have been all Quinn's fault, but he didn't help matters any more than Cassel has.

Listen, as a Cleveland Browns fan, I understand all too well how frustrating it can be to try to support a team that continually puts a substandard team on the field. It's absolutely maddening, and it can lead to a desire for change, any change to shake up a status quo that just results in one frustrating Sunday after another.

I can also understand why a great deal of that frustration is aimed at Cassel, who parlayed one decent season in New England into a $63 million contract that now sits atop general manager Scott Pioli's head like a really expensive dunce cap.

Cassel has been somewhere between mediocre and terrible for the majority of his tenure in Kansas City, but once he's been cleared to play, all starting Brady Quinn over him indicates is that the Chiefs are serious about being in the running for West Virginia quarterback Geno Smith in next year's NFL draft.

This is Brady Quinn we're talking about, folks; a first-round bust who has never posted a quarterback rating of higher than 70 in a season and who has been unable to beat out such future Hall of Famers as Derek Anderson, Tim Tebow, and yes, Matt Cassel, for starting gigs on his three NFL teams.

As a starting quarterback, he makes for a serviceable backup.

So, as disheartening as it may seem, once Cassel's healthy, the team needs to run him back out there if they are at all serious about winning another game or two this year.

Or they can stick with Quinn and get a head start on next year's draft preparation.

Whatever they wish.