ChiefsPlanet

ChiefsPlanet (https://www.chiefsplanet.com/BB/index.php)
-   Nzoner's Game Room (https://www.chiefsplanet.com/BB/forumdisplay.php?f=1)
-   -   Chiefs I've never seen a delay of game penalty that shouldn't have been called (https://www.chiefsplanet.com/BB/showthread.php?t=335478)

DaFace 12-06-2020 10:23 PM

I've never seen a delay of game penalty that shouldn't have been called
 
I mean...WTF was that?

TLO 12-06-2020 10:24 PM

Very odd. Butker comes through in the clutch though.

pugsnotdrugs19 12-06-2020 10:24 PM

Yeah that was weird AF.

Normally they won’t call it for even an extra second after it hits zero.

mlyonsd 12-06-2020 10:24 PM

Yeah that was BS

RealSNR 12-06-2020 10:25 PM

What's this ref's name again?

I want to remember it so I can curse him loudly all night the next time he does a game of ours

petegz28 12-06-2020 10:25 PM

Clock is supposed to run through 0, meaning to -1....that was a bullshit flag as was the holding on the td pass

Hammock Parties 12-06-2020 10:25 PM

Just awful.

Fortunately we are a team full of mother****ing studs.

SupDock 12-06-2020 10:26 PM

Someone blew the whistle before the play clock even hit zero. Think about that

I have no idea how that could happen.

Shiver Me Timbers 12-06-2020 10:26 PM

it was total bs
just like Hills catch in the endzone that was ruled incomplete. should have been reviewed "upstairs".

TwistedChief 12-06-2020 10:26 PM

It was on par with the infamous 'forward progress' Triplette debacle.

Bl00dyBizkitz 12-06-2020 10:27 PM

Normally it goes down to the zero for an extra second then the whistle is blown.

The whistle was blown with 1 on the clock. And you can't argue it either.

What in the ****?

kstater 12-06-2020 10:27 PM

Did they ever switch back over to the stadium clocks? I know they started keeping time on the field at one point. Wonder if that is what it was. NBCs graphic wasn't the actual clock

Sent from my Pixel 4 using Tapatalk

petegz28 12-06-2020 10:27 PM

Quote:

Originally Posted by Shiver Me Timbers (Post 15377869)
it was total bs
just like Hills catch in the endzone that was ruled incomplete. should have been reviewed "upstairs".

Would have been had they ruled it a TD.....since they called it INC it was on Andy's replay guy to put the nachos down and do his job. He almost cost us the game.

carcosa 12-06-2020 10:27 PM

That was next level ref incompetence. Almost beautifully bad

tyecopeland 12-06-2020 10:28 PM

I wonder if it had something to do with the clock malfunction earlier in the quarter. They announced that they would keep the clock on the field. So I am speculating that one of the officials was keeping the play clock by hand still and had it a couple seconds early.

suzzer99 12-06-2020 10:28 PM

That was the quickest trigger on delay of game I’ve ever seen.

BossChief 12-06-2020 10:29 PM

In the same game as a touchdown catch isn’t called a TD catch after never touching the ground.

Weird game.

Indian Chief 12-06-2020 10:29 PM

How many times over the years have you seen the clock hit zero and then the ball gets snapped, with no flag? And when it's brought up in the broadcast, they explain it by saying the ref has to watch the clock and then when he sees zero, he shifts his eyes to the snap. In that second or so, the ball is usually in the QB's hands and they don't call a penalty. So how the **** do you explain throwing a flag and blowing the whistle while there is still actual time on the goddamn clock?

Shiver Me Timbers 12-06-2020 10:29 PM

need black op to chime in but I am thinking the star chamber does not want a chiefs repeat

FloridaMan88 12-06-2020 10:30 PM

Every WTF moment went against the Chiefs tonight and they won.

Crazy shit like the non challenge.

But in the end... Mahomes.

KCUnited 12-06-2020 10:31 PM

Looked like blackops to me

siberian khatru 12-06-2020 10:31 PM

Quote:

Originally Posted by Indian Chief (Post 15377927)
How many times over the years have you seen the clock hit zero and then the ball gets snapped, with no flag? And when it's brought up in the broadcast, they explain it by saying the ref has to watch the clock and then when he sees zero, he shifts his eyes to the snap. In that second or so, the ball is usually in the QB's hands and they don't call a penalty. So how the **** do you explain throwing a flag and blowing the whistle while there is still actual time on the goddamn clock?

Happened in the Super Bowl

Bwana 12-06-2020 10:31 PM

They tried to horse **** us, but Butner was the man.

DaFace 12-06-2020 10:32 PM

Quote:

Originally Posted by kstater (Post 15377883)
Did they ever switch back over to the stadium clocks? I know they started keeping time on the field at one point. Wonder if that is what it was. NBCs graphic wasn't the actual clock

Sent from my Pixel 4 using Tapatalk

That's POSSIBLE. I'd love to know if that was the case because it's the only explanation that makes some level of sense.

TLO 12-06-2020 10:32 PM

Quote:

Originally Posted by KCChiefsFan88 (Post 15377931)
Every WTF moment went against the Chiefs tonight and they won.

Crazy shit like the non challenge.

But in the end... Mahomes.

There were some very odd moments. Not all officiating related by any means either.

But these guys still find a way to win.

chiefzilla1501 12-06-2020 10:32 PM

As I said in the other thread... Think I might scream if people keep bitching about butker missing 1 point XPs when he's been damn near automatic on crucial 3 pt FGs. Guy is an absolute killer.

493rd 12-06-2020 10:33 PM

Inexcusable and that one kinda felt egregious. NFL better reprimand those assholes.

Rain Man 12-06-2020 10:33 PM

Those are the types of things that really damage credibility.

If they were keeping time on the field, I guess I can see it being a legitimate error or miscommunication. But they need to explain that if it happened, and I question whether that's the case. The Chiefs were clearly running down the play clock before the snap and they were all shocked at the call out on the field. So they were looking at a clock when they snapped it.

SupDock 12-06-2020 10:33 PM

I don't know how something like that isn't reviewable.

I mean I get it, it's a little bit subjective when they blow the whistle after the clock hit zero, but the clock never hit zero

Just bizarre

Dayze 12-06-2020 10:34 PM

Quote:

Originally Posted by carcosa (Post 15377885)
That was next level ref incompetence. Almost beautifully bad

So incompetent it’s almost intentional

SupDock 12-06-2020 10:35 PM

Quote:

Originally Posted by Rain Man (Post 15377968)
Those are the types of things that really damage credibility.

If they were keeping time on the field, I guess I can see it being a legitimate error or miscommunication. But they need to explain that if it happened, and I question whether that's the case. The Chiefs were clearly running down the play clock before the snap and they were all shocked at the call out on the field. So they were looking at a clock when they snapped it.

I was expecting Andy to look more upset than he did

I didn't feel like I saw a lot of complaining at all, which I thought was strange

KCUnited 12-06-2020 10:35 PM

Could've been one of Triplette's 2 twins

RINGLEADER 12-06-2020 10:37 PM

Hopefully the lesson learned is that we have the ability to put 45 up every game and we can't rely on the refs to not try to take TDs and FGs away by any means possible.

KChiefs1 12-06-2020 10:46 PM

https://media1.giphy.com/media/9372N...y1DX/giphy.gif

JakeF 12-06-2020 10:50 PM

It's usually goes the other way. The refs usually wait too long before blowing the whistle and the announcers have to explain how the refs wait to look and then wait until the clock in completely on 0 before looking back at the ball to see if it's been snapped.

This went completely the other way. I'm not even sure the clock at hit 0 yet. Pretty shitty.

KChiefs1 12-06-2020 10:50 PM

https://media3.giphy.com/media/3oKIP...Dcru/giphy.gif

Megatron96 12-06-2020 10:51 PM

That was maybe the weirdest thing I've ever seen a group of refs eff up in a game. How do you call DoG when there's still "1" on the clock?

OrtonsPiercedTaint 12-06-2020 10:52 PM

Foiled!

007 12-06-2020 11:06 PM

Quote:

Originally Posted by TwistedChief (Post 15377872)
It was on par with the infamous 'forward progress' Triplette debacle.


Except we won this time

oldman 12-06-2020 11:15 PM

It was the game clock that had a problem, not the play clock. That said, the ball was snapped just as the play clock went from 1 to 0.

JakeF 12-06-2020 11:27 PM

Quote:

Originally Posted by oldman (Post 15378179)
It was the game clock that had a problem, not the play clock. That said, the ball was snapped just as the play clock went from 1 to 0.

They're supposed to turn to see if the ball was snapped AFTER the clock hits zero.

DaFace 12-06-2020 11:39 PM

Quote:

Originally Posted by JakeF (Post 15378215)
They're supposed to turn to see if the ball was snapped AFTER the clock hits zero.

And they are regularly VERY lenient about it. I know I've seen a time or two this year where I would swear it was at -2 and didn't get called.

BigRedChief 12-06-2020 11:42 PM

Another question. Why wasn’t the bench paying attention that we are running the clock down. We have 3 time outs, why wasn’t one used?

Pitt Gorilla 12-06-2020 11:43 PM

Quote:

Originally Posted by chiefzilla1501 (Post 15377960)
As I said in the other thread... Think I might scream if people keep bitching about butker missing 1 point XPs when he's been damn near automatic on crucial 3 pt FGs. Guy is an absolute killer.

Exactly this. People are stupid.

Ron Swanson 12-06-2020 11:43 PM

Quote:

Originally Posted by BigRedChief (Post 15378260)
Another question. Why wasn’t the bench paying attention that we are running the clock down. We have 3 time outs, why wasn’t one used?

Didn't need to, it was snapped in plenty of time.

DaFace 12-06-2020 11:46 PM

For the record, this wasn't related to the clocks not working. They're fine.

https://i.redd.it/zguwfaff1p361.jpg

BigRedChief 12-06-2020 11:47 PM

Quote:

Originally Posted by Ron Swanson (Post 15378265)
Didn't need to, it was snapped in plenty of time.

Evidently not. So there was a need. No reason to cut it that close.

Ron Swanson 12-06-2020 11:49 PM

Quote:

Originally Posted by DaFace (Post 15378275)
For the record, this wasn't related to the clocks not working. They're fine.

https://i.redd.it/zguwfaff1p361.jpg

The ref that threw that flag should be suspended and investigated. Missing a bang bang play at full speed is one thing, that reeked of corruption.

jerryaldini 12-06-2020 11:55 PM

Yeah that is so egregious needs to be addressed by the league. Short field easily could have sent us to OT. Imagine the meltdown after the holding, missed TD...

Megatron96 12-07-2020 12:02 AM

Quote:

Originally Posted by BigRedChief (Post 15378279)
Evidently not. So there was a need. No reason to cut it that close.

Wtf? Are you trolling, or are you just really stupid? No, this has to be sarcasm. no one's this stupid.

staylor26 12-07-2020 12:04 AM

Quote:

Originally Posted by BigRedChief (Post 15378260)
Another question. Why wasn’t the bench paying attention that we are running the clock down. We have 3 time outs, why wasn’t one used?

Why didn’t the bench call a TO when the ball was snapped before the clock hit 0?

Is this a serious question?

Demonpenz 12-07-2020 12:05 AM

They can't just put a buzzer with a light around it like a normal sport can they?

Ghost of Maslowski 12-07-2020 12:09 AM

been watching NFL games for more than 30 years and never once seen that happen

seen plenty of plays, including one late in the last Super Bowl, not get called for delay with the play clock on zero though

of course, in this same game, a KC WR caught a TD pass that was somehow ruled incomplete despite the ball never touching the ground, and none of these garbage refs actually saw that happen, either

Redbled 12-07-2020 12:16 AM

The call appears to be crap.

What I don’t understand is why not take the TO with 1 second left allowing your kicker to kick it at any point in the play clock he wants to. Seems that it would almost always take more time off and certainly safer as well. You see that all the time where coaches say I want a TO with 1 second on the play clock.

Megatron96 12-07-2020 12:25 AM

Quote:

Originally Posted by Redbled (Post 15378321)
The call appears to be crap.

What I don’t understand is why not take the TO with 1 second left allowing your kicker to kick it at any point in the play clock he wants to. Seems that it would almost always take more time off and certainly safer as well. You see that all the time where coaches say I want a TO with 1 second on the play clock.

There was still a "2" on the stupid clock when they snapped it. Why would they call a TO when the ball had obviously already been snapped? Just in case the refs decided to have a unanimous group brainfart? A brainfart that has never happened in the history of the NFL?

morphius 12-07-2020 01:05 AM

Quote:

Originally Posted by Redbled (Post 15378321)
The call appears to be crap.

What I don’t understand is why not take the TO with 1 second left allowing your kicker to kick it at any point in the play clock he wants to. Seems that it would almost always take more time off and certainly safer as well. You see that all the time where coaches say I want a TO with 1 second on the play clock.

It had been answered here already, but why bother if you are out there in plenty of time, everything is set and the bball gets off in time. If things looked doubtful, sure. But hiking the ball with one on the clock is common.

UK_Chief 12-07-2020 01:35 AM

Was there a clear offsides that wasn’t called on Denver too?

KC_Connection 12-07-2020 02:14 AM

Refs were trying to keep the game close for the entire 2nd half. This was just a particularly egregious example of it.

Another reason why you should put bad teams away while you have the chance in this league before the refereeing can get involved.

KC_Connection 12-07-2020 02:15 AM

Quote:

Originally Posted by SupDock (Post 15377981)
I was expecting Andy to look more upset than he did

I didn't feel like I saw a lot of complaining at all, which I thought was strange

Well that would fall right in line with his behavior the rest of the game. He coached like he didn't give a shit about this one at all.

Rasputin 12-07-2020 02:22 AM

Quote:

Originally Posted by DaFace (Post 15378275)
For the record, this wasn't related to the clocks not working. They're fine.

https://i.redd.it/zguwfaff1p361.jpg

We got hosed on that one.

MIAdragon 12-07-2020 02:22 AM

Quote:

Originally Posted by Megatron96 (Post 15378327)
There was still a "2" on the stupid clock when they snapped it. Why would they call a TO when the ball had obviously already been snapped? Just in case the refs decided to have a unanimous group brainfart? A brainfart that has never happened in the history of the NFL?

Running clock is exactly what he’s supposed to do, every last second. We got hit with a shit call, it’s not on him or the bench.

Rasputin 12-07-2020 02:25 AM

I'm more upset about the Tyreek Hill touchdown that wasn't called a touchdown nore reviewed. I thought all scoring plays were to be reviewed.

KC_Connection 12-07-2020 02:25 AM

Quote:

Originally Posted by Rasputin (Post 15378409)
I'm more upset about the Tyreek Hill touchdown that wasn't called a touchdown nore reviewed. I thought all scoring plays were to be reviewed.

Wasn't a scoring play. They called it incomplete.

MIAdragon 12-07-2020 02:26 AM

Quote:

Originally Posted by Rasputin (Post 15378409)
I'm more upset about the Tyreek Hill touchdown that wasn't called a touchdown nore reviewed. I thought all scoring plays were to be reviewed.

Still puzzled why we rushed the punt?

PunkinDrublic 12-07-2020 02:36 AM

Well I’m sure the parties responsible for that mistake will be held accountable by the league.

-King- 12-07-2020 02:43 AM

Quote:

Originally Posted by MIAdragon (Post 15378411)
Still puzzled why we rushed the punt?

Cause literally no one thought that he caught it. It wasn't rushed, it was a normal procedure punt.

-King- 12-07-2020 02:43 AM

Quote:

Originally Posted by DaFace (Post 15377818)
I mean...WTF was that?

Bullshit is what it was. I don't understand why the players and coaches didn't seem upset about it though

Mahomes_Is_God 12-07-2020 02:58 AM

The league is getting desperate. They realize we're just going to steamroll everybody so they're going out of their way to make our games close.

Rasputin 12-07-2020 03:21 AM

Quote:

Originally Posted by KC_Connection (Post 15378410)
Wasn't a scoring play. They called it incomplete.

Right but league still should have got it right it still should have been reviewed and I'm just saying out of principle. They got it wrong.

Bob Dole 12-07-2020 04:51 AM

Quote:

Originally Posted by -King- (Post 15378418)
Cause literally no one thought that he caught it. It wasn't rushed, it was a normal procedure punt.

With 9 seconds left on the play clock? It was rushed.

SuperBowl4 12-07-2020 04:54 AM

over officiating jerks! -> http://youtu.be/HCosRfNZnEw

jallmon 12-07-2020 05:10 AM

Quote:

Originally Posted by DaFace (Post 15377954)
That's POSSIBLE. I'd love to know if that was the case because it's the only explanation that makes some level of sense.

Yes. I've heard it explained many times that the ref watches the clock, when the clock shows zero, he/she looks down to see if the ball is snapped. On this play, the whistle/flag were at 01 on the clock we saw on tv (not sure exactly what "clock" we were seeing).

So nice to have a kicker that says **** it and kicks it again, but he shouldn't have to do that.

Coogs 12-07-2020 05:29 AM

Quote:

Originally Posted by Rasputin (Post 15378430)
Right but league still should have got it right it still should have been reviewed and I'm just saying out of principle. They got it wrong.

This! Refs are only supposed to call what they see. You can not call what you "think" happened. The ref that was emphatically calling it incomplete was on the wrong side of the play to even have a chance of seeing the ball hit the ground. Just because he thought the ball probably hit the ground he made the wrong call. League should have buzzed in there.


Damn near 17 points taken away from the Chiefs again last night against a West opponent. Twice in one season.

Sassy Squatch 12-07-2020 05:37 AM

There was a problem with the clock earlier in the game. Wonder if that had anything to do with it and the TV clock wasn't lined up quite right with the actual on field clock.

Frazod 12-07-2020 06:27 AM

Quote:

Originally Posted by PunkinDrublic (Post 15378416)
Well I’m sure the parties responsible for that mistake will be held accountable by the league.

Yeah, I'm sure they'll get right on that.

https://i.gifer.com/DXo4.gif

digger 12-07-2020 07:00 AM

This had all the markings of a "Trap" game and we over came a lot, add this to the list...

htismaqe 12-07-2020 07:05 AM

Quote:

Originally Posted by Superturtle (Post 15378447)
There was a problem with the clock earlier in the game. Wonder if that had anything to do with it and the TV clock wasn't lined up quite right with the actual on field clock.

Pretty sure they showed a replay with the actual game clock in PIP down in the corner and it showed the ball being snapped before the clock his zero.

oldman 12-07-2020 07:13 AM

Quote:

Originally Posted by DaFace (Post 15378275)
For the record, this wasn't related to the clocks not working. They're fine.

https://i.redd.it/zguwfaff1p361.jpg

There was no excuse for that call. It was the game clock, not the play clock that had a problem. What you're seeing in the window is the actual play clock. I'm beginning to think the zebras are out to get us.
The TD that wasn't a TD wasn't on the officials because even Hill didn't think he had it. But there wasn't any need to hurry the punt.

Dunerdr 12-07-2020 07:17 AM

Quote:

Originally Posted by oldman (Post 15378468)
There was no excuse for that call. It was the game clock, not the play clock that had a problem. What you're seeing in the window is the actual play clock. I'm beginning to think the zebras are out to get us.
The TD that wasn't a TD wasn't on the officials because even Hill didn't think he had it. But there wasn't any need to hurry the punt.

The punt wasnt hurried it was normal procedure. No one in that stadium thought he caught that ball. Not even Hill.

RedinTexas 12-07-2020 07:24 AM

There is the game clock and there is the play clock. The game clock may have been in the hands of the refs at the time, but why in the hell would the play clock be in the hands of the refs? The play clock is there for the players and the refs to see. How can the players get a play off in less than the allotted time unless they have access to a play clock that allows them to know how much time is left?

If the play clock was malfunctioning and "in the hands of the refs," why wouldn't the refs be cutting just a little bit of slack to the players that don't have the full knowledge that the players do? Why wouldn't the NBC crew explain that the refs had control and the play clock that we could see wasn't official?

The play clock that we could see was almost 100% certainly the official play clock. There was time left on the clock when the ball was snapped. The referee that called delay of game was wrong and not on a "close call." Calling a penalty for something that did not actually happen is pretty bad, but usually there is an explanation for it such as that it looked like it happened. There is no excuse for that penalty. It was wrong and the official that called it should be severely disciplined.


All times are GMT -6. The time now is 06:19 PM.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2024, vBulletin Solutions, Inc.