Go Back   New Orleans Saints - blackandgold.com > Main > Saints

50 things we learned in Week 7 in the NFL

this is a discussion within the Saints Community Forum; I hope he doesn't make a habit out of this! 9. Saints coach Sean Payton was 0-for-2 on replay challenges in the first quarter. He was also out of timeouts with 50 seconds to go in the first quarter. The ...

Like Tree16Likes

Closed Thread
 
LinkBack Thread Tools Display Modes
Old 10-26-2015, 12:42 PM   #1
SaintsWillWin
 
Join Date: Nov 2010
Location: Shreveport,Louisiana
Posts: 12,326
50 things we learned in Week 7 in the NFL

I hope he doesn't make a habit out of this!

9. Saints coach Sean Payton was 0-for-2 on replay challenges in the first quarter. He was also out of timeouts with 50 seconds to go in the first quarter. The first quarter!

10. Of course, Payton’s team was up 14-0 at the end of that quarter, so maybe he is onto something.

50 things we learned in Week 7 in the NFL
WhoDat!656 is offline  
Old 10-26-2015, 12:44 PM   #2
5000 POSTS! +
 
Join Date: Oct 2009
Posts: 6,446
Re: 50 things we learned in Week 7 in the NFL

The second challenge was very odd

Firstly, Watson didn't make the first down even with the outstretched hand.
Secondly, if your going to run a fake FG, then why challenge the previous play?
dizzle88 is offline  
Old 10-26-2015, 01:48 PM   #3
Site Donor
 
Join Date: Apr 2007
Location: Atlanta
Posts: 7,555
Blog Entries: 3
Re: 50 things we learned in Week 7 in the NFL

Originally Posted by dizzle88 View Post
The second challenge was very odd

Firstly, Watson didn't make the first down even with the outstretched hand.
Secondly, if your going to run a fake FG, then why challenge the previous play?
Payton knew what he was doing all along.

Challenging the previous play was just the first part of his deception.
saintsfan1976 is offline  
Old 10-26-2015, 03:28 PM   #4
Site Donor
 
Join Date: Jan 2013
Location: Bedford, TX
Posts: 5,473
Blog Entries: 1
Re: 50 things we learned in Week 7 in the NFL

Week to week league.
K Major is offline  
Old 10-26-2015, 03:41 PM   #5
1000 Posts +
 
Join Date: Jan 2005
Location: Monroe, La
Posts: 1,394
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.
nola_swammi is offline  
Old 10-26-2015, 05:03 PM   #6
Registered
 
Join Date: May 2013
Posts: 82
Re: 50 things we learned in Week 7 in the NFL

Originally Posted by nola_swammi View Post
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 is offline  
Old 10-26-2015, 05:04 PM   #7
1000 Posts +
 
Join Date: Mar 2012
Posts: 2,438
Blog Entries: 2
Re: 50 things we learned in Week 7 in the NFL

Originally Posted by nola_swammi View Post
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.

If I had a nickel for every time I heard that, the NFL would fine and suspend me.
burningmetal is offline  
Old 10-26-2015, 05:07 PM   #8
10,000+ Posts!!
 
Join Date: Mar 2006
Location: Metairie, LA
Posts: 10,390
Blog Entries: 5
Re: 50 things we learned in Week 7 in the NFL

What was harder to believe than the ball being complete on the challanges was that, we were winning by halftime.

RaginCajun83 likes this.

Last edited by foreverfan; 10-26-2015 at 08:17 PM..
foreverfan is offline  
Old 10-26-2015, 05:07 PM   #9
1000 Posts +
 
Join Date: Mar 2012
Posts: 2,438
Blog Entries: 2
Re: 50 things we learned in Week 7 in the NFL

Originally Posted by jlaw8920 View Post
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.
burningmetal is offline  
Old 10-26-2015, 05:48 PM   #10
Hou Saints Fan
 
Join Date: Sep 2009
Location: Houston, Tx
Posts: 4,725
Re: 50 things we learned in Week 7 in the NFL

Originally Posted by burningmetal View Post
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.
RaginCajun83 is offline  
Closed Thread

Thread Tools
Display Modes

Posting Rules

LinkBacks (?)
LinkBack to this Thread: http://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 06:19 PM 2
The Latest New Orleans Saints News | SportSpyder This thread Refback 10-26-2015 03:13 PM 1


All times are GMT -5. The time now is 05:07 AM.


Copyright 1997 - 2014 - BlackandGold.com
no new posts