ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Now For Something Completely Different: Once-in-a-Lifetime Plays Add to Baseball Fun

Updated on May 23, 2017
Carl Yastrzemski batting against Cleveland in 1978 or '79.
Carl Yastrzemski batting against Cleveland in 1978 or '79. | Source

There are probably more bizarre plays in baseball than any other sport. There are just so many situations over so many years that you’re bound to see something at some point that you’ve never seen before.

Buck Showalter still looks a little confused by the bizarre triple play he once witnessed.
Buck Showalter still looks a little confused by the bizarre triple play he once witnessed. | Source

The Question

The most bizarre play I ever heard about was told by Buck Showalter that happened to his team while managing in the minor leagues – his team managed to hit into a triple play without any fielder touching the ball. That’s a head scratcher. I’ll let you try to figure it out and provide the answer at the end of this blog. The key things to remember: The team had runners on first and second, the ball was hit and no fielder touched it.

An Unusual Scoring Play

The most bizarre play I ever witnessed in person was Carl Yastrzemski scoring from first base on a strikeout. This happened at old Comiskey Park on Chicago’s South Side in 1977. The White Sox were leading the Red Sox 3-2 in the sixth inning when Yaz drew a one-out walk. White Sox pitcher Francisco Barrios fanned Carlton Fisk for the second out, bringing first baseman George “Boomer” Scott to the plate.

Big Swinger

Scott, for those of you who don’t remember, was a burly power-hitter who had led the American League with 36 homers and 109 RBIs for Milwaukee in 1975. He was one of those players who understood that not only do chicks dig the long ball, but also that teams pay a lot more money to those who can hit the long ball.

Because of that Scott had geared his swing for homers, especially at Fenway Park where a long pop-up could reach the Green Monster. My brothers and I imitated him by swinging straight up and down as hard as we could. You could have placed a china tea set on a table directly in front of home plate and chances are Scott’s swing would never hit it.

The Run-Scoring Strikeout

So with two outs and Yaz on first, Scott was naturally swinging for the fences. And missing. He swung and missed badly at strike three, a pitch that bounced in the dirt in front of the plate. But the ball must have struck catcher Jim Essian’s shinguard, because it rebounded in front of the plate down the first base line.

Scott dug for first but this was an easy play. Essian pounced on the ball, scooped it up and fired it to first. A perfect throw.

Except that for some reason first baseman Jim Spencer was charging in. I don’t know if he thought Scott had hit the ball, or if it was an involuntary reaction to seeing a ball head his direction. But because of it, the catcher’s throw arced over Spencer’s head.

This still wouldn’t have been so bad except that ball hit the back edge of the base and caromed down the rightfield line.

Now another problem came into play for the White Sox. Because Scott was a dead-pull hitter, the outfielders had swung around to left. Rightfielder Richie Zisk had set up nearly in centerfield, meaning he had an excessively long run to the line to retrieve the errant throw.

By the time Zisk finally had the ball in hand, Yaz – almost 38 years old and hardly a speedster – had motored all the way around the bases and scored. Scott, who at age 33 had lost what little speed he had, reached third.

So, just to make things clear, on a strikeout that should have been the third out, the Red Sox scored the tying run and got a runner to third. It was the most bizarre thing I’d ever seen. Barrios ended any further damage by getting Butch Hobson to fly out.

Later in the game, Rice singled and then took off on a steal of second base. But as he ran, Barrios uncorked another wild pitch, allowing Rice to continue to third. Yaz then hit a sacrifice fly for what proved to be the winning run.

Triple Play Answer

Now back to Buck Showalter’s bizarre triple play. Here’s what happened: The runners on first and second were off with the pitch on a hit-and-run. The batter hit the ball but it was sky-high pop-up toward the shortstop. Pop-up on the infield with runners on first and second, that’s the infield fly rule and the batter is automatically out. Out No. 1. But remember that the ball is still in play and runners can advance at their own risk.

The runner who had been on second recognized that the ball had been popped up, hit the brakes and reversed direction. The runner who had been on first, though, kept steaming ahead with his head down and ran right past the other runner. A runner is out when he passes a runner ahead of him. So out No. 2.

Gravity being what it is, the pop-up eventually had to come down. And it did, just as the runner who had been on second ran under it on his way back to second. The ball plunked him on the shoulder, keeping the fielder from catching it. A runner who is hit by a batted ball before the fielder can field it is out for interference. And that’s out No. 3. A triple play without a fielder involved.

Showalter swears the story is true and is also why he will never ever again call for a hit-and-run with two runners on base.

Tell Me Your Story

So, what’s the most bizarre play you’ve ever witnessed in person? Tell me about it in the comments section. I love hearing people’s baseball stories.


This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

Show Details
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)