Quote:
Originally Posted by Rich
PLAY: Ball hit down the line. F9 touches it in fair ground (let's say right over the foul line), takes four or five more steps clearly into foul ground in an attempt to stop, loses his footing and falls (or crashes into the wall/fence), and the ball comes out.
NOW try selling that this was a fair ball.
The reason we signal fair/foul first is because that's what's ALWAYS decided first. It's not caught until all the elements of a catch are present, but it's fair/foul immediately.
|
Your last sentence makes sense
from an umpire's perspective, and is probably the explanation as to why the mechanic is taught that way.
But even with the play you describe the runner will be far more concerned if the catch was made or not. It's just that in your example play - there is so much intervening time between the determination of fair/foul and catch/no-catch, it only makes sense to call it in that order.
Imagine you are the runner at 3rd on this play. As soon as you see the fair signal, are you going to dash home? No! Because you have to wait until the catch/no-catch signal is made. I'm not saying fair or foul isn't important. It is! But for marginal catches, the runners are primarily going to be concerned with the catch/no-catch call. You can take off running on a foul ball - and the worst that will happen is that they call you back; so the runners do not have to be concerned with whether a ball is fair or foul.
Yet, I think your explanation makes
perfect sense and I think it
does explain why the mechanic is why it is. Thanks!