Malicious Contact Rule Help

PeteBooth · #8 (**permalink**) Mon Feb 26, 2007, 10:07am

Quote:

Originally Posted by blindofficial

Ok maybe I'm not reading this right, but I don't get part of this rule:

Malicious contact on offense pently:
"if on offense, the player is ejected and declared out, UNLESS he has already scored."

That is the part I don't. Why is he not ejected, even if he scored? Isn't the ball suppose to be dead at the moment of malicious contact and the player ejected?

Help!

There is a caveat.

As the rule states, the run scores and then the player ejected. However, if there were a Force Play situation in effect and the Runner Scored Legally but malicously contact F2, the FPSR would be in effect and 2 would be declared out. There is FED case play on this as well.

It's no different, then R1 sliding safely into second base but illegally contacts F4/F6. We would record 2 on the play.

Therefore you need to take a look at the situation meaning "is the FPSR in effect" If there was no Force Play situation in effect and R3 scored Legally but then Maliciously Contacted F2, the run counts player ejecetd.

If the FPSR is in effect, and a Player Maliciously contacts a player (even if they already scored), we record 2 on the play.

Pete Booth

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Malicious contact	SC Ump	Softball	15	Tue Mar 15, 2005 03:53pm
Malicious Contact After Scoring (Fed Only)	Blue37	Baseball	19	Tue Mar 01, 2005 10:42am
Malicious contact after scoring	DownTownTonyBrown	Baseball	41	Sun Apr 04, 2004 03:31pm
Malicious Contact	Gre144	Baseball	1	Wed Jul 04, 2001 11:42am
Malicious Contact (FED)	Gre144	Baseball	1	Tue Jun 26, 2001 09:12am