MLB

Umpire call on the first pitch so bad nobody could believe it

As Kansas City and Baltimore got underway, home plate umpire Ryan Blakney made a bewildering call on the first pitch of the game.

KYLE RIVAS | AFP
A product of Cajun country in south Louisiana, Jeff played football through high school, and baseball through college and beyond. After getting a BFA from the Savannah College of Art & Design, he moved to London, where he worked for Sky Sports and coached the 2005 British Champion Croydon Pirates baseball team. He also cooks a mean jambalaya.
Update:

A certain sector of baseball aficionados have been howling for an automated strike zone for years, with those calls becoming ever more shrill. For the record, I am not a fan of the idea for a host of reasons, and I believe that implementing that technology will make those fans less satisfied with the calls, not more. But it is difficult to ignore their argument when you see calls like the one made on Sunday in Kansas City.

On the very first pitch of the game, home plate umpire Ryan Blakney made a bewildering call that had everyone scratching their heads. Royals southpaw starter Cole Ragans threw a 96-mph fastball to Baltimore’s Gunnar Henderson that was right down the middle. It was called a ball.

Related stories

Directly on the back of the Bally Sports Kansas City announcers introducing the umpiring crew, Ryan Lefebvre said, “Fastball is right down the middle for ball one.” The baffled co-commentator Rex Hudler said, “What?! My goodness! Not on pitch one!” to which Lefebvre wondered aloud, “What part of that pitch is not a strike?”

In the end, the call had no bearing on the at-bat since Ragans struck Henderson out anyway. But none of the remaining pitches were as clearly in the zone as the one called a ball.

Tagged in:

We recommend these for you in MLB

Most viewed

More news