Skip to main content

My son is playing in a local league that follows the NFHS rules. It's a 10-12 year old league.  I'm a complete neophyte when it comes to baseball and we had some calls at last nights game that I didn't understand. I'm hoping that someone here can explain because it's still bothering me.

 

1. Bases loaded. Batter hits grounder which pitcher gets.  Catcher is just behind home and receives throw from pitcher.  Runner comes in from third and takes the catcher down.  Think " League of their Own" but catcher holds onto the ball.  Ump calls the runner safe.  Coach challenges saying he should have slid, but ump says " call remains".  We had a previous ump who said the kids must slide if it's a close play or they are out.  Which is it?

 

2. Batter bunts and runs to first.  First baseman is standing at base on line in runners way waiting for catch. Runner sidesteps to get on base.  Runner called out for being " outside the baseline".   Is he supposed to run the guy over?

 

3. Batter hits fly ball which pitcher moves forward to catch (midway between mound and HP)  It hits his glove and goes foul.  Ump calls foul. Both coaches disagree. But ump says foul and play on. Why?

 

The ump refused to explain his rulings which is unusual at this level.  

 

Sorry if this is basic stuff but my son wants to understand what happened and I don't get it.

 

Original Post

Replies sorted oldest to newest

I'll give short answers. An umpire can provide the sections and details. My responses are based on not seeing the play along with your potential bias on each situation.

 

1) The runner doesn't have to slide. But he can't intentionally make contact.

 

2) The runner is entitled to the baseline. The runner showed good judgement avoiding a collision. The umpire showed poor judgment. Is it possible the runner was not in the base runner's box (which is often not chalked off and left to umpires judgment)?

 

3) It's a fair ball. It was touched in fair territory. Another mistake inexperienced umpires make is calls along the foul line. It's were the ball is positioned not the player.

Last edited by RJM

Agilemom,

Welcome to the site.  There is another factor that is likely in play here - local youth leagues, including 10-12 y.o. age range, typically have entry level umpires, even kids in many cases, or volunteer dads.  Sounds like this is what you were dealing with.  If you are expecting these games to be officiated on the level of HS and above, you are in for a lot of unnecessary disappointment.  Let the coaches deal with the issues as best they can.  Understand that the young umpire is someone's son, just trying to do his best.  Explain to your son that they will make mistakes just like he will when he is playing.  Sit back and enjoy the game of youth baseball, imperfections and all.

Last edited by cabbagedad

That is part of the issue.  This wasn't a kid.  50 something Ump who works professionally in the area.  It might be more understandable if it was a kid (which we do have sometimes).  But usually, the Umps will explain their rulings when questioned.

 

If the coaches(volunteers) are confused by the calls and can't explain it to the kids- how are the kids supposed to learn the rules?

 

Since we've been told different things (especially about the catcher/runner issue) I'm just wondering what the actual rules say so that if we run into it again we know.

Originally Posted by Agilemom:

My son is playing in a local league that follows the NFHS rules. It's a 10-12 year old league.  I'm a complete neophyte when it comes to baseball and we had some calls at last nights game that I didn't understand. I'm hoping that someone here can explain because it's still bothering me.

 

1. Bases loaded. Batter hits grounder which pitcher gets.  Catcher is just behind home and receives throw from pitcher.  Runner comes in from third and takes the catcher down.  Think " League of their Own" but catcher holds onto the ball.  Ump calls the runner safe.  Coach challenges saying he should have slid, but ump says " call remains".  We had a previous ump who said the kids must slide if it's a close play or they are out.  Which is it?

 

You do not HAVE to slide under NFHS but there may also be a local rule that requires it.  We won't know the answer to this.  Hard to really say what should have been called without seeing it.  It could have been part of the action in which case you can call him safe although the catcher holding the ball makes one think there was a tag but it's possible there may not have been one.  On the other hand it could possibly be malicious contact on the runner.  He's out and ejected.  Really hard to say without seeing it.

 

2. Batter bunts and runs to first.  First baseman is standing at base on line in runners way waiting for catch. Runner sidesteps to get on base.  Runner called out for being " outside the baseline".   Is he supposed to run the guy over?

 

Another hard one to tell without seeing it.  Was there a running lane?  Does the 1B allow a path to the base?  The base is fair but the running lane is foul so at some point the runner has to come into fair territory which gets them out of the baseline per se.  Fielders are not allowed to block the base without the ball.  Even if the throw is on it's way but not yet caught the fielder cannot block the base under NFHS (pretty sure that's correct).  So you could have obstruction on the fielder for not allowing the runner access to the base or you could have nothing.

 

3. Batter hits fly ball which pitcher moves forward to catch (midway between mound and HP)  It hits his glove and goes foul.  Ump calls foul. Both coaches disagree. But ump says foul and play on. Why?

 

Holy cow he butchered this one.  Once the ball made contact with the fielder while the ball is in fair territory (obviously it was if it was in front of the plate halfway to the mound) then it's fair.  One thing you will hear from people who don't know the rules in these situations is "his feet were in fair territory when he dropped the ball".  Feet have nothing to do with it - it's where the ball is in relation to the foul line.  For example - pop up up the 3B line.  Catcher comes out and has to lean back to try and catch it.  His heels are just on the foul side of the line but his body is in fair territory.  Odds are this ball is fair because when contact was made the catcher's body was leaning back into fair territory although his feet were foul.  Football is the sport where your feet matter in terms of catch no catch.

 

The ump refused to explain his rulings which is unusual at this level.  

 

It doesn't matter what level - the ump has to explain his ruling if he wants to keep control of the game.  Once you get to HS and above if the coach doesn't know why a call is made it can get ugly.

 

Sorry if this is basic stuff but my son wants to understand what happened and I don't get it.

 

