50 things we learned in Week 7 in the NFL

nola_swammi · 10-26-2015, 02:41 PM

That second red flag look legitimate. I thought and still think that was a catch.

jlaw8920 · 10-26-2015, 04:03 PM

Originally Posted by nola_swammi

That second red flag look legitimate. I thought and still think that was a catch.

I completely agree that it should have been called a catch. However, as someone mentioned above, it still wouldn't have given us a first down.

burningmetal · 10-26-2015, 04:07 PM

Originally Posted by jlaw8920

I completely agree that it should have been called a catch. However, as someone mentioned above, it still wouldn't have given us a first down.

If they had ruled it as a catch as they should have, then they would have also had to spot it where he reached out. He would have been maybe a half yard short, and from where we were on the field Payton was surely going to go for it. There's no other reason he would have challenged.

I think not getting the call made him angry and influenced going for the fake.

burningmetal · 10-26-2015, 04:04 PM

Originally Posted by nola_swammi

That second red flag look legitimate. I thought and still think that was a catch.

So do I. I heard John Lynch (who was absurdly annoying throughout the entire broadcast) and Mike Pereira try to explain the rules to us for the billionth time, and they were all completely missing the point, just like the refs on the field. They kept saying how he didn't complete the process to the ground, but he had two feet, then two knees on the ground and reaches out for the first down when the ground finally knocks it out.

That is possession and a football move. It's not the same as a guy leaping for a ball and coming straight down and having the ball pop out on impact. He had clear control of the ball and REACHED.

How is it that when a guy catches the ball standing upright, catches the ball and takes two steps with some type of "football move", and the defender knocks it out, it's called a fumble. Thus declaring that the receiver had control... But if the receiver gets two feet and two knees (the equivalent of at least two steps) and makes football move in reaching out, but the ball gets knocked out by the ground it is suddenly incomplete?

Did any of that even make sense? There are rules in what makes a catch that contradict other rules that make a catch. And beyond that, it seems like no rule involving a catch is interpreted the same way twice in a row. The NFL remains a joke.

RaginCajun83 · 10-26-2015, 04:48 PM

Originally Posted by burningmetal

So do I. I heard John Lynch (who was absurdly annoying throughout the entire broadcast) and Mike Pereira try to explain the rules to us for the billionth time, and they were all completely missing the point, just like the refs on the field. They kept saying how he didn't complete the process to the ground, but he had two feet, then two knees on the ground and reaches out for the first down when the ground finally knocks it out.

That is possession and a football move. It's not the same as a guy leaping for a ball and coming straight down and having the ball pop out on impact. He had clear control of the ball and REACHED.

How is it that when a guy catches the ball standing upright, catches the ball and takes two steps with some type of "football move", and the defender knocks it out, it's called a fumble. Thus declaring that the receiver had control... But if the receiver gets two feet and two knees (the equivalent of at least two steps) and makes football move in reaching out, but the ball gets knocked out by the ground it is suddenly incomplete?

Did any of that even make sense? There are rules in what makes a catch that contradict other rules that make a catch. And beyond that, it seems like no rule involving a catch is interpreted the same way twice in a row. The NFL remains a joke.

It's stupid crap like this that is starting to make me more interested in college football over the NFL

10-26-2015, 02:41 PM	#1
nola_swammi 1000 Posts + Join Date: Jan 2005 Location: Monroe, La Posts: 2,627	Re: 50 things we learned in Week 7 in the NFL That second red flag look legitimate. I thought and still think that was a catch. mleg1972, 44Champs and jlaw8920 like this.

10-26-2015, 04:03 PM	#2
jlaw8920 100th Post Join Date: May 2013 Posts: 123	Re: 50 things we learned in Week 7 in the NFL Originally Posted by nola_swammi That second red flag look legitimate. I thought and still think that was a catch. I completely agree that it should have been called a catch. However, as someone mentioned above, it still wouldn't have given us a first down.
jlaw8920 100th Post Join Date: May 2013 Posts: 123

