Jump to content
Washington Football Team Logo
Extremeskins

WP: Perry Riley: "I feel terrible for the situation"


TK

Recommended Posts

maybe im alone here but i didnt think it was a block in the back at all. it happened right underneath me at the stadium, i saw the replay on a 100 ft TV screen, he hit the dude in the shoulder. this was a bogus call.

the kid is a potential future LB for this team, one questionable block in the back is taking a lot of you over the edge.

what some of you should be over the edge about is why are vets like moss and cooley dropping easy passes, why our oline was juggled again today, why carlos rogers thought he was a missile today, and why rocky mcintosh decided tackling is overrated. there were a lot of issues today with this team, a rookie getting flagged on a crappy call is not one of them.

From my angle at the game, it didn't look like one at all. I'm positive he hit him on the shoulder.

Link to comment
Share on other sites

There's mixed reports going around now.. First it was he had 2 block in the back pens today, then it was just one cause the ref got the # wrong, and finally I saw where someone said he had 3 special teams penalties called on him today.. If in fact it was just that one, then I'd just hope he learns from it and go about business as usual.. If he actually had 2 or 3, then I'd be fine if they cut him.. Based soley on the fact that he's not very bright and didnt learn from the 1st (or 2nd).. Also we have very little accountability for all these dumb mistakes guys are making.. Nothing will get their attention like someone loosing their job.. It's week 12 and we still have multiple false starts and blocks in the back every week.. Somehow, someway, the coached need to clean this up..

Link to comment
Share on other sites

I only saw the replay once, but I believe that that call would not be made, in the majority of runbacks. It looked like he hit the back of the shoulder, but the guy was moving laterally toward Riley. What he should have known was that anything close would probably be called on THIS team. So don't take a chance.

Link to comment
Share on other sites

-It was a legitimate penalty.

-It is an extremely common penalty, and one that rarely draws heavy scrutiny.

-It happened at the worst possible time, thanks almost exclusively to pure, dumb, terrible luck on the part of a promising rookie.

If you think the unfortunate final outcome of this game was more the fault of Perry Riley than of the o-line's incompetent run-blocking, or Santana Moss's two crushing drops, or Donovan McNabb's baffling short-yardage inaccuracy, or Jim Haslett's frustrating inability to contain Toby Gerhart... then you are simple.

Link to comment
Share on other sites

Those were two VERY visible fouls with no call. Very frustrating. As was the crappy spiking delay of game call on Armstrong. The ****ing ref could very easily have left his flag in his pocket on that one.

yea, i was confused about that spiking the ball penalty. what was that about and when did anthony armstrong ever spike it?

Link to comment
Share on other sites

Perry Riley should feel bad but nothing he shouldn't get over and try his best to improve from. Plain and simple the call was just another one in a game of horrible officiating, you dont call back a game changing play on a team trying to battle back in a game and keep their post season hopes alive if it doesn't CLEARLY EFFECT the play. This was a bone head block and a borderline block in the back but nothing that should have been called given the situation. Vikings got lucky but its hard to complain when we have been on the positive side of the calls for the most part all season. The NFL however does need to be careful about taking the game away from the players, whatever end of the call you are on, less stringent refereeing definitely makes for a more exciting product.

Link to comment
Share on other sites

We shot ourselves in the foot the whole game. Yes, Riley's block in the back on Brandon's TD was costly, but we can't totally fault him. Whose to say that Minnesota would not have still won the game anyway? For this loss, you can put blame on the dismal running game, the poor protection of McNabb from the offensive line, and the defense not being able to stop the run. The whole team played a part in this 17-13 defeat from the Vikings.

Link to comment
Share on other sites

he better learn quick... and im saying both special teams and linebacker! Cause i can sense some skin fans wanting his head.. me personally. you live you learn! you need to focus on every play and thats where our team lacks... this game is mental as well and weve lacked that since the 07 debacle!

Link to comment
Share on other sites

Bottom line is that the Skins would win more games if they could but they can't so they don't.

The Redskins would be doing themselves a favor by bringing in talent evaluators to start searching now for the hidden gems sure to be among next years undrafted players. They do still have their top picks that could produce a couple of impact players so that's a plus but it won't be enough. They need to add more than a couple of horses, they need a small herd.

Link to comment
Share on other sites

he better learn quick... and im saying both special teams and linebacker! Cause i can sense some skin fans wanting his head.. !

Well, that would be a personal problem then, if him making an illegal block in the back, would cause someone to react violently towards him. This isn't life or death. He probably feels worse about it then any of us do. No one is perfect.

And I honestly don't see him getting cut anyway, he was a fourth round pick, and he provides depth at linebacker. It's not gonna happen.

Link to comment
Share on other sites

It just sucked because I was waiting for the flag, and then they said no flags, so I was really enjoying the John Wall Dance.

I think that is what makes it hurt that much more. The fact that it was stated that there were no flags and no little flag icon popped on the screen so we did have that 5 second moment of celebration thinking that it was going to count. Hell I remember at first when they said there was a flag but I did not know where it was, I thought it was maybe on the Vikings for something after the play.

The other thing that made it hurt more is the fact that it was such an unnecessary penalty. Banks had already gotten clear of that guy and was on his way up the field when Riley decided to throw that block. I just don't understand why he threw the block unless he simply did not see Banks to his right heading up field.

Link to comment
Share on other sites

One play didn't lose this game. You expect your offense to do the scoring. Special teams is supposed to put you in position. The D has looked better the past couple of weeks with lineman actually playing on the line. This was a loss due to the breakdown of simple football rules, run and catch the ball. We have no running game. We also have an inconsistent core of receivers. The few games we have won were because we could run the ball. The Colts are losing because they can't run. One dimensional teams will be at home watching the playoffs.

Link to comment
Share on other sites

Can anyone tell me how much time was left in the game, when the Return was called back?

Thanks, in advance! :) Just disputing a few things with a Vikings fan.. He also believes that Fletcher shouldve been called on a PI, on the deep pass to Shianco.. I don't remember that even being close to a PI, however.. The other complaint, of his, was us calling a timeout and then saying "nevermind".. hmm.. I must've been getting a beer, during that one. ha.

Sucks that we lost.. :( My family was hyped up, slapping fives & celebrating, when Banks broke that return. Then came the flag.. :doh: What a buzzkill.. I thought this happened towards the end of the game. However, my Vikings fan friend tells me there was still 10 minutes left in the game?

I believe the London Fletcher play wasn't pass interference b/c the ball hit Fletcher's helmet. It would've been interference if the ball hadn't hit his helmet b/c London never turned to play the ball...

Link to comment
Share on other sites

I could feel sympathy if it wasn't for the fact this was the second time in the same darn game he committed such a dumbass penalty. This one ultimately costing us a potential game winning lead.

Sorry Perry. For a pro, veteran or rookie, that's total inexcusable stupidity.

Hail.

Agreed

Link to comment
Share on other sites

maybe im alone here but i didnt think it was a block in the back at all. it happened right underneath me at the stadium, i saw the replay on a 100 ft TV screen, he hit the dude in the shoulder. this was a bogus call.
From my angle at the game, it didn't look like one at all. I'm positive he hit him on the shoulder.

I was surprised at the number of people at FedEx Field who thought the same thing after seeing the replay. To me it was obvious that it was a block in the back from the replay they showed at the stadium. Sure, Riley hit the guy in the shoulder but that's completely irrelevant in and of itself. What matters is that he didn't hit the guy's shoulder from the front or the side, he put his pads into the back of the defender's shoulder blade. That one should be called every single time.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...