Brady Quinn: Naming QB Starter Is an Indication Chiefs' Season Is Over

Jessica MarieCorrespondent IIMarch 26, 2017

TAMPA, FL - OCTOBER 14:  Quarterback Brady Quinn #9 of the Kansas City Chiefs warms up for play against the Tampa Bay Buccaneers October 14, 2012 at Raymond James Stadium in Tampa, Florida.  (Photo by Al Messerschmidt/Getty Images)
Al Messerschmidt/Getty Images

If it wasn't already obvious by the Kansas City Chiefs' 1-5 record that their season is circling the drain, it is now.

It's not as though Kansas City really had any choice but to replace quarterback Matt Cassel with Brady Quinn, whether they're doing it for injury purposes or common sense purposes. Cassel has displayed no indication that he can competently lead this team, and over the last few years, he's been utterly unable to dodge the injury bug.

The Chiefs were looking for the Quarterback of the Future, and they thought they'd found him in Cassel. They were sadly mistaken.

Three-and-a-half seasons is enough time to show what you're worth, and in those three-and-a-half seasons, Cassel only had one good one—two years ago. Last year's campaign may not have been his fault because of the devastating injuries that afflicted the Chiefs—he himself was limited to just nine games—but there's no excuse for this season.

A 1-4 record means a change is gonna come, and after a concussion and an excruciatingly pathetic 9-6 loss to the Ravens, that change came in the form of Quinn starting against the Buccaneers in Week 6.

Quinn's first start since 2009 didn't go much better than any of Cassel's attempts this season: He threw for 180 yards, zero touchdowns and two picks in a disheartening 38-10 loss.

Disheartening, because for the last two weeks, the Chiefs offense has posted a mere 16 points.

Disheartening, because Kansas City was hoping Quinn would provide the kind of spark this team needed to put a few wins on the board—and judging by this fiasco in Tampa Bay, that doesn't seem to be in the cards.

And yet, according to the Chicago Tribune, the starting job is Quinn's to lose. Cassel is still recovering from the concussion he suffered in Week 5 against the Ravens. The Chiefs are one of the worst teams in the NFL, and they can only go up from here.

The worst that can happen is that KC will continue to be terrible. The best that can happen is that Quinn can miraculously turn this team around. In him, they have a healthy mediocre quarterback; in Cassel, they had an unhealthy mediocre quarterback. Looking at it like that, the decision to start Quinn seems to have been a fairly easy one.

But it's also an indication that the Chiefs have nothing to lose. And you never want to feel that your team is in that kind of position. You never want to feel like your team has already thrown caution to the wind when it's only Week 7.

There may not be a lot to indicate that Cassel is going to get this team going in the right direction, but there's certainly not a lot to indicate that Quinn can do what Cassel cannot. Quinn, too, has had six seasons up until now to prove himself. He had ample opportunity to establish himself as a capable and competent starter with the Browns in 2009, in his third season with the team.

That year, he started nine games and went 2-7. He threw eight touchdowns and seven interceptions. In four years in the NFL excluding this one, that was the only time in which his TDs outnumbered his INTs—and it was only by the slimmest of margins.

Quinn is no spring chicken. He's 28 years old. He's not a rookie coming in here trying to re-energize this team with his youth and exuberance.

He's just another option that is simply no worse than the first ineffective one.