Brandon Lowe Ejected After ABS Challenge Denied; Umpire ID Disputed

brandon lowe was ejected in MLB Ejection 040 after an ABS challenge was denied and ruled illegal dugout assistance; Close Call Sports notes a discrepancy over the umpire.

By
Chris Lawson
Editor
Sports writer with 9 years on the NFL and NBA beat. Sideline reporter and credentialed press member at three Super Bowls.
14 Views
3 Min Read
0 Comments
Brandon Lowe Ejected After ABS Challenge Denied; Umpire ID Disputed

logged (4; ) — recording the ejection of Brandon Lowe after an was denied and the play was ruled illegal dugout assistance, per an alternate link cited with the entry.

The entry pairs two concrete items: the headline-style label that names Jordan Baker and the numeric markers 040 and 4, and an alternate-link summary saying that umpire denied an ABS challenge, ruled the action illegal dugout assistance, and that Lowe was ejected. The site’s notation leaves no doubt that Lowe’s removal from the game is the immediate, reportable event.

Close Call Sports is explicit about its mission: the site objectively tracks and analyzes close and controversial calls in sport. Its ejection log — which grew out of ’s MLB Umpire Ejection Fantasy League — records these incidents with terse labels and linked write-ups instead of narrative game coverage, which is how MLB Ejection 040 appears in its database.

The significance is narrow but direct: an ABS challenge was denied and a ruling of illegal dugout assistance was recorded, and Lowe was ejected as the result. Those are the operational facts logged alongside the entry number 040 and the parenthetical “,” which the site places next to Jordan Baker in the title. That string of identifiers is the weight of the report — the measurable elements that mark this as a documented umpire ejection rather than a rumor.

There is a clear friction in the record. The headline-style title identifies Jordan Baker while the alternate-link text attributes the decisive action — denying the ABS challenge and ruling illegal dugout assistance — to Tosi. Both cannot be the same ruling simultaneously; the log, as published, does not reconcile which umpire made the ruling that preceded Lowe’s ejection. That discrepancy is the single concrete inconsistency in an otherwise minimalist entry.

What the Close Call Sports entry does not deliver is the specific conduct that triggered the ejection. The site records the result — the denial of an ABS challenge, a call of illegal dugout assistance and Lowe’s ejection — but it does not describe what Lowe said or did at that moment, or whether the ejection followed an on-field exchange, a dugout communication, or another action. The absence of that detail is material: it leaves the sequence between the ruling and the ejection opaque.

For readers tracking discipline, replay review, or official reassignment of umpire responsibilities, the next step is unresolved. Close Call Sports has entered the incident into its ejection ledger, but the log entry does not report any follow-up from league officials, nor does it say whether the ruling or the ejection will prompt an internal review. The most consequential unanswered question now is narrow and specific: which umpire made the ABS denial and illegal dugout assistance ruling — Jordan Baker as named in the title, or Tosi as named in the alternate link — and what exact actions by Lowe led to his ejection?

The record published by Close Call Sports establishes the basic event — Lowe’s ejection tied to an ABS-challenge denial and an illegal-dugout-assistance ruling — and it highlights a reporting gap that matters to anyone who follows umpire decisions and postgame accountability. Until the league or the officiating crew clarifies who issued the ruling and details what prompted the ejection, MLB Ejection 040 remains a logged fact with an unresolved core: the immediate cause of Brandon Lowe’s removal.

Share
Editor

Sports writer with 9 years on the NFL and NBA beat. Sideline reporter and credentialed press member at three Super Bowls.