MLB Ejection 160 - John Tumpane (4; Carl Willis)

HP Umpire John Tumpane ejected Guardians pitching coach Carl Willis (foul ball call to Garrett Hampson; QOCY) in the top of the 6th inning of the #Royals-#Guardians game. With one out and none on, Royals batter Hampson swung at a 1-2 changeup from Guardians pitcher Pedro Avila, ruled a foul ball by HP Umpire Tumpane. Replays indicate Hampson's bat made contact with the baseball before it touched the ground, the call was correct. At the time of the ejection, the Royals were leading, 5-4. The Royals ultimately won the contest, 9-4.

This is John Tumpane (74)'s 4th ejection of 2024.

This is the 160th ejection report of the 2024 MLB regular season.

This is the 26th coach ejection of 2024. Ejection Tally: 80 Managers, 26 Coaches, 54 Players.

This is Cleveland's 3rd ejection of 2024, 2nd in the AL Central (CWS 8; CLE 3; KC, MIN 2; DET 1).

This is Carl Willis' 1st ejection since Sept 3, 2017 (Sam Holbrook; QOC = N [Balls/Strikes]).

This is John Tumpane's 4th ejection of 2024, 1st since July 6 (Derek Shelton; QOC = N [Balls/Strikes]).

Wrap: Kansas City Royals vs Cleveland Guardians (Game 2), 8/26/24 | Video as follows:

MLB Ejection 123 - Edwin Moscoso (3; Bruce Bochy)

HP Umpire Edwin Moscoso ejected Rangers manager Bruce Bochy (foul tip call; QOCY) in the top of the 5th inning of the #WhiteSox-#Rangers game. With none out and one on, White Sox baserunner Luis Robert Jr attempted to steal second base on a 2-2 changeup from Rangers pitcher Michael Lorenzen, resulting in a foul tip by White Sox batter Andrew Benintendi. Replays indicate Rangers catcher Jonah Heim initially caught the batted ball before losing it on the post-catch transfer/exchange attempt, the call was correct. At the time of the ejection, the White Sox were leading, 2-1. The Rangers ultimately won the contest, 4-3, in 10 innings.

This is Edwin Moscoso (32)'s 3rd ejection of 2024.

Official Baseball Rules: "A FOUL TIP is a batted ball that goes sharp and direct from the bat to the catcher and is legally caught. It is not a foul tip unless caught, and any foul tip that is caught is a strike, and the ball is in play."

This is the 123rd ejection of the 2024 MLB regular season.

This is the 61st manager ejection of 2024. Ejection Tally: 61 Managers, 17 Coaches, 45 Players.

This is Texas' 5th ejection of 2024, 4th in the AL West (HOU, SEA 7; OAK 6; TEX 5; LAA 2).

This is Bruce Bochy's 4th ejection of 2024, 1st since June 14 (Vic Carapazza; QOC = Y [RLI]).

This is Edwin Moscoso's 3rd ejection of 2024, 1st since July 11 (Matt Blake; QOC = N [Balls/Strikes]).

Wrap: Chicago White Sox vs Texas Rangers, 7/22/24 | Video as follows:

MLB Ejection 066 - Malachi Moore (1; Dave Martinez)

HP Umpire Malachi Moore ejected Nationals manager Dave Martinez (check swing dead ball strike three call) in the top of the 3rd inning of the #Nationals-#Guardians game. With two out and none on, Nationals batter Jacob Young attempted to check his swing on a 1-2 fastball from Guardians pitcher Ben Lively for a swinging third strike, called by Moore, as the pitch touched the batter's hand.* Although Martinez signaled a "hold" for consideration about whether to challenge the play, the Nationals ran out of time as the 15-second challenge timer expired before Martinez requested a review. Replays indicate the pitched ball touched Young's hand as he struck at the pitch, the call was correct. At the time of the ejection, the Guardians were leading, 2-0. The Guardians ultimately won the contest, 3-2.

This is Malachi Moore (44)'s 1st ejection of 2024.

*Official Baseball Rules Definition of a strike states, "A STRIKE is a legal pitch when so called by the umpire, which touches the batter as they strike at it."

This is the 66th ejection of the 2024 MLB regular season.

This is the 29th player ejection of 2024. Ejection Tally: 29 Managers, 10 Coaches, 27 Players.

This is Washington's 3rd ejection of 2024, T-1st in the NL East (MIA, NYM, WAS 3; PHI 1; ATL 0).

This is Dave Martinez's 2nd ejection of 2024, 1st since April 19 (Cory Blaser; QOC = N-c [Obstruction]).

This is Malachi Moore's 1st ejection since July 18, 2023 (Pete Walker; QOC = N [Balls/Strikes]).

Wrap: Washington Nationals vs Cleveland Guardians, 6/1/24 | Video as follows:

MLB Ejections 21-2 - Stu Scheurwater (1-2; SF x2)

HP Umpire Stu Scheurwater ejected Giants manager Bob Melvin and 3B coach Matt Williams (foul ball call; QOCN) in the top of the 9th inning of the #Diamondbacks-#Giants game. With none out and two on, Diamondbacks batter Kevin Newman attempted to strike a 1-2 knuckle curve from Giants pitcher Nick Avila, ruled a foul ball by Scheurwater. Replays indicate the pitched ball did not appear to make contact with Newman's bat prior to touching the dirt, the call was incorrect. At the time of the ejections, the Diamondbacks were leading, 4-2. The Diamondbacks ultimately won the contest, 5-3.

These are Stu Scheurwater (85)'s 1st and 2nd ejections of 2024.

These are the 21st and 22nd ejection reports of the 2024 MLB regular season.

This is the 10th manager ejection of 2024.

This is the 4th coach ejection of 2024. Ejection Tally: 10 Managers, 4 Coaches, 8 Players.

This is San Francisco's 2/3rd ejection of 2024, 1st in the NL West (SF 3; SD 2; ARI, COL, LAD 0).

This is Bob Melvin's 2nd ejection of 2024, 1st since April 12 (Clint Vondrak; QOC = Y [Balls/Strikes]).

This is Matt Williams' 1st ejection since May 20, 2015 (Marvin Hudson; QOC = N [Balls/Strikes]).

This is Stu Scheurwater's 1st ejection since June 1, 2023 (Phil Nevin; QOC = N [Balls/Strikes]).

Wrap: Arizona Diamondbacks vs San Francisco Giants, 4/21/24 | Video as follows:

On-Deck Interference, A Bunt HBP & Fair-Foul at Home

