Play of the Week

Last updated 7/6/05, 10:15 PM

 

By Wednesday of each week, I will put a play on this site with several variations resulting in several outcomes. Throughout the week, you can add your comments and debate about the plays on the discussion page. Then, on the following Tuesday, along with the next “Play of the Week” I will also offer commentary and rule interpretations explaining the previous week’s play. Hopefully, these discussions will lend themselves to several key outcomes: 1) A better understanding of the rules we enforce; 2) A zest for locating and finding specific rules that apply; 3) Some consistency when these situations occur in real live games; and 4) some competition and some fun.

 

For terminology, all plays are as follows: BU, Batter-Runner, R1, Runner at first, R2, etc. F1, Fielder 1 (Pitcher), F2, Fielder 2 (Catcher); F3, Fielder 3 (1st Base), etc.; PU, Plate umpire; BU, Base umpire. As in HTL games, only Official Rules of Baseball apply.

 

April 3, 2005  (From a handout at the meeting of the HTUA)

April 5, 2005

April 20, 2005

May 11, 2005

May 14, 2005

June 3, 2005

June 17, 2005

 

Sunday, April 3rd

Cottage Grove is at Waterloo. Top of the 9th. Dagget on second and McCoy batting. Setz on the mound and the count is 1-1. Setz delivers a wild pitch and PU ( Radar) voice signals “balk”.

 

Situation A:  Daggett in attempting to advance to home on the wild pitch and is thrown out.

a.)                Enforce balk, put Daggett back at 3rd. Count 2-1

b.)                Daggett out,  Acknowledge balk, count 1-1

c.)                None of the above

 

Situation B:  Daggett advances to home and scores.

a.)                Enforce balk, Return Daggett to 3rd, count is 2-1

b.)                Score the run. Acknowledge balk, count 1-1

c.)                None of the above

 

Situation C:  Daggett is thrown out at third.

a.)                Enforce balk, Put Daggett back on 3rd, count is 1-1

b.)                Out stands, count is 2-1, balk is ignored

c.)                None of the above.

 

Terminology: Enforced, Acknowledged, or Ignored

 

Answers:

A.)         b.)      Daggett out,  Acknowledge balk, count 1-1

B.)          b.)     Score the run. Acknowledge balk, count 1-1    

C.)          a.)     Enforce balk, Put Daggett back on 3rd, count is 1-1

 

 

Tuesday, April 5th

(This actually happened to me in a HTL game): Bottom of the ninth, home team down by one run; home team at bat, R1 and R3 and one out. On a hit and run with R1 moving on the pitch (R3 stays at third) BR hits a fly ball into the gap in right center. F8 makes a diving catch as R1 rounds second base. After returning to 2B and retouching (legal touch), R1 is heading back to first to tag up. R3 has tagged (properly) and is heading home.

 

1)      F8’s throw to first is ahead of R1 when the base is tagged. Before the throw arrives at F3, R3 has scored. What have you got?

a)      Third out on a force play, inning over, R3 cannot score, game over.

b)      Three outs, run scores, extra innings.

 

 

2)      On his return to first base, R1 misses 2B and beats F8’s throw to first. R3 has already scored when F5 screams for the ball because of the missed base. A throw to F5 standing on 2B gives you,

a)      Three outs, inning over, game over.

b)      Three outs, run scores, extra innings.

c)      Two outs, illegal appeal and run scores. Inning continues with R1 safe at first.

 

3)      Instead of one out, there are two. On the hit and run, R1 misses 2B and F8 does not make the catch. R3 scores and R1 is rounding 3B and heading home. On the throw to the plate, R1 is safe, but F5 screams for the ball on the missed base. F2 throws the ball to 2B and F5 steps on the bag. What have you got?

a)      One run scored, tie game. R1 is out at 2B for the missed base.

b)      Game over, both runs score, illegal defensive appeal.

c)      R1 is out for illegal action, R3 run does not count because of the illegal action; game over.

 

Answers:

Although I am no rules expert, I will give you my opinion on the rulings for this play of the week:

 

