WORCESTER, Mass. — The Worcester Bravehearts (31-21) beat the Old Orchard Beach Raging Tide (19-33) 6-2 on Wednesday at Fitton Field behind Andy Lack, who went 2-for-2 at the plate. Lack singled in the third and fifth innings.
Tyrone Miller pitched lights out for the Bravehearts. Miller held the Raging Tide hitless over four innings relief, allowing no earned runs, with six strikeouts and no walks.
The Tide scored both its runs in the fourth, on a wild pitch and an error. The Tide offense was held to just three hits in the game.
The Bravehearts trailed 2-1 after four innings, but changed that in the fifth with a four-run inning against Tide starter Tim Holmes.
Holmes lasted six innings, but gave up six runs on eight hits, with three walks against seven strikeouts.
Dillon Corliss allowed just one hit over the final two innings in relief of Holmes.
Aaron Wilson stole his 37th base of the season in the fourth, which put him in position to score the Tide’s first run.
Cooper named Player of the Night
Despite OOB’s loss on Tuesday night to Seacoast, Rahiem Cooper did enough at the plate to earn the FCBL’s Player of the Night honors. Cooper went 2-for-4 in the game, with a triple and a home run, and scored two runs.
Comments are not available on this story. Read more about why we allow commenting on some stories and not on others.
We believe it's important to offer commenting on certain stories as a benefit to our readers. At its best, our comments sections can be a productive platform for readers to engage with our journalism, offer thoughts on coverage and issues, and drive conversation in a respectful, solutions-based way. It's a form of open discourse that can be useful to our community, public officials, journalists and others.
We do not enable comments on everything — exceptions include most crime stories, and coverage involving personal tragedy or sensitive issues that invite personal attacks instead of thoughtful discussion.
You can read more here about our commenting policy and terms of use. More information is also found on our FAQs.
Show less