The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Baseball (https://forum.officiating.com/baseball/)
-   -   fair/foul - then catch/no-catch (https://forum.officiating.com/baseball/94939-fair-foul-then-catch-no-catch.html)

David Emerling Fri May 03, 2013 12:20pm
fair/foul - then catch/no-catch
 
I do it because I see others do it, but I've always wondered why we do it. This is an especially prevalent mechanic in MLB.

A flyball down down the right field line. The catch is made about 5-feet into fair territory. The umpire first signals that it's fair and then signals that it's a catch.

First of all, if it's a catch, isn't the fact that it was caught in fair or foul territory irrelevant?

Secondly, shouldn't the fact that it's catch (or not) be more important than to first indicate whether it was on the fair or foul side?

Why does this odd mechanic exist?

Just curious.

Manny A Fri May 03, 2013 12:43pm
If the catch is routine, or if the no-catch is that obvious, then giving the catch/no-catch mechanic right away is not really necessary. You only need to give the immediate mechanic on a trouble ball, and in those cases, umpires rarely give both signals.

In other words, if a sinking line drive down the rightfield line is:
1. Caught in fair or foul territory, the umpire will almost always just come up with the Catch signal, and not bother signalling fair or foul
2. Trapped in fair territory, the umpire will almost always just come up with an emphatic fair mechanic
3. Trapped in foul territory, the umpire will almost always just come up with an emphatic foul call/mechanic

The only time I ever see what you describe (fair/foul signal, then catch signal) is on the routine catch. And I can only assume the signal is given to inform the scorer whether to write "F9" or "FF9" in the book. :)

Robert E. Harrison Fri May 03, 2013 01:13pm
Needed information and the order we need it.
 
The mechanic allows the runnners on base the information they need in the order they need it.
The fair or foul call is predicated upon where the ball is when it is touched. The catch no catch can be considerably later upon the fielders ability to control the ball. So with runners on, a runner may tag up and leave his base as soon as the ball is touched. I do not point fare or foul until the ball is touched or and then I wait to rule on the catch-no catch.

Rich Ives Fri May 03, 2013 01:18pm
I see them call it just about every time. A discussion on umpire.org is going on now. Everyone says call it with one exception by a person with questionable (to me at least) motivations. Those who have been to Evans' academy say he teaches to always call it.

It is especially important on a ball very near the line. It is possible to have a ball touched in the air over the line, then dropped so you see that determination just might have to happen before you know if it's caught or not.
And then everyone really needs to know and know now if it's fair or foul because it governs ensuing action.

Don't get lazy on calls. Make a call every time so you're in the habit and don't forget at a crucial time.

MD Longhorn Fri May 03, 2013 01:28pm
Quote:
Originally Posted by Manny A (Post 892801)
If the catch is routine, or if the no-catch is that obvious, then giving the catch/no-catch mechanic right away is not really necessary. You only need to give the immediate mechanic on a trouble ball, and in those cases, umpires rarely give both signals.

In other words, if a sinking line drive down the rightfield line is:
1. Caught in fair or foul territory, the umpire will almost always just come up with the Catch signal, and not bother signalling fair or foul
2. Trapped in fair territory, the umpire will almost always just come up with an emphatic fair mechanic
3. Trapped in foul territory, the umpire will almost always just come up with an emphatic foul call/mechanic

The only time I ever see what you describe (fair/foul signal, then catch signal) is on the routine catch. And I can only assume the signal is given to inform the scorer whether to write "F9" or "FF9" in the book. :)
All of this is fine if you're not being evaluated or observed that day. :)

The two signals are supposed to be given, as David said.

As to why ... which is his actual question that no one has answered, I suspect the reason no one has answered is that we don't really know. Sort of a "we do what we're told" kind of thing.

bob jenkins Fri May 03, 2013 02:01pm
Quote:
Originally Posted by Rich Ives (Post 892811)
I see them call it just about every time. A discussion on umpire.org is going on now. Everyone says call it with one exception by a person with questionable (to me at least) motivations. Those who have been to Evans' academy say he teaches to always call it.

