Noah Brown catch Interference?

Melonfeud · Jul 1, 2019

davidyee said:
Defender had no chance of picking off the ball. He was so intent on catching up to the play where he was clearly beaten. Just look at his stride and his feet position from 10 yard line to the 5 yard line. He was running full steam to catch up.

He was probably thinking my position coach is going to "ream me a new one" once I get back to the sideline. Or I am going to be the highlight of this week's film study, and it won't be a game ball they are handing to me.

A'La BARRY SWITZER's stylish profundities: eating his *** out,,,

KJJ · Jul 1, 2019

davidyee said:
Defender had no chance of picking off the ball. He was so intent on catching up to the play where he was clearly beaten. Just look at his stride and his feet position from 10 yard line to the 5 yard line. He was running full steam to catch up.

The defender caught up because the ball was thrown behind Brown which forced him to have to slow up and turn back toward the ball. This gave the defender a chance to make a play. Had the ball been thrown out in front of Brown where it should have been thrown he would’ve been going away from the defender and scored a TD. Brown having to turn back after the ball contributed to the contact between him and the defender.

TheMarathonContinues · Jul 1, 2019

KJJ said:
They were both playing the ball and because the pass was thrown behind Brown it forced him to turn back toward the ball initiating the contact with the defender. If we had the audio I’m sure the game announcers and the official the network used would have given the same reasons I did for the no call. Fans should be more troubled by the inaccurate throw by Dak than the no call. Had he thrown the ball accurately it would’ve been a touchdown.

Doesn’t matter where the ball was placed unless it’s uncatchable.

KJJ · Jul 1, 2019

rocyaice said:
Doesn’t matter where the ball was placed unless it’s uncatchable.

It mattered on that play because the ball being thrown behind Brown forced him to have to slow up and turn back which contributed to the contact between him and the defender. To get a PI call on a poor throw it has to be a flagrant foul and that wasn’t. Had the ball been thrown out in front of Brown he would’ve been running away from the defender scoring a touchdown, not having to turn back toward the defender to try and catch the ball. I’m not going to spend all day on this our opinions differ and we’ll just leave it at that. One of the reasons PI calls will now be reviewable is because not everyone sees them the same way. It’s a judgment call.

xwalker · Jul 1, 2019

KJJ said:
The ball was thrown slightly behind Brown forcing him to go back toward the ball to try and make the catch. This contributed to the DB hitting him a tad early. The DB did appear to be playing the ball. It’s one of those that could’ve been called. The fact that Brown had to turn back toward the ball and the DB to try and make the catch is probably why they didn’t call a PI. With Brown turning back toward the ball It appeared he may have initiated the contact.

Defenders can't run over receivers even if they have their head turned.

The ball is several feet away when the defender hits the receiver.

Brown slowed up but he was not moving back towards the QB or defender.

If the defender is running stride for stride with the WR and there are only a few inches of space when the WR slows up, then it could be debatable if contact happened just as the ball arrived.

In this play the defender has plenty of time and space to avoid contact and the contact occurs well before the ball arrives.

The quality of the throw is not relevant unless it is un-catchable.

KJJ · Jul 1, 2019

Brown had the defender beat.

xwalker said:
Defenders can't run over receivers even if they have their head turned.

The ball is several feet away when the defender hits the receiver.

Brown slowed up but he was not moving back towards the QB or defender.

If the defender is running stride for stride with the WR and there are only a few inches of space when the WR slows up, then it could be debatable if contact happened just as the ball arrived.

In this play the defender has plenty of time and space to avoid contact and the contact occurs well before the ball arrives.

The quality of the throw is not relevant unless it is un-catchable.

Brown was clearly moving toward the defender to try and catch the ball. This helped close the gap between the two of them creating the contact. Impossible to avoid contact with the defender and receiver coming together to try and make a play on the ball. The quality of the throw is relevant because it gave the defender an opportunity to close the gap and make a play on the ball. The defender was beaten and wouldn’t of had a chance to make a play on the ball had it been thrown accurately.

OmerV · Jul 1, 2019

xwalker said:
Notice the location of the ball in the air when the LB hits Brown.

Definitely a missed call, but it's a bit harder to see full speed in a game, and the LB did at the last second turn his head toward the ball. That act seems to fool a lot of refs, even if it really comes too late after the interference has occurred.

MCMetal69 · Jul 1, 2019

erod said:
That is not interference. The defender has the right to be where he is, which is where Dak threw the ball.

He has a right to HIS POSITION , not to run through the receiver which he did......................

xwalker · Jul 1, 2019

Super Slow-Mo with ball highlighted.

@408Cowboy
@blueblood70
@Bullflop
@CalPolyTechnique
@Cannibal_Cowboy
@CCBoy
@charron
@CouchCoach
@DakPresgoat
@davidyee
@erod
@eromeopolk
@Fizziksman
@gimmesix
@glimmerman
@InTheZone
@jazzcat22
@JoeKing
@Kevinicus
@KJJ
@lkelly
@MCMetal69
@Melonfeud
@OmerV
@PAPPYDOG
@Ranching
@Red Dragon
@rocyaice
@Seven
@Tangle_Foot
@The Quest for Six

