Around the League

Presented By

Philadelphia Eagles' Chris Polk might move to fullback

Four months ago, former University of Washington running back Chris Polk was considered among the Top 5 backs available in the 2012 NFL Draft. Polk had gained over 4,000 yards on the ground during his 40-game college career and, at 5-foot-10 and 215 pounds, ran a sub-4.6 time in the 40-yard dash.

If it was a surprise when Polk lasted until Day Three of the 2012 NFL Draft, and it was downright stunning that he was not among the 21 running backs to be selected in April. Instead, Polk was signed to a three-year contract by the Philadelphia Eagles that included a $10,000 signing bonus, according to a source with knowledge of the contract.

A few months into his Eagles career, Polk could be moving from running back to fullback, offensive coordinator Marty Mornhinweg said via Tim McManus of

"Certainly that's been discussed and thought of," Mornhinweg said of a position change for Polk. "I think Chris Polk is an excellent football player. I think he is an excellent ball carrier, I think he could be an excellent blocker as well."

According to the Football Outsiders Almanac 2012, the Eagles had a single-back formation on 73 percent of their offensive plays last season, which ranked seventh in the league. Head coach Andy Reid said this week that the fullback position remains a part of the offense. After losing Owen Schmitt -- who played 15.81 percent of the plays last season, according to official playing-time documents -- to free agency, the competition appears to be between Stanley Havili and Emil Igwenagu, an undrafted rookie from UMASS.

Though Polk played tailback in college, playing two seasons with Jake Locker means he's not unfamiliar with being a lead blocker and could possibly join that mix.

"In college, yeah, when we had Jake Locker we did a lot of QB draws, so I was the lead blocker," Polk said. "I'm real familiar with it. I like it. Whatever coaches need me to do, I'm going to do it."

Follow Brian McIntyre on Twitter @brian_mcintyre.

This article has been reproduced in a new format and may be missing content or contain faulty links. Please use the Contact Us link in our site footer to report an issue.

Related Content