It is especially important on a ball very near the line. It is possible to have a ball touched in the air over the line, then dropped so you see that determination just might have to happen before you know if it's caught or not.
And then everyone really needs to know and know now if it's fair or foul because it governs ensuing action.

Don't get lazy on calls. Make a call every time so you're in the habit and don't forget at a crucial time.
+1

And while the OP is right that is doesn't matter if the ball is caught (except maybe to the scorer), you won't know that the ball is caught until after you should have signaled fair/foul.

Manny A Fri May 03, 2013 02:03pm
Quote:
Originally Posted by Robert E. Harrison (Post 892809)
The mechanic allows the runnners on base the information they need in the order they need it.
What possible information does a tagging base runner gain when it comes to fair/foul? It shouldn't matter to him; the moment the ball is touched, he's running. He doesn't need to look at the umpire for a fair/foul call. He's taking off, and he'll let his base coach or his teammate tell him that he can slow up if the ball ended up foul and uncaught.

OTOH, consider R1 who goes halfway on the hit, and is waiting to see if the ball is caught or not. If the umpire first gives a fair signal, and then waits to give a catch signal as you said you would, you put the runner at a distinct disadvantage. He's not going to know for sure whether he should hightail it to second or go back to first. In fact, if you first give the fair point, he's probably going to assume the ball was NOT caught, and head to second. Then you come up with the hammer, and R1 is leaning the wrong way.

That's why I think a fair-first-then-catch mechanic is not always appropriate, despite what is taught.

David Emerling Fri May 03, 2013 02:04pm
Quote:
Originally Posted by Robert E. Harrison (Post 892809)
The mechanic allows the runnners on base the information they need in the order they need it.
Wouldn't the runner primarily care if the ball was caught or not - not whether it was caught on the fair or foul side of the line?

EXAMPLE: R3 at third. No outs. Curving line drive hit toward the right field line. The right fielder dives but it is unclear whether he made the catch. R3 is frozen about 20 feet off the bag at the time. If it's not caught, he can sprint home without returning to the bag. If it is caught, he knows he has to get back and then he can decide whether to tag-up and advance. But the first piece of information he needs is whether the ball is caught or not. I don't see how knowing which side of the line the ball was on is more important.

RPatrino Fri May 03, 2013 02:08pm
As a base runner, if I am looking at the umpire as opposed to the ball, I am at a disadvantage anyway. The signal is superfluous. Just like the 'foul tip' signal. Yet we still do it.

Robert E. Harrison Fri May 03, 2013 02:19pm
If the runner is tagging up.
 
Fair or foul is most important. If he is off the base we can certainly give him fair/foul before we have enough information to rule on catch/no catch.

David Emerling Fri May 03, 2013 02:51pm
Quote:
Originally Posted by RPatrino (Post 892828)
As a base runner, if I am looking at the umpire as opposed to the ball, I am at a disadvantage anyway. The signal is superfluous. Just like the 'foul tip' signal. Yet we still do it.
On a shoestring catch, the runner needs to know what the umpire called it, not what he thinks it was.

Naturally, the runner is going to look at the play, but if the catch/no-catch is questionable, his eyes are going to immediately turn to the umpire. He won't give a crap if it is fair or foul at that moment.

Rich Ives Fri May 03, 2013 03:26pm
Quote:
Originally Posted by Manny A (Post 892826)
What possible information does a tagging base runner gain when it comes to fair/foul? It shouldn't matter to him; the moment the ball is touched, he's running. He doesn't need to look at the umpire for a fair/foul call. He's taking off, and he'll let his base coach or his teammate tell him that he can slow up if the ball ended up foul and uncaught.

OTOH, consider R1 who goes halfway on the hit, and is waiting to see if the ball is caught or not. If the umpire first gives a fair signal, and then waits to give a catch signal as you said you would, you put the runner at a distinct disadvantage. He's not going to know for sure whether he should hightail it to second or go back to first. In fact, if you first give the fair point, he's probably going to assume the ball was NOT caught, and head to second. Then you come up with the hammer, and R1 is leaning the wrong way.

