View Single Post
  #18 (permalink)  
Old Tue Jun 04, 2019, 11:23am
youngump youngump is offline
Official Forum Member
Join Date: Mar 2008
Posts: 1,210
Originally Posted by jmkupka View Post

Thanks all for the clarification. The final answer to my OP is, "because it's the rule."

It seems to me, the point of killing it at the time the OBS runner is put out, is to let the dust settle and let the viewers know the result, while still potentially depriving the offense because of an infraction on the defense's part.

All the other DDB plays let the offense get as much as they can, and wait until play has stopped, before ruling.

Is the OBS rule the way it is because it's unfair to make the DEF mistakenly think they have an out (maybe a 3rd out) while allowing runners to keep going?
I always figured it was because umpires could barely handle the rule as is. And killing it makes it simpler to unwind.
Consider: Bases loaded, no outs. B4 hits an easy double play ball to short. While F6 misplays the ball, F3 obstructs R3 going toward second. In avoiding interfering with F6, R2 trips on the way to third. Due to the delay caused by the obstruction F4 is still able to tag out R3 after F6 recovers.

Normally, the play ends here and we make a fairly straightforward award.
But now you are about to enter another dimension, a dimension not only of sight and sound but of mind. A journey into a wondrous land of imagination. Next stop, the Twilight Zone!

Obstruction is a ddb here.

F4 steps up and throws to F5 who is standing on third base. With R3 called out F5 starts to chase R2 back toward second. A rundown ensues. B4 scampers up toward second in the confusion. R3 is tagged out going toward second and the ball is overthrown into right field. B4 advances to third. The ball is returned to the pitcher and you call the ball dead. Award bases as appropriate. And don't even get me started on if something crazy had happened.
Reply With Quote