Newspaper article The Florida Times Union

Backup Plans: Best and Worst

Newspaper article The Florida Times Union

Backup Plans: Best and Worst

Article excerpt

Byline: Hays Carlyon

Dallas' season was destroyed by quarterback Tony Romo's shoulder injury last year.

Meanwhile, Indianapolis nearly won the AFC South after losing Andrew Luck.

Why? The Colts had a sound backup in Matt Hasselbeck (5-3 as a starter) and Dallas didn't (1-11 without Romo).

Already there have been shifts in the quarterback landscape with the first preseason game yet to kick off.

The Cowboys lost backup Kellen Moore to a broken ankle on Tuesday, promoting fourth-round rookie Dak Prescott.

The Chiefs wisely boosted their depth, signing Nick Foles on Friday after Los Angeles released him on July 27.

So, which teams have the best insurance policies if their franchise quarterback gets hurt, and which would be in the deepest trouble? Here's the breakdown.



Age: 27.

Career starts: 36, including one in playoffs.

Why he's here: Foles has thrown for 53 touchdowns and 27 interceptions in his career, making the Pro Bowl in 2013. He's one of the best 30 quarterbacks in the NFL, which makes him an easy call for top backup. Kansas City would be able to withstand an injury to starter Alex Smith.


Age: 26.

Career starts: 18.

Why he's here: Glennon performed well as a rookie in 2013, throwing 19 touchdowns and nine picks. His career TD-to-INT ratio is good at 29-15. Glennon never failed; he just stopped getting a chance to prove himself on the field. The Buccaneers might have a star in second-year veteran Jameis Winston. Glennon is a nice luxury for the team to have.


Age: 30.

Career starts: 27, including one in playoffs.

Why he's here: Hoyer has started 22 games over the last two seasons for Houston (2015) and Cleveland (2014). He threw 19 touchdowns and seven picks for the Texans last season. He can keep a team together if he comes in off the bench. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed


An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.