Call the FBI, the clock was tampered with.

[LaVarIsDaMan]

Has anyone else noticed this ridicilousness? I didn't catch it until this morning but it seems that we were crucially gipped (jipped? whatever, it's early). If anyone has this recorded, start to watch closely after Brunell makes that long completion to get us in field goal range.

A play or two after the spiked ball-delay of game sequence, we take a shot at the end zone and Carl "Clutch" Berman pulls Randall Gay down for the horrible offensive pass interference. Now, if you take a look at the video the clock stops for a moment, then instantly :11 seconds dissapear, turning 0:28 left on the game clock to 0:17 seconds. Not only that but once the seconds are shaven off, the clock starts running which is instantly pointed out by Joe Gibbs and Rock Cartwright. The clock eventually stops at 0:11 seconds left. The official "corrects" the game clock to 0:17 seconds.

Now, it IS early, but it seems we may have been slighted, even though we were playing on our home field. And it can NOT be the rule of the 10 second run-off when offense is trailing with no time-outs, because that rule only pertains to illegal motion penalties such as off-side or illegal procedure ETC. If it were a rule that required the 10 second run-off, (which I'm almost sure it's not) the official never announced it. My opinion is no one caught the 0:10-0:11 seconds instantly shaven off, and looked at the clock when it started to count down from 0:17 seconds.


Someone prove me wrong because I am pissed and groggy.

[Drunken Master III]

I noticed the same thing. We definitely got ripped off.

[jnhay]

I thought we had more time, even when they put more time on the clock.

[RedskinsNation]

If we had run the ball once after the long completion down the middle of the field we would have been in FG range...granted long FG range but still makeable. We then spike the ball and kick and take our chances. Instead we couldnt get a playoff, then commit a penalty...it was over at that point. It was pre-season so I actually laughed at that goof of a series.

Would have been nice to see Suisham "try" to make that long FG to win the game.

[LaVarIsDaMan]

But if this clock issue doesn't happen, we have the ball on 2nd and long with 0:27 seconds left to go in the game, in Steeler territory. You can't fault the coaches who didn't immediatly think long field goal with Suisham, with :30 plus seconds left in the game. We apparently lost 10 seconds of game clock, which is a lot of time in this situation.

[roqnap1]

1) It's preseason

2) Brunell would have ****ed it up regardless...

[WSHRedskins3ATLBraves3]

We always get ripped off with the clock. It happens ALL THE TIME.

One more thing, whenever the giants or cowpukes have 0 on the play clock and they snap it, there is never delay of game called. I can't stand it.

[skns4life]

Yeah I definately noticed that! I was screaming at the top of my lungs at the refs...When I looked up at the clock, there were 18 seconds left and the clock kept running. The play had already ended like a good 8-10 seconds before that...So when they reset the clock to 17 seconds, I lost my voice! :doh:

[LaVarIsDaMan]

1) It's preseason

2) Brunell would have ****ed it up regardless...

1. Preaseason or not, you don't feel in the slightest way cheated? Especially since our head coach has put emphasis on winning these preseason games..

2. I don't know who you saw on that last drive, but give credit where it's due. Brunell was leading a fine drive.

P.S. In one of his media interviews, I heard Joe Gibbs say something to the nature of that delay of game penalty was the coaching staff's communication problem.

[jnhay]

2. I don't know who you saw on that last drive, but give credit where it's due.
You know that will never happen.

[RFK Lives]

Don't officials still keep time on the field? I am not sure but I thought they still carried a digital stopwatch for timing timeouts etc.

[LaVarIsDaMan]

You know that will never happen.

I know. It's sort of sad actually. As a fan base, we have almost completed the mission of getting him off the Redskin's roster, and probably the NFL. Granted, he didn't help himself much but almost every problem came back to his "weak arm" or "his anemic offense".

P.S. I was definitely a hater in the past. First step is denial. :doh:

[Tulane Skins Fan]

Was Tim Donaghy the clock official for that game?

[tizzod]

I think Gibbs would have mentioned something about this in his presser had it actually occurred. Calm down, everybody.

[corsair_joe]

isn't there a runoff for penalties against the offense inside of 2:00?

[LaVarIsDaMan]

I think Gibbs would have mentioned something about this in his presser had it actually occurred. Calm down, everybody.

uh. is it possible he missed it, much like 99% of the board? maybe you should check it out, and decide for yourself.

[jrfriedm]

Taylor 36 and I were screaming the about the same thing.

[LaVarIsDaMan]