An on-deck batter interference in Chicago, batter hit by a pitch while attempting a bunt in Cincinnati and catcher pouncing on a fair ball over home plate in New York comprise a trio of umpire Ask CCS questions over the past week.

On-Deck Interference: Cubs batter Patrick Wisdom's foul fly ball near Chicago's third base dugout drew two Pirates, including third baseman Ke'Bryan Hayes, who collided with Cubs on-deck batter Alexander Canario, who was trying to get out of the catcher's way but accidentally backed into the oncoming third baseman. After consultation, Crew Chief Alan Porter signaled batter Wisdom out for interference of his teammate Canario (who then came up to bat).

Official Baseball Rule 6.01(b), known as Fielder Right of Way, prescribes that, "The players, coaches or any member of a team at bat shall vacate any space (including both dugouts or bullpens) needed by a fielder who is attempting to field a batted or thrown ball." Whether intentional or not, an on-deck batter, dugout coach, etc. who hinders a fielder attempting to field a batted ball is guilty of interference, and the at-bat batter shall be called out for the interference of their teammate.

HBP During Bunt: Reds batter Luke Maile's attempted bunt ended unsuccessfully, as the pitched ball made contact with his hand coiled around the bat, either instead of or (more importantly) before contacting the bat. Play continued and Minnesota retired Maile at first base. Umpires went to Replay Review as the result of a Reds challenge and Replay HQ overturned the call, Crew Chief Marvin Hudson announcing that a dead ball strike would be charged to Maile for the ball hitting his hands first.

Fair or Foul at Home: Yankees batter-runner Gleyber Torres remained in the right-handed batter's box on a chopper at home plate as Blue Jays catcher Alejandro Kirk waited for the batted ball to spin back toward home plate and into fair territory before fielding the ball and tagging Torres out.

OBR's diagram of home plate confirms that the base itself is entirely in fair territory, with the intersection of the two foul lines (which themselves are within fair territory too) located at the point of home plate.

Video as follows:

Giant Un vs Intentional Ball Attendant Interference

As Athletics left fielder Conner Capel slid in attempt to catch Giants batter Bryce Johnson's foul fly ball, San Francisco ball dude Harvey reached in front of Capel and touched the baseball, ruled no catch (foul ball) by the umpire as Oakland sought an interference call. We now review the Official Baseball Rules concerning interference by a person authorized to be on the playing field.

In the bottom of the 6th inning of the final Spring Training Battle of the Bay, Giants batter Johnson hit a fly ball into foul territory in left, Capel giving chase and going into a slide in an attempt to catch the ball at the tarp along the short wall. As Capel slid into position with his glove outstretched, however, the ball attendant ("ball dude" in SF) attempted a catch of his own, with ball dude Harvey's glove contacting the ball before Capel had a chance to play it. Capel ultimately came away with the baseball, but the damage had already been done by Harvey's premature touch, resulting in a foul ball [no catch] call by 3B Umpire Nate Tomlinson (umpires in Spring tend to switch bases every few innings; Alex Tosi was originally at third base but had moved to first base for this inning).

Official Baseball Rule 6.01(d) is called Unintentional Interference, and states, "In case of unintentional interference with play by any person herein authorized to be on the playing field (except members of the team at bat who are participating in the game, or a base coach, any of whom interfere with a fielder attempting to field a batted or thrown ball; or an umpire) the ball is alive and in play. If the interference is intentional, the ball shall be dead at the moment of the interference and the umpire shall impose such penalties as in their opinion will nullify the act of interference."

The comment to OBR 6.01(d) states, "The question of intentional or unintentional interference shall be decided on the basis of the person’s action. For example: a ball attendant, police officer, etc., who tries to avoid being touched by a thrown or batted ball but still is touched by the ball would be involved in unintentional interference. If, however, they pick up the ball, catch it, or touch the ball by intentionally pushing or kicking at the ball, this act would constitute intentional interference."

Because ball dude Harvey clearly tried to catch the ball (as opposed to avoid it), this is an example of intentional interference, the penalty for which is to call "Time" and nullify the act. In order to nullify the act, 3B Umpire Tomlinson would have had to determine whether or not fielder Capel would have caught the ball, had Harvey not interfered.

Crew Chief Bill Miller ultimately announced that Replay Review had confirmed the "safe" call, but OBR 6.01(d) interference is not reviewable (unlike fan interference, which is reviewable as a boundary call). Thus, Replay was used here simply to determine whether or not Capel caught the ball cleanly, which, thanks to Harvey's touch, he clearly did not.

Video as follows:

Rules Review - LLWS Flashy Triple Play Turned Foul Ball

The Little League World Series' Italy vs Australia elimination game produced an absolutely wild and wacky sequence that began as a bases-loaded, none-out triple play before umpires corrected it to, and Replay Review confirmed, the ultimate call of a foul ball. From the infield fly rule to fair/foul to interference, we review the Official Baseball Rules to determine what happened and what could have transpired had things turned out differently.

Play: With none out and the bases loaded in the top of the 3rd inning, a batter Team Italy, trailing Australia 5-0, hit a high fly ball along the first baseline, on the infield between home plate and first base. The ball fell untouched and was fielded by Australia's first baseman, who threw to the catcher ahead of Italy's runner. The catcher stepped on home plate before throwing to the third baseman, who tagged Italy's lead runner R3 as he ran back toward third base. Having tagged R3, Australia's third baseman then threw to the second baseman, who stepped on second base and then tagged Italy's trailing runner R1 as R1 ran toward second base. Following this, Italy's middle runner R2 took off for third base and Australia's second baseman threw to the third baseman, who tagged R2 as he slid into third base.

Call: The HP Umpire declared an Infield Fly and a fair ball, the 3B Umpire declared R3 out at third base, the 2B Umpire declared R1 out at second base, and then the 3B Umpire declared R2 out at third base.

Correcting the Fourth Out...and More: After the apparent triple play, the umpires conferred and determined that the batted ball had become foul, thus negating all subsequent action. The play was ruled a foul ball, which was confirmed after manager's challenge by Australia, and Italy's batter returned to bat.

Remember, even with all other criteria satisfied (runners on first and second [or bases loaded] with less than two out, batted ball is a fly ball which is not a line drive  nor bunt that can be caught be an infielder with ordinary effort), it is only an infield fly if the batted ball is fair [it is not an infield fly if the ball is foul], and the umpire's mechanic should be "Infield Fly, if Fair."

