![]() |
|
|
|||
Int or not?
Posted this on another board, but curious what some of you all thought.
Bases loaded, 2 out. Ball hit to F5, R2 takes a couple of strides, stops directly in front of F5, turns facing ball coming at him, then turns at the last second to avoid ball and continues to run to 3B. There is no question in anyones mind (except the umpires in this game) that he is trying to cause SS to miss this ball. SS fields ball cleanly and throws to 1B, where BR barely beats the throw. INT was not called. Now to my questions: Would you call INT after the play had ended? If you would, how would you respond to the OM when he asked why INT was called? |
|
|||
If the runner tried to distract (it appeared as though he altered his path to distract F6)the fielder from being able to field the ball, I'm calling INT here...but, I didn't see the play...so that's what I would've done based upon what you're describing.
__________________
It's like Deja Vu all over again |
|
|||
Quote:
It's a ballsy call. |
|
|||
Quote:
The OM asked why it was interference if he didn't even touch the ball or the fielder. My partner answered that he denied the fielder an opportunity to see the ball sooner and make the play. He called it, but the shortstop continued and made the play. He took good command of the call and the description. Good command for a kid, that is. ![]() The defensive coach wound up being more of a pain in the a$$ about the automatic double play (no chance in hell of two on this play). |
|
|||
![]() Quote:
No, I would call it as soon as I judged it was interference. (As I'm picturing your description, that would be before the ball reached the fielder.) My response to the OC would be "In my judgement, your runner intentionally hindered the fielder's attempt to field the batted ball." If you're going to call interference, you call it when you see it. You don't wait to see the outcome of the play. JM
__________________
Finally, be courteous, impartial and firm, and so compel respect from all. |
|
|||
![]()
Coach, the fielder's ability to complete the play despite your runner's hindrance does not excuse his interference.
Let's play baseball. JM
__________________
Finally, be courteous, impartial and firm, and so compel respect from all. |
|
|||
Quote:
Or are you saying, call it, if they make the play they're intending to make, then we nullify the INT? (minus anything malicious)
__________________
It's like Deja Vu all over again |
|
|||
![]() Quote:
Not sure what you're getting at here. I don't think I would treat a runner's lane interference call any differently in this regard, and were I to call it and the defense were able to complete the play (not likely, but possible, I guess) I would certainly NOT "nullify" the interference. The only sitch I can think of where that would be proper is on a BI (or UI, I guess) with the catcher's throw to retire a runner. If the initial play is successful, the interference is "disregarded". Anything else, I'm sticking with the interference - which means there's an out AND any remaining runners return. JM
__________________
Finally, be courteous, impartial and firm, and so compel respect from all. |
|
|||
Would a play like this ever result in us calling out the runner closest to home? Assume we're calling INT on a play. New thread?
__________________
It's like Deja Vu all over again |
|
|||
Quote:
Calling out ONLY the runner nearest home? Never -- the runner who interferes is out. If it was the BR and IF you were going to get two outs on the play (for "willfull and deliberate attempt to prevent a DP"), then you also get the runner closest to home. |
|
|||
If the fielder had to pull up instead of charging a ground ball (which any coach with 1/3 of a brain should be teaching his kids to do) to avoid a runner intentionally hovering in front of a grounder, it doesn't matter how cleanly the ball was fielded.
|
![]() |
Bookmarks |
Thread Tools | |
Display Modes | Rate This Thread |
|
|