Detroit TD..Official No TD...RIght or Wrong?

Jump to Last Post 1-8 of 8 discussions (14 posts)
  1. Michael Willis profile image76
    Michael Willisposted 8 years ago

    WRONG! By the rule the receiver has to carry the ball to the ground or it is an incompletion. This is what the Official used for the over-ruling the TD. I understand that rule.

    BUT...look at replay...Johnson caught the ball in the Endzone, showed possession...then BODY made contact with ground (officially play over) and then...hand hit ground and lost ball!
    DUH...Officials blew the call and now are protecting themselves trying to "use the letter of the rule", but they are missing all parts of the play. The body contact with the ground means Play Over!
    This should have be ruled a Touchdown...Detroit Lions!!!

    Sorry Lions fans, you got ripped-off!

    1. LakeShow T profile image79
      LakeShow Tposted 8 years agoin reply to this

      Gosh, this one is tough. You pose a great argument Michael. I still don't know what to think personally. It's funny because you've got the Detroit coach saying it was the right call and Tommy Harris for the Bears saying he has no idea how the refs made the call they did. That's hilarious. I just don't know and I can't say definitively one way or the other what the right call should have been. It's a good thing it is week one between two teams that don't figure to be in the running for the playoffs. What a mess that would have been had it been a playoff game. Maybe Coach Schwartz wasn't mad about it because he knows it will just get the Lions a better draft pick next season..haha. Kudos to him at least for being classy about a heartbreaking call for his team and Lion fans.

      1. Michael Willis profile image76
        Michael Willisposted 8 years agoin reply to this

        I am not a fan of either team, so it really doesn't matter personally. But, this is a ruling that has been used right and wrong since it was implemented. I am against the way the rule is used. It Has to be changed!!!
        If the player's body had Not touched the ground Before the hand did and the ball lost...I would agree with the Ref. But, "the body touched first-Play over."

  2. bystuffonline profile image53
    bystuffonlineposted 8 years ago

    I don't understand the letter of the law.  He had two feet down in the endzone and still had possession.  At that point, I would have thought the play to be over and the touchdown good.

    1. Michael Willis profile image76
      Michael Willisposted 8 years agoin reply to this

      I agree! Ref blew the call. Now they are trying to validate the call since they are getting ripped over it.

  3. profile image61
    logic,commonsenseposted 8 years ago

    elevator, elevator, Detroit got the shaft!

  4. Ron Montgomery profile image59
    Ron Montgomeryposted 8 years ago

    I believe the ref was correct.  By rule, if a receiver goes to the ground through his own momentum, he has to maintain control completely through the play. The play is not ended simply because he hits the ground. The fact that it occurred in the end zone is irrelevant in this case.

    It may not be fair or logical, but it is the rule.

    1. Michael Willis profile image76
      Michael Willisposted 8 years agoin reply to this

      I still say it is mis-interpreted by a home field ref! Continuation was ended when he hit the ground=TD. It has been called that way through out the tenure of the rule. It was called differently today.  Johnson did what the rule called for.

    2. tony0724 profile image56
      tony0724posted 8 years agoin reply to this

      Ron this is going to be painful for me. But I agree with you !

      1. Mikeydoes profile image75
        Mikeydoesposted 8 years agoin reply to this

        Being a 100% Bears fan I have to disagree with you and Ron.

        Not only did he catch it, he hit the ground, held on to it , and as he was getting up he flipped the ball out of his hand(watch his fingers).. while on the ground. Never did he lose it.

        Worst call I have ever seen. Either that one or the 2 calls against both teams for hitting the quarterback a split second after it was released.

  5. Michael Willis profile image76
    Michael Willisposted 8 years ago

    This is a rule the NFL uses that I have disagreed with ever since is was put into place. Too many games or plays have been decided by a REF's decision, not whether a play was right or wrong.
    It is a rule the NFL needs to address and change so this type of bad call never happens again.

  6. prettydarkhorse profile image62
    prettydarkhorseposted 8 years ago

    Hmm, a real touchdown, he hit the ground with his body!

    This one is different, just to make you all smile ...

    http://sports.yahoo.com/soccer/blog/dir … sow-268819

  7. EYEAM4ANARCHY profile image85
    EYEAM4ANARCHYposted 8 years ago

    They got robbed. If holding the ball in one hand and shaking it toward the camera isn't an indication of control, I don't know what is.

    And the ball didn't get knocked out as he was going to the ground or when he hit the ground. He was down and was getting back up when the ball came out of his hand. The completion of the play doesn't extend all the way to him walking to the sidelines and getting a cup of Gatorade.

  8. Anna Marie Bowman profile image91
    Anna Marie Bowmanposted 8 years ago

    The Lions totally got robbed!!!  I was watching the game, and got pretty upset.  I WAS hoping Detroit would win...the whole underdog thing, and I hate the Bears...

 
working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)