Don't miss

Wednesday, April 16, 2014

Reds' Aroldis Chapman: bullpens every three days during road trip


By on 4/16/2014 09:15:00 PM

After that vicious line drive hit his face late in Spring Training, Cincinnati Reds closer Aroldis Chapman is already on track to pitch again before long. MLB.com's Mark Sheldon reports that Chapman will throw a bullpen session on Thursday, his second since the surgery to repair the fracture that the line drive caused in Chapman's face.


Sheldon says that Chapman will throw every three days throughout the duration of the Reds' road trip that runs from Thursday, April 17, through Sunday, April 27. This schedule would allow Chapman to pitch live batting practice near the end of the trip. Sheldon quotes manager Bryan Price describing the schedule laid out for his flame-throwing closer. Said Price,
"He's going to be on a roughly every third day throwing schedule. He'll probably get a minimum three-to-four bullpens before he throws a live batting practice, which could take place by the end of the road trip if everything continues to go well."
Chapman will continue to have exams throughout the trip to make sure that he is ready to face hitters or even take fielding practice. Price also said that Chapman will have to rebuild his stamina since he has not had much conditioning since the injury. He has thrown enough to keep his arm strong, but he will have to regain his leg and body strength.

The Reds bullpen is currently 2 for 5 in saves opportunities as play begins on April 16. Jonathan Broxton and Manny Parra are each 1 for 1, but J.J. Hoover and Logan Ondrusek are combined 0 for 3 with 2 losses. Often, the save is lost before Chapman would enter the game, but having him in the bullpen gives opposing managers something extra to consider when making decisions late in the game. Chapman was 38 for 43 in save opportunities in each of the past two seasons.

Currently, there is no timetable for Chapman's return.

Follow Raymond on Twitter @RayBureau.
Like Raymond’s “Baseball Bureau” page on Facebook.


0 comments:

Post a Comment

 
73eccce7a3ad1b23db7f38e1b8fed842050545899fe4d7b648

621dcbec1b2d3274560a101af3a95ae769e316e0