View Single Post
  #4 (permalink)  
Old Sun Apr 03, 2005, 12:47am
Carl Childress Carl Childress is offline
Official Forum Member
 
Join Date: Aug 2000
Location: Edinburg, TX
Posts: 1,212
Send a message via ICQ to Carl Childress
Quote:
Originally posted by cowbyfan1
Quote:
Originally posted by bob jenkins
It's a FPSR violation so the run doesn't count, the BR is also declared out and all other runners return. See 8.4.2Y

Ok I have no problem with that as that is a typical FPSR, but what about the runner who crosses home and is not having a play made on him. Say he just bowls over the catcher who is just standing behind home?
Also the play you mentioned the force is not removed there, lease the way I am reading it, as R3 still had not scored when he initiated the malicious contact.
Check out the citations given in the BRD, Section 319.

3-3-1n: Runner maliciously crashes into a fielder: "The umpire shall eject the offender from the game. The ejected player is declared out unless he has already scored." [my emphasis] So he is NEVER out if he has scored

EXCEPT

If he violates 8-4-2b: "A runner is out if he does not slide and causes illegal contact." Penalty: "On a force-play slide with less than two outs, the runner is declared out."

It's unfortunate that 8.4.2Y (a) and (b) both occur with the bases loaded. Try this play, though:

B1 and F2 exchange words on an inside pitch that almost nicks B1. He then doubles and intends to score on a single to right. He does make the plate [not a force play, so there can be no violation of FPSR] and after scoring maliciously contacts the catcher. He is ejected. But his run scores.

What may be confusing you is there are TWO rules in play: FPSR and Malicious contact.
__________________
Papa C
My website
Reply With Quote