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

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?

Re: 50 things we learned in Week 7 in the NFL
 

Payton knew what he was doing all along.

Challenging the previous play was just the first part of his deception.

Re: 50 things we learned in Week 7 in the NFL
 

Week to week league.

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.

Re: 50 things we learned in Week 7 in the NFL
 

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.

Re: 50 things we learned in Week 7 in the NFL
 

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.

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.

http://www.wherecoolthingshappen.com...cat-wcth01.jpg

Re: 50 things we learned in Week 7 in the NFL
 

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.

Re: 50 things we learned in Week 7 in the NFL
 

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