What if (Case Play): Although the ball was foul, let us assume for the purpose of discussion it was fair instead. In that case, the batter would be out for the Infield Fly, R3 would be out on the tag while off-base, and R1 would be out on the tag while off-base (R2's apparent out would be irrelevant and superfluous).

In that sense, the umpires officiated the infield fly portion of this play properly in real-time...the portion of the play that occurred after the first baseman fielded the baseball.

A Confounding Variable, Regardless of Fair/Foul: Replays indicate that while the batted ball was in flight, Australia's first baseman and Italy's baserunner R1 made contact while R1 was not touching first base. In this sense, presuming the umpires would have identified the first baseman F3 as the fielder entitled to field the batted ball pursuant to Official Baseball Rule 6.01(a)(10), R1 should be declared out for interference ("Fails to avoid a fielder who is attempting to field a batted ball...if two or more fielders attempt to field a batted ball and the runner comes in contact with one or more of them, the umpire shall determine which fielder is entitled to the benefit of this rule"). The fielder has the right of way in this situation.

This would then activate the Infield Fly Interference rule (from the definition of terms): "If interference is called during an Infield Fly, the ball remains alive until it is determined whether the ball is fair or foul. If fair, both the runner who interfered with the fielder and the batter are out. If foul, even if caught, the runner is out and the batter returns to bat."

Recap: If the umpires protect the pitcher as the fielder entitled to field the ball, foul ball is the correct call.

However, if the umpires identified the first baseman as the fielder entitled to field the ball, the proper call would have been a foul ball, but with the additional declaration that the runner from first base R1 is out for interference.

Under the Case Play scenario wherein the batted ball is fielded in fair territory and the pitcher is the protected fielder, this is a triple play (batter-runner out on the infield fly, R3 out on tag, R1 out on tag).

Under the Case Play scenario wherein the batted ball is fielded in fair territory and the first baseman is the protected fielder, this is a double play (R1 out on interference & batter-runner out on the infield fly).

Video as follows:

MLB Ejections 130-31 - Barksdale, Porter (Francona, Straw)

HP Umpire Lance Barksdale ejected Guardians manager Terry Francona and 3B Umpire Alan Porter ejected Guardians CF Myles Straw (foul ball reversed to foul tip or swinging strike three call; QOCY) in the bottom of the 9th inning of the #Tigers-#Indians game. With one out and one on (R3), Indians batter Myles Straw attempted to hit a 2-2 slider from Tigers pitcher Joe Jimenez, originally ruled a foul ball by HP Umpire Barksdale, and reversed following crew consultation to a third strike. Replays do not conclusively indicate whether or not Straw's bat made contact with the baseball, but do conclusively show that Tigers catcher Tucker Barnhart ultimately caught the ball prior to the ball touching the ground; whether via foul tip or via swinging strike, the call of strike three/out was correct. At the time of the ejections, the Tigers were leading, 4-3. The Tigers ultimately won the contest, 4-3.

This is Lance Barksdale (23)'s 2nd ejection of 2022.

This is Alan Porter's (64)'s 3rd ejection of 2022.

These are the 130th and 131st ejection reports of the 2022 MLB regular season.

This is the 72nd manager ejection of 2022.

This is the 41st player ejection of 2022. Prior to ejection, Straw was 0-4 (2 SO) in the contest.

This is Cleveland's 2/3rd ejection of 2022, T-3rd in the AL Central (CWS 5; DET 4; CLE, KC, MIN 3).

This is Terry Francona's 2nd ejection of 2022, 1st since June 9 (Paul Emmel; QOC = Y-c [Obstruction]).

This is Myles Straw's first career MLB ejection.

This is Lance Barksdale's 2nd ejection of 2022, 1st since April 9 (Keegan Thompson; QOC = U [Throwing At]).

This is Alan Porter's 3rd ejection of 2022, 1st since August 7 (Rocco Baldelli; QOC = N-c [Replay Review]).

Wrap: Detroit Tigers vs Cleveland Guardians, 8/16/22 | Video as follows:

MLB Ejection 073 - Marvin Hudson (1; David Bell)

HP Umpire Marvin Hudson ejected Reds manager David Bell (strike three [no foul ball] call; QOCY) in the bottom of the 4th inning of the #Rockies-#Reds game. With two out and none on, Reds batter Jesse Winker attempted to strike a 0-2 slider from Rockies pitcher German Marquez, ruled a swinging third strike by HP Umpire Hudson. Replays indicate Winker swung at and missed the pitch; the bat did not make contact with the ball, the strike three swinging / no foul ball call was correct. At the time of the ejection, the Reds were leading, 4-3. The Reds ultimately won the contest, 10-3.

The Cincinnati broadcasters referenced a play from the top of the 4th inning in which Wade Miley's initial 0-1 pitch to Rockies batter Elias Diaz was waved off by Hudson. Cincinnati's complaint was that Diaz called time and Hudson granted the request after Miley had started his windup delivery. Official Baseball Rule 5.04(b)(2) states umpires shall not call "Time" after a pitcher has started windup or come to set position.

However, replays additionally indicate Miley began his pitching motion before batter Diaz—who began the sequence outside of the batter's box (for a legal reason after strike one)—was reasonably set in the batter's box, which itself is a violation of OBR 6.02(a)(5): "A quick pitch is an illegal pitch. Umpires will judge a quick pitch as one delivered before the batter is reasonably set in the batter's box. With runners on base, the penalty is a balk; with no runners on base, it is a ball. The quick pitch is dangerous and should not be permitted."

So while "Time" should not be called after a pitcher has started windup, a pitcher shall not start such delivery before the batter is reasonably set in the box. Chicken or egg?

This is Marvin Hudson (51)'s 1st ejection of 2021.

Marvin Hudson now has 5 points in the UEFL Standings (1 Previous + 2 MLB + 2 Correct Call = 5).

Crew Chief Marvin Hudson now has 3 points in Crew Division (2 Prev + 1 Correct Call = 3).

This is the 73rd ejection report of the 2021 MLB regular season.

This is the 38th manager ejection of 2021.

This is Cincinnati's 4th ejection of 2021, 2nd in the NL Central (MIL 6; CIN 4; CHC, PIT 3; STL 2).

This is David Bell's 2nd ejection of 2021, 1st since April 25 (Joe West; QOC = U [Warnings]).

This is Marvin Hudson's 1st ejection since September 5, 2017 (Josh Donaldson; QOC = Y [Balls/Strikes]).

Wrap: Colorado Rockies vs. Cincinnati Reds, 6/12/21 | Video as follows:

Perils of Unreviewable - Foul Ball Triple Play Ends Game

In 2017, Tmac wrote that more plays should be reviewable. This is a devastating example of why as Friday's WBSC Italy-South Africa game ended on a triple play following what should have been a foul ball call, instead ruled fair by a HP Umpire who didn't see that a batted ball hit the batter in the batter's box.

With none out and two on (R1, R2) in the bottom of the 10th inning of the WBSC Europe/Africa Olympic Qualifier game between Italy and South Africa at Parma's Nino Cavalli Stadium, RSA batter Rowan Ebersohn hit a pitch into the dirt around home plate. Although the ball bounced off the ground and subsequently struck Ebersohn's left hip before settling on fair territory in front of home plate, HP Umpire Serge Makouchetchev ruled the ball fair, setting into motion the game-ending triple play, propelling Italy into a first-place tie with Israel for first place and plunging South Africa into sole possession of last place in the standings.

For those wondering, WBSC uses the Official Baseball Rules—same as Major League Baseball—and the rule making this a foul ball is 5.09(a)(7) regarding a batted ball touching the batter in the box: "a batted ball that strikes the batter or his bat [a second time] shall be ruled a foul ball."

Rule 5.09(a)(7) cases*
1. Batted ball touches batter (or bat a second time) while batter is in box = foul ball.
2. Batted ball touches batter/bat while batter is out of box, ball is over foul territory = foul ball.
3. Batted ball touches batter/bat while batter is out of box, ball over fair territory = out.
*Interference (incl potential multiple outs if runner(s)) can be called if intentional to deprive.

We're back in Parma, Italy.

Tmac Said So: In January 2017, Tmac proposed five items MLB and baseball as a whole could incorporate to fix replay. We most recently discussed #1, Give the Crew Chief a microphone, following a confusing double-challenge in St. Louis, and MLB has taken some steps to address points #2 (two challenges, must be immediate [MLB added a second challenge to postseason games & instituted a 30-second time limit to challenge]), #3 (give the manager a beanbag [MLB ordered managers to remain in the dugout and simply signal the umpire]), and #5 (90-second limit once headsets are put on [MLB instituted a two-minute 'guideline']), but MLB has largely ignored Tmac's fourth suggestion.
Related Post: Tmac's Teachable Moments - Let's Fix Replay (1/19/17).
Related Post: Challenge of Overturned Call Voids 30-Second Limit (9/18/19).

Umpires are told the bad news: Unreviewable.

Idea #4 is Let's replay more things, which very prominently states as its second item, "batted balls off batters," which Tmac called "some of the disasters that are not reviewable."

Well, you probably can't get more disastrous than a game-ending triple play on a clearly incorrect call and because WBSC uses instant replay rules similar to MLB's Replay Review regulations, this play is not currently reviewable.

Because of this fact, and despite the umpires' having consulted the Replay Official, the call unfortunately could not be changed because this obvious incorrect call is not subject to correction via replay review.

Gil's Call: MLB & WBSC—the World Baseball and Softball Confederation decides which teams go to the 2020 Summer Olympics in Japan through its "Road to Tokyo" qualifier tournament—please listen to Tmac and make this (and other) play reviewable.

Jeff Kellogg explains why umpires confer.

Precedent / Tangent Teachable: Also, Gil's Tangent Teachable here harkens back to an Ask the UEFL feature article from 2017 about umpires getting together for a crew conference before going to the replay headsets to review a play. Joe Maddon, for instance, criticized Jeff Kellogg when his crew had a get-together before going to replay on a fair/foul decision, saying the umpires "neutered instant replay by the way it was handled tonight."

Unfortunately for Maddon, not only does umpire manual documentation state the importance of Crew Consultation and Getting the Call Right, it spells out why the ump-chat is so vital, with or without replay: "An umpire is urged to seek help when that umpire's view is blocked or positioning prevents such umpire from seeing crucial elements of a play. An umpire is also encouraged to seek help in instances when that umpire has doubt and a partner has additional information that could lead to a proper ruling."
Related Post: Crew Consultation - Importance of the Call on the Field (6/22/17).

Back to Parma, the Italy-South Africa play sure could have benefited had an umpire seen the foul ball and been able to relay it to the rest of the crew—because MLB/WBSC still disallows the ball-hitting-batter play from being reviewed. As for MiLB/NCAA/NFHS/Little League or any game without Replay Review, post-play crew consultation here is all but required.

This Quasi-Teachable Nanosecond is brought to you by our sponsor, Umpire Placement Course.

Video as follows:

Mets End Game on Bobbled Foul Tip

When Yankees batter Brett Gardner made contact with a 3-2 fastball from Mets pitcher Edwin Diaz, NYM catcher Wilson Ramos bobbled the ball and caught it for a...game-ending foul tip strikeout? As umpire Gary Cederstrom—who became yet the latest umpire hit by a pitch or foul ball during a Mets game in 2019—signaled the final out, we review an odd looking non-fly-ball.

The Play: With two out in the 9th inning, Yankees batter Brett Gardner swung and fouled a 3-2 fastball from Mets pitcher Edwin Diaz off the glove of catcher Wilson Ramos and into the air, whereupon the ball ricocheted off Ramos' free hand and back into his glove for a game-ending catch.

Ramos catches a flying foul tip for strike 3.

The Call: This play was ruled a swinging strikeout by HP Umpire Gary Cederstrom, specifically a foul tip.

The Rule: This is indeed a foul tip. Although the Official Baseball Rules' definition of the term states, "A FOUL TIP is a batted ball that goes sharp and direct from the bat to the catcher’s hands and is legally caught. It is not a foul tip unless caught and any foul tip that is caught is a strike, and the ball is in play. It is not a catch if it is a rebound, unless the ball has first touched the catcher’s glove or hand," the most relevant rule is found in OBR 5.09(a)(2) Comment, which refers to "The batter is out when—a third strike is legally caught by the catcher."

The tail end of a foul tip in Milwaukee, 2015.

OBR 5.09(a)(2) Comment states, "If a foul tip first strikes the catcher’s glove and then goes on through and is caught by both hands against his body or protector, before the ball touches the ground, it is a strike, and if third strike, batter is out. If smothered against his body or protector, it is a catch provided the ball struck the catcher’s glove or hand first."

Analysis: The comment's hypothetical scenario is pretty much what happened here, and it's also what happened in a UEFL Case Play from 2015, when HP Umpire Ryan Blakney similarly ruled a foul tip when Diamondbacks batter Jarrod Saltalamacchia's offering deflected off Brewers catcher Martin Maldonado's glove and into the air, where it was caught on the fly by the diving catcher.
Related Post: Case Play 2015-04, The Flying Foul Tip [Solved] (6/8/15).

As we wrote in the Case Play, the main consideration is what the ball touched first after coming off the bat. If it's the hands/glove/mitt, it can be legally caught. If it's another part of the catcher's equipment or body, it cannot be legally caught.

To summarize:
Bat => Catcher's Hand, Glove, or Mitt => Caught or Smothered = FOUL TIP.
Bat => Anything Else => Caught or Smothered = FOUL BALL.

The ball's first point of contact: the mitt.

Implications: Finally, we'll discuss what this means in real life. Recall that the ball remains live during a foul tip, but is dead on a foul ball. Thus, if we had less than two outs (or less than two strikes) in New York, our baserunner could have legally stolen third base while the catcher was juggling the foul tip—and because it was a foul tip and not a legally caught foul ball (e.g., an actual fly ball that is caught in the air), there is no requirement to "tag up" or retouch a base. In such event, a quick-thinking catcher—with less than two strikes on the batter—might strategically choose to let the ball fall to the ground for the express purpose of preventing a potential stolen base.

But with two strikes, it's better to catch the ball for a strikeout | Video as follows:

Ask UEFL - Foul Bunt or Ball Fouled Away?

When does a bunt attempt give way to an inadvertent foul ball off the bat? Such was a question for HP Umpire Tony Randazzo during Wednesday's Brewers-Reds game when Cincinnati batter Michael Lorenzen fouled a two-strike pitch that, moments earlier, he had shown an intent to bunt.

Randazzo explains why it wasn't a bunt.

The Play: With none out and two on (R1, R2), Reds batter Lorenzen squared to bunt at the 1-2 offering from Brewers pitcher Taylor Williams. As the pitch approached home plate, Lorenzen, sensing the pitch would be a ball, pulled his bat back and, in doing so, the pitched ball made contact with Lorenzen's bat, sending the batted ball flying behind home plate for a foul ball.

The Call and Argument: After HP Umpire Randazzo ruled the play a foul ball (affirmed as no swing by 1B Umpire Nick Mahrley on appeal), Brewers Manager Craig Counsell argued that Lorenzen had bunted the two-strike pitch foul, while Randazzo maintained his ruling of 'simple' foul ball (no bunt attempt). Who's right?

SIDEBAR: Remember, the hands are not part of the bat. "Hands are part of the bat" is one of the worst rules myths in terms of perpetuation throughout the sport. It is vital that all umpires understand the hands are never part of the bat; they are part of the player's body. When a pitched ball contacts a player's body or hands, it is a HBP and the batter is awarded first base unless the batter is deemed to have attempted to bunt the ball, in which case it is a dead ball strike (see following section).

Analysis: Umpire Randazzo is correct. Lorenzen's foul is not a bunt attempt and, thus, not a foul bunt. The proper call here is "foul ball" and the count remains 1-2. Had Lorenzen attempted to bunt the ball and bunted foul, he would have struck out.

The Rule: The three relevant rules are the definitions of Bunt, Foul, and Strike.

The Official Baseball Rules states that, "A BUNT is a batted ball not swung at, but intentionally met with the bat and tapped slowly within the infield."

The relevant portion of the rulebook's foul ball definition is, "A FOUL BALL is a batted ball that settles on foul territory between home and first base," while the two relevant provisions of the strike rule are as follows:

(c) Is fouled by the batter when he has less than two strikes;
(d) Is bunted foul.

If the batter pulls the bat back, it is not a bunt.

Conclusion: If you missed it, the answer to this play lies in the definition of BUNT: the ball must be met with the bat intentionally. Because Lorenzen was in the act of pulling the bat back when it struck the ball, the contact was not intentional, which means, by rule, it cannot be considered a bunt attempt.

Related Ejection: In 2012, 1B Umpire Jim Joyce ejected Astros Manager Brad Mills for arguing a very similar play when Pirates batter Clint Barmes fouled a 1-2 pitch while attempting to pull the bat back after initially squaring to bunt. In ruling the play a foul ball, the crew determined that Barmes did not intentionally meet the ball with his bat.
Related Post: Ejection 026: Jim Joyce (1) (5/11/12).
Related Video: HP Umpire James Hoye and Joyce crew rule play a foul ball; Joyce ejects Mills.

Alternate Thought: Another way to think of the issue of foul bunt vs non-bunt foul ball is to consider the play from an aspect of, "If the ball hadn't touched the bat, would this have been strike three based on the batter's attempt to strike at the ball?" If the answer is yes, you have a bunt. If the answer is no, it is not a bunt.

To recap, a foul bunt requires intent. A foul ball does not require intent.

Insult to Injury: After Counsell's unsuccessful campaign for a strikeout, Lorenzen hit a home run.

Video as follows:

Wild Walk-Off - Analysis of 6 Rules for 1 Play in Houston

The final play of Houston's walk-off victory over Oakland Tuesday featured an overcharged bouncing ball and at least six rules situations for HP Umpire David Rackley to quickly consider as A's catcher Jonathan Lucroy and Astros batter Alex Bregman danced around home plate before Lucroy finally threw the baseball wildly into right field, plating Houston's game-winning run. This article and video analyzes each individual phase of Tuesday's final play in Houston, as well as the plate umpire's responsibilities and reactions.

Rackley's Rapid Response™ passed the test.

The Play: With one out and two on (R1, R2), Astros batter Alex Bregman hit a ground ball softly to the right of home plate, where A's catcher Jonathan Lucroy fielded the ball in fair territory, attempted to tag batter-runner Bregman while fumbling and dropping the ball, which bounced off of HP Umpire David Rackley, before Lucroy retrieved the loose ball and threw it off of batter-runner Bregman's helmet, past first baseman Mark Canha, and down the right field line, allowing Astros baserunner R2 Kyle Tucker to score the game-winning run, affirmed following an A's challenge for Lucroy's attempted tag of Bregman.

Analysis: There is a lot to unpack here, so let's go step by step, rule by rule, and solve this wild play.

Call #1: Fair or Foul: This complex play begins, simply, when batter Bregman hits A's pitcher Blake Treinen's 1-2 pitch, which bounces in foul territory before rolling back into fair territory, whereupon catcher Lucroy makes initial contact with the baseball.

This ball was fielded in fair territory.

Rule #1: Amongst other criteria, and relevant to the play at hand, "A FOUL BALL is a batted ball that settles on foul territory between home and first base" while "A FAIR BALL is a batted ball that, while on or over fair territory touches the person of an umpire or player."

Analysis, Call #1: Because Lucroy makes first contact with the baseball while it is over fair territory, this is a fair ball.

Call #2: Interference or Incidental: As Lucroy attempts to field the ball, batter Bregman considers running to first base, and moves from his position in the right-handed batter's box toward first base. Seeing that Lucroy is about to field the ball, Bregman stops to avoid the imminent tag.

The batter did not interfere with the fielder.

Rule #2: The relevant portion of interference rule 6.01(a)(10) states the batter or runner is out when—"He fails to avoid a fielder who is attempting to field a batted ball," whereas, "Offensive interference is an act by the team at bat which interferes with, obstructs, impedes, hinders or confuses any fielder attempting to make a play."

QOC, Call #2: Bregman does not impede Lucroy's ability to field the batted ball, which means he has not interfered with the fielder's attempt to field a batted ball.

Call #3: Out of Base Path or Legal: As Lucroy attempts to tag Bregman, Bregman jumps backward, toward home plate, in an effort to avoid the tag.

The runner did not illegally exit his path.

Rule #3: According to retiring-a-runner rule 5.09(b)(1), a runner is out when—"He runs more than three feet away from his base path to avoid being tagged unless his action is to avoid interference with a fielder fielding a batted ball."

QOC, Call #3: The batted ball exemption doesn't apply here, as Lucroy has already fielded the ball, leaving us to consider whether Bregman is three+ feet out of his path, established at the time of the tag attempt. It appears Bregman never quite arrived at (returned to) home plate, which also renders moot an MLB Umpire Manual interpretation regarding a batter-runner who retreats to home ("In situations where the batter-runner gets in a rundown between first and home, if the batter-runner retreats and reaches home plate, the batter-runner shall be declared out").

Call #4: Umpire Interference or Play On: As Lucroy fumbled the ball and HP Umpire Rackley stepped in for a closer look, the ball bounced off Rackley and settled in the dirt.

HP Umpire Rackley did not interfere.

Rule #4: Umpire interference occurs under very specific circumstances, which are presented in 6.01(f) [5.06(c)(2), delineating when the ball is dead, also describes that which is depicted by 6.01(f)(1)]: "Umpire’s interference occurs (1) when a plate umpire hinders, impedes or prevents a catcher’s throw attempting to prevent a stolen base or retire a runner on a pick-off play; or (2) when a fair ball touches an umpire on fair territory before passing a fielder. Umpire interference may also occur when an umpire interferes with a catcher returning the ball to the pitcher." To put it even more bluntly, "If a thrown ball accidentally touches a base coach, or a pitched or thrown ball touches an umpire, the ball is alive and in play."

QOC, Call #4: There is no call to make here, as a fumbled ball bouncing off of an umpire's chest is not one of the scenarios depicted nor covered by the umpire interference rule.

Call #5: Obstruction or Legal: As catcher Lucroy fumbles the ball into the left-handed batter's box, batter-runner Bregman reverses his retreat and sprints toward first base, avoiding the catcher in the process.

The runner did not obstruct the fielder.

Rule #5: The definition of terms holds that "OBSTRUCTION is the act of a fielder who, while not in possession of the ball and not in the act of fielding the ball, impedes the progress of any runner."

QOC, Call #5: It appears batter-runner Bregman was not impeded by catcher Lucroy, so no obstruction occurred. Had this been obstruction, it would be an instance of OBS Type 2 (Type B), as in rule 6.01(h)(2), because Lucroy had already fumbled the ball away after fielding it and making a play on the runner: "If no play is being made on the obstructed runner, the play shall proceed until no further action is possible."

Call #6: Runner's Lane Interference or Nothing: Lest we give up too quickly, the final aspect of this play concerns whether Bregman legally ran to first base as catcher Lucroy threw to first baseman Canha.

The runner did not commit RLI (INT).

Rule #6: Rule 5.09(a)(11) allows the batter-runner to be declared out if, "In running the last half of the distance from home base to first base, while the ball is being fielded to first base, he runs outside (to the right of) the three-foot line, or inside (to the left of) the foul line, and in the umpire’s judgment in so doing interferes with the fielder taking the throw at first base."

QOC, Call #6: Replays indicate Bregman's running lane adventure was entirely legal; he entered the lane on or between the two chalk lines and remained in the lane until the ball was already up the right field line, well past the infield.

At least six rules were involved in just one play Tuesday.

BONUS Call #7: Obstruction (on F3) or Nothing: Once Lucroy's throw eluded first baseman Canha, we were left with a first baseman standing in front of the base and a batter-runner who had to change his path in order to avoid the first baseman and touch first base. As Call #5 states above, if first baseman Canha impeded batter-runner Bregman from timely touching his base, the umpires would be within their rights to allow play to proceed through its conclusion and (let's assume Bregman was thrown out at second base prior to the winning run scoring...with two outs) make whatever call or runner placement that, in their judgment, would nullify the act of obstruction.

Mechanically Speaking: Rackley employs two "safe" mechanics here. The first signifies "no tag," "no interference," "not out of the base path," and "no obstruction"—essentially saying "everything that just happened is legal"—and the final safe call pertains to the runner's lane interference no-call, all of it the proper decision. Hunter Wendelstedt is on this crew and you sure hope he'll add Rackley's play to his curriculum at Umpire School for what to do when a crazy play finds you.

Postscript: Perhaps the most obvious call isn't even included in the aforementioned analysis—whether or not the catcher tagged the runner! As Replay Review confirmed, following an A's challenge, Lucroy did not tag Bregman—that is to say, Lucroy did not "touch a runner with the ball, or with his hand or glove holding the ball (not including hanging laces alone), while holding the ball securely and firmly in his hand or glove" [Definition of Terms: TAG]—but it just goes to show you what type of a call an umpire analyst can take for granted when confronted with no less than six additional considerations, all within a mere matter of seconds. As for HP Umpire Rackley, score that a QOC of Correct, multiplied by at least six.

Video as follows:

MLB Ejection 062 - Joe West (1; Andy Green)

HP Umpire Joe West ejected Padres Manager Andy Green (foul ball call; QOCY) in the bottom of the 4th inning of the Padres-Braves game. With two out and none on, Braves batter Ozzie Albies attempted to strike a 1-2 slider from Padres pitcher Clayton Richard for a called foul ball. Replays indicate Albies' bat made contact with the baseball, which in turn bounced into the dirt before being fumbled by Padres catcher Raffy Lopez, the call was correct. Ruling was reviewed and affirmed by the UEFL Appeals Board (7-0-2), the call was correct. At the time of the ejection, the game was tied, 2-2. The Padres ultimately won the contest, 9-3.

This is Joe West (22)'s first ejection of 2018.
Joe West now has 4 points in the UEFL Standings (0 Prev + 2 MLB + 2 Correct Call = 4).
Crew Chief Joe West now has -3 points in Crew Division (-4 Previous + 1 Correct Call = -3).

This is the 62nd ejection report of the 2018 MLB regular season.
This is the 26th Manager ejection of 2018.
This is San Diego's 5th ejection of 2018, 1st in the NL West (SD 5; ARI, SF 4; COL 3; LAD 2).
This is Andy Green's 2nd ejection of 2018, 1st since April 9 (Brian Gorman; QOC = Y [Replay Review]).
This is Joe West's first ejection since August 31, 2017 (AJ Hinch; QOC = Y-C [Batter's Interference]).

