Monday, May 23, 2022

Teachable - Expected the Unexpected on Texas Torpedo

After wild throws flew into both the right and left field walls in foul territory behind first and third base during Corpus Cristi's Friday night victory over Frisco in Double-A's Texas League, we revisited the umpire crew of three's task to officiate such a broken play.

Play: Leading off the bottom of the 1st inning, Frisco RoughRiders batter Jonathan Ornelas hit a line drive to left field, where CC Hooks left fielder Wilyer Abreu fielded the ball on a bounce. Abreu then threw to...second base? an attempt to hold Ornelas to a single, but overthrew his target, Abreu's throw launching itself all the way to the right field wall in foul territory near the field's tarp. First baseman Luke Berryhill retrieved the ball and then threw wildly past third base and to the left field wall in foul territory as Ornelas circled the bases for a single + three-base pair of errors.

In this quick Teachable, tmac reminds umpires to expect the unexpected and follows the paths and calls of 1B Umpire Harrison Silverman and 3B Umpire Willie Traynor, who both rule their respective overthrows alive and in play by giving the safe mechanic, signaling that the ball remained on the playing field and did not fall out of play (note that HP Umpire Tanner Dobson was likely screened from seeing the overthrow beyond the bases).

Video as follows:

Sunday, May 22, 2022

MLB Ejection 047 - Greg Gibson (2; Matt Blake)

HP Umpire Greg Gibson ejected Yankees pitching coach Matt Blake (fair ball call; QOCN) in the top of the 3rd inning of the #WhiteSox-#Yankees game. With one out and one on (R1), White Sox batter Tim Anderson hit a 1-1 changeup from Yankees pitcher Luis Severino on the ground, fielded along the third baseline by Severino and ruled a fair ball by HP Umpire Gibson. Replays indicate the batted ball appeared to strike Anderson's foot in the batter's box (this is not a reviewable play), the call was incorrect. At the time of the ejection, the game was tied, 0-0. The White Sox ultimately won the contest, 5-0.

This is Greg Gibson (53)'s 2nd ejection of 2022.
Greg Gibson now has -2 points in the UEFL Standings (0 Previous + 2 MLB - 4 Incorrect Call = -2).
Crew Chief Greg Gibson now has 2 points in Crew Division (2 Previous + 0 Incorrect Call = 2).
RelatedTmac's Teachable Moments - Let's Fix Replay (1/19/17).

This is the 47th ejection report of the 2022 MLB regular season.
This is New York's 4th ejection of 2022, 2nd in the AL East (TOR 5; NYY 4; BOS 3; BAL, TB 2).
This is Matt Blake's 1st ejection since Sept 8, 2021 (Edwin Moscoso; QOC = Y [Balls/Strikes]).
This is Greg Gibson's 2nd ejection of 2022, 1st since April 12 (Antoan Richardson; QOC = U [NEC]).

Wrap: Chicago White Sox vs. New York Yankees, 5/23/22 | Video as follows:

MLB Ejection 046 - Bill Welke (2; Kevin Cash)

HP Umpire Bill Welke ejected Rays manager Kevin Cash (strike three call; QOCY) in the top of the 5th inning of the #Rays-#Orioles game. With none out and none on, Rays batter Ji-Man Choi took a 3-2 fastball from Orioles pitcher Bryan Baker for a called third strike. Replays indicate the pitch was located over the inner half of home plate and below the midpoint (px -0.50, pz 3.23 [sz_top 3.25 / RAD 3.37]) and that all other pitches during the at-bat were properly officiated the call was correct.* At the time of the ejection, the Orioles were leading, 2-1. The Orioles ultimately won the contest, 7-6.

This is Bill Welke (3)'s 2nd ejection of 2022.
Bill Welke now has 2 points in the UEFL Standings (-2 Prev + 2 MLB + 2 Correct Call = 2).
Crew Chief Bill Welke now has 2 points in Crew Division (1 Previous + 1 Correct Call = 2).
*This pitch was located 2.68 vertical inches from being deemed incorrect.

