I like that Patrick does this. He takes a play, explains it from different aspects, and renders a decision. Working with different partners all the time, I've learned that not everyone does everything exactly the same way, but many feel that they are doing it right, and that they are always right. The key here is "judgment." Good judgment comes from experience both in actual games, and in continued study of the rules. The more we see situations, and the more we read and consider situations, the more ready we are to render our judgment, "our opinion," quickly, and more accurately. The best umpires are those who really do know the rules, know the mechanics, and know how to work with their partners. Any time there is more than one umpire, you are working as a team, and it is best done when you work together.
Great video. Only note I’d like to make is temperament of the game at the time. If it’s been that type of game. An ejection may be warranted before game gets out of hand later.
I’m wondering if the runner is reacting to the fielder taking a step in fair territory and the runner is thinking of going foul to get around… Very tough play here
That's what I see, too. The fielder moves into fair territory, then both the fielder and the runner react in the same direction and move toward foul territory. I have obstruction, not malicious contact. (The runner ducks to protect himself because he knows contact is coming and he knows a ball is probably coming.)
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
After watching the college world series this year where umps are wearing cop-style body cams, it is amazing the number of plays in which "bangers" occur! These are the BEST umps available and with the technology available today, they still get it right 90% of the time. Feel for the rest of us poor schmucks that have to deal with none of the technology for our aid + bonehead coaches that STILL think that "the tie goes to the runner", etc. I'm not sure that the runner in this play intended to bowl over the 3rd baseman as he had maybe :01 to react at the end of the play. Patrick does a great job in breaking the play down thoroughly. U1 was WAY too slow in moving over to assist on the play. I work Legion and HS baseball and feel too many of our brethren spend little to no time viewing stuff like this to sharpen their game! I've been doing this 40 years and am no "expert" yet.
I tried umping and couldn't hack it. We had 3 levels of players. At the lowest level players were out or safe by a foot just about every play. Easy to Umpire. The next level the players were out or safe by inches so it was much harder to umpire. The top level the players were out or safe was less than an inch and very hard to umpire. I remember one play where the ball hit the second baseman's glove and went up in the air. I thought well play over. Then out of nowhere the shortstop ran over and grabs the ball out of the air to fire it to first a fraction of a second before the batter got there. I knew then I was out of my league umping with players that could do that play.
I like this video. It shows a side of umpiring people seldom see or think about. To umpire you have to learn "where" to go, be, to get the best angle. Few people realize this, and think all umps need to know is the rules. Not True.
Great video. I would have called this offensive interference personally; by R3 impeding/hindering the 3B in his attempt to catch a throw. A runner's normal route to a base would have been to attempt to go to the side of the fielder to get to the bag. Here, the runner creates contact to do 1 of 2 things; either try and buy an obstruction call, OR dislodge the ball that the 3B is about to catch. Imagine R3 rather than lower his shoulder and creating contact to attempt to dislodge, reaches out with his hand and swipes at the 3B glove arm (a la A-Rod) - we would have offensive interference. Just because the 3B catches the ball doesn't negate the ability to call interference IMO - the language of impede and hinder just mean it made it harder on the player etc. I completely agree with everything said on Umpire positioning though - Angles are your friend!
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
@@royparker6364 sounds good to me; tough play to call, and I wasn't there so I will always defer to the judgement of the umpires on the field (I love your situational thought you shared above of pre-play planning, knowing the defense might not go home due to score etc)- we don't get video replay to look at dozens of times while we're on the field (sometimes wish we could have it!).
I feel like I'm back coaching 8-year-olds again ... where every fielder holds the ball WAY too long. Throw the ball! THROW THE BALL!!! In real time on the first viewing, I have obstruction on F5 ... mainly because F2 held the ball too long. On replay, I agree with your breakdown at 6:00 and the runner is out ... and for the reasons you give at 11:00, I'd call it Interference rather than malicious contact (or better, if there was a tag ... I can't tell in the video ... then just an out).
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
8:30 time stamp. Your breakdown here is what I was taught to do in this situation by a former double A umpire. He pre-gamed this (the first time I had ever even thought of anything like this) - And sure enough, it happened in that game. He had a close play at home for an out, and I was at 2nd base for the close banger there for an out. Because we were both in great positions - no one said a word. (this was a college game using 2 man mechanics)
at first I had obstruction then I saw the runner deviate from his path to create contact. I wouldn't rule that he had intent to dislodge the ball rather to make contact and get an obstruction call. I think the perfect call is the the no call, out.
Another possibility is Manufactured Obstruction which this appears to be. Maybe it's malicious as well. It could be interference as an attempt to dislodge the ball. No obstruction regardless. If he dislodges the ball, interference, runner is out. I had a 13 year old in an all star game the other day that manufactured an obstruction call rounding first. You never know what's going to happen out there.
I have obstruction prior to the tag (since there is no ‘in the act of fielding the throw’ clause in NFHS). However, there is a case for intentional interference. I don’t believe anything was excessive enough to warrant calling it malicious. Though, I am not sure that the runner intentionally changed his path to create contact/obstruction. He may have been turning his head back toward 3rd, or possibly working away from F6 covering the base-all without knowledge of F5’s location.
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
I like that Patrick does this. He takes a play, explains it from different aspects, and renders a decision. Working with different partners all the time, I've learned that not everyone does everything exactly the same way, but many feel that they are doing it right, and that they are always right. The key here is "judgment." Good judgment comes from experience both in actual games, and in continued study of the rules. The more we see situations, and the more we read and consider situations, the more ready we are to render our judgment, "our opinion," quickly, and more accurately. The best umpires are those who really do know the rules, know the mechanics, and know how to work with their partners. Any time there is more than one umpire, you are working as a team, and it is best done when you work together.
Great video. Only note I’d like to make is temperament of the game at the time. If it’s been that type of game. An ejection may be warranted before game gets out of hand later.
I’m wondering if the runner is reacting to the fielder taking a step in fair territory and the runner is thinking of going foul to get around…
Very tough play here
That's what I see, too. The fielder moves into fair territory, then both the fielder and the runner react in the same direction and move toward foul territory. I have obstruction, not malicious contact. (The runner ducks to protect himself because he knows contact is coming and he knows a ball is probably coming.)
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
After watching the college world series this year where umps are wearing cop-style body cams, it is amazing the number of plays in which "bangers" occur! These are the BEST umps available and with the technology available today, they still get it right 90% of the time. Feel for the rest of us poor schmucks that have to deal with none of the technology for our aid + bonehead coaches that STILL think that "the tie goes to the runner", etc. I'm not sure that the runner in this play intended to bowl over the 3rd baseman as he had maybe :01 to react at the end of the play. Patrick does a great job in breaking the play down thoroughly. U1 was WAY too slow in moving over to assist on the play. I work Legion and HS baseball and feel too many of our brethren spend little to no time viewing stuff like this to sharpen their game! I've been doing this 40 years and am no "expert" yet.
I tried umping and couldn't hack it. We had 3 levels of players. At the lowest level players were out or safe by a foot just about every play. Easy to Umpire. The next level the players were out or safe by inches so it was much harder to umpire. The top level the players were out or safe was less than an inch and very hard to umpire. I remember one play where the ball hit the second baseman's glove and went up in the air. I thought well play over. Then out of nowhere the shortstop ran over and grabs the ball out of the air to fire it to first a fraction of a second before the batter got there. I knew then I was out of my league umping with players that could do that play.
I like this video. It shows a side of umpiring people seldom see or think about. To umpire you have to learn "where" to go, be, to get the best angle. Few people realize this, and think all umps need to know is the rules. Not True.
Great video. I would have called this offensive interference personally; by R3 impeding/hindering the 3B in his attempt to catch a throw. A runner's normal route to a base would have been to attempt to go to the side of the fielder to get to the bag. Here, the runner creates contact to do 1 of 2 things; either try and buy an obstruction call, OR dislodge the ball that the 3B is about to catch. Imagine R3 rather than lower his shoulder and creating contact to attempt to dislodge, reaches out with his hand and swipes at the 3B glove arm (a la A-Rod) - we would have offensive interference. Just because the 3B catches the ball doesn't negate the ability to call interference IMO - the language of impede and hinder just mean it made it harder on the player etc. I completely agree with everything said on Umpire positioning though - Angles are your friend!
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
@@royparker6364 sounds good to me; tough play to call, and I wasn't there so I will always defer to the judgement of the umpires on the field (I love your situational thought you shared above of pre-play planning, knowing the defense might not go home due to score etc)- we don't get video replay to look at dozens of times while we're on the field (sometimes wish we could have it!).
I feel like I'm back coaching 8-year-olds again ... where every fielder holds the ball WAY too long. Throw the ball! THROW THE BALL!!! In real time on the first viewing, I have obstruction on F5 ... mainly because F2 held the ball too long. On replay, I agree with your breakdown at 6:00 and the runner is out ... and for the reasons you give at 11:00, I'd call it Interference rather than malicious contact (or better, if there was a tag ... I can't tell in the video ... then just an out).
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
8:30 time stamp. Your breakdown here is what I was taught to do in this situation by a former double A umpire. He pre-gamed this (the first time I had ever even thought of anything like this) - And sure enough, it happened in that game. He had a close play at home for an out, and I was at 2nd base for the close banger there for an out. Because we were both in great positions - no one said a word. (this was a college game using 2 man mechanics)
Well done.
at first I had obstruction then I saw the runner deviate from his path to create contact. I wouldn't rule that he had intent to dislodge the ball rather to make contact and get an obstruction call. I think the perfect call is the the no call, out.
I wonder if his path deviated because he was actually looking back at the catcher while running to 3rd. Not sure he ever saw 3B before contact.
@@MwD676 all the more reason for a no call I believe…good point
What is the mechanic for malicious contact?
I know the mechanic for interference and obstruction, but what about “malicious contact?”
WHAT is the mechanic for “malicious contact?”
I know the mechanic for interference and obstruction, but what about “malicious contact?”
Simply call "Time" and then if it is by the offense I'd point at the runner and say, "That's malicious" and then signal out followed by ejection.
Another possibility is Manufactured Obstruction which this appears to be. Maybe it's malicious as well. It could be interference as an attempt to dislodge the ball. No obstruction regardless.
If he dislodges the ball, interference, runner is out.
I had a 13 year old in an all star game the other day that manufactured an obstruction call rounding first. You never know what's going to happen out there.
I have obstruction prior to the tag (since there is no ‘in the act of fielding the throw’ clause in NFHS). However, there is a case for intentional interference. I don’t believe anything was excessive enough to warrant calling it malicious.
Though, I am not sure that the runner intentionally changed his path to create contact/obstruction. He may have been turning his head back toward 3rd, or possibly working away from F6 covering the base-all without knowledge of F5’s location.
I sent this in to get clarification. I was the umpire on second base. I had to stay out of the way of the possible throw to first. In this situation the defense could have afforded to give 1 run up due to the score. We called obstruction because I seen the third baseman take a step towards the runner giving no clear path to the base. As Patrick said, the runner did not see the ball throw so in mu mind how did he know which player to run into? Hindsight is 20/20 but at the time I felt like you did the ball could have been delivered earlier and he may have thrown it to the wrong player. Short stop was standing on third.
Wasn’t he tagged anyway?
He was. But that does not impact whether or not we have malicious contact, obstruction, or interference!
4:12, typo: *Base
No it's bae 😂