In situation #1, with R3 and R1, fly ball caught; when R1’s base is tagged for failure to retouch after a fly ball is caught, that runner is out, yet if R3 scores ahead of that tag, the run counts. The answer for #1 as written is (b), 3 outs, run scores, tie game. This IS NOT a force play; this is a time play. Umpires need to understand that this is actually a defensive appeal play and the ball is alive and in play and all subsequent action prior to the third out is legal. Reference rule 7.08(d), 7.08(e) and 7.10(a).

 

In situation # 2, again this is a defensive appeal play and the ball is still alive and in play. In this situation, R1 is called out for missing the base at second, yet R3 has scored ahead of that out, therefore the correct answer is (b) 3 outs, 1 run scored and extra innings. Reference rule 7.10(b) and Approved Ruling (2).

 

Again, in situation #3, like #2, the ball is alive and in play, all subsequent action is legal and the missed base at second represents an appeal by the defense for the third out. R3’s run is legal, R1’s is not – he is out for missing the bag. Once again, this play is referenced in 7.10(b) and the Approved Rulings, both (1) & (2).

 

If you agree or disagree or want to add some insight to these plays and my rule interpretations, feel free to add your comments onto the discussion page.

Play of the week 4-20-05  (posted 5/11/05)

For terminology, all plays are as follows: BR, Batter-Runner, R1, Runner at first, R2, etc. F1, Fielder 1 (Pitcher), F2, Fielder 2 (Catcher); F3, Fielder 3 (1st Base), etc.; PU, Plate umpire; BU, Base umpire. As in HTL games, only Official Rules of Baseball apply.

 

#1) BR hits ball to F6 who throws wild into stands (ball is dead). BR runner misses first base while rounding the bag as the ball goes into the stands. Umpire awards BR second base on the overthrow. The ball is put back into play, with the pitcher on the rubber, he steps off (legally) throws to F3, where F3 tags the base. Your call?

a)      No call, BR was awarded 2B, therefore no play can be made on him.

b)      BR safe on appeal because no play can be made after a dead ball is put back into play.

c)      BR is out for failure to touch first.

 

#2) R1 and R3 with one out, R1 is stealing on the pitch; R3 holds. The catcher rises and on his wind to throw hits the umpire’s mask. R3 takes off for home as soon as F2 releases the ball. The thrown ball is late, R1 is safe at second, R3 has scored. Make the call, place the runners.

a)      Runner at second, one run scores.

b)      R1 is out, R3 goes back to third.

c)      R1 goes back to first, R3 back to third; call the pitch a strike or a ball.

 

#3) Same scenario as #2 except just the one runner at first. R1 is stealing and again the umpire’s mask is struck on the throw. R1 is out on the throw, however. Make the call, place the runners.

a)      R1 goes back to first on the interference.

b)      R1 is safe at second on the interference.

c)      R1 is out on the play by F2 and no interference is called.

 

Answers:

In situation #1, the over throw is a result of the continuation of the play. The runner still must satisfy the requirement to touch all bases in order. Once the ball is put back into play (legally) and the pitcher steps off (legally) the defense is allowed to make an appeal on the missed base. As written, play #1 would result in BR being called out on the missed base. Reference 7.10(b)

 

I put this play in there to illustrate another point. All too often I see base umpires following a fly ball with their bodies and eyes when no runners are on. They lethargically follow into the grass area or stay in the dirt and are intently following the ball. Even though I have said in pre-game that I have the ball and you have the runner in the no runner on situation, invariably umpires will drift out following the ball. Did the runner touch first? What if a blooper lands safely and the fielder throws wildly into the stands and second base is awarded? Did BR touch first base? Base umpires … when no runners are on your job is to come into the infield, pivot and follow the runner. Keeping an eye on (towards) the ball is okay, but the runner and his actions are your responsibility.

 

In situation # 2, umpire’s interference is called after the play is over. As per Rule 5.09(b) no runners may advance. Put the runners back at 1st and 3rd and resume play. Remember to call the pitch.

 

Again, in situation #3, like #2, the ball is alive and in play, until the play is over. Because F2 was able to throw out the runner despite the interference, the umpire’s interference is ignored.

 

If you agree or disagree or want to add some insight to these plays and my rule interpretations, feel free to add your comments onto the discussion page.

 

Play of the week 5/11/05

 

