Preview: Army vs #8 Ohio State

After a long week of bickering and talk from anyone and everyone, game day is finally upon us, and it will turn the page on the previous weeks awful showing at the home opener.  There was a whirlwind of opinions from people dishing their hot takes after the Oklahoma loss at home.  A lot of people got into the conversation, ranging from notable analysts, former Buckeyes, hardcore fans and even potential recruiting targets found themselves in the storm.  Most notably, two top tier 5* targets in OT Jackson Carman and DE Micah Parsons, who were calling their shot and stating their desire to pass on Barrett and go to their “boy” Dwayne Haskins.

A lot of people got into the conversation, ranging from notable analysts, former Buckeyes, hardcore fans and even potential recruiting targets found themselves in the storm.  Most notably, two top tier 5* targets in OT Jackson Carman and DE Micah Parsons, who were calling their shot and stating their desire to pass on Barrett and go to their “boy” Dwayne Haskins.

We all weathered the storm and now an opportunity to right the ship and turn the page is almost here.  The Army Black Knights are 2-0 and they will test the strength of the front seven for the entirety of this contest with an efficient rushing offense that ranks 2nd in the nation with 835 yards and 11 touchdowns on 113 attempts, averaging 417.5 yards per game.

On the other side, the home team Ohio State Buckeyes are surrendering 60.5 yards per contest, holding their opponents to 121 total yards on 64 rushing attempts.  They are allowing 1.89 yards per rush, while only giving up a single rushing touchdown so far this season.

Ohio State is #32 in the NCAA in rushing offense for 459 total yards in 85 attempts for 4 scores. They are averaging 5.4 yards per rushing attempt and 229.5 yards per contest and they must establish a balance to control the pace of the game.

The right side of the O-Line suffered against the constant pressure, so this game will be needed to regain their swagger.  They got beat often and were caught off guard by blitzing defenders, so they really need a boost.

Barrett on the other hand also needs this game to re-establish himself as the starting QB with everyone and their mother bashing him over the lack of down the field pass attempts and the lack of accuracy in his passes.  He is 39-70 for 487 yards and 3 touchdowns against one interception. He is averaging 243.5 yards per game, 6.96 yards per attempt and 12.49 yards per completion, which isn’t bad but he needs to show a lot of improvement in both the accuracy and the production department to truly improve and become more successful.

This Army team appears to be no threat to the Buckeyes through the air and through 2 games, as they are 2-10 for 17 yards.  They are averaging 1.7 yards per attempt and 8.5 yards per game, but they will be a could find a way to involve the running backs, similar to what Oklahoma did.

The Buckeyes linebackers were getting beat by dump-off passes, which could work to Army’s advantage during the game. The linebackers were often out of position and looked confused, so let’s hope they worked out the kinks.

The secondary improved, but tackling was an issue again as they were constantly looking for the big hit instead of wrapping up for the sure tackle.  They need to build on their performance again this week.

Prediction:  41-9 Buckeyes

After that embarrassing loss at home, it will drive the cause the Buckeyes to take a step in the right direction.  The offense improves and executes better, but will still be a work in progress. There will be a balance between the run and pass, and a big play or two will occur, with emphasis on improving the play-calling situation.    

The defense racks up TFL’s against the Army rushing attack forcing them to attempt more passes.  I am calling for a forced fumble and a pick to happen due to the immense pressure that the Rushmen place of the Army O-Line.  

 

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: