ADVERTISEMENT

King INT

cubsMDdmb

HB MVP
Jan 15, 2003
2,132
2,048
113
After watching the King INT again, I'm convinced that was no fluke play. At first I thought it was King being in the right place at the right time. But King knew what play was being called from the start and made a play on the ball that led to the INT. King is a great player and I hope he stays another year. Great player for the Hawks.
 
The key to the King interception was shutting down the throw to the right side that the QB wanted to make. Once we took that option away, their QB just threw in desperation and the rest is history. Great play by King.
 
Was it just me or was their an obvious no-call block in the back on that return? looked like Lomax pushed a persuit down from behind.
 
I remember seeing an interview from before the season saying he is intending on returning for his senior year. Maybe he's changed his mind after his performance this year though.

I just don't see how his stock could be higher next year. Interceptions are fluky and he might lead the Country. Pretty tough to duplicate that so why would t you go pro?

I obviously hope he stays, but it would be borderline irresponsible to risk injury. If you're a freak athlete teams will overlook a torn ACL, but I don't see that for a guy like King (even as special as he is). It is millions of dollars on the line.

I wish he would stay away from freaking punts he doesnt want to return, but definitely a special special Hawk. All timer..
 
On the last Maryland punt, as the ball came to the ground, Desmond ran towards the Iowa bench. It was like Ferentz had a rope around his waist and pulled him away from the football!

The previous punt was a little scary. But he is a special player that i hope returns next year.
 
The real key to this play was Meier reading the screen to his side and making Hills throw a desperation pass. Great return by King though. And a great block in the back by Mabin.
 
  • Like
Reactions: WWDMHawkeye
The real key to this play was Meier reading the screen to his side and making Hills throw a desperation pass. Great return by King though. And a great block in the back by Mabin.

Yeah -- it was pretty blatant. Hard to believe the refs missed it. That said, had they called it, we probably would have run some clock and scored, anyway. It could have worked out to our benefit, in that sense, had they called it.
 
OP: It was for sure a fluke. The QB missed his target by feet and the ball went into the hands of King. All Desmond after that though. Special player.
 
No, a fluke play is the interception Wisconsin had yesterday that bounced off of Shobert's helmet.
 
Great play by DK. The pass was into a crowd but on the money. You could see him recognize the play and beat the receiver to the spot. He talked earlier in the season about "running the route" along with the receiver. He did that again on this play. How about the stiff arm on the guy that clearly had an angle on him? The guy is just a playmaker.
 
Total whiff by the refs. He never got any part of the front of that jersey.
The penalty is for blocking in the back. In the replay you can see that Mabin pushed the guy on the shoulders, which is the side of a player, not the back. It was a good no call as the block was legal.

I however was worried before it happened while watching it live because you could see something was going to happen for at least 10-20 yards, but Mabin got forward just enough to avoid the penalty.
 
Was it just me or was their an obvious no-call block in the back on that return? looked like Lomax pushed a persuit down from behind.
It was Hills, the quarterback.

Looked like Hills was going to come up just short of getting to King but it was a hell-of-an-effort. For his size Hills has some serious wheels. Imagine if he could pass really well.
 
Was it just me or was their an obvious no-call block in the back on that return? looked like Lomax pushed a persuit down from behind.
Nope. I saw that too....it most definitely was a block in the back. I am shocked it wasn't called, especially since there was an official looking right at it.
 
Great play by DK. The pass was into a crowd but on the money. You could see him recognize the play and beat the receiver to the spot. He talked earlier in the season about "running the route" along with the receiver. He did that again on this play. How about the stiff arm on the guy that clearly had an angle on him? The guy is just a playmaker.

The throw was nowhere near a Maryland WR. Great stiff arm, yes.



FSsulaQ.jpg
 
The "block" was to the shoulder, not the back. Honestly, I'm not sure he even touched him, the guy lunged for King and that is why he went down.

King's interception was not a fluke, he had his eyes in the QB and went to the spot he was looking. King plays textbook corner, he is just one in a million talent.

I'm hoping if the Hawks make a nice run this year that we get him to come back by pimping him for the Heisman. Give him some plays on offense. He'd never win, but it would be fun to have him in the conversation.
 
  • Like
