![]() |
|
|
|
|||
|
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. |
|
|||
|
Quote:
__________________
It's like Deja Vu all over again |
|
|||
|
Please describe a specific play where that happens -- I'm having trouble envisioning the BR hindering F3, but F3 "successfully fields the ball" (by which I assume you mean catches the throw).
|
|
|||
|
Yes. Doesn't the provision for runner's lane interference deal with F3's ability to field the throw?
Example: Bunt down 1BL, F2 fields, throws, B/R is inside the runner's lane about 20 ft from 1B, F2 successfully threads the needle by throwing the ball over B/R's left shoulder and F3 catches the ball for a 2-3 putout. If the ball goes off of B/R's helmet and out into RF...you have running lane INT right? So...I'm asking the other poster if he would call it before he saw the result of the attempted play?
__________________
It's like Deja Vu all over again |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|