The way Navy’s defense has played this year, one mistake by the offense has been enough to put a game out of reach. Three mistakes, and it’s sure to result in a blowout. After Navy’s offense gave up three turnovers on Saturday afternoon, that’s exactly what happened. A homecoming crowd of nearly 37,000 saw Kenny Moore catch 15 passes for 181 yards as Wake Forest thumped Navy, 44-24. The loss, which brought Navy’s record down to 4-3, was the result of poor play in all three phases of the game for the Mids. We’ll start with the offense.

Navy had rallied back from a 14-3 deficit to take a 17-14 lead after a Shun White touchdown run in the second quarter. Wake tied it up with a field goal on their next drive, and Navy took posession on their own 20 following the kickoff. It was at that point that everything pretty much went to hell. On the second play of the drive, Kaipo had barely turned around after carrying out his fake on a counter option when he was met by a blitzing Aaron Curry. The force of Curry’s accelerating 240-pound frame was delivered directly to Kaipo’s face, whipping the quarterback’s neck back and knocking him out of the game. Jarod Bryant stepped in and was promptly blindsided on the next play as he brought his arm back to pass, causing a fumble that was scooped up and returned for a Wake Forest touchdown.

I wrote earlier that the key to Navy’s first two losses this year was turnovers. The third loss was no exception; three Navy turnovers turned into 17 Wake Forest points. The normally sure-handed Eric Kettani fumbled on the Wake 24 as Navy was driving in the third quarter. Jarod Bryant fumbled a snap on the next drive, giving Wake Forest the ball at the Navy 39. And just like that, a game that looked like it was on its way to 34-31 turned into a 44-24 debacle.

Kaipo’s injury was the key play of the game. Navy had three scores on its first three posessions with Kaipo at the helm, but managed only one more (along with three turnovers) the rest of the way. The offense is just a more efficient machine with Kaipo in charge. That’s not a slap at Jarod Bryant as much as it is the reality of developing quarterbacks in this offense. Time and repetition mean everything, and Navy fans have been spoiled with a long line of senior quarterbacks ready to take over year after year. Kaipo isn’t a senior, but the experience that he already has in this offense is comparable to the experience that Navy’s previous senior signal callers have had. While Jarod is a classmate of Kaipo’s, he just doesn’t have the same foundation in the offense, and it shows.

Jarod gets a lot of praise for being a “decisive” runner; Scott Zolak wouldn’t stop using that word during the CSTV broadcast. People say that Jarod appears to be more confident cutting upfield. It’s an illusion. The reality is that Jarod looks decisive because he doesn’t make reads very well. Contrary to what you’re supposed to do when running the option, Jarod decides where he’s going to go with the ball before it’s snapped. If his pre-snap decision happens to take what the defense ends up giving him, then it looks like a “decisive read.” Unfortunately, for every “decisive read,” there’s a play that gets stuffed because the ball went to the wrong option. Paul Johnson recognizes this and does his best to call plays where Jarod can succeed. Think back to Jarod’s biggest plays this season. How many were on predetermined carries? The comeback against Duke was engineered using QB draws. Yesterday, the big plays on the opening drive of the second half came on the midline option, which is the easiest read for the quarterback to make (he only has one key). But you can only draw from that well so many times. Calling these plays can give a defense a different look for a drive or two at the end of the game, but defenses will be able to adjust if they have a whole half to do so. And that’s exactly what Wake Forest did.

It isn’t just in the option game that Jarod is deciding where to go before the snap; he did it in the passing game as well. On two occasions Jarod threw to a double-covered slotback on a wheel route when there was a receiver running wide open on a post pattern over the middle. Jarod never made the progression to his secondary receiver. In fairness, getting hit from behind in the second quarter probably didn’t make Jarod comfortable standing and looking for too long. Nevertheless, those became missed opportunities.

We’ve seen these kinds of struggles from non-senior quarterbacks under Paul Johnson before. Craig Candeto was far more effective in 2003 than he was the previous year. Aaron Polanco looked shaky in his one start in 2002 before stepping in two years later and leading Navy to a 10-2 record. Brian Hampton had a lot of the same problems with pre-determining ballcarriers and receivers before he took over the offense in 2006 and led them to 400 rushing yards in his first game. Jarod is progressing the same way that his predecessors did, but Kaipo’s injury compressed that timeline.

