Sunday, July 20, 2008

Outfielder, where to throw the ball w/ bases loaded

I was with my 6 yr. old son at a little league practice the other day and witnessed something that really caused some confusion with me. His team was simply practicing simulated situations and my son was in right field. The bases were loaded and the coach hit a pop up to right field. My son, Luke, hustled over near the line and caught the ball.

Then, the fun began.

Luke turned to throw the ball to someone in the infield but literally had no idea who to throw the ball to. He hesitated, hesitated some more and eventually tossed it to the 2B. A coach admonished Luke for not throwing the ball right away. But, the play was much much deeper than any little league coach could realize.

The runner at 3B tagged. The ball was not deep but with little league arms it was certainly a ball that a player could tag up on. So, the throw should go to some sort of cut man at the pitchers mound, right? In little league this very may well be the pitcher.

Here's the thing, though. The runner at 2nd left early and was near the 3B bag when the ball was caught. So, there is a potential double play waiting at 2B if the ball can be relayed back into the infield quickly enough. If the out is recorded after the runner crosses home plate, the run counts.

To make matters more complicated, when Luke looked to throw for the appeal double play no one was standing at 2B. So, I believe he wanted to record the out at 2B but there was no one there to receive the throw. Furthermore, what if someone was there? Is it worth the risk throwing it to 2B when a runner is prepared to tag at 3B?

Obviously, this situation was in a simulated game. Yet, imagine a 3-3 game in the last inning. What do you do? The runner at 3B is the winning run. The outfielder is trained to throw to that cutoff man. The only way you could actually communicate to him to throw to another base would be to do so as the ball were in the air. Quite challenging indeed considering the magnitude of the situation.

No comments: