The Official Forum  

Go Back   The Official Forum > Baseball
Register FAQ Community Calendar Today's Posts Search

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old Mon Feb 26, 2007, 12:13am
Official Forum Member
 
Join Date: Dec 2006
Posts: 60
Arrow Malicious Contact Rule Help

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!
Reply With Quote
  #2 (permalink)  
Old Mon Feb 26, 2007, 12:29am
Official Forum Member
 
Join Date: Apr 2005
Posts: 2,057
Send a message via Yahoo to UmpJM
Cool

blindofficial,

He IS ejected (when the play is over) - he's just not out.

Because he has already scored and the malicious contact does not nullify his run or "retroactively" make him out.

JM
__________________
Finally, be courteous, impartial and firm, and so compel respect from all.
Reply With Quote
  #3 (permalink)  
Old Mon Feb 26, 2007, 12:32am
Official Forum Member
 
Join Date: Jun 2005
Location: USA
Posts: 1,577
Good question

He may be ejected, but he may not be declared out if he has already scored.

Here is an interesting video.
http://www.youtube.com/watch?v=E1lHspk6IVM
Careful if video is not HS or NCAA game.
Notice how many members of the offense leave the dugout to converge behind the circle.

Last edited by SAump; Mon Feb 26, 2007 at 12:36am.
Reply With Quote
  #4 (permalink)  
Old Mon Feb 26, 2007, 12:48am
Official Forum Member
 
Join Date: Aug 2000
Location: Spokane, WA
Posts: 4,222
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!
The phase "unless he has already scored" refers to "and declared out", and not to "The player is ejected."
__________________
GB
Reply With Quote
  #5 (permalink)  
Old Mon Feb 26, 2007, 01:45am
Official Forum Member
 
Join Date: Dec 2006
Posts: 60
Question

Quote:
Originally Posted by CoachJM
blindofficial,

He IS ejected (when the play is over) - he's just not out.

Because he has already scored and the malicious contact does not nullify his run or "retroactively" make him out.

JM
So that being said, do you see alot of that? Meaning, I imagine one player would do this to score a run to "take one for the team." I guess I don't understand why the run would count if the player will be ejected for doing a "malicious act."
Reply With Quote
  #6 (permalink)  
Old Mon Feb 26, 2007, 01:51am
Official Forum Member
 
Join Date: Aug 2000
Location: Spokane, WA
Posts: 4,222
Quote:
Originally Posted by blindofficial
So that being said, do you see alot of that? Meaning, I imagine one player would do this to score a run to "take one for the team." I guess I don't understand why the run would count if the player will be ejected for doing a "malicious act."
Read it again, carefully. It says unless he has ALREADY scored. Scoring came before the malicious act, therefore the ejection is the appropriate penalty and the run scores. Why would you penalize a legal act that occured prior to the illegal act?

The kid is getting tossed for the crime he committed. What more do you think should happen?
__________________
GB
Reply With Quote
  #7 (permalink)  
Old Mon Feb 26, 2007, 03:31am
Official Forum Member
 
Join Date: Jan 2007
Location: SW Kansas
Posts: 728
Easy breakdown:

I punch you in the face before scoring: I'm out and ejected.

I punch you in the face after scoring: I scored and I'm ejected.
Reply With Quote
  #8 (permalink)  
Old Mon Feb 26, 2007, 04:13am
Official Forum Member
 
Join Date: Dec 2006
Posts: 60
Quote:
Originally Posted by DonInKansas
Easy breakdown:

I punch you in the face before scoring: I'm out and ejected.

I punch you in the face after scoring: I scored and I'm ejected.
Got it! I looked into way too much. I was thinking a the runner was the same one that did the act AND having the score count when he scored. I was thinking the score counted when he crossed the plate, but afterwards got ejected.... Rookie mistake!
Reply With Quote
  #9 (permalink)  
Old Mon Feb 26, 2007, 08:51am
Official Forum Member
 
Join Date: Jan 2002
Location: Birmingham, Alabama
Posts: 3,100
The phase "unless he has already scored" refers to "and declared out", and not to "The player is ejected."

100% correct. Therefore:

"if on offense, the player is ejected and, UNLESS he has already scored, declared out."
__________________
greymule
More whiskey—and fresh horses for my men!
Roll Tide!
Reply With Quote
  #10 (permalink)  
Old Mon Feb 26, 2007, 09:59am
rei
Guest
 
Posts: n/a
Quote:
Originally Posted by greymule
[B]"if on offense, the player is ejected and, UNLESS he has already scored, declared out."
You would think all of those english majors at NFHS rules committee would have worded it that way eh?
Reply With Quote
  #11 (permalink)  
Old Mon Feb 26, 2007, 10:07am
Official Forum Member
 
Join Date: Aug 2000
Location: Newburgh NY
Posts: 1,822
Quote:
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
__________________
Peter M. Booth
Reply With Quote
  #12 (permalink)  
Old Mon Feb 26, 2007, 07:22pm
Registered User
 
Join Date: May 2005
Posts: 21
How about this twist to the situation

Not infrequently, malicious contact occurs in conjunction with obstruction. For example, the catcher is four or five feet up the line without the ball and the the runner collides with him barreling for home.

Now, according to this discussion, the runner is out/ejected and the run does not score. However, what about the obstruction on the part of the catcher? Why is the obstruction infraction not punished also?

Why, then, would it not be malicious contact, but awarded home on the obstruction, THEN ejected for the malicious contact?
Reply With Quote
  #13 (permalink)  
Old Mon Feb 26, 2007, 08:30pm
Official Forum Member
 
Join Date: Apr 2005
Posts: 2,057
Send a message via Yahoo to UmpJM
Cool

NickG,

FED has decided that they really want to discourage malicious contact.

Hence, in the situation you describe, the malicious contact "trumps" the obstruction, and the obstruction is ignored - by rule.

JM
__________________
Finally, be courteous, impartial and firm, and so compel respect from all.
Reply With Quote
  #14 (permalink)  
Old Mon Feb 26, 2007, 09:18pm
Official Forum Member
 
Join Date: May 2005
Posts: 1,226
Quote:
Originally Posted by NickG
Why, then, would it not be malicious contact, but awarded home on the obstruction, THEN ejected for the malicious contact?
If i'm not mistaken, this is the NCAA interp.

FED, by rule, MC superscedes obstruction always.


ps- the new FED defensive MC rule is pretty darn stupid IMO
Reply With Quote
  #15 (permalink)  
Old Mon Feb 26, 2007, 10:17pm
DG DG is offline
Official Forum Member
 
Join Date: Feb 2004
Location: North Carolina
Posts: 4,022
Quote:
Originally Posted by bossman72
If i'm not mistaken, this is the NCAA interp.

ps- the new FED defensive MC rule is pretty darn stupid IMO
That is correct for NCAA, runner would be awarded the base on obstruction and then ejected.

What's stupid about a defensive player creating MC and being ejected for it?
Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On


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


All times are GMT -5. The time now is 12:37pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1