![]() |
Quote:
Only announce a run scored when appropriate during a play in which the third out was executed. I do not ask a team nor need to know the score and there is no reason to talk to a scorekeeper except to report a substitute or ejection. |
Quote:
I ask again, what if you are going to the bottom of the 7th in a game that is over? Would you even know it was over? If this sitch happens to you, I hope it goes 16:D Why make things difficult? I prefer to make thins easy. Joe In Missouri:D |
Thanks Mike and Steve...either of those works for me.
I would think that a call of "safe" on the first runner along with the umpire having a different number of outs from the score keeper, somebody is going to figure something out quickly. |
You dont need to know the score in the way that coaches, players, and fans do - but it is an aspect of the game that is at times part of umpire a) duties and b) good officiating.
We are responsible for enforcing Run Rules and game ending run situations. We need to know tie games. It is important you understand certain game situations as part of umpiring and being a student of the game. Most often as PU, I keep track of the runs as part of what I do between innings. It is not a sin to talk to people involved in this game and the level of play (championship/tournament/friendly) may determine how you must approach that. If its a regular joe tourney I may ask the book to run and grab me a cup of coffee in between padding her kids stats. I wouldnt do that in championship play :D If you do need to talk to the book - talk to the book. What you CANT do is something horrible like I saw a few weeks back. Umpire loses count.. goes to the book :rolleyes: Book says count is 2-2. Other team is complaining the count is 2-1. He says "We gotta go by the home book - home book says its 2-2, so its 2-2". They say, well they arent the home book, we are. Ump says, "ok counts 2-1". :rolleyes: Meanwhile, he never did go to his partner. That was so bad, it was a little humorous. |
Quote:
Even in local games, the teams will tell you when there is an issue. If there is an issue, that is the scorekeepers' job to get it straight, not mine. BTW, I never said I wasn't aware of the score, I just don't need it or ask for it. Teams give you all sorts of data and don't even know it if you are paying attention to what is going on inside the fences. Or I can just look at the scoreboard.:D Back to the play. The once-taught, still used mechanic on plays like this or an "assumed out, but safe" on the front end of a double play was for the umpire to reiterate the unanticipated call after the fact if the umpire believes it is necessary. If a team cannot figure out, "safe, no tag!" means the runner wasn't out, maybe they need to find another sandlot in which to play. |
Not questioning your mechanics, Mike (ok I guess I am), but... if there's no touch of the plate and no tag, why would I not have a "no call"? Is it because F2 was standing on the plate?
Seems to me that, in this case, calling R1 safe after she passes the plate would call attention to the fact that she didn't touch it. That's how I'd've handled it... obviously wrong... trying to improve my skills. |
In ASA, that is how the umpires are instructed to call the play. I'm paraphrasing the passage: If there is a missed tag and the plate is missed, the plate umpire should hesitate slightly to see if there is an attempt to tag out the runner. If there is no attempt, the umpire should declare the runner safe.
An initial no call indicates that you have nothing but if the defense does not attempt to retire the runner, you have to indicate in some manner that the runner acquired the base. |
Quote:
Quote:
Quote:
So, lacking a tag on a non-force play, the runner is indeed safe once s/he passes home plate. Doesn't mean the defense cannot appeal the runner missing the base. |
R1 should be called out for waiting so long. ;) :rolleyes: :D :D
|
Quote:
________ Jomtien condos |
Quote:
Quote:
Quote:
|
All times are GMT -5. The time now is 04:33am. |