Jump to content

2012 NCAA Baseball Rules Test Question


jpperez14
Umpire-Empire locks topics which have not been active in the last year. The thread you are viewing hasn't been active in 2683 days so you will not be able to post. We do recommend you starting a new topic to find out what's new in the world of umpiring.

Recommended Posts

R1 and R2. 3-2 Count. No outs. The pitch is an uncaught 3rd strike. B1 immediately starts for 1st. After both feet have touched the ground outside the batter's box, he unintentionally kicks the drop 3rd strike. R2 is stealing on the pitch, R1 is not.

A) The batter is not out on strike three. The defense must throw out B1 at first on the dropped third strike. R1 and R2 remain at their advanced bases.

B) The batter is out on strike three. R1 stays at 1st, but R2 is allowed to stay at 3rd.

C) The batter is out on strike three. R1 stays at 2nd, R2 stays at 3rd.

D) The batter is out for interference. Both R1 and R2 must return to TOP bases. 

Link to comment
Share on other sites

  • Replies 19
  • Created
  • Last Reply

Top Posters In This Topic

Thanks, Mr. noumpere, for eliminating two choices. I now choose B.

From the 2016 BRD (section 291, p. 190):

...“If the batter-runner unintentionally deflects the ball, the ball is alive and in play. EXCEPT:  If there are fewer than two outs and first is occupied, the ball is dead and runners return UNLESS the runners are stealing on the pitch.” (7-11h AR 1)

Play 149-291:  NCAA only. R1, R2, 0 outs, 3-2 count. B1 strikes out and erroneously starts for first. Just outside the box he unintentionally kicks the ball, and the umpire calls: “Time! Dead ball.” (a) Both runners were stealing; (b) neither runner was stealing; (c) R1 was stealing, but R2 was not; (d) R2 was stealing, but R1 was not.  RULING:  In (a), runners get second and third; in (b) and (c) they remain on first and second. In (d), R2 keeps third, but R1 remains on first. (Paronto, 1/3/04)

Link to comment
Share on other sites

4 minutes ago, Jimurray said:

I don't see where the rule differentiates between a legal batter-runner or not. They it a "dropped third strike" which is different than an uncaught third strike. 

I'm not sure what you mean but......

If you're addressing the OP, the batter has been retired on strikes. 

Link to comment
Share on other sites

6.01(a)(1), old 7.09(a). They do call it an uncaught third strike now in the rule. My older MLBUM referred to a dropped third strike. But the OBR rule appears to apply whether the batter became a legal runner or not. So if he's out on strikes if he clearly hinders the catcher in fielding the ball that the catcher just dropped the ball is dead and runners return. 

Link to comment
Share on other sites

8 minutes ago, Jimurray said:

6.01(a)(1), old 7.09(a). They do call it an uncaught third strike now in the rule. My older MLBUM referred to a dropped third strike. But the OBR rule appears to apply whether the batter became a legal runner or not. So if he's out on strikes if he clearly hinders the catcher in fielding the ball that the catcher just dropped the ball is dead and runners return. 

But the rule that applies to the batter interfering with the catcher's ability to field a drop third strike doesn't apply here, because we don't have a dropped third strike. We have strike three batter is out. The catcher isn't making a play on a runner at this point so, in OBR, wouldn't the correct call simply be nothing?

Link to comment
Share on other sites

5 minutes ago, Stk004 said:

But the rule that applies to the batter interfering with the catcher's ability to field a drop third strike doesn't apply here, because we don't have a dropped third strike. We have strike three batter is out. The catcher isn't making a play on a runner at this point so, in OBR, wouldn't the correct call simply be nothing?

@Senor Azul might tell us more from 2016 BRD. But if you call nothing what do you do if the runners start to go on the hindrance? When the rule/interp was changed the MLBUM called it a dropped third strike. That is imprecise language unless they mean any third strike that the catcher put on the ground, with no qualifier regarding whether the batter could run. The latest rule calls it an uncaught third strike. Is OBR similar to NCAA in killing the ball even though it was interfered with by a retired runner? But OBR returns all runners?

Link to comment
Share on other sites

5 minutes ago, Jimurray said:

@Senor Azul might tell us more from 2016 BRD. But if you call nothing what do you do if the runners start to go on the hindrance? When the rule/interp was changed the MLBUM called it a dropped third strike. That is imprecise language unless they mean any third strike that the catcher put on the ground, with no qualifier regarding whether the batter could run. The latest rule calls it an uncaught third strike. Is OBR similar to NCAA in killing the ball even though it was interfered with by a retired runner? But OBR returns all runners?

Remember the Texas Toronto ALDS where F2's throw hit the batters bat between pitches and a run scored? Comparing apples to oranges but just because the defense was hindered doesn't always mean interference. 

Link to comment
Share on other sites

11 hours ago, Jimurray said:

@Senor Azul might tell us more from 2016 BRD. But if you call nothing what do you do if the runners start to go on the hindrance? When the rule/interp was changed the MLBUM called it a dropped third strike. That is imprecise language unless they mean any third strike that the catcher put on the ground, with no qualifier regarding whether the batter could run. The latest rule calls it an uncaught third strike. Is OBR similar to NCAA in killing the ball even though it was interfered with by a retired runner? But OBR returns all runners?

The only reason for the wording change from "dropped" to 'uncaught" was to address the pitch that skipped into the catcher's glove and the catcher "caught" the skipped pitch.  Some were improperly arguing that this was NOT a dropped third strike since the catcher never dropped the ball.

 

Note that the rule in question refers to a BR.  There is no BR in the OP.

Link to comment
Share on other sites

4 hours ago, noumpere said:

The only reason for the wording change from "dropped" to 'uncaught" was to address the pitch that skipped into the catcher's glove and the catcher "caught" the skipped pitch.  Some were improperly arguing that this was NOT a dropped third strike since the catcher never dropped the ball.

 

Note that the rule in question refers to a BR.  There is no BR in the OP.

That cinches it for me. Live ball.

  • Like 1
Link to comment
Share on other sites

I, like Mr. Jimurray, am convinced it would be a live ball under OBR thanks to another helpful clue from Mr. noumpere. But I do not agree with the rule cited. I think the applicable rule would be:

6.01 Interference, Obstruction, and Catcher Collisions

(a) (7.09) Batter or Runner Interference

It is interference by a batter or a runner when:

(5) Any batter or runner who has just been put out, or any runner who has just scored, hinders or impedes any following play being made on a runner. Such runner shall be declared out for the interference of his teammate (see Rule 6.01(j));

Here’s a case play taken from the 2016 BRD (section 349, p. 233):

Play 213-349:  R1, 1 out, 2-2 count. The next pitch is in the dirt, B1 swings and misses for strike three, the ball bounces off the catcher, and BR streaks for first. He kicks the ball (accidentally) and makes it safely to first as R1 pulls up at second.  Ruling:  At every level, BR is out:  First is occupied with fewer than two outs. In FED, R1 returns TOI. In NCAA, he also returns since he was not stealing. In OBR, R1 is out.

 

So none of the choices offered in the NCAA question in the OP would be a proper answer for OBR.

Link to comment
Share on other sites


×
×
  • Create New...