Friday, May 24, 2013
By Steve Solloway ssolloway@mainetoday.com
Staff Writer
(Continued from page 1)

Baltimore Orioles' Ryan Flaherty (3) high-fives teammates after a game against the Boston Red Sox in Baltimore on Sept. 28, 2012. Baltimore won 9-1.
AP

Ryan Flaherty
The Associated Press
"He's a tall kid (6-foot-3) so he stands out that way," said Ed Flaherty, the longtime baseball coach at the University of Southern Maine. "You know how it is."
I know a father and a family who wouldn't dream of blowing their own horns or beating their own drums.
Ed Flaherty can't really stand up and cheer, even if it is for his son. He couldn't that night in Yankee Stadium in Game 3 when his son swung at a fastball from Hiroki Kuroda.
Debbie and Ed Flaherty had seats in the first deck behind third base with other family members of Orioles players. "I knew he hit it well but it was awful high," said Ed Flaherty. "Then I saw fans starting to stand. I said to Debbie, 'my God, that's going out.'
"You get a numbness. I'm not a big cheering guy, as you know. My wife and I just looked at each other. The next thing I know, my cell phone is going off. In five minutes I probably got 25 text messages from my players."
Ed Flaherty has watched the replays. He noticed his son's deadpan expression as he ran around the bases. He must have noticed the bubblegum popping in his mouth.
In most of the Flaherty video highlight clips online, you can see the bubblegum after other home runs and fielding plays.
Has the kid from Deering High changed? Yes and no. It depends how you look at it. He's a major league ballplayer.
Staff Writer Steve Solloway can be contacted at 791-6412 or at: ssolloway@pressherald.com
Twitter: SteveSolloway
Tweet
Further Discussion
Here at PressHerald.com we value our readers and are committed to growing our community by encouraging you to add to the discussion. To ensure conscientious dialogue we have implemented a strict no-bullying policy. To participate, you must follow our Terms of Use.Questions about the article? Add them below and we’ll try to answer them or do a follow-up post as soon as we can. Technical problems? Email them to us with an exact description of the problem. Make sure to include: