KCKingdom
Fansided

Kansas City Chiefs: There is No Quarterback Controversy

By Leigh Oleszczak

Sep 3, 2015; St. Louis, MO, USA; St. Louis Rams quarterback Nick Foles (5) talks with Kansas City Chiefs quarterback Alex Smith (11) after a game at the Edward Jones Dome. The Chiefs defeated the Rams 24-17. Mandatory Credit: Jeff Curry-USA TODAY Sports
Sep 3, 2015; St. Louis, MO, USA; St. Louis Rams quarterback Nick Foles (5) talks with Kansas City Chiefs quarterback Alex Smith (11) after a game at the Edward Jones Dome. The Chiefs defeated the Rams 24-17. Mandatory Credit: Jeff Curry-USA TODAY Sports /
facebooktwitterreddit

The Kansas City Chiefs had a scary situation occur on Sunday when Alex Smith took two bad hits in a game against the Indianapolis Colts. Nick Foles looked good in relief of him, but there shouldn’t be talk of benching Smith.

Ahhh, quarterback controversy. All NFL teams have experienced it at some point, including our beloved Kansas City Chiefs. In 2012, there was the whole Matt Cassel or Brady Quinn debacle, which I think we can all agree when I say we were losers no matter who started there.

In 2006, we had Trent Green or Damon Huard vying for the starting job. The following year it was Huard and Brodie Croyle.

The one most Chiefs fans remember though is Elvis Grbac and Rich Gannon in the late 90s.

Live Feed

Jonathan Taylor Next Team Odds: 3 Contenders That Make Sense for Star Running Back
Jonathan Taylor Next Team Odds: 3 Contenders That Make Sense for Star Running Back /

Betsided

  • Should the KC Chiefs consider an extension for Harrison Butker?Arrowhead Addict
  • Danny Shelton feels ready to contribute to KC Chiefs title defenseArrowhead Addict
  • NFL Rumors: 5 Jonathan Taylor trade packages Colts can't possibly turn downFanSided
  • Caesars + FanDuel Promos: Back Chiefs in Preseason Week 3, Win $450 Bonus + $100 Off NFL Sunday Ticket!Arrowhead Addict
  • Chiefs Rumors: Pacheco injury, Shane Buechele shoutout, QB predictionFanSided

    • So, no, the KC Chiefs are no strangers to the whole quarterback controversy talk. They’re currently hearing this crap right and left at the moment in regards to Alex Smith or Nick Foles.

    Well, let me tell you folks something… There is no quarterback controversy in Kansas City. 

    Even if Smith can’t play this Sunday against the Jacksonville Jaguars and Foles goes out there and lights it up, Alex Smith is still the guy for the KC Chiefs. Smith is in his fourth year with the team and the Chiefs have played well while he’s been taking snaps for them.

    Since Smith joined the Chiefs in 2013, he’s led the team to a 35-18 record. Kansas City has made the playoffs twice during that span and even won a playoff game last year, which was huge for this city.

    When Foles signed this offseason, he knew what he was agreeing to. The 2016 Kansas City Chiefs were Alex’s team and Foles knew he’d be the backup unless something were to go horribly wrong with Smith.

    That’s still the case here.

    As much as I liked the signing of Nick Foles, I knew that if something like this were to happen, that the “quarterback controversy” talks would begin to surface.

    Foles might be better with throwing the ball deep, but Smith has been the leader of this team since 2013. He knows how to win football games. He’s been the leader of this offense for four seasons now and knows the system better than anybody.

    The Chiefs went out and signed Foles this offseason because they knew this season could be special. This season could (and should) result in a playoff berth, but if something were to happen to Alex, then a lot of that confidence would go out the window.

    I don’t think the KC Chiefs would have won that game on Sunday had Tyler Bray had to come into the game for Smith. I don’t think Bray would have thrown for multiple touchdowns and look as poised as Foles did.

    More from KC Kingdom

    That’s why Kansas City signed Nick Foles. He provides insurance in case something happens to the starting quarterback, and that’s just what he did on Sunday.

    As much as I liked the signing of Nick Foles, I knew that if something like this were to happen (Smith having to exit a game for a period of time), that the “quarterback controversy” talks would begin to surface. It’s not an issue here in Kansas City.

    Take this quote from Justin Mosqueda of Bleacher Report as an example of what people are saying as a reason to start Foles from now on.

    "Basically, if you take Smith’s best game in any season he’s played with Kansas City, it looks a lot like what Foles just did on Sunday. In fact, the last time Smith ever had a better passer rating than Foles’ Week 8 effort was in September 2014."

    Foles went out against a terrible Colts secondary and threw for over 200 yards and two touchdowns. It’s not enough evidence to justify benching Alex Smith, who has consistently played well for the Chiefs since arriving here in 2013.

    Next: Top 15 Leaders in Passing Yards for Kansas City Quarterbacks

    We’re going to continue to hear murmurs of this nationwide all week, and possibly next week too if Foles does end up playing on Sunday. Just ignore them. Foles is our reliable backup and Smith is the go-to starter for the Kansas City Chiefs.

    Now, let’s all move on and focus on the next game against the Jaguars, who are just awful.

    Home/Kansas City Chiefs