ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Blown calls: Questioning the value of instant replay if it isn't available for all plays or doesn't get the call right

Updated on September 25, 2012

When Chicago Bears fans, who hate the Green Bay Packers, are complaining that the Packers got robbed, you know something is badly amiss. Such was the case after the Seattle Seahawks’ 14-12 victory over the Packers Monday night.

By now you’ve probably seen replays and read about what may go down in history as the worst officiated game in the history of the NFL. But to recap briefly: On the final play of the game, Seattle quarterback Russell Wilson heaved a ball into the end zone. Green Bay defender M.D. Jennings intercepted the ball over the outstretched hands of Seattle’s Golden Tate, who was that close to the ball only because he had blatantly shoved the Packers’ Sam Shields out of the way.

On the way to the ground Tate managed to place his hands on the ball, which Jennings hugged tightly to his chest. One official ruled it a simultaneous catch, which automatically goes to the receiver and thus was ruled a touchdown. After an instant replay review that showed clearly to everyone within range of a television set that the correct call was an interception, the referees decided that the ruling the field, a touchdown, stands.

Not even the worst call of the quarter

But that wasn’t even the worst call to go against Green Bay in the fourth quarter. On the Seahawks’ previous possession, Wilson tried a pass to wide receiver Sidney Rice. Shields had perfect position to catch the ball but as he went up for it, Rice grabbed Shields from behind, pushed him down and placed his hand on Shields’ face mask. An easy call of offensive pass interference, right? And possibly even a hands-to-the-face penalty. But the referees ruled it was defensive pass interference on Shields.

If that play had been called correctly, the Packers wouldn’t have been pinned on their own two-yard line later on, wouldn’t have had to punt out of their end zone and the final controversial play may never have happened.

Those weren’t the only bad calls but they were the main ones that affected the outcome of the game.

Who's at fault?

Of course, the Internet and Twitter have blown up about the officiating of that game (I haven’t read nearly all of the blogs but I have yet to see one that even hints that the officials got the call right).

The biggest bone of contention for most people is the replacement referees. The regular officials are on strike for better pension benefits and for some reason, Division I college referees are not allowed to replace them. So the NFL has tried its luck with lower level college referees without much success.

It’s easy to blame the replacement referees for the debacle they’ve caused to the NFL season so far. Or to blame the regular refs for going on strike. Or to blame the NFL for not settling the strike. My guess is that all are at fault.

Regular refs may have blown it too

But would the game have been called differently had the regular refs been there? Hopefully, but there’s no guarantee. In light of the blown calls by the replacement refs, some fans talk about the regular officials as if they could walk on water, and possibly change the water into wine as they walked on it. But I’ve seen plenty of egregious calls made by the regular officials.

If you doubt this, just ask the Seattle fans who believed they got hosed by the officials in Super Bowl XL, which allowed the Pittsburgh Steelers to win. And they may be right, since several years later one of the officials publically apologized to Seattle for two botched calls he made.

Let’s not forget that one of the main reasons we have instant replay in the NFL now is because the regular officials made so many errant calls on scoring plays and turnovers.

So while the regular refs are no doubt better than their replacements – certainly better versed in the rules – they may have botched the final call as well.

Instant replay should be available on all calls

And this brings me around to the issue of instant replay. It is somewhat stunning how often bad calls on the field are allowed to stand despite contradictory evidence on the replays.

Fox Sports employs Mike Pereira, former NFL official and former Vice President of Officiating, as its analyst for officiating decisions. While observing the replays – the same replays the on-field officials are reviewing – he explains why a call should or shouldn’t be reversed based on the rules. The actual after-review call goes against his explanation at least 50 percent of the time, which leads me to believe that either a) Pereira is the worst official in the history of the game or b) the officials are not only messing up the plays on the field but on the replays as well. (I realize there might be option c) all of the above.)

But penalties – either called or not called – are not reviewable. Those are seen as judgment calls by the refs so they cannot be questioned. However, all calls by the referees are judgment calls. Whether the runner stepped out of bounds, if the ball crossed the goal line, where the ball should be spotted on the field are all judgment calls. But those can be reviewed or challenged.

Not allowing penalties to be reviewed would make more sense if the referees had some leeway in making the calls. But the NFL has extremely detailed rules and requirements for nearly every penalty. It is pretty clear to determine from a replay what is and what isn’t holding, based on the rulebook. Same for pass interference, roughing the passer and virtually every other rule. It would be no harder to reverse a penalty decision than an out of bounds decision.

I believe that if it is so critical to get a call right about whether a receiver has possession of the ball all the way to the ground, then you should use it for every critical decision, which includes penalties. If the technology is good for one thing, then why isn’t it good for everything?

Questioning value of instant replay in baseball

And this brings me to the proposed expansion of instant replay in baseball. As I’ve written before, this concerns me a great deal. Currently only potential home runs are reviewable. Next season, fair-foul calls and catch-trapped ball plays will be under review as well.

However, plays at the bases and balls-strikes, wherein lies most of the controversy, won’t be. I don’t think I’ve seen a manager ejected for arguing a fair-foul call but I’ve seen plenty run out for arguing plays at the bases and balls and strikes.

(Side note: I believe baseball umpires are vastly superior to NFL officials, even the regular ones. While there are the occasional egregious calls like the Jim Joyce call that ended Armando Galarraga’s chance for a perfect game two years ago, or calling Mark Teixeira out on a play where he was clearly safe at first a couple of weeks ago against the Orioles, most of the time instant replay vindicates their calls on the bases, or at least it’s too close to tell on even slow motion. On Monday night, for example, Curtis Granderson threw home for a bang-bang play at the plate. Umpire Paul Nauert called Ryan Doumit out. Initially, and even after looking at the first replay, I thought he’d blown the call. But when they showed the super slo-mo it was obvious that Russell Martin’s glove touched Doumit’s shoulder while his hand was still about three inches from the plate. It seems that baseball umpires collectively, over the course of a long season, have several blown calls that affect games. Football referees, in contrast, seem to have several per game in a much shorter season.)

If you want to get it right, get it all right

Back to football, though. My question is: Are people concerned about getting all the calls right or just some of the calls? If just some of them, and those the infrequent and usually non-controversial ones, then why bother at all? But if you want to get all the calls right, then why not subject all calls, including penalties, to replay scrutiny?

Of course, if Monday’s final play is any indication, then probably there will still be plenty of times where it won’t be called right even after the replay. And if not, then why bother at all?


    0 of 8192 characters used
    Post Comment
    • profile image

      Joe M 

      6 years ago

      The TD call was the correct call. It may take a few decades, but once the emotion dies down, people will realize that they were scammed by ESPN

    • rfmoran profile image

      Russ Moran - The Write Stuff 

      6 years ago from Long Island, New York

      The Packers loss Monday night will go down in the annals of bad officiating because the Packers weren't defeated by Seattle but by one inexperienced official. If this keeps up the whole season will be in doubt as to who really won what game.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, 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:

    Show Details
    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 or domains, for performance and efficiency reasons. (Privacy Policy)
    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)
    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.
    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)