Why Kansas City Chiefs Must Not Turn to Brady Quinn

Lou RomContributor IOctober 1, 2012

GREEN BAY, WI - AUGUST 30:  Brady Quinn #9 of the Kansas City Chiefs looks for a receiver as Darryl Harris #66 moves to block against the Green Bay Packers during a preseason game at Lambeau Field on August 30, 2012 in Green Bay, Wisconsin. The Packers defeated the Chiefs 24-3.  (Photo by Jonathan Daniel/Getty Images)
Jonathan Daniel/Getty Images

Things look pretty bleak for Matt Cassel and the Kansas City Chiefs after another demoralizing loss Sunday at San Diego.

So bleak that it left many Chiefs fans calling for a certain former Notre Dame quarterback to take the reins behind center.

But is now the time for Brady Quinn to get his shot? Or should Cassel get a few more games to turn his year around?

Cassel leads the league with seven interceptions—including three picks in the first half that sealed the Chiefs' fate early.

Since arriving in Kansas City after a monster 2008 season in New England, he is 19-24 as the starter, has completed 57 percent of his passes and is averaging about 200 yards per game.

Cassel has two good seasons to show for his seven years in the league.

His 2008 year, when he stepped in for the injured Tom Brady in New England, he threw for 3,600 yards, completing 63 percent of his passes with a 2-to-1 touchdown to interception ratio. Then in his second year, in Kansas City, he completed 58 percent of his passes for 3,100 yards and had a 4-to-1 touchdown to interception ratio.

Beyond those two years, Cassel has thrown 33 touchdowns compared to 34 interceptions.

Quinn, though, has even less to show for his six years in the league. He has completed barely 52 percent of his passes and has only one more touchdown than interceptions, 10 compared to nine. In his one stretch as a starter, he went 2-7 in Cleveland.

But Quinn's old college coach, Charlie Weis, recently voiced his support for Quinn, saying there is no doubt Quinn would have been an NFL starter under his direction.

“Brady could have been a starting quarterback for me in the NFL. Go back and look at those numbers for the two years he played for me. He was great. He wasn't good. And I know if I had him as a quarterback, I would have felt very comfortable that I could have won no matter where we were." —Charlie Weis as told to the Kansas City Star's Rustin Dodd.

It's hard not to believe Weis, who just happens to be the guy who coaxed the best year ever out of Cassel.

The Chiefs should give Cassel a chance to work out his issues on the field. Even if Romeo Crennel is leaning toward pulling Cassel, he wont' do it until after this week's matchup against the Baltimore Ravens, one of the toughest defenses in the league.

Throwing Quinn, who has not taken a regular season snap since 2010, to the Ravens would be asking for trouble. His next two weeks, against Oakland and Tampa Bay, would be much more forgiving.