Wrap: San Diego Padres vs. Atlanta Braves, 6/15/18 | Video as follows:

Yadier Molina's Foul Tip - Hands First, Body Last

Cardinals catcher Yadier Molina caught a foul tip in unorthodox fashion when a batted ball came to rest between his right thigh and torso as HP Umpire Chris Segal declared the play a legal catch and strikeout, explaining to Padres Manager Andy Green why the odd rebound resulted in strike three.

Video: A foul tip vs a foul or lodged ball.

This play highlights the importance of knowing Official Baseball Rule 5.09(a)(2) as well as the Definition of Terms regarding a foul tip and catch. Not only is the batter's status as a strikeout victim (if a foul tip) or being able to continue the at-bat (if a foul ball) in question, if there were runners on base, stolen bases or other advancement could come into question (if a foul tip, the ball is live and any steals would be valid; if a foul ball, the ball is dead and any steals would not count).

The Play: With two strikes, the batter swings at the pitched ball, his bat making contact with the ball and sending it sharply and directly toward the catcher, whose hand/glove/mitt either (A) does, or (B) does not, touch the ball, after which it comes to rest trapped between the catcher's thigh and torso. The catcher slowly stands up and retrieves the ball with his bare hand; the ball never touches the ground. Is this a foul tip or a foul ball?

