Bat Slinging

[gregm]

Last Sunday we had a tournament and I umpired the 10/under games. In this particular game I was BU. The batter, after hitting the ball, violently slung his bat into the catcher hitting him in the upper chest and arm. Immediatley after play had stopped, the Pu called time and told the OM that the next time he slung his bat he would be ejected. The catcher who got hit happened to be the DM son, who was quite upset and wanted the player to be called out. The catcher was crying and in a lot of pain and came out of the game because of this. The PU told him that an out ws not the rule, it was a warning then ejection. The PU gave him some lead way of arguing because of the circumstances. But I started easing in just in case. Just so happens, the grandfather of the batter was coaching first base (OM's team was occupying first base dugout) and he started arguing with the DM taking up for his grandson. This is when I started busting in but before I could even get there, there had been 2 ejections.
I escorted the 2 off of the field and we waited for the TD to come and send a fan (batter's aunt) out of the stands and told to leave the pemises for running her mouth.
The batter plays in our local league and last night ws their first game since the tournament. Last night I was PU. The same player, last night slung his bat and hit a catcher again. Not very hard this time though, and I issued the warning.
Althought the rules call for a warning, then ejection, would it be wrong to issue the warning to this player before he even bats, becasue of his history of doing so. I am afraid that a catcher is going to get hurt badly before he stops doing it and maybe an ejection is just the incentive he needs to do so.

[jjb]

We have a local rule that allows us to (1) warn, (2) call the BR out, or (3) eject. It simplifies it for us.

[SJC_Blue]

Greg,

You don't have to warn. If this is ongoing and you've already warned the player before, then eject the player the next time it happens. Seems to me this is the only way this player is going to correct this bad habbit.

[Dragon29]

What league &/or rule-set? Without that reference, it's hard to comment.

If it's Little League, there is no provision within the rules to call the batter out. (Even jjb's "local league" rules are, well . . . against the rules - if it's LL) The standard is to warn (though that's not absolutely necessary) and then eject; simply tell the manager that the player is a safety hazard and is therefore not allowed to play.

[gregm]

I am sorry. I umpire in Dizzy Dean. And thanks for the input already posted.

[findit99]

If a batter throws the bat straight back (hits the catcher or the umpire or slings it to the backstop straight backwards) is it appropriate to warn the entire team? "Next batter to throw the bat will be ejected!"

I'd like to hear opinions on that.

[LomUmp]

Hey all,

First offense=warning
Second offense by same player=ejection
Second offense by a different player on same team=bench warning for that team
Second offense by player on other team=bench warning for both teams
Every time after that=ejection.

LomUmp 8)

[kylejt]

If a batter throws the bat straight back (hits the catcher or the umpire or slings it to the backstop straight backwards) is it appropriate to warn the entire team? "Next batter to throw the bat will be ejected!"

I'd like to hear opinions on that.

Depends on the organization.

LL now has a new directive through their Rule Instructors Manual, available on -line. It does indeed call for a team warning, which I don't agree with.

[dtpoet]

You don't have to warn. If this is ongoing and you've already warned the player before, then eject the player the next time it happens.

Really? Do you bring other bits of history along to each game about each team? Each player? That doesn't seem to fair. I thought each game was to suppose to start with a clean slate.

Do any of you do this? I'm just curious. I just always assumed each umpire game with a clear mind.

Thanks

[kylejt]

Bench warnings are for intention acts, like beanball stuff. Not accidental releases of the stick.

Warn each player, and eject only if warranted. Try not to though, unless you think you or the catcher are truly in danger.

[dtpoet]

That's what I do kylejt. I've umpired a few 9-10 level games this year in our LL. One or two times I've had a kid fling the bat. The first kid flung it to the back stop but clearly away from F2 and myself. I did talk to his coach about it. The 2nd time up, the kid did the same thing. This time I called time and brought to kid over to where the bat was laying against the fence and explained to him directly that the bat shouldnt end up against the fence.

[TarheelUmp]

A few weeks ago I had a Mustang game 9/10 y/o and it started as a bat slinging fest. The first Inning I had two. Second Inning in the top I had another two and in the bottom I had 1 early. Each time I called time made the warning and asked the coaches to help take care of it.

Still in the bottom of the second, I had another slung bat. This one was a beauty hit me in the shin guard and the catcher in the side of the helmet. I called time and announced loudly, "This is the final warning for both teams for slung bats anybody who slings a bat will now be ejected!" Neither coach said a word back to me, and guess what ... we didn't have another slung bat.

Giving team warnings can and does work for individual infractions. I should have done it earlier.

[kylejt]

With little kids like this, I'll never, ever use the E word. There's no need to threaten the little people that you want to continue in the program.

If a kid continues to fling the bat, simply tell the manager that he's done for the day. If the manager wishes to take issue with it, quietly eject him and the bat slinger. Just don't make a big deal of it, or make LOUD threats to both benches.

Can you do it? Sure. I can also threaten to eject any catcher that lets a ball hit me too. It's just not a good idea, even though it might work.