It is somewhat basic stuff but he's at the age where he needs to learn this.  We all started somewhere and it was the basics.  It makes it tougher when the ump either doesn't know what's going on or doesn't explain why.  Like someone said earlier - don't expect the best umps to be at these games.  The umpiring gets better as you go up in levels.

 

 

Originally Posted by Agilemom:

Since we've been told different things (especially about the catcher/runner issue) I'm just wondering what the actual rules say so that if we run into it again we know.

 

Federation rules prohibit what they call "malicious contact," which occurs when a player initiates contact with more force than necessary or an intent to injure another player.  The rules don't prohibit incidental contact, but they come down hard on players who try to run over or drill or hurt other players.  

 

When a runner does it to a fielder, it is an immediate dead ball, the runner is out (even if he otherwise would have been safe and even if there would have been obstruction on the fielder), and the offender is ejected. 

 

I didn't see the play and I never watched the movie, but if the runner initiated contact above the catcher's waist and knocked him over, there's a good likelihood malicious contact should have been called.  

 

This rule gets a lot of emphasis because they are trying hard to prevent those runner-catcher collisions.   

 

Even though this scenario discusses a runner, the rules also punish fielders who are too forceful in the performance of their duties.  

Originally Posted by Agilemom:

That is part of the issue.  This wasn't a kid.  50 something Ump who works professionally in the area....

Well, I sure guessed wrong on that one.  Something doesn't add up though.  An ump who works professionally would never miss one as seemingly obvious as the fly ball hit between home and the mound that hit the P's glove... unless he didn't see it hit the glove and thought it just spun foul, in which case he would be correct.

Last edited by cabbagedad
Originally Posted by coach2709:
Originally Posted by Agilemom:

My son is playing in a local league that follows the NFHS rules. It's a 10-12 year old league.  I'm a complete neophyte when it comes to baseball and we had some calls at last nights game that I didn't understand. I'm hoping that someone here can explain because it's still bothering me.

 

1. Bases loaded. Batter hits grounder which pitcher gets.  Catcher is just behind home and receives throw from pitcher.  Runner comes in from third and takes the catcher down.  Think " League of their Own" but catcher holds onto the ball.  Ump calls the runner safe.  Coach challenges saying he should have slid, but ump says " call remains".  We had a previous ump who said the kids must slide if it's a close play or they are out.  Which is it?

 

You do not HAVE to slide under NFHS but there may also be a local rule that requires it.  We won't know the answer to this.  Hard to really say what should have been called without seeing it.  It could have been part of the action in which case you can call him safe although the catcher holding the ball makes one think there was a tag but it's possible there may not have been one.  On the other hand it could possibly be malicious contact on the runner.  He's out and ejected.  Really hard to say without seeing it.

 

 

Since the bases were loaded, the Force Play Slide Rule (FPSR) comes into play.  While the runner does not need to slide, if he does not do so and makes contact with the fielder, the runner will be out, so will the Batter-Runner, and other runners will return.

 

(In addition, the slide must be directly to the base (or away from the fielder).  If the runner goes in the direction of the fielder, the penalty applies.  If the runner goes through the base and THEN makes contact, the penalty applies).

Thank you for all your responses and the information.  The rest of the story, in case you are interested, is that our coach called it a "series of bad calls" but we all suspected some biased but were trying to be good sports during the game.

 

The Ump is hired by the home team, and we were the visitors. We only had one ump, opposed to the normal 2, but it happens.  It started out subtle with a bat inspection, of only our team bats.  When our runner stole 2nd the ump watched until the batter was completely upright on the bag to be sure he didn't step off base while getting up from slide.  When their runner stole 2nd & slid, he called safe and turned away immediately.

 

It became more obvious each inning, ending with these last three calls that were the biggest of the game.  In the bunt occurrence at first, the first baseman was standing directly in the runners path waiting for the ball. Our runner had to step around or run him over. 

 

 

From what has been posted here, I'm guessing that he didn't find the collision at home as malicious, but likely a different ump might have.  Catcher ended up flat on his back with the wind knocked out of him.  Had to have a back up come in.

 

I have a coworker who is a coach (same league different city team) that is considering putting the Ump on his "will not play under list" ( you can list two umps per season) because this team has won every home game under this ump (always with just the single ump)- and lost every away game anyone else.

 

 

Again thanks for the information.

Last edited by Agilemom

Don't get caught up in blaming the umpire. Some people who accuse umpires are wrong. You don't want to jump on that band wagon. Baseball can be a long journey for some kids and parents. There are a lot better things to focus on and develop (skills, temperment, passion) than worrying about umpires. Besides, umpires can't help it if they're blind.

Originally Posted by RJM:

Don't get caught up in blaming the umpire. Some people who accuse umpires are wrong. You don't want to jump on that band wagon. Baseball can be a long journey for some kids and parents. There are a lot better things to focus on and develop (skills, temperment, passion) than worrying about umpires...

+1

 

I hope you hang around this site as your son continues with baseball.  It can be very helpful with providing a good perspective from those who have been down the road before you and wish they hadn't had to learn from their own mistakes

I would add that the runner going to first doesn't have to stay in the running lane as long as he doesn't obstruct the first baseman. Simply being in fair territory or foul outside of the running lane is no violation. If it were, every kid with a clear single or double who "bubbles" as he rounds first would be out.

Originally Posted by noumpere:
Originally Posted by roothog66:

I would add that the runner going to first doesn't have to stay in the running lane as long as he doesn't obstruct the first baseman.

It's impossible for the BR to obstruct the first baseman. 

 

 


Arrgh! I always screw that one up. Obstruction being the usual term for an offense by the defense, I've never understood why they use the term Catcher's Interference rather than Catcher's Obstruction.

Add Reply

×
×
×
×
Link copied to your clipboard.
×