Quote:
Originally posted by PAblue87
But he is not "SAFE". In order to be safe he must beat the ball to the base and that has not happened. I still think you wait. Most likely, if there is no call both players will realize what happened and try to either get back to the base or tag the runner.
|
This play has been beaten to death. At every level but FED, the correct mechanic is to signal "Safe." One may not like that, but it is the accepted pro method. Here's the necessary "evidence":
The batter-runner beats the throw to 1st base by a full step, but he did not touch the base as he crossed it. He is past the base when the ball arrives. The 1st baseman takes the late throw while touching the base. Is the runner out?
RULING: This runner should be ruled safe as he has passed the base. This becomes an appeal play and requires the fielder to lodge an appeal in a timely and unmistakable manner. The 1st baseman can retire the B-R by tagging him or by tagging the base on the appeal. (Professional Interpretation) (JEA 7:56)
The reason is obvious, and it has nothing to do with "coaching" or "helping the defense" or "helping the offense." It's a mechanic rooted in the tradition of baseball, which says that a runner who beats the play is safe. Should he miss the base, that error may be appealed.
Here's an example that will illustrate the point:
Play: Two out, bases loaded, roller to short, but his throw pulls F4 off the base. R3 scores, R2 tries to score but is thrown out. R1 has continued to occupy third at the time of the third out.
The umpire
in all likelihood will have signaled "safe -- off the base" as the play occurred at second. The fact he called R1 safe does not relieve R1 of the responsibility to touch second. But play continues
as if he did, and R3's run scores
unless the defense returns to appeal R1 missed second.
The same appeal is available to the defense when the B-R misses first.
[Edited by Carl Childress on Mar 17th, 2001 at 12:17 AM]