This is the 46th ejection report of the 2022 MLB regular season.
This is the 21st manager ejection of 2022.
This is Tampa Bay's 2nd ejection of 2022, T-4th in the AL East (TOR 5; BOS, NYY 3; BAL, TB 2).
This is Kevin Cash's 1st ejection since Sept 1, 2020 (Chad Fairchild; QOC = U [Warnings]).
This is Bill Welke's 2nd ejection of 2022, 1st since May 14 (Marcus Thames; QOC = N [Check Swing]).

Wrap: Tampa Bay Rays vs. Baltimore Orioles, 5/22/22 | Video as follows:

Same Pitch Nets Different RoboUmp Calls by Feed

TV's home and away broadcast feeds disagreed with each other over whether HP Umpire Gabe Morales' ball four call during Eduardo Escobar's at-bat during Tuesday's Cardinals-Mets game was correct as one broadcast showed ball while the other had strike. Determining QOC from the visual strike zone box alone, thus, depends on whether one watched St Louis or New York's broadcast, as the TV called the same pitch two different ways depending on which feed was being used.

Although alarmingly common, RoboUmp's mostly-hidden secret of occasionally displaying two different strike zone and pitch representations for the same exact pitch took center stage during Game 1 of STL-NYM's doubleheader, but only to an esoteric few who actually watched both broadcast feeds and noticed the ambiguous absurdity on a ball four call that produced very little fanfare.

If you were to have watched the home Mets feed, you would have seen an apparent strike but if you were to have watched the visiting Cardinals feed, you would have seen an apparent ball. Video analysis indicates the two broadcasts used different on-screen graphic strike zone boxes for the same batter, on the same pitch.

The pitch data, however, is direct from MLB and confirms that Cardinals pitcher Miles Mikolas 3-2 sinker to Mets batter Escobar was correctly ruled ball four: With a px value of 0.25, pz 3.47, sz_bot 3.14 and RAD 3.26, the pitch missed high by 2.52 vertical inches, well outside of both UEFL f/x and Zone Evaluation's respective margins of error—the pitch was a ball, though if you were to have watched the wrong broadcast, you'd never know it.

Video as follows:

Saturday, May 21, 2022

Ask the Teachable - Rotation Replay & Plate Blocking

This Ask the Teachable takes us to Milwaukee, where Nationals batter-runner Lane Thomas was tagged out at home plate by Brewers catcher Omar Narvaez on an unsuccessful inside-the-park home-run attempt, ruled out by 1B Umpire Stu Scheurwater, who rotated home to fill in for HP Umpire Charlie Ramos, who rotated to third base to fill in for 3B Umpire CB Bucknor, who rotated to second base to fill in for 2B Umpire Jeff Nelson, who went into the outfield to officiate Thomas' fly ball to deep right-center field. This is an example of an umpire rotation on a batted ball to the outfield with no runners on base at the time of the pitch.

As we followed the batted ball off the wall, we saw Thomas hustling around the bases as Milwaukee right fielder Hunter Renfroe gathered the ball and threw to second baseman Kolten Wong, who threw to catcher Narvaez as Thomas arrived at home plate.

Replay Review
: Despite earlier issues with the clubhouse replay system in the 1st inning, by the time of this play in the top of the 7th inning, replay had been restored for both teams and thus as soon as Scheurwater made the out call at home plate, the 20-second decision timer began. Replays indicate the 20-second timer expired before Nationals manager Davey Johnson requested a review, meaning that Crew Chief Nelson properly denied Johnson's untimely request for a Manager's Challenge.

Plate Blocking Rule: Another issue here is whether or not catcher Narvaez blocked the runner Thomas' path to home plate. Recall that, pursuant to Official Baseball Rule 6.01(i)(2) pertaining to Collisions At Home Plate, the catcher is allowed to block the pathway of the runner under very specific circumstances. One of these is as follows: "Not withstanding the above, it shall not be considered a violation of this Rule 6.01(i)(2) if the catcher blocks the pathway of the runner in a legitimate attempt to field the throw (e.g., in reaction to the direction, trajectory or the hop of the incoming throw, or in reaction to a throw that originates from a pitcher or drawn-in infielder)."

