Recommended Posts

The defender has the right of way when fielding the ball. The runner is out if he impedes a fielder's progress while fielding a ball. The defender doesn't have to move out of the runner's way while receiving the ball.

Based on the rule, though, that's incorrect, as it states: The catcher, without the ball in his possession, has no right to block the pathway of the runner attempting to score.

The question is the definition of 'fielding' My view, it's actively retrieving the ball...performing an action...not waiting for it to be relayed to you.

Based on the rule, though, that's incorrect, as it states: The catcher, without the ball in his possession, has no right to block the pathway of the runner attempting to score.

The question is the definition of 'fielding' My view, it's actively retrieving the ball...performing an action...not waiting for it to be relayed to you.

You're correct. That rule relates to someone actually fielding a batted ball, it has nothing to do with a player waiting for the ball to be relayed to them. This means if a catcher is blocking the plate without the ball or the ball in flight within a reasonable distance , then you could possibly have obstruction and the runner awarded home. AJ did nothing wrong in railroading the catcher, the catcher was in the way, it's part of the game.

The defender has the right of way when fielding the ball. The runner is out if he impedes a fielder's progress while fielding a ball. The defender doesn't have to move out of the runner's way while receiving the ball.

Yes, that is correct, but Barrett wasn't fielding the ball. Barrett was standing in front of the plate waiting for the ball, impeding AJ from reaching home plate, which doesn't apply to the "fielding" rule.

The catcher would never be called for interference if he was just standing there, because the runner can easily go around him. If the catcher is waiting for the thrown ball, and the runner barrels into him, it would be runner's interference, for interfering with the play. Only when the catcher has the ball can the runner and catcher clash legally, and even then it needs to be clean. If the runner comes in with his arm raised to decapitate the catcher, he is in the wrong.

OK, I just watched the play. That was total bull**** of him to knock down the catcher like that, because the plate was not blocked. He could have slid, he could have dodged and still made the tag, but instead he chose to flatten Barrett.

:laugh: i knew you would come around

The catcher would never be called for interference if he was just standing there, because the runner can easily go around him. If the catcher is waiting for the thrown ball, and the runner barrels into him, it would be runner's interference, for interfering with the play. Only when the catcher has the ball can the runner and catcher clash legally, and even then it needs to be clean. If the runner comes in with his arm raised to decapitate the catcher, he is in the wrong.

I disagree, that is not how the rule is interpreted. If the catcher was trying to field the ball, say in the case of a bunt, then yes you have runner's interference, but a thrown ball is a whole other situation. You can't call runner's interference on a runner for barreling into a catcher that is blocking or near the plate under MLB/OBR rules. Sure there are situations where the barreling of the catcher isn't the right thing to do because the runner could have gotten around him, but still you don't have interference. As for a runner coming in with his arm raised to decapitate the catcher, normaly that is handled by MLB itself not the umpires on the field, because I don't believe there is anything in OBR that talks about what constitutes what a legal barreling of the catcher is, thus there is nothing the umps can do.

Now under Federation (high school) and NCAA rules, which are the two levels I umpire, barreling of the catcher is never allowed regardless of the situation. If it happens the runner is out and ejected.

For those of you that really want to learn the rules, grab a case book of the accepted rules interpretations. Before a season starts I never just read the rule book, you can get so much more out of a book of interpretations.

OBR:

http://www.gerrydavis.com/Merchant2/mercha...gory_Code=PRINT

High school:

http://www.nfhs.com/index.asp?cmd=showcategory&param_0=61

NCAA:

http://www.ncaa.org/wps/portal/!ut/p/k...ball/index.html

And FYI:

defense causes it: it's called obstruction

offense causes it: it's called interference

Edited by musicman

Interesting note...AJ didn't get suspended at all. :p

He should have, although his fine may even it out. I don't have a problem with him running the catcher down, but I do have a problem with him going in with forearm out, slapping the plate, and then he started walking toward Barrett. I can accept Barrett's explanation that he was a bit dazed after being drilled, and when he saw AJ coming his direction, he did something about it.

I wasn't expecting him to be suspended. However, I was expecting a minor fine.

He got a $2000 fine didn't he?

And personally to me it looked more like a shoulder-to-shoulder hit than a forearm to the face. IMO all A.J. did that could be questionable was the pumping up the crowd. I'm sure they needed that lol.

He got a $2000 fine didn't he?

And personally to me it looked more like a shoulder-to-shoulder hit than a forearm to the face. IMO all A.J. did that could be questionable was the pumping up the crowd. I'm sure they needed that lol.

According to the report, pumping up the crowd is exactly what AJ was fined for. It seems that the only people who are against AJ in all this are Cubs' fans. Both Dusty Baker and Barret were quoted as saying it was a clean play at the plate.

