Cam Cameron Can’t Take All Blame For Ravens Issues
Be honest, you kind of saw this coming. Didn’t you?
The Baltimore Ravens beating the Dallas Cowboys in week six on a game ending missed field should have been enough to have fans in Charm City sweating bullets about their team’s matchup with the red hot Texans. Even if they did get pounded by Aaron Rodgers and the Packers the week before.
The Ravens have played down to their opponents and have been squeaking out victories with in an underwhelming fashion for most of the season. While the defense has looked old and flat, the Ravens offensive schemes and play calling can easily be questioned this season as well.
On Sunday, the Ravens finally snapped their 132 minute and 56 second road touchdown drought when Tandon Doss reached the end zone in the in the third quarter. The Texans had eight more first downs, 174 more yards and 26 more points than the Ravens in the first half alone.
And things only got worse from there.
Whenever games go awry, sports fans often like to point the finger and find some one person to blame. For the Ravens, this guy is typically offensive coordinator Cam Cameron. And I’ll admit, he’s rightfully generated a lot of this angst.
But it wasn’t Cam Cameron who allowed Joe Flacco to be sacked four times — including once in the endzone — for a loss of 26 yards. Cam Cameron didn’t bat down Joe Flacco’s passes for sixty minutes or take a pick-six to the house. And Cam Cameron didn’t let the Ravens defense give up 420 total yards.
Calling nine running plays for Ray Rice, who averaged 4.7 yards per carry, certainly didn’t help though.
The Ravens aren’t going to fire Cam Cameron. At least not right now. So getting upset with him for a loss that the Ravens as a team should accept is really just a waste of your time.
You can point the finger at all 53 guys on the roster for this one. One guy isn’t responsible for a 30 point loss.