Reactions: LGEND24
Nope. I saw that too....it most definitely was a block in the back. I am shocked it wasn't called, especially since there was an official looking right at it.
I don't know if there was more than one instance of a block in the back, or who the player was that did it, but the one I noticed out of the corner of my eye...................... if that particular block was indeed the instance, I think the reason it wasn't called was because King was well out in front at that point, and it really had no effect on the play. If that is the indeed the case, the Ref may have just swallowed the whistle due to the fact it was pretty much meaningless to the eventual outcome.
 
It was a good no-call. The Maryland guy was not much touched, the Iowa guy held-off from really pushing him and actually pulls his hands back, so a good no-call. I hate ticky-tack penalties on returns that wouldn't make a difference in the play, anyway. It looked to me that the Maryland guy may have been losing his balance anyway, whether our guy touched him or not. Still, a nice break not to have had that called. Remember when Colorado won the Orange Bowl (and a share of the NC) when Rocket Ismail returned a kick for a TD at the end of the game, and a block in the back was called like 20 yards behind the play? God, I hate that kind of officiating.
 
  • Like
Reactions: WWDMHawkeye
It was a good no-call. The Maryland guy was not much touched, the Iowa guy held-off from really pushing him and actually pulls his hands back, so a good no-call. I hate ticky-tack penalties on returns that wouldn't make a difference in the play, anyway. It looked to me that the Maryland guy may have been losing his balance anyway, whether our guy touched him or not. Still, a nice break not to have had that called. Remember when Colorado won the Orange Bowl (and a share of the NC) when Rocket Ismail returned a kick for a TD at the end of the game, and a block in the back was called like 20 yards behind the play? God, I hate that kind of officiating.
Yeah well dem's da rules. In Mabin's case, that wasn't even close to block in the back. He got even with him and pushed the side of his shoulder.
 
It was a good no-call. The Maryland guy was not much touched, the Iowa guy held-off from really pushing him and actually pulls his hands back, so a good no-call. I hate ticky-tack penalties on returns that wouldn't make a difference in the play, anyway. It looked to me that the Maryland guy may have been losing his balance anyway, whether our guy touched him or not. Still, a nice break not to have had that called. Remember when Colorado won the Orange Bowl (and a share of the NC) when Rocket Ismail returned a kick for a TD at the end of the game, and a block in the back was called like 20 yards behind the play? God, I hate that kind of officiating.

I agree about ticky-tack calls, and this would have been one, but in that situation it gets called a lot more than not.

As for whether it was a block in the back, it sure looked like one to me in real time although I haven't gone back and looked at slo-mo. Maybe it would have been more apparent that it wasn't a block in the back. That said, if it's close (and it was, at the very least, close), they usually throw the flag -- even if the outcome of the play wasn't directly affected. I'm glad they didn't, obviously.
 
That int. started with the play before it Lomax lit the qb up when. He fumble and outlaw had a huge hit later on that QB
 
  • Like
Reactions: wyldhawk9
I just don't see how his stock could be higher next year. Interceptions are fluky and he might lead the Country. Pretty tough to duplicate that so why would t you go pro?

I obviously hope he stays, but it would be borderline irresponsible to risk injury. If you're a freak athlete teams will overlook a torn ACL, but I don't see that for a guy like King (even as special as he is). It is millions of dollars on the line.

I wish he would stay away from freaking punts he doesnt want to return, but definitely a special special Hawk. All timer..

Whether or not his stock can go higher will have nothing to do with leading the nation in interceptions. I heard he is projected as a third rounder? If so, another year at Iowa could have huge financial benefits if he can get into round 1
 
The refs were letting them play all day. See King getting popped after the fair catch. So it's not surprising it was a no call.
 
Those refs should be fired for missing that block in the back on Mabin. Just atrociously bad. Anyone that thinks it was legal or should have just been ignored is a retard and should never be allowed to watch football ever again.

This was also the same crew that lost track of downs in the Neb/Ill game. Don't think you'll be seeing them in the B1G next year.
 
Last edited:
ADVERTISEMENT
ADVERTISEMENT