2011 World Series Game 3 - Texas Rangers v St Louis Cardinals

A reporter’s suggestion of umpire bias was way out of line

59 Comments

We finally have a situation in which I feel that an umpire and Joe Torre are worthy of being defended after an on-field screwup and in which I found myself nodding my head in agreement with Joe Buck and Tim McCarver.

First base umpire Ron Kulpa screwed up on Saturday night. There’s no mistaking that. Rangers first baseman Mike Napoli tagged baserunner Matt Holliday out at first base during the Cardinals’ four-run fourth inning in Game 3. He clearly tagged him. Kulpa called him safe. Blown call, no question.  But the far more egregious act came after the game when a pool reporter from the Associated Press asked Ron Kulpa — who had made himself available to discuss the missed call — about the fact that he was from St. Louis.

I suppose it’s possible that the reporter simply and abruptly changed the subject from the blown call to a feel-good story about Kulpa’s roots, but it’s more likely that he was insinuating that the umpire was harboring bias based on some local rooting interest.  That’s certainly what Joe Torre felt as he took the unusual step of criticizing that question and defending Kulpa’s integrity before last night’s game.

And good for Torre. We can — and often do — criticize bad calls and bad umpires around here. We want instant replay. We think that some umpires have shown that they are incompetent or something close to it. But it’s an entirely different thing to suggest that one is biased in favor of a certain team based on … nothing.  Even Joe West is an equal opportunity awful umpire. Suggesting or even entertaining the notion that one favors a given team is simply inappropriate behavior for a credentialed reporter.

I don’t say this very often, but last night Joe Buck and Tim McCarver hit the nail on the head when they noted how stupid and pervasive charges of bias are. Buck noted that, at various times, he’s been accused of favoring just about every team. I can certainly relate to that. In just the past few weeks I’ve been accused of tipping the editorial scales in favor of the Yankees, the Red Sox, the Rangers, the Tigers and, of course, my personal rooting interest, the Braves. Anyone who writes or reports about the game gets that. Never does it make any sense. More importantly, never do such accusations come from a person who themselves isn’t a partisan of the team being criticized or a person who hates the team being praised.

The bias card is so, so common these days that I presume that this AP reporter felt like he was simply asking a question that he felt readers were demanding be asked. But the fact is that true bias — especially bias by someone significant in a way that matters — is pretty damn rare. There’s a rational bias of broadcasters who prefer to show east coast games and feature east coast topics because of ratings and page views. There are the local provincials who see and report on the entire world through locally-tinted goggles. There are disclosed biases — like my Braves fandom — that exist in a writer’s heart but which don’t cause the writer to ignore reality.

But an umpire being unable to shake off what could have possibly been a youthful rooting interest so that it impacts his job? Please. Even the suggestion of that absent a shred of evidence requires one to leave sanity and reality behind and reveals that the reporter himself was biased by the culture of bias accusations that has sprung up on the Internet over the years. And no matter what motivated it, the question itself was low rent and totally unprofessional.

But what do you expect? The guy who asked it was probably from [insert the city you don’t like here].

Video: Nelson Cruz hits second-longest home run of 2016

ANAHEIM, CA - SEPTEMBER 14:  Nelson Cruz #23 of the Seattle Mariners celebrates his solo homerun with Daniel Vogelbach #20 of the Seattle Mariners to take a 2-1 lead over the Los Angeles Angels of Anaheim during the seventh inning at Angel Stadium of Anaheim on September 14, 2016 in Anaheim, California.  (Photo by Harry How/Getty Images)
Getty Images
1 Comment

There’s certainly never a bad time to hit a home run, but when you get the opportunity to crush a triple-deck, 493-foot shot off of Tyler Duffey, you should take it. With the Mariners down 2-0 to the Twins in the fourth inning, Cruz hammered a fastball to deep left field for his 39th long ball of the season — and the second-longest home run hit in 2016, to boot.

It doesn’t hurt that the Mariners are 1.5 games back of a playoff spot, although they’ll have to oust the Blue Jays, Orioles, or Tigers to get a wild card. They’ve gone 3-3 in the last week, dropping two consecutive series to the Astros and Blue Jays and taking their series opener against Minnesota 10-1 on Friday night.

Cruz, for his part, entered Saturday’s game with a .299/.337/.610 batting line and six home runs in September. According to ESPN.com’s Home Run Tracker, Cruz sits behind Edwin Encarnacion and Mike Napoli with 13 “no-doubt” home runs in 2016, third-most among major league sluggers. It’s safe to say he can add Saturday’s moonshot to that list.

Marlins’ outfielder and undisputed home run king Giancarlo Stanton remains untouched at the top of the Statcast leaderboard with a 504-ft. home run, and it’s difficult to envision any slugger reaching beyond that before the end of the season. Even so, Cruz won’t need to clear 500 feet to extend an impressive hitting record. One more home run will put the 36-year-old at 40 on the year, making 2016 his third consecutive season with at least 40 homers, and his second such season doing so in Seattle.

Report: John Farrell won’t rule out a postseason return for Pablo Sandoval

BOSTON, MASSACHUSETTS - APRIL 11:  Pablo Sandoval #48 of the Boston Red Sox looks on from the dugout before the Red Sox home opener against the Baltimore Orioles at Fenway Park on April 11, 2016 in Boston, Massachusetts. The Orioles defeat the Red Sox 9-7.  (Photo by Maddie Meyer/Getty Images)
Getty Images
6 Comments

It’s been a strange season for Red Sox’ third baseman Pablo Sandoval, who lost his starting role in spring training, went 0-for-6 in three regular season appearances, and underwent season-ending surgery to repair a torn labrum in his left shoulder in May. That was the last the Red Sox were supposed to hear about Sandoval until spring 2017, when he was expected to rejoin the team after a lengthy rehab stint in Florida.

On Saturday, manager John Farrell was telling a different story. Per MLB.com’s Sam Blum, Farrell hinted that Sandoval could return to the team as soon as October, albeit in a very limited capacity.

At the time of the surgery, it was all looking at the start of next Spring Training,” Farrell said. “We’re not getting too far ahead of ourselves here, but at the same time, we compliment him for the work he’s put in, the way he’s responded to the rehab, the way he’s worked himself into better condition. We’re staying open-minded.

If the 30-year-old does return in 2016, don’t expect him to look like the three-home run hitter of the 2012 World Series. Should the Red Sox lose another player to injury, Sandoval might be called on as a backup option, but he’s unlikely to see substantial playing time under any other circumstances. Despite making two appearances at DH in the instructional league, Sandoval has not started at third base since undergoing surgery, though Farrell noted that a return to third base would be the next logical step in his recovery process.

Sandoval has yet to hit his stride within the Red Sox’ organization after hitting career-worst numbers in 2015. According to FanGraphs, his Offensive Runs Above Average (Off) plummeted to -20.2, contributing approximately two wins fewer than the average offensive player in 2015. (The Diamondbacks’ Chris Owings held the lowest Off mark in 2015, with -26.3 runs below average.) Sandoval has not appeared in a postseason race since the Giants’ championship run in 2014.

Heading into Saturday evening, the Red Sox could clinch their spot in the postseason with a win over the Rays and an Orioles’ loss.