Nominations for the Umpire Ejection Fantasy League's Postseason Awards have begun—fill out the form to vote for eligible umpires* who, during the past season, have demonstrated significant performances to fit the terms of one of several awards (UEFL Rule 4-4).
Link to Postseason Awards Ballot (also appears below).
a. Umpire of the Year (min. 1 / max. 1 umpire) [+5 pts]
b. Promising Umpire of the Year (min. 1 / max. 2) [+3]
c. Honorable Umpire of the Year (min. 0 / max. 2) [+2]
d. Fill-In Umpire of the Year (min. 0 / max. 1) [+2]
e. Most Improved Umpire (min. 0 / max. 1) [+1]
f. Crew Chief of the Year (min. 0 / max. 1) [+1]
g. Best Ejection of the Year (min. 0 / max. 2) [Link: 2019 MLB Ejections (UEFL Portal)] [+1]
h. Most Disappointing Season (min. 0 / max. 1) [-1]
Click here for the complete history and list of UEFL Postseason Awards recipients
An eligible umpire may be selected for as many or as few awards as you wish; Ballots will be accepted until 11:50 PT on Sunday, November 3, with awards distribution beginning on Monday, November 4.
Triple-A Umpires with at least 115 MLB games officiated in 2019 are eligible to be written in (via comment) for any UEFL Award, in addition to the Fill-In Umpire of the Year award. In 2019, the following call-up umpires officiated at least 115 MLB games and are eligible for write-in: Jansen Visconti (142), Jeremie Rehak (130), Ryan Blakney (125), Nic Lentz (123), Chris Segal (123), Sean Barber (120). Chad Whitson was hired to the MLB staff mid-season and is eligible for all awards except d (Fill-In Umpire of the Year).
Definitions:
a. Umpire of the Year: This Umpire has been the best MLB Umpire the past year, bar none. This Umpire has been more dedicated, professional, and positive than all others. This award will be given to one umpire.
b. Promising Umpire of the Year: This Umpire has been dedicated, professional, and has worked hard. Perhaps a rising star, the Promising Umpire of the Year is an umpire to keep an eye on, for an expectation of great things down the line. Formerly known as Noteworthy Umpire of the Year, this award will be given to one or two umpires.
c. Honorable Umpire of the Year: This Umpire has been the most honorable Umpire during the past year. Perhaps through Community Service, or through struggling with and overcoming his own difficulties, this Umpire has been the most personally admirable of all. This award may or may not be given to either one or two umpires.
d. Fill-In Umpire of the Year: This Umpire has been the best AAA Call-Up Umpire the past year, bar none. This Umpire has been the most dedicated, professional, and positive AAA/Non-MLB Full Time Umpire of all non-MLB Full Time Umpires. This award may or may not be given to a maximum of one umpire.
e. Most Improved Umpire of the Year: This Umpire has improved his overall performance from the previous season more noticeably than any other Umpire. Generally, this umpire has developed into a solid arbiter within the past year. This award may or may not be given to a maximum of one umpire.
f. Crew Chief of the Year: This Umpire has been the best MLB Umpire Crew Chief, the past year, bar none. This Umpire has led his crew(s) better than all others. This award will be given to one umpire.
g. Best Ejection of the Year: In the form of "Ejection 123: Umpire (1)," this award recognizes the best ejection(s) of the year. Nominated and selected due to form, mechanics, entertainment value, reason for ejection, or overall quality, the Best Ejection of the Year is awarded to one or two umpires for one or two specific ejections. The award may be given to one umpire for two separate ejections, in which case, he receives one point for each ejection.
h. Most Disappointing Season: This Umpire has demonstrated a regression in ability, and might have had a regrettable incident(s) occur in-season. The Most Disappointing Season award may or may not be given to a maximum of one umpire.
Video & Ballot as follows:
Thursday, October 31, 2019
Wednesday, October 30, 2019
Discussion of 2019 World Series
Welcome to the 2019 #WorldSeries discussion and liveblog at Close Call Sports. We'll list each game's home plate umpire and provide postgame scores, as well as analysis and other commentary pertaining to rules situations and other umpiring elements throughout the World Series.
Alan Porter takes Game 1 of the fall classic for World Series Crew Chief Gary Cederstrom's crew, the full list of which is available at the following link.
Related: 2019 MLB World Series Umpire Crew Roster.
- 10/22 WAS@HOU Gm 1: Alan Porter: 113/115 Balls + 48/49 Strikes = 161/164 = 98.2%. +3 HOU.
- 10/23 WAS@HOU Gm 2: Doug Eddings: 116/123 Balls + 52/56 Strikes = 168/179 = 93.9%. +5 HOU.
- 10/25 HOU@WAS Gm 3: Gary Cederstrom: 112/116 Balls + 53/56 Strikes = 165/172 = 95.9%. +5 HOU.
- 10/26 HOU@WAS Gm 4: James Hoye: 131/136 Balls + 45/48 Strikes = 176/184 = 95.7%. +0 Nu.
- 10/27 HOU@WAS Gm 5: Lance Barksdale: 96/97 Balls + 41/46 Strikes = 137/143 = 95.8%. +0 Nu.
- 10/29 WAS@HOU Gm 6: Sam Holbrook: 101/102 Balls + 51/56 Strikes = 152/158 = 96.2%. +0 Nu.
- 10/30 WAS@HOU Gm 7: Jim Wolf: 123/125 Balls + 46/52 Strikes = 169/177 = 95.5%. +2 WAS.
Series Complete (WAS Def HOU 4-3): 1128/1177 = 95.8%. +11 HOU.
Note: The highest plate score during the 2018 World Series was Jeff Nelson's 98.3% (WS Gm 5).
The highest plate score during the 2018 Postseason was Joe West's 99.4% (ALCS Gm 3).
The highest plate score during the 2019 Postseason, thus far, is James Hoye's 99.3% (ALDS 4).
Live Blog: Join the CCS Crew for live postseason discussion and analysis (Java required):
Alan Porter takes Game 1 of the fall classic for World Series Crew Chief Gary Cederstrom's crew, the full list of which is available at the following link.
Related: 2019 MLB World Series Umpire Crew Roster.
- 10/22 WAS@HOU Gm 1: Alan Porter: 113/115 Balls + 48/49 Strikes = 161/164 = 98.2%. +3 HOU.
- 10/23 WAS@HOU Gm 2: Doug Eddings: 116/123 Balls + 52/56 Strikes = 168/179 = 93.9%. +5 HOU.
- 10/25 HOU@WAS Gm 3: Gary Cederstrom: 112/116 Balls + 53/56 Strikes = 165/172 = 95.9%. +5 HOU.
- 10/26 HOU@WAS Gm 4: James Hoye: 131/136 Balls + 45/48 Strikes = 176/184 = 95.7%. +0 Nu.
- 10/27 HOU@WAS Gm 5: Lance Barksdale: 96/97 Balls + 41/46 Strikes = 137/143 = 95.8%. +0 Nu.
- 10/29 WAS@HOU Gm 6: Sam Holbrook: 101/102 Balls + 51/56 Strikes = 152/158 = 96.2%. +0 Nu.
- 10/30 WAS@HOU Gm 7: Jim Wolf: 123/125 Balls + 46/52 Strikes = 169/177 = 95.5%. +2 WAS.
Series Complete (WAS Def HOU 4-3): 1128/1177 = 95.8%. +11 HOU.
Note: The highest plate score during the 2018 World Series was Jeff Nelson's 98.3% (WS Gm 5).
The highest plate score during the 2018 Postseason was Joe West's 99.4% (ALCS Gm 3).
The highest plate score during the 2019 Postseason, thus far, is James Hoye's 99.3% (ALDS 4).
Live Blog: Join the CCS Crew for live postseason discussion and analysis (Java required):
Labels:
Discussions
,
UEFL
,
Umpire Odds/Ends
World Series Interference - Blame the Rule, not the Umpire
Nationals batter Trea Turner's runner's lane interference, Manager Dave Martinez's argument, and umpire Sam Holbrook's #WorldSeries ejection: here's a comprehensive analysis of the play, the history of baseball's RLI rule, and what Turner could have done differently to avoid this call.
Summary: We have a runner on first with none out. Turner hits a ground ball to Astros pitcher Brad Peacock, who throws toward first baseman Yuli Gurriel as Turner arrives at first base. Gurriel's glove collides with Turner's leg and the baseball winds up hitting Turner's thigh, resulting in HP Umpire Holbrook's call of interference. Martinez is furious and after the half-inning ends, he works himself into a tizzy and is ejected.
Related Post: MLB Ejection P1 - Sam Holbrook (3; Dave Martinez) (10/29/19).
Reaction: MLB Chief Baseball Officer Joe Torre says Holbrook got the call right, the media largely says otherwise, and here we are...trying to explain a controversial call to readers who probably have their own strong opinions on the matter and aren't looking to be swayed one way or the other.
Precedent: CloseCallSports.com is full of prior runner's lane interference plays. For instance, Bill Miller ejected Joe Maddon in August 2018 over a properly officiated interference call.
Related Post: MLB Ejection 116 - Bill Miller (1; Joe Maddon) (8/10/18).
The Rule: It always helps to start with the rule. So many people fail right out of the box because they never cite the rule, so here it is, Official Baseball Rule 5.09(a)(11): "A batter is out when—In running the last half of the distance from home base to first base, while the ball is being fielded to first base, he runs outside (to the right of) the three-foot line, or inside (to the left of) the foul line, and in the umpire’s judgment in so doing interferes with the fielder taking the throw at first base, in which case the ball is dead."
Sidebar: OBR 5.09(a)(11) Comment states, "The batter-runner is permitted to exit the three-foot lane by means of a step, stride, reach or slide in the immediate vicinity of first base for the sole purpose of touching first base." Be advised that a runner must be within the lane in order to exit it. It is physically impossible to exit something that one has never been in.
You'll notice there's nothing about a "direct route" to the base (Joe Buck), or "center of the base" (John Smoltz), "grass" (Buck), or even "allowed to be inside the line for his last step" (Tom Verducci), etc. When talking about a rule, it's generally helpful to cite the rule, so that's what we have done here. Verducci was the closest to getting the rule right, but he forgot one key aspect: a runner is not protected if said runner ran the entire length to first base to the left of (or the right of) the runner's lane.
Translation: This means that Turner could have avoided being called out for interference by doing just one thing: running within the lane at some point during his journey to first base. Replays conclusively indicate he failed to run within the lane at any point, which subjects him to an interference call if the second criterion of the rule is met: "interferes with the fielder taking the throw at first base."
Brief History: The three-foot-wide runner's lane at the 45' mark was added to baseball fields in 1882 (National League) and 1884 (American Association), and its purpose was to prevent collisions between batter-runners and first basemen (sound familiar?). This is because in the 19th century, first base was located half in fair territory and half in foul territory. The prevailing logic was that the lane would guide the runner to the foul territory half of the bag, while the fielder would tag the fair territory side, thus preventing injury.
In 1887, however, the NL and AA agreed to move first and third base 7.5 inches toward second base, so as to place both bases entirely within fair ground—which would make adjudicating fair/foul near the corner bases a whole lot easier.
Yet the runner's lane remained in its foul territory location, and a rule was subsequently adopted to give the batter-runner permission to exit the lane in the vicinity of first base in order to touch the base, which was now entirely in fair territory—to cross over, so to speak.
Fast forward to today, collisions between runners and first basemen are exceedingly rare (unless you're Manny Machado), yet the lane and interference rules remain. As former umpire Jim Evans once opined, "Going to first you have the runner's lane, which the runner is supposed to stay in, which I think is really antiquated. The runner's lane violation was to prevent the collisions at first base, not interference with the throw."
Sidebar: Softball solves this problem by having two bases sitting next to each other: one for the fielder and one for the runner.
Interference Analysis: The intriguing part about Turner's interaction with Gurriel is that a minor collision, of sorts, actually did occur in that Gurriel's hand/wrist/glove made contact with Turner in fair territory.
Yes, Turner had reason to be in fair territory in the immediate vicinity of first base (to touch it), but he got there illegally—by running to the left of the lane the entire way down the baseline.
To review, here's the first professional rules interpretation from Wendelstedt (Evans agrees, as do all codes): "A runner that is running the entire distance outside of the running lane will not be protected if he interferes with a play at first base, even if it is in his last stride or step to the base. In order to be protected, this last step must be when he first exits the running lane" (recall that in order to exit, one must first be within).
For illustration's sake, here's Evans: "A runner who has advanced the entire distance from home plate to first in fair territory making no effort to run within the lane is not extended the same leniency as the runner who runs in the lane as required and then cuts into fair territory near the base to touch it."
The second concerns the throw: "The determination is not whether the throw is true, but whether it could still reasonably retire the runner."
Because of the contact between Gurriel and Turner, which occurred a fraction of a second prior to the ball arriving at the point of contact, it is ultimately unclear whether the throw would have retired Turner. As such, it can be said that the throw could have reasonably retired him...not that it would have for it might not have, but it could have, and in this situation, the rulebook gives the benefit of the doubt to the fielder because of the runner's violation of the lane rule.
The throw may not have been great, but that isn't the rule...we're not looking for a "true" throw...we're just looking for whether it could have reasonably retired the runner.
While Gurriel's left arm stretched for the tailing throw, his glove ran into Turner's hip before the ball arrived at the plane even with Gurriel's glove at the point of contact with Turner, which means we'll never know if Gurriel would have caught the ball...but he could have, and that's what breaks the tie.
Similar RLI Call: Here's an example. In July 2019, Chris Segal ejected Jeff Banister for arguing a correctly officiated runner's lane interference call against Rangers batter Carlos Tocci. It was a similar circumstance: the runner advanced the entire distance from home plate to first base in fair territory and not within the lane, the throw was sailing into foul territory, the fielder at first base stretching to receive it, and the ball hit the runner. "Time. That's interference."
Related Post: MLB Ejection 090 - Chris Segal (3; Jeff Banister) (7/8/18).
Possible Rules Absurdity: Had the exact same interaction between Turner and Gurriel occurred at first base, but instead, Turner had been running legally in the runner's lane the entire time, then Turner would not have been out for interference. In other words, the only difference between being safe and out here is not simply the interference that occurred that occurred at first base, but Turner failing to run in the lane AND also interfering with Gurriel at first base.
Finally, bear in mind that the fact that the runner may have beaten the ball to the base is irrelevant: we're looking for the fielder to catch the ball in front of the base, not waiting for the ball to get to the base itself. The image above illustrates the ball arriving at the point where the fielder's glove ended up while the batter's foot had not yet touched first base.
Whether the rule itself is fine or needs work is a legitimate debate, but this analysis pertains solely to Holbrook's enforcement of the rule and whether this was RLI. Blame the rule, not the umpire, for the umpire is tasked with calling the rule.
Verdict: This is runner's lane interference, Sam Holbrook's call was correct.
One more note: Crew Chief Gary Cederstrom and Holbrook put on the replay headsets to speak with Alan Porter and the MLBAM replay room in New York not for the purposes of reviewing the play (it's not reviewable), but in order to conduct a rules check to ensure the rule was properly enforced. Washington's attempted protest was rejected because a judgment call cannot be protested (the RLI rule clearly states "in the umpire's judgment" while OBR 7.04 states in part, "No protest shall ever be permitted on judgment decisions by the umpire").
Further Reading: For a more comprehensive overview of runner's lane interference and examples of similar plays, refer to the following play from the 2018 World Series in Los Angeles. For reference, both tmac and I had RLI on the 2018 Steve Pearce-Cody Bellinger play linked below and, to be consistent, it would follow that we have RLI here as well. Again, the key is that the runner was illegal the entire time to first base by virtue of failing to run within the runner's lane.
Related Post: Runner's Lane Interference - 2018 World Series Edition (10/28/18).
Video as follows:
Summary: We have a runner on first with none out. Turner hits a ground ball to Astros pitcher Brad Peacock, who throws toward first baseman Yuli Gurriel as Turner arrives at first base. Gurriel's glove collides with Turner's leg and the baseball winds up hitting Turner's thigh, resulting in HP Umpire Holbrook's call of interference. Martinez is furious and after the half-inning ends, he works himself into a tizzy and is ejected.
Related Post: MLB Ejection P1 - Sam Holbrook (3; Dave Martinez) (10/29/19).
![]() |
| An example of RLI during the 2019 season. |
Precedent: CloseCallSports.com is full of prior runner's lane interference plays. For instance, Bill Miller ejected Joe Maddon in August 2018 over a properly officiated interference call.
Related Post: MLB Ejection 116 - Bill Miller (1; Joe Maddon) (8/10/18).
The Rule: It always helps to start with the rule. So many people fail right out of the box because they never cite the rule, so here it is, Official Baseball Rule 5.09(a)(11): "A batter is out when—In running the last half of the distance from home base to first base, while the ball is being fielded to first base, he runs outside (to the right of) the three-foot line, or inside (to the left of) the foul line, and in the umpire’s judgment in so doing interferes with the fielder taking the throw at first base, in which case the ball is dead."
Sidebar: OBR 5.09(a)(11) Comment states, "The batter-runner is permitted to exit the three-foot lane by means of a step, stride, reach or slide in the immediate vicinity of first base for the sole purpose of touching first base." Be advised that a runner must be within the lane in order to exit it. It is physically impossible to exit something that one has never been in.
![]() |
| Turner would be safe had he run legally. |
Translation: This means that Turner could have avoided being called out for interference by doing just one thing: running within the lane at some point during his journey to first base. Replays conclusively indicate he failed to run within the lane at any point, which subjects him to an interference call if the second criterion of the rule is met: "interferes with the fielder taking the throw at first base."
![]() |
| In the mid-1880s, the lane prevented collisions. |
![]() |
| In 1887, first base moved, but the lane stayed. |
Yet the runner's lane remained in its foul territory location, and a rule was subsequently adopted to give the batter-runner permission to exit the lane in the vicinity of first base in order to touch the base, which was now entirely in fair territory—to cross over, so to speak.
![]() |
| 1B collisions in the present era are rare. |
Sidebar: Softball solves this problem by having two bases sitting next to each other: one for the fielder and one for the runner.
Interference Analysis: The intriguing part about Turner's interaction with Gurriel is that a minor collision, of sorts, actually did occur in that Gurriel's hand/wrist/glove made contact with Turner in fair territory.
![]() |
| This video analysis is extremely detailed. |
To review, here's the first professional rules interpretation from Wendelstedt (Evans agrees, as do all codes): "A runner that is running the entire distance outside of the running lane will not be protected if he interferes with a play at first base, even if it is in his last stride or step to the base. In order to be protected, this last step must be when he first exits the running lane" (recall that in order to exit, one must first be within).
For illustration's sake, here's Evans: "A runner who has advanced the entire distance from home plate to first in fair territory making no effort to run within the lane is not extended the same leniency as the runner who runs in the lane as required and then cuts into fair territory near the base to touch it."
The second concerns the throw: "The determination is not whether the throw is true, but whether it could still reasonably retire the runner."
![]() |
| This throw could have retired the runner. |
The throw may not have been great, but that isn't the rule...we're not looking for a "true" throw...we're just looking for whether it could have reasonably retired the runner.
![]() |
| In July, a similar play resulted in RLI. |
Similar RLI Call: Here's an example. In July 2019, Chris Segal ejected Jeff Banister for arguing a correctly officiated runner's lane interference call against Rangers batter Carlos Tocci. It was a similar circumstance: the runner advanced the entire distance from home plate to first base in fair territory and not within the lane, the throw was sailing into foul territory, the fielder at first base stretching to receive it, and the ball hit the runner. "Time. That's interference."
Related Post: MLB Ejection 090 - Chris Segal (3; Jeff Banister) (7/8/18).
![]() |
| We'll never know if it would have been caught. |
Finally, bear in mind that the fact that the runner may have beaten the ball to the base is irrelevant: we're looking for the fielder to catch the ball in front of the base, not waiting for the ball to get to the base itself. The image above illustrates the ball arriving at the point where the fielder's glove ended up while the batter's foot had not yet touched first base.
Whether the rule itself is fine or needs work is a legitimate debate, but this analysis pertains solely to Holbrook's enforcement of the rule and whether this was RLI. Blame the rule, not the umpire, for the umpire is tasked with calling the rule.
Verdict: This is runner's lane interference, Sam Holbrook's call was correct.
One more note: Crew Chief Gary Cederstrom and Holbrook put on the replay headsets to speak with Alan Porter and the MLBAM replay room in New York not for the purposes of reviewing the play (it's not reviewable), but in order to conduct a rules check to ensure the rule was properly enforced. Washington's attempted protest was rejected because a judgment call cannot be protested (the RLI rule clearly states "in the umpire's judgment" while OBR 7.04 states in part, "No protest shall ever be permitted on judgment decisions by the umpire").
Further Reading: For a more comprehensive overview of runner's lane interference and examples of similar plays, refer to the following play from the 2018 World Series in Los Angeles. For reference, both tmac and I had RLI on the 2018 Steve Pearce-Cody Bellinger play linked below and, to be consistent, it would follow that we have RLI here as well. Again, the key is that the runner was illegal the entire time to first base by virtue of failing to run within the runner's lane.
Related Post: Runner's Lane Interference - 2018 World Series Edition (10/28/18).
Video as follows:
Labels:
Articles
,
Gil's Call
,
Interference
,
Rule 5.09
,
Sam Holbrook
,
UEFL
,
UEFL University
,
Umpire Odds/Ends
,
Video Analysis
Tuesday, October 29, 2019
MLB Ejection P1 - Sam Holbrook (3; Dave Martinez)
HP Umpire Sam Holbrook ejected Nationals Manager Dave Martinez (runner's lane interference call; QOCY) in the top of the 7th inning of #Nationals-#Astros #WorldSeries Game 6. With none out and one on (R1), Nats batter Trea Turner hit a 0-0 fastball from Astros pitcher Brad Peacock on the ground to Peacock, who threw to first baseman Yuli Gurriel as Turner arrived, resulting in an interference call and extensive Replay Review as the result of an attempt to protest the game by the Nationals, officially classified as a rules check (RLI is not reviewable), which was disallowed as a result of baseball's longstanding prohibition on protesting judgment calls. Replays indicate Turner failed to run within the three-foot-wide runner's lane the entire distance from the 45-foot mark to first base, while Gurriel failed to catch Peacock's throw as a result of interference from Turner when Gurriel's hand and glove made contact with Turner prior to the ball's arrival at the contact plane, the call was correct.* At the time of the ejection, the Nationals were leading, 5-2. The Nationals ultimately won the contest, 7-2.
This is Sam Holbrook (34)'s third ejection of 2019.
Sam Holbrook now has 20 points in the UEFL Standings (15 Prev + 3 MLB-Post + 2 Correct Call = 20).
Crew Chief Gary Cederstrom now has 19 points in Crew Division (18 Previous + 1 QOCY = 19).
*Official Baseball Rule 5.09(a)(11) states, in part, that a batter is out when—"In running the last half of the distance from home base to first base, while the ball is being fielded to first base, he runs outside (to the right of) the three-foot line, or inside (to the left of) the foul line, and in the umpire’s judgment in so doing interferes with the fielder taking the throw at first base, in which case the ball is dead...The batter-runner is permitted to exit the three-foot lane by means of a step, stride, reach or slide in the immediate vicinity of first base for the sole purpose of touching first base."
^Official Baseball Rule 7.04 states, in part, "No protest shall ever be permitted on judgment decisions by the umpire."
There will be further analysis on this play in a subsequent article.
This is the 218th ejection report of 2019, first of the postseason.
This is the 99th Manager ejection of 2019.
This is the 1st World Series ejection since October 26, 1996 (Tim Welke/Bobby Cox [out call]).
This is Washington's 11th ejection of 2019, 1st in the NL East (WAS 11; PHI 10; ATL 8; MIA, NYM 5).
This is Dave Martinez's 5th ejection of 2019, 1st since Sept 8 (Mike Estabrook; QOC = Y [Balls/Strikes]).
This is Sam Holbrook's 3rd ejection of 2019, 1st since Sept 25 (Scott Servais; QOC = Y [Balls/Strikes]).
Wrap: Washington Nationals vs. Houston Astros (World Series Game 6), 10/29/19 | Video as follows:
This is Sam Holbrook (34)'s third ejection of 2019.
Sam Holbrook now has 20 points in the UEFL Standings (15 Prev + 3 MLB-Post + 2 Correct Call = 20).
Crew Chief Gary Cederstrom now has 19 points in Crew Division (18 Previous + 1 QOCY = 19).
*Official Baseball Rule 5.09(a)(11) states, in part, that a batter is out when—"In running the last half of the distance from home base to first base, while the ball is being fielded to first base, he runs outside (to the right of) the three-foot line, or inside (to the left of) the foul line, and in the umpire’s judgment in so doing interferes with the fielder taking the throw at first base, in which case the ball is dead...The batter-runner is permitted to exit the three-foot lane by means of a step, stride, reach or slide in the immediate vicinity of first base for the sole purpose of touching first base."
^Official Baseball Rule 7.04 states, in part, "No protest shall ever be permitted on judgment decisions by the umpire."
There will be further analysis on this play in a subsequent article.
This is the 218th ejection report of 2019, first of the postseason.
This is the 99th Manager ejection of 2019.
This is the 1st World Series ejection since October 26, 1996 (Tim Welke/Bobby Cox [out call]).
This is Washington's 11th ejection of 2019, 1st in the NL East (WAS 11; PHI 10; ATL 8; MIA, NYM 5).
This is Dave Martinez's 5th ejection of 2019, 1st since Sept 8 (Mike Estabrook; QOC = Y [Balls/Strikes]).
This is Sam Holbrook's 3rd ejection of 2019, 1st since Sept 25 (Scott Servais; QOC = Y [Balls/Strikes]).
Wrap: Washington Nationals vs. Houston Astros (World Series Game 6), 10/29/19 | Video as follows:
Labels:
Dave Martinez
,
Ejections
,
Interference
,
Protest
,
Rule 5.09
,
Rule 7.04
,
Sam Holbrook
,
UEFL
,
WAS
Barksdale and Washington's Pitch Skew Problem
Umpire Lance Barksdale's #WorldSeries Game 5 was one of the few games in which pitch skew hasn't favored the Nationals' opponent this postseason (was neutral), but if Washington wants to beat Houston in the pitch skew department, best bench catcher Kurt Suzuki, whose framing quality seems to have declined dramatically as October has worn on. With a hip flexor strain possibly sidelining the Nats' backstop, Yan Gomes could again draw in for Game 6, which makes it more likely for Washington to take its first pitch skew advantage of the postseason...and it's not because the umpires are biased for or against any particular team.
Definition: Pitch skew takes all veritably incorrect ball/strike calls by a home plate umpire and attributes the call to favoring one team or another (e.g., a pitch thrown outside the strike zone called a strike favors the defensive team, etc.). At the end of the game, all favors are added up and a game skew reflects which team benefited from more errors throughout the game. A series skew simply adds up all game skews. Skews of +0 and +1 should be deemed statistically neutral and equivalent, as when an odd number of callable pitch errors exist, skew cannot be 0 and must at minimum be 1. Under this framework, every game caught by Gomes this postseason has been a statistically neutral game.
Washington, on the verge of losing three straight games at home in a best-of-four World Series, seemed rather upset with HP Umpire Lance Barksdale's strike zone during Game 5. Barksdale did indeed miss a crucial strike three call to Nats batter Victor Robles and another ball call with Houston at-bat, but his overall game score was remarkably average and his skew was +0 (neutral rating): the definition of when baseball "evens out."
Barksdale at one point purportedly told Washington catcher Yan Gomes, "you were taking off on me" after Gomes started to run off the field on a two-strike pitch that Barksdale balled. The media ran with it to suggest Barksdale called it a ball because he felt shown up or what have you when Barksdale's comment was rather elementary.
An umpire is taught to see the ball from the pitcher's hand into the catcher's glove/mitt—in basketball, referees call it Start-Develop-Finish. If the catcher jumps up and blocks the umpire before the "finish" stage, the umpire's call is made more difficult—that's why pitches in the strike zone on stolen base attempts are balled at a higher rate...because the umpire couldn't see the ball into the catcher's glove/mitt.
That's what happened here, but the public at large has not one whit of umpiring technique, much less rules knowledge, so the story was spun to one of untoward motives...and this is why umpires don't do postgame press conferences or often speak in public: the spin room isn't umpire-friendly and silence can't be misquoted, especially not after the ongoing Rob Drake debacle.
Related Post: Rob Drake's Twitter War, Umpires and Social Media (10/24/19).
Despite Barksdale's statistically-confirmed neutrality, fans already frustrated with dropping all three games at home decried a "biased" Game 5 performance (see umpire scapegoating). For a sport with a fanbase and populace so enamored with the concept of computerized umpires and zones, it seems rather ironic yet entirely predictable that these same fans would so quickly shun the computer—which indicates the umpire called an entirely even-handed game—in favor of emotional arguments.
History Repeats Itself: This is extremely similar to what happened when Royals pitcher Mike Montgomery accused Manny Gonzalez of personal bias in a September game against Minnesota. Montgomery, ejected for arguing balls and strikes, called for automated strike zones while claiming that HP Umpire Gonzalez was personally biased against him and gave him "that look like, 'I'm going to screw you.'"
Naturally, we fact checked the entire game and the computer returned a skew of +1...in favor of Montgomery's Kansas City Royals.
Why is it that fans and players who are so passionate about pursuing an electronic strike zone seem to suffer a case of technological illiteracy when the computer statistics don't support claims of bias and unfairness?
Related Post: Montgomery Slams Ump Manny, Alleges Personal Bias (9/20/19).
DC's Pitch Skew Woes: I previously spoke of Washington's pitch skew struggles against the Los Angeles Dodgers in the Division Series such that Washington—which won the series—lost the pitch skew war in dramatic fashion to a team whose analytic-minded front office seems to take great pride in blowing out opponents on the pitch skew front, all while losing key postseason baseball games.
Related Post: Postseason Pitch Skew - Dodgers Catcher Change (10/11/19).
The Nationals have two catchers: Kurt Suzuki and Yan Gomes. Suzuki's average pitch skew rating this postseason has been -2.9, or a skew of +2.9 pitches in favor of his opponent. Gomes' average pitch skew rating this postseason has been -0.4, or a skew of +0.4 pitches in favor of his opponent.
For instance, after suffering a cumulative pitch skew of -13 through three games of the 2019 World Series with Suzuki catching, Nats Manager Dave Martinez started Gomes for Games 4 and 5, earning a +0 (Neutral) skew for both games.
The following is a table indicating skews for Washington this postseason.
As such, Washington's best bet for finally winning a pitch skew battle would be to start Gomes over Suzuki for the remainder of the World Series.
Video as follows:
Definition: Pitch skew takes all veritably incorrect ball/strike calls by a home plate umpire and attributes the call to favoring one team or another (e.g., a pitch thrown outside the strike zone called a strike favors the defensive team, etc.). At the end of the game, all favors are added up and a game skew reflects which team benefited from more errors throughout the game. A series skew simply adds up all game skews. Skews of +0 and +1 should be deemed statistically neutral and equivalent, as when an odd number of callable pitch errors exist, skew cannot be 0 and must at minimum be 1. Under this framework, every game caught by Gomes this postseason has been a statistically neutral game.
Washington, on the verge of losing three straight games at home in a best-of-four World Series, seemed rather upset with HP Umpire Lance Barksdale's strike zone during Game 5. Barksdale did indeed miss a crucial strike three call to Nats batter Victor Robles and another ball call with Houston at-bat, but his overall game score was remarkably average and his skew was +0 (neutral rating): the definition of when baseball "evens out."Barksdale at one point purportedly told Washington catcher Yan Gomes, "you were taking off on me" after Gomes started to run off the field on a two-strike pitch that Barksdale balled. The media ran with it to suggest Barksdale called it a ball because he felt shown up or what have you when Barksdale's comment was rather elementary.
An umpire is taught to see the ball from the pitcher's hand into the catcher's glove/mitt—in basketball, referees call it Start-Develop-Finish. If the catcher jumps up and blocks the umpire before the "finish" stage, the umpire's call is made more difficult—that's why pitches in the strike zone on stolen base attempts are balled at a higher rate...because the umpire couldn't see the ball into the catcher's glove/mitt.
That's what happened here, but the public at large has not one whit of umpiring technique, much less rules knowledge, so the story was spun to one of untoward motives...and this is why umpires don't do postgame press conferences or often speak in public: the spin room isn't umpire-friendly and silence can't be misquoted, especially not after the ongoing Rob Drake debacle.
Related Post: Rob Drake's Twitter War, Umpires and Social Media (10/24/19).
Despite Barksdale's statistically-confirmed neutrality, fans already frustrated with dropping all three games at home decried a "biased" Game 5 performance (see umpire scapegoating). For a sport with a fanbase and populace so enamored with the concept of computerized umpires and zones, it seems rather ironic yet entirely predictable that these same fans would so quickly shun the computer—which indicates the umpire called an entirely even-handed game—in favor of emotional arguments.
History Repeats Itself: This is extremely similar to what happened when Royals pitcher Mike Montgomery accused Manny Gonzalez of personal bias in a September game against Minnesota. Montgomery, ejected for arguing balls and strikes, called for automated strike zones while claiming that HP Umpire Gonzalez was personally biased against him and gave him "that look like, 'I'm going to screw you.'"
Naturally, we fact checked the entire game and the computer returned a skew of +1...in favor of Montgomery's Kansas City Royals.
Why is it that fans and players who are so passionate about pursuing an electronic strike zone seem to suffer a case of technological illiteracy when the computer statistics don't support claims of bias and unfairness?
Related Post: Montgomery Slams Ump Manny, Alleges Personal Bias (9/20/19).
DC's Pitch Skew Woes: I previously spoke of Washington's pitch skew struggles against the Los Angeles Dodgers in the Division Series such that Washington—which won the series—lost the pitch skew war in dramatic fashion to a team whose analytic-minded front office seems to take great pride in blowing out opponents on the pitch skew front, all while losing key postseason baseball games.
Related Post: Postseason Pitch Skew - Dodgers Catcher Change (10/11/19).
The Nationals have two catchers: Kurt Suzuki and Yan Gomes. Suzuki's average pitch skew rating this postseason has been -2.9, or a skew of +2.9 pitches in favor of his opponent. Gomes' average pitch skew rating this postseason has been -0.4, or a skew of +0.4 pitches in favor of his opponent.
For instance, after suffering a cumulative pitch skew of -13 through three games of the 2019 World Series with Suzuki catching, Nats Manager Dave Martinez started Gomes for Games 4 and 5, earning a +0 (Neutral) skew for both games.
The following is a table indicating skews for Washington this postseason.
| Game | Opponent | Skew | Catcher | Opp Catcher |
|---|---|---|---|---|
| WC | Brewers | +1 MIL | Suzuki | Grandal |
| NLDS 1 | Dodgers | +1 LA | Gomes | Smith |
| NLDS 2 | Dodgers | +0 Nu | Suzuki | Smith |
| NLDS 3 | Dodgers | +3 LA | Suzuki | Martin |
| NLDS 4 | Dodgers | +6 LA | Suzuki | Smith |
| NLDS 5 | Dodgers | +2 LA | Suzuki | Smith |
| NLCS 1 | Cardinals | +0 Nu | Gomes | Molina |
| NLCS 2 | Cardinals | +1 STL | Suzuki | Molina |
| NLCS 3 | Cardinals | +3 STL | Suzuki | Molina |
| NLCS 4 | Cardinals | +1 STL | Gomes | Molina |
| WS 1 | Astros | +3 HOU | Suzuki | Maldonado |
| WS 2 | Astros | +5 HOU | Suzuki | Chirinos |
| WS 3 | Astros | +5 HOU | Suzuki | Chirinos |
| WS 4 | Astros | +0 Nu | Gomes | Chirinos |
| WS 5 | Astros | +0 Nu | Gomes | Maldonado |
Video as follows:
Labels:
Articles
,
Gil's Call
,
Lance Barksdale
,
UEFL
,
Umpire Odds/Ends
Monday, October 28, 2019
Fixing the Strike Zone - Pitch Challenge Proposal
Today we unveil a responsible proposal for fixing the strike zone through technology: not full robot-umpire pitch calling, but a challenge system instead. Tech is coming to baseball and MLB has the opportunity to fix obvious errors while preserving umpire autonomy regarding most aspects of officiating behind home plate. You might think this rather out of left field for us, but we did call ourselves The Left Field Corner all those years ago for a reason.
As we've known for several years, baseball's attempts at incorporating technology for balls and strikes has proven rather frustrating for fans and umpires alike: mostly because teams and fans tend to zero-in on perceived missed ball/strike calls shown on television broadcasts and internet graphics while umpires lament that fans are exposed to a flawed computer system that is subject to a multitude of errors.
Publicly available pitch data exposes teams and fans to statistics suggesting umpires are 91% accurate behind home plate while MLB's evaluations show an average 97% Zone Evaluation score...that creates a disconnect of problems.
Related Post: Podcast - Truth About Baseball's Electronic Strike Zone (6/5/19).
Related Post: Call for Umpire Accountability & the 97% Plate Score (4/19/19).
On the one extreme are fans demanding fully automated pitch calling, similar to the Automated Ball/Strike System (ABS) attempted in the Atlantic and Arizona Fall Leagues (which resulted in several coach and player ejections for arguing the computer's ball/strike calls...there were additional ejections to those we've highlighted, but unfortunately, they did not feature video).
Related Post: Computer Strike Call Prompts Navas' AFL Ejection (10/16/19).
Related Post: Atlantic League ABS Robo-Ump Ejection Encore (9/28/19).
Related Post: History - Baseball's First Ejection Due to TrackMan (7/12/19).
On the other are traditionalists seeking to preserve the human element, and somewhere in the middle is Close Call Sports, which acknowledges that technology can assist in the ball/strike call mission, while also acknowledging that the very system baseball presently uses on MLB Gameday, Baseball Savant, Brooks Baseball, PitchCast / Fox Trax / ESPN K-Zone is prone to error.
Umpiring can be an art, while ball/strike analysis is generally a science. Through our proposal, we'll try and strike a balance: preserve the art while incorporating some of the science.
Both sides have to face some facts: For fans, no, a fully-automated system may not be realistic at this time. For umpires, the tech might have reached a breaking point similar to Replay Review before its 2014 expansion. The NBA just adopted a challenge system for some foul calls, the NHL expanded its existing challenge system, and the NFL red flag is famous. Maybe not now, maybe not next year or two, but soon.
MLB Chief Baseball Officer Joe Torre said in 2019, "I don't see the robotic strike zone happening," while MLB Commissioner Rob Manfred stated his motive: "I think an automated strike zone puts you in a position to manage that strike zone. Where should it be exactly to produce the amount of offense that you want?" Theoretically, a computer could be tweaked to only calls strikes between the thighs and belt, for instance, if Manfred wanted to "manage" the zone that way...assuming, of course, a most accurate computer.
Related Post: Citing Atlantic Lg, Manfred Ready for Robo-Zone (8/19/19).
Related Post: Torre Doesn't Want Robot Umpires in MLB (7/26/19).
Proposal: To mediate the discussion, it would follow that a compromise might be at hand: to the robo-ump crowd, there are some elements of the game that computers are unable—proven time and time again—to adjudicate, while to the traditionalist faction, technology exists to help guide us to the concept of correcting "the obvious miss."
As such, we propose a challenge system, which we further break down into one of two options depending on how optimistic you feel about TrackMan (Hawk-eye, going forward)'s ability to adjudicate pitches.
For instance, the Automated Ball/Strike System (ABS) was subject to the following errors:
> Standardization and Radial Error;
> Calibration Error;
> Vertical Strike Zone Error;
> 2D vs 3D Zone Measurement Error;
> Final Approach Error (e.g., pfx is measured at 40 feet [NOT 60 feet]);
> Tracking, Capture, and Margin of Error (1-2 inches per statistics);
> Computer failing to see pitches (fails to register that a pitch was thrown).
Trajectory Measured by Automated Caller (TMAC): The TMAC system is as black-and-white as you can get and assumes the computerized pitch tracker is 100% accurate at all times and never makes any mistakes. Margin of error is zero, for under TMAC, "error" does not exist. Another way to think of the TMAC system is a computer that after a brief delay calls the pitch on its own, similar to Hawk-Eye in tennis. NOTE: For TMAC to be incorporated at the present time means that baseball would BE REQUIRED to accept inaccuracy, which might be somewhat ironic since the whole idea stems from a fandom unhappy about perceived umpire inaccuracy.
Here are the basics:
> Each team receives 3 challenges per game. Like Replay, a won challenge is retained.
> > The system will declare each challenged pitch to be a Ball or Strike.
> Offense: Only a batter may challenge a call of "strike."
> Defense: Only the catcher or pitcher may challenge a call of "ball."
> For pace-of-play purposes, a challenge must be immediate upon the umpire's call.
> One additional challenge per team for each three extra innings (e.g., +1 in 10th, +1 in 13th, etc.).
> If Hawk-Eye malfunctions or fails to capture the pitch, no challenge is charged (call stands).
> There is no other method for Borderline/Call Stands because the system assumes that the computer is 100% accurate on all pitches that it sees (aka Zero-Error).
> The Atlantic League's ABS experiment turned up quite a number of malfunctions in that the system sometimes failed to capture as many as 50% (possibly even more) of pitches thrown during a given inning. On several occasions, ABS had to be shut off for the night due to poor performance.
Related Post: ABS Playoff Highlights - Delayed Calls & System Errors (10/1/19).
Related Post: ALPB - Inconsistent TrackMan Use Riles Coaches (7/22/19).
Graphic Inaccuracy Logic (GIL): The GIL system acknowledges that the computer sometimes makes mistakes on close calls, are occasionally subject to errors, and affords the benefit-of-the-doubt to the umpire. Another way to think of the GIL system is one that operates under the framework of Replay Review in that all calls are Confirmed/Stands/Overturned, with Stands going to the original on-field ruling.
The basic structure of GIL is similar to TMAC, except that "Call Stands" is a realistic outcome if the pitch falls within the UEFL f/x's one-inch margin of error (could be expanded to ML Private/Zone Eval Equivalent's two-inch margin of error, depending on administrative preference). Like Replay Review, a challenge is considered lost if the call stands.
For instance, the GIL system would attempt to account for an error such as vertical zone error—see our work on postgame processing for example—while for the TMAC system to work effectively, no such error can exist.
Related Post: Postgame Processing Changes Gibson's Strike EJ QOC (9/21/19).
Conclusion: That's our proposal to incorporate technology into the game while acknowledging its shortcomings and accounting for those close calls that the computer cannot decipher. The goal with the challenge proposal is to correct the "obvious miss," similar to what Tony La Russa once said was the original purpose of expanded Replay Review.
The idea with the GIL system is to avoid the level of pedanticism that plagues those out/safe reviews that overturn a safe call to an out call based on slow-motion replay that shows the runner—who clearly beat the throw—broke contact with the base for one-tenth of a second. I wrote about this level of technicality in 2018 (see related post)...but if you don't mind that, and assume the computer is always right, then choose the TMAC system.
Related Post: Replay Rewind - Technically Correct or Spiritual Travesty? (6/9/18).
In either event, the goal should be to correct the "that strike was three inches outside" call. If the umpire's was truly an incorrect call by such an amount, as alleged, we'd like to help fix that.
Proposal video as follows:
As we've known for several years, baseball's attempts at incorporating technology for balls and strikes has proven rather frustrating for fans and umpires alike: mostly because teams and fans tend to zero-in on perceived missed ball/strike calls shown on television broadcasts and internet graphics while umpires lament that fans are exposed to a flawed computer system that is subject to a multitude of errors.
Publicly available pitch data exposes teams and fans to statistics suggesting umpires are 91% accurate behind home plate while MLB's evaluations show an average 97% Zone Evaluation score...that creates a disconnect of problems.
Related Post: Podcast - Truth About Baseball's Electronic Strike Zone (6/5/19).
Related Post: Call for Umpire Accountability & the 97% Plate Score (4/19/19).
On the one extreme are fans demanding fully automated pitch calling, similar to the Automated Ball/Strike System (ABS) attempted in the Atlantic and Arizona Fall Leagues (which resulted in several coach and player ejections for arguing the computer's ball/strike calls...there were additional ejections to those we've highlighted, but unfortunately, they did not feature video).
Related Post: Computer Strike Call Prompts Navas' AFL Ejection (10/16/19).
Related Post: Atlantic League ABS Robo-Ump Ejection Encore (9/28/19).
Related Post: History - Baseball's First Ejection Due to TrackMan (7/12/19).
![]() |
| Robots? Torre said no, but Manfred said yes. |
Umpiring can be an art, while ball/strike analysis is generally a science. Through our proposal, we'll try and strike a balance: preserve the art while incorporating some of the science.
Both sides have to face some facts: For fans, no, a fully-automated system may not be realistic at this time. For umpires, the tech might have reached a breaking point similar to Replay Review before its 2014 expansion. The NBA just adopted a challenge system for some foul calls, the NHL expanded its existing challenge system, and the NFL red flag is famous. Maybe not now, maybe not next year or two, but soon.
MLB Chief Baseball Officer Joe Torre said in 2019, "I don't see the robotic strike zone happening," while MLB Commissioner Rob Manfred stated his motive: "I think an automated strike zone puts you in a position to manage that strike zone. Where should it be exactly to produce the amount of offense that you want?" Theoretically, a computer could be tweaked to only calls strikes between the thighs and belt, for instance, if Manfred wanted to "manage" the zone that way...assuming, of course, a most accurate computer.
Related Post: Citing Atlantic Lg, Manfred Ready for Robo-Zone (8/19/19).
Related Post: Torre Doesn't Want Robot Umpires in MLB (7/26/19).
![]() |
| Vertical zone error remains an unanswered ? |
As such, we propose a challenge system, which we further break down into one of two options depending on how optimistic you feel about TrackMan (Hawk-eye, going forward)'s ability to adjudicate pitches.
For instance, the Automated Ball/Strike System (ABS) was subject to the following errors:
> Standardization and Radial Error;
> Calibration Error;
> Vertical Strike Zone Error;
> 2D vs 3D Zone Measurement Error;
> Final Approach Error (e.g., pfx is measured at 40 feet [NOT 60 feet]);
> Tracking, Capture, and Margin of Error (1-2 inches per statistics);
> Computer failing to see pitches (fails to register that a pitch was thrown).
![]() |
| Delayed pitch calls remain an issue. |
Here are the basics:
> Each team receives 3 challenges per game. Like Replay, a won challenge is retained.
> > The system will declare each challenged pitch to be a Ball or Strike.
> Offense: Only a batter may challenge a call of "strike."
> Defense: Only the catcher or pitcher may challenge a call of "ball."
> For pace-of-play purposes, a challenge must be immediate upon the umpire's call.
> One additional challenge per team for each three extra innings (e.g., +1 in 10th, +1 in 13th, etc.).
> If Hawk-Eye malfunctions or fails to capture the pitch, no challenge is charged (call stands).
> There is no other method for Borderline/Call Stands because the system assumes that the computer is 100% accurate on all pitches that it sees (aka Zero-Error).
> The Atlantic League's ABS experiment turned up quite a number of malfunctions in that the system sometimes failed to capture as many as 50% (possibly even more) of pitches thrown during a given inning. On several occasions, ABS had to be shut off for the night due to poor performance.
Related Post: ABS Playoff Highlights - Delayed Calls & System Errors (10/1/19).
Related Post: ALPB - Inconsistent TrackMan Use Riles Coaches (7/22/19).
![]() |
| Robo-Umps: Bringing rivals together since '19. |
The basic structure of GIL is similar to TMAC, except that "Call Stands" is a realistic outcome if the pitch falls within the UEFL f/x's one-inch margin of error (could be expanded to ML Private/Zone Eval Equivalent's two-inch margin of error, depending on administrative preference). Like Replay Review, a challenge is considered lost if the call stands.
For instance, the GIL system would attempt to account for an error such as vertical zone error—see our work on postgame processing for example—while for the TMAC system to work effectively, no such error can exist.
Related Post: Postgame Processing Changes Gibson's Strike EJ QOC (9/21/19).
![]() |
| The question is whether to nitpick or not. |
The idea with the GIL system is to avoid the level of pedanticism that plagues those out/safe reviews that overturn a safe call to an out call based on slow-motion replay that shows the runner—who clearly beat the throw—broke contact with the base for one-tenth of a second. I wrote about this level of technicality in 2018 (see related post)...but if you don't mind that, and assume the computer is always right, then choose the TMAC system.
Related Post: Replay Rewind - Technically Correct or Spiritual Travesty? (6/9/18).
In either event, the goal should be to correct the "that strike was three inches outside" call. If the umpire's was truly an incorrect call by such an amount, as alleged, we'd like to help fix that.
Proposal video as follows:
Labels:
Articles
,
Computer Strike Zone
,
Gil's Call
,
tmac
,
UEFL
,
Umpire Odds/Ends
,
Video Analysis
Saturday, October 26, 2019
Umpire Julius E "Chuck" Meriwether Dies at 63
Julius Edward Meriwether, who went by "Chuck," was born in June 1956 in Nashville, TN, attended the Wendelstedt Umpire School (then-newly acquired from Al Somers by Harry Wendelstedt) in 1979 upon reading an advertisement in the newspaper, and never looked back after his first game in Minor League Baseball in 1979.Chuck made his way to the Pacific Coast League and American Association before his first American League game in 1987 and hiring to the AL staff shortly thereafter. 2,594 regular season games and 28 ejections later, Meriwether left the field after the 2009 season due in part to wear-and-tear on his knees, and soon became an umpire supervisor.
In 2016, his hometown Nashville Sounds renamed the First Tennessee Park umpire room the "Chuck Meriwether Umpire Room" and in 2017, the Tennessee Sports Hall of Fame inducted Chuck as its newest member.
Related Post: Umpire Chuck Meriwether Inducted into TN Hall of Fame (6/30/17).
Chuck and Coop worked on the same crew under chief Mike Reilly in 2004 and 2009.
Video as follows:
Labels:
Articles
,
Chuck Meriwether
,
Injury
,
News
,
UEFL
,
Umpire Odds/Ends
Thursday, October 24, 2019
Rob Drake's Twitter War, Umpires and Social Media
With MLB umpire Rob Drake under fire for a since-deleted political tweet referencing an AR-15 firearm and "cival war," we analyzed the freedom of speech concept, umpires in public and online, and disciplinary appropriateness for what happens when an umpire goes beyond the pale of protected speech in a public forum hosted on a private platform, as social media on the internet is.
Disclaimer: Close Call Sports has had a longstanding policy of no politics on the website. This story is so significant that it all but requires an article, but we will attempt to do so while not delving into the political discussion other than to report the facts of what occurred.
The Story: According to ESPN, Drake on Tuesday tweeted "I will be buying an AR-15 tomorrow, because if you impeach MY PRESIDENT this way, YOU WILL HAVE ANOTHER CIVAL WAR!!! #MAGA2020." The tweet, published to Drake's @thedrake30 Twitter account, was subsequently deleted and the account deactivated, but the damage was done as the tweet's content was spread throughout the news world, resulting in a pending MLB investigation.
Freedom of Speech: As an American citizen, Drake—just like anyone else—is entitled to the protections of the USA's first amendment regarding freedom of expression, but what exactly is free speech?
The First Amendment to the United States Constitution states, "Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances."
What That Means: In short, the US government cannot arrest a person for exercising his or her first amendment right...to an extent. For example, speech is limited if it presents a "clear and present danger" (e.g., a terroristic threat) and it is also limited on private property. If Twitter, for instance, wanted to remove Drake's tweet (as opposed to Drake deleting it himself), it would have the legal right to do so, as Twitter is a private platform (thus, it would be a legal form of censorship, but not a violation of the US constitution regarding free speech).
Freedom of Speech Doesn't Apply to Private Entities: The accompanying image of a sign outside Gelson's Market asserts the private property owner (the supermarket)'s right to censor speech while acknowledging the public/government (local police)'s default declination to take action against it.
Although a person's speech is protected by constitutional law, a non-public company can set its own rules (as long as they aren't discriminatory pursuant to federal, state, or local law)...so while the speech may be "unauthorized activity" from Gelson's Market's point of view, it is not the same from the police's perspective (trespassing is another matter entirely).
Court of Public Opinion: The mythical court of public opinion cares not one whit about rules, laws, nor facts—i.e., the electronic strike zone issue. Keep this in mind, because I will refer back to this "court" throughout the article's latter half.
For example, the court of public opinion might ask if Drake's prior body of work was in any way influenced by the perceived ideas exposed through the content of his tweet, for instance, did he call a pitch one way or another because of X or Y, related to his twitter presence and unrelated to his professional umpiring training.
Sidebar: In the Angel Hernandez lawsuit, MLB referenced its federal anti-trust exemption, which goes back nearly 100 years, and which technically could mean that MLB is bound by some degree of public oversight and/or responsibility. For instance, the Mitchell Report for MLB Commissioner Bud Selig in 2007 was conducted by the US Congress and Maine Senator George J. Mitchell, a public body and a publicly elected official.
Although an employee is protected from retaliation (e.g., adverse treatment, demotion/firing, etc.) by an employer for political speech/beliefs in certain jurisdictions, such as California (A's, Angels, Dodgers, Giants, Padres) or the federal protection from discrimination based on political affiliation—Drake's tweet goes beyond any potentially protected political speech by referencing (1) an AR-15 firearm [which on its own may be protected by the second amendment, if not for...], and (2) civil ("cival") war [...invoking war].
Gun & War: Those two parts of the tweet, in concert, are what have Drake in hot water. We researched the issue, and Drake's longstanding Twitter account has featured political content for a considerable length of time—most nearly all of which were his right to express. But what set this tweet apart were his invocation of a direct action relative to a firearm ("I will be buying an AR-15 tomorrow") and an allusion to its use ("YOU WILL HAVE ANOTHER CIVAL [sic] WAR").
If he doesn't put those two elements in his tweet, there isn't much actionable content for anyone to react to (other than, again, his politics, which, agree or disagree, we are not discussing, and which is anyone's right to have). The question is whether a reasonable person might construe such a sentence as violent or invocative of violence.
Referring back to the limits of free speech relative to the potentially criminal threat issue, these limits can also vary by jurisdiction/state, and in some places, rather depends on how a reasonable person interprets the speech regardless of whether the person who said the speech intended it to be threatening or not.
Which means that Drake's tweet about guns and war may or may not be a threat—again, largely in reference to the court of public opinion. The question of whether "threat" is appropriate here depends not on Drake, but on the person interpreting his statement.
Considering that the answer is largely politically-inclined (for instance, a court-of-opinion jury of 12 reasonable people might split on the issue—quite dramatically too, as in a "how could you POSSIBLY think it was a threat?" versus "how could you POSSIBLY think it was NOT a threat?" debate), we will leave that question open-ended...and ultimately, I don't personally believe we're looking at a crime per se...unless one were to consider it a social media/public opinion crime, in which case we're back to the political divide that CCS isn't touching.
Umpires at ALL Levels are Public: My educated guess is that someone in the media had been following Drake's twitter account (and perhaps those of other MLB umpires) for months. Journalism what it is, I would think Drake's political tweets were known, but again, as long as they were only about politics, they were rather benign—not once did Drake appear to comment on MLB game events, and, after all, even Joe West made a political statement in an interview, but it was woven into a story, and, again, rather benign.
As soon as Drake—operating with a fully public Twitter account—tweeted something beyond the pale of simple politics, it was go time.
Bias: What really hurts Drake comes down to the same thing that doomed Toby Basner in 2016 (when a family member's Facebook post applauded Basner's May 21, 2016 ejection of Blue Jays player Josh Donaldson) and netted Joe West a three-game suspension in 2017 (when he described Adrian Beltre as baseball's biggest complainer): an appearance of lack of impartiality as an umpire.
Impartiality is Officiating's Lifeblood: Again, we're not talking politics, so I'll just leave it as society's expectation that an umpire must be impartial in all aspects of life in order to be impartial on the field, and an indication to the contrary thus calls into question, in the court of public opinion, the umpire's neutrality on the field...Drake's tweet hit on hot-button issues in the popular culture as well as sports officiating specifically.
To repeat: yes, any official is absolutely entitled to political opinions by nature of being a citizen and a human being...but the court of public opinion judges officials far more harshly than others due to an expectation of neutrality.
I refer to August 2019, when Phil Cuzzi had a terrific response when he was asked in Chicago which MLB player talks the most trash to umpires—he laughed, patted a reporter on the shoulder, and walked away without answering the question...because he knew that saying any name in public would instantly lead to a news story that he lacked impartiality and was biased against a certain player, or certain team, such that any future close call against that team or in favor of a divisional foe (or game opponent) would be called into question even more so than they would be otherwise.
Related Post: Playing in Public - Cuzzi Keeps Cool (8/12/19).
It's the same reason Joe West is suing Paul Lo Duca over Lo Duca's public claim that West purportedly accepted a bribe in exchange for favorable calls: one of an umpire's most valuable attributes is the perception of impartiality or fairness, and this reputation for ethics is fairly vital to a successful officiating career.
Related Post: Joe West Sues Paul LoDuca Over Bribery Claim (10/22/19).
And that's what hurts Drake so much here from an officiating standpoint—politics aside, the fact that Drake has such a strong opinion may call into question, in the court of public opinion, his ability to be a neutral arbiter.
From a humanistic standpoint, tweeting about gun violence in a cavalier manner is harmful in today's environment. In 2015, the Houston Rockets fired social media manager Chad Shanks for tweeting an emoji of a gun on the brand's account. In 2018, Disney removed James Gunn from directing Guardians of the Galaxy after a series of offensive tweets. In June, Compass Elementary School placed principal Dr. Chad Searcey on administrative leave—he later entered into a separation agreement with the school—after he tweeted photographs of guns in opposition to a gun control conversation.
It's not just guns. The Des Moines Register fired reporter Aaron Calvin over past racially-charged tweets, and the Fort Worth Independent School District fired teacher Georgia Clark for her tweets referencing "illegal students."
The Point? Silence Cannot Be Misquoted: When it comes to an official's online presence—from MLB crew chiefs to Little League umpires, NFL referees to Pop Warner officials—less is often more. It's absolutely fine to share innocuous well wishes and positive messages—as we've seen with tributes to the late Eric Cooper and various charitable endeavors with UmpsCare and beyond—but it's wholly another matter to enter into the fray of controversial hot-button issues of the day.
Case Study, NHL: The National Hockey League made headlines when it suspended referee Tim Peel in 2015 for meeting with hockey reporter Greg Wyshynski in a bar, and taking a picture with him. As Wyshynski wrote, "Peel's a good guy who genuinely wanted for me to learn about where he's coming from and vice versa; and in turn, to enlighten the critics of NHL referees about why they do what they do."
As Wyshynski phrased it, "it references the myopic micro-managing of officials that leaves so many fans and media frustrated." Yet...Wyshynski and other reporters help contribute to the problem by criticizing officials for the most minor of actions, which perpetuates the suffocating cycle in the first place.
For instance, Peel joined Twitter on July 21, 2014 and tweeted out a welcome message at 1:55pm. By 7:45am on July 22, he tweeted, "Sorry hockey fans..gotta shut it down#Passionate hockey fans!" 16 hours and that was that.
Is it fair? Probably not, but that's the scrutiny officials are under. In 2011, NHL's newly-created social media policy restricted referees and linesmen from using social media to make certain statements about games—especially when controversy or critique was involved.
The NHL-NHLOA agreement subsequently added a line prohibiting NHL officials from using social media outlets such as Twitter and Facebook entirely. In 2019, the Russian KHL followed suit and banned its officials from social media altogether.
Meanwhile, NBA referees use social media to such a great extent that the official NBA referee twitter account has been known to live tweet games and regularly interact with fans. So at least it's consistently inconsistent.
MLB: At present, umpires are free to have social media accounts, though, as the Drake saga demonstrates, an umpire is an umpire at all times. Will this Drake controversy cause MLB to pursue an NHL-esque ban on umpires using social media during 2019's CBA negotiations or will the league and its umpires seek to develop a less prohibitive yet responsible social media policy? At the very least, it might give an insight to how the secretive CBA addresses social media use...or lack thereof.
For reference, here is the NFHS' social media guidance for sports officials.
Video as follows:
Disclaimer: Close Call Sports has had a longstanding policy of no politics on the website. This story is so significant that it all but requires an article, but we will attempt to do so while not delving into the political discussion other than to report the facts of what occurred.
The Story: According to ESPN, Drake on Tuesday tweeted "I will be buying an AR-15 tomorrow, because if you impeach MY PRESIDENT this way, YOU WILL HAVE ANOTHER CIVAL WAR!!! #MAGA2020." The tweet, published to Drake's @thedrake30 Twitter account, was subsequently deleted and the account deactivated, but the damage was done as the tweet's content was spread throughout the news world, resulting in a pending MLB investigation.
Freedom of Speech: As an American citizen, Drake—just like anyone else—is entitled to the protections of the USA's first amendment regarding freedom of expression, but what exactly is free speech?
![]() |
| Free Speech is a right with certain allowances & limitations. |
What That Means: In short, the US government cannot arrest a person for exercising his or her first amendment right...to an extent. For example, speech is limited if it presents a "clear and present danger" (e.g., a terroristic threat) and it is also limited on private property. If Twitter, for instance, wanted to remove Drake's tweet (as opposed to Drake deleting it himself), it would have the legal right to do so, as Twitter is a private platform (thus, it would be a legal form of censorship, but not a violation of the US constitution regarding free speech).
![]() |
| Free speech can get somewhat complicated. |
Freedom of Speech Doesn't Apply to Private Entities: The accompanying image of a sign outside Gelson's Market asserts the private property owner (the supermarket)'s right to censor speech while acknowledging the public/government (local police)'s default declination to take action against it.
Although a person's speech is protected by constitutional law, a non-public company can set its own rules (as long as they aren't discriminatory pursuant to federal, state, or local law)...so while the speech may be "unauthorized activity" from Gelson's Market's point of view, it is not the same from the police's perspective (trespassing is another matter entirely).
Court of Public Opinion: The mythical court of public opinion cares not one whit about rules, laws, nor facts—i.e., the electronic strike zone issue. Keep this in mind, because I will refer back to this "court" throughout the article's latter half.
![]() |
| Drake walks away from Justin Turner in SD. |
Sidebar: In the Angel Hernandez lawsuit, MLB referenced its federal anti-trust exemption, which goes back nearly 100 years, and which technically could mean that MLB is bound by some degree of public oversight and/or responsibility. For instance, the Mitchell Report for MLB Commissioner Bud Selig in 2007 was conducted by the US Congress and Maine Senator George J. Mitchell, a public body and a publicly elected official.
![]() |
| What does this say about non-USA players? |
Gun & War: Those two parts of the tweet, in concert, are what have Drake in hot water. We researched the issue, and Drake's longstanding Twitter account has featured political content for a considerable length of time—most nearly all of which were his right to express. But what set this tweet apart were his invocation of a direct action relative to a firearm ("I will be buying an AR-15 tomorrow") and an allusion to its use ("YOU WILL HAVE ANOTHER CIVAL [sic] WAR").
![]() |
| Mentioning a gun & war sealed the deal. |
Referring back to the limits of free speech relative to the potentially criminal threat issue, these limits can also vary by jurisdiction/state, and in some places, rather depends on how a reasonable person interprets the speech regardless of whether the person who said the speech intended it to be threatening or not.
Which means that Drake's tweet about guns and war may or may not be a threat—again, largely in reference to the court of public opinion. The question of whether "threat" is appropriate here depends not on Drake, but on the person interpreting his statement.
Considering that the answer is largely politically-inclined (for instance, a court-of-opinion jury of 12 reasonable people might split on the issue—quite dramatically too, as in a "how could you POSSIBLY think it was a threat?" versus "how could you POSSIBLY think it was NOT a threat?" debate), we will leave that question open-ended...and ultimately, I don't personally believe we're looking at a crime per se...unless one were to consider it a social media/public opinion crime, in which case we're back to the political divide that CCS isn't touching.
Umpires at ALL Levels are Public: My educated guess is that someone in the media had been following Drake's twitter account (and perhaps those of other MLB umpires) for months. Journalism what it is, I would think Drake's political tweets were known, but again, as long as they were only about politics, they were rather benign—not once did Drake appear to comment on MLB game events, and, after all, even Joe West made a political statement in an interview, but it was woven into a story, and, again, rather benign.
![]() |
| How'd they get in? Drake's account was public. |
Bias: What really hurts Drake comes down to the same thing that doomed Toby Basner in 2016 (when a family member's Facebook post applauded Basner's May 21, 2016 ejection of Blue Jays player Josh Donaldson) and netted Joe West a three-game suspension in 2017 (when he described Adrian Beltre as baseball's biggest complainer): an appearance of lack of impartiality as an umpire.
![]() |
| Cuzzi kept it light in August by demurring. |
To repeat: yes, any official is absolutely entitled to political opinions by nature of being a citizen and a human being...but the court of public opinion judges officials far more harshly than others due to an expectation of neutrality.
I refer to August 2019, when Phil Cuzzi had a terrific response when he was asked in Chicago which MLB player talks the most trash to umpires—he laughed, patted a reporter on the shoulder, and walked away without answering the question...because he knew that saying any name in public would instantly lead to a news story that he lacked impartiality and was biased against a certain player, or certain team, such that any future close call against that team or in favor of a divisional foe (or game opponent) would be called into question even more so than they would be otherwise.
Related Post: Playing in Public - Cuzzi Keeps Cool (8/12/19).
It's the same reason Joe West is suing Paul Lo Duca over Lo Duca's public claim that West purportedly accepted a bribe in exchange for favorable calls: one of an umpire's most valuable attributes is the perception of impartiality or fairness, and this reputation for ethics is fairly vital to a successful officiating career.
Related Post: Joe West Sues Paul LoDuca Over Bribery Claim (10/22/19).
![]() |
| We are very comfortable with this fact check. |
From a humanistic standpoint, tweeting about gun violence in a cavalier manner is harmful in today's environment. In 2015, the Houston Rockets fired social media manager Chad Shanks for tweeting an emoji of a gun on the brand's account. In 2018, Disney removed James Gunn from directing Guardians of the Galaxy after a series of offensive tweets. In June, Compass Elementary School placed principal Dr. Chad Searcey on administrative leave—he later entered into a separation agreement with the school—after he tweeted photographs of guns in opposition to a gun control conversation.
![]() |
| Social media hate & harm leads to job loss. |
The Point? Silence Cannot Be Misquoted: When it comes to an official's online presence—from MLB crew chiefs to Little League umpires, NFL referees to Pop Warner officials—less is often more. It's absolutely fine to share innocuous well wishes and positive messages—as we've seen with tributes to the late Eric Cooper and various charitable endeavors with UmpsCare and beyond—but it's wholly another matter to enter into the fray of controversial hot-button issues of the day.
Case Study, NHL: The National Hockey League made headlines when it suspended referee Tim Peel in 2015 for meeting with hockey reporter Greg Wyshynski in a bar, and taking a picture with him. As Wyshynski wrote, "Peel's a good guy who genuinely wanted for me to learn about where he's coming from and vice versa; and in turn, to enlighten the critics of NHL referees about why they do what they do."
![]() |
| This photo landed Peel in hot water. |
For instance, Peel joined Twitter on July 21, 2014 and tweeted out a welcome message at 1:55pm. By 7:45am on July 22, he tweeted, "Sorry hockey fans..gotta shut it down#Passionate hockey fans!" 16 hours and that was that.
Is it fair? Probably not, but that's the scrutiny officials are under. In 2011, NHL's newly-created social media policy restricted referees and linesmen from using social media to make certain statements about games—especially when controversy or critique was involved.
![]() |
| Tim Peel lasted less than a day on Twitter. |
Meanwhile, NBA referees use social media to such a great extent that the official NBA referee twitter account has been known to live tweet games and regularly interact with fans. So at least it's consistently inconsistent.
MLB: At present, umpires are free to have social media accounts, though, as the Drake saga demonstrates, an umpire is an umpire at all times. Will this Drake controversy cause MLB to pursue an NHL-esque ban on umpires using social media during 2019's CBA negotiations or will the league and its umpires seek to develop a less prohibitive yet responsible social media policy? At the very least, it might give an insight to how the secretive CBA addresses social media use...or lack thereof.
For reference, here is the NFHS' social media guidance for sports officials.
Video as follows:
Labels:
Articles
,
Gil's Call
,
News
,
Rob Drake
,
UEFL
,
Umpire Odds/Ends
Podcast - Mike Reilly Recalls Crew Mate Eric Cooper
We continue the celebration of MLB umpire Eric Cooper's life in a Plate Meeting Podcast episode with one of the umpires who perhaps knew him best: his long-time crew chief, Mike Reilly.
Mike was there for Cooper's first career MLB game in 1996, and Eric was there for Reilly's final career MLB game in 2010.
The two Iowa-born umpires shared a bond that kept them on the same crew for the better part of the 2000s—maybe it was their shared fandom for Notre Dame or simply being from the same region. Mike talks about the good times with Coop on the show.
This episode is available in both audio and video form. Click the following link to access the audio of "Episode 20 - Mike Reilly Remembers Longtime Crew Mate Eric Cooper" or watch the video via "Read More."
Mike was there for Cooper's first career MLB game in 1996, and Eric was there for Reilly's final career MLB game in 2010.
The two Iowa-born umpires shared a bond that kept them on the same crew for the better part of the 2000s—maybe it was their shared fandom for Notre Dame or simply being from the same region. Mike talks about the good times with Coop on the show.
This episode is available in both audio and video form. Click the following link to access the audio of "Episode 20 - Mike Reilly Remembers Longtime Crew Mate Eric Cooper" or watch the video via "Read More."
Labels:
Eric Cooper
,
Mike Reilly
,
Podcast
,
UEFL
,
Umpire Odds/Ends
Tuesday, October 22, 2019
Joe West Sues Paul LoDuca Over Bribery Claim
MLB umpire Joe West filed a lawsuit against Paul Lo Duca, alleging defamation after the former catcher in May purportedly asserted during a podcast that West accepted a bribe in exchange for favorable calls during a Mets game. West's complaint reads, "These statements impugn the integrity, honesty and professional fitness of Mr. West and affect his profession as a Major League Baseball umpire."
West's lawsuit against Lo Duca and The Action Network, a sports betting website that hosted or distributed the podcast, was filed in New York according to USA Today.
In May, we reported on Lo Duca's audio accusations against West, including claims that West ejected him "eight or nine" times, and that New York teammate Billy Wagner purportedly bribed West with the use of a car in exchange for favorable balls/strikes calls during a Phillies-Mets game ("I lend him my '57 Chevy so he can drive it around so then he opens up the strike zone for me"), finding that they might just be slanderous.
Related Post: Pants on Fire - Paul Lo Duca's Joe West Accusation (5/10/19).
Fact Check - Wagner Claim: We fact checked Wagner's appearances against Philadelphia from 2006 through 2009, when Wagner was on the Mets, and West made just one appearance: as a second base umpire on August 30, 2007, in Philadelphia. Ed Hickox was the home plate umpire for that game.
The complaint corroborates our research: "In reality, during 2006 and 2007, the two years that Lo Duca played for the New York Mets with Billy Wagner, Joe West was the home plate umpire for a game between the Philadelphia Phillies and the Mets only once, Billy Wagner did not pitch at all, and the game ended on a home run, not on called strikes."
Fact Check - Lo Duca Ejections: Of Lo Duca's eight career ejections, just one involved West (in 2003), and never before the game actually started, which was an allegation made by Lo Duca during the podcast.
Precedent for Defamatory Litigation: In 2011, NBA referee Bill Spooner—who previously was a minor league baseball umpire—filed a lawsuit against The Associated Press alleging defamation over AP report Jon Krawczynski's allegedly libelous tweet during a January 24 game between the Houston Rockets and Minnesota Timberwolves. Krawczynski purportedly tweeted, "Ref Bill Spooner told [Wolves Head Coach Kurt] Rambis he’d ‘get it back’ after a bad call. Then he made an even worse call on Rockets. That’s NBA officiating folks."
Spooner's suit alleged that Krawczynski, an AP reporter, reported the "get it back" statement as fact when it did not actually happen, triggering an NBA disciplinary investigation into Spooner's actions that tarnished his reputation.
In December 2011, the AP agreed to pay $20,000 in damages to Spooner to settle the lawsuit, and to remove the tweet from Krawcynski's account. In its settlement with Spooner, the Associated Press released a statement acknowledged that it "learned through discovery that referee Bill Spooner and coach Kurt Rambis have both consistently and independently denied that Mr. Spooner told the coach 'he'd get it back' in an exchange that occurred after a disputed call against the Timberwolves on Jan. 24, 2011."
The AP went on to explain it was a misunderstanding: "The NBA promptly investigated at the time and concluded that Mr. Spooner had acted properly...During the game, Mr. Krawczynski tweeted what he believed he had heard. Mr. Krawczynski acknowledges the possibility that he misunderstood what Mr. Spooner said and has therefore removed the Tweet from his APKrawczynski Twitter feed."
A $20,000 mistake... Krawczynski no longer works for the Associated Press.
West's lawsuit against Lo Duca seeks unspecified damages. The complaint is filed under case #160250/2019 in New York County Supreme Court as Joseph H West v. The Action Network, Inc. et al. Summons were issued to The Action Network and Paul Lo Duca.
West's lawsuit against Lo Duca and The Action Network, a sports betting website that hosted or distributed the podcast, was filed in New York according to USA Today.
In May, we reported on Lo Duca's audio accusations against West, including claims that West ejected him "eight or nine" times, and that New York teammate Billy Wagner purportedly bribed West with the use of a car in exchange for favorable balls/strikes calls during a Phillies-Mets game ("I lend him my '57 Chevy so he can drive it around so then he opens up the strike zone for me"), finding that they might just be slanderous.
Related Post: Pants on Fire - Paul Lo Duca's Joe West Accusation (5/10/19).
![]() |
| Lo Duca's tall tales may be legally defamatory. |
The complaint corroborates our research: "In reality, during 2006 and 2007, the two years that Lo Duca played for the New York Mets with Billy Wagner, Joe West was the home plate umpire for a game between the Philadelphia Phillies and the Mets only once, Billy Wagner did not pitch at all, and the game ended on a home run, not on called strikes."
Fact Check - Lo Duca Ejections: Of Lo Duca's eight career ejections, just one involved West (in 2003), and never before the game actually started, which was an allegation made by Lo Duca during the podcast.
![]() |
| Bill Spooner successfully sued the AP. |
Spooner's suit alleged that Krawczynski, an AP reporter, reported the "get it back" statement as fact when it did not actually happen, triggering an NBA disciplinary investigation into Spooner's actions that tarnished his reputation.
In December 2011, the AP agreed to pay $20,000 in damages to Spooner to settle the lawsuit, and to remove the tweet from Krawcynski's account. In its settlement with Spooner, the Associated Press released a statement acknowledged that it "learned through discovery that referee Bill Spooner and coach Kurt Rambis have both consistently and independently denied that Mr. Spooner told the coach 'he'd get it back' in an exchange that occurred after a disputed call against the Timberwolves on Jan. 24, 2011."
The AP went on to explain it was a misunderstanding: "The NBA promptly investigated at the time and concluded that Mr. Spooner had acted properly...During the game, Mr. Krawczynski tweeted what he believed he had heard. Mr. Krawczynski acknowledges the possibility that he misunderstood what Mr. Spooner said and has therefore removed the Tweet from his APKrawczynski Twitter feed."
A $20,000 mistake... Krawczynski no longer works for the Associated Press.
West's lawsuit against Lo Duca seeks unspecified damages. The complaint is filed under case #160250/2019 in New York County Supreme Court as Joseph H West v. The Action Network, Inc. et al. Summons were issued to The Action Network and Paul Lo Duca.
Labels:
Articles
,
Joe West
,
News
,
UEFL
,
Umpire Odds/Ends
Subscribe to:
Posts
(
Atom
)






