Turnovers were only the beginning of Navy’s problems. Defensively, nobody could stop Kenny Moore. Nobody could get to Riley Skinner, either. As a result, Wake Forest was 10 for 14 on 3rd down conversions. Four of those conversions came on passes to Moore. For the second week in a row Navy’s defense was able to stop the run once in a while on first and second down, only to give up a first down on 3rd and long. Navy had a chance to stop Wake Forest on each of its first three scoring drives, putting the Deacs in 3rd & 6 or more 4 times. Combine the 17 points scored on those drives with the 17 points that Wake scored off of Navy turnovers, and you account for nearly all of their scoring in the game.

The run defense has been inconsistent all year, but in the last couple of games they’ve been able to make a play here and there. Irv Spencer had a season-high 3 tackles for a loss this week. But when those plays set up a 3rd & long, the complete lack of a pass rush gives opposing quarterbacks all the time in the world to make a play, both through the air and with their legs. Navy has never exactly been a sack factory, but averaging less than one sack every two games is insanely low even by Navy standards. It’s especially disappointing given the high hopes that Navy fans had for Nate Frazier and Andy Lark. Physically, they remind you of Babatunde Akingbemi. Yet they haven’t looked like him on the field. Or have they? Akingbemi’s 2004 season was a thing of beauty, but he wasn’t nearly as effective as a junior in 2003. Having a big body is one thing; learning to use it is another. Akingbemi didn’t become a good nose guard until he refined his technique. I suspect the same can be said for Nate and Andy; they really aren’t that far removed from playing games in high school or prep school where they could get away with just overpowering their opponents with sheer physical superiority. That doesn’t fly in Division I football. Like Jarod Bryant, they are probably both a year away from being truly effective. Unfortunately, that doesn’t do this year’s defense much good.

Something else that isn’t doing the Navy defense much good is Navy’s special teams– or more specifically, the kick return coverage. Between Navy’s turnovers and Kevin Marion’s kickoff returns, Wake Forest enjoyed excellent field position all afternoon. That set the defense up for failure. In fact, the defense actually played reasonably well when they didn’t start a drive with their backs against the wall. Wake Forest had 10 drives in the game. Five of those drives started on their own 40 yard line or better. One of those drives was at the end of the game as Jim Grobe ran out the clock. The other four resulted in 28 points. Wake Forest had 5 drives where they had to drive 70 yards or more, and those 5 drives yielded only 9 points. When they were given some field to work with, the defense did its job. It’s hard to believe when you see 44 points on the scoreboard, but the defense was actually a little bit better this week. Not good by any stretch of the imagination… But better.

That’s a mighty thin silver lining, though. It was an ugly game, and Navy can’t afford to have many more like it.

