you’re reading...

NCAAF

Rivalry Week Preview: #9 Oklahoma State – #13 Oklahoma

Share on Facebook
Post to Google Buzz
Bookmark this on Yahoo Bookmark
[`tweetmeme` not found]

#13 Oklahoma at #9 Oklahoma State

In what should be a high scoring and very entertaining game, Oklahoma and Oklahoma State renew their rivalry Saturday evening in the Bedlam Series. It hasn’t been much of a rivalry when it comes to football with Oklahoma leading the all-time series 81-16-7.  This year may prove to be different as Oklahoma State brings a potent offense and higher national ranking into this match up in Stillwater.

The Cowboys offense will have to contend with a Sooner defense that is excellent at disguising coverages and blitzers. Oklahoma State QB Brandon Weeden will have to rely on his tape study in order to make the correct reads and adjustments. If he only goes by exactly what he sees, he may find a few of his passes headed the other way. Cowboy RB Kendall Hunter could be in for a big game. He is excellent at making plays in space as well as between the tackles. The Cowboys should be able to get him going and open up their tremendous vertical game headlined by WR Justin Blackmon.

Oklahoma is banged up on both sides of the ball, but they will need a lot out of their offense in order to compete with Oklahoma State. Like Hunter, Oklahoma has a game-breaking back in DeMarco Murray that should be in for a big game. The Cowboy defense should be successful in getting pressure on QB Landry Jones, but bringing him down is another story. Jones has pro-level pocket presence and a quick release which gives him an advantage over other Big 12 quarterbacks. Jones should be able to keep the offense rolling through the air, teaming up with WRs Kenny Stills and Ryan Broyles against a shaky Cowboy secondary.

This game should come down to which defense can get a stop when they need to, and if that’s the case, I’ll take the Sooners.

Oklahoma 34 – Oklahoma State 30

Discussion

No comments yet.

Post a comment

Follow Me on Twitter

Error: Twitter did not respond. Please wait a few minutes and refresh this page.