Answer: In (A), it is a foul tip and results in the third strike on the batter; the batter is out and the ball remains live, meaning any stolen bases or other runner movement would stand. In (B), it is a foul ball; the batter remains at bat and the ball is dead, nullifying any stolen bases or other runner advancement.
Related Post: An Unconventional Foul Tip in the Big Apple (4/10/17).

Rule 5.09(a)(2): This rule simply states that a batter is out when the third strike is legally caught by the catcher. The important portion of this rule relative to the Molina foul tip play is in the rule's comment:

If a foul tip first strikes the catcher’s glove and then goes on through and is caught by both hands against his body or protector, before the ball touches the ground, it is a strike, and if third strike, batter is out. If smothered against his body or protector, it is a catch provided the ball struck the catcher’s glove or hand first.

This is an example of a foul ball.

The Definition of Terms resembles Rule 5.09(a)(2) Comment, and states that, "A FOUL TIP is a batted ball that goes sharp and direct from the bat to the catcher’s hands and is legally caught."

For instance, the accompanying image of a batted ball that strikes the catcher's mask immediately after it is hit by the bat would be an example of a foul ball. Though this particular play ended up as a lodged ball (the ball was stuck in the mask), had the ball fallen out of the mask and into the catcher's hand, it would still be deemed a foul ball.