That's why I think a fair-first-then-catch mechanic is not always appropriate, despite what is taught.
Uh Manny - he can go on first touch - waiting for the actual catch isn't part of the decision.

bob jenkins Fri May 03, 2013 03:31pm
Quote:
Originally Posted by David Emerling (Post 892832)
On a shoestring catch, the runner needs to know what the umpire called it, not what he thinks it was.

Naturally, the runner is going to look at the play, but if the catch/no-catch is questionable, his eyes are going to immediately turn to the umpire. He won't give a crap if it is fair or foul at that moment.
That's true whether the ball is in dead center or on the line -- and has nothing to do with the "issue" of whether to signal the fair/foul when it happens.

Dave Reed Fri May 03, 2013 03:32pm
Uh Rich,
Read Manny's post again.

MD Longhorn Fri May 03, 2013 03:34pm
Quote:
Originally Posted by RPatrino (Post 892828)
Just like the 'foul tip' signal. Yet we still do it.
Every time I use the foul tip signal, my mind is saying, "Yes, you idiots, I saw it tip off the bat - so shut up and leave me alone". And I guarantee that if I or a partner neglects to make the signal, and someone steals (or strikes out) on that pitch - one half of the crowd will be yelling, "but Blue - she tipped it!!!"

The signal is self defense more than being actually useful.

MD Longhorn Fri May 03, 2013 03:34pm
Quote:
Originally Posted by Rich Ives (Post 892838)
Uh Manny - he can go on first touch - waiting for the actual catch isn't part of the decision.
Uh, coach ... which direction should they run on first touch if they don't yet know if it was caught?

David Emerling Fri May 03, 2013 05:22pm
Quote:
Originally Posted by Rich Ives (Post 892811)
And then everyone really needs to know and know now if it's fair or foul because it governs ensuing action.
I think the most important thing that governs ensuing action is whether it is caught or not.


If the ball is caught - it makes no difference whether it was caught in fair or foul territory. Runners can tag up without any concern about the fair/foul status of the ball. If the ball was on the fair side and was a marginal "catch" requiring an umpire ruling - the runner will primarily want to know if it was caught or not. Because, if it was on the foul side and ruled a no-catch, it really doesn't matter.

If the ball was not caught, once the runners see the no-catch ruling they can assume that it was fair and immediately respond appropriately - if it subsequently turns out to be foul - no harm.

I don't know, it just seems backwards to me.

I'm thinking the reason they encourage umpires to call it in this manner is so they focus on the fair/foul status of the ball; because, if they focus too much on whether it's a catch or not, they will fail to notice where the ball was first touched. That's great for the umpire - doesn't work so well for the runners.

kylejt Sat May 04, 2013 10:04am
On a caught ball, near the line, fair/foul is the least important of the two mechanics. It serves only to inform the scorekeeper on what to put in the book. It's only a courtesy call, only for them.

Signal the catch, and if you have the time, then fair/foul.

I'm fully aware of what's taught, and it makes zero sense, if you think about it for more than three seconds.

jicecone Sat May 04, 2013 12:25pm
David, I really think your giving way too much credit to the officials signal being the guide to the runner for whether or not a catch is made. I doubt very much if 10% of the time the runners are judging whether to tag up or not on a signal by the official. I will reserve that 10% for traps.

For the most part, at second, you are watching the fielder and at third/first your listening to the coach.

David Emerling Sat May 04, 2013 12:51pm
Quote:
Originally Posted by jicecone (Post 892869)
David, I really think your giving way too much credit to the officials signal being the guide to the runner for whether or not a catch is made. I doubt very much if 10% of the time the runners are judging whether to tag up or not on a signal by the official. I will reserve that 10% for traps.

For the most part, at second, you are watching the fielder and at third/first your listening to the coach.
At high levels of play and on well-coached teams, runners are always taught to read the ball and not rely on the coach for baserunning decisions. On a fly ball, waiting for the coach to say "Go!" is Little League stuff.