10-26-2015, 04:07 PM	#3
burningmetal 1000 Posts + Join Date: Mar 2012 Posts: 3,923 Blog Entries: 3	Re: 50 things we learned in Week 7 in the NFL Originally Posted by jlaw8920 I completely agree that it should have been called a catch. However, as someone mentioned above, it still wouldn't have given us a first down. If they had ruled it as a catch as they should have, then they would have also had to spot it where he reached out. He would have been maybe a half yard short, and from where we were on the field Payton was surely going to go for it. There's no other reason he would have challenged. I think not getting the call made him angry and influenced going for the fake. Rell&Gold likes this.

10-26-2015, 04:04 PM	#4
burningmetal 1000 Posts + Join Date: Mar 2012 Posts: 3,923 Blog Entries: 3	Re: 50 things we learned in Week 7 in the NFL Originally Posted by nola_swammi That second red flag look legitimate. I thought and still think that was a catch. So do I. I heard John Lynch (who was absurdly annoying throughout the entire broadcast) and Mike Pereira try to explain the rules to us for the billionth time, and they were all completely missing the point, just like the refs on the field. They kept saying how he didn't complete the process to the ground, but he had two feet, then two knees on the ground and reaches out for the first down when the ground finally knocks it out. That is possession and a football move. It's not the same as a guy leaping for a ball and coming straight down and having the ball pop out on impact. He had clear control of the ball and REACHED. How is it that when a guy catches the ball standing upright, catches the ball and takes two steps with some type of "football move", and the defender knocks it out, it's called a fumble. Thus declaring that the receiver had control... But if the receiver gets two feet and two knees (the equivalent of at least two steps) and makes football move in reaching out, but the ball gets knocked out by the ground it is suddenly incomplete? Did any of that even make sense? There are rules in what makes a catch that contradict other rules that make a catch. And beyond that, it seems like no rule involving a catch is interpreted the same way twice in a row. The NFL remains a joke. nola_swammi, mleg1972, RaginCajun83 and 2 others like this.
	If I had a nickel for every time I heard that, the NFL would fine and suspend me.

10-26-2015, 04:48 PM	#5
RaginCajun83 Hou Saints Fan Join Date: Sep 2009 Location: Houston, Tx Posts: 5,050	Re: 50 things we learned in Week 7 in the NFL Originally Posted by burningmetal So do I. I heard John Lynch (who was absurdly annoying throughout the entire broadcast) and Mike Pereira try to explain the rules to us for the billionth time, and they were all completely missing the point, just like the refs on the field. They kept saying how he didn't complete the process to the ground, but he had two feet, then two knees on the ground and reaches out for the first down when the ground finally knocks it out. That is possession and a football move. It's not the same as a guy leaping for a ball and coming straight down and having the ball pop out on impact. He had clear control of the ball and REACHED. How is it that when a guy catches the ball standing upright, catches the ball and takes two steps with some type of "football move", and the defender knocks it out, it's called a fumble. Thus declaring that the receiver had control... But if the receiver gets two feet and two knees (the equivalent of at least two steps) and makes football move in reaching out, but the ball gets knocked out by the ground it is suddenly incomplete? Did any of that even make sense? There are rules in what makes a catch that contradict other rules that make a catch. And beyond that, it seems like no rule involving a catch is interpreted the same way twice in a row. The NFL remains a joke. It's stupid crap like this that is starting to make me more interested in college football over the NFL captainshawn likes this.

LinkBacks (?) LinkBack to this Thread: https://blackandgold.com/saints/74874-50-things-we-learned-week-7-nfl.html
Posted By	For	Type	Date	Hits
50 things we learned in Week 7 in the NFL	This thread	Refback	10-26-2015 05:19 PM	2
The Latest New Orleans Saints News \| SportSpyder	This thread	Refback	10-26-2015 02:13 PM	1