http://iscoresports.com/

I opened the play by play for today's game, and found this:

SACBTS: { guid=41E06C80-1563-412B-AE3C-112AA99F4A6B, update_dt=1269646833.45154, type=SACBTS, bt_act=3:1, ft_act=, home_at_bat=1, visitor_at_bat=4, visitor_score=0, home_score=0, outs=1, inning=1, top_inning=0, courtesy_runners=, strikes=0, } : Prev=,

where there should have been a sac bunt.

Looking at it a little, I found that iScore recorded the batter as safe at first and then forced out...

Is there a reason that iScore would think that the batter-runner is safe on a successful SAC bunt?

Is that even possible?

Does not happen often, but yes, it can happen (and the rarity is why it is not showing right in Play by Play... we will get that fixed right away - probably before you read this response unless you are fast).

One way it would happen is for a player to lay down a Sacrifice Bunt, a fielder fields it, and goes to 2nd intead of first, but the runner is safe at 2nd. Since the batter was attempting a Sacrifice, they still get credited with a Sacrifice (as opposed to a Fielders Choice which would be a hit against their batting average). Had the runner been out at second base, then this would be scored as a Fielders Choice.