Recall that a catch "is the act of a fielder in getting secure possession in his hand or glove of a ball in flight and firmly holding it." A fielder may smother the ball against his body and complete the catch simply by holding the ball in his hand or glove, but the fielder may not use a cap, chest protector, mask, pocket, or other item not natural to the fielder's person in order to complete the catch. It is similarly not a legal catch if at any time prior to secure possession the batted ball touches the ground, an umpire, or an opponent (it may touch a teammate).

To reiterate, a foul tip requires the batted ball
a) Go sharply and directly from the bat to the catcher's hands;
b) Touch the catcher's hands, mitt, or glove;
c) Be legally caught.

Video as follows:

Ask the UEFL - Fletcher, Phantom Foul & Plate Blocking

New York defeated Washington on a contested foul ball no-call and dramatic game-ending play at the plate, confirmed after a Nationals-prompted Replay Review regarding baseball's home plate collision rule. After the game, Nats Manager Dusty Baker—along with fans of the team, most likely—wasn't exactly thrilled with the 9th inning's outcome. As suggested by a viewer via our Ask the UEFL feature, let's take a look at the plays.

Degree of descent on two phases of swing.

Strike Three Swinging (2nd Out): With one out and none on, Nationals batter Alejandro De Aza attempted to strike a 0-2 slider from Mets pitcher AJ Ramos for an uncaught third strike.
The Rule: OBR 5.09(a)(2) and (10) specify when the batter is out, relative to this play: "(2) A third strike is legally caught by the catcher" and "(10) After a third strike or after he hits a fair ball, he or first base is tagged before he touches first base."
Definition of Terms [Strike] tells us what is and what is not a strike: a) struck at and missed, b) passes through strike zone, c) fouled with less than two strikes, d) bunted foul (with any count), e) touches batter as he strikes it, f) touches batter in the strike zone (in flight), g) a foul tip.
A FOUL TIP is a batted ball that goes sharp and direct from the bat to the catcher’s hands and is legally caught. It is not a foul tip unless caught and any foul tip that is caught is a strike, and the ball is in play. It is not a catch if it is a rebound, unless the ball has first touched the catcher’s glove or hand.