About the only time runners rely on the coach is when their back is to the ball and something unexpected happens. (i.e. runner advancing to 3rd and the outfielder bobbles the ball or the relay is mishandled.) For instance, you'll almost never see a 1st base coach tell a batter to advance to 2nd on a hit because the batter is expected to see the play and make his own decision.

I disagree. I think the umpire's signal on a shoestring catch that could've gone either way is critical to the runner. Primarily, the runner will watch the play and then, if there's any doubt (and there will be doubt on a shoestring catch), his attention will turn immediately to the umpire for a catch/no-catch ruling. The last thing the runner will care about in that situation is whether the ball was fair or foul. Which, to me, is why it seems so odd that it is taught to give the fair/foul call before the catch/no-catch call.

I admit, I'm thinking about this more as a former (Div I) player of the game than I am as an umpire. It's really not that big of a deal. I'm not losing any sleep over it.

Rich Sat May 04, 2013 01:30pm
Quote:
Originally Posted by kylejt (Post 892865)
On a caught ball, near the line, fair/foul is the least important of the two mechanics. It serves only to inform the scorekeeper on what to put in the book. It's only a courtesy call, only for them.

Signal the catch, and if you have the time, then fair/foul.

I'm fully aware of what's taught, and it makes zero sense, if you think about it for more than three seconds.
Really?

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.

David Emerling Sat May 04, 2013 01:58pm
Quote:
Originally Posted by Rich (Post 892872)
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!

Steven Tyler Sat May 04, 2013 03:05pm
Quote:
Originally Posted by Manny A (Post 892801)

The only time I ever see what you describe (fair/foul signal, then catch signal) is on the routine catch. And I can only assume the signal is given to inform the scorer whether to write "F9" or "FF9" in the book. :)
They use F9 or f9.

tcarilli Sun May 05, 2013 06:49pm
Quote:
Originally Posted by David Emerling (Post 892874)
...But even with the play you describe the runner will be far more concerned if the catch was made or not...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. ...
No, as the runner you don't. By rule runners have complied with the retouch rule by being on the bag when the ball is touched not when it is caught.

It is pretty simple the batted ball is fair or foul first and then it is either a catch or a no catch. Umpire in order of priorities: ball/strike, fair/foul, catch/no catch, safe/out...

David Emerling Sun May 05, 2013 07:07pm
Quote:
Originally Posted by tcarilli (Post 892962)
No, as the runner you don't. By rule runners have complied with the retouch rule by being on the bag when the ball is touched not when it is caught.
But the runner will not be on the bag when the line drive is hit. He'll freeze some distance off the bag. What he'll want to know is if it was caught. If it was - he'll know that he has to get back or get doubled-up. If it wasn't, he'll have to decide whether it's worth continuing to advance toward home.

This is not an umpire issue. I'm simply disputing those in this thread who have claimed that the most important piece of information to the runner is the fair/foul call.

Quote:
It is pretty simple the batted ball is fair or foul first and then it is either a catch or a no catch. Umpire in order of priorities: ball/strike, fair/foul, catch/no catch, safe/out...
There really is no hurry to call a ball fair or foul when a catch is being made. Anything that is marginal, everybody is going to assume is fair until told otherwise. That will be the case for both the offense and defense. That's the way the game is played. By default, all balls are fair until ruled otherwise.

I could see an umpire indicating "no catch" and then, immediately following it with a fair or foul signal. So? Why would that be so bad? Even if, in the umpire's mind, the moment the fielder touched the ball it was in fair territory - he can wait until the catch/no-catch determination is made before indicating that the ball was fair and no harm would be done to either side.

If it's not caught in foul territory - who cares what order he gives them in? It's not going to matter one way or the other.

If its caught in foul territory - it's irrelevant that it was in foul territory. It's neither fair nor foul - it's just LIVE.

I guess it's really not that big of deal after all.

