Orioles-Blue Jays: He Wasn’t “Out of the Base Line.” You Don’t Know the Rule.

Gunnar Henderson of the Orioles protesting an umpire "base line" decision he didn't like against the Blue Jays

Photo by Kevin Sousa/Getty Images

June 9, 2026

Orioles-Blue Jays: No, He Wasn’t “Out of the Baseline.” You Simply Don’t Know the Rule.

There are bad takes. There are uninformed takes. And then there are “out of the baseline” takes like the ones seen from Sunday’s game between the Baltimore Orioles and Toronto Blue Jays, which exist in a special category of their own. These are a swirling vortex of confidence, ignorance, and absolute refusal to read the rulebook that governs the sport they claim to love.

Let’s set the scene.

Rule 6.01 (b) Fielder Right of Way

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. If a member of the team at bat (other than a runner) hinders a fielder’s attempt to catch or field a batted ball, the ball is dead, the batter is declared out, and all runners return to the bases occupied at the time of the pitch. If a member of the team at bat (other than a runner) hinders a fielder’s attempt to field a thrown ball, the ball is dead, the runner on whom the play is being made shall be declared out and all runners return to the last legally occupied base at the time of the interference.

The Play

Runners on the corners, one out. Blue Jays catcher Brandon Valenzuela hits a slow bouncer up the middle. Fielder charging — in this case, Orioles shortstop Gunnar Henderson. Runner (Ernie Clement) veers wide — as required by Rule 6.01(b) — to avoid interfering with a fielder fielding a batted ball as well as his expected throw to first.

This is not controversial. This is not borderline. This is not “interpretation.” This is literally the rule.

But then Henderson, realizing he has no play on Clement, does a half‑hearted push tag (glove push of maybe two inches?) at empty air — a tag attempt so symbolic it might as well have been performance art. The runner is already at least five feet away. The “attempt” happens after the avoidance. And the throw to first retires the batter‑runner.

Clement reaches second safely. Legally. Correctly.

And then… the meltdown begins.

5.09 (b) Retiring a Runner

Any runner is out when:

(1) 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. A runner’s base path is established when the tag attempt occurs and is a straight line from the runner to the base he is attempting to reach safely; (emphasis added)

Suddenly, half the internet becomes self‑appointed base‑path experts. They are armed with nothing but confidence and a complete misunderstanding of Rule 5.09(b)(1) — the one that explicitly says a runner may deviate more than three feet to avoid a fielder fielding a batted ball, not to mention a base path is established when a tag attempt occurs and is a straight line from where the runner is at that specific point to the base he is attempting to reach safely.

You know. Exactly what happened.

The Meltdown Based on Myth, Not Fact

But no. Why let the rulebook get in the way of a good tantrum?

We got:

“He’s out of the base line!”
“He can’t run that far wide!”
“Umpires don’t know the rules!”
“He was ALREADY out of the base path!”

And my personal favorite: “This is a missed call and the league needs to explain it!”

They did explain it. You simply didn’t like the explanation because it required reading.

Here’s the truth fans don’t want to hear: the base path is not a chalk line. It is not the imaginary line between bases. It is not whatever you think it is. It is a straight line from the runner to the base AT THE MOMENT A TAG ATTEMPT OCCURS.

The tag “attempt” here — and “attempt” is being generous — wasn’t real. It wasn’t close, nor was it directed at the runner. In fact, it happened after the runner had already avoided the fielder. Therefore, it established the base path where the runner already was — five feet away. And remember — at that point, the runner could have gone another three feet to his right if he wanted, even though he didn’t.

This is Umpiring 101. This is Rulebook 101. This is “anyone who has ever umpired a baseball game above age 12 and has had to pass a rules test knows this” territory.

Spreading the False Narrative

But instead of learning, fans doubled down. And tripled down. They demanded the universe bend to their misunderstanding. So did the Orioles and their television color analyst on MASN Sunday, retired infielder Brian Roberts. Here was his incorrect claim as the replay started: “The rule is, you gotta keep it somewhat in the lane. Right? If you’re going to second base, you gotta keep somewhat in the lane, and I understand. Ernie, you wanna try to avoid getting tagged.”

Play-by-play commentator Ben Wagner added, “That is a frustrating result on what should have been two.” Well, yeah, it is, and yeah, it should have been two…but not for the reasons they were implying. The call was correct.

Henderson himself added fuel to the fire when he said, “I’m not about to chase him into right field when I’m trying to turn a double play.” Okay, then pivot and throw to second for the force. Sorry, but that’s what had to happen here to get him out.

Even worse? Google’s AI bot — Gemini — hallucinated a “controversial missed call,” misquoted the umpire, and confidently explained the rule incorrectly — which is basically the perfect metaphor for the discourse. A machine that doesn’t know the rulebook confidently telling millions of people the umpires were wrong.

Sound familiar?

So here’s the bottom line:

The call was correct. The runner was legal. The rulebook is clear. And the only thing “out of line” was the reaction from people who would rather invent rules than read them.

If you want to argue about baseball rules, great. Start by learning them.