Ravens Fire OC Marc Trestman

The Baltimore Ravens this morning fired offensive coordinator Marc Trestman in the wake of yesterday's 16-10 loss to Washington. Trestman, notorious at times for gleefully abandoning the run, called 50 passes to just 18 runs even though Terrence West and Buck Allen were averaging more yards per play running than Joe Flacco was throwing. Marty Mornhinweg, who had been serving as quarterbacks coach, replaces him.

View Full Article


22 comments, Last at 14 Oct 2016, 5:56pm

6 Re: Ravens Fire OC Marc Trestman

Tough year for Bears coaches current and former. Gase probably gets a free year in Miami, but I don't imagine this is the start he had in mind.

19 Re: Ravens Fire OC Marc Trestman

Strike while the iron's hot? If he had stayed in Chicago another year or two, maybe the offense takes a step back (possibly not even Gase's fault) and he doesn't look like such a hot candidate anymore.

Also, I wonder how much money might play into it. I know assistant coaches earn a pretty good living, but a head coach's salary is several times more, isn't it? And we're not talking about guys who are financially set for life like some of the players are. I could imagine someone taking a less-than-ideal head coaching job in part because of the money. Yes, Gase could have expected another chance to come if he turned them down, but who knows if and when it would have?

22 Re: Ravens Fire OC Marc Trestman

I didn't realize coordinator salaries were even that high...if I'd had to guess I would have said more like the $250-500k range. Apparently most of the coordinator and even some of the coaches' salaries aren't publicly available, which surprises me in this day and age.

13 Re: Ravens Fire OC Marc Trestman

It should be mentioned that the Redskins came into the game with the 32nd-ranked run defense. After the game, commentators on Redskins Radio were saying things like "We don't know why the Ravens abandoned the run, but we sure are happy they did!"

14 Re: Ravens Fire OC Marc Trestman

On the opening drive, they scored a touchdown with a heavy dose of running (all three backs) and play action -- only one straight dropback -- so it's not like the run-based attack wasn't in their game plan or wasn't working for them. Even with their relative abandonment of the run, they still collectively went over 100 yards.

So yeah, abandoning the run makes no sense, especially after Steve Smith went out with an injury.

16 Re: Ravens Fire OC Marc Trestman

Let's just pause for thought here. There must be some reason for the lack of run plays, surely? Perhaps after being gashed on the first drive Washington began loading up against the run? Perhaps the clock/scoreline put them in situations that simply demanded passing? And it's not like a rookie QB was being asked to do the passing - Flacco is one of the highest paid QBs in the league.

I'm not trying to defend Trestman here; whatever the scenario the offence faced, clearly what they were doing was not working. But this site that has done a lot of work towards debunking myths about the value of running the ball. We know that the average pass play in the NFL has significantly higher payoff than the average run play. So we should be absolutely sure before we criticise a coach for 'abandoning' the run.

17 Re: Ravens Fire OC Marc Trestman

I watched that game from start to finish, and it sure didn't look like that to me. Even after taking out the 35-yarder on the opening drive, and even with Kenneth Dixon having a debut to forget (3 carries for -1 yard), the Ravens backs averaged 4.5YPC on 17 carries. Their YPC was higher than their YPA even excluding their biggest run play, but their backs only had 18 runs while their quarterback had 49 dropbacks (including three sacks, but not his six-yard scramble). With their best receiver on the sidelines with an ankle injury, it made very little sense to me that they passed so often.

Here's the justification for my claim of abandoning the run: Baltimore ran five times on the opening drive, which finished with a touchdown on a play action pass. This was the highest margin in the game, in Baltimore's favour, 7-0 after that first drive. They went up 10-6 about 30 seconds into the second quarter, at which point they had 74 yards on 11 carries and had scored on two of their three drives. They were averaging almost 7 yards per carry, but only ran seven more times the entire game, despite still averaging 5.6YPC, and didn't score again. The next highest score margin was 16-10 to Washington at the end of the third quarter. Score and time remaining wasn't really a factor until late in the fourth, but they ended the game with twenty-two consecutive dropbacks.