Darren McFadden: Latest Update on Injured Raiders RB

Jeremy SickelContributor IIIDecember 10, 2012

OAKLAND, CA - DECEMBER 06:  Darren McFadden #20 of the Oakland Raiders runs with the ball against the Denver Broncos at O.co Coliseum on December 6, 2012 in Oakland, California.  (Photo by Ezra Shaw/Getty Images)
Ezra Shaw/Getty Images

The Oakland Raiders returned to normalcy last Thursday night when running back Darren McFadden was in the lineup against the Denver Broncos.

While his 64 total yards and one score on 13 touches were certainly positive signs, McFadden tweaked his injured right ankle and would finish the game on the sidelines.

This is the same injury that kept the running back out of action the previous four games—seeing the field last against the Tampa Bay Buccaneers in Week 9.

After a breakout season in 2010 that saw McFadden rush for 1,157 yards and seven touchdowns, he has played in and started only 16 out of a possible 29 games since.

For what it is worth, however, McFadden was seen at the Raiders team facility Friday morning with no visible effects from re-injuring his ankle. How Oakland handles this situation going forward is anyone's guess.

With McFadden still under contract through next season, the Raiders will soon have to make a decision about his future with the organization. The running back is due a cap hit of $8 million in 2013—a lofty number for someone that has such a hard time staying on the field.

The Raiders are obviously a better team with McFadden as their featured back. But at 3-10, this team is going nowhere in 2012 and sitting their star—and possibly saving his career—should become the point of emphasis.

Regardless, McFadden will want to hit the field if he is healthy enough to do so. Proving he can overcome this injury will be the deciding factor on whether or not he gets another contract as a starting running back after this one is up.

The long layoff between games will help both McFadden and the Raiders settle on the running back's status for the Week 15 matchup with the Kansas City Chiefs.

As the week progresses, we should know more about this situation.


Follow Jeremy on Twitter @KCPopFlyBoy.