tcarilli Sun May 05, 2013 07:41pm
Quote:
Originally Posted by David Emerling (Post 892963)
But the runner will not be on the bag when the line drive is hit. He'll freeze some distance off the bag. What he'll want to know is if it was caught. If it was - he'll know that he has to get back or get doubled-up. If it wasn't, he'll have to decide whether it's worth continuing to advance toward home.

This is not an umpire issue. I'm simply disputing those in this thread who have claimed that the most important piece of information to the runner is the fair/foul call.



There really is no hurry to call a ball fair or foul when a catch is being made. Anything that is marginal, everybody is going to assume is fair until told otherwise. That will be the case for both the offense and defense. That's the way the game is played. By default, all balls are fair until ruled otherwise.

I could see an umpire indicating "no catch" and then, immediately following it with a fair or foul signal. So? Why would that be so bad? Even if, in the umpire's mind, the moment the fielder touched the ball it was in fair territory - he can wait until the catch/no-catch determination is made before indicating that the ball was fair and no harm would be done to either side.

If it's not caught in foul territory - who cares what order he gives them in? It's not going to matter one way or the other.

If its caught in foul territory - it's irrelevant that it was in foul territory. It's neither fair nor foul - it's just LIVE.

I guess it's really not that big of deal after all.
This has nothing to do with being in a hurry. Baseball plays happen in a certain order and they should be umpired in that order.

The first thing that can happen with runners on base is a balk if the pitcher balks and the B/R gets a base hit the balk is ignored (save NFHS where the ball is dead) does this mean it really doesn't matter when the balk is called?

The second thing that can happen is ball/strike, so rule on that next.

In sequence, the next thing is fair/foul, so rule on that next.

Then catch/no catch, so...

Then safe/out, so...

etc...

Every play should be ruled on in this manner. Of course the sequence can be stopped at some point, but it should be ruled on in order each time until the sequence ends.

That's what this is about. The play happens in order, rule on it in order. Fair/foul has a higher priority than catch/no catch, so rule on fair foul first.

Rich Sun May 05, 2013 08:03pm
Quote:
Originally Posted by David Emerling (Post 892874)
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!
If I'm R3 and there's a ball hit in the air to the outfield, I'm going back to tag.

If it falls, I walk home. If it's caught as a trouble ball, I walk home.

As an umpire: If it falls, I'm signaling safe as soon as it's practical. I'm signaling fair/foul on first touch and it's rare that unless the ball hits the ground first that I could signal either one of those signals simultaneously. Only on a short hop could that be an issue. If it's not a fair/foul issue right on the line, I'm probably coming up with a safe signal right away.

EsqUmp Sun May 05, 2013 08:23pm
It is important to signal fair/foul because of the potential for the defender to bobble the ball and drop it. It is possible that the defender initially touched the ball fair and then dropped it over foul territory. By sticking your arm out and pointing, the umpire will know whether the ball is fair or foul in case it falls. That is much better than a defender diving for the ball, bobbling it and dropping it only for the umpire to stand there wondering, "Hmm, was that fair or foul?" Your brain may not remember, but if your arm is sticking out, you'll have your answer.

In MLB, if the catch becomes obvious, they do not signal "catch" after the point.

A good case in point is when the Yankees were playing the Red Sox and Jeter initially touched a ball in fair territory, then ran into the stands. Fielden Colbreth pointed fair, then ran over toward the stands. If the ball had fallen, it would have been fair.

David Emerling Sun May 05, 2013 09:54pm
Quote:
Originally Posted by Rich (Post 892969)
If I'm R3 and there's a ball hit in the air to the outfield, I'm going back to tag.

If it falls, I walk home. If it's caught as a trouble ball, I walk home.
What if it's a looper behind 1st base, in short right field? The right fielder is running in and makes the catch. You're not going tag up on that. Too shallow. You'll get thrown out by a mile.

On a hit like that, tagging up would be a mistake. Because if you go back to the bag and wait to see what happens - if it's not caught, you will probably not be able to score because you have to run 90 feet. The ball may very well get picked up in plenty of time to throw you out.

You're going want to get quite a distance off 3rd so, if it drops, you can get home before the ball can be picked up. If it's caught, you can get back to 3rd safely. You usually don't tag up on shallow hits into the outfield. You get off the bag so that if it drops, you can score.