Well, Barrett has appealed the suspension and will remain playing until his appeal is heard. I don't understand why he appealed. He is clearly guilty for what he did and should take the consequences like a man.

All players appeal their suspensions. He's trying to get the number of games reduced.

All players appeal their suspensions. He's trying to get the number of games reduced.

Barrett is especially concerned with playing during this "critical juncture" for my beloved Cubbies. This team would sink (further) if Barrett wasn't playing. Hopefully, with this appeal, he can get his suspension reduced to 8 games.

I disagree, that is not how the rule is interpreted. If the catcher was trying to field the ball, say in the case of a bunt, then yes you have runner's interference, but a thrown ball is a whole other situation. You can't call runner's interference on a runner for barreling into a catcher that is blocking or near the plate under MLB/OBR rules.

Sure you can, because it was an unnecessary hit on the catcher. Barrett was in no way blocking the plate. I think he even had both feet on one side of the foul line.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Windows 11 gets graphics and Firewall fixes in build 26100.4767 by Taras Buria Following the new Windows 11 Canary build released for Windows Insiders earlier today, Microsoft pushed a small update for those testing preview builds in the Release Preview Channel. Build 26100.4767 (KB5062663) is out with a few additional fixes for build 26100.4762, which arrived one week ago. Here is what Microsoft fixed in today's update: [Graphics] Fixed: An issue where external graphics cards connected through Thunderbolt weren’t always recognized in some cases. [Input (know issue)] Fixed: An issue when using the Microsoft Changjie IME (input method editor) for Traditional Chinese might cause problems such as not being able to form or select words, an unresponsive spacebar or blank key, incorrect word output, or a broken candidate window display. This can occur after installing KB5062553. Fixed: This update addresses an issue that affects Phonetic input methods, including the Hindi Phonetic Input keyboard and the Marathi Phonetic keyboard, which might not work correctly after installing KB5062553. [Group Policy Editor] Fixed: This update addresses an issue where the Group Policy Editor shows error messages like “No element was expected but found” or “Encountered an unknown error” when opened. [Windows Firewall] Fixed: This update addresses an issue found in Event Viewer as Event 2042 for Windows Firewall with Advanced Security. The event appears as “Config Read Failed” with the message “More data is available.” For more information about this issue, see “Error events are logged for Windows Firewall” in the Windows Health Dashboard. You can find the updated announcement post on the official Windows Blog website. All these changes are expected later this month as part of the July 2025 non-security update for Windows 11.
    • Hynix P41 2TB Gen4 NVMe 2280 SSD is priced just $115 by Sayan Sen If you are SSD shopping, especially an M.2 2280 NVMe drive, then will certainly want to have a look at the Platinum P41 from SK hynix, which is currently back to its lowest price in the last six or so months (purchase link down below). The Platinum P41 is a Gen4 SSD that promises sequential reads and writes of up to 7000MB/s and 6500MB/s, respectively. Meanwhile, the sequential read and write speeds are rated at up to 1400K IOPS and 1300K IOPS, respectively. The 2TB variant of the P41, which is the discounted one, features a 2GB DDR4 DRAM cache as well and is meant to improve write caching and random access times, thanks to quicker metadata look-ups. Hynix says that the drive can operate at temperatures of up to 70 °C and thus you should opt for a heatsink if you intend to do data transfers for longer periods at a time. That should not be a problem, as the P41 Platinum is based on 176-layer TLC NAND and has a rated endurance of up to 1200 TBW (terabytes written) for 2TB. Get it at the link below: SK hynix Platinum P41 M2 SSD 2TB: $129.99 + $15 off with promo code EPEUA626, limited offer => $114.99 (Sold and Shipped by Newegg US) Make sure to update the firmware for the Platinum P41, as it fixes a throttling issue wherein the SSD would drop speeds after being used for several months (via Lower-Tone-3503 on Reddit). SSD firmware updates can often resolve critical problems, like in the case of WD/SanDisk SSDs, for example, which are still blocking Windows 11 24H2 due to inappropriate firmware.
    • Good feedback! I will keep this in mind.
  • Recent Achievements

    • Reacting Well
      Mokisharo earned a badge
      Reacting Well
    • Week One Done
      stevecastellano66 earned a badge
      Week One Done
    • One Month Later
      rshit earned a badge
      One Month Later
    • Week One Done
      rshit earned a badge
      Week One Done
    • Reacting Well
      ThatGuyOnline earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      430
    2. 2
      ATLien_0
      227
    3. 3
      +FloatingFatMan
      167
    4. 4
      Xenon
      133
    5. 5
      Michael Scrip
      126
  • Tell a friend

    Love Neowin? Tell a friend!