Does the NFL Have an Inexcusable Officiating Problem?

Being a referee is something of a thankless job on the best of days.

It was not the best of days for the zebras in Week 16. In fact, it hasn't been the best of years.

The 2013 season in the NFL has been littered with officiating gaffes. From botched spots to blasted punters, it's been a rough year for the refs.

Just ask Jeff Triplette, aka "the poster boy for bad officials."

Like it or not, if the following plays are any indication, then the NFL has a serious officiating problem.

Getting a call wrong here or there is one thing. Missing on four of five borderline calls is another.

And that thing is not good.

Follow the Bouncing Ball

OK, this play is more bad rule than bad call.

In the third quarter of Sunday's matchup between the Pittsburgh Steelers and Green Bay Packers, a Le'Veon Bell fumble gave the Packers a 1st-and-goal.

When the Steelers held the Packers to a field-goal attempt and then blocked that attempt, it appeared the team had dodged a bullet.

Not so fast my friend!

At the end of that scrum, defensive end Ziggy Hood batted the ball out of bounds, which is a foul.

The issue arises after the penalty.

It appears that Pittsburgh safety Ryan Clark possessed the ball, which would have given the ball to the Steelers, albeit backed up due to the penalty.

However, the officials ruled that Clark did not have possession, so the Packers got the ball back and proceeded to score a touchdown.

The issue here isn't really the call itself. It's bang-bang. A case can be made for either side.

However, since the ruling was that Clark didn't possess the ball, the call isn't reviewable according to Fox Sports officiating guru Mike Pereira.

Then why exactly do we have replay?

Time Is on My Side...Unless It Isn't.

The officials' hands may well have been tied on that blocked kick.

They sure seemed to be where stopping the clock was concerned.

As the game wound down, and the Packers were on the brink of scoring a tying touchdown, Don Barclay was flagged for a false start.

The play cost Green Bay five yards and a 10-second runoff.

OK, so it was more like 15.

"

So there was a false start, but the play kept going and ran 5 seconds off the clock, but the refs didn’t add that 5 seconds back.

— Bill Barnwell (@billbarnwell) December 23, 2013

"

Time ran out on the Packers (and possibly their season) on the next play.

What is it with teams in Wisconsin and clocks?

A Horse (Collar) Is a Horse (Collar) of Course of Course

Not a lot went right for the Kansas City Chiefs in Week 16, as the team lost any hope of winning the AFC West with a loss to the Indianapolis Colts.

It didn't help that the officiating crew led by Tony Corrente was not exactly on top of things.

In the first quarter of the game, with the Chiefs leading 7-0, Colts running back Trent Richardson was pulled down by linebacker Derrick Johnson. The play would have resulted in fourth down, but Johnson was penalized for a horse-collar tackle.

Except that it wasn't a horse-collar tackle. In fact, it wasn't even especially close.

Here's what the NFL rules say about horse-collar tackles:

"

No player shall grab the inside collar of the back or the side of the shoulder pads or jersey  pads or jersey, and pull the runner toward the ground. This does not apply to a runner who is in the tackle box or to a  quarterback who is in the pocket.

Note: It is not necessary for a player to pull the runner completely to the ground in order for the act to be illegal. If his knees are buckled by the action, it is a foul, even if the runner is not pulled completely to the ground.

"

What the rule says, and what that tackle was, are not the same.

You'd think to horse-collar someone you'd have to get, you know, the collar or something.

Apparently not.

It's a FUMBLE! Wait, No It's Not

In recent seasons, there have been any number of instances where plays either looked like a catch only to be ruled incomplete or looked incomplete only to be called a catch.

For the record, here's what the NFL rules have to say about what constitutes a reception.

"

A player who makes a catch may advance the ball. A forward pass is complete
(by the offense) or intercepted (by the defense) if a player, who is inbounds:
(a) secures control of the ball in his hands or arms prior to the ball touching the ground; and
(b) touches the ground inbounds with both feet or with any part of his body other than his hands; and
(c) maintains control of the ball long enough, after (a) and (b) have been fulfilled, to enable him to perform any act common to the game (i.e., maintaining control long enough to pitch it, pass it, advance with it, or avoid or ward off an opponent, etc.).

"

If that sounds confusing, it's because it is.

This may be another instance where a bad rule has as much to do with a problem as bad officiating, but the fact remains that Junior Hemingway's second-quarter fumble that wasn't certainly looked like a catch to most:

"

 Uh, that was a catch/fumble by KC's Junior Hemingway. #colts should get the ball

— Mike Chappell (@mchappell51) December 22, 2013

"

Not only was it not ruled a fumble on the field, but the play stood on review.

Of course, without "incontrovertible physical evidence," even the worst call in history can't be overturned.

First Bounce Counts, Right?

For this one you don't need a detailed and thorough knowledge of the NFL rule book.

So long as you know that the ball isn't supposed to bounce, you should be fine.

Unless, that is, you were an official working Sunday afternoon's game in Seattle.

With the Seahawks trailing by seven late in the fourth quarter, Russell Wilson attempted a pass to Doug Baldwin that appeared to carom off the ground before being snagged by Arizona Cardinals linebacker Karlos Dansby.

When the play was ruled an interception it was head-scratching. The fact that the play wasn't overturned was jaw-dropping.

The ball hit the ground. If they can't get the easy calls right, how are the officials going to fare on the hard ones?

As this season has shown, not very well.

Flags for Everyone!

It's been a miserable year for the Atlanta Falcons, who showed a lot of guts and pride in playing the San Francisco 49ers tough Monday night.

Unfortunately the Falcons lost the game, although it isn't entirely their fault...

What with having to take on the 49ers AND the officials.

There were a few questionable calls in the last ever regular-season game at Candlestick Park, but the rest don't hold a candle to the atrocious pass interference call on linebacker Paul Worrilow in the third quarter.

What did he do? Give the receiver a dirty look? Use harsh language?

The play led to a field goal for San Francisco. It was also the point in the game where they took the lead for good.

Not that that's important or anything.