KCKingdom
Fansided

KC Chiefs: Five Worst Starting Quarterbacks In Team History

facebooktwitterreddit
Prev
3 of 10
Next

Tyler Palko #4 of the Kansas City Chiefs (Photo by Chris Trotman/Getty Images)

It just keeps getting worse and we’re only at number four.

The 2011 season was a weird one for the Chiefs in general. They would go from looking terrific to looking awful in the span of a week. A lot of that fell on Matt Cassel’s shoulders, but boy did fans miss him when he ended up having to go on injured reserve halfway through the season.

The Chiefs went on to get embarrassed that night at Gillette Stadium (losing 34-3), and it was pretty clear that Tyler Palko wouldn’t be the answer at quarterback for this team.

Cassel being placed on IR meant that fans were now counting on one Tyler Palko, formerly of Pittsburgh University. No one really knew much about Palko, as he was only briefly a member of the New Orleans Saints and didn’t do much with them at all.

Once Cassel was lost for the season, Tyler Palko was thrown into the starting quarterback position and did not do well in the least bit. It didn’t bode well for Palko that his first NFL start would come against the New England Patriots on Monday Night Football in Foxborough. Of all of the places to play at, Palko got one of the toughest stadiums in the league, and didn’t fare well.

Palko managed to throw for over 200 yards in his first start, but he was picked off three times in that game. The Chiefs went on to get embarrassed that night at Gillette Stadium (losing 34-3), and it was pretty clear that Tyler Palko wouldn’t be the answer at quarterback for this team… Not that anyone thought he was.

Following that loss, the Chiefs went out and claimed Kyle Orton off of waivers.

Next: More On Palko