WOW - I 'm Bears fan and Detroit just got rioyally screwed on that call.
How is that not a touchdown?
God hates the Lions. The Lions need Courage Wolf as a new mascot.
Ugh.
Well, it was a good loss for once!
Wow, week one and I already have a “worst call of the season” call.
I officially put a * by the Bears win on this one.
They got HOSED! That was a HORRENDOUS call!
For those of us not watching, what happened? Something about Megatron not coming down with the ball in the end zone?
It probably is correct if you go by the letter of the rule but it certainly seemed to be a catch by most other definitions. To compound matters, I have an over/under bet with a friend of mine that says Detroit will win more than 5 games, Calvin Johnson is my number 1 receiver on my fantasy team, and I hate the bears.
They have instituted a new rule that seems to determine a catch through the entire play. He caught the ball held it in his hands . He had control when he hit the ground. But when he rolled to get up it hit the ground. It looked like he was tossing it away after the play. The refs says a catch is determined by a continuation of the play until they decide it is over apparently. You have to hold it through the whole process( until the next day or maybe next game, who knows.)
Catch was made in the end-zone - both feet down, CLEARLY in possession of the ball. When the receiver hit the ground AFTER taking a step, again CLEARLY in possession of the ball, the ball hit the ground and popped out. The officials say the “process” must be completed, therefor it’s not a complete pass.
Did I pretty much get that right or does someone want to add?
Then, absent a recent rule change (have there been any applicable ones?), he should have a touchdown, given that guys break the plane of the goal line with the ball all of the time and are awarded the TD right then. It doesn’t matter that the FS popped the ball out of the RBs hands a millisecond later, the play is a TD.
Can’t figure out why the same logic isn’t true for a completed pass in the endzone. Receiver catches ball, comes down with both feet, maintains possession: who cares if he makes a later step and then loses the ball?
Sounds like Pereira is covering the NFL’s ass again.
That was every bit as bad as Polamalu’s non-interception a few years back.
Here’s a video of it. (At least until they take it down.)
I’m a passive Bears fan. It seems to me that the call may have been correct by the letter of the stupid rule, but that sure as hell looks to me like a touchdown.
why would it be taken down?
“Any rebroadcast, retransmission, or account of this game without the express written consent,” etc. There have already been a couple videos of this play removed from Youtube, so I was anticipating this one getting booted. On the other hand, there’s plenty of video that hasn’t been removed, so I don’t know how well this is policed.
Wow. Bears fan here and we got away with murder on that one. This is going to be a long year if THATs what it takes for us to beat the worst team in the NFL…AT HOME.
Is this rule saying that the ball is still live even after the player is down?
That’s what it sounds like to me, at least, the ball is still live if it’s in the end zone.
I think with the addition of Suh and Best, that Detroit has easily gone from worst to not worst.
A runner can break the plane and it is a touchdown even if he coughs it up. But ,that catch is not a touchdown?
A rusher has possession of the ball. Johnson didn’t, as the rule is written, and it isn’t a brand new rule. He caught the ball and went to the ground. In the process of going to the ground, he allowed the ball to hit the ground and spin out of his control. That hasn’t been catch for years. Maybe it’s a terrible rule, but it’s definitely the rule.