xwalker · Jul 1, 2019

OmerV said:
Definitely a missed call, but it's a bit harder to see full speed in a game, and the LB did at the last second turn his head toward the ball. That act seems to fool a lot of refs, even if it really comes too late after the interference has occurred.

A defender turning his head is with regards to incidental contact on a contested ball.

This defender body slammed the WR and it was long before the ball was close enough to be contested.

OmerV · Jul 1, 2019

xwalker said:
A defender turning his head is with regards to incidental contact on a contested ball.

This defender body slammed the WR and it was long before the ball was close enough to be contested.

I agree, which is why I said it was a missed call and talked about it fooling refs even though it may happen after the interference has already occurred.

Toruk_Makto · Jul 1, 2019

Idgit said:
Defender isn’t playing the ball. That’s an obvious PI. It was a poorly thrown pass, as well, though.

Yup. This was all discussed at the time too.

MapleLeaf · Jul 1, 2019

KJJ said:
It mattered on that play because the ball being thrown behind Brown forced him to have to slow up and turn back which contributed to the contact between him and the defender. To get a PI call on a poor throw it has to be a flagrant foul and that wasn’t. Had the ball been thrown out in front of Brown he would’ve been running away from the defender scoring a touchdown, not having to turn back toward the defender to try and catch the ball. I’m not going to spend all day on this our opinions differ and we’ll just leave it at that. One of the reasons PI calls will now be reviewable is because not everyone sees them the same way. It’s a judgment call.

This opinion will not work for NFL football. If what you say is true, then the technique I would be teaching all pass defenders is if the WR turns back towards you don't play the ball just run straight into the WR. It won't be pass interference.

You have spent time giving your opinion, but I dare you or any other who claim the defender turns his head back to show it in a video or picture. From even the grainy pics I isolated he never looks back at the ball. He just runs right into Brown. If you look at this feet he doesn't even stops striding. He just crashes right into him.

xwalker · Jul 1, 2019

davidyee said:
This opinion will not work for NFL football. If what you say is true, then the technique I would be teaching all pass defenders is if the WR turns back towards you don't play the ball just run straight into the WR. It won't be pass interference.

You have spent time giving your opinion, but I dare you or any other who claim the defender turns his head back to show it in a video or picture. From even the grainy pics I isolated he never looks back at the ball. He just runs right into Brown. If you look at this feet he doesn't even stops striding. He just crashes right into him.

The super-slow-motion vid I just posted should help.

If you view it full screen on a computer, not phone, it's clear the defender never really turns his head back to the ball.

The most he turns his head is after he has slammed into the WR.

It's hard to see his face-mask after he puts his hand up, but prior to putting his hand up the face mask is not closed to being turned back towards the ball.

KJJ · Jul 1, 2019

davidyee said:
This opinion will not work for NFL football. If what you say is true, then the technique I would be teaching all pass defenders is if the WR turns back towards you don't play the ball just run straight into the WR. It won't be pass interference.

You have spent time giving your opinion, but I dare you or any other who claim the defender turns his head back to show it in a video or picture. From even the grainy pics I isolated he never looks back at the ball. He just runs right into Brown. If you look at this feet he doesn't even stops striding. He just crashes right into him.

Brown ran into the defender due to an inaccurate pass. He had to slow up and turn back which initiated the contact with the defender. I’m not wasting anymore time with this.

xwalker · Jul 1, 2019

KJJ said:
Brown ran into the defender due to an inaccurate pass. He had to slow up and turn back which initiated the contact with the defender. I’m not wasting anymore time with this.

Probably a good idea for you to give up spending time on this.

I don't spend time trying to be a ballet dancer since I know it's beyond my abilities.

It appears that football analysis is beyond your abilities.

KJJ · Jul 1, 2019

xwalker said:
Probably a good idea for you to give up spending time on this.

I don't spend time trying to be a ballet dancer since I know it's beyond my abilities.

It appears that football analysis is beyond your abilities.

It appears you’re just looking to exchange insults. If analyzing football was beyond my abilities I wouldn’t end up right all the time. My posting history speaks for itself. :thumbup:

KJJ · Jul 1, 2019

If some want to spend 10+ pages arguing a non call against an average WR in a game the Cowboys won go ahead. Some are acting like that play cost the Cowboys the game. Gotta love this dead period before training camp. LOL It's the inaccurate throw that everyone should be concerned with. If that pass was thrown accurately the defender never has a chance to make contact with Brown. Brown had to slow up and go back to the ball which caused the contact and incompletion.

HungryLion · Jul 1, 2019

The defender himself even admitted after the game that it was pass interference.

Doomsay · Jul 1, 2019

rocyaice said:
Dak could’ve put more air under that and Brown could’ve sold it more but that was one of the more ridiculous PI calls not called.

It was a bad pass

Noah Brown catch Interference?

I Copy!,,, er,,,I guess,,,ah,,,maybe.

You Have an Axe to Grind

Well-Known Member

You Have an Axe to Grind

Well-Known Member

You Have an Axe to Grind

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Maple Leaf

Well-Known Member

You Have an Axe to Grind

Well-Known Member

You Have an Axe to Grind

You Have an Axe to Grind

Well-Known Member

Well-Known Member