Editions
Los 40 USA
Scores
Follow us on
Hello

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.

KANSAS CITY, MISSOURI - APRIL 20: Cole Ragans #55 of the Kansas City Royals pitches against the Baltimore Orioles during the first inning at Kauffman Stadium on April 20, 2024 in Kansas City, Missouri.   Kyle Rivas/Getty Images/AFP (Photo by Kyle Rivas / GETTY IMAGES NORTH AMERICA / Getty Images via AFP)
KYLE RIVASAFP

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.

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.

Rules