Does runner return to first....

[12-6 curve]

A 12u batter throws bat after hitting ball and is receives a warning. Same batter comes up again with runner on 1st. Batter hits ball and throws bat again. Batter is called out. Should umpire call dead ball immediately, batter is out, and then direct base runner to return to 1st?

[Jay R.]

Talk to the league about what rule and mechanics they have in place. 

I am unaware of any major rules code having support for calling a batter out for unintentionally throwing the bat. Little League and NFHS both choose to eject (or have the coach remove) the offender. 

It is, however, a popular local rule. I am yet to see even written versions of this rule specify when the batter should be called out. 

I think the most common application (and what I do when leagues want me to call offenders out) is to treat it as a form of interference, on the grounds that it prevents the catcher from fully participating in the play. All interference is an immediate dead ball, the offender is out, and no runners may advance. 

[12-6 curve]

Thank you, that helps.

[beerguy55]

1 hour ago, Jay R. said:

It is, however, a popular local rule. I am yet to see even written versions of this rule specify when the batter should be called out. 

Yeah - it becomes an interesting argument when the coach says, "there is no rule for a batter being called out for throwing his bat...you're supposed to eje...uhmm...never mind."

I do agree with you in my experience, with all the talk about local bi-laws, for all the leagues, communities, tournaments I've coached and played in over the past 40 years, I've yet to see this in print - everyone talks about it, and is sure it was discussed at some pre-season/pre-tournament meeting, but in the end  you're left with an umpire who either doesn't know the rules, is on a power trip, or, most likely, feels he must do "something" and thinks kicking an 8-year old out of the game is a bit harsh.

[Jay R.]

At least one of the local leagues I work with has it in writing that the batter is out if the same batter does it multiple times in a game. They do not, however, say in the rules sheet whether it's interference and immediate dead ball, or whether the result of the batted ball should otherwise stand.

[beerguy55]

1 hour ago, Jay R. said:

They do not, however, say in the rules sheet whether it's interference and immediate dead ball, or whether the result of the batted ball should otherwise stand

Of course it doesn't - why would they want to take culpability and think it through to its proper conclusion?  Their goal is to "do something"...they don't really care if that "something" is stupid.  These are the people who end up in Congress.

[BigBlue4u]

10 hours ago, 12-6 curve said:

A 12u batter throws bat after hitting ball and is receives a warning. Same batter comes up again with runner on 1st. Batter hits ball and throws bat again. Batter is called out. Should umpire call dead ball immediately, batter is out, and then direct base runner to return to 1st?

I ejected a batter for throwing his bat during a tournament.  I did nothing the first time, The second time, it appeared he was throwing his bat to gain momentum running to first base.  I then warned the coach if the batter threw his bat again, he would be ejected.  He did throw it again and he was ejected. Nobody complained.  If his coach took exception to the call, I would have used that old standby, "for safety reasons."

[MadMax]

On 5/28/2026 at 9:16 AM, Jay R. said:

I am unaware of any major rules code having support for calling a batter out for unintentionally throwing the bat. Little League and NFHS both choose to eject (or have the coach remove) the offender.

No worries, you're correct – there isn't. Anywhere. 

 

On 5/28/2026 at 9:16 AM, Jay R. said:

It is, however, a popular local rule. I am yet to see even written versions of this rule specify when the batter should be called out.

Again, you're not going to find it. It's a feral, completely contrived and improvised "rule" based off an emotional response – "Oh! That bat flung into the catcher's shinguards isn't supposed to happen! That could have hurt him! I must stop that! I must... <beat>... dispense justice!!!"

"... but... "

"... ~ I don't wanna eject a little kid and be confronted / accused / labeled as Big Bad Blue, that monster! That would hurt his feelings!... and mine!~"

On 5/28/2026 at 10:21 AM, beerguy55 said:

I've coached and played in over the past 40 years, I've yet to see this in print - everyone talks about it, and is sure it was discussed at some pre-season/pre-tournament meeting, but in the end  you're left with an umpire who either doesn't know the rules, is on a power trip, or, most likely, feels he must do "something" and thinks kicking an 8-year old out of the game is a bit harsh.

Exactly.

And, we haven't even addressed the inherent inconsistency of the rule's "application"... immediate dead ball? Why? Delayed dead ball? Why? We're trying so freakin' hard to "teach that kid a lesson", but have we thought about what / how that teaches baseball to the other kids, and their play(s)? Are we truly lumping it into INT? How? How does that affect any other play(s) upon or regarding the ball? Are we calling the Out on any release of the bat? Why? So only if it hits the catcher? What if it hits us (the umpire)? What if a kid is trying to imitate a bat-flip? Calling an Out for that? Where's the rule or precedent for that??

Ya just didn't open Pandora's box, you obliterated it. 

At least – at the very least – by Ejecting the kid (or removing him from the game), you do so at the completion of the play, and all the other things the kids do on that play, by both sides, remains in place.