Quote:Yeah, he did cut in, but I think he was pulling a double move on the play because if you watch it, especially on the replay, you can see where he cuts in, then goes to turn up field and he's brought down. Not saying the ball was even remotely catchable, but when your receiver gets taken down on the play, that should draw an illegal contact flag in most instances. It wasn't a good throw by Bortles, but it never should have wound up being a pick 6. The refs suddenly had a little stage fright with the flags.
Here's the video.
He definitely cuts inward in a way that would imply it's intentional, rather than a panic attempt to make up ground. Looking at it again though, regardless of intent, I agree, I do think a flag should've been thrown there. I didn't even realize the DB went at him like that
I just don't see how you don't even throw a flag so you can at least talk about it with the other officials out there.
Quote:The refs realized they screwed this call up. The PI on the final drive on the walters play was a make up call for this. IMO, A Rob got tackled. It was no ones fault.
Thats why I didn't feel bad about the Walters call because we had some big calls cost us not only in that game but multiple games this year. You win some you lose some.
All due respect blake blew the read. He saw blitz and anticipated cover zero instead of single high. I believe robinson made a sight adjust to an incut because the safety eas over the top and the corner had outside leverage. His move upfield was in reaction to the throw. The flag stayed in because the contact occured so far away that it was deemed uncatchable and i think holding wasnt called because the ref could tell that the ckntavt was a spontaneous interaction based on the wrong route that made the ball clearly uncatchable.
Quote:All due respect blake blew the read. He saw blitz and anticipated cover zero instead of single high. I believe robinson made a sight adjust to an incut because the safety eas over the top and the corner had outside leverage. His move upfield was in reaction to the throw. The flag stayed in because the contact occured so far away that it was deemed uncatchable and i think holding wasnt called because the ref could tell that the ckntavt was a spontaneous interaction based on the wrong route that made the ball clearly uncatchable.
Thats too much assuming from the refs. They have to go by what they see. And what they should have seen was contact by the conerback while the ball was in the air. Throw the flag for PI. Discuss with other officials. Determine if it was catchable or not.
To me it was obvious when it happened. I would have loved the flag but in reality i think the game as a whole benefits when refs take into account when the qb and the reciever were clearly on different pages or the initial route was sloppy.
Quote:To me it was obvious when it happened. I would have loved the flag but in reality i think the game as a whole benefits when refs take into account when the qb and the reciever were clearly on different pages or the initial route was sloppy.
Regardless of the intent of the play, is it possible Robinson could have made a play on the ball? It sure seemed like it.
The pressure (due to LT Luke) on his blind side caused him throw a bad pass...
Quote:The pressure (due to LT Luke) on his blind side caused him throw a bad pass...
No it didn't, Joeckel is running his guy by Blake. He's not worried about the rush at all. Blake and Robinson were not on the same page like others have said. That being said, there definitely should have been a flag thrown. The DB tackles Robinson as Robinson cuts up field after he sees Blakes throw and adjusts. We never know if Robinson could make it to the ball and make a play because he's tackled by the DB and not given a chance.
FBT, even though I still don't think he should have thrown the ball, off his back foot, with the time remaining and on the side that side of the 50, I do agree that I like his mentality to keep throwing. Especially like the fact he bounced back and made a great throw against his body when he could have taken the easy way and ran it. I think those who are extra critical are missing one of his best attributes right now. Moving in the pocket and always keeping his eyes down field for the bigger play. Man, we just haven't had that since Brunell. I'm honestly more concerned with he completion percentage than I am with his mistakes because of how young he still is. Also, he has cut down significantly from INT's from last year at this point.
2014 Blake
Passing Yards - 1,631 (ends season at 2,908)
Passing TDs - 8
INTs - 13
QB Rating - 71.47
Completion Percentage - 63.9% (ends season at 58.9%)
2015 Blake
Passing Yards - 1,812
Passing TDs - 15
INTs - 8
QB Rating - 82.5
Completion Percentage - 55.7%
Blake started to really cool off after the bye in week 11 last year. He actually was on a pretty good pace minus the INTs (and that is a big minus), but his last 6 games he threw for less than 200 yards 4 times and never eclipsed 300 yards again. The amount of throws were relatively the same, but the INTs dropped significantly averaging just 1 every other game. That part was obviously good, but he also only threw 3 TDs. I don't think we are looking for a game manager here, but hopefully Blake will take chances when the percentage are higher for success.
The glaring thing that stands out is the completion percentage. It is the only thing other than YPA (which in some ways is tied to completion percentage) that hasn't improved. I'm sure if you nitpick there is something else, but pretty much all other stats are either better or significantly better. Lets remember where Blake was and how much he has improved. Can he sustain this type of pace TD and yard wise while completing more passes at a higher percentage for the rest of the year? Lets see if Blake keeps on improving. If anyone before the season said in week 7 this would be Blake's stat line, most if not all would take it with a collective hell yeah. I understand he deserves some criticism, but don't quite get the minority who have been so critical of a 2nd year QB with an Oline that hasn't done him many favors (and now missing their best player).
Yes Robinson is "built" to catch those jump balls, it doesn't mean you throw those in the middle of the field where the safety is lurking along with a LB. That is asking for an INT or you WR to get hit bad.
Quote:No it didn't, Joeckel is running his guy by Blake. He's not worried about the rush at all. Blake and Robinson were not on the same page like others have said. That being said, there definitely should have been a flag thrown. The DB tackles Robinson as Robinson cuts up field after he sees Blakes throw and adjusts. We never know if Robinson could make it to the ball and make a play because he's tackled by the DB and not given a chance.
I guess we can agree to disagree, because many (media) felt that it was a bad choice and throw by Blake (but I felt it had to do with the pressure given up by his Oline)..
Quote:I was so sure a flag was out I didn't even react to the play. Then slowly... slowly realized there wasn't going to be a penalty, and well...
Haha yeah I saw it the PI when it first happened and was with friends and was so adamantly sure it would be pulled back I even turned around to one of my friends and said 'unlucky for the PI ref' and then the flag didn't come...and then it didn't come...and then my smugness quickly faded!
I do think it was a 50/50 ball but I like Robinson in those scenarios
Quote:To me it was obvious when it happened. I would have loved the flag but in reality i think the game as a whole benefits when refs take into account when the qb and the reciever were clearly on different pages or the initial route was sloppy.
Uncatchable doesn't matter. Perhaps you've heard of the illegal contact rule or even holding?
To continue to beat the dead horse...In Bortles' presser, he specifically called it an in and up route. On the all 22, Robinson sort of twitched in and then planted and was starting upfield. At that moment, Bortles threw the ball...to where he expected (I surmise) Robinson to be when the ball got there. The cb bit on the in move, got crossed up and tackled Robinson. There is no way he could have legally stayed with Robinson based on where his feet were when he tackled Robinson. I did understate the pressure on Bortles...there was a fair amount, but he did get the ball out, and I think he got it out to where he wanted to put it.
I think we need to start having some tackling drills and discussion about angles to take on a running safety or cb for our offense if we are gonna have a gunslinger QB. :turned:
Jim
Quote:No it didn't, Joeckel is running his guy by Blake. He's not worried about the rush at all. Blake and Robinson were not on the same page like others have said. That being said, there definitely should have been a flag thrown. The DB tackles Robinson as Robinson cuts up field after he sees Blakes throw and adjusts. We never know if Robinson could make it to the ball and make a play because he's tackled by the DB and not given a chance.
Exactly. Joeckel did exactly what he should have. Forced the DE out of the play and Bortles was able to step up in front of him. If anything, the pressure came from the middle.
Wait. So I get to blame Bortles, Joeckel and Olsen for me feeling upset at one point on Sunday?!?!?!
It's a Jags fan dream come true!!!
Quote:Wait. So I get to blame Bortles, Joeckel and Olsen for me feeling upset at one point on Sunday?!?!?!
It's a Jags fan dream come true!!!
I blame you.
Quote:To me it was obvious when it happened. I would have loved the flag but in reality i think the game as a whole benefits when refs take into account when the qb and the reciever were clearly on different pages or the initial route was sloppy.
Still should have been a penalty
ODB would have got that call
I called that the moment it happened. Arob got tackled on the play as soon as the guy knew he was beat, that's why the safety was able to make the play all day. I maintain that the reason there was a PI call on Walters is because the reffs blew the Pick six call and made up for it. Usually we don't get so lucky.