Analysis, Uncaught Third Strike: The quality of correctness here is inconclusive. First and foremost, let's (yet again) address the "foul tip" terminology so often employed by players, coaches, fans, and broadcasters. Simply put, the De Aza play does not describe a foul tip: by rule, a foul tip is always caught by the catcher. Assuming the ball touched the bat, it cannot possibly be a foul tip if it is not caught by the catcher. For more information on the difference between foul balls and foul tips, refer to the following 2015 Case Play involving plate umpire Ryan Blakney, or Tony Randazzo's bobbled foul tip at Citi Field from April:
Related Post: Case Play 2015-04, The Flying Foul Tip [Solved] (6/8/15).
Related Post: An Unconventional Foul Tip in the Big Apple (4/10/17).

That said, Washington was adamant two different sounds were heard, which ordinarily can help an umpire determine if the ball hit something before reaching the catcher. Unfortunately, for this play, the something could have been De Aza's bat, or it could have been the dirt behind home plate. Visual analysis of the play indicates the ball's downslope angle was approximately -12 degrees prior to reaching the location where De Aza's bat could have potentially contacted the baseball, and was approximately -13 degrees after this location. Because the pitch was a slider, some deviation in glideslope may be expected (due to spin-rate, for instance), which makes this rather statistically insignificant difference in angles somewhat unreliable in determining whether or not the ball hit the bat. As such, even if this play was reviewable, I'd surmise the call would "stand," similar to how many hit-by-pitch vs no-HBP reviews end up with a "call stands" outcome | Video via "Read More" (below).

