The Kansas City Chiefs And The Curious Case Of Chase Daniel


Dec 28, 2014; Kansas City, MO, USA; Kansas City Chiefs quarterback Chase Daniel (10) drops back to pass against the San Diego Chargers in the first half at Arrowhead Stadium. Mandatory Credit: John Rieger-USA TODAY Sports

Many Kansas City Chiefs fans were ecstatic when they heard that former Mizzou quarterback Chase Daniel was going to come to KC.

Daniel was a standout at the University of Missouri. His career college stats include: passing for 12,515 yards, 101 touchdowns, 41 interceptions, with a career passer rating of 148.9.

Despite the impressive numbers, Daniel went undrafted in 2009, eventually signing with the Washington Redskins. After not making the cut, he was signed by the New Orleans Saints, and became the backup to Drew Brees from 2010 through 2012.

It was in 2013 when new head coach Andy Reid and general manager John Dorsey brought in Daniel for the backup role to starting quarterback Alex Smith. Daniel signed an abnormally lucrative contract for a primarily backup role — three years, $10 million. But despite the large contract, Daniel has only appeared in seven total games, including two starts with the Chiefs. In the games he has started in, he has passed for 405 yards, one touchdown and one interception. Nothing too impressive, but nothing absolutely horrible.

Now we flash forward to the current year. As Jonathan Rhodes spoke about yesterday in his feature on Daniel’s future, the Chiefs only have $2.4 million and change according to, with Daniel accounting for $4.8 million in 2015. That amount of money is far too much for a player who may or may not see the field. But as it stands today, the Chiefs have not cut or tried to trade the high-price backup, at least not publicly. The Chiefs would be able to save $3.8 million if they decided to cut the quarterback, if they chose to go that route.

The Chiefs currently have five — count them FIVE — quarterbacks on their roster this offseason. Alex Smith, Chase Daniel, Aaron Murray, Tyler Bray, and newly signed Terrelle Pryor. Now while it has been reported that Bray suffered a torn ACL injury playing basketball, you could argue there are only truly four quarterbacks on the team. But still, trying to figure out what the Chiefs’ QB situation is, can be somewhat confusing. We know that not all of the QBs will make the final roster for 2015, but trying to pick and choose will be a difficult task.

Dec 28, 2014; Kansas City, MO, USA; Kansas City Chiefs quarterback Chase Daniel (10) scrambles against the San Diego Chargers in the first half at Arrowhead Stadium. Kansas City won the game 19-7. Mandatory Credit: John Rieger-USA TODAY Sports

This brings the main question to the surface, what to do with Chase Daniel? Daniel is a hometown boy, much like recent signing Jeremy Maclin, so fans of Missouri like the fact that Daniel is on the team. But, the fact that he accounts for such a high cap number and it has not been reworked to save room, or that the Chiefs have not dealt the quarterback, makes one wonder if Chiefs are planning to keep him at a high price. Especially when Pryor was signed and both Murray and Bray are a cheaper option for a development quarterback.

What needs to happen is a parting of ways with Daniel. The NFL is currently a quarterback-hungry league and Daniel, who might be a starter for another team should be given the chance to find out. A team like the Houston Texans or the Tennesse Titans might be in the market for a solid quarterback. Keeping him on the bench, not only eats up cap space, which is a luxury the Chiefs cannot afford, but also does not make sense in the long run.

A possible scenario might be a draft day trade for a lower-round pick in exchange for Daniel. Another would be cutting Daniel after the draft in order to sign another free agent in return, after the market has adjusted. Daniel is a good backup, but it might be time for him to leave KC for greener pastures.

What do you think, Addicts? Should the Chiefs keep Daniel? What would you do with Daniel? Let us know in the comments.

Thanks for reading.

Go Chiefs!