A lot of the noise around the Ravens’ 1-1 start has centered on the fourth-quarter collapse against the Saints, with fans pointing fingers everywhere from the defense to Declan Doyle. But the cleaner explanation is sitting right in front of them: penalties.
Not just penalties in the abstract, either. Baltimore has been bleeding drives on flags that wipe out real production, and that’s where the damage has piled up fast.
Through two weeks, the Ravens have lost -11.0 EPA on penalties themselves, which ranks second-worst in the NFL behind only the Carolina Panthers. Even that number doesn’t tell the whole story, because it only accounts for the flag - not the play the flag erased.
When you add in the value of the plays that got called back, the picture gets uglier. Baltimore’s nullified plays have totaled +9.2 EPA, the most in the league by a wide margin.
These aren’t dead-end snaps getting wiped away. They’re productive moments disappearing from the ledger: a Ja’Kobi Lane touchdown, a 19-yard catch by Rashod Bateman, an 11-yard grab by Mark Andrews, a Lamar Jackson first-down scramble.
Put it all together and the Ravens’ total penalty cost lands at -20.1 EPA, just behind Carolina’s -20.2.
There’s another layer, too. Most offenses claw back some of what they lose when opposing defenses get flagged.
Carolina has recovered +3.1 EPA that way, while Minnesota and Buffalo have each gained more than +19. Baltimore, though, has gotten nothing back.
The Ravens are the only offense in the league without a single accepted defensive penalty.
That leaves Baltimore with a net offensive penalty EPA of -20.1, the worst mark in the NFL. No offense has lost more, and no offense has gotten less in return.
Some of the calls in the Saints game only made the whole thing look worse, especially late. That’s when the numbers start to feel less like bad luck and more like a pattern.
A few of Baltimore’s offensive flags were clearly legitimate, but others were highly questionable. Chris Moore’s holding penalty last week and John Simpson’s “chop block” in Week 1 both fall into that category.
The opposing side hasn’t been hit with any of those 50/50 breaks, especially not on plays that produced big gains. And while penalties can sometimes be a byproduct of explosive offense, Baltimore has also created explosive plays without drawing flags, which makes that explanation feel thin.
The biggest swing came against New Orleans, particularly in the third quarter, when the Ravens gave away roughly 5 expected points. They had driven to the Saints’ 28-yard line, then got pushed backward by penalties and settled for a field goal.
Given how easily the ball was moving, a touchdown looked likely. With the game ending in a seven-point loss, those flags loom large.
Without them, Baltimore would have at least had a real shot to be in position for a field goal at the end to win or tie.
None of that changes the final score, of course. But it does underline the problem: the Ravens have to clean up the penalty mess. Some of it is on technique, but some of it also looks like the kind of luck that should eventually even out.
Two weeks is a small sample, yet Baltimore is already on pace to threaten the NFL record for the most net expected points lost to offensive penalties. At this rate, they’d be tracking toward quadrupling that mark.
So yes, the Ravens need to get sharper. They also probably need the breaks to start going their way.
In Other News...
Ravens Just Got A Pregame Edge Dallas Cant Ignore
The Cowboys are heading into their matchup with Baltimore already shorthanded on defense, and the injury list is hitting hard in the middle of the field and on the back end. Linebacker DeMarvion Overshown, cornerback Cobie Durant, and safeties Malik Hooker and P.J. Locke have all been ruled out, leaving Dallas to patch together its coverage and run support against a Ravens offense that will be looking to test every weakness.
Rookie linebacker Jaishawn Barham and cornerback Shavon Revel are expected to step into larger roles, which gives Baltimore a chance to go after some inexperienced snaps early and often. For a Ravens team that can make life difficult with pace, physicality and layered pressure, the absences on Dallas defense create a much different pregame feel than the Cowboys probably wanted entering this one. [Read more 🡒]
Ravens-Cowboys Brazil Trip Suddenly Comes With A Serious Field Concern
The Ravens Week 3 trip to face the Cowboys at Maracan Stadium in Rio de Janeiro was supposed to be one of the more intriguing items on the early-season calendar, but the conversation has shifted to the field itself. Heavy rainfall and a packed soccer schedule have left noticeable bumps and wear on the grass, creating a concern that matters to both sides long before kickoff in Brazil.
The NFL says it is confident the surface can be managed, and maintenance work is already underway to help reinforce it ahead of the game. Still, for Baltimore, the bigger picture is easy to see: a showcase matchup in a famous venue is only as good as the ground beneath it, and the coming days will determine whether this one feels like a marquee event or a slog. [Read more 🡒]
Giants Quarterback Search Takes A Turn Ravens Fans Should Notice
The Giants quarterback search has picked up another layer of intrigue after a season-ending injury forced them to sort through both the short term and the bigger picture. Jameis Winston is set to start for now, but New York is still evaluating depth behind him, and the coaching staff has kept the door open to just about every possibility as it looks for stability at the position.
One name that surfaced in the discussion was Joe Milton, though Josina Anderson reported that he remains on the Cowboys practice squad and that the Giants have not made any formal move to bring him in. For Ravens fans, it is the kind of NFC roster churn worth tracking because any quarterback shuffle in New York can ripple through the league conversation, especially with a divisional-style urgency attached to teams trying to protect themselves from being left thin behind center. [Read more 🡒]