Quote:
Originally posted by MPC
For those guys who will absolutely not call int on the high throw in the example, how would you handle a batters int with a catchers throw to retire R1 at 2nd base when the ball end up 5' over the fielders head and in center field? Example: R1 to 2nd, B1 swings on the pitch and his mo carries him in front of the plate. F2 comes up to throw and B1 is in front of him causing his release to be high and results in the ball ending up in center. Same basic theory. B1/BR is blocking throwing lane Illegally so I don't see how int can't be called given that the offensive actually is the direct cause of the misfire.
Looks like another good example of common sense/fair play.
|
Unfortunately for your position, the OBR rule book cares not a whit about common sense/fair play since it unwaveringly favors the team on offense. But that aside...
There's simply no connection between a batter interfering and causing a throw into centerfield during a steal, and the batter-runner not in the lane when the catcher launches one into right field. As is basketball, it's a matter of time and distance.
The catcher has but a
moment to make his throw to prevent a stolen base. In the
close quarters at the plate, when the batter is out of the box, even "obstructing the catcher's vision may be interference." (Evans)
But the running lane doesn't operate for the first 45 feet. Let's say it takes a speedy runner three to four seconds to reach first. The catcher has ample time and plenty of room to make a quality throw. When he sails the ball into right field -- even with a runner not in the lane! -- it simply cannot be, to use your word, "int."
BTW: I posted this message this morning around 8:00, but "previewed" it instead of "submitting" it. Anybody else done that?