isn't there a runoff for penalties against the offense inside of 2:00?

yes, but as mentioned in the original post, it seems that the run-off only is enforced on illegal movements before the ball is snapped, on the offensive team with no timeouts remaining. such as an illegal procedure or a false start, which would give the offense essentially another timeout, (without the run-off being enforced) and no loss of down if abused.

[Dan T.]

Here's an explanation of the 10-second runoff rule from former NFL referee Jerry Markbreit. He's got a regular column in the Chicago Tribune, and it came up because of a play in a Bears-Saints game a couple years back:

Jerry, I enjoy reading your weekly column. I'm sure the bulk of your e-mails will be regarding this issue, so can you explain what happened at the end of the first half of the Bears-Saints game. Also, if the 10-second runoff was not applicable on this play, when exactly is it used? -- Mike Berkowitz, Marquette, Mich.

I hope my answer to the question above answers your question. The 10-second runoff rule has two parts:

(1) After the two-minute warning of either half, while time is in, if the score is tied, or the team in possession is behind in the score and the offensive team has exhausted its legal timeouts, an additional timeout may be requested and granted for an injury. However, the ball shall not be put in play until the time on the clock has been reduced by ten seconds.

(2) During the last minute of either half and with the clock running, any foul by the offense for false start, illegal shift or illegal motion without the offensive team coming to a complete stop will have a ten-second runoff.

Link: http://chicagosports.chicagotribune.com/sports/football/bears/askthereferee/cs-031015markbreitanswers,1,2376672.story?coll=cs-bears-asktheref-utility

[LaVarIsDaMan]

Here's an explanation of the 10-second runoff rule from former NFL referee Jerry Markbreit. He's got a regular column in the Chicago Tribune, and it came up because of a play in a Bears-Saints game a couple years back:

Jerry, I enjoy reading your weekly column. I'm sure the bulk of your e-mails will be regarding this issue, so can you explain what happened at the end of the first half of the Bears-Saints game. Also, if the 10-second runoff was not applicable on this play, when exactly is it used? -- Mike Berkowitz, Marquette, Mich.

I hope my answer to the question above answers your question. The 10-second runoff rule has two parts:

(1) After the two-minute warning of either half, while time is in, if the score is tied, or the team in possession is behind in the score and the offensive team has exhausted its legal timeouts, an additional timeout may be requested and granted for an injury. However, the ball shall not be put in play until the time on the clock has been reduced by ten seconds.

(2) During the last minute of either half and with the clock running, any foul by the offense for false start, illegal shift or illegal motion without the offensive team coming to a complete stop will have a ten-second runoff.

Link: http://chicagosports.chicagotribune.com/sports/football/bears/askthereferee/cs-031015markbreitanswers,1,2376672.story?coll=cs-bears-asktheref-utility

perfect explanation, thank you. it's official, the timekeeper at fed-ex screwed us out of a potential win.

[twenty-eight]

Well I dont mind getting ****ed over in the preseason. Now if this happens in the regular season :cuss:

[ouvan59]

I noticed the same thing. We definitely got ripped off.

I'm not sure we did. I noticed it when the clock was still running after the interference call and was hopping mad but then I ran it back and the clock was late starting from the previous play so the 0:17 may have been correct.

[LaVarIsDaMan]

I'm not sure we did. I noticed it when the clock was still running after the interference call and was hopping mad but then I ran it back and the clock was late starting from the previous play so the 0:17 may have been correct.

the clock started late on which play?

[jrfriedm]

perfect explanation, thank you. it's official, the timekeeper at fed-ex screwed us out of a potential win.
The sad thing is that this was a home team clock keeper. If we can't get any help from our own statidum people, how the heck are we going to get any help from anywhere else.

[LaVarIsDaMan]

The sad thing is that this was a home team clock keeper. If we can't get any help from our own statidum people, how the heck are we going to get any help from anywhere else.

the even sadder thing is we won't get help from anywhere else.

[Taylor 36]

I think Gibbs would have mentioned something about this in his presser had it actually occurred. Calm down, everybody. You're right, because Gibbs wants to start off the season with officials already pissed off at him and the team.

[mrhetzler]

One more thing, whenever the giants or cowpukes have 0 on the play clock and they snap it, there is never delay of game called. I can't stand it.

You are so right. I just EXPECT a non-call anymore.

[InsaneBoost]

1) It's preseason

2) Brunell would have ****ed it up regardless...


1) It is preseason, but if nothing is done now, it could happen later on in the season.

