![]() |
Big List of Bad SB Calls
Here's a nice list for everyone to debate:
1st Quarter 2:00 Offensive pass interference against Darrell Jackson negates touchdown. Contact is incidental. Television commentator John Madden observes that “when you think of a push-off, that's not the kind you think about, really [in terms of calling a penalty].” Commentator Michael Irvin observes during the halftime review that the penalty was a “ticky-tack foul.” Commentator Steve Young observes that Darrell Jackson’s catch was “a touchdown. That was an absolute touchdown.” Steelers defensive back Chris Hope can be seen grabbing Darrell Jackson’s left arm just prior to the pass. Seahawks are forced to go for the field goal. Loss of four points for the Seahawks. 2nd Quarter 14:44 Etric Pruitt called for holding on 35 yard punt return by Peter Warrick. Change of field position from Steelers 46 yard line to Seahawks 25 yard line. This represents a difference of 29 yards. On the replay Pruitt can be seen making a clean block on Steelers player Tyrone Carter during the return. 8:34 Mack Strong reception to the 33 yard line spotted short of the 33 yard line, negating first down yardage on the 3rd down play. Video evidence clearly shows the ball coming down on the yellow television first down line at the 33 yard line. Mack Strong is shorted about two feet on the spot. 8:15 Antwaan Randel-El fumbles punt return but the play is whistled dead. The fumble was recovered by the Seahawks. 1:55 Ben Roethlisberger does not score on the 3rd down run. The official can be seen signaling 4th down and preparing to spot the ball short of the goal line until Ben Roethlisberger moves the ball across the goal line after the play was over. The official can be seen changing his mind at this point, and raising both arms to signal touchdown in response to this dead ball movement by Roethlisberger. He tells David Letterman on the February 6th CBS Late Show that he did not get in. The play is ruled a touchdown and is upheld on review. 1:47 Holding call against Seahawks linebacker Kevin Bentley on kickoff return. The replay does not show Bently holding the Steelers player. Instead of starting their drive at the 38 yard line, the Seahawks are moved back to the 27 yard line, a loss of 11 yards. 0:48 Darrell Jackson touchdown reception ruled incomplete. Video evidence shows Jackson’s left foot in bounds, while his right foot kicks over the pylon. A 2002 rule change says that this is a touchdown. Here is the rule: “A player will be ruled in bounds if he touches the pylon at the goal line before going out of bounds. For example, a pass would be considered complete if one foot touches the pylon and the other foot is in bounds.” The game clock was under two minutes to go in the half and the officials did not review the play. This represents a loss of seven points for the Seahawks. 3rd Quarter 14:45 Steelers tight end Heath Miller holds Seahawks defensive end Bryce Fisher, preventing him from getting to Steelers running back Willie Parker who scored a touchdown on the play. No holding penalty was called. 9:51 Steelers receiver Hines Ward pushes off Seahawks defensive back Kelly Herndon with a blatant stiff arm to the face mask of Herndon on a 3rd and 4 play. No penalty is called. Ward catches the pass and gains 16 yards to convert a 1st down on the play. If Seahawks receiver Darrell Jackson was called in the first quarter for pushing off when he barely touched the defender, why then is Hines Ward not called for pushing off in this instance when his violation was far more flagrant? 6:51 Steelers defensive backs Deshea Townsend and Troy Polomalu both hold Seahawks tight end Jerramy Stevens running a post route. Commentator John Madden observes during the replay that “Stevens got held up…getting held is what happened.” Neither obvious hold was flagged. 4th Quarter 12:24 Holding called against Seahawks right tackle Sean Locklear on Clark Hagans of the Steelers negates an 18-yard catch by Jerramy Stevens to the Steelers one yard line. During the replay, commentator John Madden observes “ooh, I didn’t see holding!...Sean Locklear wasn’t really bad on that play.” Also, the replay of this play clearly shows that Hagans was offsides to begin with. He was across the line of scrimmage prior to the ball being snapped. No penalty was called on Hagans. Matt Hasselbeck is subsequently intercepted a few plays later. This chain of events likely represents a loss of a Seahawks go-ahead touchdown to make the score 17-14. 11:24 Obvious horse collar tackle on Shaun Alexander by Joey Porter not called on 2nd down run. The 15-yard penalty would have resulted in a 3rd and approximately one at the Steelers 11 yard line, instead of a 3rd and 18 at the Steelers 26 yard line. Commentator Al Michaels understatedly observes that Porter’s tackle was “close to a horse collar, but no call.” 10:46 Matt Hasselbeck inexplicably flagged for “blocking below the waist” while making a tackle on Steelers defensive back Ike Taylor during the interception run back. This adds 15 yards to the end of the run, moving the ball from the 29 yard line to the 44 yard line, which in turn perfectly set up the Steelers for their trick pass play. Instead of the score likely being 17-14 in favor of the Seahawks, it is 21-10 in favor of the Steelers – a change in fortune directly attributable to the biased officiating, beginning with the phantom holding call on Sean Locklear and lack of offsides on Clark Hagans. 4:45 Play clock runs out while Steelers offense is at the line of scrimmage. Ben Roethlisberger calls time out after the play clock runs down to zero. The officials give the time out to the Steelers and do not call a delay of game penalty. Instead of 3rd and 11, it remains 3rd and 6, and the Steelers convert the 1st down by one yard on the ensuing play. |
Re: Big List of Bad SB Calls
Just an absolute awsome job with that Redrock, AWSOME!!!!!!!!!!!!!!1 :headbange
|
Re: Big List of Bad SB Calls
[QUOTE=offiss]Just an absolute awsome job with that Redrock, AWSOME!!!!!!!!!!!!!!1 :headbange[/QUOTE]
Sorry it came from a Seattle board here and I forgot to cite it: [url]http://seattlepi.nwsource.com/forum/boards/viewtopic.asp?topicid=79641[/url] Don't want any credit for it. I just loved the list and the explanations. Even I forgot a lot of those non-calls. |
Re: Big List of Bad SB Calls
Holy crap, the hawks really got shafted.
|
Re: Big List of Bad SB Calls
who cares, its over and they're not changing the score.
[quote]1:55 Ben Roethlisberger does not score on the 3rd down run. The official can be seen signaling 4th down and preparing to spot the ball short of the goal line until Ben Roethlisberger moves the ball across the goal line after the play was over. The official can be seen changing his mind at this point, and raising both arms to signal touchdown in response to this dead ball movement by Roethlisberger. He tells David Letterman on the February 6th CBS Late Show that he did not get in. The play is ruled a touchdown and is upheld on review.[/quote] this one is just wrong, someone here posted the pic that clearly showed ben getting in before being down. |
Re: Big List of Bad SB Calls
They do fail to mention, regarding the 0 sec time out, that on two separate occasions the Seahawks snapped the ball with apparently 0 seconds left on the play clock. I believe the announcers pointed out later that there is a delay in calling delay of game because the official responsible has to watch the clock then look for the snap, or something like that. Still a bad call, but that adds two more instances of bad calls in the game if you count them.
|
Re: Big List of Bad SB Calls
My philosophy is...who freakin' cares? It was the Seattle Seahawks! Not the Washington Redskins.
|
Re: Big List of Bad SB Calls
Here's why to care -- keep ignoring it when it's another team and it could happen to you.
|
Re: Big List of Bad SB Calls
tell the seahawks ppl there's a difference b/t a bad call and one not going your way. i think at least 5 of those are just bs. i did not think randle el fumbled. and the TD where his foot hit the pylon; i may have seen wrong, but he was o u t OUT. there were some iffy calls but come on...
if those calls went the way the seahawks board proposed then you'd see the exact same list on [url]www.thesteelerspath.net[/url]... |
Re: Big List of Bad SB Calls
So by their records every call against them was a bad call. Maybe thy should look at the droped passes missed FG and not scoring when they should of. I will agree there where some bad calls but not all of those where bad calls.
|
Re: Big List of Bad SB Calls
Every play could have a penalty called, some are more obvious than others.
"The refs screwed us" is the cry of the loser. The Steelers played as bad as they could have and Seattle still could'nt beat them because they played even worse. The game over and its time for seattle to move on. |
Re: Big List of Bad SB Calls
[QUOTE=Daseal]Here's why to care -- keep ignoring it when it's another team and it could happen to you.[/QUOTE]
Washington has been getting the sh-t end of the stick on calls ever since Snyder became the owner of the team. It was only this year that I noticed more calls going their way, which probably has something to do with Gibbs pestering the hell out of the NFL review board when they get them wrong. As far as the Super Bowl goes, I did feel that the game seemed a little bit skewed towards the Steelers, but the only call the was completely wrong the call on Hasselbecks "low block". All the others can be argued either way. Pulling up all the "bad calls" from a thread on the Seattle board doesn't really hold any weight, since the views of the writer are obviously biased. |
Re: Big List of Bad SB Calls
[QUOTE=Southpaw]Washington has been getting the sh-t end of the stick on calls ever since Snyder became the owner of the team. It was only this year that I noticed more calls going their way, which probably has something to do with Gibbs pestering the hell out of the NFL review board when they get them wrong.
As far as the Super Bowl goes, I did feel that the game seemed a little bit skewed towards the Steelers, but the only call the was completely wrong the call on Hasselbecks "low block". All the others can be argued either way. Pulling up all the "bad calls" from a thread on the Seattle board doesn't really hold any weight, since the views of the writer are obviously biased.[/QUOTE]I just don't buy into the idea that Snyder has anything to do with how a game is called. So what your saying is that the REf's 1 either don't like Snyder (I don't realy see that) or 2 the NFL tells the REFs that they don't want Snyders team to when so call more penalties on the Skins (again that does not make alot of sense). As I've said before that players and coaches make mistakes and so do the REFs. Don't you think that those REFs were as nerves as the players and coaches being on the biggest stage in sports. Its going to happen. |
Re: Big List of Bad SB Calls
[QUOTE=Southpaw]Washington has been getting the sh-t end of the stick on calls ever since Snyder became the owner of the team. It was only this year that I noticed more calls going their way, which probably has something to do with Gibbs pestering the hell out of the NFL review board when they get them wrong.
As far as the Super Bowl goes, I did feel that the game seemed a little bit skewed towards the Steelers, but the only call the was completely wrong the call on Hasselbecks "low block". All the others can be argued either way. Pulling up all the "bad calls" from a thread on the Seattle board doesn't really hold any weight, since the views of the writer are obviously biased.[/QUOTE] Exactly there are a ton of penalties in the NFL that could easily go one way or the other. There were plenty of iffy calls, but the only one that we know was 100% wrong is the low block on Hasselbeck. Everything else can be disputed. The holding call that brought the play back from the 1 could have been on another player, it wouldn't have been the first time a ref got a number wrong. Roethlisberger was in, D Jack pushed off, D Jack was out on their so called TD, and Randle El was way down. That list is ridiculous. |
Re: Big List of Bad SB Calls
[QUOTE=firstdown]I just don't buy into the idea that Snyder has anything to do with how a game is called. So what your saying is that the REf's 1 either don't like Snyder...[/QUOTE]
well he was one of two owners to vote no on ref raises or something like that a couple years back ;) I think its closer to the NBA though, the winners get the benefit of the doubt, and the skins have been losers for a long time. It happened with the wizards last year too. |
Re: Big List of Bad SB Calls
Banging your head against the wall, let's agree to disagree.badly officated game and post season.
|
Re: Big List of Bad SB Calls
what about the non fumble by stevens that went seattle's way or the pass interference call on Miller before the pass was thrown(which I thought meant there couldn't be a PI call but maybe an illegal contact or something). both teams had bad calls go against them, not as many as some r making them out to be and not as blatant, but let it go cuz all of this talk of a fix is absolutely delusional. it's over and done, but hopefully there is a silver lining because of this and the officiating throughout the playoffs hopefully some long needed tweaks and changes will finally occur.
|
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]My philosophy is...who freakin' cares? It was the Seattle Seahawks! Not the Washington Redskins.[/QUOTE]
It's a sense of fairness...thats why we care it could have easily been the skins...hell it happened to the skins all year... |
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]My philosophy is...who freakin' cares? It was the Seattle Seahawks! Not the Washington Redskins.[/QUOTE]
Had we made it to the Superbowl, I can't see us getting any better treatment against the Steelers. Skins aside, I just want to see a champ crowned, but not by using Vince McMahon's "special guest referee". The only thing missing from this game were the teams that lost to Seattle (including ours) to run onto the field whe Seattle tries to score and create outside interference folding chairs and all. |
Re: Big List of Bad SB Calls
I have to feel that if there wasn't money being placed on the Super Bowl from some of you guys, we wouldn't have duplicate threads whining about the Super Bowl. If it was Dallas getting "screwed" out of the Super Bowl championship, there would be no issue.
|
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]I have to feel that if there wasn't money being placed on the Super Bowl from some of you guys, we wouldn't have duplicate threads whining about the Super Bowl. If it was Dallas getting "screwed" out of the Super Bowl championship, there would be no issue.[/QUOTE]I bet on the Stealers so I loved the calls even the bad ones. Go REF's.
|
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]I have to feel that if there wasn't money being placed on the Super Bowl from some of you guys, we wouldn't have duplicate threads whining about the Super Bowl. If it was Dallas getting "screwed" out of the Super Bowl championship, there would be no issue.[/QUOTE]
I'd probably laugh at the Cowboys if it happened to them. If I am laughing, that means I know they were robbed too. |
Re: Big List of Bad SB Calls
It' SO trendy to bitch about the officials...........this is nothing new, remember alsnot?
|
Re: Big List of Bad SB Calls
[QUOTE=That Guy]who cares, its over and they're not changing the score.
this one is just wrong, someone here posted the pic that clearly showed ben getting in before being down.[/QUOTE] i thought that picture showed that ben clearly DID NOT score. it looks like his right arm is not fully across the goal line, since he has the ball in his right arm there is no way the ball crossed if his arm didn't. |
Re: Big List of Bad SB Calls
Who cares????
|
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]Who cares????[/QUOTE]
lots of people. |
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]Who cares????[/QUOTE]
evidently a lot of non seahawk fans :confused: |
Re: Big List of Bad SB Calls
[QUOTE=skinsfanthru&thru]evidently a lot of non seahawk fans :confused:[/QUOTE]
Yeah, weird! :confused- |
Re: Big List of Bad SB Calls
[QUOTE=skinsfanthru&thru]evidently a lot of non seahawk fans :confused:[/QUOTE]
Exactly what I'm thinking. Here's what I feel is the bottom line. Bad officiating or not, and we've said this all year: DON'T PUT YOURSELF IN THE POSITION TO LOSE THE GAME. If your team is not dominant enough to win with ref problems, then you don't deserve to win. Yes, it has been happening to the Skins all year, it's been happening around the LEAGUE all year. But you know what? Good teams win, average teams lose. |
Re: Big List of Bad SB Calls
And I mean try not missing field goals, try NOT dropping balls.
Hagans was actually not offsides on the play they said he was. Remember, if you're looking for bias, you're going to get it from a Seahawks fan board. They should be worried about the 6 KEY FAs they might lose. |
Re: Big List of Bad SB Calls
[QUOTE=wolfeskins]i thought that picture showed that ben clearly DID NOT score. it looks like his right arm is not fully across the goal line, since he has the ball in his right arm there is no way the ball crossed if his arm didn't.[/QUOTE]
This call was basically the anti-Alstott call. Based on physics alone Alstott's arm could not have been in, even though no one could clearly see the ball. Based on PHYSICS ALONE, Ben's arm with the football SHOULD have been in even though no one could clearly see the ball. The correct call was made because touchdown was the call on the field and there was not enough evidence to overturn it. |
Re: Big List of Bad SB Calls
[QUOTE=TheMalcolmConnection]This call was basically the anti-Alstott call. Based on physics alone Alstott's arm could not have been in, even though no one could clearly see the ball. Based on PHYSICS ALONE, Ben's arm with the football SHOULD have been in even though no one could clearly see the ball.
The correct call was made because touchdown was the call on the field and there was not enough evidence to overturn it.[/QUOTE] Personally I thought he was in, but my contention is that the play was I believe ruled inconclusive [don't remember] but when the line judge making the determination of whether or not he was in, he ran in pointing to the ground to spot the ball, then once he gets close to Ben when Ben was clearly on the ground behind the line he watches Ben reach forward and stretch the ball across the line, he then rules a TD, how do you make that switch when your first inclination is that he didn't get in? You then wait until he's down and pushed behind the line to call a TD? I believe he got the call right, but had the wrong intentions. You have a clear view of that play, rule it down outside the goal line, to only then deciede after you get to your spot rule that it's a TD, sorry I ain't buying it! |
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]Who cares????[/QUOTE]Fans of competitive football, like myself.
|
Re: Big List of Bad SB Calls
[QUOTE=skindogger47]Fans of competitive football, like myself.[/QUOTE]
Oh pleeassee...you wouldn't be making a case if it was Dallas being the "victims." |
Re: Big List of Bad SB Calls
Why are we even making a case because it was Seattle as the "victim"? And if I could make those " " marks about a 72 pt. font, I would.
|
Re: Big List of Bad SB Calls
[QUOTE=skinsguy]Oh pleeassee...you wouldn't be making a case if it was Dallas being the "victims."[/QUOTE]
to me, it doesn't matter who was playing. the officiating was just very bad and seemed to be one sided. i just don't like to see the refs determine the winner and loser of a game, in any sport. i feel that they definately determined the outcome of the superbowl. you may disagree with me and thats fine but thats just the way i feel about it. |
Re: Big List of Bad SB Calls
[QUOTE=offiss]Personally I thought he was in, but my contention is that the play was I believe ruled inconclusive [don't remember] but when the line judge making the determination of whether or not he was in, he ran in pointing to the ground to spot the ball, then once he gets close to Ben when Ben was clearly on the ground behind the line he watches Ben reach forward and stretch the ball across the line, he then rules a TD, how do you make that switch when your first inclination is that he didn't get in? You then wait until he's down and pushed behind the line to call a TD? I believe he got the call right, but had the wrong intentions. You have a clear view of that play, rule it down outside the goal line, to only then deciede after you get to your spot rule that it's a TD, sorry I ain't buying it![/QUOTE]
thats exactly how i feel about it. i'm not so upset about the replay not overturning the call on the field, i'm more upset in the way the line judge handled it. OFFISS did a perfect job of describing it. |
Re: Big List of Bad SB Calls
I could care less about either of those teams but if you couldn't see that Seattle was getting screwed all night long then you weren't watching the same game as me.
|
Re: Big List of Bad SB Calls
if seattle makes the field goals,and stephens catches a couple of balls,and hassleback manages the end of half clock better,no matter how bad the officiating was,seattle did not do enough to deserve to win
|
Re: Big List of Bad SB Calls
[QUOTE=dmek25]if seattle makes the field goals,and stephens catches a couple of balls,and hassleback manages the end of half clock better,no matter how bad the officiating was,seattle did not do enough to deserve to win[/QUOTE]
well since you want to play the IF game.... if you have good officiating, seattle did more than enough to win. they kinda go hand in hand. |
| All times are GMT -4. The time now is 02:40 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
We have no official affiliation with the Washington Commanders or the NFL.