receivers not catching

[greediron]

Still thrown behind him and high as he jumped and turned awkwardly for the ball IIRC.

I remember that from the INT that got called back, but not the first one.  It was a bit behind I think, but catchable.  The other was all on JJ.

[StickierBuns]

Nailor has two this year that caused INTs. Three if you count the second one from today. Not ideal.

Its really been nuts. Can't remember WRers dropping so many TDs in my life....and the INT because Nailor goofed it was gross. But no one will remember the how on some of these JJM INTs and he'll get full blame for all of them. 

All the crap and the Lions and Vikings are one game apart in the standings, lol. Bad times in Motown.

[JimmyinSD]

I remember that from the INT that got called back, but not the first one.  It was a bit behind I think, but catchable.  The other was all on JJ.

Out cutting routes need to be thrown to the outside,  reciever is running blind to a ball that is typically thrown before they have a chance to get their head around and see the release,  when the ball isn't where its supposed to be thats hard to put it on the receiver unless they ran the route wrong,   which could be the case here,  but there has been so many timing routes that have been errant its hard to assume that it always the receiver. 

We can assume catchable, or the same assumption could say he made a great effort to even get his hands on the errant throw.  Either way the ball wasn't where it needed to be,  but I am seeing improvement from JJ in that he is bringing his misses down from early in the season where he was sending them 3 feet over their targets hands.   It's growth.