Week 4 Game Balls

Written by Dan McGrain1 Comment »

Offensive Game Ball: Ray Rice. Rice ran for more than 100 yards on just 11 carries, including a 50 yard run that set up the Ravens third touchdown and made it a three point game. Rice also gets the game’s underused game ball for only seeing 11 touches. Even 10 carries for 50 yards sounds good (Rice’s numbers minus his big run), so we all have to be wondering why Cam didn’t put the ball on the ground more.

Feelin’ Fine Ball: Ray Lewis. Because I’m feeling a fine coming his way for his post game remarks. I didn’t agree with every call on the field out there today, but the Ravens need to learn how to take their losses and the game’s circumstances and move on.

Lesson Learned Ball: Terrell Suggs. Asked post-game about his personal foul on Tom Brady, Suggs replied quietly, “it is what it is.” That shouldn’t be taken to mean Suggs liked the call, but he knows how to keep his pay check fat.

Buddy Buddy Ball: Tom Brady. Brady played a good game. But between his Manning-esque “flag wrist” asking for a personal foul and the closing shot of Brady walking off the field with the refs… I can’t help but think it. These refs know they have a job to protect the league’s stars.

Fired Up Ball: John Harbaugh. I’ve got mixed feelings on Harbaugh’s tantrum. I don’t think it cost the Ravens as much as some fans do, but there’s no way to tell. I do know that I want my coach to care enough that he’s ready to go. First time we’ve seen Harbaugh go off like that. Probably won’t see it again for a while.

Read the rest of this entry »

Patriots 27, Ravens 21: The Blame Game

Written by Dan McGrainNo Comments »

I’ll get to a more complete review of the game tomorrow, along with our not-so-standard game balls. But for now, it’s time to play something we like to call The Blame Game.

Offensive Play Calling / Cam Cameron: 40%.

Dear Cam, take a look at the numbers. Your offense ran the ball just 17 times for more than 100 yards, averaging 6.8 yards per rush. Meanwhile, you threw the ball 47 times for 264 yards, averaging just 5.6 yards per attempt. What does that mean? That our rushing game was actually far more effective than our passing game.

I don’t know that anyone thought the winning team in this game would come out with fewer than 25 rushing attempts… let alone fewer than 20. The Pats, despite managing only 85 yards, ran the ball 30 times. Where was Le’Ron McClain on 4th and short?

And please don’t give me that “game circumstances forced us into a different mode.” First, the lack of balance was apparent from the first moment of the game – the Ravens managed just 7 rushes in the first half. But additionally, the Ravens were never anywhere close to being out of this game. The rushing attack should have been featured more prominently. Period. It’s been said since our Week 1 victory against Kansas City.

Third Down Penalties: 25%.

I’m doing my best to not put blame on the refs. It truly wasn’t the refs fault (at least not most of the time). But despite being stout on defensive third downs throughout the game, the Ravens continued to give the Pats second chances. The second roughing call on Brady was extremely questionable. I heard it justified with a “if Brady doesn’t move his leg, he gets hit.” I didn’t know the NFL gave out penalties for almost roughing the quarterback.

Regardless of the calls, the Ravens need to be better about keeping their play in check. The defense looked confused and overmatched at various times and penalties are a symptom of that disorganization. Good teams don’t give second chances.

Meanwhile, a big kudos to John Harbaugh for letting the refs have it on some of the game’s more questionable calls.

Mark Clayton: 15%.

I’m trying to hold off on Clayton a bit here. If the Ravens perform better earlier in the game, if they play their game for three quarters, the team shouldn’t even be in that kind of position. But regardless, Clayton dropped the biggest pass of the game.  It was a great play call, a great route and a rocket pass to Clayton’s hands. Top receivers are paid to make those catches. We’re still waiting for you to prove yourself, Mark.

Chris Carr: 10%.

Carr has yet to be anything but a disappointment on special teams this season. We haven’t seen speed. We haven’t seen agility. We haven’t seen brilliant insight or smart moves. Until today, the most we had seen was the failure to make mistakes. Oops.

Carr’s fumble on the opening kick-off set up a long day for the Ravens. Instead of walking on the field, ready to establish the game’s tempo, Carr handed that opportunity to the Patriots. And it gave Belichick an early look at the Ravens D.

Dawan Landry: 10%.

Landry looked lost on the field for the second time this season. He was confused in Week 2 by the Chargers and looked similarly bothered by the Patriots schemes. He did a fine job in helping double Randy Moss and Wes Welker at various times throughout the game, but it didn’t make up for his mistakes.

Landry’s biggest mistakes cost the Ravens. Early in the game it was a pair of missed tackles on consecutive plays, leading to a Sammie Morris touchdown. The Ravens didn’t have any points to give away today.

Ravens-Browns: Predictions

Written by Dan McGrainNo Comments »

Three Predictions:

1. Two Ravens runners will top 100 yards. That’s pretty bold, right? I’m leaning towards Willis McGahee and Ray Rice, obviously. Not sure that there are even enough carries in one game to get them both over 100 yards, but it only really takes one big run (and the Browns specialize in making those available). If this doesn’t happen, I won’t be losing any sleep. Just a gut feeling.

2. It won’t be a shut-out. As much as Ravens fans and the team want it, the Browns are going to score. This Ravens defense is not there yet, especially not with Josh Cribbs helping out with field position. Not sure if the Browns will find the endzone or not (based on yesterday’s score prediction, I’m leaning towards not), but they will put something up on the scoreboard. But man, what would a shut out do for the Ravens points allowed average!

3. The Bengals will upend the Steelers. Ok, so this one isn’t Ravens, obviously. But there’s only so much to say about Ravens-Browns. Looking at the other division game this weekend, I’m loving the Bengals. Their defense is more legitimate than most think at the moment, and with the Steelers unable to run and vulnerable to the sack, there’s hope for Cincy. I also love Hines Ward saying that Pitt isn’t worried about their running game because the passing attack can handle it – for how long, Hines?

Three Questions:

1. Will the Ravens big play defense show up? The Ravens are facing a pair of back-up runners (one a rookie). Their also facing an inexperience quarterback leading a sloppy offense. The turnovers should be there for the taking – so will the Ravens take them? I expect a couple of turnovers, of course. But the bigger question is can the Ravens turn one into their signature scoring play? Fans are waiting – Ed Reed, Fabian Washington, Haloti Ngata, we’re looking at you.

2. Will the Ravens secondary improve? It better, given the opponent is far less advanced than San Diego was last week, but we all still have doubts. Defensive coordinator Greg Mattison said the defense will be returning to more standard secondary arrangements, hopefully keeping everyone on the same page and (we can only hope) in the right position. It would also help if he taught his smaller corners how to defend a pass, and not just run stride for stride with a receiver. But we can only hope for so much in a week.

3. Will the Browns implode? Their play on the field has already collapsed, obviously. That’s not really the question. But the whole team seems on the verge of absolute self-destruction. If the Ravens really pound the Browns, it might just be enough to send them over the edge and on the path to being one of the truly memorable bad teams in football history. Ray Lewis has a history of leaving bad memories for opponents, we can only hope he delivers here.



Copyright © 2007 One Winning Drive. All rights reserved.
FireStats icon Powered by FireStats