Brian Burns not credited with a sack?

[Eazy-E]

So unless I am mistaken, Burns did not get credit for the sack on the Mahomes read option he destroyed because there was no apparent attempt at a pass. 

I don't really understand the rules there and how you determine if a play is designed to be a run or a pass if the QB is taken down as fast as Mahomes was. I know there was quite a number of times Cam got killed running option plays and the opposing team was credited with a sack.

If you botch a snap and fall on the ball in the backfield is that not a sack?

Anyone care to explain/elaborate? 

[kungfoodude]

He wasn't old enough to get that call.

[TylerDurden]

I feel so pissed off for Burns.  Glad you checked bc I meant to look earlier when it had crossed my mind and forgot...  but yeah, upset for him bc that's like the 3rd off the top of my head that he has been screwed out of bc of the scorekeepers/officials - one of the Herbert strip sacks against the chargers wasn't counted and it was an obvious strip sack, the sack against ATL that was negated by a meaningless def holding penalty (and Burns was injured on the play), and then that play yesterday.  I really wish we had/quickly develop his bookend, bc the Chiefs literally kept the RB on his side every play to either chip or run a screen behind him to slow him down.

[SetfreexX]

A Read Option is a run play for either the QB or HB, it would be classified as a TFL, not a sack. 

[TylerDurden]

1 minute ago, SetfreexX said:

A Read Option is a run play for either the QB or HB, it would be classified as a TFL, not a sack. 

My guess is it was more likely an RPO than a read option run play if Mahomes was keeping it.  IIRC, the commentators even said it was an RPO, so Burns not getting credit was likely just due to interpretation by the scorekeepers.

[Rags]

2 minutes ago, Proudiddy said:

My guess is it was more likely an RPO than a read option run play if Mahomes was keeping it.  IIRC, the commentators even said it was an RPO, so Burns not getting credit was likely just due to interpretation by the scorekeepers.

Burns blew it up so fast its hard to say.

God bless him.

[micnificent28]

22 minutes ago, Rags said:

Burns blew it up so fast its hard to say.

God bless him.

Well the fact he didn't hand it off which he had time to do tells me it was a pass. Even the wrs were running routes and not blocking like it was a run.

[WarHeel]

They screw him week in and week out with the lack of holding calls. Not surprised.

[Basbear]

55 minutes ago, kungfoodude said:

He wasn't old enough to get that call.

I still believe that was the turning point in Cams career, not brainlet Rivera/Shula. Though he should have said things public, rather than "send it league office". Refs didnt protect him like other QBs form that comment on, beyond dumb reasoning. 

[Kuhndog94]

55 minutes ago, Rags said:

Burns blew it up so fast its hard to say.

God bless him.

Suffering from success. 

[TheCasillas]

1 hour ago, SetfreexX said:

A Read Option is a run play for either the QB or HB, it would be classified as a TFL, not a sack. 

but he still had an option to throw it. Silly NFL rules. 

[WUnderhill]

Seems like it would be a lot easier just to say anytime a QB is tackled behind the LOS it’s a sack. Like would anybody really complain about that?

[Mister]

thats criminal im about to write a letter to godell 

[Panthercougar68]

Remmers learned how to beat speed rushers finally

1) Hold 

2) kick start before the ball is snapped (there were multiple false starts not called)