Quote:
Originally posted by bob jenkins
Interesting conflict.
8-4-2j Exception states that "No runner may be forced out if a runner who follows him in the batting order is first put out." In case 9.1.1H, R3 was put out before R2 (damn FED notation) and R3 followed R2 in the batting order. So, we'd not ahve a force out on the appeal.
But, 2-29-3 states that "For a given runner, a force play ends as soon as ... a following runner is put out AT A PREVIOUS BASE." (emphasis added) In case 9.1.1H, R3 was put out at the base to which R2 was forced -- not at a previous base. Therefor, R2 was still forced to third, and the out is a force out.
Maybe the case is saying that 2-29-3 takes precedence.
|
Bob:
Interesting! I thought I posted the answer to this question yesterday. I guess I "previewed" without "submitting."
Contrary to what someone posted, this has nothing to do with passing a base or rounding a base, or anything you might have left out, or anything esoteric other than WHEN an out was made.
In Situation 9.1.1. K, the out was made BEFORE the runner from second missed the base. Therefore, the force was removed, and the run scores.
In Situation 9.1.1. H, the out (on appeal) was made AFTER the runner missed the base. Therefore, the force was NOT removed, and the run does NOT score.
An official interpretation now aligns OBR with those rulings.
That is not the case in NCAA. I know because I wrote that rule back in the 80s. At that level, a force in effect at the time of the pitch remains in effect throughout the play if baserunning errors are later in question.
Thus, in BOTH cases the run would NOT score in an NCAA contest. That, of course, is the simplest rule to adminster.
Just my facts. (grin)