PI in end zone

[ClkWrkOrange]

my man. wow, your right. All those referee's are wrong. I wonder why they call it a penalty? if its legal to clear a defender out to get another Wr to a spot? I know why because its a penalty that Ive seen called hundred times in my coaching career. Its not legal. What book did you get that from? when its straight up contact cause by the D its not a penalty? You can only block a defender before the ball is thrown when the ball is thrown behind the line of scrimmage. Thats the rule. Thats why screens, bubbles are often considered run plays even though there's a pass being thrown. The defender couldnt get there because he was being blocked. You have to distinguish a pass play or a run play. Its football 101. If they are blocking then its a run play if they are trying to run a route its a pass play. Its been that way since the beginning of football. Its only right that the defense has a chance to determine pass or run so they can defend the play. And it has alot to do with 88 getting to the flats. If # 20 jammed the WR backwards and knocked him into 88 it would have re routed him and disrupted the timing and the placement of the ball.

You're wasting your time with this guy.He.Will.Never.Get.It.

 

[upperdeck]

You're wasting your time with this guy.He.Will.Never.Get.It.

you are funny..

Just because it was called on the field that makes it correct..

You forget how many coaches/players/announcers/fans actually know the rules.. its pretty close to zero.

Like how we have had discussions on 5 yd chuck rules in college/HS or touching the ball in the endzone on punts or WR going out of bounds and catching a ball. and how many times have we seen refs not start the clock properly in games this year. they screw up too.

oh and here are two comments from one of the NCAA handbooks for officials

"For the "pick" to be a foul it must be obvious that the offensive player "initiated" the contact" .. Oh wait I think thats what i said, that cant be right.

and

"This is the equivalent to the "charge" in basketball. "

So if you throw the flag on #20 then i could live with the call since even with the defender created the contact you could argue he also had established position, the WR can not run threw the player but he is also allowed to maintain his position just like basketball, had he run and turn its not called most likely.

but the call is on #7 who did he was supposed to do, jab step and cut away from the DB.. in bball that would be a foul on the D and not a charge so it cant be a pick call..

 

[money3189]

you are funny..

Just because it was called on the field that makes it correct..

You forget how many coaches/players/announcers/fans actually know the rules.. its pretty close to zero.

Like how we have had discussions on 5 yd chuck rules in college/HS or touching the ball in the endzone on punts or WR going out of bounds and catching a ball. and how many times have we seen refs not start the clock properly in games this year. they screw up too.

oh and here are two comments from one of the NCAA handbooks for officials

"For the "pick" to be a foul it must be obvious that the offensive player "initiated" the contact" .. Oh wait I think thats what i said, that cant be right.

and

"This is the equivalent to the "charge" in basketball. "

So if you throw the flag on #20 then i could live with the call since even with the defender created the contact you could argue he also had established position, the WR can not run threw the player but he is also allowed to maintain his position just like basketball, had he run and turn its not called most likely.

but the call is on #7 who did he was supposed to do, jab step and cut away from the DB.. in bball that would be a foul on the D and not a charge so it cant be a pick call..

man Im convinced now. I am now sold that is wasnt a pick. I changed my view when you described it in basketball terms. Makes alot of sense. lol. Besides, ND Wr's didnt deserve to get that call anyways. They didnt do a good job of selling it. They did the opposite of that. All he had to do was run the slant. It wouldnt have looked so obvious then. They would have scored without the pick because of coverage was blown.

 

[upperdeck]

man Im convinced now. I am now sold that is wasnt a pick. I changed my view when you described it in basketball terms. Makes alot of sense. lol. Besides, ND Wr's didnt deserve to get that call anyways. They didnt do a good job of selling it. They did the opposite of that. All he had to do was run the slant. It wouldnt have looked so obvious then. They would have scored without the pick because of coverage was blown.

i didnt describe it that way the book did. but i agree FSu defended it poorly and ND ran it poorly, but one team got rewarded and the one guy who ran it correctly got called for it..

 

[ClkWrkOrange]

you are funny..

Just because it was called on the field that makes it correct..

You forget how many coaches/players/announcers/fans actually know the rules.. its pretty close to zero.

Like how we have had discussions on 5 yd chuck rules in college/HS or touching the ball in the endzone on punts or WR going out of bounds and catching a ball. and how many times have we seen refs not start the clock properly in games this year. they screw up too.

oh and here are two comments from one of the NCAA handbooks for officials

"For the "pick" to be a foul it must be obvious that the offensive player "initiated" the contact" .. Oh wait I think thats what i said, that cant be right.

and

"This is the equivalent to the "charge" in basketball. "

So if you throw the flag on #20 then i could live with the call since even with the defender created the contact you could argue he also had established position, the WR can not run threw the player but he is also allowed to maintain his position just like basketball, had he run and turn its not called most likely.

but the call is on #7 who did he was supposed to do, jab step and cut away from the DB.. in bball that would be a foul on the D and not a charge so it cant be a pick call..

You're going to live with it regardless.Or not.Either way I'm done with this.

 

[Tobias Funke]

Pretty simple way to look at it.

Nd fan thinks it was a bad call

NonND fans know it was the right call.

 

[Jake]

Unquestionably a pick play.

 

[TerryD]

Pretty simple way to look at it.

Nd fan thinks it was a bad call

NonND fans know it was the right call.

Or the other way around?

Good luck to Syracuse the rest of the season.

 

[djcon57]

Or the other way around?

Good luck to Syracuse the rest of the season.

Nope, to non ND or FSU fans, we have no bias

I'm not a FSU or a ND fan.
It was a pick play.

 

[longtimefan]

So if you throw the flag on #20 then i could live with the call since even with the defender created the contact you could argue he also had established position, the WR can not run threw the player but he is also allowed to maintain his position just like basketball, had he run and turn its not called most likely.

but the call is on #7 who did he was supposed to do, jab step and cut away from the DB.. in bball that would be a foul on the D and not a charge so it cant be a pick call..

Is it possible that the referee announced the wrong number? After all, we all agree that officials make mistakes.