Is this the worst call in MLB history?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • FirstTimer
    Freeman Error

    • Feb 2009
    • 18729

    Is this the worst call in MLB history?



    The "worst call ever" is a term that's popping up quite frequently in the wake of umpire Tim Welke somehow deciding that Colorado's Todd Helton was close enough to first base on Wednesday and that Los Angeles' Jerry Hairston was out on the ol' 5-3 force.

    I'm not sure I can go that far. It could have ruined a perfect game. It could have occurred in a crucial postseason game in October instead of on a getaway day in early May.

    But if we're talking on a pure "holy heck, what planet was Welke viewing the action from" basis? Then yes, it probably is the worst call ever. One that the 27-year veteran and member of four World Series crews is going to have trouble shaking from his reputation in today's instant world of iPads, Twitter and instant game highlights on your cell phone.

    Not that you needed a MLB.TV replay to know that Welke completely booted this ruling in the sixth inning of the Rockies' 8-5 win over the Dodgers at Coors Field.

    Watch it unfold in real time: _

    In case you're somehow worse than Welke and missed the call on both the big screencap and that replay, let's go to Dodgers manager Don Mattingly. He immediately argued the call by either staging a demonstration of the distance between Helton's left foot and first base or estimated the amount of Interent grief that Welke was about to get for the call.

    (MLB.TV)

    Seriously, after watching that play, the only explanations for making that call are that Welke was amazed at Chris Nelson's diving stop at third or that he got lost in this thinking about the dining options in his next city. We can't be certain, however, because an attendant at the umpire's room told the Associated Press that the umpires would not be commenting on the play.

    Perhaps it's also possible that he could have written this off as a "neighborhood play" had Helton been a foot or so closer to the bag. But even the Rockies veteran first baseman had no trouble telling Troy Renck of the Denver Post that his foot was closer to the 970 area code of western Colorado than it was to the 303 or 720 codes in Denver. There's no way that he could have ruled that a gimme, no matter how great of a career Helton has had. (Plus, this isn't the NBA where the career achievements of a player are routinely figured into judgements.)

    Welke's call ended the top half of the sixth inning instead of giving the Dodgers runners at first and second with two outs. Though Jason Giambi's walkoff three-run homer provided the final margin, who knows how things might have unfolded differently had the inning continued?

    ''It really doesn't matter at this point,'' Mattingly told reporters after the game. ''I think he knows he missed it. I think Helton told him he was off the bag. We had a chance to get a run there. I just don't think he realized he came off the bag.''

    Of course, it's probably not cliche to say that no one feels worse than this about Welke and you do have to feel bad for the guy. His reputation wouldn't be getting raked over the coals if instant replay existed on a wider scale or if other umpires weren't afraid to overrule one of their colleagues every now and then.

    Still, that's a call he has to make. And one that will deservedly go on his permanent record.
  • Rudi
    #CyCueto
    • Nov 2008
    • 9905

    #2
    He's giving Todd Helton the benefit of the doubt because hes a veteran

    Comment

    • FirstTimer
      Freeman Error

      • Feb 2009
      • 18729

      #3
      I loved Helton's reaction...

      Turn..."uhh....flip ball.....run off quietly"

      I think one of the worst rules in baseball is that other umps can't help out unless the retarded umpire asks for the help first.

      Comment

      • Warner2BruceTD
        2011 Poster Of The Year
        • Mar 2009
        • 26142

        #4
        This was bad, but nothing will ever top the Braves/Pirates call last year.

        Comment

        • Senser81
          VSN Poster of the Year
          • Feb 2009
          • 12804

          #5
          Agree on the terrible call, but I think the umps sometimes botch those "plays at first" calls because they have to watch/listen for both the ball getting to the first baseman and the runner's foot. For whatever reason, sometimes the ump's brain won't be able to process what actually happened.

          My vote for the worst call I've ever seen is during the Twins-Yankees postseason, when the special "foul line" postseason umpire had a ball drop about 15 feet away from him clearly inside the foul line (at that section of the stadium there was perhaps 2 feet of 'foul territory' next to the wall), actually hit off the Yankee outfielder's glove in fair territory, and then bounce into the stands for a ground-rule double. So, not only did the ball end up bouncing in fair territory, it was also touched by a player who clearly was in fair territory at the time he touched it. The ump's call? Foul ball.

          Comment

          • Leftwich
            Bring on the Season

            • Oct 2008
            • 13700

            #6
            Originally posted by Warner2BruceTD
            This was bad, but nothing will ever top the Braves/Pirates call last year.
            Truf.

            A lot of people will say the Jim Joyce play is the worst cause it ruined a perfect game, the play was close but as for the Braves/Pirate and OP, those are terrible.

            Originally posted by Tailback U
            It won't say shit, because dying is for pussies.

            Comment

            • Slateman
              Junior Member
              • Apr 2009
              • 2777

              #7
              I'm still going with the Jim Joyce call. Ruined a perfect game.
              The king was shaken. He went up to the room over the gateway and wept.
              As he went, he said: "O my son Absalom! My son, my son Absalom!
              If only I had died instead of you
              O Absalom, my son, my son!"

              Comment

              • FirstTimer
                Freeman Error

                • Feb 2009
                • 18729

                #8
                Originally posted by Warner2BruceTD
                This was bad, but nothing will ever top the Braves/Pirates call last year.
                I guess. But I'm still not 100% sure that he tagged him. No view really shows it. I think Lugo was tagged and I think the call was blown but it wasn't THIS obvious.

                Comment

                • jms493
                  Junior Member
                  • Feb 2009
                  • 11248

                  #9
                  WTH happened to Melky?

                  Comment

                  Working...