The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Baseball (https://forum.officiating.com/baseball/)
-   -   how would you fix this? (https://forum.officiating.com/baseball/44557-how-would-you-fix.html)

umpjayfire Wed May 21, 2008 07:16am

how would you fix this?
 
Sitch

I will try to properly paint this picture
0 outs bases empty...2 man mechanics...obr

F3 is playing about 25 feet behind the bag and BU is slightly further back in A
Lefthanded batter hits a hot grounder down the line, over the base where F3 makes a great diving stop.
BU sees its fair, makes proper voice mechanic (meaning none), and just points with his left arm FOUL....uuuuggghhh....
F3, who has heard nothing, knows its a fair ball and it might be a close play (pitcher didn't cover) and runs to first only to see that the B/R has stopped running. F3 steps on the bag and the BU takes a couple steps toward the base and gives an out mechanic....

COMMENCE CRAPHOUSE

I am UIC and ,without being asked, walk up the 1B line to talk to BU who has just said, "What the hell did I just do?" loud enough for the offensive dugout to hear...needless to say he was embarrassed....
If anyone cares I will tell you how we fixed it later but I am interested in how you guys would have fixed it.
Stay with out or call it a foul ball?

mbyron Wed May 21, 2008 07:58am

Under FED, of course, once BU signals foul the ball is dead by rule. The defense cannot record an out.

OBR is less clear about this kind of umpire error. The BRD has an OBR ruling that says "the umpire may reverse his call if everyone concerned ignored his initial signal." The umpire's error likely caused BR to stop running. To stick with the erroneous call would give the defense an advantage not intended by the rules.

I would stick with the foul call, apologize to the defense for the blown call, and explain that if it had been a double down the line and I signaled foul, we'd probably still stick with the call.

BU needs to do all the talking during the explanations.

gordon30307 Wed May 21, 2008 09:05am

Quote:

Originally Posted by umpjayfire
Sitch

I will try to properly paint this picture
0 outs bases empty...2 man mechanics...obr

F3 is playing about 25 feet behind the bag and BU is slightly further back in A
Lefthanded batter hits a hot grounder down the line, over the base where F3 makes a great diving stop.
BU sees its fair, makes proper voice mechanic (meaning none), and just points with his left arm FOUL....uuuuggghhh....
F3, who has heard nothing, knows its a fair ball and it might be a close play (pitcher didn't cover) and runs to first only to see that the B/R has stopped running. F3 steps on the bag and the BU takes a couple steps toward the base and gives an out mechanic....

COMMENCE CRAPHOUSE



I am UIC and ,without being asked, walk up the 1B line to talk to BU who has just said, "What the hell did I just do?" loud enough for the offensive dugout to hear...needless to say he was embarrassed....
If anyone cares I will tell you how we fixed it later but I am interested in how you guys would have fixed it.
Stay with out or call it a foul ball?

If the ball was clearly fair you have to stay with the call. All players have a responsibility to know what the situation is. Screaming foul (since this was close) would be expected. He may have signalled but he didn't verbally call it which would have been expected by both teams. Poor mechanics no question. If the ball was indeed fair the out is the correct call. BR may or may not have seen the foul signal. You don't know that for certain. No matter what you do you're in trouble. Declaring the ball "foul" almost amounts to a "do over". Eat the crow and make the correct call.

Rich Ives Wed May 21, 2008 09:18am

Quote:

Originally Posted by gordon30307
If the ball was clearly fair you have to stay with the call. All players have a responsibility to know what the situation is. Screaming foul (since this was close) would be expected. He may have signalled but he didn't verbally call it which would have been expected by both teams. Poor mechanics no question. If the ball was indeed fair the out is the correct call. BR may or may not have seen the foul signal. You don't know that for certain. No matter what you do you're in trouble. Declaring the ball "foul" almost amounts to a "do over". Eat the crow and make the correct call.


WHAT?

It was called foul. The runner stopped. The craphouse happened because they saw the foul call.

umpjayfire Wed May 21, 2008 09:28am

Quote:

Originally Posted by gordon30307
If the ball was clearly fair you have to stay with the call. All players have a responsibility to know what the situation is. Screaming foul (since this was close) would be expected. He may have signalled but he didn't verbally call it which would have been expected by both teams. Poor mechanics no question. If the ball was indeed fair the out is the correct call. BR may or may not have seen the foul signal. You don't know that for certain. No matter what you do you're in trouble. Declaring the ball "foul" almost amounts to a "do over". Eat the crow and make the correct call.

i think you are saying that we should have called the B/R out...he saw the foul point so he stopped. (he thought he knew the situation)...F3 didn't hear foul and saw a fair ball so he thought he knew the situation...the ball was fair but not 'obvious' to everyone i.e. a nutcutter....when you say 'eat the crow and make the correct call', i am not sure what that should be that is why i am asking

rei Wed May 21, 2008 09:52am

Under FED, you stick with the foul ball call.

I did almost the same exact thing this year.:o

In a playoff game last night, we had a situation where a batter hit the ball off the end of the bat. The ball bounced out into the field funny. The ball was fielded and the batter/runner thrown out at first. As we follow our eyes to U1, he has his arms up for foul ball!!! :( Then he slaps his foot. Upon the meeting of the minds, the plate guy and me (U3) KNOW that it didn't hit the batters foot. From my angle, which was 90 degrees from his foot and ball, and seen at least 2 feet of daylight between ball and foot. I know for certain it never hit his foot. Oh well.

The only "right" call was to let the "foul ball" stand. The UIC took charge and told the defensive team head coach that no matter whether there was a judgment mistake or not, by rule, once it is called foul, it is foul. No argument. The batter hit a double after that taking that 0-1 count to full count! :(

gordon30307 Wed May 21, 2008 10:07am

Quote:

Originally Posted by Rich Ives
WHAT?

It was called foul. The runner stopped. The craphouse happened because they saw the foul call.

It wasn't "called foul" it was signalled foul I don't know about you but I'm going to be yelling foul on close ones down the line. Both teams expect this. BR may or may not have seen ( he probably did but he also could have been throwing a hissy fit because the first baseman made a great play) the signal and we know for a fact the first baseman did not see the signal. If the ball was clearly fair (which it apparently was) have the balls to make the correct call. Admit your mistake and play on.

gordon30307 Wed May 21, 2008 10:11am

Quote:

Originally Posted by rei
Under FED, you stick with the foul ball call.

I did almost the same exact thing this year.:o

In a playoff game last night, we had a situation where a batter hit the ball off the end of the bat. The ball bounced out into the field funny. The ball was fielded and the batter/runner thrown out at first. As we follow our eyes to U1, he has his arms up for foul ball!!! :( Then he slaps his foot. Upon the meeting of the minds, the plate guy and me (U3) KNOW that it didn't hit the batters foot. From my angle, which was 90 degrees from his foot and ball, and seen at least 2 feet of daylight between ball and foot. I know for certain it never hit his foot. Oh well.

The only "right" call was to let the "foul ball" stand. The UIC took charge and told the defensive team head coach that no matter whether there was a judgment mistake or not, by rule, once it is called foul, it is foul. No argument. The batter hit a double after that taking that 0-1 count to full count! :(

I don't think this game was played using Fed Rules. I beleive it was OBR. UIC has nothing to do with changing this call. Any change has to originate from the calling official which in this case is the BU. UIC certainly can provide input but the change has to come from the calling official.

gordon30307 Wed May 21, 2008 10:17am

Quote:

Originally Posted by umpjayfire
i think you are saying that we should have called the B/R out...he saw the foul point so he stopped. (he thought he knew the situation)...F3 didn't hear foul and saw a fair ball so he thought he knew the situation...the ball was fair but not 'obvious' to everyone i.e. a nutcutter....when you say 'eat the crow and make the correct call', i am not sure what that should be that is why i am asking

If the ball was indeed "fair" have the balls to make the correct call which is "out". Close ones down the line aren't you yelling "foul" and isn't that what both teams expect? I rest my case.

chuckfan1 Wed May 21, 2008 10:18am

Gordon...

If someone stops "playing" in this case, because of an umpires signal of foul, then its a foul ball. The Umpire who made the erroneus call has to eat it, and take the crap. This wasnt a ball hit in the gap, where no one is going to make a "foul" call. This was a ball up the line, maybe BR had his head down, whatever, its foul.
And your going to let the play stand? Your going to most likely have a bigger sh*thouse.

gordon30307 Wed May 21, 2008 10:42am

Quote:

Originally Posted by chuckfan1
Gordon...

If someone stops "playing" in this case, because of an umpires signal of foul, then its a foul ball. The Umpire who made the erroneus call has to eat it, and take the crap. This wasnt a ball hit in the gap, where no one is going to make a "foul" call. This was a ball up the line, maybe BR had his head down, whatever, its foul.
And your going to let the play stand? Your going to most likely have a bigger sh*thouse.

Hey the first baseman didn't stop playing. Not my problem BR didn't run the ball out. It's a bad situation granted. But if the ball was indeed "fair" the only correct call is "out". Don't you scream "foul" on close ones down the line. Don't both teams expect to hear foul verbalized on close ones? I rest my case.

LakeErieUmp Wed May 21, 2008 10:52am

This isn't court, Gordon (I know, I'm an attorney and if this was court I'd be billing $350 an hour to talk to you).
F3 didn't stop playing because he saw the ball was fair - AND DIDN'T HAVE ANY CONTRARY INFORMATION FROM THE BU TO TELL HIM OTHERWISE.
However, B/R DID have information from BU that it was foul and that caused him to stop running.
You can "rest your case" but the judgment is going against you.
We're not penalizing the offense because BU flubbed - and there's nothing for UIC to do so we're not going there.

dash_riprock Wed May 21, 2008 10:55am

Calling the batter out would be FAR worse than the original foul call. Keep it to one blown call. The ball is foul.

gordon30307 Wed May 21, 2008 11:08am

Quote:

Originally Posted by LakeErieUmp
This isn't court, Gordon (I know, I'm an attorney and if this was court I'd be billing $350 an hour to talk to you).
F3 didn't stop playing because he saw the ball was fair - AND DIDN'T HAVE ANY CONTRARY INFORMATION FROM THE BU TO TELL HIM OTHERWISE.
However, B/R DID have information from BU that it was foul and that caused him to stop running.
You can "rest your case" but the judgment is going against you.
We're not penalizing the offense because BU flubbed - and there's nothing for UIC to do so we're not going there.

The ball was fair why do we have a do over. Can you aboslutely beyond a reasonable doubt be certain that BR saw the signal? I'm assuming you're an umpire don't you scream foul on close ones down the line? Don't both teams expect this? If the ball is fair the proper call is out. Why penalize the defensive team because of poor mechanics? I win on appeal. Also I'm from Illinois the most corrupt state in the Union and I know people. LOL

gordon30307 Wed May 21, 2008 11:10am

Quote:

Originally Posted by dash_riprock
Calling the batter out would be FAR worse than the original foul call. Keep it to one blown call. The ball is foul.

Is that "fair" to the defensive team of depriving them of an out?

Rich Ives Wed May 21, 2008 11:13am

Quote:

Originally Posted by gordon30307
The ball was fair why do we have a do over. Can you aboslutely beyond a reasonable doubt be certain that BR saw the signal? I'm assuming you're an umpire don't you scream foul on close ones down the line? Don't both teams expect this? If the ball is fair the proper call is out. Why penalize the defensive team because of poor mechanics? I win on appeal. Also I'm from Illinois the most corrupt state in the Union and I know people. LOL

The ball may have been in fair territory but the BU indicated foul.

The batter-runner stopped because he saw the foul call and reacted.

The S*&%house happened because the offense SAW the foul call.

It's foul - deal with it.

bob jenkins Wed May 21, 2008 11:24am

I agree that the ball is foul.

archangel Wed May 21, 2008 11:53am

gordon, soon a jury of 12 posters total will rule against you!

PeteBooth Wed May 21, 2008 12:01pm

[QUOTE]
Quote:

Originally Posted by gordon30307
It wasn't "called foul" it was signalled foul

You are missing the point.

Whether you call FOUL or SIGNAL FOUL = FOUL

Example: PU puts the "stop sign up" towards F1.

That means we have TIME and DO NOT PITCH. The PU does need to say anything.

Bottom Line: Rightly or wrongly when the players hear or see an umpire signal FOUL they STOP.

There are those rare instances (in both the LLWS and a ML baseball game) where a FOUL call was changed to fair.

The ball in this play is FOUL. BU admitted mistake (hey it happens) now time to move on.

Pete Booth

celebur Wed May 21, 2008 12:10pm

Quote:

Originally Posted by gordon30307
Why penalize the defensive team because of poor mechanics?

Why penalize the offensive team because of poor mechanics?


Quote:

Originally Posted by gordon30307
I win on appeal.

Declaring it so doesn't make it so.

dash_riprock Wed May 21, 2008 12:13pm

Quote:

Originally Posted by gordon30307
Is that "fair" to the defensive team of depriving them of an out?

How do you know it deprived the D of an out? Your OP said F3 was playing "about 25 feet behind the bag." So he's lying on the ground in right field, and no one is covering 1st, at least not yet. Maybe you deprived the O of a base hit.

Lie isn't fair. The BU f'ed up. Sometimes you get the short end of the stick. Next.

LittleLeagueBob Wed May 21, 2008 01:27pm

FED Case Play -
 
Quote:

Originally Posted by gordon30307
If the ball was clearly fair you have to stay with the call. All players have a responsibility to know what the situation is. Screaming foul (since this was close) would be expected. He may have signalled but he didn't verbally call it which would have been expected by both teams. Poor mechanics no question. If the ball was indeed fair the out is the correct call. BR may or may not have seen the foul signal. You don't know that for certain. No matter what you do you're in trouble. Declaring the ball "foul" almost amounts to a "do over". Eat the crow and make the correct call.

Gordon -

Altho the OP states OBR, I'm posting the FED case play here to give some guidance on what they want us to do in essentially the same situation. I think the Major League Umpire Manual has something silimar in it, but I don't have a copy - prehaps someone else can post that so you can see what OBR has to say...

2.16.1 SITUATION B: On a count of 1-ball, 2-strikes, B1 hits a ground ball down the third-base line and the umpire inadvertently declares “foul ball.” F6 fields the ball in fair territory and throws to F3. RULING: The ball is dead immediately once it hits the ground; B1 returns to bat with a count of 1-2.

LMan Wed May 21, 2008 01:33pm

Quote:

Originally Posted by dash_riprock
Lie isn't fair. The BU f'ed up. Sometimes you get the short end of the stick. Next.

This man 'gets it.' :cool:

MrUmpire Wed May 21, 2008 03:58pm

Quote:

Originally Posted by gordon30307
It wasn't "called foul" it was signalled foul

This man doesn't.

Chris_Hickman Wed May 21, 2008 04:38pm

FOUL

umpjayfire Wed May 21, 2008 04:55pm

End Result
 
Since I Am The Original Poster I Get The Last Word On This And Before I Tell You How We Ruled I Must Commend Gordon For Sticking To His Guns Even Though I Disagree....We Ruled It Foul, Saying That, Although The Mechanic Was Poor, The Foul Signal Has Pretty Much Killed The Action And Nothing Further Can Happen After That, Because We Killed The Ball, No Matter How Wrong It Was.
---gordon...as The Pu I Know For A Fact The Batter Stopped Because Of The Signal Because As Soon As My Bu Made The Out Mechanic He Turned To Me And Said ,"what The F--k, He Pointed Foul"...i Said," Give Me A Second While My Partner And I Figure It Out".....
End Result Is We Had No Ejections Because We Had A Good Rapport With The Defensive Coach And He Had Seen What Transpired...instead He Jokingly Ribbed My Partner For The Rest Of The Season...he Also Gave A Dvd Of The Sitch With My Partner Obvious Mouthing,"what The Blank Did I Just Do?" Clearly Visible To Him When He Saw Him Later In The Season As Another Joke....

Thanks For Everyone's Input

Paul L Wed May 21, 2008 05:14pm

Devil's Advocating
 
The proper foul mechanic is raising both arms in the air and verbalizing "foul". Right? BU did not use either mechanic, just pointed with his left arm, presumedly toward foul territory. If memory serves, the foul mechanic was changed many years ago precisely to avoid accidental foul calls.
The proper fair mechanic is pointing towards fair territory and verbalizing nothing. This is what BU did, except for the accidental point in the wrong direction. So why is BR entitled to think foul was called?
Well, I guess I know the answer to that question. If the commonly understood foul signal caused BR to stop running, then BU has to eat the foul call.
But I was surprised no one mentioned the wrong foul signal. Is pointing foul, rather than raising both arms, the proper signal anywhere?

Rich Ives Wed May 21, 2008 05:41pm

Quote:

Originally Posted by Paul L
The proper foul mechanic is raising both arms in the air and verbalizing "foul". Right? BU did not use either mechanic, just pointed with his left arm, presumedly toward foul territory. If memory serves, the foul mechanic was changed many years ago precisely to avoid accidental foul calls.
The proper fair mechanic is pointing towards fair territory and verbalizing nothing. This is what BU did, except for the accidental point in the wrong direction. So why is BR entitled to think foul was called?
Well, I guess I know the answer to that question. If the commonly understood foul signal caused BR to stop running, then BU has to eat the foul call.
But I was surprised no one mentioned the wrong foul signal. Is pointing foul, rather than raising both arms, the proper signal anywhere?


Both hands in the air is "time". Pointing is the indicator.

LMan Thu May 22, 2008 09:15am

Quote:

Originally Posted by MrUmpire
This man doesn't.

You are correct. The sooner he gets off the 'fairness' kick, the better off he will be.

'It aint fair!' is a whiny coach's crutch. Don't use it.

mbyron Thu May 22, 2008 10:36am

Quote:

Originally Posted by LMan
You are correct. The sooner he gets off the 'fairness' kick, the better off he will be.

I disagree. He's right to insist on fairness, but wrong in his understanding of what fairness requires.

BU signaled "foul," so BR stopped running. It's unfair to the offense to change the call at this point.

Gordon is concerned about fairness to the defense: how can you take away an out? You take it away because it was obtained unfairly due to an umpire's mistake.

Fairness--providing no advantage not intended by the rules--is the justification for the OBR ruling I posted in post #2 above.

CO ump Thu May 22, 2008 12:55pm

Quote:

Originally Posted by rei
Under FED, you stick with the foul ball call.

I did almost the same exact thing this year.:o

In a playoff game last night, we had a situation where a batter hit the ball off the end of the bat. The ball bounced out into the field funny. The ball was fielded and the batter/runner thrown out at first. As we follow our eyes to U1, he has his arms up for foul ball!!! :( Then he slaps his foot. Upon the meeting of the minds, the plate guy and me (U3) KNOW that it didn't hit the batters foot. From my angle, which was 90 degrees from his foot and ball, and seen at least 2 feet of daylight between ball and foot. I know for certain it never hit his foot. Oh well.

The only "right" call was to let the "foul ball" stand. The UIC took charge and told the defensive team head coach that no matter whether there was a judgment mistake or not, by rule, once it is called foul, it is foul. No argument. The batter hit a double after that taking that 0-1 count to full count! :(

Just curious.
Why was there a meeting of the minds?
U1 sees the ball hit the foot, properly signals foul. It's foul. Get the batter back in the box and lets play.
If DHC or OHC has a problem he deals with U1 not the whole crew.
IMO, UIC had no business being involved at all, except to get the batter back in the box. Being this was a playoff game I'm assuming U1 can take care of himself. Secondly, it appears as if UIC threw U1 under the bus with his comment about mistake in judgement.

MrUmpire Thu May 22, 2008 03:56pm

Quote:

Originally Posted by mbyron
I disagree. He's right to insist on fairness,


Fairness has nothing to do with it. The rules aren't fair in numerous places. Our job is to see that neither team gets an advantage not intended by the rules, not to decide what is fair and what isn't.

mbyron Fri May 23, 2008 06:49am

Quote:

Originally Posted by MrUmpire
Fairness has nothing to do with it. The rules aren't fair in numerous places. Our job is to see that neither team gets an advantage not intended by the rules, not to decide what is fair and what isn't.

Ah, now we're just quibbling over 'fair'. All I mean is, unfair="advantage not intended by the rules." In general, for any game the rules define fairness (that's why "life is not fair"). You must have some more substantive notion of fairness in mind.

MrUmpire Fri May 23, 2008 10:49am

Quote:

Originally Posted by mbyron
Ah, now we're just quibbling over 'fair'. All I mean is, unfair="advantage not intended by the rules." In general, for any game the rules define fairness (that's why "life is not fair"). You must have some more substantive notion of fairness in mind.

No. I'm using and responding to the word "fair" as it is commonly defined and used by the population in general, particularly whiny coaches, players, fans and misunderstanding umpires. You seem to be attempting to create a new defintition of the word.

The rules do not define "fair". They define accepted and required practices and observances of a game, some of which are not "fair."

The role of the umpire is not to decide what is fair, but to enforce the rules, whether they appear fair or not.

mbyron Fri May 23, 2008 07:41pm

Quote:

Originally Posted by MrUmpire
No. I'm using and responding to the word "fair" as it is commonly defined and used by the population in general, particularly whiny coaches, players, fans and misunderstanding umpires. You seem to be attempting to create a new defintition of the word.

The rules do not define "fair". They define accepted and required practices and observances of a game, some of which are not "fair."

The role of the umpire is not to decide what is fair, but to enforce the rules, whether they appear fair or not.


The rules define what is fair for games.


All times are GMT -5. The time now is 12:42pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1