Thus, because Wong's throw bounced and the trajectory of said through took the catcher into foul territory to receive it, the catcher is legally allowed to block the pathway of the runner.

Video as follows:

Sox-Yankees Donaldson Fight - Officiating Provocateurs

Benches cleared during Saturday's White Sox-Yankees game in New York during Josh Donaldson's 5th inning at-bat after a confrontation with Chicago catcher Yasmani Grandal, resulting in Umpire Greg Gibson issuing warnings to both teams. Of the four general types of game participants, adversaries and abusers are most likely to be involved in unsporting situations and we revisit our 2017 "Let's Talk - Mental Health in an Abusive Environment" article in the context of the Chicago-New York feud.

This, of course, invites the disclaimer and reminder that the game participant label applies to the participant's role in the game, not the participant's personal off-field attributes.

These two teams' animosity stems from, amongst others, Josh Donaldson's physical play in pushing Chicago baserunner Tim Anderson off of third base earlier in May, a play featured as an Ask the UEFL video that highlights 3B Umpire Chris Guccione's success in both properly calling Donaldson for illegally forcing Anderson off his base and effectively diffusing a potential fighting situation through strong game management. Rewinding the tape even further, Donaldson was upset with a strike call Grandal got from HP Umpire Dan Bellino in 2020, when Bellino ejected Donaldson for actions intended to ridicule in kicking dirt on home plate after hitting a home run against Chicago.

In studying the history of Chicago and New York's interdivisional bickering, we note that Donaldson appears to have historically been involved in other unsporting situations with other teams, as well as with umpires. For instance, Donaldson was one of our Top 10 MLB Hothead Players by Ejection Frequency in 2019, Donaldson's history of ejections—which doesn't include situations like the Anderson push or hard slide into second—suggests the possible presence in Chicago-New York of a player that would be classed as an adversary or abuser pursuant to the 2017 framework.

To review, the four types of game participants are allies, neutralsadversaries, and abusers, with allies comprising the most helpful and cordial team personnel who work with officials to help a game run smoothly and help diffuse volatile situations, whereas adversaries and abusers provoke the vast majority of on-field problems, with abusers crossing a definitive sportsmanship boundary.

When a player further provokes animosity with the opposing team, they cross into perhaps a new category of disruptor, a label borrowed from basketball that runs ancillary to the four types described above.

Thus, a player who is both an abuser and a disruptor may routinely harass or otherwise cause problems—just a general air of hostile tension—as well as disrupt the game, perhaps due to this hostility, and perchance cross over into causing problems with their opponents as well. (Similarly a player can be both an apparent ally and a disruptor in that the player appears cordial with officials but routinely incites and provokes with the other team).

As we stated in 2017, "Although getting away from an abuser may temporarily halt the potentially unsporting behavior—and it is appealing to keep the ejection- or technical foul-gun in its holster—chances are that a future call that goes against the abuser's team will be met with an episode of greater harassment. Remember, intimidation or being made to feel guilty is a tactic of abuse and must be dealt with assertively. Bullies thrive on passive victims' behavior."

The key here is to rely on both psychological game management and situation handling techniques as well as application of book rules to support disciplinary and other mitigative measures to remove problem players (and/or coaches) from the game.

In New York, Crew Chief Greg Gibson sought fit to issue warnings rather than eject personnel. In Chicago, Guccione simply separated the two players and prevented further escalation. In 2016, Dale Scott ejected Donaldson for his active role during the Blue Jays-Rangers benches-clearing brawl, as did Brian Gorman in 2019 when Donaldson's Atlanta Braves fought with the Pittsburgh Pirates after Donaldson was hit by a pitch.

Officiate evenhandedly, or as the rulebook's General Instructions to Umpires section states, "be courteous, impartial and firm, and so compel respect from all." You might just find that once you eject a problem player, your game will all of a sudden appear to run much more smoothly.

Video as follows:

Friday, May 20, 2022

