Chop Blocking and Delay

[TXMike]

We know there is no requirement for there to be a delay between the hi and the low blocks to have a chop block.  But if there is a delay, when is the delay too much of a delay?   Example:  At the snap the TE blocks a LB above the waist.  The LBr gets free and pursues the runner for about 20 yards  before another Team A player blocks him low from the front.  I don't think any of us would say that is a chop block.  But what about this?

https://youtu.be/uJBmytOQuqI

[mishatx]

Are we looking at 10 and 75 on the left side of the line?  I'd say that both blocks have to be engaged for this to be a foul, and at the time of 75's block, 10 is no longer engaged. 

[Osric Pureheart]

Neither engaged nor still confronting.

However, do I see a possible low-low combination over at the point of attack?

[first_year_guy]

Are you complementing the low-low combo? Because that's perfectly legal to go low-low

[Osric Pureheart]

That was supposed to be one to catch out the veterans!

[NVFOA_Ump]

The delay is no longer a factor in chop block calls.  The current requirement is that the blocked player is still engaged with the initial blocker (high or low block) when the 2nd block  (high or low block / opposite of initial block) is first made such that the player being blocked is engaged with both high and low blocks.

[TXMike]

Don't the rules also say it is a foul if 1st blocker had just disengaged?

[NVFOA_Ump]

Agreed that the player must be free from the first block prior to the 2nd block but there is no set delay.  Straight judgment call as to when the player is disengaged from the 1st block, but there is no time defined.

[bossman72]

Are you referring to the TE and G on the back side at about the 30 yd line?  No, that's not a chop either.

[Magician]

Not even close to a chop block. Definitely an IC if flagged. Both blocks need to be engaged at the same time. There is some gray area when one player posts and the other cuts, but the high block is completely disengaged here. No foul.