Instead of plays and rule interpretations this week, I wanted to focus on – for a change – positioning. As umpires, we all have little habits and quirks about things, but sometimes, without a regular partner or when we work with someone who doesn’t know our quirks and habits, we can look out of position or disorganized on a diamond. The emphasis this year at the annual meetings was consistency. One of the things the HTL management said we (as an organizational “whole”) lacked consistency.

 

Dave already addressed balls and strikes and working consistently behind the plate. Timing and focus being the best tools we can bring to the game along with sound mechanics for getting into the slot and keeping still to see the pitch.

 

I wanted to speak this week about consistency as a team; partnership and fluid motion on the field as a two-man crew; not necessarily two men on a field. As I said above, I think the no runners on presents more problems for crews because we assume this positioning is “the easiest” to handle. But like in any position during the game, a lot can happen with no runners on, so as a crew, we need to think and act alike in covering these plays. So this week I’ll focus on no runners, BU in position A.

 

Situation: Bunt or weakly hit ball along either line.

Immediately the base umpire (BU) should recognize bunt and hustle to the grass dirt line between 1st and 2nd and straddle that line about 15-18 feet from the base. This position gives you the best 90 degree view of the play happening quickly down the line. The plate umpire (UIC) needs to straddle what ever line the ball could go foul near, wait for the ball to settle or be picked up (obviously ruling fair/foul) and then take a position which will allow a view (and help) of out of the baseline, swipe tag or pulled foot.

 

Situation: Base hit to the “V” of the outfield.

Invariably BU’s will follow that ball out to the outfield, making some hap-hazard line along the infield dirt. BR is behind them and even a cursory glance isn’t the right mechanic. Proper positioning on this play is for the BU to come into the infield, pivot about 15-18 feet from first base on the infield grass and anticipate BR going to second. Glance at the ball and note it’s position, but the BR is your responsibility. Should the throw come into the infield and BR retreat, move towards the 45-foot mark and keep your eye on the ball and potential play at first. Nothing catches us more off guard then to give up on BR once the outfielder throws the ball into the infield and some strong armed shortstop whips the ball to first with our back completely to the play lolly-gagging to position B. By the same token, UIC should follow the flight of the ball to the outfield getting as close to the pitcher’s mound as possible to see the play. Call catch/no catch if warranted. A good mechanic once the base hit is down on the ground is to say just loud enough for your partner to hear, “The ball is down, Scott.” Again, fluid motion with both umpires moving in harmony on this play looks and feels right.

 

In coming weeks, I’ll do more on positions and mechanics. If you have a play or position or mechanic that just seems to give you fits, or is a pet peeve or whatever, write in and I’ll try to address it. The more we recognize and share problems, the more consistent we become.

 

 

Play of the Week, May 14, 2005

 

Situation:
 Runners on first (R1) and second (R2). No outs. Batter hits a ground ball that strikes R1. BU rules runner interference. The correct placement after this call of runners is:  R2 back to second, R1 is out, and Batter/Runner ( BR ) is awarded first.
 
Reference rule:  7.08
Any runner is out when_  (f) He is touched by a fair ball in fair territory before the ball has touched or passed an infielder. The ball is dead and no runner may score, nor runners advance, except runners forced to advance. EXCEPTION: If a runner is touching his base when touched by an Infield Fly, he is not out, although the batter is out; If two runners are touched by the same fair ball, only the first one is out because the ball is instantly dead. If runner is touched by an Infield Fly when he is not touching his base, both runner and batter are out.

Umpire/Player relationships

 

Play of the Week, June 3, 2005

 

I have, over the last few weeks received some nice comments from coaches and several players on the articles found on this web site. I’m not taking all the credit for that because I’m not the only contributor. It is refreshing to note that some players and managers have taken an interest in our communications – and hopefully have gleaned a little insight into “our world” from this web site. With that in mind, this week’s article will hopefully be read by umpires, players and coaches alike and can be of some assistance to all three groups.

 

