Blue Jays vs. Red Sox somehow wasn't John Schneider's first time dealing with absurd Fourth Out rule

If John Schneider had a nickel for every time he managed a team that encountered the "fourth out rule" he would have two nickels. It's not a lot, but it's weird it happened twice right? The manager of the Toronto Blue Jays was almost at a loss for words when he talked about the game following Toronto's 2-1 win over the Boston Red Sox on Monday (Aug. 10).

Jays Journal covered an explanation of the rule, breaking down how a runner from third was allowed to score, even though that runner didn't tag up on a fly out to center field in which the ball was caught and another runner was called out on the same play for also not tagging up. The inning was technically over after the Blue Jays doubled off the runner at first, but could have also appealed to third to enforce the "fourth out," which would have negated the run entirely. They didn't appeal and the run was allowed to count.

Amidst all the chaos and confusion, Schneider was asked about the play after the game and he explained everything from his point of view. He also went on to say, "Yeah it was confusing, first time for me. Going forward if this play happens again in the next 100 years, if it's us we will record the out at third."

However, thanks to some in depth sleuthing on the internet by Lansing Lugnuts broadcaster Jesse Goldberg-Strassler, this exact play happened ten years ago. On Jul. 30, 2016, the Lugnuts were playing in Fort Wayne against the TinCaps. In the bottom of the fifth, Nick Vilter flied out to left fielder Austin Davis. Davis threw the ball home to catcher Ryan Hissey who then tossed it to first baseman Justin Atkinson. On the play, Ruddy Giron scored from third, while Carlos Belen was called out at first.

There's a slight difference here in the fact that although both runners moved on contact and didn't tag up, Lansing attempted a play at home, before throwing the ball to first base to appeal the play. But the similarity is that the inning ended on the appeal at first, but the run holding up and being allowed to count. Both plays officially resulted in what was called a sacrifice double play.

The other similarity is that in 2016, the Lugnuts were a farm team for the Blue Jays and they were managed by none other than John Schneider. So for Schneider to say it's the first time this play has happened to him, it's a crazy coincidence that it has actually happened more than once.

Blue Jays didn't allow the bizarre ruling to ruin the outcome of the game

Toronto still walked away with the win when it was all said and done. Had the outcome gone differently, the Blue Jays may have had more to say about this incident. However, it's the Red Sox who probably have the biggest gripe. The reason the runners took off without tagging up is because the scoreboard showed there were two outs when in fact there was only one.

Any ball player knows that you're not supposed to rely on the scoreboard and they should have been checking in with their coaches to make sure. And the scoreboard itself is actually managed by employees of Major League Baseball and not the Blue Jays - but there is still a gripe to be had here. If the runners did tag, there's an argument to be made that Siegler would have scored and they would have had Nick Sogard still on first base with two out and Wilyer Abreu coming to the plate and who know what would've happened had Abreu faced Simeon Woods Richardson instead of Tyler Rogers to begin the top of the eighth inning.

Either way, it's a really weird play that enforced a rule that rarely comes up and both the Blue Jays and the Red Sox are likely hoping for less controversy as the series continues.

Add us as a preferred source on Google

Follow