Jump to content
Umpire-Empire locks topics which have not been active in the last year. The thread you are viewing hasn't been active in 1033 days so you will not be able to post. We do recommend you starting a new topic to find out what's new in the world of umpiring.

Recommended Posts

Posted
catcher-block.png
After Reds baserunner R3 Elly De La Cruz was confirmed out on a play at home plate that Cincinnati manager David Bell unsuccessfully challenged for both a violation of the home plate collision rule and HP Umpire Jeff Nelson's tag out/safe call after ruling the runner never touched home plate, we were asked if Padres catcher Gary Sanchez's position was, indeed, legal.

Replays indicate that when Reds batter Nick Senzel hit a ground ball to Padres shortstop Xander Bogaerts, San Diego's infield was drawn in, anticipating a play at the plate. Bogaerts' throw to Sanchez arrived as Reds runner R3 De La Cruz slid headfirst into home, but Sanchez's left foot, positioned in front of home plate, effectively blocked De La Cruz from reaching it, resulting in the tag out.

The question, thus, is whether Sanchez violated baseball's home plate collision rule. Official Baseball Rule 6.01(i)(2) very specifically addresses this situation: "...It shall not be considered a violation of this Rule 6.01(i)(2) if the catcher blocks the pathway of the runner in a legitimate attempt to field the throw (e.g., in reaction to the direction, trajectory or the hop of the incoming throw, or in reaction to a throw that originates from a pitcher or drawn-in infielder)."

Thus, even though Sanchez may have physically blocked De La Cruz from scoring, this blocking was legal pursuant to the throw that originates from a drawn-in infielder part of the rule.

View the full article

Posted

Ummm … why?
 

Not why is that not blocking (fully understood that) but why is that not blocking in the rule book? What is the logic behind allowing it?  Not arguing, just curious.

Posted

My speculation is the ”‘there isn’t enough time to be that precise on the setup” argument was enough to get that exception.

Plus since it’s (almost always) only on R3, they wouldn’t be at full steam. Additionally, this isn’t how Buster got hurt.

So, I’d further speculate this was decided towards the end of the rule drafting so was possibly influenced by fatigue.

Posted

There is less time for F3 to react to runner coming back into 1B ... just saying.  

I thought about the "full steam" thing, but we don't allow blocking in any other shorter or less momentum-driven experience.

I don't know ... just trying to talk through this one because it makes no sense to me.

  • Like 1
×
×
  • Create New...