Chris Culliver has INT called back for ... well, a really, really bad call

The NFL has tried to clean up the game of some dirty hits, and that’s a good thing. But it becomes a bad thing when defensive players can’t play football anymore.

Washington Redskins cornerback Chris Culliver had what looked like an interception for a touchdown on Sunday, which would have put his team up 21-14 over the Carolina Panthers. Huge play.

But there was a flag, and if you can watch the play and figure out what exactly Culliver did that should be penalized, you’ve got me beat. Everything about that play looks like football. I can't even tell you what the officials thought was illegal about it – that's how bad of a call it was.

Culliver hit Olsen, who had to reach a bit for a pass from Cam Newton. That hit looked normal and legal in every way. But a flag was thrown, the officials talked about it for a while (“Wait, you actually saw something illegal that play? Like what?” is what I imagine was said) and decided to penalize Washington 15 yards instead of letting a legitimate touchdown stand.

That call turned the momentum of the game. Washington battled for a while, but it’s hard when you have a touchdown stolen from you. Carolina went on to win 44-16. And that one play wasn't the reason Washington ultimately lost.

(Washington's Jason Hatcher has some ideas about the officiating.)

The NFL is right to try to clean up the game and make it as safe as it can, but when Culliver’s play isn’t legal, what is anymore?

​

- - - - - - -

Frank Schwab is the editor of Shutdown Corner on Yahoo Sports. Have a tip? Email him at shutdowncorner@yahoo.com or follow him on Twitter! Follow @YahooSchwab