One the most key relationships between umpire and players is between the catcher and a plate umpire. An old umpire adage goes something like, “A catcher can make or break his pitcher’s day.” True to some extent, I don’t firmly believe this adage, but some of that thinking has validity. Let me explain by example. Earlier this year I worked a good game by two top teams. Each team had quality starting pitchers, good hitters, good fielders and were both tops in their “early” divisional standings. Both starters had great command; however their respective catchers had as much to do with the number of strikes I called that day. Here’s why: Both catchers had great mechanics. That is, they got down in their stance to give the sign and stayed put. They both “disappeared” from sight, getting low to the ground – giving me a great view. They both shaded slightly the outside corner, leaving the glove hand side a huge opening for seeing and calling the inside corners AND not having to reach on outside corner pitches. Finally – and this is big – both catchers let the ball come to them, catching the ball several inches from their bodies, rather than reaching or swiping at the ball as it crossed the plate. Both catchers held the caught ball an instant giving me a great view, a great read and a great final position. I had a super view of pitches all day. The catchers weren’t swiping or moving the ball in and out of the zone and both catchers disappeared from sight in getting into their position. In 2 hours and 20 minutes, we completed a great contest 5-3.

 

Contrarily, I worked another game last month where two first place teams had less than stellar pitching coupled with (what I consider) poor catching. Both catchers sat high in their stances and dead center on the plate – cutting off my view of the slot. Both catchers stabbed or swiped at the ball as it crossed the plate, moving the ball either down or back after catching it. The higher stances forced me to stand higher, looking down over them. This potentially takes a little away from the low – knee high – strike. Setting up near the middle of the plate, forces their glove side shoulder to be deeper (towards the batter) into my slot area. A pitch on the outside corner is reached for more than a catcher who set up a little off center. And again, the higher stance, the closed slot takes away from my view of that outside corner. A catcher swiping at the ball takes away that instantaneous look at where the pitch crosses the plate and where the pitch ended up. Although the pitching and the fielding wasn’t the caliber of the game above, 3 hours and 37 minutes after we started, the 13-10 game ended.

 

Now in either case, I’m not suggesting that the catchers had a great deal of contribution to the fast (or slow) pace of a game, not the low (or high) score that proceeded. I will say however, that as a plate umpire, the better view I was afforded in the first game had a great deal to do with the pitchers seeing strikes called and having the confidence to throw more strikes. Definitely in the second game, the frustrations of “close” pitches being balled and the frustration of not “getting my pitch” leads to pitchers who throw more and get tired faster. I will say, given equal talent, hitting and fielding by each team (a hypothetical here) the first two catchers would have definitely helped their pitchers where the second two definitely hurt their pitchers.

 

Here’s a good test for players and managers when your first indication is that the plate umpire is “having a bad day.” Are a lot of the pitches caught by the catcher between his chin and his knees? Is the catcher high in his stance or low (do you see more catcher from the bench or more umpire)? Are pitches high, in the dirt, outside then way inside (consistency)? Maybe – just maybe – you could ask your catcher to help the umpire see better. And maybe – just maybe – you might see more calls go, “Strike” before you hear, “Ball!”

 

And finally, I’m not suggesting that all rough days on the diamond are a catcher’s fault, no more than I’d suggest that all poor games are the result of poor umpiring. It’s a give and take from this unique relationship. I will be the first to admit that I’ve done games for whatever reason I just didn’t have my “A” stuff. Like a good hitter gone south, for some reason, “today ain’t the day.” But I have had days where my A-game is on and my views are blocked and I’m just not seeing the pitches where they actually are. In some cases I’ve asked catchers to get lower, move over, whatever was impeding my ability to see. And some catchers are quite congenial about it and make the moves and things improve. I’ve had other catchers (and a manager from time to time) tell me to keep quiet and not tell them how to play. In most of those cases, we continued to struggle the rest of the game; suffice it to say I wasn’t the most popular person at its conclusion.

 

The purpose of today’s article is help umpires see where a catcher can help or hurt their abilities that day. Also to show umpires it’s okay to ask the catcher to move, sit lower or whatever to help you (and his pitcher) a bit. Finally, this article was written today to give some connection, some focus on the unique relationship that exists behind home plate and that there are some things that can be improved upon – from all of us; players and umpires alike.

 

Thanks for listening; I’d love to hear your comments for and against.

 

Mark Ambrosius

 

