All Hokie, All the Time. Period. Presented by First Bank & Trust Company

HolidayInnHokie
Joined: 11/22/2004
Posts: 11,175
Likes: 16,005
Subscriber

No, bad call. Where could he slide? Into the catcher’s chest?

That would just transfer the risk of injury from the catcher to the runner. Or, even a clean side could end up getting the catcher cleated (unintentionally). The catcher was in the wrong by totally walling off the plate. In that case, he deserves whatever he gets. There was ZERO place for the runner to slide that was still within the baseline with a viable path to the plate. Also, not sure how the contact that was made could be considered “malicious.” It was intentional, and forcible, but it wasn’t malicious. The runner crossed his arms and went straight into the midsection of the catcher. Had he had an elbow out, or leaned his entire shoulder into the catcher, especially up top, then you might consider it malicious. Maybe. This was a truly awful call. If the ump thought it was malicious in real time, he would’ve called it as such. Hate seeing replay unnecessarily getting involved and then changing the game (as well as possibly today’s game since the ejection carries over). This is what the NCAA has become…..what next, no tackling in football?
Posted: 05/31/2025 at 04:12 PM ET
(In response to this post by Virtual Hokie)

Thread Replies (6)

Full Thread →
Interesting play in the Oregon game last night
VTChip 05/31/25 11:01 AM ET
No attempt to slide and trucking the catcher will get you ejected.
Virtual Hokie 05/31/25 03:27 PM ET
No, bad call. Where could he slide? Into the catcher’s chest?
HolidayInnHokie 05/31/25 04:12 PM ET
NCAA Baseball Rule 8-7 - collision rule.
Virtual Hokie 05/31/25 05:13 PM ET
The runner saw the ball
Virtual Hokie 05/31/25 05:18 PM ET
Tough call at that moment
Hockeydad 05/31/25 02:23 PM ET
she?**
squarerootofone 05/31/25 04:33 PM ET