Weird Call and Ejection

[zm1283]

Originally Posted by bobbybanaduck

absolutely not. professional umpires do not conference on this type of thing. they either call it or they don't. and if they don't, it's not because they saw it was foul but aren't going to say anything, it's cuz they didn't think have it as foul. if ANY of the BUs had it hitting the bat and the ground, they would have immediately called it foul. therefore, the conference must have been about whatever bob saw on the ball when he inspected it.

Okay, fair enough. It just reinforces my point to others that it wasn't a foul ball then, because it never touched the bat.

They still got it wrong no matter which way you cut it.

By the way, he called it a foul tip originally, but the call was reversed to foul ball after he talked to the BUs. What else would they be discussing other than whether it hit the ground or not before going into F2's glove?

[UmpTTS43]

I don't understand why guys don't think it possibly couldn't have hit the bat. How many times have you heard a "tick", or "tink" with an aluminum bat, and the ball doesn't change direction? Bob heard something. Maybe he heard the "tick" and didn't see the ball hit the ground, or maybe he heard it hit the ground and thought it was a foul tip. It seemed to me that the batters reaction was that it hit the bat and was surprised that F2 caught the ball.

I didn't know that accusing an umpire of "making sh*t up" was cause for ejection.

[Ump153]

Originally Posted by UmpTTS43

I didn't know that accusing an umpire of "making sh*t up" was cause for ejection.

Only if your integrity is important to you.

[SanDiegoSteve]

Originally Posted by UmpTTS43

I didn't know that accusing an umpire of "making sh*t up" was cause for ejection.

Let me put it this way: Wedge accused the umpire of cheating. Is that plain enough?