What you've described would be correct on a ball hit deep down the right field line.

But now we're talking more about how the game is played than how the game is umpired.

Rich Sun May 05, 2013 10:07pm
Quote:
Originally Posted by David Emerling (Post 892976)
What if it's a looper behind 1st base, in short right field? The right fielder is running in and makes the catch. You're not going tag up on that. Too shallow. You'll get thrown out by a mile.

On a hit like that, tagging up would be a mistake. Because if you go back to the bag and wait to see what happens - if it's not caught, you will probably not be able to score because you have to run 90 feet. The ball may very well get picked up in plenty of time to throw you out.

You're going want to get quite a distance off 3rd so, if it drops, you can get home before the ball can be picked up. If it's caught, you can get back to 3rd safely. You usually don't tag up on shallow hits into the outfield. You get off the bag so that if it drops, you can score.

What you've described would be correct on a ball hit deep down the right field line.

But now we're talking more about how the game is played than how the game is umpired.
Regardless of which mechanic you'd like to see first, if it's a catch I'm going to make sure all elements of a catch are present (including voluntary release) before signaling an out. That's not going to happen quickly on a play like this regardless -- I'll have plenty of time to signal fair first before calling the runner out. If the ball hits the ground, I'm pointing fair quickly and then selling the "no catch" part of the sequence.

So I'm not sure how we're putting anyone at a great disservice here.

Steven Tyler Mon May 06, 2013 02:45am
Do some want to signal no catch on a dropped foul fly ball?

CT1 Mon May 06, 2013 02:42pm
Quote:
Originally Posted by Steven Tyler (Post 892991)
Do some want to signal no catch on a dropped foul fly ball?
I do, if it's obviously foul and it's a close catch/no catch. Usually happens when F2 goes to the screen or dives toward a fence.

Steven Tyler Mon May 06, 2013 03:18pm
Quote:
Originally Posted by CT1 (Post 893041)
I do, if it's obviously foul and it's a close catch/no catch. Usually happens when F2 goes to the screen or dives toward a fence.
Wouldn't just a foul signal suffice? Nobody going anywhere on a "dropped" foul ball regardless.

MD Longhorn Mon May 06, 2013 03:44pm
Quote:
Originally Posted by Steven Tyler (Post 893048)
Wouldn't just a foul signal suffice? Nobody going anywhere on a "dropped" foul ball regardless.
My thoughts exactly. In fact, this is one of the few instances where a verbal FOUL call is actually helpful.

CT1 Mon May 06, 2013 04:30pm
Quote:
Originally Posted by Steven Tyler (Post 893048)
Wouldn't just a foul signal suffice? Nobody going anywhere on a "dropped" foul ball regardless.
It's just the way I was trained, & I don't really see a problem with the "no catch" signal. Remember, this would be on a ball that's in obviously foul territory -- the kind where you'd give no signal if someone weren't trying to make a play on it.

jicecone Mon May 06, 2013 06:14pm
Quote:
Originally Posted by CT1 (Post 893066)
It's just the way I was trained, & I don't really see a problem with the "no catch" signal. Remember, this would be on a ball that's in obviously foul territory -- the kind where you'd give no signal if someone weren't trying to make a play on it.
CT1, I am not ganging up here but, I believe that is the point being made here,obviously foul territory. Its either caught or a dead ball. If its a dead ball, it just doesn't matter what happens next.

MD Longhorn Tue May 07, 2013 08:58am
Quote:
Originally Posted by CT1 (Post 893066)
It's just the way I was trained, & I don't really see a problem with the "no catch" signal. Remember, this would be on a ball that's in obviously foul territory -- the kind where you'd give no signal if someone weren't trying to make a play on it.
The "correct" call is "FOUL BALL" or "FOUL". Kills the play clearly and concisely.

A "no catch" signal is really meant for fair balls where play is continuing and a loud call by an umpire would be disruptive.


All times are GMT -5. The time now is 11:00am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1