![]() |
OBS call
Well, both umpires had the call. 3BU did it correctly, PU, IMO, had it right, but not the proper mechanics, even for MLB
Play is here BTW, this is also a great example as to why you discuss issue with one team representative and that is it. You ended up with 6 umpires providing personal explanations for 20 people. Should have discussed it with the manager and left the field |
Quote:
|
The way I am hearing virtually everyone who will comment for the record explain the play, if Middlebrooks had been killed on the play and his body was tripped over by Craig, the call is the same.
|
Quote:
|
Quote:
Rita |
Quote:
|
Quote:
DeMuth just gave a safe signal, then pointed at third base. |
Quote:
|
Quote:
IOW, the umpire is to kill the play, then make the ruling. In this case, when two umpire make a call on the same runner, they should get together to ensure they are on the same page with the same call. |
Quote:
Now, the effects may be different; but the mechanic is if the obstructed runner is apparently out when protected, the umpire is to kill the play (dead ball or time called), NOT declare out nor safe on the initial play. |
Quote:
|
Quote:
Also - PU did not know what award 3BU had in mind - so he's not the one that awards home. |
Quote:
Quote:
What the PU did was communicate "runner safe due to the call my partner made at 3rd." Should he have done that? Well, by the book (or even by sound umpiring standards), no. Were there things that could have happened (e.g. Boston appealing) that would have resulted in a big mess? Absolutely. But, no one watching was confused as to what the call was or why. JMO, of course. I haven't heard a single fan, commentator, talking head, sports show host, etc., who was confused about what the call was. Whereas killing the ball and conferring with the 3rd base umpire on the award.... really.... how do you think THAT would have worked out in the fan-base, media, etc.? My point was that the way he did it better communicated to the fans what was going on, and I'll add to that: it also better sold the call than the correct mechanics would have. Again, JMO. |
OK AGREE, but this forum is also about improving ourselves as umpires and knowing our mechanics. :cool:
My leg-raising question still stands. :rolleyes: Found it interesting that in 4 games of 14&U, 12&U on Saturday; there was only one OBS. :) |
Quote:
|
I'm one of those that is wondering if the runner ever did touch the plate. But when the umpire called him safe when he clearly was tagged out before reaching home was initially confusing.
I suspected OBS was going to be the call but watching it live the first time, it wasn't obvious to me. All I focused on was yet another throw from the plate area sailing off into never land. BTW, Nava did a great job of backing up that throw, getting to the ball, and making a great throw himself. None of which will be remembered. This is certainly going down as one of the more unconventional World Series. Not sure if it will ever qualify as a classic. |
Quote:
|
Quote:
|
Quote:
There was no play being made on the obstructed runner. At the time of the obstruction the ball was loose in LF. In this case (OBR rule 7.06(b )) play continues and ends when playing action ceases. At that time the umpires may award whatever they feel is necessary to negate the obstruction. This can be nothing if they think the runner would have been out anyhow and range to awarding the run as they did here. |
Quote:
|
Quote:
If this had been the game-tying run, for example, the play would have been killed when the tag was made, and there would not have been an opportunity for the defense to play on the batter-runner. But I know you know that. |
Quote:
|
Quote:
Originally Posted by CecilOne Do you think the leg-raising is what decided the call? Quote:
|
Quote:
Quote:
MLB rule 7.06(a) states that when a play is made on the OBS runner, the umpire shall call time. Nowhere does it state that such a play be made by the defender who caused the OBS. To me, when the catcher tags the OBS runner, that is your play which ends action. Quote:
|
Quote:
Quote:
Quote:
|
Quote:
|
Quote:
Turns out having the ability to cut and paste the whole thing made it more like contributing a $1.45 than 2 cents. |
Quote:
|
Quote:
|
Quote:
For example, a runner caught in a rundown between third and home is obstructed as he attempts to dive back into third base. If it was one catch-all obstruction rule as it is in other organizations, the award would be third base, since that's the base he would have achieved minus the obstruction. But the MLB rule mandates an award of home for the runner. The real question is, Why the need for a harsher penalty? I dunno. Maybe the rulesmakers felt that without it, it would lead to unwanted shenanigans by the defense. Suppose when a pitcher throws to first base to hold the runner, the first baseman intentionally positioning himself in the runner's path back to the bag to prevent him from accessing it. Calling obstruction and putting the runner safely on first doesn't prevent the first baseman from continuing to do this until, by chance, they do throw a runner out just before the hindrance takes place. Awarding the runner second base after the first obstruction violation puts an immediate end to this. |
Quote:
NFHS tried a similar tactic with their softball rules several years back...the penalty for obstruction was to advance the runner at least one base. Didn't matter where the obstruction was, which direction the runner was heading, the degree of the severity of the obstruction, etc. If obstruction was called, the runner got the next base automatically. What happened was that umpires became reluctant to call obstruction since the penalty was so harsh. Basically, a defender had to knock somebody over in order for obstruction to be called. |
All times are GMT -5. The time now is 08:58am. |