Calling a penalty after a review

[chknwing]

I don't think I have ever seen a review that resulted in a penalty being called.  And it happened twice last night.  you sure as hell cant challenge a penalty and have it reversed.  Very odd.

[the butch]

Bet that Ron will send in a letter to New York.

[SmokinwithWilly]

The tipped pass/interference call made sense, even though it was a weird play. The rule should be tipped ball or contact with the QB's arm. But that rule won't be changed unless it's Tom Brady. 

[CoastalCat]

I don't think I have ever seen a review that resulted in a penalty being called.  And it happened twice last night.  you sure as hell cant challenge a penalty and have it reversed.  Very odd.

It was weird. I guess the fact that they threw the flag, then picked it up, meant that a reversal of the no-call was a call. I suppose it did get to the right place. It was pass interference.

[chknwing]

It was weird. I guess the fact that they threw the flag, then picked it up, meant that a reversal of the no-call was a call. I suppose it did get to the right place. It was pass interference.

I can agree with that but the sideline catch that resulted in a penalty that was never called originally?

[mc52beast]

NFL should provide rules books for every household that has a fan living there...

[CoastalCat]

I can agree with that but the sideline catch that resulted in a penalty that was never called originally?

Valid. 

[shreddingdefense]

How long does one have to be in bounds in order to make a play on the ball, if they accidently stepped out of bounds prior?

[Jase]

So last night, We had:

a butt-interception,

the ground causing an interception,

a pass interference after review that occured a split second before the ball hit the ground 7 yards away,

an illegal touch penalty that came after review,

and two interceptions that hit the ground that should've been reviewed but weren't

 

Let's just call this a weird fuging game

[osd22]

The commentator said it best. When a receiver steps out, comes back in then it always should be an incomplete pass/catch. The current rule seems stupid.

[tiger7_88]

It was weird. I guess the fact that they threw the flag, then picked it up, meant that a reversal of the no-call was a call. I suppose it did get to the right place. It was pass interference.

It was NOT pass interference lol.

For their to be PI, the pass has to be catchable... that ball landed 10 ft away from the receiver.

[chknwing]

It was NOT pass interference lol.

For their to be PI, the pass has to be catchable... that ball landed 10 ft away from the receiver.

well luke did hit him and make him fly 10 ft

[osd22]

It was NOT pass interference lol.

For their to be PI, the pass has to be catchable... that ball landed 10 ft away from the receiver.

But if Luke hadn`t smacked the guy to the ground he would have made a five yard diving catch. LOL ;)

[CoastalCat]

So last night, We had:

a butt-interception,

the ground causing an interception,

a pass interference after review that occured a split second before the ball hit the ground 7 yards away,

an illegal touch penalty that came after review,

and two interceptions that hit the ground that should've been reviewed but weren't

 

Let's just call this a weird fuging game

Having trouble arguing with the PI call. In stride, I think the receiver would have gotten there if he hadn't been pushed. Anyone have a gif?

EDIT: To clarify, I was talking about the one down the right sideline, not the one that was deep in Eagles territory.