HP Collision Violation No-Call (3rd Out): With two out and one on (R1), Nationals batter Daniel Murphy hit a ground ball to Mets center fielder Juan Lagares, who threw to second baseman Asdrubal Cabrera to catcher Travis d'Arnaud as Nationals baserunner Edwin Jackson arrived at home plate. Initially ruled out by HP Umpire Fletcher, the call was confirmed as an out (no HP collision/plate blocking violation) following a Manager's Challenge.

Diagram of legal catcher positioning.

The Rule: OBR 6.01(i)(2) states, in part, "Unless the catcher is in possession of the ball, the catcher cannot block the pathway of the runner as he is attempting to score...Not withstanding the above, it shall not be considered a violation of this Rule 6.01(i)(2) (Rule 7.13(2)) if the catcher blocks the pathway of the runner in a legitimate attempt to field the throw (e.g., in reaction to the direction, trajectory or the hop of the incoming throw, or in reaction to a throw that originates from a pitcher or drawn-in infielder)."
Related Post: Anatomy of a Rule 7.13 HP Collision Review, SEA-OAK (4/11/15).

C d'Arnaud exhibits legal positioning in DC.

Analysis, HP Collision: This call is correct on all accounts—the runner is tagged prior to his arrival at home plate, and the catcher's positioning is legal; there is no illegal block of home plate. The tag is self-explanatory, and as for Rule 6.01(i)(2), refer to the attached diagram. As indicated by the white circle, catcher d'Arnaud is positioned entirely in fair territory (on or to the inside/right of the foul line) in the final moment before he will receive Cabrera's throw. This is a legal position as baserunner Jackson has the entire foul-facing edge of home plate at his disposal, similar to our "gold standard" of catcher legality as indicated in the above image featuring Mariners catcher Jesus Sucre and A's runner Josh Phegley in Oakland (click here for more detail about that play).

F2 is in possession prior to runner's arrival.

Finally, based on EVP Joe Torre's September 2014 clarification of the home plate collision rule, "If the runner would have been called out notwithstanding the catcher's improper positioning in front of the plate, the out call will stand." We know that d'Arnaud was legal (e.g., the call was confirmed), but assume he wasn't. According to Torre's statement, an illegally positioned catcher will not be called for illegal positioning if—to put it bluntly—the ball beats the runner. As indicated by the attached image, F2 d'Arnaud received the throw prior to R1 Jackson's arrival; thus, even if d'Arnaud was improperly positioned in front of home plate (which really means blocking off the runner's access to the shortest edge of home plate that is parallel to the inner batter box line), the out call would stand based on the rationale that F2's illegal position did not by itself prevent the runner from scoring (the fact that F2 caught the ball before R1 arrived at home plate is primarily what prevented the runner from scoring).

Catcher is legal well before the runner arrives.

To really drive the point home, a catcher will only be called for the Rule 6.01(i)(2) violation if his illegal positioning "holds up" or clearly prevents a runner from scoring. If the catcher gains possession of the ball at any point prior to the runner reaching the catcher's position in front of home plate, there is no violation of Rule 6.01(i)(2). Once the catcher catches the ball, he no longer can be considered as illegally blocking the plate.
Related Post: MLB Issues Rule 7.13 Plate Blocking Clarification (9/10/14).

Wrap: New York Mets vs. Washington Nationals (Game 1 of DH), 8/27/17 | Video as follows:

Case Play 2015-04, The Flying Foul Tip [Solved]

Case Play time! When is a foul tip a foul ball? A catch an out? A dead ball alive? First year MiLB call-up umpire Ryan Blakney witnessed the case of the flying foul tip Sunday during the eighth inning of a tied D'Backs-Brewers game at Miller Park. With none out and none on, Diamondbacks batter Jarrod Saltalamacchia faced a 2-2 fastball from Brewers pitcher Jeremy Jeffress. With the 95-mph heater cruising over the heart of home plate, Saltalamacchia's swing made slight contact with the ball, propelling it directly toward BrewCrew catcher Martin Maldonado's glove.

Replays indicate the ball deflected off Saltalamacchia's bat directly onto the top of Maldonado's glove, popping up into the air behind the right-handed batter's box where it was caught on the fly by the diving catcher and declared a foul tip by plate umpire Blakney.

Case Play Question 2015-04: First, was Blakney's call correct? Was this a caught foul tip for strike three or was this a caught foul ball for an air out? This is an important distinction, for had there been a baserunner attempting to steal during this play, he may have been safe at second on a foul tip, but easily doubled up at first base on a caught foul or fly. Second, what would the call have been had the ball deflected not off Maldonado's glove, but his chest protector or helmet instead (and subsequently been caught on the fly in similar diving fashion) - out or safe? Were the broadcasters correct in their description? What rule(s) covers this?

Case Play Answer 2015-04: 1) Yes, Blakney was correct and the batter was out on three strikes. Rule 5.09(a)(2) [OBR 2015 Rule 6.05(b)] specifies this play was a foul tip out (batter is out when "a third strike is legally caught by the catcher").

Rule 2.00 (Foul Tip) [OBR 2015 Definition of Foul Tip]: "A FOUL TIP is a batted ball that goes sharp and direct from the bat to the catcher’s hands and is legally caught. It is not a foul tip unless caught and any foul tip that is caught is a strike, and the ball is in play. It is not a catch if it is a rebound, unless the ball has first touched the catcher’s glove or hand."

Replays indicate Maldonado's catch was a rebound that first touched F2's glove/hand, meaning this was a foul tip and the batter is out.

2) Had the ball first contacted Maldonado's equipment (e.g., so the sequence would be BAT=>CHEST PROTECTOR=>GLOVE as opposed to BAT=>GLOVE=>GLOVE), the proper ruling would be a foul ball. If first contact was glove or hand, the proper ruling would be foul tip, if caught (foul ball if dropped). The comment for Rule 5.09(a)(2) [6.05(b)] covers this: "If a foul tip first strikes the catcher’s glove and then goes on through and is caught by both hands against his body or protector, before the ball touches the ground, it is a strike, and if third strike, batter is out. If smothered against his body or protector, it is a catch provided the ball struck the catcher’s glove or hand first."

Thanks to all participants in this discussion; two UEFL CP points are headed your way.

Video: Acrobatics behind home plate result in an out and highlight reel catch in Milwaukee (MIL)