NFL.com - Mike Periera On Rule Changes

[Hoofbite]

http://www.nfl.com/videos?videoId=09000d5d807a506c

Interesting stuff. Talks about the forceout rule.

One thing that struck me was that he said there were only 16 plays that involved forceouts and they were wrong on about 6 of them.

To me, thats not all that bad. And even if it was, I still didn't see the need for getting rid of the rule. Instead of having the refs work on correcting their calling and recognizing when to make certain calls to improve the quality of officiating, they just ditch the rule.

He goes on to talk about the timeout problem on FGs. Said they didn't address it because it died out towards the end of the season after Shanahan called a timeout and had it bite him in the ***. I really don't see how making this rule would be so tough. You just don't allow a timeout after the kicking team is set. Lets the defense ice him all they want but doesn't allow for the Bush league "prove it" aspect.

 

[AdamJT13]

One thing that struck me was that he said there were only 16 plays that involved forceouts and they were wrong on about 6 of them.

You can bet there will be many more this season. In the past, when there was a high pass near the sideline or end line, defensive backs had to play the ball. Now, if they can't intercept it, they can just knock the receiver out of bounds before he comes down.

 

[L-O-Jete]

You can bet there will be many more this season. In the past, when there was a high pass near the sideline or end line, defensive backs had to play the ball. Now, if they can't intercept it, they can just knock the receiver out of bounds before he comes down.

And then they'll flag the defender for hitting the WR while vulnerable... Those are 2 rules I consider "crappy"

 

[Paniolo22]

http://www.nfl.com/videos?videoId=09000d5d807a506c

Interesting stuff. Talks about the forceout rule.

One thing that struck me was that he said there were only 16 plays that involved forceouts and they were wrong on about 6 of them.

To me, thats not all that bad. And even if it was, I still didn't see the need for getting rid of the rule. Instead of having the refs work on correcting their calling and recognizing when to make certain calls to improve the quality of officiating, they just ditch the rule.

He goes on to talk about the timeout problem on FGs. Said they didn't address it because it died out towards the end of the season after Shanahan called a timeout and had it bite him in the ***. I really don't see how making this rule would be so tough. You just don't allow a timeout after the kicking team is set. Lets the defense ice him all they want but doesn't allow for the Bush league "prove it" aspect.

16 seems low. I bet that doesn't include times when a forceout should have been called, but wasn't. (Owens at least twice)

 

[Shady12]

Besides the fact that it's an illogical and insane rule in the first place to have on the books, the example of only 16 instances is another good reason to drop it. Doesn't happen much so won't be missed, and is called wrong a lot anyway.

Why shouldn't a db be able to do his job, which is keeping a receiver from making a reception, by pushing him out of bounds if he's in the air with the ball? That's football.

I've never heard of anyone complain about it in college or high school ball. It doesn't even happen that much, obviously.

 

[Kangaroo]

Besides the fact that it's an illogical and insane rule in the first place to have on the books, the example of only 16 instances is another good reason to drop it. Doesn't happen much so won't be missed, and is called wrong a lot anyway.

Why shouldn't a db be able to do his job, which is keeping a receiver from making a reception, by pushing him out of bounds if he's in the air with the ball? That's football.

I've never heard of anyone complain about it in college or high school ball. It doesn't even happen that much, obviously.

You also only need one foot down in college

 

[Hoofbite]

Besides the fact that it's an illogical and insane rule in the first place to have on the books, the example of only 16 instances is another good reason to drop it. Doesn't happen much so won't be missed, and is called wrong a lot anyway.

Why shouldn't a db be able to do his job, which is keeping a receiver from making a reception, by pushing him out of bounds if he's in the air with the ball? That's football.

I've never heard of anyone complain about it in college or high school ball. It doesn't even happen that much, obviously.

heres your answer

16 seems low. I bet that doesn't include times when a forceout should have been called, but wasn't. (Owens at least twice)

They aren't counting the ones they should have called forceout which would probably inflate that number just a little bit.

 

[Paniolo22]

heres your answer



They aren't counting the ones they should have called forceout which would probably inflate that number just a little bit.

There is too much judgement needed on a rule that would seem obvious, especially if it were reviewable.