Skip to main content

Top Oklahoma RB Keith Ford out 2-3 weeks with injury


Oklahoma is riding high after a big win over Tennessee on Saturday and is tied for third in the latest CFB 24/7 Top 25 Power Rankings. Things might be a bit tougher for the team as Big 12 play begins this week, though.

Sooners head coach Bob Stoops announced on Monday's Big 12 coaches teleconference that top running back Keith Ford would miss the team's upcoming game against West Virginia and could be out as long as three weeks after injuring his leg.

"He won't play this week for sure, and after that it's a little unsure," Stoops said. "There's a small fracture, from what I understand, on the non-weight-bearing bone (in Ford's foot). That can be anywhere from two weeks to three. You don't really know. So for sure he won't play this week."

Ford went to the locker room in the second half of Saturday's game and did not return to action against the Volunteers. He finished the game with 15 carries for 56 yards and scored two touchdowns in Oklahoma's 34-10 win in Norman.

In addition to missing West Virginia, Ford will likely not see action during Oklahoma's trip to TCU but should be back in time for the team's annual rivalry game against Texas in Dallas.

The 5-foot-11, 206-pound Ford leads the team in rushing with 194 yards and five touchdowns. While Ford's absence will be noticeable on the lineup card, freshman Samaje Perine and sophomore Alex Ross have seen significant time as part of the backfield rotation and should be able to handle an increased load.

If there's one area where Ford will be missed, it's as a pass-catching threat, considering he's made six catches for 100 yards and a touchdown this season. He's one of the team's top backs in pass protection, too.

With quarterback Trevor Knight and company on offense, the Sooners can likely absorb the loss of Ford, but early season injuries before a pair of road conference games is never a positive thing for a team with College Football Playoff aspirations.

You can follow Bryan Fischer on Twitter at @BryanDFischer.

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