The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Baseball (https://forum.officiating.com/baseball/)
-   -   Intentionally Deviating to Add Difficulty (https://forum.officiating.com/baseball/92686-intentionally-deviating-add-difficulty.html)

Manny A Wed Oct 17, 2012 01:55pm

Intentionally Deviating to Add Difficulty
 
I'm not sure how many of you happened to see a play between Detroit and New York involving Ichiro. I can't recall which game it was, but the situation was this: Ichiro was on second base, and someone hit a ground ball to the shortstop, who was playing deep. Ichiro, against common practice, took off for third. The shortstop decided to throw to first instead to retire the BR.

During the play (which was highlighted by an announcer during a replay), Ichiro started running straight to third from second. But then he deviated to his right and ran in an arc towards third base, essentially putting himself between the shortstop and third to add to the difficulty of any potential throw.

If the shortstop had thrown the ball to third and hit Ichiro in the back, would you consider an interference call under 7.08(b)? Why or why not?

kylejt Wed Oct 17, 2012 02:01pm

I think I would only call it if the runner intentionally got in way of the player actively gloving the ball. Other than that, it's just great baserunning by one of the smartest players ever to lace up a cleat.

nopachunts Wed Oct 17, 2012 02:07pm

And I think it would be hard to say he did it intentionally with his back to the SS. He would not have any idea what the track of the throw to F5 is going to be.

Totally agree with KyleJT. Smart base running.

Manny A Wed Oct 17, 2012 02:57pm

Yeah, I feel the same way.

I just find it interesting how a BR is required to stay in a runner's lane when going the last half distance from home to first. But a runner is free to knowingly place himself where he may force the fielder to alter his throw anywhere else along the bases.

RPatrino Wed Oct 17, 2012 02:57pm

In school we were taught to always loop when approaching a base in order to not have to deviate too far from the straight line between bases. Perhaps that is a lost art?

MD Longhorn Wed Oct 17, 2012 03:55pm

Quote:

Originally Posted by RPatrino (Post 858783)
In school we were taught to always loop when approaching a base in order to not have to deviate too far from the straight line between bases. Perhaps that is a lost art?

Huh? You mean ROUNDING a base... like every player from 12U up to the major leagues does? Lost art? I don't think so.

Manny A Thu Oct 18, 2012 09:36am

Quote:

Originally Posted by RPatrino (Post 858783)
In school we were taught to always loop when approaching a base in order to not have to deviate too far from the straight line between bases. Perhaps that is a lost art?

It was pretty obvious that what Ichiro did was not rounding. There was no way he was going to continue to home, seeing that the ball was fielded by the shortstop. Runners round bases when they anticipate they'll continue on. What Ichiro did was intentionally put himself in the perceived path of the throw.

nopachunts Thu Oct 18, 2012 11:09am

Quote:

Originally Posted by Manny A (Post 858894)
It was pretty obvious that what Ichiro did was not rounding. There was no way he was going to continue to home, seeing that the ball was fielded by the shortstop. Runners round bases when they anticipate they'll continue on. What Ichiro did was intentionally put himself in the perceived path of the throw.

When I was coaching and I had a runner coming to third, he was paying attention to the 3BC as to slide, come in standing, or head for home. If the SS fielded the ball and was throwing to 1B or 2B, I had my players ready to go home in case of an overthrow. I imagine he was doing the same thing. Again smart base running.

MD Longhorn Thu Oct 18, 2012 11:19am

Quote:

Originally Posted by nopachunts (Post 858930)
When I was coaching and I had a runner coming to third, he was paying attention to the 3BC as to slide, come in standing, or head for home. If the SS fielded the ball and was throwing to 1B or 2B, I had my players ready to go home in case of an overthrow. I imagine he was doing the same thing. Again smart base running.

You imagine he was beginning a round of third base before reaching the shortstop? Really? (If this is what you are coaching, you're wasting several steps for them).

Rich Ives Thu Oct 18, 2012 03:43pm

Weren't you taught to run toward the glove side of the fielder when the ball's coming from behind? That's pretty much SOP in baseball.

David B Fri Oct 19, 2012 08:31am

Quote:

Originally Posted by Rich Ives (Post 859006)
Weren't you taught to run toward the glove side of the fielder when the ball's coming from behind? That's pretty much SOP in baseball.

Exactly. So much of this is not done today because players simply aren't taught these things - they simply rely on talent.

Thanks
DAvid

dash_riprock Fri Oct 19, 2012 08:41am

Quote:

Originally Posted by Rich Ives (Post 859006)
Weren't you taught to run toward the glove side of the fielder when the ball's coming from behind? That's pretty much SOP in baseball.

Indeed I was. Ratology 101.

Rich Ives Fri Oct 19, 2012 09:12am

Quote:

Originally Posted by Manny A (Post 858782)
Yeah, I feel the same way.

I just find it interesting how a BR is required to stay in a runner's lane when going the last half distance from home to first. But a runner is free to knowingly place himself where he may force the fielder to alter his throw anywhere else along the bases.

I think that's pretty much to keep the runner from blindsiding the fielder when the throw is coming from somewhere other than the HP area. And yes, the PBUC ruled that the throw can be coming from anywhere - because the rule doesn't limit it. If I recall CC's resulting rant correctly, they even wrote that they didn't want the runner crashing the fielder in the note they sent to CC.

dash_riprock Fri Oct 19, 2012 09:36am

A runner is not immune to intentional interference with a thrown ball just because the throw is coming from behind him and he can't see the ball.

Rich Ives Fri Oct 19, 2012 11:12am

Quote:

Originally Posted by dash_riprock (Post 859089)
A runner is not immune to intentional interference with a thrown ball just because the throw is coming from behind him and he can't see the ball.

By rule if out of the lane at first. But otherwise how could you sell an INT call on a throw the runner couldn't see? Maybe if he was waving his arms wildly in the air - but just running? Can a fielder deliberately hit the runner to try to get an INT call? Would he survive after doing that?

Throws hit runners as they are going into bases regularly. Never gets called. No one expects it to get called.

It's tossing out these "well maybe on the second Tuesday of the week when the moon is full" remote possibilities that get beginners thinking they can call it on a whim. It's counterproductive.

Manny A Fri Oct 19, 2012 11:36am

Quote:

Originally Posted by Rich Ives (Post 859126)
By rule if out of the lane at first. But otherwise how could you sell an INT call on a throw the runner couldn't see? Maybe if he was waving his arms wildly in the air - but just running? Can a fielder deliberately hit the runner to try to get an INT call? Would he survive after doing that?

Throws hit runners as they are going into bases regularly. Never gets called. No one expects it to get called.

It's tossing out these "well maybe on the second Tuesday of the week when the moon is full" remote possibilities that get beginners thinking they can call it on a whim. It's counterproductive.

By rule, interference with a thrown ball requires intent. I agree that in most cases, intent is hard to prove if the runner isn't actively doing something out of the ordinary, such as waving the arms as you've stated.

But couldn't you judge intent to interfere if the runner starts running straight for the base, and suddenly pulls a 45-degree turn to place himself in the perceived path of the throw? If it's something that blatantly obvious, why should he be given the benefit of the doubt just because he can't see the ball?

jicecone Fri Oct 19, 2012 12:05pm

Quote:

Originally Posted by Manny A (Post 859133)
But couldn't you judge intent to interfere if the runner starts running straight for the base, and suddenly pulls a 45-degree turn to place himself in the perceived path of the throw? If it's something that blatantly obvious, why should he be given the benefit of the doubt just because he can't see the ball?

No, that is called inserting yourself into a game because you do not have a clear understanding of the rule and its meaning. I am talking in general and not directing it to you Manny.

The rules allow the runner, to run whereever they feel like, unless there are conditions restricting that, such as a fielder with possesion and waiting to make a tag or RLI at first.

Now , your allowed to make a judgement about whatever you feel like but, your career as an official may be shortlived if you were to make and inteference call for this situation.

dash_riprock Fri Oct 19, 2012 12:25pm

Quote:

Originally Posted by Rich Ives (Post 859126)
By rule if out of the lane at first. But otherwise how could you sell an INT call on a throw the runner couldn't see? Maybe if he was waving his arms wildly in the air - but just running? Can a fielder deliberately hit the runner to try to get an INT call? Would he survive after doing that?

Throws hit runners as they are going into bases regularly. Never gets called. No one expects it to get called.

It's tossing out these "well maybe on the second Tuesday of the week when the moon is full" remote possibilities that get beginners thinking they can call it on a whim. It's counterproductive.

Although I have never had the occasion to call it, if a runner goes out of his way to run at the glove and I am convinced he is intentionally trying to interfere with the throw, I will call it.

Steven Tyler Sat Oct 20, 2012 01:17am

Quote:

Originally Posted by Rich Ives (Post 859006)
Weren't you taught to run toward the glove side of the fielder when the ball's coming from behind? That's pretty much SOP in baseball.

When running the bases, I can pretty much tell by the fielder's eyes, and reactions as to where the throw is going.

johnnyg08 Sat Oct 20, 2012 08:15am

Quote:

Originally Posted by dash_riprock (Post 859154)
Although I have never had the occasion to call it, if a runner goes out of his way to run at the glove and I am convinced he is intentionally trying to interfere with the throw, I will call it.

Cruddy end of the stick. no?

dash_riprock Sat Oct 20, 2012 08:36am

Quote:

Originally Posted by johnnyg08 (Post 859260)
Cruddy end of the stick. no?

If enforcing the penalty for intentional interference with a thrown ball is the cruddy end of the stick, then so be it.

Don't get me wrong - I am not advocating calling INT any time a runner slides or runs toward the glove. All the benefit of any doubt goes to the runner. But if a runner deviates from his path in such a way that convinces me his only purpose in doing so is to interfere, then I'm busting him for it.

jicecone Sat Oct 20, 2012 08:55am

Quote:

Originally Posted by dash_riprock (Post 859261)
If enforcing the penalty for intentional interference with a thrown ball is the cruddy end of the stick, then so be it.

Don't get me wrong - I am not advocating calling INT any time a runner slides or runs toward the glove. All the benefit of any doubt goes to the runner. But if a runner deviates from his path in such a way that convinces me his only purpose in doing so is to interfere, then I'm busting him for it.

You may be right if, you could ACCURATELY and CORRECTLY discern that "his only purpose in doing so is to interfere". However, I question any officials ability to make that decision on the field. It would have to be SOOOOOO obvious.

Then again, I do not know your abilities, and just, about anything is possible.

dash_riprock Sat Oct 20, 2012 11:19am

There are numerous rules that require the umpire to determine intent.


All times are GMT -5. The time now is 10:25pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1