14 thoughts on “Yuck

  1. HunkerDawg

    Good wrap-up. At yesterday’s game, I noticed a couple of those “pre-determined” decisions by JB that were costly. On one, inside the 20, he faked the handoff, the D-End had already commited and he could have cut the ball upfield and gained a significant amount of yardage. However, he’d already pitched and the DE was waiting to pounce on the slotback. I can’t help but wonder if he will move to slot next year. I think he’s a good enough runner and athlete to get playing time, but after yesterday, I’m not sure he can run the FULL offense effectively enough. He’s been in this offense for 3 years so I don’t know how much more he can improve. I just want to see him on the field. And the defense, while porous, was put in some awfully tough spots early. The second KO was flat and had little air time so the coverage wasn’t downfield – at least that’s what it looked like to me. But what the hell do I know? I had been drinking for 2 hours by kickoff! ha!

  2. thebirddog

    Ivin Jasper played both slotback & #2 quarterback for PJ in Hawaii. I think the only reason PJ did that though was because Ivin was good enough to start at slot. I don’t think he’d move Jarod unless he was good enough to start, and I don’t think he would be. Don’t give up on Jarod. He’ll come around. And if you switch him, then you’re left with a sophomore at #2 next year and we have the same problem all over again.

  3. jgish92

    Jarod was not impressive, IMO. From my end zone seats, he clearly missed streaking receivers down the middle because he was focused on the slotback coming out on the wheel route. After watching this game, I think it should be clear to all that Kaipo is head and shoulders better. That’s how I came away from this game. Don’t think it matters if we have Vince Young at QB if we lose the field position and turnover war this badly.

  4. Squeeze

    Damn Phat–great analysis. Esp the Jarod Bryant part. I had noticed a little bit of that but not nearly to the extent that you have elucidated here. Agree about Lark and Frazier, too. I figured some of it was that they were being double-teamed all game every game and that the blame goes to the DEs, but I guess that’s not necessarily the case.

  5. thebirddog

    Yeah. It’s really their job to get double-teamed. If they could force a double-team more often, then maybe our blitzes would actually work once in a while!

  6. I think the DEs play too wide to get double teamed, leaving the Gs to go at the LBs or help double team the NT. They’re also a little too small and most LTs can block them by themselves so no need for the double team. I think JB definitely missed a few reads and should have actually pitched the ball more than he did. I can’t blame the D this week, they gave the offense the ball with a chance to go up by two possessions and possibly three with Navy getting the ball first in the 2nd half.

  7. Gary

    It did look to us that JB was pressing too hard as his passes which were a supposed strength looked like wobbling drunk ducks.
    Perhaps he was grabbing the ball too hard a sign of pressure/stress.
    Regardless when the O seemed to stall and lost its momentum it had when Kaipo was in-the Wake D pinned its ears back and made the rest of the day miserable for all of us.
    This game showed just how overmatched we were against the big boys and I wonder if we are in for some of the same against a larger (yet overall inferior?) ND team in 2 weeks.
    Also should we be as scared of losing to Delaware as I am feeling right now too?

  8. thebirddog

    Overmatched? It’s almost surreal how good our offense is when Kaipo is in, and our defense at least made some stops. I swear you & I watch different games every week, Gary. Wake Forest is the better team, but without two stupid turnovers that game would’ve been at least been close.

  9. Gary

    But you cant tell me that in the 2nd half our O line was not overmatched?
    It seemed to collapse all around JB.
    Most of the second half had the feel of “mop up” time as there was a feeling that we could never come back .

  10. football dad dan

    If one looks objectively @ that Rutgers game, … Take away those two foolish end-zone INT’s thrown by Kaipo, and the “non-called fumble” by Teel right before Rutgers scored that TD (screen pass to Rice) seconds before halftime, … and the outcome of that game goes down to the wire. True too for this WF game —> Take away the fumbles & botched 4th down conversions late, … and Navy is matching the Deacons “point for point” … and another PITT- type game is achieved.
    When Navy reverted to the “passing game” (supposedly Bryant’s strength given his issues w/ running the triple option) is when we had our only 3 & Out.
    We were NOT overmatched, … but as The Birddog so exactly expressed in his analysis, … with the horrible state of the defense, … any (let alone multiple) stumble/hiccup by the Offense is devastating.
    —> Gary’s glass always seems to be “half empty” … and potentially containing some type of “mind altering” fluid??? (o;

  11. Gary

    While I wish it were true about that fluid…I do tend to lean to the half full a bit too much!
    I thought about things again and you guys are right that we really were in there against Rutgers and Wake.
    In fact thats what made me so frustrated was that we were right there with Wake and all this with such a depleted defense.
    But it was all the turnovers that crushed us in both games.
    Instead of focusing too much about the end results I should take more solace in the fact that we were competitive with those teams and could have won.
    The wrong word I used was “overmatched” when it should have been more attributed to the miscues and the Wake pass rush- not that were were overmatched as we were neck and neck for so long.
    Perhaps it was more that we had stalled and they sensed a kill after the Kettani fumble (last gasp).

  12. football dad dan

    It’s probably fair to say that the Navy Defense has been “overmatched” (and “out-manned”) by most of the opponents’ Offenses thusfar this season, … but that is expected given the fact we now have zero returning starters from last season’s senior-laden squad, … where even many of the 2nd stringers were class of 2007. And true, … Once Navy got significantly behind, … and our offense became more predictable (when Kaipo went down), … Wake Forest pinned their ears back & overwhelmed our undersized O-Line. Credit their coaches to recognize that Navy wasn’t running our effective triple option “O” … and it didn’t help that Jarod stunk up the joint throwing the pigskin.
    Delaware worries me because their offense is very explosive (both running & passing), … So any miscue by our offense spells potential disaster. Won’t even touch the ND game for now.

  13. Gary

    I have to admit that when JB went in things went south pretty fast.
    I could not believe his passes were so wobbly and of course his fumbles..
    There was no rooting on our part for any player to get hurt but I thought JB had a chance to really show something and he was way off and Wake was psyched at the predictability we showed.
    Plus there is that comfort level for them of when we are down by 2 TD`s there is no fear of a comeback.
    I too think Delaware could be tough for our D-but so too could Columbia at this time too.
    However that said , I fully expect us to be able to match and overmatch any score Delaware puts up- meaning nothing less than another W would be acceptable.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s