Redskins Reality Checks: Insult added to injury in Week 9 loss to Falcons
By Tim Payne
The Redskins failed a test against another high-powered offense as the Falcons ran (and passed) all over the Redskins’ defense.
This game set up as an opportunity for the Redskins to prove their defense hadn’t just been fortunate to go up against bad offensive teams in recent weeks, but was actually much improved from last year. It was an opportunity to prove the debacle against the Saints in New Orleans was a fluke. It was an opportunity to make some strides offensively against a terrible defensive unit.
It was all of those things…and then kickoff happened.
On the second snap of the game, Shawn Lauvao tweaked his leg while committing a holding penalty that negated a first down catch by Jordan Reed. On the ensuing snap, he injured his knee while getting bull-rushed to give up a sack. And the game went downhill from there for the Redskins. Let’s take a look back at what we thought before this game and look at where the Redskins stand now.
1. Reality Is, Matt Ryan is not Eli Manning.
I didn’t expect the Redskins to make Matt Ryan look bad in this game…but I also didn’t expect him to make them look bad. I didn’t expect Ryan to be sacked seven times this week, nor did I expect him to throw two picks. I predicted he would be harassed by the Redskins’ defensive line. Ryan would get his yards but would look about as uncomfortable as he has all season. I also thought the defense would hold up in the red zone, limiting the Falcons to field goals. I projected that Ryan would pass for 342 yards, going 37-for-52, but only notch one TD.
Reality Check: The Falcons used outside running to set up play action passes, and Ryan was pretty comfortable all day. A few glimpses of pressure set up a couple stops, but otherwise, Ryan led an insanely efficient attack against Washington. His final line: 26-for-38 for 350 yards, four TDs, and one INT. In addition, the Falcons converted their first eight (EIGHT!!!!!) 3rd downs on a day when the defense simply had no answers.