![]() |
Running Lane violation
Had a play last night that I have a question about. Men's league, pretty good quality ball. Turf field without a marked running lane. 1 out, no one on, D3K just to the 3B side of HP. B/R takes off for first. F2 picks up ball and makes throw directly over B/R who is running completely inside the foul line. F3 jumps to make catch and comes down on bag as runner touches the bag. I have an out and sell it.
Question is if I didn't have an out, could this have been interference even though the throw was high? In my opinion it was high because the catcher was throwing over the runner. The runner was basically taking away the inside throw and based on where the ball ended up an outside throw would have been a little impractical. What is the correct mechanic? |
Quote:
The runner doesn't "take away" anything from the catcher's ability to make a quality throw. |
6.05(k) A batter is out when in running the last half of the distance from home base to first base, while the ball is being fielded to first base, he runs outside (to the right of) the three foot line, or inside (to the left of) the foul line, and in the umpire's judgment in so doing interferes with the fielder taking the throw at first base; except that he may run outside (to the right of) the three foot line or inside (to the left of) the foul line to avoid a fielder attempting to field a batted ball;
the last half of the distance from home base to first base... lane need not be marked interferes with the fielder taking the throw at first base...use your own judgement here as in any interference/obstruction scenario. In my opinion, if the runners presence outside the prescribed runners lane necessitated or caused F2 to throw the ball wildly (ie. rainbow a throw over the batter/runners head), that could be interference even though no contact was made. |
Quote:
|
Quote:
|
Quote:
FED puts the burden on the runner more than OBR, and the rule discourages catchers from drilling the runner in the back by explicitly permitting an INT call even if the throw is poor. Safety considerations motivate this rule difference from OBR. |
Quote:
If it is not a quality throw then there is no play by the fielder to interfere with. |
Quote:
|
Quote:
interferes with the fielder taking the throw at first base. Not "causes the catcher to abandon all hope of an out by throwing the ball into right field" :) |
Quote:
The cite is the text of 6.05(k) (posted above). The OBR running lane interference rule only hold the runner liable for interfering with the fielder receiving the throw at 1B - not the fielder making the throw. FED holds him liable for both. JM |
Quote:
|
Quote:
If the throw drills the runner (assuming it's not plainly obvious to the world that the catcher was TRYING to hit the runner, and not throwing to first base), then he did, in fact, interfere with the fielder's ability to receive the throw. It's not rocket science. Don't make it harder than it is. (And if you don't believe the 100% agreement in the responses you're getting, ask your clinician or UIC ... OBR, all over, is interpreted this way. FED, all over, is interpreted more broadly) |
Quote:
thanks. |
Quote:
|
Quote:
|
All times are GMT -5. The time now is 08:30am. |