MLB Ejection 045 - Ryan Additon (1; Willson Contreras)

HP Umpire Ryan Additon ejected Cubs catcher Willson Contreras (strike three call; QOCY) in the bottom of the 7th inning of the #Diamondbacks-#Cubs game. With one out and one on (R1), Cubs batter Contreras took a 1-2 fastball from Diamondbacks pitcher Caleb Smith for a called third strike. Replays indicate the pitch was located over the inner edge of home plate and waist-high (px -0.87, pz 2.71) and that all other pitches during the at-bat were officiated properly, the call was correct.* At the time of the ejection, the Diamondbacks were leading, 9-5. The Diamondbacks ultimately won the contest, 10-6.

This is Ryan Additon (67)'s 1st ejection of 2022.
Ryan Additon now has 4 points in the UEFL Standings (0 Previous + 2 MLB + 2 Correct Call = 4).
Crew Chief Mark Carlson now has 4 points in Crew Chief (3 Previous + 1 Correct Call = 4).
*UEFL Rule 6-2-b-1 (Kulpa Rule): |0| < STRIKE < |.748| < BORDERLINE < |.914| < BALL.
This pitch was located 0.53 horizontal inches from being deemed incorrect.

This is the 45th ejection report of the 2022 MLB regular season.
This is the 17th player ejection of 2022. Prior to ejection, Contreras was 0-4 (2 SO).
This is Chicago's 2nd ejection of 2022, T-1st in the NL Central (CHC, PIT, STL 2; CIN, MIL 0).
This is Willson Contreras' 1st ejection since Sept 18, 2021 (Chad Whitson; QOC = Y [Balls/Strikes]).
This is Ryan Additon's 1st ejection since June 19, 2021 (David Bell; QOC = Y-c [Check Swing]).

Ask UEFL - KBO Run Nullified Due to Force Double Play

This Ask the UEFL question comes from the Korea Baseball Organization, as umpires cancelled a game-winning run in extra innings after a fly ball to left field turned into a double-play on two trailing runners.

During Wednesday's KBO matchup between SSG Landers and Doosan Bears, Bears batter Jo Soo-haeng stepped to the plate with the bases loaded and one out, hitting a fly ball to shallow left field. SSG left fielder Oh Tae-gon dove in attempt to catch the sinking fly, but our 3B Umpire going out on the play signaled "safe" to rule no catch, or trap.

While leading baserunner R3 Kim Jae-ho appeared to score far ahead of the defense retiring trailing runners R2 Jung Soo-bin (tagged out between second and third) and R1 An Jae-seok (forced out at second base), umpires ruled the winning run had not scored after all, leading Doosan to challenge the call.

The call was confirmed via Replay Review: both R1 and R2 were forced out and no run scored, despite R3 touching home plate far in advance of R1 and R2 being put out.

The reason is the same one we see on "standard" inning-ending double plays on a ground ball to the shortstop, who throws to the second baseman for one, and back to the first base for two, negating any potential runs due to the third out force play.

This is not a Time Play: It is a simply a pair of force outs on R2 and R1 for the second and third outs of the inning, respectively. Had the defense instead tagged second base to force R1 out prior to tagging R2, R1's retirement as the inning's second out would have removed the force on R2 such that tagging R2 somewhere between second and third base would be a non-force tag play. In such an event, this would be a time play as R2's third out would no longer be due to a force out, meaning that R3's run would count due to R3 touching home plate prior to the third out (which is not a force out) being made.

The relevant rule, to review, is Official Baseball Rule 5.08(a) Exception, which states, "A run is not scored if the runner advances to home base during a play in which the third out is made (1) by the batter-runner before he touches first base; (2) by any runner being forced out; or (3) by a preceding runner who is declared out because he failed to touch one of the bases."

Although not strictly necessary for a force-third-out play like this one in which OBR 5.08(a) specifically cancels the run as opposed to umpire judgment that is used during a time play, a "score the run" or "disallow the run" signal might help communication-wise. Remember, the wash out signal is distinct from the safe mechanic in that washing out a run is signaled by raising both arms above the head whereas the safe sign is much more horizontal in nature.