2) I thought Brunell did a pretty damn good job, if it wasn't for the guy who was called with the false start, we probably wouldn't have gotten out of our rhythm.

[Real Deal]

Was Tim Donaghy the clock official for that game?:rotflmao:

[[[ghost]]]

Either way, let the Refs get their shots in during pre season, before they job us during the season.

[Chachie]

Better yet, if you check the clock now, it'll show you that the game is in the past. Leave it there and look to saturday the 25th. ;)

[AJWatson3]

my sister actually pointed that out while we were at the game... i didn't notice.

and as bad as the game ended it was pre-season. if that **** would've counted i'd be furious.

[ouvan59]

the clock started late on which play?

The offensive pass interference. It sat on 0:29 for about 3 or 4 seconds after the snap.

[LadderCrew17]

No truth to the rumor that this man was the clock operator...

[roqnap1]

2. I don't know who you saw on that last drive, but give credit where it's due. Brunell was leading a fine drive.

I'm all for giving credit where credit is due, but Brunell's passes sucked. He was consistantly off target. The receivers made that drive, not him. His inaccuarcy caused the tip that caused the INT.

Oh....and if you're going to ask people to give credit where credit is DUE...change your screen name. Lavar is due ZERO credit... :laugh:

[Butz65]

My guess is that Gibbs told the official to make sure and drop the 10 seconds off so he could get the team off of the field without any more injuries.......

[ncr2h]

I'm all for giving credit where credit is due, but Brunell's passes sucked. He was consistantly off target. The receivers made that drive, not him. His inaccuarcy caused the tip that caused the INT.

Oh....and if you're going to ask people to give credit where credit is DUE...change your screen name. Lavar is due ZERO credit... :laugh:

Log off, dude. You know NOTHING. The receiver's made that drive? Which receiver...the one that pulled the DB down for a 15 yard penalty? Or was it the one who couldn't keep his feet in bounds? Oh wait...I know! It was the one who tipped the ball right to the other team!

EDIT: On second thought...maybe it was the one who tripped over his own feet?

[dizzinator53]

thought I was dreaming... the second poorly officiated game I have seen this preseason.... I have only really watched two full games.

[dizzinator53]

I think our third team sucked all the way around on "O" Both of you are right and wrong.

[roqnap1]

Log off, dude. You know NOTHING. The receiver's made that drive? Which receiver...the one that pulled the DB down for a 15 yard penalty? Or was it the one who couldn't keep his feet in bounds? Oh wait...I know! It was the one who tipped the ball right to the other team!

EDIT: On second thought...maybe it was the one who tripped over his own feet?

Dude, seriously, you are so wrong. LOOK! (http://www.nfl.com/videos?videoId=09000d5d8019740d)

The pass was a classic Brunell P.O.S. The receiver tipped it after having to stretch out as far as he could to try to catch a pass that is off the mark. If the ball isn't tipped and picked by Gay (22), it's past them both and picked by Mason (41).

Done and done.

[ncr2h]

Dude, seriously, you are so wrong. LOOK! (http://www.nfl.com/videos?videoId=09000d5d8019740d)

The pass was a classic Brunell P.O.S. The receiver tipped it after having to stretch out as far as he could to try to catch a pass that is off the mark. If the ball isn't tipped and picked by Gay (22), it's past them both and picked by Mason (41).

Done and done.

I don't know how to reply, other than by saying you're wrong.

[zskins]

1) It's preseason

2) Brunell would have ****ed it up regardless...

:applause: :applause: :applause:

[mcarey032]

I think last year there was some funny business that went on during a pittsburgh game. There was like two minutes shaved off the clock or something. You would think that if it was at home, the clock situation would benefit us? I have to say that I didn't notice anything that wasn't Kosher.

[ChampSkinsFanatic]

I was at the game, they fixed the clock when the mistake happened. Unless it happened differently on tv

[nace14]

first of all, berman's feet got tangled and he fell forward into the cb, it wasn't a horrendous play, just a tough break.
second of all, if anyone messed with the clock, it was probably us hoping to end the game before any more injuries.
third of all, less filling.
fourth of all, who cares, it's preseason.

[roqnap1]

I don't know how to reply, other than by saying you're wrong.

You obviously didn't look at the link...but it's cool. I'm lazy too, sometimes.

[goldbean]

I certainly am not going to debate whether the last pick was Brunell's fault or the receiver's. All I'll say is that the pass was super smart. People can draw their own conclusions.


I don't know how to reply, other than by saying you're wrong.

[TeddyKGB]

