By BRENT STUBBS
Senior Sports Reporter
bstubbs@tribunemedia.net
AS he continues his comeback from an injury that hampered him from completing his sophomore collegiate season in May, Justin Roberts played in his third Futures Tournament, but fell short of getting into the main draw for the third time this year.
Coming off his second round main draw loss last week at the USA F19 Futures in Buffalo, New York, Roberts participated in the USA F20 Futures in Rochester, New York, where he suffered a 6-3, 3-6, 6-3 loss to Evan Zhu of the United States in the third round of the qualifying segment.
“I think I played well for the most part,” Robert told The Tribune after the match. “It was a battle with only one break a set. This was the best I’ve played these three weeks.”
Roberts, the No.7 seed, won his first round match, beating Justin Ghavami from Canada 6-1, 6-3. He then pulled off a 7-6 (5), 6-3 win over American Drew Van Orderlain.
Despite the loss, Roberts feels he can take some consolation into his next tournament.
“I played pretty well,” he said. “I could have won but happy to be playing at a good level again. This was a really positive first three weeks for me.”
Roberts, a member of the University of South Florida, is not done yet.
He and partner Jody Maginley from Antigua & Barbuda will be playing doubles today against the team of William Bushamuka and Nathan Pasha, both from the United States.
Roberts, 19, won his first round main draw event at the USA F19 Futures in Buffalo, New York with a 6-3, 6-4 win over Juan Manuel Matute from Argentina before he lost 6-2, 4-6, 6-3 to Hans Hach from Mexico.
Prior to that, Roberts qualified for the main draw of the USA F17 Futures in Charlottesville, Virginia where he lost 6-4, 6-2 to Takanyl Garanganga from Zimbabwe during the week of June 7-12.
Roberts, who began playing tennis at the age of seven, is currently ranked at 1402 on the ATP list with a total of four points. He’s the only Bahamian with any ATP points.
Comments
Use the comment form below to begin a discussion about this content.
Sign in to comment
OpenID