lamafist
Rotational Player and Threatening Starter's Job
- Joined
- Jul 26, 2008
- Messages
- 1,197
- Reaction score
- 124
Registered Members experience this forum ad and noise-free.
CLICK HERE to Register for a free account and login for a smoother ad-free experience. It's easy, and only takes a few moments.I've got no problem with the play call. I like the idea of trying to take advantage of a team when they might still be pouting from the previous play. The problem I have is that once Brady sees the S back there, he's basically throwing it into double coverage. If its single coverage, let it rip. But double coverage to a WR who caught all of one pass all season is just a terrible decision.
He should have checked down to another receiver as soon as he saw that their safety didn't bite. That one is completely on Brady.
Personally, i would have run the ball, but i too, didnt mind the call. I put that int on Brady.
Nothing wrong with taking a shot if its there. It was so obviously covered that I can't believe Brady threw it.
That came across on tv, the ravens moving inexorably down the filed was like a slow tortuous death, when spikes got the pick it was such a relief followed by WTF we're going to start having our finger nails ripped out again.no...I'll take the running play with a back who's averaging over 4.5 YPC and try to up that percentage by getting first downs as the clock winds down....effectively running out the clock...which I have seen the Patriots do numerous times in the past years...in fact, being AT the game, there was a pervasive feeling of relief when the Pats got that turnover, and a feeling that the game was finally in hand...only to be wrenched right out of our grasp by that ill conceived play...
Are you guys kidding?
The play resulted in two Ravens' defenders being devoted to Matthew Slater. That's actually great... except the part where Brady still threw it to him, rather than finding Welker or Gronk and taking advantage of the room cleared out underneath Slater's deep post.
It's not that the call was bad; Brady shouldn't have thrown it once he saw the coverage. He had several throws like that during the game, including the 2 ints which were called back because they were across the line before the snap. It's like he got so frustrated he just threw it up several times.
Brady made a bad decision to throw into double coverage.
Which points to us needing a real threat at WR...we are weak on the outsides and it shows against Very Good Defenses.
Well, the great majority seems to think that it was a bad play, so I guess I'm way in the dissent.
I thought it was terrible execution, and once he saw double coverage, he shouldn't have thrown it. But I don't necessarily disagree with taking a shot there or with throwing the ball if Brady thought he had it.
Everyone saying "we were controlling the ball and just needed a couple of first downs," think about it. We had that very situation a few minutes later with a chance to win the game and tried some dinking and dunking and didn't get the first down, almost leading to a loss. There's no one perfect way to play it. I'm guessing the coaches were reviewing photos and watching the plays and thought they saw something and took the shot. Sometimes it works. Sometimes the other guys make a play.