Play of the Week, June 17, 2005

 

For the play of the week this week, here’s one in which I got caught with my pants down. It embarrasses me that I got this one wrong, but it shows an important point in your approach to umpiring. Like players and managers there are those times in a game situation where – when the pressure is on – we choke. I’m not making excuses; just admitting I choked.

 

The situation was, Cottage Grove had R1 & R3 with R1 stealing second. Cottage Grove’s batter swung at the pitch. The Waterloo catcher faked a throw to second and his throw to third was late, but UIC called interference, announcing “Time, that’s interference” (pointing to the batter). Then the fun started. UIC called R3 out for the batter interference, while BU put R1 back to first. As play continued I stood there dumbfounded mentally nursing a complete brain-fart. I mulled the play over and over in my head, but it wasn’t until after Waterloo had batted in the eighth inning that the brain cells I killed in the early ‘70’s with alcohol kicked back in. I can even recite the rule number without looking it up. Rule 6.06(c) states that a BATTER is out on interference, the ball is dead and no runner may advance.

 

Knowing full well we (I) blew the call, I e-mailed my partner on Monday and we discussed our error. Cottage Grove put up a minor stink (warranted) but did not question the call or the ruling – merely looking for clarification. When my partner and I e-mailed back and forth that next day, we both admitted our mistake and realized we had blown that call.

 

Impact on the game … R3 obviously did not score as we incorrectly gave him an early seat. I believe R1 eventually did score that inning and had R3 been properly placed at 3B where he should have, we would have gone home one batter sooner as Cottage Grove 10-runned Waterloo in 8 innings. It was a blown call – one I should never get wrong – but I did. We got lucky that this bonehead mistake didn’t impact the game – but sometimes kicked calls do. In my opinion the call had little effect on the outcome, however there’s never an excuse for making a wrong call and I am embarrassed I got that one wrong.

 

The moral of this story is this: We do our conscious very best every Sunday. At times – for reasons only the gods know – we develop that air-lock in the brain and just totally kick one. When that happens, as professional acting umpires, we just have to eat the consequences of our booted call. Hopefully – like my partner and me – we are conscientious enough to look up and correct our errors and never let the same one happen again.

 

Refresher on interference and obstruction …

Generally on interference, the ball is dead immediately; except when there is batter interference to the catcher’s attempt to pick off a stealing runner. When batter interference occurs, the play is allowed to continue and if the runner is out, the interference is ignored. The same is with umpire’s interference on a catcher attempting the same throw.

 

When interference is called the ball is dead immediately and no runner may advance, unless the result of the interference forces a runner. Example: R1 & R2, batted ball to F6. In attempting to field the ball R2 runs over F6. The ball is dead and no runners (R1 in this case) may advance. However, because B-R is not out at first on the play, R1 is “forced” to second base. R2 is out and the ball is dead.

 

Obstruction occurs when a runner is impeded from going to or returning to a base by the defense. Intent is not an issue with obstruction and as the rule states, he is entitled to the base he would have obtained had the obstruction not occurred. Not always is that the next base! In a game recently a batter aggressively makes the turn at first on a base hit. The left fielder with a gun fires a rocket back into the infield. The batter, now scrambles back to the bag and runs into the first baseman standing in line and near first base. The left fielder’s bullet is true and the runner is tagged out. I rule obstruction, call time and award the runner 1B. I soon get a visitor who insists that I “have to” award the runner second on the obstruction. “Not true,” I explain, as the runner is only entitled to the base he would have gotten had the obstruction not occurred, which in his case was first base.

 

As we’ve seen here, we can – and will – kick some very obvious calls. When we do, as a crew we should do our best to rectify the situation on the field and make the right call. In the case of Cottage Grove and Waterloo, we just kept going and corrected our mistake by re-reading the rules and brushing up on our knowledge. As umpires, we always strive to do our very best, but once in a while a little “crow” is on the menu. We learn, we go forward and we teach. That’s the purpose of this week’s play of the week: to teach our members from the mistakes we make in every attempt to minimize them. Probably another lesson from this week’s play of the week is to learn to avoid choosing me as a partner!

 

Have a great game, till next time …

Mark Ambrosius