Calvin Johnson getting a touchdown taken away from him in Week 1 on a goofy replay reversal ... it's a tradition unlike any other.
In 2010, Johnson had a touchdown taken away against the Bears in a play so controversial, it spawned the explanation "The Calvin Johnson Rule" for any touchdown that isn't a touchdown because the receiver doesn't finish the catch. That play cost the Lions a win (and still, to this day, it's a baffling call).
[Play Y! Sports Fantasy Football: Create or join a league today!]
On Sunday against Minnesota, it looked like Johnson had a sure touchdown. He made a great diving catch. For fantasy owners who dealt with Johnson being continuously tackled on the 1-yard line last year, it was a nice way to start the season. There was no question watching it in real time that it was a touchdown. Then the officials went to the replay booth.
And then they ruled it wasn't a touchdown.
Oh, say it ain't so.
Johnson ended up stretching the ball and apparently lost control as he cradled the ball going to the ground, negating his touchdown.
As I said on FOX, in Detroit, that was the process of making the catch you have to hold on to it unless you've had it long enough to make...
— Mike Pereira (@MikePereira) September 8, 2013
...a "football move." — Mike Pereira (@MikePereira) September 8, 2013
Yep, he Calvin Johnson Rule. The call was reversed even though it looked like a great play and a sure touchdown, Johnson had his first touchdown taken off the board, and his reaction was understandable – a frustrated smile that seemed to say "Again?"
Yeah, Megatron. Again.