![]() |
I blew this, but it took an inning to realize it
2-1 count to batter (weak batter). Next pitch, purposely high so catcher can make a play (very close to an out) on the lazy runner at first. After ball hits the glove, batter chops at the high pitch in obvious strike. Catcher stands high to grab the pitch, whips ball to first--safe there--and my partner obviously didn't see the VERY late swing by the batter because it was very late and the catcher stood high. Before the next pitch, PU announces the count as 3-1. I wait but nothing happens, and it is obvious to me my partner missed the swinging strike, so I called time, we had a conference, and we changed the count to 2-2 based upon my advice to him, and not because of any appeal....at the time, it felt right because we got it right, but then I got to thinking....No appeal was made, and I was wrong....it should have been on the defense to be game-aware and make the appeal.....Right?
|
sounds like good preventative umpiring to me. why have him walk on the next pitch and go through the discussion of what the count should be when you know? others will disagree with me on this...but oh well.
|
No, you are OK. This wasnt a check swing. If nothing else you were just making sure the count was right. But if you had an inkling that your partner didnt see the swing, then in my opinion, good umpiring on your part. If you were my partner, you would get an atta boy.:D
|
Quote:
|
Quote:
|
w/o seeing it, we don't know...but if there's no attempt to actually try to hit the pitch, yep, we've got BI here.
|
Quote:
|
Quote:
|
Quote:
Batters often do this to get in the catcher's way of his throw to make their interference look "natural." |
Quote:
|
Quote:
Quote:
|
In regards to the OP. If grandma in the upperdeck knew the batter swung at the pitch, then I would correct the count. If there was any question, check swing, I would wait for the appeal. YMMV
|
Quote:
A) What makes your count more likely to be right than PU's? B) How do you know PU didn't see the late swing? |
For those who are tempted by the thought of BI here: Remember that nothing -- and I mean NOTHING -- that the batter does BY ITSELF constitutes interference. Intent to be a nuisance does not violate the rules.
In order to call batter interference, there has to be some actual hindrance of the play. In this case, it doesn't sound as if there was any: F2 threw down to 1B just fine, and there was a close play there. So BI is the wrong call in the OP, if I'm reading it correctly. Now, even if there's hindrance on this play, I'm leery about calling BI because the batter was doing what he was supposed to be doing, namely swinging at the pitch. I don't work much ball below HS varsity, so a late swing might be suspicious in my games; but a late swing by itself will not constitute BI. You don't want to be the kind of umpire who shows off his knowledge of the rules by looking for situations to make unusual calls. Don't be a plumber. |
Quote:
I've called this when the batter swings AFTER my ball/strike call (and I have SLOW timing). This is pretty obvious to me that he's trying to interfere. Conversely, I've had a batter try this on a pitch that was wayyy outside in the other batter's box and the bat in no way came close to hindering him and I had nothing in that instance. |
All times are GMT -5. The time now is 06:47am. |