Anyone else also notice that a phantom PI call in the end of the first half stopped the clock for the steelers(which at that point they couldn't of done on their own) at like 00:02. Letting them kick the first FG. In my mind it should of been 7-0 at half. They called PI , stopped the clock, then said "oh wait nevermind" and took the flag back. Which at that point Steelers had no more TO's . I'd go nuts if that happened in a real game.

[nace14]

Anyone else also notice that a phantom PI call in the end of the first half stopped the clock for the steelers(which at that point they couldn't of done on their own) at like 00:02. Letting them kick the first FG. In my mind it should of been 7-0 at half. They called PI , stopped the clock, then said "oh wait nevermind" and took the flag back. Which at that point Steelers had no more TO's . I'd go nuts if that happened in a real game.

it didn't matter, it would have been stopped on the incomplete pass regardless of the PI call.

[CM916]

After those penalties, we weren't going to win it anyway, especially when Brunell felt forced to throw it over the middle with no time left to set up the FG even if it didn't get tipped.

[mrdoctor]

I noticed the same thing. We definitely got ripped off.

yea man if you were in my section you would of heard me

[burgngold fan]

I'm all for giving credit where credit is due, but Brunell's passes sucked. He was consistantly off target. The receivers made that drive, not him. His inaccuarcy caused the tip that caused the INT.

Oh....and if you're going to ask people to give credit where credit is DUE...change your screen name. Lavar is due ZERO credit... :laugh:
finally someone who noticed the same thing as i did. not only that but a veteran qb should have been able to make that play after the interference call. he had a wide open reciever on the side lines in which the player made a heck of a catch but MB pass was high and carried the player out of bounds. an accurate throw and the skins would have been able to attempt a field goal anyway.

and not let us forget that MB started the 4th quarter and proceeded to go 3 and out every time until that last drive. all these MB supporters can say what they want but one long pass is not enough to make me feel confident that he can consistantly lead this team. a vet. qb with his experience should have been able to do a whole lot more in the 4th quarter of a pre-season game.

i know i am about to get ripped for this post. but what the heck. he still has done nothing to gain my trust.

[burgngold fan]

Log off, dude. You know NOTHING. The receiver's made that drive? Which receiver...the one that pulled the DB down for a 15 yard penalty? Or was it the one who couldn't keep his feet in bounds? Oh wait...I know! It was the one who tipped the ball right to the other team!

EDIT: On second thought...maybe it was the one who tripped over his own feet?
you got to be kidding me! the one who could not keep his feet in bounds. you are blaming the reciever? he did a heck of a job to to get his hands on the ball. much less catch it. the ball was off target he had no chance to catch it in bounds.

the only credit i could give brunell on that pass was he did rifle it in there just a little high. (i did not think MB could muster that much heat any more)

[burgngold fan]

You obviously didn't look at the link...but it's cool. I'm lazy too, sometimes.
yea! that's funny. some poeple just see what they want.

[Zazzaro703]

I def noticed it. The clock was at 14secs i think and they added back what 3 seconds. I was def telling my dad the clock was around 28 secs then someone slipped down to about 14secs.

[ouvan59]

I def noticed it. The clock was at 14secs i think and they added back what 3 seconds. I was def telling my dad the clock was around 28 secs then someone slipped down to about 14secs.

I just went back and rewatched that play. The play started with 0:29 seconds left and the clock didn't even start until after the play was over and then ran down to 0:13. I counted about 7 or 8 seconds should have run off so it should have been reset to 0:21 or 0:22. Not sure how they ended up at 0:17.

[ouvan59]

Anyone else also notice that a phantom PI call in the end of the first half stopped the clock for the steelers(which at that point they couldn't of done on their own) at like 00:02. Letting them kick the first FG. In my mind it should of been 7-0 at half. They called PI , stopped the clock, then said "oh wait nevermind" and took the flag back. Which at that point Steelers had no more TO's . I'd go nuts if that happened in a real game.

It was an incomplete pass so it would have been stopped anyway. No effect on the game.

[Bacon]

Whatever. We hung in that game until the bitter end and our receivers blew it. It's the preseason anyway, so a loss isn't a big deal. The important thing is that we played well, and hopefully don't make the same mistakes next week.

[Peregrine]

Yeah, noticed it. I dont understand how, as a ref, you can be so stupid as to not notice that a short play took 12 seconds(what they eventually "corrected" it to). Further, arent they supposed to get the booth to check how much time they are supposed to have left? Obviously they didnt have a clue what it was. Fantastic job there.