In sum, though unconventional, this was an inning-ending force out as both R2 and R1 were forced to advance to their next bases by virtue of the batter becoming a runner (uncaught fly ball) | Video as follows:

Thursday, May 19, 2022

MLB Ejection 044 - Ramon De Jesus (1; Amir Garrett)

2B Umpire Ramon De Jesus ejected Royals pitcher Amir Garrett (balk call by 1B Umpire Shane Livensparger; QOCN) in the top of the 9th inning of the #WhiteSox-#Royals game. With two out and one on (R1), 1B Umpire Shane Livensparger called Garrett for a balk after a 0-2 delivery to White Sox batter Josh Harrison, advancing baserunner R1 Yasmani Grandal to second base. Replays indicate Garrett appeared to come to a stop in his delivery, a requirement for pitchers working out of Set Position, and did not otherwise commit and illegal pitching act, the call was incorrect.* At the time of the ejection, the White Sox were leading, 7-4. The White Sox ultimately won the contest, 7-4.

This is Ramon De Jesus (18)'s 1st ejection of 2022.
Ramon De Jesus now has 0 points in the UEFL Standings (0 Prev + 2 MLB - 2 Incorrect-Crewmate = 0).
Crew Chief Alfonso Marquez now has 3 points in Crew Division (3 Previous + 0 Incorrect Call = 3).

This is the 44th ejection report of the 2022 MLB regular season.
This is the 16th player ejection of 2022. Prior to ejection, Garrett's line was 1.0 IP, 0 ER, Balk.
This is Kansas City's 2nd ejection of 2022, T-1st in the AL Central (DET, KC 2; CWS, MIN 1; CLE 0).
This is Amir Garrett's 1st ejection since August 27, 2019 (Ryan Blakney; QOC = Y-c [Check Swing]).
This is Ramon De Jesus' 1st ejection since August 18, 2021 (Craig Counsell; QOC = N [Balls/Strikes]).

MLB Ejection 043 - Manny Gonzalez (2; Anthony Rizzo)

HP Umpire Manny Gonzalez ejected Yankees batter Anthony Rizzo (strike one and two call; QOCN) in the top of the 8th inning of the #Yankees-#Orioles game. With none out and none on, Yankees batter Rizzo took a first-pitch slider and 0-1 changeup from Orioles pitcher Joey Krehbiel for called first and second strikes before subsequently striking out swinging. Replays indicate the first pitch of the at-bat, ruled strike one, was located over the heart of home plate and below of the hollow of the knee (px 0.15, pz 1.43 [sz_bot 1.73 / RAD 1.61 / MOE 1.52]) and that the 0-1 pitch was located over the heart of home plate and at the hollow of the knee (px 0.17, pz 1.52 [sz_bot 1.73 / RAD 1/61 / MOE 1.52]), the call was incorrect.* At the time of the ejection, the game was tied, 5-5. The Orioles ultimately won the contest, 9-6.

This is Manny Gonzalez (79)'s 2nd ejection of 2022.
Manny Gonzalez now has 2 points in the UEFL Standings (4 Previous + 2 MLB - 4 Incorrect Call = 2).
Crew Chief Chris Conroy now has -1 points in Crew Division (-1 Previous + 0 Incorrect Call = -1).
The 0-0 pitch was located 1.08 vertical inches from being deemed correct.

This is the 43rd ejection report of the 2022 MLB regular season.
This is the 15th player ejection of 2022. Prior to ejection, Rizzo was 2-4 (SO) in the contest.
This is New York's 3rd ejection of 2022, T-2nd in the AL East (TOR 5; BOS, NYY 3; BAL 2; TB 1).
This is Anthony Rizzo's 1st ejection since July 24, 2019 (Jordan Baker; QOC = Y [Balls/Strikes]).
This is Manny Gonzalez's 2nd ejection of 2022, 1st since April 29 (Mike Matheny; QOC = Y [Out/Safe]).

Wrap: New York Yankees vs. Baltimore Orioles, 5/19/22 | Video as follows: