Kam PI was BS

[hawksfansinceday1]

..........Just let the players play.... whether you agree or not, its the end of a close playoff game, let the players decide the outcome, and not the refs making a call on something highly ticky tack. It's whats wrong with the NFL right now.

This X1000

 

[HawkGA]

That was a crap call. In that situation, that was B.S.

I don't agree with you on Bevell, but you show a lot of wisdom here! :0190l:

 

[kamikazehawk]

Sometimes fan try to hard NOT to be bias. You are seriously smoking crack if you think that is pass interference. The WR directs his route at the defender and runs directly into him well past the 5 yards from scrimmage. The defender barely moves a muscle. There is no "arm bar" by Kam or any initialized contact. That is offensive PI at the very most. The defender has every right to occupy that space.

This is the same exact situation on Earl Thomas interception in Arizona Week 17 on a throw targeted for Fitzgerald. He directs his route directly at the defender, makes contact and then looks for the penalty. Its a veteran move that can get called incorrectly if the refs arent paying attention but I promise you that is not Defensive PI any day of the week. Claiming otherwise doesn't avoid you being called a homer... just wrong.

 

[HawkGA]

I didn't get to see the game today (had to go sign papers for a house. Grrrrr!). But dispassionately looking at the replay and knowing the outcome, that was not DPI for all the reasons people said. Primarily, the offensive player ran straight into the defensive player. It's not like Chancellor jumped in front of him or that they were running together and Chancellor pushed him.

Another thing, from a Viking perspective, they should be ticked because if he actually runs around Kam instead of through him, he probably makes a big gain as Chancellor would be trailing him, unable to catch up.

 

[Aristotle22]

The receiver ran into him. He was standing in position. Such BS. At least we won.

P

I was wondering about that. From where I was it looked like it could have been OPI.

 

[Seahawk Sailor]

Obvious pass interference

Yes . . . offensive pass interference. :th2thumbs:

That's what I saw. Watched it delayed on NFL.com Game Pass, and saw it fairly well. Offensive pass interference all the way. Hey, I should know what offensive pass interference looks like--saw a lot less flagrant version of it in Super Bowl XL*.

 

[hawknation2015]

ARTICLE 2. PROHIBITED ACTS BY BOTH TEAMS WHILE THE BALL IS IN THE AIR
Acts that are pass interference include, but are not limited to:

Initiating contact with an opponent by shoving or pushing off, thus creating a separation in an attempt to catch a pass.

http://operations.nfl.com/the-rules/201 ... terference

Looked an awful lot like the first example in this video, except Kam also grabbed his arm after Rudolph initiated contact:
http://operations.nfl.com/the-rules/nfl ... erference/

 

[loafoftatupu]

It was a crap call. Kam was not motioning into his body or grabbing him. Rudolph generated the contact and shoved Kam down. The Cards do the exact same thing at least twice a game on Seattle. Fitz was crying about it on Thomas after getting the call in the previous game.

It is not interference to be in a zone and get bumped intentionally by the WR and the shove could have been called OPI. They took that play right out of AZs book.

The Hawks weren't getting anything from the Zebras today. But the refs couldn't control the Peterson fumble and the missed kick.

That has always been the key with the Hawks.. a nice turnover margin makes up for being the team that for two years opposed the least penalized team that week they played the Hawks.

 

[loafoftatupu]

It's just like what Larry fixtgerald tried to do to us except it worked. It's like coincidental pick play. Manufacturing penalties. On the edge of cheating.

Fitz tries it at least once a game since Arians has been coaching. I think Carroll warned the officials and asked for them to look at it because week 17 was the first time it hasn't been called. Damn Arians..

 

[JSeahawks]

Kam put his right arm up to stop him from cutting in front of him. Obvious pass interference. Or defensive holding at least.

 

[hawknation2015]

Kam put his right arm up to stop him from cutting in front of him. Obvious pass interference. Or defensive holding at least.

Yeah, but the contact was initiated by the offensive player slamming into him. Kam only grabbed his arm in response, and then Rudolph shoves him.

If you want to call a penalty on the defender for his interference, then you have to also acknowledge the offensive player's interference, since he was the one who initiated the contact.

 

[Smellyman]

He got beat on a double move, that was pi

I would call that illegal contact, not PI.

Now, the call on Sherman was complete horse shit.

If the ball is in the air it is PI and not illegal contact.

 

[AgentDib]

Could have been called a lot of ways:
70% no call
15% OPI
15% illegal contact
0% DPI

 

[JSeahawks]

Kam put his right arm up to stop him from cutting in front of him. Obvious pass interference. Or defensive holding at least.

Yeah, but the contact was initiated by the offensive player slamming into him. Kam only grabbed his arm in response, and then Rudolph shoves him.

If you want to call a penalty on the defender for his interference, then you have to also acknowledge the offensive player's interference, since he was the one who initiated the contact.

First contact was Kam's outreached arm on the TE's left shoulder as the TE tried to cut underneath him because Kam was caught leaning to the outside on the TE's first move.

 

[hawknation2015]

Kam put his right arm up to stop him from cutting in front of him. Obvious pass interference. Or defensive holding at least.

Yeah, but the contact was initiated by the offensive player slamming into him. Kam only grabbed his arm in response, and then Rudolph shoves him.

If you want to call a penalty on the defender for his interference, then you have to also acknowledge the offensive player's interference, since he was the one who initiated the contact.

First contact was Kam's outreached arm on the TE's left shoulder as the TE tried to cut underneath him because Kam was caught leaning to the outside on the TE's first move.

No, the first contact is Rudolph dipping his shoulder into Kam:

 

[TeamoftheCentury]

Everything I've seen says it shouldn't have been called. Especially the way this game was being called.

It should have been a no call, but Kam wasn't entirely blame free. Had he not reached his right arm across Rudolph's body, it would have been a lot more clear.

All things considered and seeing that a guy like Brian Billick from the outside agreed with Kam, I'm inclined to most agree with the above two quotes + HawkNation2015 showing that Rudolph initiated the contact.

I agree Rudolph had intent to draw the flag. That's gamesmanship. Player's learn to do what works. But, I agree that the way the game was being called, it was unnecessary. Kam bringing his arm up is the reason they called it. But, if the officials saw that Rudolph ran into Kam intentionally initiating the contact, then there's also a case for OPI. So, a "no-call" in that instance would have been the better option.

It's water under the bridge for this game. But, since Fitzgerald tried to pull the same thing, perhaps it's worth Pete bringing it up, getting clarification and also communicating with the officials that this is a tactic that receivers are working. If the offensive player runs right into the defender in his space, seems like that should be illegal contact on the initiating player.

One thing's for certain... it's debatable. :hmmmm:

 

[TwistedHusky]

This team still has not learned.

Crap calls happen.

Guys suddenly get hurt and it changes everything, including your ability to consistently shut down offenses 3-5 possessions in a row. The ball bounces funny. Sh*t happens.

The more you allow a game to stay close? The more you make it possible for Sh*t to Happen to you. So put the game away. Score. (Ask the idiot Bengals that punted when inside their opponent's 38 in a playoff game...not trying to score when you can has the capacity to burn you bad)

Basically, the closer you keep a game - the more you leave it open for external forces to influence the outcome.

If you have a 14 point lead or EVEN JUST STILL HAVE THE BALL, then they cannot just slam into you for penalties.

We were trying to bleed a clock with a 2 yd per carry run attack highlighted by multiple long passes that had no chance of being completed and just killed conversion %.

The entire first half consisted of this team screwing around trying to set the defense up for plays that were not going to work later anyway. There was no reasonable effort to try to mount a scoring drive, and Bevell's incompetence here almost hurt us badly.*

This was followed by one freak play that leads to a possession close enough the RZ for a TD pass. And then a fumble recovery that got us a single FG.

We followed by breaking out "1st Half Bevell", trying to suck a clock down from near 6 minutes to go in the game. A game we might have needed the clock to score in.

Kam's PI wouldn't have come close to almost handing the team the game if we had even put together a reasonable effort to move the ball in the 2nd half. And so it is hard to complain about a call that we never should have been in the position to be upset about.

This team needs the offense to start producing a little bit more than 3 plays per game in the playoffs. And not doing so just puts you in position where a bad call like the one on Kam can swing the game. If you have the lead in the 4th and the other team can still score + win? You have no business not trying to score, because otherwise you are unfairly putting the pressure on your defense to fix your screwups.

 

[Hawkpower]

This team still has not learned.

Crap calls happen.

Guys suddenly get hurt and it changes everything, including your ability to consistently shut down offenses 3-5 possessions in a row. The ball bounces funny. Sh*t happens.

The more you allow a game to stay close? The more you make it possible for Sh*t to Happen to you. So put the game away. Score. (Ask the idiot Bengals that punted when inside their opponent's 38 in a playoff game...not trying to score when you can has the capacity to burn you bad)

Basically, the closer you keep a game - the more you leave it open for external forces to influence the outcome.

If you have a 14 point lead or EVEN JUST STILL HAVE THE BALL, then they cannot just slam into you for penalties.

We were trying to bleed a clock with a 2 yd per carry run attack highlighted by multiple long passes that had no chance of being completed and just killed conversion %.

The entire first half consisted of this team screwing around trying to set the defense up for plays that were not going to work later anyway. There was no reasonable effort to try to mount a scoring drive, and Bevell's incompetence here almost hurt us badly.*

This was followed by one freak play that leads to a possession close enough the RZ for a TD pass. And then a fumble recovery that got us a single FG.

We followed by breaking out "1st Half Bevell", trying to suck a clock down from near 6 minutes to go in the game. A game we might have needed the clock to score in.

Kam's PI wouldn't have come close to almost handing the team the game if we had even put together a reasonable effort to move the ball in the 2nd half. And so it is hard to complain about a call that we never should have been in the position to be upset about.

This team needs the offense to start producing a little bit more than 3 plays per game in the playoffs. And not doing so just puts you in position where a bad call like the one on Kam can swing the game. If you have the lead in the 4th and the other team can still score + win? You have no business not trying to score, because otherwise you are unfairly putting the pressure on your defense to fix your screwups.

Your rant isnt wrong.

But there also is a strong possibility that the -20 windchill and a top 5 defense across the way made it challenging to score.

It seems odd to read this after weeks and weeks of offensive dominance. Did you not watch the last two months of football from Seattle?

 

[nanomoz]

KR didn't even look for the ball.

 

[twisted_steel2]

Kam put his right arm up to stop him from cutting in front of him. Obvious pass interference. Or defensive holding at least.

Yeah, but the contact was initiated by the offensive player slamming into him. Kam only grabbed his arm in response, and then Rudolph shoves him.

If you want to call a penalty on the defender for his interference, then you have to also acknowledge the offensive player's interference, since he was the one who initiated the contact.

First contact was Kam's outreached arm on the TE's left shoulder as the TE tried to cut underneath him because Kam was caught leaning to the outside on the TE's first move.

I keep watching the .gif over and over trying to see your point of view of how it went down. Just can't see it, Kam's right arm goes up to the TE's left shoulder because he's getting knocked down and run over...